@Juan Iturralde I think you need to structure a bit better the use case.
Based on your first description
"
This time, I need support related with the business case in which it's needed check geographic attributes. These attributes could be technical, comercial or regulatory. With this information, we need to generate the product offering showed to the customer. Some examples of these attributes are: Max Speed, Bandwidth, ToIP Available, TV Type Available, etc."
Analyzing the information I can see the following:
- GOAL: "we need to generate the product offering showed to the customer"
- I may imagine you mean "selecting" the ProductOffering
- Coverage: "I need support related with the business case in which it's needed check geographic attributes"
- what is the goal? as I said before ... coverage? feasibility? serviciability?
- Characteristics: "Some examples of these attributes are: Max Speed, Bandwidth, ToIP Available, TV Type Available, etc."
- there are multiple potential types like: input characteristics (from the GUI at ordering time), instance characteristics (related with fulfillment), etc.
Maybe what you need is having a catalog that contains the right Characteristics, in such a way that at ordering time and after the coverage check, you have the information to call the product APIs to filter the ProductOffering at the geographic area the customer is. But in this case we are not talking about calling one APIs but multiple ones. Pre-Commercial and commercial ones. In any case, if you do the previous categorization of catalog Offering, you will be able to call the product API for showing the offering.
hope it helps
------------------------------
------------------------------
SANTIAGO LORENTE JURADO
Pegasystems, Inc.
Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
------------------------------
------------------------------
Original Message:
Sent: Nov 14, 2019 03:11
From: Ludovic Robert
Subject: Geographic feasibility
Hi Juan
Ok ok... very straighforward:
- GeographicAddress allow to manage ....geographic address meannig formatted address based on street, country, zip code ,etc... There is a specific resource to perfom address validation
- GeographicLocation is about latitude, longitude, etc... you can manage any point or polygon representation. Ccould be used to define coverage zone or drone geo fencing for example
- Geograpic Site is specific place where a service provider are interest.... like a shop, an 4G antenna or why not a truck with mobile transmitters. A geo Site could of course related to geo Address & geo Location.
If you need more info I invite you to take a look on the APII specifications or on the SID which covers also this topic.
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
Original Message:
Sent: Nov 13, 2019 11:42
From: Juan Iturralde
Subject: Geographic feasibility
Thank you so much Ludovic Robert and SANTIAGO LORENTE JURADO for yours anwers.
My question is which of the following APIs should we use to obtain information related to the geographical area because I found these:
Geographic Address Management API
Geographic Location Management API
Geographic Site Management API
Thanks again for your help.
Regards
------------------------------
Juan Iturralde
Telecom Argentina, S.A.
Original Message:
Sent: Nov 13, 2019 02:54
From: Ludovic Robert
Subject: Geographic feasibility
Hello,
Just to provide additionnal information in addition to Santiago answer ... Juan you can take a look on 2 APIs:
TMF645: ServiceQualification: This API is very useful to check technical eligibility at service level. Of course geographic location is an input. Once you get eligible service(s) then you can leverage productCatalog API to get the product offering(s) selling these services.
TMF679: ProductOfferingQualification API: This API is useful for commercial eligibility. Geographic location could be also used in the input (when you want to restrict some offering to specific location).
Of course both API allows you to go at characteristic level to qualify not only a service/product but also a 'configured' product/service.
Hope it helps
Ludovic
------------------------------
Ludovic Robert
Orange
My answer are my own & don't represent necessarily my company or the TMF
Original Message:
Sent: Nov 12, 2019 03:56
From: SANTIAGO LORENTE JURADO
Subject: Geographic feasibility
Hola Juan
related to the subject of your question (geographics) SID 19.0 defines Location entity as the following: "The ProductOffering may also be defined by the Location(s) at which it is available (i.e. Place). Locations in the SID model are represented by the Location business entity. Customers do not need to know anything about the detailed ProductSpecification, as the enterprise tailors the ProductOffering to their needs".
However, related with the "attributes could be technical, comercial or regulatory" those can be modelled as Characteristic. Section 1.2.4. Product Characteristics, provides you with a view on them and how to use them.
You may want to explain a bit more about the use case, but it seems to me you are checking first coverage based on the customer Location and then, obtaining for this system the set of technical parameters: bandwith speed, etc available in the customer Locations.
Cheers
------------------------------
SANTIAGO LORENTE JURADO
Pegasystems, Inc.
Original Message:
Sent: Nov 11, 2019 08:11
From: Juan Iturralde
Subject: Geographic feasibility
Hi All,
This time, I need support related with the business case in which it's needed check geographic attributes. These attributes could be technical, comercial or regulatory. With this information, we need to generate the product offering showed to the customer. Some examples of these attributes are: Max Speed, Bandwidth, ToIP Available, TV Type Available, etc.
My question is about what are the APIs we should use to get this attributes?
As always, thanks for any information you could provide us.
Regards,
Juan.
------------------------------
Juan Iturralde
Telecom Argentina, S.A.
------------------------------