7.4 Provisioning

28.5383GPPEdge Computing ManagementManagement and orchestrationRelease 18TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

7.4.1 Description

The clause contains procedures associated with provisioning.

7.4.2 Configuration needed for EAS registration

Figure 7.4.2-1 depicts a procedure to describe how a consumer can consume provisioning MnS to request ECSP management system to configure the EASID and EES address that are required for EAS registration procedure (see clause 8.4.3.2.1 in TS 23.558 [2]). It is assumed that the EASFunction MOI has been created.

Figure 7.4.2-1: Configuration needed for EAS registration

1. A consumer (i.e., ASP or ECSP) consumes the provisioning MnS with modifyMOIAttributes operation (see TS 28.532 [5]) to configure the EASID (clause 7.2.4 in TS 23.558 [2]) and EES address (e.g. URI).

2. ECSP management system returns notifyMOIAttributes to notify the consumer that attributes have been changed.

7.4.3 EDN NF 5GC connection provisioning

Figure 7.4.3-1 depicts a procedure to describe how ECSP management system can consume provisioning MnS to request PLMN management system to query the connection information of EDN NFs (i.e., EAS, EES, ECS) to 5GC NFs, as specified in clauses 6.3.2, 6.3.4, 6.4.6 in TS 23.558 [2]. To support the connection of EDN NFs to 5GC NFs, EcmConnectionInfo IOC should contain the following attributes:

– EDN identifier: used to determine whether the EDN is trusted by PLMN operators.- EAS, EES, and ECS IP address: indicate the indicate the EAS, EES, and ECS IP address.

– Service area requirements: including EDN service area, EES service area, and EAS service area (see clause 7.3.3 in TS 23.558 [2]) representing the service areas for ECS, EES, and EAS, respectively.

– ECM connection type: indicate the control plane connection.

– 5GC NF Connection information list: each entry in the list should contain the following attributes:

– Accessing NF type: the NF (i.e., PCF, NEF, or SCEF) where the EDN NFs should interface to access the 5GC NFs.

– IP address: the IP address of the accessing NF.

– 5GC NF DN: the DN of the accessing NF that needs to be configured in EASFunction IOC, EESFunction IOC, and ECSFunction IOC to indicate where the EDN NFs are connected.

Figure 7.4.3-1: EDN NF to access 5GC NF

1. ECSP management system consumes the provisioning MnS with createMOI operation (see clause 11.1.1.1. in TS 28.532 [5]) for EcmConnectionInfo IOC to request PLMN management system to provide the connection information. EcmConnectionInfo IOC includes EDN identifier, and service area requirements (i.e., EDN service area, EES service area, and EAS service area).

2. PLMN management system determines whether the EAS and EES are trusted by PLMN operators, based on the EDN identifier ednIdentifier.

If the EDN NFs are trusted by PLMN operators, then performs the following steps.

3. PLMN management system found the PCF(s) based on EES service area eESServiceArea, and EAS service area requiredEASservingLocation, and NEF(s) based on EDN service area eDNServiceArea, and then creates the EcmConnectionInfo MOI with connection information for PCF and NEF, including the IP address and DN.

4. PLMN management system returns the connection information in the attributeListOut of the output parameter in createMOI operation to ECSP management system.

5. Connects EDN NFs to 5GC NFs via PCF and NEF.

5.1 ECSP management system executes the following actions to connect EAS / EES to PCF and ECS to NEF:

– create EP_N5 MOI with EAS IP address in localAddress, and PCF IP address in remoteAddress to connect EAS to PCF.

– create EP_N5 MOI with EES IP address in localAddress, and PCF IP address in remoteAddress to connect EES to PCF.

– create EP_N33 MOI with ECS IP address in localAddress, and NEF IP address in remoteAddress to connect ECS to NEF.

5.2 PLMN management system executes the following actions to add the EAS and EES connections to PCF and the ECS connection to NEF:

– create EP_N5 MOI with PCF IP address in localAddress, and EAS IP address easAddress in remoteAddress.

– create EP_N5 MOI with PCF IP address in localAddress, and EES IP address eecsAddress in remoteAddress.

– create EP_N33 MOI with NEF IP address in localAddress, and ECS IP address ecsAddress in remoteAddress.

Note: There is no sequence dependency between steps 5.1 and 5.2.

5.3 ECSP management system performs the following configuration operations:

– configure the farEndEntity in EP_N5 MOI with the PCF DN.

– configure the farEndEntity in EP_N33 MOI with the NEF DN.

If the EDN NFs are untrusted by PLMN operators, then performs the following steps:

6. PLMN management system found the NEF(s) based on EES service area, EAS service area, EDN service area, and then creates the EcmConnectionInfo MOI with connection information for NEF, including the IP address and DN.

7. PLMN management system returns the connection information in the attributeListOut of the output parameter in createMOI operation to ECSP management system.

8. Connects EDN NFs to 5GC NFs via NEF.

8.1 ECSP management system executes the following actions to connect EAS, EES, and ECS to NEF:

– create EP_N33 MOI with EAS IP address in localAddress, and NEF IP address in remoteAddress to connect EAS to PCF.

– create EP_N33 MOI with EES IP address in localAddress, and NEF IP address in remoteAddress to connect EES to PCF.

– create EP_N33 MOI with ECS IP address in localAddress, and NEF IP address in remoteAddress to connect ECS to NEF.

8.2 PLMN management system executes the following actions to add the EAS, EES, and ECS connections to NEF:

– create EP_N33 MOI with NEF IP address in localAddress, and EAS IP address easAddress in remoteAddress.

– create EP_N33 MOI with NEF IP address in localAddress, and EES IP address eesAddress in remoteAddress.

– create EP_N33 MOI with NEF IP address in localAddress, and ECS IP address ecsAddress in remoteAddress.

8.3 ECSP management system performs the following configuration operations:

– configure the farEndEntity in EP_N33 MOI with the NEF DN.

– configure the farEndEntity in EP_N33 with the NEF DN.

7.4.4 EAS to connect to UPF

Figure 7.4.4-1 depicts a procedure to describe how ECSP management system can consume provisioning MnS to request PLMN management system to connect EAS to UPF for transporting the user traffic via the N6 interface (see clause (see clause 4.2.3 in TS 23.501 [11]). To support the connection of EAS NF to UPF NF, EcmConnectionInfo IOC should include the following attributes:

– EAS IP address: indicate the UPF IP address.

– EAS and EDN service area requirements: EAS service area (see clause 7.3.3 in TS 23.558 [2]).

– ECM connection type: indicate the user plane connection

– N6 traffic routing list: each entry in the list should contain the following attributes (see clause 8.2.4 in TS 23.558 [2]):

– DNAI: DNAI(s) associated with the EAS.

– N6 traffic routing requirements: N6 traffic routing information corresponding to each EAS DNAI.

– UPF Connection information: contains the following attributes:

– UPF IP address: the IP address of the accessing NF.

– UPF DN: the UPF DN to be configured in EASFunction IOC to indicate where the UPF is connected.

Figure 7.4.4-1: EAS to connect to UPF

1. ECSP management system consumes the provisioning MnS with createMOI operation (see clause 11.1.1.1. in TS 28.532 [5]) for UPFConnection IOC to to request PLMN management system to connect the EAS to an UPF. UPFConnection IOC includes EAS DN, EAS IP address, EAS service area requirements, and N6 traffic routing requiremments.

2. PLMN management system finds a UPF based on the EAS and EDN service areas.and N6 traffic routing requirements.

If an UPF can be found, then performs the following steps:

3. PLMN management system creates the UPFConnection MOI with UPF connection information, including UPF IP address and UPF DN.

4. PLMN management system create EP_N6 MOI with UPF IP address in localAddress, and EAS IP address in remoteAddress to connect UPF to EAS.

5. PLMN management system returns the UPF connection information in the attributeListOut of the output parameter in createMOI operation to ECSP management system.

6. ECSP management system create EP_N6 MOI with EAS IP address in localAddress, and UPF IP address in remoteAddress.

7. ECSP management system configures the upfRef in EP_N6 MOI with the UPF DN.

If an UPF cannot be found, then performs the following steps:

8. PLMN management system returns the output parameters for createMOI operation to indicate the UPF instantiation is in progress.

9. PLMN management system invokes the InstantiateNsRequest operation (see clause 7.3.3 in ETSI GS NFV-IFA 013 [6]) to request NFVO via the Os-Ma-nfvo interface to instantiate a NS instance including the UPF VNF instance.

10. NFVO sends a notification to PLMN management system indicating the result of instantiation procedure (see clause 7.3.3.4 of ETSI GS NFV-IFA 013 [6]).

11. If the UPF has been instantiated, then performs the following steps:

11.1. PLMN management system creates the UPFConnection MOI with UPF connection information, including UPF IP address and UPF DN.

11.2. PLMN management system create EP_N6 MOI with UPF IP address in localAddress, and EAS IP address in remoteAddress to connect UPF to EAS.

11.3 PLMN management system sends notifyMOICreation with UPF connection information in attributeList.

11.4. ECSP management system create EP_N6 MOI with EAS IP address in localAddress, and UPF IP address in remoteAddress.

11.5 ECSP management system configures the upfRef in EP_N6 MOI with the UPF DN.

12. If the UPF has not been instantiated, then performs the following step:

12.1 PLMN management system sends notifyMOICreation to ECSP management system to indicate no UPF can be found.