Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 38.300  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.2…   16.3…   16.4…   16.9…   16.10…   16.12…   16.13…   16.14…   17…   18…   19…   A…   B…   C…

 

18  Small Data Transmission |R17|Word‑p. 179

18.0  GeneralWord‑p. 179

Small Data Transmission (SDT) is a procedure allowing data and/or signalling transmission while remaining in RRC_INACTIVE state (i.e. without transitioning to RRC_CONNECTED state). SDT is enabled on a radio bearer basis and is initiated by the UE only if less than a configured amount of UL data awaits transmission across all radio bearers for which SDT is enabled, the DL RSRP is above a configured threshold, and a valid SDT resource is available as specified in clause 5.27 of TS 38.321.
SDT procedure is initiated with either a transmission over RACH (configured via system information) or over Type 1 CG resources (configured via dedicated signalling in RRCRelease). The SDT resources can be configured on initial BWP for both RACH and CG. RACH and CG resources for SDT can be configured on either or both of NUL and SUL carriers. The CG resources for SDT are valid only within the cell the UE received RRCRelease and transitioned to RRC_INACTIVE state. For RACH, the network can configure 2-step and/or 4-step RA resources for SDT. When both 2-step and 4-step RA resources for SDT are configured, the UE selects the RA type according to clause 9.2.6. CFRA is not supported for SDT over RACH.
Once initiated, the SDT procedure is either:
  • successfully completed after the UE is directed to RRC_IDLE (via RRCRelease) or RRC_INACTIVE (via RRCRelease or RRCReject) or to RRC_CONNECTED (via RRCResume or RRCSetup); or
  • unsuccessfully completed upon cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble transmission threshold, an RLC entity reaching a configured maximum retransmission threshold, or expiry of SDT-specific timing alignment timer while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission.
Upon unsuccessful completion of the SDT procedure, the UE transitions to RRC_IDLE.
The initial PUSCH transmission during the SDT procedure includes at least the CCCH message. When using CG resources for initial SDT transmission, the UE can perform autonomous retransmission of the initial transmission if the UE does not receive confirmation from the network (dynamic UL grant or DL assignment) before a configured timer expires as specified in clause 5.27.1 of TS 38.321. After the initial PUSCH transmission, subsequent transmissions are handled differently depending on the type of resource used to initiate the SDT procedure:
  • When using CG resources, the network can schedule subsequent UL transmissions using dynamic grants or they can take place on the following CG resource occasions. The DL transmissions are scheduled using dynamic assignments. The UE can initiate subsequent UL transmission only after reception of confirmation (dynamic UL grant or DL assignment) for the initial PUSCH transmission from the network. For subsequent UL transmission, the UE cannot initiate re-transmission over a CG resource.
  • When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic UL grants and DL assignments, respectively, after the completion of the RA procedure.
While the SDT procedure is ongoing, if data appears in a buffer of any radio bearer not enabled for SDT, the UE initiates a transmission of a non-SDT data arrival indication using UEAssistanceInformation message to the network and, if available, includes the resume cause.
SDT procedure over CG resources can only be initiated with valid UL timing alignment. The UL timing alignment is maintained by the UE based on a SDT-specific timing alignment timer configured by the network via dedicated signalling and, for initial CG-SDT transmission, also by DL RSRP of configured number of highest ranked SSBs which are above a configured RSRP threshold. Upon expiry of the SDT-specific timing alignment timer, the CG resources are released while maintaining the CG resource configuration.
Logical channel restrictions configured by the network while in RRC_CONNECTED state and/or in RRCRelease message for radio bearers enabled for SDT, if any, are applied by the UE during SDT procedure.
The network may configure UE to apply ROHC continuity for SDT either when the UE initiates SDT in the cell where the UE received RRCRelease and transitioned to RRC_INACTIVE state or when the UE initiates SDT in a cell of its RNA.
Up

18.1  Support of SDT procedure over RACHWord‑p. 180

For SDT procedure over RACH, if the UE accesses a gNB other than the last serving gNB, the UL SDT data/signalling is buffered at the receiving gNB, and then the receiving gNB triggers the XnAP Retrieve UE Context procedure. The receiving gNB indicates SDT to the last serving gNB and the last serving gNB decides whether to relocate the UE context or not. Other SDT assistance information (i.e., single packet, multiple packets) may also be provided by the receiving gNB to help the decision.
If the last serving gNB decides not to relocate the UE context, it transfers at least a partial UE context containing SDT RLC context information necessary for the receiving gNB to handle SDT. Then, UL/DL tunnels are established for DRBs configured for SDT between the receiving gNB and the last serving gNB and PDCP PDU of UL/DL data are transferred over the tunnels, until the last serving gNB decides to terminate the SDT session and move the UE back to RRC_INACTIVE by sending RRCRelease message. During the SDT session, the receiving gNB may also request to terminate the SDT session to the last serving gNB.
If the last serving gNB decides not to relocate the UE context, in case SDT is used for signalling, SRB PDCP PDUs is transferred between the receiving gNB and the last serving gNB via the XnAP RRC Transfer procedure.
When the receiving gNB receives DL data or DL signalling over radio bearer(s) not enabled for SDT from the core network and the UE context has been relocated to the receiving gNB, the receiving gNB may send the UE to RRC_CONNECTED state by directly sending the RRC Resume message.
When the last serving gNB receives DL data or DL signalling over radio bearer(s) not enabled for SDT from the core network and it has decided to not relocate the UE context, it may send the UE back to RRC_INACTIVE by sending the RRCRelease message.
Up

18.2  SDT with UE context relocationWord‑p. 180

The overall procedure for SDT procedure over RACH with UE context relocation is illustrated in the Figure 18.2-1.
Reproduction of 3GPP TS 38.300, Fig. 18.2-1: RA-based SDT with UE context relocation
Up
Step 1.
The UE sends an RRCResumeRequest as well as UL SDT data and/or UL SDT signalling to the receiving gNB.
Step 2.
The receiving gNB identifies the last serving gNB using the I-RNTI and retrieves the UE context by means of Xn-AP Retrieve UE Context procedure. The receiving gNB indicates that the UE request is for an SDT transaction and may also provide SDT assistance information (i.e., single packet, multiple packets).
Step 3.
The last serving gNB decides to relocate UE context for SDT and responds with the RETRIEVE UE CONTEXT RESPONSE message. The UL SDT data, if any, is delivered to the UPF.
Step 4-6.
The receiving gNB decides to keep UE in RRC Inactive state for SDT. If loss of DL user data buffered in the last serving gNB shall be prevented, the receiving gNB provides forwarding addresses. The receiving gNB alsoinitiates NG-AP Path Switch procedure to establish a NG UE associated signalling connection to the serving AMF. After path switch, the UL NAS PDU is delivered to AMF.
Step 7.
After the SDT transmission is completed, the receiving gNB generates and sends RRCRelease message including the Suspend indication to the UE to send the UE back to RRC_INACTIVE.
Step 8.
The receiving gNB indicates the last serving gNB to remove the UE context by sending the XnAP UE CONTEXT RELEASE message. The XnAP UE CONTEXT RELEASE message can be sent after step 6.
Up

18.3  SDT without UE context relocationWord‑p. 181

The overall procedure for SDT procedure over RACH without UE context relocation is illustrated in the Figure 18.3-1.
Reproduction of 3GPP TS 38.300, Fig. 18.3-1: RA-based SDT without UE context relocation
Up
Step 1/2.
The steps 1/2 are as defined in steps 1/2 in Figure 18.2-1.
Step 3.
The last serving gNB decides not to relocate the UE context for SDT.
Step 4.
The last serving gNB transfers a partial UE context including the SDT related RLC context.
Step 5.
The receiving gNB acknowledges receiving the partial UE context and provides associated DL TNL address, if needed. After the Partial UE Context Retrieval procedure, the UE context is kept at the last serving gNB and the SDT related RLC context is established at the receiving gNB, then the UL SDT data is delivered to the UPF, the UL NAS PDU is delivered to AMF, if any.
Step 6.
After SDT transmission is completed, the last serving gNB responds to the receiving gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated RRCRelease message. The RRCRelease message includes suspend configuration.
Step 7.
The receiving gNB sends the RRCRelease message to the UE.
Step 8.
The UE moves to RRC_INACTIVE mode.
Up

Up   Top   ToC