...
| Item | Notes |
|---|---|
MULTI-LANGUAGE SUPPORT | LANGUAGE – Check on representation of location for Non-western Languages & scripts. Civil address specify in the data. How would A&AI represent addresses but expressed in different language. Store the address with way to designate language type. Relevant only if SP deals with more than one language at a time.
|
| ALIGN SOL001 & A&AI | There are 12 elements from the civic_address_element that do not map “nicely” to the complex elements fields. These are notably: division, block, street group, additional loc info, residence name, unit, floor, room, postal name, PO box, additional Code, seat/cubicle. We need to decide if we wish to intentionally not map these or introduce new fields into the complex object. Note this item is dependent on a number of above items being solved first. ACTION: Analysis to complex object. If what’s in complex object is sufficient and raise at the modeling and second opinion. (1) Internationalize the complex object, IETF 4776. (2) resolution. Maybe generalize the country/regional specific location elements. as a discussion group, discuss the model; for the missing field would have to show that there is a need within ONAP; is there a ONAP requirements for those item. Is there another attribute that covers that or is it something new that needs to be added. a Topic in Common. If the discussion would is good with it discuss it in Poll. RESULT: (Oct 3) should be covered with the analysis & development of the PLACE & Complex object (see above) |
| PNF PLUG and PLAY | During PNF PnP PNFRegistration VES event will send information about the PNF Eventually sends civic address & geolocation information in the VES event. (1) VES PNFregistration VES events need to be updated. (2) decide which parameters we want to have the VES event report. |
...
| TOPIC | DISCUSSION |
|---|---|
| PNFD MAPPING | PNFD and ending up in an instance data (A&AI Model mapping) |
TOPIC #4
| TOPIC | DISCUSSION |
|---|---|
| 5G Service Model Use Case | The 5G service model use case in R6 5G RAN SERVICE MODELING & DEFINITION in R6 Frankfurt is analyzing 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 Runtime Config DB. Parameters related to inventory & commissioning would go to A&AI and schema updates. Others (run-time) would go into the runTime DB. in R6 we expect only modeling analysis, in R7 look and see which parameters might actually be used. Onboarding - and schema definition for RunTime Cfg DB could be either (a) artifact loaded from vendors and (b) pre-defined driven from standards. Arch. Flows that are used: SDC artifact distribution, RunTime Cfg DB flows. Presentations: Modeling S/C calls, U/C realization call, 5G U/C call. |
LOGISTICS
| TOPIC | DISCUSSION |
|---|---|
| TIMETABLE (WHAT RELEASE TO INTRODUCE) | Investigate when these would be really necessary. Are they needed in R6? Our discussion today (educated guess) is that they will be needed probably a release or two AFTER an actual, real physical DU is integrated with ONAP. No code changes being requested in R6; but will likely need S/W changes in R7. ACTION: R6: OUTPUT in R6 - Need to document what S/W and U/C (PnP) impacts that there will be. Schema impacts, API changes, and consumers of the API impacts. |
| NEXT MEETING | Meeting on the FIRST Thursday of Each Month ONAP Meeting 4 is inviting you to a scheduled Zoom meeting. Meeting ID: 112 318 171 |
...
| Recording | File | ||||||
|---|---|---|---|---|---|---|---|
Zoom Video / Audio MP4 |
| ||||||
Audio Only M4A |
| ||||||
Playback M3U |
|
ADDENDUM
Complex Object Fields
...