4 UE Radio Capability Provisioning Service
29.6753GPPRelease 18Stage 3TSUser Equipment (UE) radio capability provisioning service
4.1 Service Description
4.1.1 Overview
The UE radio capability provisioning service, as defined in 3GPP TS 23.502 [3], is provided by the UE radio Capability Management Function (UCMF).
This service:
– allows NF service consumers to create, update and delete UCMF dictionary entries for Manufacturer-assigned UE Radio Capability IDs.
4.1.2 Service Architecture
The Service Architecture is defined in 3GPP TS 23.501 [2].
The UE radio capability provisioning service (Nucmf_Provisioning) is part of the Nucmf service-based interface exhibited by the UCMF.
The known NF service consumers of the Nucmf_Provisioning service are:
– Network Exposure Function (NEF); and
– Application Function (AF).
The Nucmf_Provisioning service is provided by the UCMF and consumed by the NEF and the AF, as shown in figure 4.1.2-1 for the SBI representation model and in figure 4.1.2-2 for reference point representation model.
Figure 4.1.2-1: Nucmf_Provisioning service Architecture, SBI representation
Figure 4.1.2-2: Nucmf_Provisioning service Architecture, reference point representation
4.1.3 Network Functions
4.1.3.1 UCMF
The UCMF is a functional element that provides service to the NF service consumer.
It allows NF consumers to provision (create, update and delete) UCMF dictionary entries for Manufacturer-assigned UE Radio Capability IDs.
4.1.3.2 NF Service Consumers
The Network Exposure Function (NEF):
– Provision (create, update and delete) UCMF dictionary entries for Manufacturer-assigned UE Radio Capability IDs to the UCMF, if it receives the UE Radio Capability information from the untrusted AF.
The Application Function (AF):
– As the trusted AF, provision (create, update and delete) UCMF dictionary entries for Manufacturer-assigned UE Radio Capability IDs to the UCMF.
4.2 Service Operations
4.2.1 Introduction
Service operations defined for the Nucmf_Provisioning Service are shown in table 4.2.1-1.
Table 4.2.1-1: Nucmf_Provisioning Service Operations
|
Service Operation Name |
Description |
Initiated by |
|
Nucmf_Provisioning_Create |
This service operation is used by an NF service consumer to create UE radio capability provisioning resource for Manufacturer-assigned UE Radio Capability IDs. |
NF service consumer (e.g. AF, NEF) |
|
Nucmf_Provisioning_Update |
This service operation is used by an NF service consumer to modify UE radio capability provisioning resource for Manufacturer-assigned UE Radio Capability IDs. |
NF service consumer (e.g. AF, NEF) |
|
Nucmf_Provisioning_Delete |
This service operation is used by an NF service consumer to remove a UE radio capability provisioning resource. |
NF service consumer (e.g. AF, NEF) |
4.2.2 Nucmf_Provisioning_Create service operation
4.2.2.1 General
This service operation is used by an NF service consumer to create UE radio capability provisioning resource for Manufacturer-assigned UE Radio Capability IDs.
The following procedure using the Nucmf_Provisioning_Create service operation is supported:
– creating a UE radio capability provisioning resource.
4.2.2.2 Creating UE radio capability provisioning resource
This procedure is used by the NF service consumer (e.g. NEF) to create a UE radio capability provisioning resource containing UCMF dictionary entries for Manufacturer-assigned UE Radio Capability IDs, as defined in 3GPP TS 23.501 [2] and 3GPP TS 23.502 [3].
Figure 4.2.2.2-1: Creating new UE radio capability provisioning resource
To create a UE radio capability provisioning resource, the NF service consumer shall send an HTTP POST request to the UCMF with: "{apiRoot}/nucmf-provisioning/<apiVersion>/provisionings" as request URI as shown in step 1 of figure 4.2.2.2-1, and the "RacsData" data structure as request body. The "RacsData" data type shall contain one or more RACS configurations in the "racsConfigs" attribute which include:
– a RACS ID in the "racsId" attribute;
– UE radio capability information in the "racsParamEps" and/or "racsParam5Gs" attributes; and
– the related UE model(s) IMEI-TAC value(s) in the "imeiTacs" attribute.
Upon reception of the HTTP POST message from the NF service consumer requesting to create UCMF dictionary entries, the UCMF shall, for each requested RACS ID, check if there is any existing dictionary entry having the same RACS ID. If yes, the UCMF shall indicate "RACS_ID_DUPLICATED" in the "result" attribute for the requested RACS ID; otherwise if there is no other error the UCMF shall create a UCMF dictionary entry.
After processing all requested RACS IDs, if at least one UCMF dictionary entry is successfully provisioned, the UCMF shall create the resource "Individual UE radio capability provisioning" and respond "201 Created" as shown in step 2 of figure 4.2.2.2-1 with the successfully provisioned RACS information, the UCMF may include RACS report(s) within attribute "racsReports" with a list of RACS ID(s) and the corresponding failure code for which the provisioning has failed as specified in table 5.16.2.2.3-1 of 3GPP TS 29.122 [15] in the body of the HTTP response; otherwise the UCMF shall respond "500 Internal Server Error" and may include the RACS report(s) to indicate failure details.
4.2.3 Nucmf_Provisioning_Update service operation
4.2.3.1 General
This service operation is used by an NF service consumer to modify UE radio capability provisioning resource for Manufacturer-assigned UE Radio Capability IDs.
The following procedure using the Nucmf_Provisioning_Update service operation is supported:
– modifying an existing UE radio capability provisioning resource.
4.2.3.2 Modifying a UE radio capability provisioning resource
Figure 4.2.3.2-1: Modifying a UE radio capability provisioning resource
In order to modify a UE radio capability provisioning resource, i.e. add new UCMF dictionary entries, update and/or remove the existing UCMF dictionary entries for one or more RACS ID(s), the NF service consumer shall send an HTTP PUT or PATCH request to the UCMF with: "{apiRoot}/nucmf-provisioning/<apiVersion>/provisionings/{provisioningId}" as request URI as shown in step 1 of figure 4.2.3.2-1, and the "RacsData" or "RacsDataPatch" data structure as request body, correspondingly. The "RacsData" or "RacsDataPatch" data type shall contain one or more RACS configurations in the "racsConfigs" attribute which include:
– a RACS ID in the "racsId" attribute;
– UE radio capability information in the "racsParamEps" and/or "racsParam5Gs" attributes; and
– the related UE model(s) IMEI-TAC value(s) in the "imeiTacs" attribute.
Upon reception of the HTTP PUT message from the NF service consumer, the UCMF shall start replacing the existing UE radio capability provisioning resource and update the corresponding UCMF dictionary entr(ies).
Upon reception of the HTTP PATCH message from the NF service consumer, the UCMF shall start modifying the existing UE radio capability provisioning resource:
– remove RACS ID and its UE radio capability information with a NULL map key value, and the corresponding UCMF dictionary entry;
– replace the UE radio capability information for any existing RACS ID in the resource, and the corresponding UCMF dictionary entry; and/or
– create a UCMF dictionary entry for any new RACS ID if there is no ID conflict with other existing resources.
After processing all requested RACS IDs, if at least one UCMF dictionary entry is successfully provisioned, the UCMF shall respond "200 OK" as shown in step 2 of figure 4.2.3.2-1 with the successfully provisioned RACS information, the UCMF may include RACS report(s) within attribute "racsReports" with a list of RACS ID(s) and the corresponding failure code for which the provisioning has failed as specified in table 5.16.2.2.3-1 of 3GPP TS 29.122 [15] in the body of the HTTP response; otherwise the UCMF shall respond "500 Internal Server Error" and may include the RACS report(s) to indicate failure details.
4.2.4 Nucmf_Provisioning_Delete service operation
4.2.4.1 General
This service operation is used by an NF service consumer to remove UE radio capability provisioning resource for Manufacturer-assigned UE Radio Capability IDs.
The following procedure using the Nucmf_Provisioning_Delete service operation is supported:
– removing an existing UE radio capability provisioning resource.
4.2.4.2 Removing a UE radio capability provisioning resource
Figure 4.2.4.2-1: Removing a UE radio capability provisioning resource
In order to remove a UE radio capability provisioning resource, the NF service consumer shall send an HTTP DELETE request to the UCMF with: "{apiRoot}/nucmf-provisioning/<apiVersion>/provisionings/{provisioningId}" as request URI as shown in step 1 of figure 4.2.4.2-1.
Upon successful reception of the HTTP DELETE, the UCMF shall remove the corresponding resource and the corresponding UCMF dictionary entries, and send an HTTP "204 No Content" response as shown in step 2 of figure 4.2.4.2-1.
If the UCMF cannot successfully fulfil the received HTTP DELETE request due to the internal error or the error in the HTTP DELETE request, the UCMF shall send the HTTP error response as specified in clause 5.7.