RFC6225 GEOLOCATION FIELDS

Geolocation fields from RFC6225.  (CLOSED) – see table below ACTION: (DONE) Fill in tie-in fields to standards elements

COMMON LOCATION MODEL  / GB922

Standard TM Forum GB922 - Location Modeling Discussion

(Email) TMF SID classes for Urban Property Address and Urban Property Sub-Address as per:

https://www.tmforum.org/resources/suite/gb922-information-framework-models-r18-5/

COMPLEX OBJECT: How-To: Register a VIM/Cloud Instance to ONAP click on "CREATE A COMPLEX OBJECT"

AAI REST API Documentation - Frankfurt (swagger for complex object) / Info Model - Data model Map between.

 {
            "physical-location-id": "clli2",
            "data-center-code": "example-data-center-code-val-6667",
            "complex-name": "clli2",
            "identity-url": "example-identity-url-val-28399",
            "physical-location-type": "example-physical-location-type-val-28399",
            "street1": "example-street1-val-28399",
            "street2": "example-street2-val-28399",
            "city": "example-city-val-28399",
            "state": "example-state-val-28399",
            "postal-code": "example-postal-code-val-28399",
            "country": "example-country-val-28399",
            "region": "example-region-val-28399",
            "latitude": "1111",
            "longitude": "2222",
            "elevation": "example-elevation-val-28399",
            "lata": "example-lata-val-28399"
 }

ETSI SOL001 - work with ETSI to incorporate it into ETSI SOL 001. Incorporate Geolocation element into ETSI SOL 001 standards.

ACTION: (DONE) Contacted Thinh N. (Nokia); Thinh RESPONDED to bring it up at the Modeling Call. Ben → Contact Thinh

ACTION: (DONE) Proposal in ETSI. Geoloc harmonization standards would go back to ETSI SOL001. Incorporate into Standards.

PNFD and ending up in an instance data (A&AI Model mapping). From PNFD (onboarded) loaded into SDC AID to A&AI

Improvement of ingestion onto SDC AID

PNF ETSI NFV SOL001 - descriptor_id, function_description, provider, version, descriptor_invariant_id, name, geographical_location_info, virtual_link

SDC - invariantUUID, uui, customizationUUID, version, type, name, description, resourceVendor, resourceVendorRelease, resourceVendorModelNumber, category, subcategory, nf_function, nf_role, nf_type, software_versions

ACTION: Go to SDC and/or CDS. Identify Use Case. Will specification for geolocation in SOL001. Geolocation in PNFD not per site. Inventory information. For vendor may not be so useful as sites instances are tied to locations not so much descriptors; for service provider probably country or region may be useful. Onboarding in ETSI. SDC → Vendor PNFD → SDC Model

The 5G service model use case in R6: 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt

5G Service Model U/C in R7: R7 5G Service Modeling

Highlights of 5G Service Model U/C

• Analyze the incorporation of 3GPP TS28.540, 3GPP TS28.541 (the 5G NRM) ~100 parameters driven from the standards that might be incorporated into the ONAP databases incl. A&AI and Configuration & Persistency Service (C&PS).
• Parameters related to inventory & commissioning would go to A&AI and schema updates. Others run-time data would go into the C&PS DB.
• Onboarding - and schema definition for C&PS DB could be either (a) artifact loaded from vendors and (b) pre-defined driven from standards.
• Arch. Flows that are used: SDC artifact distribution, C&PS DB flows.
• 5G resources for 5G BTS (DU, PNF) to introduce an object in Resource Model
• Model-driven ONAP design would eventually be used to onboard vendor specific CM information
• Introduce into Platform ONAP information model objects to support 5G NRM.

NEXT STEP: Modeling discuss with Modeling S/C. What do we need to store; information model for C&PS. path to follow to get to info needed which guides API development & schema formation. Storing information relates to Netconf yang model ; common constructs topo endpoint that you would hang w/ more detailed implementation specific resource information; extend it for any resource; common constructs. ONF. R7 mature a model to evolve. Introduce modeling requirement

In R7 OOF SON PCI Use case uses the concept of Geolocation as it relate to Cell Objects, which is a "first application" for the Geolocation model development.

Meeting on the FIRST Thursday of Each Month

ONAP Meeting 4 is inviting you to a scheduled Zoom meeting.

https://zoom.us/j/112318171

Meeting ID: 112 318 171

ONAP R7 Modeling High Level Requirements

Modeling Activity & Use Case Relevance. See Category 2 (table 2) for Geolocation development