Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.682  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4.2   4.3…   4.4…   4.5…   4.5.7…   4.5.14…   4.6…   5…   5.3…   5.5…   5.6…   5.6.2…   5.6.6…   5.7…   5.8…   5.9…   5.13…   5.14…   5.15   5.16   5.17…   5.18   5.19…   A…   C… 
5.19 RACS information provisioning procedures  5.19.1 General  5.19.2 RACS information provisioning procedures via SCEF  5.19.3 RACS information provisioning procedures via T9a 
...

 

5.19  RACS information provisioning procedures |R16|  p. 125

5.19.1  General  p. 125

This clause specifies procedures for provisioning of UCMF with RACS related information from SCS/AS, either via SCEF or directly. Specification of these procedures does not preclude other methods of UCMF provisioning being used, e.g. O&M.

5.19.2  RACS information provisioning procedures via SCEF  p. 125

This procedure is used by SCS/AS to add, update or delete UE radio access capability entries in the UCMF using the protocol specified in TS 29.122 for the SCEF northbound API and the protocol defined in TS 29.675 for the UCMF northbound API. Figure 5.19.2-1 illustrates the procedure.
Copy of original 3GPP image for 3GPP TS 23.682, Fig. 5.19.2-1: RACS information provisioning procedure via SCEF
Figure 5.19.2-1: RACS information provisioning procedure via SCEF
(⇒ copy of original 3GPP image)
Up
Step 1.
The SCS/AS sends a Radio Capability Entry Request ((list of) UE Radio Capability ID(s), UE radio access capability(s) set with its coding format(s) for each UE radio Capability ID, one (list of) IMEI/TAC values(s) for each UE Radio Capability ID, action) message to the SCEF. The action indicates add/modify/delete operation for the UE Radio Capability ID and UE radio access capability.
Step 2.
The SCEF may check whether the UE Radio Capability ID is within the allowed list of manufacturers according to local policy. If the checking fails, step 6 is executed with error response.
Step 3.
The SCEF sends a Radio Capability Entry Request ((list of) UE Radio Capability ID(s), UE radio access capability(s) set with its coding format(s) for each UE radio Capability ID, one (list of) IMEI/TAC values(s) for each UE Radio Capability ID, action) message to the UCMF.
Step 4.
The UCMF creates, updates or deletes the UE radio access capability entry (or entries) for the indicated UE Radio Capability ID(s). The UCMF shall ensure that for the same UE Radio Capability ID, only one UE radio access capability entry in one or both the coding formats exists.
Step 5.
The UCMF sends a Radio Capability Entry Response (Cause) message to the SCEF.
Step 6.
The SCEF sends a Radio Capability Entry Response (Cause) message to the SCS/AS.
Up

5.19.3  RACS information provisioning procedures via T9a  p. 126

This procedure is used by SCS/AS to add, update or delete UE radio access capability entries in the UCMF using the protocol defined in TS 29.675. Figure 5.19.3-1 illustrates the procedure.
Copy of original 3GPP image for 3GPP TS 23.682, Fig. 5.19.3-1: RACS information provisioning procedure via T9a
Figure 5.19.3-1: RACS information provisioning procedure via T9a
(⇒ copy of original 3GPP image)
Up
Step 1.
The SCS/AS sends a Radio Capability Entry Request ((list of) UE Radio Capability ID(s), UE radio access capability(s) set with its coding format(s) for each UE radio Capability ID, one (list of) IMEI/TAC values(s) for each UE Radio Capability ID, action) message to the UCMF. The action indicates add/modify/delete operation for the UE Radio Capability ID and UE radio access capability.
Step 2.
The UCMF creates, updates or deletes the UE radio access capability entry (or entries) for the indicated UE Radio Capability ID(s). The UCMF shall ensure that for the same UE Radio Capability ID, only one UE radio access capability entry in one or both the coding formats exists.
Step 3.
The UCMF sends a Radio Capability Entry Response (Cause) message to the SCS/AS.
Up

Up   Top   ToC