1 .. This file is licensed under the CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE
2 .. Full license text at https://creativecommons.org/licenses/by/4.0/legalcode
7 .. _docs_E2E_network_slicing:
10 E2E Network Slicing Use Case
11 ============================
15 The objective of this use case is to realize **End-to-End 5G Network
16 Slicing** using ONAP. An End-to-End Network Slice consists of RAN (Radio
17 Access Network), Transport Network (TN) and Core Network (CN) slice
18 sub-nets. This use case intends to demonstrate the modeling,
19 orchestration (life cycle and resources) and assurance of a network
20 slice which are implemented in alignment with relevant standards. The
21 key highlights of this use case include:
23 - Modular architecture providing building blocks and flexibility under
24 various deployment scenarios
26 - Functionality aligned with 3GPP and other relevant standards such as
29 - Interfaces and APIs aligned with relevant standards (3GPP, IETF,
30 ETSI, TM Forum, etc.) while enabling easy customization through use
31 of appropriate plug-ins. This would enable easier interoperability of
32 slice management functions realized within ONAP with 3\ :sup:`rd`
33 party slice management functions, as well as northbound and
36 - Taking a step-by-step approach to realizing different architectural
37 options in an extendable manner.
39 - Providing flexibility in network slice selection by providing an
40 option of manual intervention, as well as abstracting the network
43 - The use case implementation team is composed of service providers,
44 software and hardware vendors, solution providers and system
45 integrators thereby taking into consideration different perspectives
48 This use case is a multi-release effort in ONAP with the first steps
49 taken in Frankfurt release. It will continue to expand in scope both in
50 breadth and depth, and along the journey it shall also align with
51 updates to the relevant standards which are also currently evolving.
52 This use case shall also collaborate with SDOs such as
53 O-RAN and ETSI to enable wider adoption and use.
57 3GPP(TS 28.801) defines three layer slice management functions which include:
59 CSMF(Communication Service Management Function):
61 • Responsible for translating the communication service related requirement to network slice related requirements.
63 • Communicate with Network Slice Management Function (NSMF).
65 NSMF(Network Slice Management Function):
67 • Responsible for management and orchestration of NSI.
68 • Derive network slice subnet related requirements from network slice related requirements.
69 • Communicate with the Network Slice Subnet Management Function (NSSMF) and Communication Service Management Function.
71 NSSMF(Network Slice Subnet Management Function):
73 • Responsible for management and orchestration of NSSI.
74 • Communicate with the NSMF.
76 To realize the three layers of the slice management function, we need to decide whether to implement CSMF, NSMF or NSMF within ONAP, or use the external CSMF, NSMF or NSSMF. This implies that for ONAP-based network slice management, we have different choices from an architectural perspective:
78 1) Implement CSMF, NSMF, NSSMF all within ONAP;
80 2) Connect an external CSMF from the Northbound, Implement NSMF and NSSMF within ONAP;
82 3) Connect an external CSMF from the Northbound, Implement NSMF within ONAP, Connect a 3rd party NSSMF from the Southbound;
84 4) Implement CSMF, NSMF within ONAP, Connect a 3rd party NSSMF from then Southbound.
86 5) Use external CSMF and NSMF, only implement NSSMF within ONAP.
90 The guiding principle is when a Slice Management function is outside ONAP, standard interfaces/APIs (3GPP, IETF, ETSI, TM Forum, etc.) can be supported by default, while any customization of such interfaces shall also be supported by ONAP using suitable plug-ins/adaptors. This would enable easier interoperability of slice management functions realized within ONAP with 3rd party slice management functions, as well as northbound and southbound systems.
92 Another key point would be that both internal and external interface mechanisms should be supported by the corresponding ONAP modules. To be more specific, communication between Slice Management Functions within ONAP (e.g., CSMF and NSMF) shall use ONAP internal mechanisms such as workflow calls, DMaaPmessages, etc. or standard APIs as appropriate. For example, SO acting as NSMF should support API call directly from CSMF in ONAP, as well as API trigger from an external CSMF via EXT-API.
94 Network Slice Instance (NSI) Life Cycle View
95 --------------------------------------------
96 3GPP Specification (3GPP TS 28.530) describes management aspects of a Network Slice Instance, which can be described by the four phases:
98 Preparation: The preparation phase includes network slice design, network slice capacity planning, on-boarding and evaluation of the network functions, preparing the network environment and other necessary preparations required to be done before the creation of an NSI
99 Commisioning: NSI provisioning in the commissioning phase includes creation of the NSI. During NSI creation all needed resources are allocated and configured to satisfy the network slice requirements. The creation of an NSI can include creation and/or modification of the NSI constituents
100 Operation:The Operation phase includes the activation, supervision, performance reporting (e.g. for KPI monitoring), resource capacity planning, modification,and de-activation of an NSI.
101 Decommissioning: Network slice instance provisioning in the decommissioning phase includes decommissioning of non-shared constituents if required and removing the NSI specific configuration from the shared constituents. After the decommissioning phase, the NSI is terminated and does not exist anymore.
102 The ONAP-based NSI lifecycle management will finally provide the demonstration of all these phases.
107 +---------------+--------------------------------------------+
108 | Abbreviation | Meaning |
109 +===============+============================================+
110 | CSMF | Communication Service Management Function |
111 +---------------+--------------------------------------------+
112 | CSI | Communication Service Instance |
113 +---------------+--------------------------------------------+
114 | CST | Communication Service Template |
115 +---------------+--------------------------------------------+
116 | NSI | Network Slice Instance |
117 +---------------+--------------------------------------------+
118 | NSMF | Network Slice Management Function |
119 +---------------+--------------------------------------------+
120 | NSSI | Network Slice Sub-net Instance |
121 +---------------+--------------------------------------------+
122 | NSSMF | Network Slice Sub-net Management Function |
123 +---------------+--------------------------------------------+
124 | NST | Network Slice Template |
125 +---------------+--------------------------------------------+
126 | NSST | Network Slice Sub-net Template |
127 +---------------+--------------------------------------------+
130 Recap of Frankfurt functionality
131 --------------------------------
132 In Frankfurt release, CSMF and NSMF within ONAP was implemented, while connecting to an external Core NSSMF.
133 From the NSI Life Cycle perspective, the scope for Frankfurt included NSI design and pre-provision, NSI instantiation
134 and configuration, and NSI activation and deactivation. In particular:
136 - CSMF: Functions of slice service creation, slice service activation and deactivation were implemented.
138 - NSMF: Functions of NSI instantiation, NSI activation and deactivation were implemented. In addition, manual
139 intervention is also provided in NSMF slice task management portal to ensure the selected NSI/NSSI as well as
140 Service Profile and Slice Profile are OK or need adjustment.
142 - Design of CST, NST and onboarding NSST that are required to support the run-time orchestration functions
144 - To connect to the external (core) NSSMF, an adaptor was implemented to provide interface between ONAP and 3rd party
147 To support the above functions, code impacts in U-UI, SO, OOF and ExtAPI components, and schema change in A&AI
148 were implemented. See the `Proposed Functions for R6 and Impacted Modules wiki page <https://wiki.onap.org/display/DW/Proposed+Functions+for+R6+and+Impacted+Modules>`_ for details.
150 As part of Frankfurt release work, we supported the minimum-scope installation of ONAP to reduce the resource requirements.
151 From the module perspective, 5G E2E Slicing use case involves SDC, SO, A&AI, UUI, EXT-API, OOF and Policy modules of ONAP.
152 So we will configure these required modules along with the mandatory common modules such as DMaaP. Further, for each module,
153 the use case also does not use all of the charts,so we removed the not needed Charts under those modules to optimize the
154 resources required for setting up the use case. This approach will help to install a minimum-scope version ONAP for the
155 E2E Slicing use case.
157 Further details of the installation steps are available at: `Install Minimum Scope ONAP for 5G Network Slicing wiki page
158 <https://wiki.onap.org/display/DW/Install+Minimum+Scope+ONAP+for+5G+Network+Slicing>`_
160 Recap of Guilin functionality
161 -----------------------------
162 From the architecture point of view, in Guilin release, besides the continuation of NSMF which was implemented in
163 Frankfurt release, the RAN NSSMF, TN NSSMF, CORE NSSMF have been implemented within ONAP, apart from interacting with
164 ezternal RAN NSSMF and external CORE NSSMF.
166 The following provides an overview of the enhancements done in Guilin release:
168 - **Enhancements in NSMF**: Service Profile decomposition into Slice Profiles for 3 domains, NSI selection enhancement,
169 E2E slice instance creation including RAN, TN and CN slice sub-net instance creation/reuse, activation/deactivation
170 of E2E slice, and deciding whether to terminate E2E slice or not.
172 - **RAN NSSMF, TN NSSMF, CN NSSMF within ONAP**: Basic logic for all 3 NSSMFs to support NSSI allocation, activation,
173 deactivation, deletion and modification (in case of reuse of NSSI).
175 - **Enable NSMF interaction with RAN NSSMF, TN NSSMF, CN NSSMF**: Implement generic NSSMF adaptor for three domain NSSMFs,
176 alignment with standard intefaces (3GPP, IETF), enable the connection to external RAN NSSMF.
178 - **Design of RAN NSST, TN NSST, CN NSST and Slice Profiles, TN information models**: Basic E2E Slicing model was provided
179 all the related templates designed from SDC, TN related information models.
181 - **TMF 641 support**: Extension of the TMF 641 based interface from NB of ExtAPI to support service activation,
182 deactivation and termination.
184 - **RAN and CN NFs set up and initial configurations**: CN NF simulators was developed: AMF, SMF, UPF and configure the
185 S-NSSAI on CN NFs; RAN NF Simulator was enhanced for PM data reporting, CU and Near-RT RIC configuration.
187 - **KPI monitoring**: Implementation to request details of a KPI via UUI to ONAP DCAE. Providing the requested data to UUI
188 by DCAE using a new microservice (Data Exposure Service - DES). Enhancements in PM-Mapper to do KPI computation is
189 in progress, and will be completed in Honolulu release.
191 - **Closed Loop**: First steps to realizing a simple Closed Loop in the RAN using PM data collected from the RAN was
192 implemented - update the allowed throughput for a S-NSSAI per Near-RT RIC coverage area based on DL/UL PRB for data
193 traffic that was reported from the RAN. The analysis of the PM data was done using a new Slice Analysis MS in DCAE,
194 and the Policy-based Control Loop framework was applied to trigger the updates in the RAN.
196 - **Intelligent Slicing**: First steps to realizing a simple ML-based Closed Loop action in the RAN using PM data collected
197 from the RAN was implemented - update the maxNumberofConns for a S-NSSAI in each cell based on PDU session related
198 PM data that was reported from the RAN (PDU sessions requested, successfully setup and failed to be set up). The
199 training was done offline, and the ML model is onboarded as a micro-service to ONAP for demo purpose alone (it is
200 not part of ONAP code/repos). The ML model provides updates to the Slice Analysis MS, which then uses the
201 Policy-based Control Loop framework to trigger the updates in the RAN.
203 - **Modeling enhancements**: Necessary modeling enhancements to support all the above functionalities.
205 The base use case page for Guilin release is `E2E Network Slicing Use Case in R7 Guilin <https://wiki.onap.org/display/DW/E2E+Network+Slicing+Use+Case+in+R7+Guilin>`_.
207 The child wiki pages of the above page contains details of the assumptions, flows and other relevant details.
209 Honolulu release updates
210 ------------------------
211 In Honolulu release, the following aspects were realized:
213 - **Modeling Enhancements** were made, details can be found at:
214 `Modeling enhancements in Honolulu <https://wiki.onap.org/display/DW/Modeling+enhancements+in+Honolulu>`_.
216 - **Functional Enhancements**
218 (a) Minor enhancements in NSMF and NSSMFs including NST Selection, Shared slices, coverageArea to
219 coverageAreaTAList mapping, etc.
220 (b) Enhancements related to endpoints for stitching together an end-to-end network slice
221 (c) Use of CPS (instead of Config DB) to determine the list of Tracking Areas corresponding to a given
222 Coverage Area (input by user). For the remaining RAN configuration data, we continue to use Config DB.
223 (d) RRM Policy update by SDN-R to RAN NFs during RAN NSSI creation/reuse
225 - **Integration Testing**
226 Continuing with integration tests deferred in Guilin release, and associated bug-fixing
230 (a) 2 deployment scenarios for RAN NSSI are supported. In the first scenario, the RAN NSSI comprises also of
231 TN Fronthaul (FH) and TN Midhaul (FH) NSSIs, and RAN NSSMF shall trigger TN NSSMF for TN FH and MH NSSI
232 related actions. In the second scenario, the RAN NSSI comprises only of RAN NFs. TN NSSMF shall be triggered by
233 NSMF for TN FH and MH NSSI related actions. This part is not yet implemented in NSMF within ONAP.
235 (b) Details of the modeling aspects, flows and other relevant info about the use case are available in:
236 `R8 E2E Network Slicing Use Case <https://wiki.onap.org/display/DW/R8+E2E+Network+Slicing+use+case>`_ and its child wiki pages.
239 Impacted Modules for Honolulu
240 -----------------------------
241 The code-impacted modules of E2E Network Slicing in Honolulu release are:
243 - **UUI**: The enhancements done include:
245 (a) The coverageArea The coverageArea number param is added in CSMF creation UI. Users could input
246 the grid numbers to specify the area where they want the slicing service to cover.
247 (b) The relation link image of AN/TN/CN has been added. Users can see the links and related params
248 of the three domains.
249 (c) The TN’s connection link with AN/CN has been added in NS Task management GUI.
251 - **AAI**: Schema changes were introduced. We added some new parameters in 2 nodes:
253 (a) ‘Connectivity’ is used to store IETF/ACTN ETH service parameters. New attributes added in order
254 to support the CCVPN network configuration operations on multi-domain (2+) interconnections.
255 (b) ‘Vpn-binding’is used to store ACTN OTN Tunnel model’s parameters.
257 - **OOF**: Updates include:
259 (a) NST selection is enhanced by fetching the templates from SDC directly.
260 (b) coverageArea to coverageAreaTAList mapping is done by OOF (as part of Slice Profile generation)
264 - **SO**: Main updates include support of NSI shared scenarios by enhancing the interaction with OOF, AAI and
265 UUI. Apart from this some updates/fixes have been made in NSMF, RAN/Core/TN NSSMF functionality in SO, for
268 (a) *NSMF*: Update NSI selection process support shared NSI and add sst parameter
269 (b) *AN NSSMF*: Activation flow for SDN-R interactions, allocate flow & added timeDelay in QueryJobStatus,
270 support of Option 1 for topmost RAN NSSI
271 (c) *CN NSSMF*: Non-shared allocate flow
272 (d) *TN NSSMF*: Modify TN NSSI operation
274 - **CPS**: 2 APIs required for the use case are supported. The remaining yang models are also onboarded,
275 however, the API work as well as further enhancements to CPS Core, NF Proxy and Template-Based Data
276 Model Transformer Service shall continue beyond Honolulu.
278 - **SDN-R**: RRMP Policy updates, enhancements for updating the RAN configuration during slice reuse,
279 closed loop and intelligent slicing.
283 (a) *KPI Computation MS*: This MS was introduced newly for computation of slice related KPIs. In this release,
284 it supports basic KPI computation based on formula specified via Policy. Further details about this MS is
285 available at `KPI Computation MS <https://wiki.onap.org/display/DW/DCAE+R8+KPI-Computation+ms>`_
286 (b) *Slice Analysis MS*: Minor updates were done.
288 Apart from the above, Policy and SDC had test-only impact for this use case.
292 - **Config DB** was updated to handle bugs and gaps found during testing. This is not an official ONAP component, and
293 its functionality is expected to be performed fully by the Configuration Persistence Service (CPS) in future ONAP
294 release (beyond Honolulu).
296 - **Core NF simulator** and *ACTN simulator* were also updated and checked into ONAP simulator repo.
298 - **RAN-Sim** has been updated to fix bugs found during testing, and also checked into ONAP simulator repo.
301 Functional Test Cases
302 ---------------------
303 The functional testing of this use case shall cover CSMF/NSMF, the 3 NSSMFs and Closed Loop functionality. We classify the
304 test cases into 5 tracks: CSMF/NSMF, RAN NSSMF, Core NSSMF, TN NSSMF and Closed Loop.
305 Details of the test cases can be found at:
306 `Integration Test details for Honolulu <https://wiki.onap.org/display/DW/Integration+Test+details+for+Honolulu>`_ and its child wiki pages.
311 The Honolulu release setup details for the E2E Network Slicing use case will be available at the following page and its
313 `User Operation Guide for Honolulu release <https://wiki.onap.org/display/DW/User+Operation+Guide+for+Honolulu+release>`_
316 Known Issues and Resolutions
317 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
318 Details of manual configurations, work-arounds and known issues will be documented in the child wiki pages of:
319 `User Operation Guide for Honolulu release <https://wiki.onap.org/display/DW/User+Operation+Guide+for+Honolulu+release>`_
321 The foll. integration tests are carried over to Istanbul release: see `REQ-721 <https://jira.onap.org/browse/REQ-721>`_
322 - NSMF: Option 2 testing, remaining regression testing and service termination testing for NSMF
323 - RAN NSSMF: RAN NSSI termination, interactions with TN NSSMF for FH/BH NSSI reuse and some minor aspects related to SDN-R <-> RAN interaction
324 - TN NSSMF: Checking some minor aspects in SO for modifying TN NSSI.
325 - Core NSSMF: Modifying and deallocating a Core NSSI, reusing an existing Core NSSI
326 - KPI Computation, Closed Loop & Intelligent Slicing: Some minor aspects on SDN-R <-> RAN-Sim interface needs to be addressed.
328 Further details of these test cases can be found in REQ jiras for integration testing for Honolulu, and in the
329 use case wiki. This means that the functionality associated with these test cases may require updated versions
330 of the relevant components - the User Operation Guide will also be updated with details of any bug fixes
331 beyond Honolulu as the testing is anyhow continuing as part of Istanbul release.
333 Istanbul release updates
334 ------------------------
335 Below aspects are covered in Istanbul release:
337 1. **CPS-TBDMT Enhancements** - This service shall be used to map the erstwhile Config-DB-like REST APIs to appropriate CPS API calls. The purpose of this service is to abstract the details of (possibly multiple, and complex) XPath queries from the users of CPS. It enables CPS-users to continue using simple REST API calls that are intuitive and easy-to-understand and implement. The mapping to appropriate queries to CPS (including mapping of one API call to many Xpath queries) shall be done in a generic way by the CPS-TBDMT service. In Istanbul release, following are the main enhancements done:
339 - Support edit query ie. post, put and patch requests to CPS
341 - Support Output Transformation
343 (a) Extract desired output from the data returned from CPS.
344 (b) If 'transformParam' is not defined in the template no transformation takes place.
345 - Support Multiple query
347 (a) Make multiple queries to CPS in single request.
348 (b) If 'multipleQueryTemplateId' is mentioned in the template, it will execute this template first and insert the result to the current template to make multiple queries to CPS.
349 - Support Delete data requests to CPS
351 (a) Process delete request type.
352 - Support for dynamic anchor - Accept anchors at run time and execute query
354 2. **CPS Integration**
356 - Config DB is replaced with the CPS component to read, write, update and delete the RAN Slice details. CPS APIs are accessed via CPS-TBDMT component. CPS integration with DCAE - Slice Analysis MS and OOF are completed. SDN-R integration with CPS is completed for the shared RAN Slice flow, activateRANslice and terminateRANSlice implementations are in progress.
357 - A new SDN-C karaf feature is introduced to register the cm-handle (anchor) with CPS. The integration with CPS-DMI plugin will be done in Jakarta release.
359 3. **NSMF based TN Slices** - Support for interacting with TN NSSMF directly from NSMF for front haul and mid haul slice subnets. There will be separate SDC template for this scenario. NST will have 5 NSSTs - CN NSST, AN NSST, TN FH NSST, TN MH NSST, TN BH NSST.
361 4. **KPI Monitoring** - Implementation is done in KPI Computation MS to configure the required KPIs and the KPI computaion formula based on policies.
363 5. **Closed Loop** - Closed Loop updates are sent over A1 interface to NearRT-RIC. This is done at the POC level. This will be further enhanced in Jakarta release to make use of the A1-Policy Management Service in CCSDK.
365 6. **Intelligent Slicing** - End to end intelligent slicing - closed loop flow is tested with the initial version of Machine Learning MS.
367 7. **Carry-over Testing from Honolulu Release**
371 (a) Testing completed for the allocation, modification, activation and deactivation of the RAN slice to support option1
372 (b) Integration Testing of AN NSSMF with SDNR interactions for allocate and modify flow is completed
375 (a) Service instantiation for non-shared and shared scenario and fixes to support option 1 are done
376 (b) NSI selection process support for shared NSI is tested
378 Impacted Modules for Istanbul Release
379 -------------------------------------
381 (a) Support of NSI termination by enhancing the interaction with OOF, AAI and UUI
382 (b) RAN NSSI Termination support with OOF & SDN-R interactions
383 (c) Bug fixes in Option 1 (CSMF, NSMF and NSSMFs are within ONAP & TN-FH, TN-MH are created by RAN NSSMF)
384 - **CSMF**: Fixed sNSSAI format and updated authentication for NSMF invocation
385 - **NSMF**: Fixes in NSI termination issues to support OOF interaction for NSI termination query and added subnet Type support for respective TN Domain
386 - **AN NSSMF**: Fixes for different termination scenarios in Option 1
387 - **CN NSSMF**: Bug fixes in shared allocate flow, modify flow and terminate flow
388 - Slice Profile alignement with NSSMF
389 (d) NSMF based TN Slices (TN-FH, TN-MH are created by NSMF) - Work flow changes to support this approach
392 (a) Integration with CPS for coverage area to coverage area TA list
393 (b) Bug fixes in NxI termination
396 (a) Minor changes in Slice Analysis MS to support CPS integration
397 (b) KPI Computation MS in enhanced to support policy based KPIs and formula
400 (a) Bug fixes in instantiateRANSliceAllocate, instantiateRANSliceAllocateModify, activateRANSlice, terminateRANSlice Directed Graphs
401 (b) CPS integration for the instantiateRANSliceAllocateModify, activateRANSlice, terminateRANSlice Directed Graphs
402 (c) A new karaf feature is introduced to register the cm-handle with CPS
405 (a) This component is enhanced to support different type of queries based on templates
408 (a) Bug fixes and support for GET, POST, PATCH and DELETE type of queries.
410 Istanbul Release - Functional Test cases
411 ----------------------------------------
412 **Honolulu release carry-over test cases**
413 (a) Different possible scenarios of E2E Slice (eMBB) creation are tested in I-release
414 (b) RAN slice Termination testing completed
415 (c) Test cases to validate slice reuse and terminate using Option 2 (Core NSSMF and RAN NSSMF external) are completed
417 **R9 Integration Testing**
418 (a) RAN NSSMF integration with CPS is covered for RANSlice modification, activation, deactivation and termination
419 (b) NSMF driven TN-FH and TN-MH slices creation is tested
420 (c) CPS impacts in closed loop scenario is validated and few test cases are deferred to Jakarta release
422 Integration test plan is available at `Integration Testing in Instanbul Release <https://wiki.onap.org/display/DW/R9+Integration+Test+for+E2E+Network+Slicing>`_
424 Istanbul Release - Operation Guidance
425 -------------------------------------
426 The steps for E2E network slicing use case will be available at `User Operation Guidance - Istanbul Release <https://wiki.onap.org/pages/viewpage.action?pageId=111118867>`_. It is an update to the user manual created in Honolulu release.
428 Istanbul Release - Known issues and Solutions
429 ---------------------------------------------
431 **REGISTER 3RD PARTY CONTROLLERS**
433 The ONAP TSC approved on July 9th, 2020 to change the status of ESR GUI Module
434 to an 'unmaintained' project. Further information about 'Unmaintained Projects'
435 can be found in the `ONAP Developer Wiki. <https://wiki.onap.org/x/Pw_LBQ>`__
437 But excluding the ESR GUI module from ONAP does not mean that the “external
438 system registration” mechanism is excluded; i.e. only the GUI is not available
441 Nevertheless, in order to register the 3rd party controllers (like it is done
442 in E2E network slicing use case and recently in Cloud Leased Line “CLL” use
443 case as part of Intent-Based Networking), AAI’s API are invoked manually.
445 To do so, please send the following CURL command (PUT) to your AAI, with the
446 attached xml payload. In the payload, please adjust the controller name (in
447 this case sdnc1) and the controller ip address accordingly based on your
454 curl -k -X PUT https://{{your-onap-ip-address}}:30233/aai/v16/external-system/esr-thirdparty-sdnc-list/esr-thirdparty-sdnc/sdnc1 -u "AAI:AAI" -H "X-FromAppId:postman" -H "Content-Type:application/xml" -H "Accept: application/xml" -H "X-TransactionId:9999" -d @/home/onap/esr-registration-controller-1.xml
457 PAYLOAD (esr-registration-controller-1.xml):
461 <?xml version="1.0" encoding="UTF-8"?>
462 <esr-thirdparty-sdnc xmlns="http://org.onap.aai.inventory/v16">
463 <thirdparty-sdnc-id>sdnc1</thirdparty-sdnc-id>
464 <location>Core</location>
465 <product-name>TSDN</product-name>
466 <esr-system-info-list>
468 <esr-system-info-id>sdnc1</esr-system-info-id>
469 <system-name>sdnc1</system-name>
471 <vendor>Huawei</vendor>
472 <version>V3R1</version>
473 <service-url>http://192.168.198.10:18181</service-url>
474 <user-name>onos</user-name>
475 <password>rocks</password>
476 <system-type>nce-t-controller</system-type>
477 <protocol>RESTCONF</protocol>
478 <ssl-cacert>example-ssl-cacert-val-20589</ssl-cacert>
479 <ssl-insecure>true</ssl-insecure>
480 <ip-address>192.168.198.10</ip-address>
482 <cloud-domain>example-cloud-domain-val-76077</cloud-domain>
483 <default-tenant>example-default-tenant-val-71148</default-tenant>
484 <passive>true</passive>
485 <remote-path>example-remotepath-val-5833</remote-path>
486 <system-status>example-system-status-val-23435</system-status>
488 </esr-system-info-list>
489 </esr-thirdparty-sdnc>
492 Additional issues occured during the deployment and integration testing will be
493 listed in the ONAP Developer Wiki at `Network Slicing - Issues and Solutions <https://wiki.onap.org/display/DW/Network+Slicing+-+Issues+and+Solutions>`_