Managing small data transmissions with user equipment

By determining the status and capabilities of the user equipment in the network node and generating and sending appropriate radio resource messages, the problem of low data transmission efficiency of UE in the inactive state is solved, and efficient data transmission and resource management are achieved.

CN118901268APending Publication Date: 2024-11-05GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380032518.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-08
Filing Date
2023-04-06
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

In the prior art, when a user equipment (UE) configures a random access network (RA-SDT) or configures authorized small data transmission (CG-SDT) in a radio access network (RAN) node, a clear configuration mechanism is lacking, resulting in The UE has low data transmission efficiency in the inactive state.

Method used

The network nodes generate appropriate radio resource messages, including RA-SDT or CG-SDT configurations, by determining the status and capabilities of the UE, and send them to the UE, so that they can efficiently transmit small data in an inactive state. This method is managed jointly by a central unit (CU) and a distributed unit (DU) in a base station in a distributed architecture, and the SDT configuration is determined based on the UE's support capabilities and resource availability.

Benefits of technology

It realizes efficient small data transmission of UE in inactive state, improves data transmission efficiency and flexibility, reduces the waste of radio resources, and enhances network management capabilities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure FT_1
    Figure FT_1
  • Figure FT_2
    Figure FT_2
  • Figure FT_3
    Figure FT_3
Patent Text Reader

Abstract

A radio access network (RAN) and a user equipment (UE) may implement a method for managing small data transmissions (SDT). The method comprises: (i) determining that the UE should operate in a state of a protocol for controlling radio resources, wherein the UE is not connected to the RAN (704); (ii) generating a message (706, 708 and 710) for the UE to transmit small data according to the capability of the UE based on at least whether the UE supports a first type of SDT dependent on a random access procedure and / or a second type of SDT dependent on resources previously allocated to the UE; and (iii) sending the message to the UE (712).
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of the filing date of Provisional U.S. Patent Application No. 63 / 329,292, entitled “MANAGING SMALL DATA TRANSMISSION WITH A USER EQUIPMENT,” filed on April 8, 2022. The entire contents of the provisional application are hereby expressly incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to uplink and / or downlink data communications at a user equipment (UE) and a radio access network (RAN) when the UE is operating in an inactive or idle state associated with a protocol for controlling radio resources. Background Art

[0004] This background description is provided to generally present the context of the present disclosure. The work of the presently named inventors is neither explicitly nor implicitly admitted to be prior art to the present disclosure to the extent that it is described in this background section and in all aspects that may not have otherwise qualified as prior art at the time of filing.

[0005] Typically, a base station operating a cellular radio access network (RAN) uses a certain radio access technology (RAT) and multiple layers of a protocol stack to communicate with a user equipment (UE). For example, the physical layer (PHY) of the RAT provides a transport channel to the media access control (MAC) sublayer, which provides a logical channel to the radio link control (RLC) sublayer. The RLC sublayer similarly provides data transfer services to the packet data convergence protocol (PDCP) sublayer. The radio resource control (RRC) sublayer is arranged above the PDCP sublayer.

[0006] The RRC sublayer specifies: an RRC_IDLE state, in which the UE does not have an active radio connection with a base station; an RRC_CONNECTED state, in which the UE has an active radio connection with a base station; and an RRC_INACTIVE state, which allows the UE to transition back to the RRC_CONNECTED state more quickly due to radio access network (RAN) level base station coordination and RAN paging procedures. In some cases, a UE in the RRC_INACTIVE state has only a relatively small packet to send. A small data transfer (SDT) procedure can support data transmission for a UE operating in the RRC_INACTIVE state without transitioning to the RRC_CONNECTED state.

[0007] The device enables SDT for a specific radio bearer. The UE may initiate SDT only when less than the configured amount of uplink data is waiting to be transmitted on all radio bearers for which SDT is enabled, the downlink reference signal received power (RSRP) is above the configured threshold, and valid SDT resources are available. In addition, the UE may initiate the SDT process by transmission on the random access channel (RACH) as part of a random access SDT (RA-SDT) session, or by transmission on type 1 configured grant (CG) resources as part of a CG-SDT session. For RA-SDT, the network configures 2-step and / or 4-step random access resources for SDT transmission. In a RA-SDT session, the UE may perform an initial transmission of data in message 3 (MSG3) of a 4-step random access procedure or in message A (MSGA) of a 2-step random access procedure. Then, after the random access procedure is completed, the network may schedule subsequent uplink and / or downlink transmissions using uplink grants and downlink assignments, respectively.

[0008] The UE can initiate a CG-SDT session with only valid uplink (UL) timing alignment. The UE uses the network-configured SDT-specific timing alignment timer and the downlink (DL) RSRP of the configured number of highest-ranked synchronization signal blocks (SSBs) to maintain UL timing alignment. After the SDT-specific timing alignment timer expires, the UE releases the CG resources. After initiating CG-SDT, the UE uses the CG to perform an initial transmission including data during the CG opportunity, and the network can use dynamic grants to schedule subsequent uplink transmissions. Alternatively, uplink transmissions can be performed during subsequent CG resource opportunities. During the CG-SDT, the base station uses dynamic assignments to schedule downlink transmissions. The UE can initiate subsequent uplink transmissions only after receiving confirmation of the initial transmission from the network.

[0009] However, in some scenarios and implementations, the UE may be connected to a Radio Access Network (RAN) node. It is not clear how the RAN node configures RA-SDT or CG-SDT for the UE. Summary of the invention

[0010] The network node manages small data transmission with the UE. The network node (such as a base station of the RAN) determines that the UE should operate in an inactive state before generating a radio resource message for the UE. The radio resource message includes an indication of RA-SDT communication, CG-SDT communication, or non-SDT communication for the UE, depending on whether the UE and / or the network node supports RA-SDT communication or CG-SDT communication. The network node then sends a radio resource message including appropriate indications to the UE. Depending on the implementation, the network node can have a standard or distributed architecture.

[0011] For network nodes with a distributed architecture (sometimes referred to as a split base station), the CU of the network node manages small data transfers with the UE. The DU of the network node may regulate and / or manage specific aspects, such as generating a specific SDT configuration. The DU may determine whether to generate an SDT configuration, such as a CG-SDT configuration, based on metrics such as whether resources are available for the UE and / or whether the UE and DU support the type of SDT being used.

[0012] An example embodiment of these techniques is a method for managing small data transmission (SDT) with a user equipment (UE) implemented in a network node of a random access network (RAN). The method includes: determining that the UE should operate in a state of a protocol for controlling radio resources, wherein the UE is not connected to the RAN; generating a message that enables the UE to transmit small data according to the capabilities of the UE based on at least whether the UE supports a first type of SDT that depends on a random access procedure and / or a second type of SDT that depends on resources previously allocated to the UE; and sending the message to the UE.

[0013] Another example embodiment of the techniques is a method for managing a small data transfer (SDT) with a user equipment (UE), the method being implemented in a distributed unit (DU) of a distributed base station, the distributed base station also including a central unit (CU). The method includes receiving a message from the CU requesting SDT resources for the UE for an SDT type that is dependent on resources previously allocated to the UE; determining whether to include a configuration for the SDT type in a response message to the CU; and sending the response message to the CU. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1A is a block diagram of an example wireless communication system in which user devices and base stations of the present disclosure may implement the disclosed techniques for managing small data transmissions;

[0015] Figure 1B The centralized unit (CU) and the distributed unit (DU) can be Figure 1A A block diagram of an example base station operating in a system of FIG.

[0016] Figure 2A yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a base station;

[0017] Figure 2B yes Figure 1A A block diagram of an example protocol stack according to which a UE communicates with a CU and a DU;

[0018] Figure 3An example scenario is shown in which the UE communicates with the DU of the RAN using a non-SDT configuration before the UE receives an SDT configuration from the DU and transitions to an inactive state;

[0019] Figure 4 An example scenario is shown in which the UE communicates with the DU of the RAN in an inactive state before the UE receives an SDT configuration from the DU and remains in an inactive state;

[0020] Figure 5A An example scenario is shown in which the UE transitions from an inactive state to a connected state before the UE receives an SDT configuration from a DU and transitions back to an inactive state;

[0021] Figure 5B Shown with Figure 5A A similar scenario, but where the UE does not initially communicate small data with the DU when in the initial inactive state;

[0022] Figure 6 An example scenario is shown in which the UE communicates with the DU of the RAN while in an inactive state, but as part of the SDT communication, the base station retrieves the context of the UE from another base station;

[0023] Figure 7 is a flow chart of an example method implemented in a base station of a RAN for determining whether to generate an RRC release message including or excluding an SDT configuration based on whether a UE and a RAN node support RA-SDT;

[0024] Figure 8 is a flow chart of an example method implemented in a base station of a RAN for generating and sending an RRC release message including an SDT configuration and a RA-SDT configuration;

[0025] Fig.9A is a flow chart of an example method implemented in a base station of a RAN for determining whether to generate an RRC release message including or excluding an SDT configuration based on whether a UE and a RAN node support CG-SDT;

[0026] Fig. 9B is similar to Fig.9A A flow chart of an example method implemented in a base station of a RAN, but wherein the determination is based on whether the UE supports CG-SDT for the UL carrier frequency;

[0027] Fig. 10A is a flow chart of an example method implemented in a base station of a RAN for determining whether to generate an RRC release message including or excluding SDT configuration based on whether a UE and a RAN node support RA-SDT and CG-SDT;

[0028] Fig. 10B is similar to Fig. 10A a flowchart of an example method implemented in a base station of a RAN, but wherein the determination is based on whether the UE and the RAN node support RA-SDT and whether the UE supports CG-SDT for the UL carrier frequency;

[0029] Fig.11 is a flow chart of an example method implemented in a CU of a RAN for determining whether to generate an RRC release message including or excluding an SDT configuration based on whether a UE and a DU support RA-SDT;

[0030] Fig. 12A is a flow chart of an example method implemented in a CU of a RAN for determining whether to generate an RRC release message including or excluding an SDT configuration based on whether a UE and a DU support CG-SDT;

[0031] Fig. 12B is similar to Fig. 12A A flowchart of an example method implemented in a CU of a RAN, but wherein the determination is based on whether the UE supports CG-SDT for the UL carrier frequency;

[0032] Fig.13A is a flow chart of an example method implemented in a CU of a RAN for determining whether to generate an RRC release message including or excluding SDT configuration based on whether a UE and a DU support RA-SDT and CG-SDT;

[0033] Fig. 13B is similar to Fig.13A A flowchart of an example method implemented in a CU of a RAN, but wherein the determination is based on whether the UE and the DU support RA-SDT and whether the UE supports CG-SDT for the UL carrier frequency;

[0034] Fig.14A is a flow chart of an example method implemented in a DU of a RAN for determining whether to send a message including or excluding a CG-SDT configuration to a CU based on whether CG-SDT resources are available for a UE;

[0035] Fig. 14B is similar to Fig.14A A flowchart of an example method implemented in a DU of a RAN, but wherein the determination is based on whether the UE and the DU support CG-SDT;

[0036] Fig.15 is a flow chart of an example method implemented in a base station of a RAN for managing small data transmissions with a UE;

[0037] Fig.16is a flow chart of an example method implemented in a DU of a RAN for managing small data transfers with a UE;

[0038] Fig.17A is a flow chart of an example method implemented in a base station of a RAN for enabling RA-SDT for a cell and broadcasting an SDT configuration to a UE;

[0039] Fig. 17B is similar to Fig.17A A flowchart of an example method implemented in a base station of a RAN, but wherein the base station determines to enable CG-SDT;

[0040] Fig. 17C is similar to Fig.17A A flowchart of an example method implemented in a base station of a RAN, but wherein the base station determines whether to enable RA-SDT and / or CG-SDT; and

[0041] Fig.18 is a flow chart of an example method implemented in a base station of a RAN for generating data packets for enabling a UE to transmit small data. DETAILED DESCRIPTION

[0042] As discussed in more detail below, a user equipment (UE) and / or a network node of a radio access network (RAN) may use the techniques of the present disclosure for managing early data communications and transitioning the UE between states of a protocol for controlling radio resources between the UE and the RAN. As used in the present disclosure, early data communications may refer to early data transfer (EDT) from a network perspective (i.e., EDT in a downlink direction), or EDT from a UE perspective (i.e., EDT in an uplink direction).

[0043] First reference Figure 1A , the example wireless communication system 100 includes a UE 102, a base station 104, a base station 106, and a core network (CN) 110. The base stations 104 and 106 may operate in a RAN 105 connected to the core network (CN) 110. For example, the CN 110 may be implemented as an evolved packet core (EPC) 111 or a fifth generation (5G) core (5GC) 160. In another example, the CN 110 may also be implemented as a sixth generation (6G) core.

[0044] Base station 104 covers cell 124, and base station 106 covers cell 126. If base station 104 is a gNB, cell 124 is an NR cell. If base station 104 is an ng-eNB, cell 124 is an Evolved Universal Terrestrial Radio Access (E-UTRA) cell. Similarly, if base station 106 is a gNB, cell 126 is an NR cell, and if base station 106 is an ng-eNB, cell 126 is an E-UTRA cell. Cells 124 and 126 may be located in the same radio access network notification area (RNA) or in different RNAs. In general, RAN 105 may include any number of base stations, and each of the base stations may cover one, two, three, or any other suitable number of cells. UE 102 may support at least 5G NR (or simply "NR") or E-UTRA air interface to communicate with base stations 104 and 106. Each of base stations 104, 106 may be connected to CN 110 via an interface (e.g., S1 or NG interface). The base stations 104 and 106 may also be interconnected via an interface for interconnecting NG RAN nodes (e.g., an X2 or Xn interface).

[0045] Among other components, the EPC 111 may include a serving gateway (SGW) 112, a mobility management entity (MME) 114, and a packet data network gateway (PGW) 116. In general, the SGW 112 is configured to deliver user plane packets associated with audio calls, video calls, Internet traffic, etc., and the MME 114 is configured to manage authentication, registration, paging, and other related functions. The PGW 116 provides connectivity from the UE to one or more external packet data networks (e.g., an Internet network and / or an Internet Protocol (IP) Multimedia Subsystem (IMS) network). The 5GC 160 includes a user plane function (UPF) 162 and an access and mobility management function (AMF) 164 and / or a session management function (SMF) 166. Generally speaking, UPF 162 is configured to pass user plane packets associated with audio calls, video calls, Internet traffic, etc., AMF 164 is configured to manage authentication, registration, paging and other related functions, and SMF 166 is configured to manage PDU sessions.

[0046] like Figure 1A As shown, base station 104 supports cell 124, and base station 106 supports cell 126. Cells 124 and 126 may partially overlap, so that UE 102 may select, reselect, or handover from one of cells 124 and 126 to the other. In order to exchange messages or information directly, base station 104 and base station 106 may support an X2 or Xn interface. In general, CN 110 may be connected to any suitable number of base stations supporting NR cells and / or EUTRA cells.

[0047] As discussed in detail below, the UE 102 and / or RAN 105 utilize techniques of the present disclosure when a radio connection between the UE 102 and the RAN 105 is suspended, e.g., when the UE 102 operates in an inactive or idle state of a protocol for controlling radio resources between the UE 102 and the RAN 105. For clarity, the examples below relate to the RRC_INACTIVE or RRC_IDLE states of the RRC protocol.

[0048] As used in the present disclosure, the term "data" or "data packet" refers to signaling, control plane information at the protocol layer for controlling radio resources (e.g., RRC), controlling mobility management (MM), controlling session management (SM); or non-signaling, non-control plane information at the protocol layer above the layer of the protocol for controlling radio resources (e.g., RRC), above the layer of the protocol for controlling mobility management (MM), above the layer of the protocol for controlling session management (SM), or above the layer of the protocol for controlling quality of service (QoS) flow (e.g., Service Data Adaptation Protocol (SDAP)). Some non-signaling, non-control plane information may be referred to as user plane data. The data to which the UE 102 and / or RAN 105 apply the techniques of the present disclosure may include, for example, Internet of Things (IoT) data, Ethernet traffic data, Internet traffic data, or Short Message Service (SMS) messages. In addition, as discussed below, in some implementations, the UE 102 applies these techniques only if the size of the data is below a certain threshold.

[0049] In the example scenario discussed below, UE 102 transitions to the RRC_INACTIVE or RRC_IDLE state, selects a cell of base station 104, and exchanges data with base station 104 (via base station 106 or directly with base station 104) without transitioning to the RRC_CONNECTED state. As a more specific example, after UE 102 determines that data is available for uplink transmission in the RRC_INACTIVE or RRC_IDLE state, UE 102 may apply one or more security functions to an uplink (UL) data packet, generate a first UL protocol data unit (PDU) including a security-protected packet, include a UL RRC message in a second UL PDU along with the first UL PDU, and send the second UL PDU to RAN 105. UE 102 includes a UE identity / identifier (ID) of UE 102 in the UL RRC message. RAN 105 may identify UE 102 based on the UE ID. In some implementations, the UE ID is an Inactive Radio Network Temporary Identifier (I-RNTI), a Recovery ID, or a Non-Access Stratum (NAS) ID. The NAS ID may be an S-Temporary Mobile Subscriber Identity (S-TMSI) or a Globally Unique Temporary Identifier (GUTI).

[0050] The security functions may include integrity protection and / or encryption functions. When integrity protection is enabled, UE 102 generates a message authentication code (MAC-I) for integrity to protect the integrity of the data. Therefore, in this case, UE 102 generates a security-protected packet including data and MAC-I. When encryption is enabled, UE 102 encrypts the data to obtain an encrypted packet so that the security-protected packet includes the encrypted data. When both integrity protection and encryption are enabled, UE 102 generates a MAC-I for protecting the integrity of the data and encrypts the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. Then, UE 102 sends the security-protected packet to RAN 105 when in RRC_INACTIVE or RRC_IDLE state.

[0051] In some implementations, the data is an uplink (UL) service data unit (SDU) of a packet data convergence protocol (PDCP) or SDAP. The UE 102 applies security functions to the SDU and includes the secure SDU in a first UL PDU (e.g., UL PDCP PDU). The UE 102 then includes the UL PDCP PDU in a second UL PDU (such as a UL MAC PDU), which is associated with a media access control (MAC) layer depending on the implementation. Therefore, in such a case, the UE 102 sends a secure UL PDCP PDU in the UL MAC PDU. In some implementations, the UE 102 includes the UL RRC message in the UL MAC PDU. In further implementations, the UE 102 does not include the UL RRC message in the UL MAC PDU. In some such cases, the UE 102 does not include the UE ID of the UE 102 in the UL MAC PDU that does not include the UL RRC message. In yet further implementations, the UE 102 includes the UL PDCP PDU in a UL radio link control (RLC) PDU, and then includes the UL RLC PDU in a UL MAC PDU. In some implementations where the UE 102 includes the UL RRC message in the UL MAC PDU, the UE 102 generates an RRC MAC-I and includes the RRC MAC-I in the UL RRC message. For example, the RRC MAC-I is a resumeMAC-I field, as specified in 3GPP specification 38.331. In further implementations, the UE generates an RRC MAC-I field using an integrity key (e.g., K RRCint The UE may obtain the RRC MAC-I from the UL RRC message by including the following parameters: a key, an integrity protection algorithm, and / or other parameters: COUNT (e.g., a 32-bit, 64-bit, or 128-bit value), BEARER (e.g., a 5-bit value), and DIRECTION (e.g., a 1-bit value). In some implementations, the UE sets the bits of COUNT, BEARER, and DIRECTION to binary ones to generate the RRC MAC-I.

[0052] In a further implementation, the data is a UL service data unit (SDU) of NAS. The UE 102 applies a security function to the SDU and includes the secure SDU in a first UL PDU (such as a NAS PDU), which may be associated with a NAS layer. For example, depending on the implementation, the NAS layer is an MM sublayer or an SM sublayer of 5G, an evolved packet system (EPS), or 6G. Then, in some implementations, the UE 102 includes the UL NAS PDU in a second UL PDU (such as a UL RRC message). Therefore, in such a case, the UE 102 sends a (first) secure UL NAS PDU in the UL RRC message. In some implementations, the UE 102 includes the UL RRC message in a UL MAC PDU and sends the UL MAC PDU to a base station (e.g., base station 104 or 106) via a cell (e.g., cell 124 or 126). In this case, the UE 102 does not include the RRC MAC-I in the UL RRC message. Alternatively, UE 102 includes RRC MAC-I as described above.

[0053] In some implementations, the UL RRC message described above is a common control channel (CCCH) message, an RRC recovery request message, or an RRC early data request message. In further implementations, the UL RRC message includes the UE ID of the UE 102 as described above.

[0054] More generally, the UE 102 may secure data using at least one of ciphering and integrity protection, include the secured data as a security-protected packet in a first UL PDU, and send the first UL PDU to the RAN 105 in a second UL PDU.

[0055] In some scenarios and implementations, the base station 106 retrieves the UE ID of the UE 102 from the UL RRC message and identifies the base station 104 as the destination of the data in the first UL PDU based on the determined UE ID. In one example implementation, the base station 106 retrieves the first UL PDU from the second UL PDU and sends the first UL PDU to the base station 104. The base station 104 then retrieves the security-protected packet from the first UL PDU, applies multiple security functions to decrypt the data and / or check integrity protection, and sends the data to the CN 110 (e.g., SGW 112, UPF 162, MME 114, or AMF 164) or an edge server. In some implementations, the edge server operates within the RAN 105. More specifically, the base station 104 derives at least one security key from the UE context information of the UE 102. The base station 104 then retrieves the data from the security-protected packet by using the at least one security key and sends the data to the CN 110 or the edge server.

[0056] When the security-protected packet is an encrypted packet, the base station 104 decrypts the encrypted packet by using at least one security key (e.g., an encryption and / or decryption key) to obtain data. In some implementations, if the security-protected packet is an integrity-protected packet, the integrity-protected packet includes data and MAC-I. The base station 104 can verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., an integrity key). When the base station 104 confirms that the MAC-I is valid, the base station 104 sends the data to the CN 110 or the edge server. However, when the base station 104 determines that the MAC-I is invalid, the base station 104 discards the security-protected packet. In a further implementation, if the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet includes an encrypted packet and an encrypted MAC-I. In this case, the base station 104 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. Then, the base station 104 determines whether the MAC-I is valid for the data. If the base station 104 determines that the MAC-I is valid, the base station 104 retrieves the data and forwards the data to the CN 110 or edge server. However, if the base station 104 determines that the MAC-I is invalid, the base station 104 discards the packet.

[0057] In a further implementation, the base station 106 retrieves the security-protected packet from the first UL PDU. The base station 106 performs a retrieve UE context procedure with the base station 104 to obtain UE context information of the UE 102 from the base station 104. The base station 106 derives at least one security key from the UE context information. Then, the base station 106 retrieves data from the security-protected packet by using the at least one security key and sends the data to the CN 110 (e.g., UPF 162) or an edge server. When the security-protected packet is an encrypted packet, the base station 106 obtains the data by decrypting the encrypted packet using at least one security key (e.g., an encryption and / or decryption key).

[0058] In some implementations, if the security-protected packet is an integrity-protected packet, the integrity-protected packet includes data and MAC-I. The base station 106 can verify whether the MAC-I is valid for the security-protected packet by using at least one security key (e.g., an integrity key). When the base station 106 confirms that the MAC-I is valid, the base station 106 sends the data to the CN 110. On the other hand, when the base station 106 determines that the MAC-I is invalid, the base station 106 discards the security-protected packet. In addition, in an implementation in which the security-protected packet is both encrypted and integrity-protected, the encrypted and integrity-protected packet includes an encrypted packet and an encrypted MAC-I. In this case, the base station 106 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. Then, the base station 106 determines whether the MAC-I is valid for the data. If the base station 106 determines that the MAC-I is valid, the base station 106 retrieves the data and forwards the data to the CN 110. However, if the base station 106 determines that the MAC-I is invalid, the base station 106 discards the packet.

[0059] In other scenarios and implementations, the base station 104 retrieves the UE ID of the UE 102 from the UL RRC message and identifies that the base station 104 stores the UE context information of the UE 102. Accordingly, the base station 104 retrieves the security-protected packet from the first UL PDU, retrieves the data from the security-protected packet, and sends the data to the CN 110 or the edge server, as described above.

[0060] Furthermore, in some cases, the RAN 105 sends data in the downlink (DL) direction to the UE 102 operating in the RRC_INACTIVE or RRC_IDLE state.

[0061] For example, when the base station 104 determines that the data is available for downlink transmission to the UE 102 currently operating in the RRC_INACTIVE or RRC_IDLE state, the base station 104 applies at least one security function to the data to generate a security-protected packet, a first DL PDU including the security-protected packet, and includes the first DL PDU in the second DL PDU. Depending on the implementation, in order to make the data secure, the base station 104 applies a security function (e.g., integrity protection and / or encryption) to the data. More specifically, when integrity protection is enabled, the base station 104 generates a MAC-I for protecting the integrity of the data, so that the security-protected packet includes the data and the MAC-I. When encryption is enabled, the base station 104 encrypts the data to generate an encrypted packet, so that the security-protected packet is an encrypted packet. In addition, in an implementation in which both integrity protection and encryption are enabled, the base station 104 generates a MAC-I for protecting the integrity of the data, and encrypts the data together with the MAC-I to generate an encrypted packet and an encrypted MAC-I. In some implementations, the base station 104 generates a first DL PDU (such as a DL PDCP PDU) using the security-protected packet; includes the first DL PDU in a second DL PDU (e.g., a DL MAC PDU) associated with a MAC layer, for example; and sends the second DL PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state. In some implementations, the base station 104 includes the DL PDCP PDU in the DL RLC PDU, includes the DL RLC PDU in the DL MAC PDU, and sends the DL MAC PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state.

[0062] In a further implementation, the base station 104 sends the first DL PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the first DL PDU, and sends the second DL PDU to the UE 102 without first causing the UE 102 to transition from the RRC_INACTIVE or RRC_IDLE state to the RRC_CONNECTED state. In some implementations, the base station 106 generates a DL RLC PDU including the first DL PDU, and includes the DL RLC PDU in the second DL PDU. In a further implementation, the base station 104 includes the first DL PDU in the DL RLC PDU, and sends the DL RLC PDU to the base station 106, which then generates a second DL PDU (e.g., DL MAC PDU) including the DL RLC PDU, and sends the second DL PDU to the UE 102.

[0063] In some implementations, a base station (i.e., base station 104 or 106) generates downlink control information (DCI) and a cyclic redundancy check (CRC) scrambled with an ID of UE 102 to send a second DL PDU generated by the base station. In some implementations, the ID of UE 102 may be a radio network temporary identifier (RNTI). For example, depending on the implementation, the RNTI is a cell RNTI (C-RNTI), a temporary C-RNTI, or an inactive C-RNTI. The base station sends the DCI and the scrambled CRC to UE 102 operating in the RRC_INACTIVE or RRC_IDLE state on a physical downlink control channel (PDCCH). The base station scrambles the CRC with the ID of UE 102. In some implementations, the base station assigns the ID of UE 102 to UE 102 in a random access response or message B (MsgB) sent by the base station in a random access process with UE 102 before sending the DCI and the scrambled CRC. In a further implementation, the base station assigns the ID of UE 102 to UE 102 in an RRC message (e.g., an RRC release message or an RRC reconfiguration message) sent by the base station to UE 102 before sending the DCI and the scrambled CRC, such as when UE 102 is in the RRC_CONNECTED state.

[0064] In some implementations, a UE 102 operating in an RRC_INACTIVE or RRC_IDLE state receives a DCI and a scrambled CRC on a PDCCH. The UE 102 then confirms that a physical downlink shared channel (PDSCH) including a second DLPDU is addressed to the UE 102 based on the ID of the UE 102, the DCI, and the scrambled CRC. The UE 102 then retrieves data from the security-protected packet. If the security-protected packet is an encrypted packet, the UE 102 may decrypt the encrypted packet using an appropriate decryption function and a security key to obtain the data. If the security-protected packet is an integrity-protected packet including data and a MAC-I, the UE 102 may determine whether the MAC-I is valid. If the UE 102 confirms that the MAC-I is valid, the UE 102 retrieves the data. However, if the UE 102 determines that the MAC-I is invalid, the UE 102 discards the packet. In addition, in an implementation where the security-protected packet is both encrypted and integrity-protected (having encrypted data and encrypted MAC-I), the UE 102 decrypts the encrypted packet and the encrypted MAC-I to obtain the data and the MAC-I. The UE 102 can then verify that the MAC-I is valid for the data. If the UE 102 confirms that the MAC-I is valid, the UE 102 retrieves and processes the data. Otherwise, when the UE 102 determines that the MAC-I is invalid, the UE 102 discards the data.

[0065] The base station 104 is equipped with processing hardware 130, which may include one or more general-purpose processors (e.g., CPUs) and non-transitory computer-readable memory that stores instructions executed by one or more general-purpose processors. Additionally or alternatively, the processing hardware 130 may include a dedicated processing unit. In an example implementation, the processing hardware 130 includes a media access control (MAC) controller 132, which is configured to: perform a random access procedure with one or more user devices, receive uplink MAC protocol data units (PDUs) of one or more user devices, and send downlink MAC PDUs to one or more user devices. The processing hardware 130 may also include a packet data convergence protocol (PDCP) controller 134, which is configured to: send DL PDCP PDUs in some scenarios, according to which the base station 104 can send data in the downlink direction; and receive UL PDCP PDUs in other scenarios, according to which the base station 104 can receive data in the uplink direction. The processing hardware may further include an RRC controller 136 to implement processes and message delivery at the RRC sublayer of the protocol communication stack. In an example implementation, the processing hardware 130 includes an RRC inactive controller 138, which is configured to manage uplink and / or downlink communications with one or more UEs operating in an RRC_INACTIVE or RRC_IDLE state. The base station 106 may include substantially similar components. Specifically, components 140, 142, 144, 146, and 148 of the base station 106 may be similar to components 130, 132, 134, 136, and 138, respectively.

[0066] UE 102 is equipped with processing hardware 150, which may include one or more general-purpose processors (such as CPUs) and non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors, and / or special-purpose processing units. In an example implementation, processing hardware 150 includes an RRC inactive controller 158, which is configured to manage uplink and / or downlink communications when UE 102 operates in an RRC_INACTIVE state. In an example implementation, processing hardware 150 includes a media access control (MAC) controller 152, which is configured to perform a random access procedure with a base station, send uplink MAC protocol data units (PDUs) to the base station, and receive downlink MAC PDUs from the base station. The processing hardware 150 may also include a PDCP controller 154 configured to: transmit a DL PDCP PDU in some scenarios, according to which the base station 106 may transmit data in a downlink direction; and receive a UL PDCP PDU in further scenarios, according to which the base station 106 may receive data in an uplink direction. The processing hardware may further include an RRC controller 156 to implement procedures and messaging at the RRC sublayer of the protocol communication stack.

[0067] Figure 1B An example distributed or decentralized implementation of any one or more of the base stations 104, 106 is depicted. In this implementation, the base stations 104, 106 include a central unit (CU) 172 and one or more distributed units (DU) 174. The CU 172 includes processing hardware, such as one or more general-purpose processors (e.g., CPUs) and a computer-readable memory storing machine-readable instructions that can be executed on the general-purpose processors, and / or a dedicated processing unit. For example, the CU 172 may include a PDCP controller, an RRC controller, and / or an RRC inactive controller, such as the PDCP controllers 134, 144, the RRC controllers 136, 146, and / or the RRC inactive controllers 138, 148. In some implementations, the CU 172 includes a radio link control (RLC) controller that is configured to manage or control one or more RLC operations or processes. In further implementations, the CU 172 does not include an RLC controller.

[0068] Each of the DUs 174 also includes processing hardware, which may include one or more general-purpose processors (e.g., CPUs) and computer-readable memory storing machine-readable instructions executable on the one or more general-purpose processors, and / or a dedicated processing unit. For example, the processing hardware may include: a MAC controller (e.g., MAC controllers 132, 142) configured to manage or control one or more MAC operations or processes (e.g., random access processes); and / or an RLC controller configured to manage or control one or more RLC operations or processes. The processing hardware may also include a physical layer controller configured to manage or control one or more physical layer operations or processes.

[0069] In some embodiments, the RAN 105 supports integrated access and backhaul (IAB) functionality. In some implementations, the DU 174 operates as an (IAB) node and the CU 172 operates as an IAB donor.

[0070] In some implementations, the CU 172 includes a logical node CU-CP 172A that hosts a control plane portion of a PDCP protocol of the CU 172. In further implementations, the CU 172 includes a logical node CU-UP 172B that hosts a user plane portion of a PDCP protocol and / or a Service Data Adaptation Protocol (SDAP) protocol of the CU 172. Depending on the implementation, the CU-CP 172A sends control information (e.g., RRC messages, F1 application protocol messages), and the CU-UP 172B sends data packets (e.g., SDAP PDUs or Internet Protocol packets).

[0071] CU-CP 172A may be connected to multiple CU-UPs 172B via an E1 interface. CU-CP 172A selects an appropriate CU-UP 172B for the requested service of UE 102. In some implementations, a single CU-UP 172B is connected to multiple CU-CPs 172A via an E1 interface. CU-CP 172A may be connected to one or more DUs 174 via an F1-C interface. CU-UP 172B may be connected to one or more DUs 174 via an F1-U interface under the control of the same CU-CP 172A. In some implementations, one DU 174 is connected to multiple CU-UPs 172B under the control of the same CU-CP 172A. In such an implementation, CU-CP 172A establishes connectivity between CU-UP 172B and DU 174 by using a bearer context management function.

[0072] Figure 2AAn example protocol stack 200 is shown in a simplified manner, according to which a UE 102 may communicate with an eNB / ng-eNB or gNB (e.g., one or both of base stations 104, 106).

[0073] In the example stack 200, the physical layer (PHY) 202A of EUTRA provides transport channels to the EUTRA MAC sublayer 204A, which in turn provides logical channels to the EUTRA RLC sublayer 206A. The EUTRA RLC sublayer 206A in turn provides RLC channels to the EUTRA PDCP sublayer 208 and, in some cases, to the NR PDCP sublayer 210. Similarly, the NR PHY 202B provides transport channels to the NR MAC sublayer 204B, which in turn provides logical channels to the NR RLC sublayer 206B. The NR RLC sublayer 206B in turn provides data delivery services to the NR PDCP sublayer 210. In some implementations, the NR PDCP sublayer 210 then provides data to the Service Data Adaptation Protocol (SDAP) 212 or the Radio Resource Control (RRC) sublayer ( Figure 2A (not shown) provides data transfer services. In some implementations, such as Figure 2A As shown, UE 102 supports both EUTRA and NR stacks to support handover between EUTRA and NR base stations and / or support DC implemented through EUTRA and NR interfaces. Figure 2A As shown, the UE 102 can support NR PDCP 210 layered on EUTRA RLC 206A, and the SDAP sublayer 212 layered on the NR PDCP sublayer 210.

[0074] The EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 receive packets, which may be referred to as service data units (SDUs) (e.g., from an Internet Protocol (IP) layer layered directly or indirectly on the PDCP layer 208 or 210), and output packets, which may be referred to as protocol data units (PDUs) (e.g., to the RLC layer 206A or 206B). Unless the difference between SDUs and PDUs is relevant, for simplicity, this disclosure refers to both SDUs and PDUs as "packets".

[0075] In some implementations, for example, on the control plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 provide a signaling radio bearer (SRB) or an RRC sublayer ( Figure 2AIn the embodiment of the present invention, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 may be used to exchange RRC messages or non-access stratum (NAS) messages. In a further implementation, on the user plane, the EUTRA PDCP sublayer 208 and the NR PDCP sublayer 210 provide data radio bearers (DRBs) to support data exchange. The data exchanged on the NR PDCP sublayer 210 may be SDAP PDUs, Internet Protocol (IP) packets, or Ethernet packets.

[0076] Figure 2B An example protocol stack 250 is shown in a simplified manner, via which the UE 102 can communicate with a DU (e.g., DU 174) and a CU (e.g., CU 172). The radio protocol stack 200 is functionally divided, such as Figure 2B 206B, NR MAC 204B, and NR PHY 202B) are delegated to the DU. To support the connection to the 5GC, the NR PDCP 210 provides SRBs to the RRC 214, and the NR PDCP 210 provides DRBs to the SDAP 212 and SRBs to the RRC 214.

[0077] Next, follow-up reference Figures 3 to 6 To discuss the Figure 1A Several components of and several example scenarios related to sending data in an inactive or idle state. In order to simplify the following description, "inactive state" is used and it can represent RRC_INACTIVE or RRC_IDLE state, and "connected state" is also used and it can represent RRC_CONNECTED state.

[0078] First reference Figure 3, the figure shows a scenario 300 in which a base station 104 includes a central unit (CU) 172 and a distributed unit (DU) 174. CU 172 further includes CU-CP 172A and CU-UP 172B. In scenario 300, UE 102 initially operates in a connected state 302 and communicates 304 with DU 174, such as by using a DU configuration (i.e., a first non-SDT DU configuration). UE 102 further communicates 304 with CU-CP 172A and / or CU-UP 172B via the DU by using the CU configuration (i.e., the first non-SDT CU configuration). While the UE is communicating 304 with the base station 104, CU-CP 172A may send 306 a UE context modification request message. In response, DU 174 sends 308 a UE context modification response message to CU-CP 172A including a non-SDT configuration for UE 102 (i.e., a second non-SDT configuration). CU-CP 172A generates an RRC reconfiguration message including the second non-SDTDU configuration and sends 310 a first CU-to-DU message (e.g., a DL RRC messaging message) including the RRC reconfiguration message to DU 174. DU 174, in turn, sends 312 the RRC reconfiguration message to UE 102. In response, UE 102 sends 314 an RRC reconfiguration complete message to DU 174, which in turn sends 316 a first DU-to-CU message (e.g., an UL RRC messaging message) including the RRC reconfiguration complete message to CU-CP 172A.

[0079] After receiving 312 the RRC reconfiguration message, the UE 102 in the connected state communicates 318 with the DU 174 using the second non-SDT DU configuration. The UE 102 further communicates with the CU-CP 172A and / or the CU-UP 172B via the DU 174. In the event that the RRC reconfiguration message does not include a CU configuration, the UE 102 communicates 318 with the CU-CP 172A and / or the CU-UP 172B via the DU 174 using the first non-SDT CU configuration. In the event that the RRC reconfiguration message includes a non-SDT CU configuration (i.e., the second non-SDT CU configuration), the UE 102 communicates 318 with the CU-CP 172A and / or the CU-UP 172B via the DU 174 using the second non-SDT CU configuration.

[0080] In some implementations, the second non-SDT CU configuration modifies or augments the first non-SDT CU configuration, or includes at least one new configuration parameter not included in the first non-SDT CU configuration. In such a case, the UE 102 and at least one of the CU-CP 172A and / or CU-UP 172B may communicate 318 with each other using the second non-SDU CU configuration and the configuration parameters in the first non-SDT CU configuration that are not modified or augmented by the second non-SDU CU configuration. In some implementations, the first non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers (e.g., RRC 214 and / or NR PDCP 210), and the UE 102 and the CU 172 use the configuration parameters to communicate with each other when the UE 102 operates in a connected state. Similarly, in a further implementation, the second non-SDT CU configuration includes configuration parameters related to the operation of the RRC and / or PDCP protocol layers, and when the UE 102 operates in the connected state, the UE 102 and the CU 172 communicate with each other using the configuration parameters.

[0081] In some implementations, the first non-SDT CU configuration includes configuration parameters in a RadioBearerConfig information element (IE) and / or a MeasConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. Similarly, the second non-SDT CU configuration includes configuration parameters in a RadioBearerConfig IE and / or a MeasConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. In some implementations, the first non-SDTCU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE, and the second non-SDT CU configuration may be or include a RadioBearerConfig IE and / or a MeasConfig IE.

[0082] In some implementations, the first non-SDT DU configuration includes configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers (e.g., RLC 206B, MAC 204B, and / or PHY 202B), which are used by the UE 102 and the DU 174 to communicate with each other when the UE 102 operates in a connected state. Similarly, the second non-SDT DU configuration may include configuration parameters related to the operation of the RRC, RLC, MAC, and / or PHY protocol layers, which are used by the UE 102 and the DU 174 to communicate with each other when the UE 102 operates in a connected state.

[0083] In some implementations, the first non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. Similarly, the second non-SDT DU configuration includes configuration parameters in a CellGroupConfig IE defined in 3GPP specification 38.331 version 16.7.0 or later. In some implementations, the first non-SDT DU configuration and the second non-SDT DU configuration are CellGroupConfig IEs.

[0084] Events 306, 308, 310, 312, 314, 316, and 318 are Figure 3 The non-SDT resource (re)configuration process 390 is collectively referred to as the non-SDT resource (re)configuration process, which may be optional.

[0085] While the UE 102 is communicating with the base station 104, or after the non-SDT resource configuration / reconfiguration process 390 (if performed), the CU-CP 172A may determine to transition the UE 102 from the connected state to the inactive state based on the data inactivity of the UE 102 (i.e., the UE 102 in the connected state does not have data activity with the base station 104). In some implementations, while the UE 102 is communicating with the base station 104, or after the non-SDT resource configuration / reconfiguration process 390 (if performed), the UE 102 determines or detects the data inactivity and sends 320 UE assistance information (e.g., a UEAssistanceInformation message) to the DU 174, the UE assistance information indicating that the UE 102 prefers or requests to transition to the inactive state or leave the connected state. In some implementations, the UE 102 indicates in the UE assistance information that the UE 102 prefers or requests to transition to the inactive state of the configured SDT. Then, DU 174 sends 321 a UL RRC messaging message including the UE assistance information to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 has data inactivity based on the UE assistance information.

[0086] In other implementations, the DU 174 performs data inactivity monitoring for the UE 102. The CU-CP 172A may send (not shown) a CU-to-DU message (e.g., a UE context setup request message or a UE context modification request message) to the DU 174 to request or command the DU 174 to perform data inactivity monitoring. In the event that the DU 174 detects or determines during monitoring that the UE 102 has data inactivity, the DU 174 may send 322 an inactivity notification (e.g., a UE inactivity notification message) to the CU-CP 172A. Thus, the CU-CP 172A may determine that the UE 102 has data inactivity based on the inactivity notification received from the DU 174.

[0087] In yet other implementations, CU-UP 172B performs data inactivity monitoring for UE 102. CU-CP 172A may send (not shown) a CP to UP message (e.g., a bearer context setup request message or a bearer context modification request message) to CU-UP 172B to request or command CU-UP 172B to perform data inactivity monitoring. In the event that CU-UP 172B detects or determines that UE 102 has data inactivity during monitoring, CU-UP 172B may send 323 an inactivity notification (e.g., a bearer context inactivity notification message) to CU-CP 172A. Thus, CU-CP 172A may determine that UE 102 has data inactivity based on the inactivity notification received from CU-UP 172B. In some implementations, CU-CP 172A determines that UE 102 has data inactivity based on UE assistance information from events 320, 321, an inactivity notification of event 322, and / or an inactivity notification of event 323.

[0088] In some implementations, after a specific period of data inactivity, CU-CP 172A determines that neither CU 172 (i.e., CU-CP 172A and / or CU-UP 172B) nor UE 102 has sent any data in the downlink direction or uplink direction, respectively, during the specific period. In response to the determination, CU-CP 172A may determine to transition UE 102 to an inactive state with SDT configured. Alternatively, CU-CP 172A may determine to transition UE 102 to an inactive state without SDT configured in response to determining that UE 102 has data inactivity.

[0089] In response to determining that the UE 102 has data inactivity (within a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, or thereafter, the CU-CP 172A sends 324 a bearer context modification request message to the CU-CP 172B to suspend data transmission of the UE 102. In response, the CU-UP 172B suspends data transmission of the UE 102 and sends 326 a bearer context modification response message to the CU-CP 172A. In some implementations, in response to determining that the UE 102 has data inactivity (within a specific period of time) or determining to transition the UE 102 to an inactive state with SDT configured, or thereafter, the CU-CP 172A sends 328 a second CU-to-DU message (e.g., a UE context modification request message) to instruct the DU 174 to provide an SDT DU configuration for the UE 102. In some implementations, the CU-CP 172A includes an SDT request indication (eg, an IE such as a CG-SDT Query Indication IE or an SDT Query Indication IE) requesting SDT DU configuration in the second CU-to-DU message.

[0090] In a further implementation, in response to the SDT request indication or the second CU-to-DU message, the DU 174 sends 330 a second DU-to-CU message (e.g., a UE context modification response message) to the CU-CP 172A. Alternatively, the DU 174 does not include the SDT DU configuration in the second DU-to-CU message. Instead, after receiving the second CU-to-DU message or sending the second DU-to-CU message, the DU 174 sends (not shown) an additional DU-to-CU message (e.g., a UE context modification request message) including the SDT DU configuration to the CU-CP 172A. In some implementations, the CU-CP 172A sends (not shown) an additional CU-to-DU message (e.g., a UE context modification confirmation message) to the DU 174 in response to the additional CU-to-DU message.

[0091] In other implementations, the CU-CP 172A sends 328 a second CU to DU message and receives 330 a second DU to CU message or an additional DU to CU message before determining that the UE 102 has data inactivity. In still other implementations, the CU-CP 172A includes an SDT request indication in the first CU to DU message at event 308, and the DU 174 includes an SDT DU configuration in the first DU to CU message at event 310 in response to the SDT request indication.

[0092] Depending on the implementation, in response to determining to transition the UE 102 to the inactive state in which the SDT is configured, the CU-CP 172A generates an RRC release message (e.g., an RRCRelease message, an RRCConnectionRelease message) to transition the UE 102 to the inactive state. The CU-CP 172A may include the SDT DU configuration (if obtained from the DU 174) and / or the SDT CU configuration in the RRC release message. Then, the CU-CP 172A sends 332 a third CU-to-DU message (e.g., a UE context release command message, a UE context modification request message, or a DL RRC messaging message) including the RRC release message to the DU 174. Subsequently, the DU 174 sends 334 the RRC release message to the UE 102. In some implementations, the DU 174 generates a MAC PDU including the RRC release message and sends 334 the MAC PDU to the UE 102. The RRC release message instructs the UE 102 to transition to the inactive state. UE 102 transitions 336 from the connected state to the inactive state upon receiving the RRC release message. Depending on the implementation, in response to the third CU to DU message, DU 174 retains the SDT DU configuration (if generated by DU 174 during processes 328, 330) and may release or retain (a portion of) the first non-SDT DU configuration and / or (a portion of) the second non-SDT DU configuration. In response to the third CU to DU message, DU 174 may send (not shown) a third DU to CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A.

[0093] In some implementations, when operating 302 in a connected state, the UE 102 uses the C-RNTI to monitor the PDCCH to receive DCI. In response to receiving 334 an RRC release message, or thereafter, the UE 102 stops using the C-RNTI to monitor the PDCCH. In some implementations, in response to receiving 334 an RRC release message or transitioning 336 from a connected state to an inactive state, or thereafter, the UE 102 retains the C-RNTI. In some implementations, the UE 102 performs a two-step or four-step random access procedure with a base station 104 (e.g., CU-CP 172A and / or DU 174) and receives a random access response message including the C-RNTI from the DU 174 during the random access procedure. In other implementations, the UE 102 receives a random access response message from the CU-CP 172A or from the DU 174 via the DU 174. Figure 3 Another base station (eg, base station 106) not shown in the figure receives an RRC message (eg, an RRC reconfiguration message) including the C-RNTI.

[0094] Events 320 (optional), 321 (optional), 322 (optional), 323, 324, 326, 328, 330, 332, and 334 are Figure 3 It is collectively referred to as the SDT configuration process 394.

[0095] In some implementations, in response to the RRC release message, the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT DU configuration. In further implementations, in response to the RRC release message, the UE 102 releases at least a portion of the first non-SDT DU configuration and / or at least a portion of the second non-SDT DU configuration. In other implementations, if the RRC release message instructs the UE 102 to transition to an idle state (i.e., RRC_IDLE), the UE 102 releases the first non-SDT DU configuration and / or the second non-SDT configuration. In yet other implementations, if the RRC release message instructs the UE 102 to transition to an inactive state (i.e., RRC_INACTIVE), the UE 102 releases the first non-SDT DU configuration and / or the first portion of the second non-SDT DU configuration, and retains the second portion of the first non-SDT DU configuration and / or the second non-SDT DU configuration. In still other implementations, if the RRC release message instructs the UE 102 to transition to an inactive state (ie, RRC_INACTIVE), the UE 102 retains the first non-SDT DU configuration (if received, not augmented by the second non-SDT DU configuration) and / or the second non-SDT DU configuration.

[0096] In some implementations, CU-CP 172A does not include an indication for instructing DU 174 to retain the SDT DU configuration in the third CU to DU message. DU 174 retains the SDT DU configuration as described above by default. In other implementations, CU-CP 172A includes an indication for instructing DU 174 to retain the SDT DU configuration in a third CU to DU message (e.g., a UE context release command message), and DU 174 retains the SDT DU configuration in response to the indication. If the UE context release command message excludes the indication, DU 174 releases the SDT DU configuration. In yet other implementations, CU-CP 172A does not include an indication for instructing DU 174 to release the SDT DU configuration in a third CU to DU message (e.g., a UE context modification request message or a DL RRC messaging message) for UE 102. Therefore, in response to the third CU to DU message excluding the indication, DU 174 retains the SDT DU configuration. If the third CU-to-DU message includes the indication, the DU 174 releases the SDT DU configuration.

[0097] In some implementations, the SDT CU configuration (e.g., SDT-Config IE) includes a DRB list (e.g., std-DRB-List) including a DRB ID list indicating the IDs of the DRBs configured for SDT. In some implementations, the SDT CU configuration may include an SRB2 indication (e.g., sdt-SRB2-Indication) indicating the SRB2 configured for SDT. In some implementations, the SDT CU configuration includes a compression protocol continuation indication (e.g., sdt-DRB-ContinueROHC) indicating that the PDCP entity for the DRBs configured for SDT is in SDT operation (i.e., for Figure 4 In some implementations, the CU-CP 172A includes the SDT DU configuration in the SDT CU configuration. In some implementations, the “SDT CU configuration” is simplified to “SDT configuration”.

[0098] In some implementations, the SDT DU configuration includes at least one of a buffer status report (BSR) configuration, a power headroom report (PHR) configuration, a configured grant (CG) configuration for CG-SDT, a UL bandwidth part (BWP) configuration, a DL BWP configuration for CG-SDT, a time alignment timer value for CG-SDT (e.g., a CG-SDT time alignment timer (CG-SDT-TAT) value), and / or a timing advance validity threshold for CG-SDT. In some implementations, the UL BWP configuration configures a dedicated UL BWP for the UE 102 to perform CG-SDT. Depending on the implementation, the UL BWP configuration includes a CG configuration, a PUCCH configuration, a PUSCH configuration, and / or a sounding reference signal (SRS) configuration. In some implementations, the DL BWP configuration configures a dedicated DL BWP for the UE 102 during CG-SDT. In some implementations, the DL BWP configuration includes a PDCCH configuration and / or a PDSCH configuration for the UE to receive DL control signals from DU 174 on the PDCCH and data from DU 174 on the PDSCH when UE 102 performs CG-SDT with DU 174. Each of the CG configurations configures periodic radio resources (i.e., CG resources), which UE 102 can use to send data without receiving a dynamic grant for data transmission. Each of the CG configurations configures or includes a periodicity, indicating that the CG resources appear periodically. In some implementations, the periodicity is a fixed number of symbols, time slots, or subframes. Depending on the implementation, some or all of the CG configurations have the same periodicity or different periodicities.

[0099] In some implementations, each of the CG configurations configures or includes an offset that indicates a time domain offset (e.g., timeDomainOffset) of the CG resources relative to a reference time (e.g., system frame number (SFN)). In some implementations, the CG configuration configures or includes a reference time (e.g., timeReferenceSFN). In some implementations, the CG configuration is or is similar to the ConfiguredGrantConfig IE specified in 3GPP specification 38.331. DU 174 configures a timing advance validity threshold (e.g., including an RSRP range) for UE 102 to determine whether UE 102 can initiate SDT using a configured grant configuration for CG-SDT, such as for Figure 4 Based on the timing advance validity threshold, UE 102 evaluates whether the stored timing advance value is still valid. In an implementation where UE 102 determines that the stored timing advance value is invalid, UE 102 initiates a RA-SDT with CU 172 via DU 174, as described for Figure 4 In some implementations, the SDTDU configuration is an SDT-MAC-PHY-CG-Config IE or an SDT-MAC-PHY-Config IE.

[0100] In some implementations, "SDT DU configuration" is replaced with "CG-SDT configuration". In such implementations, the configurations in the SDT DU configuration are specific to CG-SDT. In other implementations, some of the configurations in the SDT DU configuration described above are part of the CG-SDT configuration, while other configurations in the SDT DU configuration (e.g., BSR configuration and / or PHR configuration) are not within the CG-SDT configuration. The SDT DU configuration includes the CG-SDT configuration. In such a case, UE 102 configures other configurations for CG-SDT or RA-SDT. In other implementations, the "SDT DU configuration" is simplified to the "SDT configuration".

[0101] In some implementations, the DU 174 starts or restarts the DU CG-SDT timer in response to or after receiving the SDT request indication, generating the CG-SDT configuration, receiving 328 the second CU to DU message, sending 330 the CG-SDT configuration to the CU 172, receiving 332 the third CU to DU message, or sending 334 the CG-SDT configuration to the UE 102. In further implementations, the DU 174 starts or restarts the DU CG-SDT timer with the timer value to manage the CG-SDT configuration.

[0102] In some implementations, the timer value is the same as the CG-SDT time alignment timer value. In other implementations, the timer value is close to the CG-SDT time alignment timer value. For example, the timer value may be greater than and close to the CG-SDT time alignment timer value. In another example, the timer value may be less than and close to the CG-SDT time alignment timer value. In the event that the DU CG-SDT timer expires, DU 174 releases the CG-SDT configuration or the CG resources configured in the CG-SDT configuration. When the CG-SDT configuration is released, or thereafter, DU 174 avoids receiving PUSCH transmissions from UE 102 on radio resources reserved or configured by RAN 105 for the CG-SDT configuration. In some implementations, when the CG-SDT configuration is released, or thereafter, DU 174 schedules transmissions for other UEs on radio resources reserved or configured for the CG-SDT configuration.

[0103] As described above, in some implementations, the RRC release message 334 includes a CG-SDT configuration. In response to receiving the CG-SDT configuration, or thereafter, the UE 102 starts or restarts a UE CG-SDT timer (e.g., CG-SDT-TAT). In some implementations, in response to receiving the CG-SDT configuration, or thereafter, the UE 102 starts or restarts a UE CG-SDT timer (i.e., a first UE CG-SDT timer). In some cases where the UE CG-SDT timer expires, the UE 102 releases the CG-SDT configuration. In other cases where the UE CG-SDT timer expires, the UE 102 instead retains the CG-SDT configuration and avoids sending UL transmissions (e.g., MAC PDUs) on CG resources. In some such cases, the UE 102 releases the CG resources or determines that the CG resources are invalid. Depending on the implementation, when the UE CG-SDT timer expires, the UE 102 releases the SRS configuration or the SRS resources configured in the SRS configuration. Alternatively, when the UE CG-SDT timer expires, the UE 102 retains the SRS configuration and refrains from sending one or more SRSs to the DU 174 on the SRS resources.

[0104] When the UE CG-SDT timer is running, the UE 102 in an inactive state communicates with the DU 174 via the dedicated DL BWP and the dedicated ULBWP (e.g., performs CG-SDT, sends SRS and / or receives DL control signals (e.g., DCI) and / or data). In some implementations, when the UE CG-SDT timer expires, the UE 102 in an inactive state switches from the dedicated DL BWP and the dedicated UL BWP to the initial DL BWP and the initial UL BWP, respectively. In some such cases, the UE 102 readjusts the transceiver of the UE 102 to switch to the initial DL BWP and the initial UL BWP. In some implementations, when the RAN 105 configures the UE 102 using the CG-SDT configuration, the UE 102 in an inactive state switches to the initial DL BWP and the initial ULBWP to perform a random access procedure. Depending on the implementation, the UE 102 performs a random access procedure for different situations as described below. In some implementations, the UE 102 in the inactive state switches to the initial DL BWP and the initial UL BWP to perform measurements on the SSBs sent by the DU 174 on the initial DL BWP.

[0105] In some implementations, the DU 174 or the CU-CP 172A configures the dedicated DL BWP and the dedicated UL BWP to be the same as or include the initial DL BWP and the initial UL BWP, respectively. In some such implementations, when the UE CG-SDT timer expires, the UE 102 does not switch from the dedicated DL BWP and the dedicated UL BWP to the initial DL BWP and the initial UL BWP, respectively. In further such cases, the UE 102 does not readjust the transceiver of the UE 102 due to switching BWP. In still further such cases, when the UE 102 in an inactive state performs a random access procedure with the DU 174, the UE 102 performs the random access procedure without switching to the initial DL BWP and the initial UL BWP. In such a case, while performing CG-SDT with the DU 174, the UE 102 performs measurements on the SSBs sent by the DU 174 within the initial DL BWP.

[0106] In some implementations, in response to expiration of the UE CG-SDT timer, or thereafter, the UE 102 performs RA-SDT with the CU 172 via the DU 174 on the initial UL BWP and the initial DL BWP, such as for Figure 4 That is, in response to the UE CG-SDT timer expiring, or thereafter, the UE 102 determines that the RA-SDT is valid.

[0107] In some implementations, DU 174 reserves the CG resources configured in the CG configuration. In further implementations, DU 174 releases the CG resources when the SDT DU configuration or the CG-SDT configuration is released, or when the DU CG-SDT timer expires. In some implementations, DU 174 releases the SRS resources configured in the SRS configuration when the SDT DU configuration or the CG-SDT configuration is released, or when the DU CG-SDT timer expires.

[0108] In the case where DU 174 does not provide CG-SDT configuration or SDT DU configuration to CU-CP 172A, in response to the third CU-to-DU message, DU 174 releases all signaling and user data transmission resources for UE 102. In the case where DU 174 provides SDT DU configuration or CG-SDT configuration to CU-CP 172A, in response to receiving the third CU-to-DU message, or thereafter, DU 174 reserves signaling and user data transmission resources for UE 102.

[0109] In the case where the SDT DU configuration does not include a configuration for CG-SDT, CU-CP 172A and / or DU 174 only configure RA-SDT for UE 102. In some such cases, UE 102 performs RA-SDT with CU 172 via DU 174, such as for Figure 4 described.

[0110] In some implementations, when determining to transition UE 102 to an inactive state with SDT configured, CU-CP 172A does not request DU 174 to provide an SDT DU configuration. In some such cases, events 328 and 330 are omitted, and CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A generates the SDT DU configuration on its own without requesting DU 174 to provide the SDT DU configuration, and includes the SDT DU configuration in the RRC release message.

[0111] In some implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message. In some such implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message because UE 102 does not support CG-SDT, and therefore DU 174 does not support CG-SDT. In other implementations, DU 174 does not include the SDT DU configuration in the second DU to CU message because DU 174 does not have available radio resources for CG-SDT. In such a case, the RRC release message does not include the SDT DU configuration. Otherwise, DU 174 sends the SDT DU configuration to CU-CP 172A as described above.

[0112] In some implementations, DU 174 does not include the configuration for CG-SDT in the SDT DU configuration in the second DU to CU message. In some such implementations, DU 174 does not include the configuration for CG-SDT because UE 102 does not support CG-SDT, and therefore DU 174 does not support CG-SDT. In other implementations, DU 174 does not include the configuration for CG-SDT because DU 174 does not have available radio resources for CG-SDT. In such a case, the SDT DU configuration does not include the CG-SDT configuration. Otherwise, DU 174 includes the CG-SDT configuration in the SDT DU configuration, as described above.

[0113] In some implementations, such as when UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A requests DU 174 to provide SDT DU configuration, as described above. In the case where UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, CU-CP 172A does not request DU 174 to provide SDT DU configuration. Depending on the implementation, when UE 102 operates 302 in a connected state, CU-CP 172A receives UE capabilities (e.g., UE-EUTRA-Capability IE, UE-NR-Capability IE, or UE-6G-Capability IE) of UE 102 from UE 102, CN 110 (e.g., MME 114 or AMF 164), or base station 106. UE capabilities indicate whether UE 102 supports CG-SDT. Thus, CU-CP 172A may determine whether UE 102 supports CG-SDT based on UE capabilities. In some implementations, CU-CP 172A receives a DU-to-CU message from DU 174 indicating whether DU 174 supports CG-SDT. Depending on the implementation, the DU-to-CU message is a second DU-to-CU message, a message of event 308 or 316, or a non-UE-associated message (e.g., a non-UE-associated F1AP message defined in 3GPP specification 38.473).

[0114] In some implementations, depending on whether the UE 102 supports CG-SDT, the DU 174 determines whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A. In further implementations, depending on whether the DU 174 supports CG-SDT, the DU 174 additionally determines whether to provide the SDT DU configuration for the UE 102 to the CU-CP 172A. In the event that the UE 102 supports CG-SDT and / or the DU 174 supports CG-SDT, the DU 174 provides the SDT DU configuration for the UE 102 to the CU-CP 172A, as described above. In the event that the UE 102 does not support CG-SDT or the DU 174 does not support CG-SDT, the DU 174 does not provide the SDT DU configuration for the UE 102 (e.g., the DU 174 does not include the SDT DU configuration in the second DU to CU message). In some implementations, when UE 102 is operating 302 in a connected state or in an inactive state before event 302, DU 174 receives UE capabilities from CU-CP 172A. Therefore, DU 174 can determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, DU 174 sends a DU-to-CU message to CU-CP 172A indicating whether DU 174 supports CG-SDT, as described above.

[0115] Reference now Figure 4 , scenario 400 depicts a small data transmission. In scenario 400, base station 104 includes CU 172 and DU 174. CU 172 includes CU-CP 172A and CU-UP 172B. In scenario 400, UE 102 initially operates in an inactive state with SDT configured 402. In some implementations or scenarios, UE 102 transitions from a connected state with SDT configured to an inactive state, such as for Figure 3Described. In such an implementation, the UE receives a first SDT CU configuration and / or a first SDT DU configuration in an RRC release message (e.g., event 334). In other implementations or scenarios, the UE 102 transitions from an inactive state where SDT is not configured to an inactive state where SDT is configured. For example, the UE 102 receives an RRC release message from a base station (e.g., base station 104 or base station 106) that causes the UE 102 to transition to an inactive state but does not configure SDT (e.g., indicates release of SDT, or does not include the SDT configuration in the RRC release message). In this case, the UE 102 transitions to an inactive state where SDT is not configured in response to the RRC release message. The UE 102 in an inactive state where SDT is configured or not configured performs a RAN Notification Area (RNA) update with the base station without a state transition. During the RNA update, the UE 102 receives another RRC release message from the base station that includes a first SDT CU configuration and / or a first SDT DU configuration similar to the RRC release message of event 334.

[0116] At a later time, the UE 102 operating in the inactive state with SDT configured initiates SDT. In response to or after initiating SDT, the UE 102 generates an initial UL MAC PDU including a UL RRC message and initiates SDT in a cell (e.g., cell 124 or cell 126). Figure 1A 406 DU-CP 172A sends 404 the initial UL MAC PDU to DU 174 on another cell of base station 104 not shown in the figure). The following events between UE 102 and DU 174 occur on the cell. In some implementations, UE 102 starts an SDT session timer in response to initiating SDT. In some implementations, the SDT session timer is a new timer (e.g., T319a) defined in the RRC specification (e.g., Version 17.0.0). DU 174 retrieves the UL RRC message from the initial UL MAC PDU, generates a first DU to CU message including the UL RRC message, and sends 406 the first DU to CU message to CU-CP 172A. In some implementations, the first DU to CU message is an initial UL RRC message delivery message. In other implementations, the first DU to CU message is a UL RRC message delivery message.

[0117] In a scenario where the UE 102 initiates an SDT to send UL data (e.g., data packets) that is eligible for the SDT, the UE 102 sends 404 an initial UL MAC PDU including the UL data. In a scenario where the UE 102 initiates an SDT to receive DL data, the UE 102 sends 404 an initial UL MAC PDU without an UL data packet. The UE 102 may initiate an SDT to receive DL data in response to receiving a paging message (not shown) from the DU 174. In such a scenario, the UE 102 may include an SDT indication for indicating to the base station 104 that the UE 102 is initiating an SDT to receive DL data in the initial UL MAC PDU or UL RRC message.

[0118] In some implementations, the UE 102 in an inactive state performs a random access procedure with the DU 174 to send 404 a UL MAC PDU. In such a case, the SDT may be a RA-SDT. For example, the random access procedure may be a four-step random access procedure or a two-step random access procedure. In the case where the procedure is a four-step random access procedure, the UE 102 sends a random access preamble to the DU 174, and in response, the DU 174 sends a random access response (RAR) including a dynamic uplink grant, a temporary C-RNTI, and a timing advance command to the UE 102. The UE 102 then sends 404 a UL MAC PDU to the DU 174 according to the dynamic uplink grant. The DU 174 receives 404 a UL MAC PDU according to the dynamic uplink grant in the RAR, and in response, sends a DL MAC PDU including a contention resolution MAC control element to the UE 102.

[0119] In the case where the procedure is a two-step random access procedure, the UE 102 sends 404 a message A (MsgA) including a random access preamble and a UL MAC PDU to the DU 174 according to the two-step random access configuration parameters. The UE 102 receives a message B (MsgB) including a temporary C-RNTI and a timing advance command from the DU 174 in response to the MsgA. The DU 174 includes a contention resolution MAC control element in the MsgB. The UE 102 receives the two-step random access configuration parameters in the system information broadcast by the DU 174 on the cell 124 before sending 404 the UL MAC PDU. The DU 174 receives 404 the UL MAC PDU according to the two-step random access configuration parameters.

[0120] When UE 102 successfully performs contention resolution (i.e., receives a contention resolution MAC control element) during the random access procedure, UE 102 discards the previously reserved C-RNTI (e.g., for Figure 3 418 . The UE 102 uses the C-RNTI to monitor the PDCCH from the DU 174 to transmit 418 data (e.g., UL data and / or DL ​​data) with the base station 104. In detail, the UE 102 receives the DCI and the cyclic redundancy check (CRC) of the DCI on the PDCCH from the DU 174, and verifies the CRC using the C-RNTI. The DCI may include a dynamic uplink grant or a downlink assignment. If the UE 102 verifies that the CRC is correct and the DCI includes a dynamic uplink grant, the UE 102 uses the dynamic uplink grant to send 418 UL data to the DU 174. If the UE 102 verifies that the CRC is correct and the DCI includes a downlink assignment, the UE 102 uses the downlink assignment to receive 418 DL data from the DU 174. In some implementations, the DU 174 scrambles the CRC using the C-RNTI, and the UE 102 verifies the scrambled CRC using the C-RNTI.

[0121] In other implementations, for example, Figure 3 As described, when UE 102 receives a CG configuration or RAN 105 configures UE 102 using a CG configuration, UE 102 sends 404 UL MAC PDU on CG resources. In such a case, UE 102 performs CG-SDT. UE 102 does not perform a random access procedure for sending 404 UL MAC PDU. Therefore, DU 174 receives 404 UL MAC PDU on CG resources. In some such implementations, after generating or sending 404 UL MAC PDU, if CU-CP 172A or DU 174 configures UE 102 to apply a UE timer during SDT, UE 102 starts a UE timer (e.g., a second UE CG-SDT timer). In some implementations, UE 102 starts a UE timer using a UE timer value (e.g., a cg-SDT-RetransmissionTimer value). After sending 404 the UL MAC PDU, when the UE 102 receives the DCI and the CRC of the DCI from the DU 174 on the PDCCH and verifies that the CRC is correct using the C-RNTI, the UE 102 stops the UE timer. In some implementations, the DU 174 scrambles the CRC using the C-RNTI and the UE 102 verifies the scrambled CRC using the C-RNTI.

[0122] In a further implementation, similar to events 332, 334, UE 102 receives 434, 432 an RRC release message including a UE timer value from base station 104. CU-CP 172A includes the UE timer value in the CG-SDT configuration and sends the RRC release message including the CG-SDT configuration to UE 102 via DU174. In other implementations, UE 102 receives the UE timer value in a system information block (SIB) broadcast by DU174 via cell 124. When the UE timer is running, UE 102 in an inactive state or SDT session avoids retransmitting UL MAC PDUs on CG resources. In some implementations, in response to receiving 404 to the UL MAC PDU on the CG resources, or thereafter, DU 174 starts a DU timer (e.g., a second DU CG-SDT timer) using the DU timer value. In some implementations, the DU timer value is equal to or greater than the UE timer value. While the DU timer is running, DU 174 processes the UL transmission received from UE 102 on the CG resources as a new transmission.

[0123] In some implementations, the UE 102 sends 418 a subsequent UL MAC PDU including one or more UL data packets on the CG radio resources. In further implementations, the UE 102 sends 418 the subsequent UL MAC PDU on radio resources configured in a dynamic uplink grant received on the PDCCH from the DU 174. In some implementations, the UE 102 sends 418 some of the subsequent UL MAC PDUs on radio resources configured in the CG configuration and sends 418 the remainder of the subsequent UL MAC PDUs on radio resources configured in the dynamic uplink grant.

[0124] In some implementations in which the UE 102 sends 418 subsequent UL MAC PDUs on CG resources, the UE 102 starts or restarts a timer (e.g., a second UE CG-SDT timer) after generating or sending 418 each of the subsequent UL MAC PDUs. The UE 102 may start or restart the timer using the timer value as described above. When the UE timer is running, the UE 102 in an inactive state or SDT session avoids resending the UL MAC PDU. In some implementations, in response to receiving 418 each of the subsequent UL MAC PDUs on the CG resources, or thereafter, the DU 174 starts or restarts the DU timer (e.g., a second DU CG-SDT timer) using the DU timer value. When the DU timer is running, the DU 174 processes the UL transmission received from the UE 102 on the CG resources as a new transmission. In other implementations, the DU 174 processes 404, 418 UL MAC PDUs without starting the DU timer.

[0125] If UE 102 includes UL data in the initial UL MAC PDU 404, DU 174 retrieves the UL data from the initial UL MAC PDU. In some such cases, DU 174 includes the UL data in the DU to CU message of event 406. Alternatively, DU 174 sends 415 a DU to CU message including the UL data to CU-CP 172A. In such an alternative implementation, the UL data includes or is a PDCP PDU, an RRC PDU, a NAS PDU, or an LTE Positioning Protocol (LPP) PDU. Depending on the implementation, the PDCP PDU includes an RRC PDU. In a further implementation, DU 174 sends 416 UL data to CU-UP 172B separately via a user plane (UP) connection as described below. In some such implementations, the UL data includes or is a PDCP PDU, and the PDCP PDU includes an SDAP PDU, an IP packet, or an Ethernet packet.

[0126] After receiving 406 the first DU-to-CU message, in some implementations, the CU-CP 172A sends 408 a UE context setup request message to the DU 174 to establish a UE context for the UE 102 at the DU 174. In some implementations, the CU-CP 172A includes transport layer information of one or more GTP-U tunnels between the CU-UP 172B and the DU 174 in the UE context setup request message so that the DU 174 can send UL data and / or subsequent UL data (e.g., in a small data communication 418) to the CU-UP 172B via the one or more GTP-U tunnels. In response, the DU 174 sends 410 a UE context setup response message to the CU-CP 172A. After receiving 406 the first DU to CU message, sending 408 the UE context setup request message, or receiving 410 the UE context setup response message, CU-CP 172A sends 412 a bearer context modification request message to CU-UP 172B to resume data transmission for UE 102. In response, CU-UP 172B resumes data transmission for UE 102 and sends 414 a bearer context modification response message to CU-CP 172A. In some cases where the UL data of event 404 includes an RRC message or is associated with an SRB (e.g., SRB1 or SRB2), after receiving 408 the UE context setup request message or sending 410 the UE context setup response message, DU 174 sends 415 a DU to CU message including the UL data to CU-CP 172A. In some cases where the UL data is associated with a DRB, DU 174 sends 416 the UL data to CU-UP 172B. In some cases where CU-CP 172A determines that DU 174 already has the UE context of UE 102, CU-CP 172A omits events 408 and 410. For example, in the case of the CG-SDT described above, CU-CP 172A instructs DU 174 to retain the UE context of UE 102. In some such cases, instead of a UE context setup request message, CU-CP 172A sends a UE context modification request message to DU 174 to modify the UE context, and in response, DU 174 sends a UE context modification response message.

[0127] In some implementations, the CU-CP 172A may include transport layer information for the CU-UP 172B in the UE context setup request message. The transport layer information for the CU-UP 172B may include an IP address and / or an uplink tunnel endpoint ID (e.g., TEID). The DU 174 uses the transport layer information for the CU-UP 172B to send 416 UL data to the CU-UP 172B. In some cases where the UE 102 has subsequent UL data (e.g., one or more UL data packets) to send, the UE 102 sends 418 one or more subsequent UL MAC PDUs including the subsequent UL data to the DU 174. Then, the DU 174 retrieves the subsequent UL data from the subsequent UL MAC PDU. In the case where the subsequent UL data is associated with one or more SRBs (e.g., SRB1 and / or SRB2), the DU 174 sends 418 one or more DU to CU messages (e.g., UL RRC messaging messages) including the subsequent UL data to the CU-CP 172A. Each DU to CU message may include a specific UL data packet of subsequent UL data. In some cases where the CU-CP 172A receives DL data from the CN 110 or edge server, the CU-CP 172A sends 418 one or more CU to DU messages (e.g., DL RRC messaging messages) including the DL data (e.g., one or more DL data packets) to the DU 174. In turn, the DU 174 sends 418 one or more DL MAC PDUs including the DL data to the UE 102 operating in the inactive state. In some implementations, the DL data includes NAS PDUs and / or LPP PDUs.

[0128] In the case where the subsequent UL data is associated with one or more DRBs, similar to event 416, DU 174 sends 418 the subsequent UL data to CU-UP 172B. In some implementations, DU 174 includes DU transport layer information for DU 174 in the UE context establishment response message. Subsequently, CU-CP 172A may include the transport layer information of DU 174 in the bearer context modification request message. Depending on the implementation, the transport layer information of DU 174 includes an IP address and / or a downlink TEID. In some cases where CU-UP 172B receives DL data from CN 110 or an edge server, CU-UP 172B uses the transport layer information of DU174 to send 418 DL data (e.g., one or more DL data packets) to DU 174. Subsequently, DU174 sends 418 one or more DL MAC PDUs including the DL data to UE 102 operating in an inactive state.

[0129] In some implementations, the UE 102 includes a buffer status report or a power headroom report in an initial and / or subsequent UL MAC PDU according to the BSR configuration and / or the PHR configuration, respectively. In the buffer status report, the UE 102 includes or indicates the buffer status of one or more logical channels or logical channel groups. In the power headroom report, the UE 102 includes or indicates the power headroom status or value.

[0130] In some example scenarios, the subsequent UL data and / or DL ​​data described above include Internet Protocol (IP) packets, Ethernet packets, or application packets. In other scenarios, the UL data includes a PDU (e.g., an RRC PDU, a PDCP PDU, or an RLC PDU), which includes an RRC message, a NAS message, an IP packet, an Ethernet packet, or an application packet.

[0131] Events 404, 406, 408, 410, 412, 414, 415, and 416 are Figure 4 It is collectively referred to as small data transmission process 492.

[0132] In some implementations, the UL RRC message is an existing RRC recovery request message (e.g., RRCResumeRequest message, RRCResumeRequest1 message, RRCConnectionResumeRequest message, or RRCConnectionResumeRequest1 message). In other implementations, the UL RRC message is a new RRC recovery request message, similar to the existing RRC recovery request message. For example, the new RRC recovery request message may be defined in a future 3GPP standard document. The new RRC recovery request message may be in a format similar to the existing RRC recovery request message. In the case of a downlink SDT, the UL RRC message includes an SDT indication, which may be a field or an information element (IE) (e.g., resumeCause or ResumeCause). In some implementations, the UL RRC message is a common control channel (CCCH) message.

[0133] In some implementations, after the UE 102 sends 404 a UL MAC PDU or communicates 418 subsequent UL data and / or DL ​​data with the DU 174, the CU-CP 172A determines to stop the SDT of the UE 102 based on data inactivity of the UE 102 (i.e., the UE 102 in the inactive state has no data activity with the base station 104). After the UE 102 sends 404 a UL MAC PDU or communicates 418 subsequent UL data and / or DL ​​data with the DU 174, the UE 102 in the inactive state determines or detects data inactivity and sends 420 UE assistance information (e.g., a UEAssistanceInformation message) to the DU 174 indicating that the UE 102 prefers or requests to stop the SDT.

[0134] Events 420 (optional), 421 (optional), 422 (optional), 423, 424, 426, 428, 430, 432, and 434 are Figure 4 492. In the embodiment of the present invention, the UE 102 performs 495 an SDT completion procedure with the base station 104, which is similar to the procedure 494. The examples and implementations of events 320, 321, 322, 323, 324, 326, 328, 330, 332, 334 are respectively applicable to events 420, 421, 422, 423, 424, 426, 428, 430, 432, 434. Depending on the implementation, after stopping the SDT, the UE 102 performs 493 another small data transmission procedure with the base station 104, which is similar to the procedure 492. In a further implementation, after completing the procedure 493, the UE 102 performs 495 an SDT completion procedure with the base station 104, which is similar to the procedure 494.

[0135] During the SDT session (i.e., events 492 and 494), UE 102 uses the C-RNTI to monitor the PDCCH to receive DCI. In some implementations, UE 102 receives the C-RNTI during the random access procedure described for event 404. In other implementations, UE 102 receives and retains the C-RNTI, such as for Figure 3 In response to receiving 434 the RRC release message, or thereafter, the UE 102 ends the SDT session and stops using the C-RNTI to monitor the PDCCH. Depending on the implementation, the UE 102 retains the C-RNTI after receiving 434 the RRC release message or transitioning 436 from the connected state to the inactive state. In some cases where the RRC release message 434 configures the CG-SDT, the UE 102 retains the C-RNTI. In further cases where the RRC release message 434 does not configure or release the CG-SDT, the UE 102 releases the C-RNTI.

[0136] After UE 102 ends the SDT session, the inactive UE 102 monitors the PDCCH using a paging RNTI (P-RNTI). In some scenarios or implementations, the CU-CP 172A determines to page the UE 102 to receive a mobile terminated call or data. In response to the determination, the CU-CP 172A sends a CU to DU message (e.g., a paging message) to the DU 174 to request the DU 174 to page the UE 102. In response to the CU to DU message, the DU 174 generates a paging message, a DCI for scheduling a PDSCH transmission including the paging message, a CRC of the DCI; scrambles the CRC using the P-RNTI to obtain a scrambled C-RNTI; and sends the DCI and the scrambled CRC on the PDCCH monitored by the UE 102. The UE 102 receives the DCI and the scrambled CRC on the PDCCH and verifies the scrambled CRC with the G-RNTI. In the event that the UE 102 verifies that the scrambled CRC is valid, the UE 102 receives and decodes the PDSCH transmission according to the DCI. The UE 102 then retrieves the paging message from the PDSCH transmission.

[0137] In some implementations, the second SDT CU configuration is the same as the first SDT CU configuration. In other implementations, the second SDT CU configuration is different from the first SDT CU configuration. Depending on the implementation, the UE 102 updates (e.g., replaces or modifies) the first SDT CU configuration with the second SDT CU configuration. In some implementations, the CU-CP 172A includes an indication in the RRC release message for indicating that the UE 102 updates the first SDT CU configuration with the second SDT CU configuration. In some such implementations, the UE 102 updates the first SDT CU configuration with the second SDT CU configuration in response to the indication.

[0138] In other implementations, CU-CP 172A includes a modification indication for instructing UE 102 to modify the first SDT CU configuration with the second SDT CU configuration in the RRC release message. In some such implementations, UE 102 modifies the first SDT CU configuration with the second SDT CU configuration in response to the modification indication. In still other implementations, CU-CP 172A includes a setup indication for instructing UE 102 to replace the first SDT CU configuration with the second SDT CU configuration in the RRC release message. In some such implementations, UE 102 replaces the first SDT CU configuration with the second SDT CU configuration in response to the setup indication.

[0139] In some implementations, the second SDT DU configuration is the same as the first SDT DU configuration. In other implementations, the second SDT DU configuration is different from the first SDT DU configuration. Depending on the implementation, the UE 102 updates (e.g., replaces or modifies) the first SDT DU configuration with the second SDT DU configuration. In some implementations, the DU 174 includes an indication in the second SDT DU configuration that the UE 102 updates the first SDT DU configuration with the second SDT DU configuration. In some such implementations, the UE 102 updates the first SDT DU configuration with the second SDT DU configuration in response to the indication.

[0140] In other implementations, DU 174 includes a modification indication for instructing UE 102 to modify the first SDTDU configuration with the second SDTDU configuration in the second SDTDU configuration. In some such implementations, UE 102 modifies the first SDTDU configuration with the second SDTDU configuration in response to the modification indication. In still other implementations, DU 174 includes a setup indication for instructing UE 102 to replace the first SDTDU configuration with the second SDTDU configuration in the second SDTDU configuration. In some such implementations, UE 102 replaces the first SDTDU configuration with the second SDTDU configuration in response to the setup indication.

[0141] In some cases where the CU-CP 172A and / or DU 174 support delta configuration, the CU-CP 172A does not send 428 a CU to DU message to obtain a second SDT DU configuration from the DU 174. Unless the conditions for releasing the first SDT configuration are met, the DU 174 retains the first SDT DU configuration. Alternatively, the CU-CP 172A includes the first SDT DU configuration in the second CU to DU message so that the DU 174 retains the first SDT DU configuration. In some such cases, the CU-CP 172A does not include the SDT DU configuration and / or the SDT CU configuration in the RRC release message so that the UE 102 continues to use the first SDT CU configuration and / or the first SDU DU configuration. In some implementations, the CU-CP 172A does not include a release indication in the RRC release message so that the UE 102 is configured to continue to use the first SDT DU configuration and / or the first SDT CU configuration. The release indication indicates the release of the previously received SDT DU configuration and / or SDT CU configuration. In the case where CU-CP 172A includes the release indication in the RRC release message, UE 102 releases the first SDT CU configuration and / or the first SDTDU configuration in response to the release indication. In some cases where CU-CP 172A and / or DU 174 do not support incremental configuration, CU-CP 172A includes the SDT DU configuration and / or SDT CU configuration in the RRC release message as described above.

[0142] In some implementations, in response to the third CU-to-DU message, DU 174 retains the second SDT DU configuration and may release the first non-SDT DU configuration and / or the second non-SDT DU configuration. In response to the third CU-to-DU message, DU 174 sends a third DU-to-CU message (e.g., a UE context release complete message or a UE context modification response message) to CU-CP 172A. In some implementations, if the RRC release message instructs UE 102 to transition to an idle state (i.e., RRC_IDLE), UE 102 releases the non-SDT configuration (e.g., for Figure 3 The first non-SDT DU configuration, the first non-SDT CU configuration, the second non-SDT DU configuration and / or the second non-SDT CU configuration) and at least one SDT configuration (e.g., for Figure 3 The SDT DU configuration and SDT CU configuration described above).

[0143] In some implementations, CU-CP 172A does not request DU 174 to provide an SDT DU configuration to transition UE 102 to an inactive state with SDT configured. In some such cases, events 428 and 430 are omitted. In such cases, CU-CP 172A does not include the SDT DU configuration in the RRC release message. Alternatively, CU-CP 172A generates the SDT DU configuration separately and includes the SDT DU configuration in the RRC release message.

[0144] In some implementations, similar to the above description of Figure 3 In the process described above, DU 174 does not include the SDT DU configuration in the second DU to CU message. Figure 3 According to the described process, DU 174 does not include the configuration for CG-SDT in the SDT DU configuration in the second DU to CU message.

[0145] In some implementations where UE 102 supports CG-SDT and / or DU 174 supports CG-SDT, CU-CP 172A requests DU 174 to provide SDT DU configuration, as described above. In the case where UE 102 does not support CG-SDT or DU 174 does not support CG-SDT, CU-CP 172A does not request DU 174 to provide SDT DU configuration. Depending on the implementation, before UE 102 initiates SDT, when UE 102 operates in an inactive state 402, when UE 102 performs SDT (e.g., in a UE context setup request message of event 408 or a CU to DU message of event 428), or when UE 102 is in a state such as for a CU-to-DU message, the CU-CP 172A requests DU 174 to provide SDT DU configuration. Figure 3 When operating in the described connected state, CU-CP 172A receives UE capabilities (e.g., UE-EUTRA-Capability IE, UE-NR-Capability IE, or UE-6G-Capability IE) of UE 102 from UE 102, CN 110 (e.g., MME 114 or AMF 164), or base station 106. The UE capabilities indicate whether UE 102 supports CG-SDT. Therefore, CU-CP 172A can determine whether the UE supports CG-SDT based on the UE capabilities. In some implementations, CU-CP 172A receives a DU to CU message from DU 174 indicating whether DU 174 supports CG-SDT. The DU to CU message can be a second DU to CU message, a message of event 308 or 316, or a non-UE associated message (e.g., a non-UE associated F1AP message defined in 3GPP specification 38.473).

[0146] In some implementations, depending on whether UE 102 or DU 174 supports CG-SDT, DU 174 determines whether to provide SDT DU configuration for UE 102 to CU-CP 172A, similar to the above. Figure 3 In addition, DU 174 may determine and signal UE 102 whether CG-SDT is supported, similar to the above Figure 3 .

[0147] Reference now Figure 5A , scenario 500A depicts a small data transfer and a transition from SDT to non-SDT. In scenario 500, base station 104 includes CU 172 and DU 174. CU 172 includes CU-CP 172A and CU-UP 172B. In scenario 500A, UE 102 initially operates 502 in an inactive state with SDT configured, similar to event 402 or 436. Then, UE 102 performs 592 a small data transfer process with base station 104, similar to event 492 or 493.

[0148] During the small data transfer process 592, the CU-CP 172A determines whether to transition the UE 102 to a connected state, for example, based on the UL or DL ​​data activity of the UE 102. In some implementations, the UE 102 sends 503 a non-SDT indication as a message or within a message to the DU 174 to indicate that non-SDT UL data is available or to request a transition to a connected state. In some implementations, the UE 102 sends 503 a non-SDT indication to the DU 174 on radio resources configured in the CG configuration (or CG-SDT configuration) for SDT. In other implementations, the UE 102 uses the C-RNTI to receive a dynamic uplink grant from the DU 174 on the PDCCH and sends 503 a non-SDT indication to the DU 174 on radio resources configured in the dynamic uplink grant. Then, the DU 174 sends 505 a UL RRC messaging message including a non-SDT indication to the CU-CP 172A.

[0149] In some implementations, CU-CP 172A determines to transition UE 102 to a connected state in response to or based on a non-SDT indication. In other implementations, CU-UP 172B receives DL data from CN 110, and in response to receiving the DL data, sends 507 a DL data notification (e.g., a DL data notification message) to CU-CP 172A to indicate that the DL data is available for transmission. In further implementations, CU-CP 172A determines to transition UE 102 to a connected state in response to or based on a DL data notification. In yet other implementations, CU-CP 172A determines to transition UE 102 to a connected state based on a measurement result received from UE 102. In other implementations, CU-CP 172A receives DL data (e.g., a NAS message) from CN 110, and in response to receiving the DL data, determines to transition UE 102 to a connected state.

[0150] In some implementations, UL data and DL data are associated with radio bearers (e.g., SRBs and / or DRBs). For example, the UL data includes an RRC message or a NAS message associated with the SRB. In another example, the UL data includes an IP packet associated with the DRB. In some implementations, the UE 102 may include the ID of the radio bearer in a message with a non-SDT indication. Therefore, the CU-CP 172A may determine whether to transition the UE 102 to a connected state based on the ID. For example, if the radio bearer ID identifier is not eligible for SDT, the CU-CP 172A determines to transition the UE 102 to a connected state. Otherwise, the CU-CP 172A determines not to transition the UE 102 to a connected state.

[0151] In some implementations, UE 102 includes data volume information for UL data in a message including a non-SDT indication. Thus, CU-CP 172A may determine whether to cause UE 102 to transition to a connected state based on the data volume information. In some implementations, the data volume information includes the total data volume of UL data, and UE 102 may quantize or round the total data volume to a value for the data volume information. In another implementation, the data volume information includes the data volume of each of the radio bearers, and UE 102 may quantize or round the data volume to a value for the data volume information. For example, if the total data volume is higher than a predetermined threshold, CU-CP 172A determines to cause UE 102 to transition to a connected state. Otherwise, CU-CP 172A may determine not to cause UE 102 to transition to a connected state. In another example, if the data volume for a particular radio bearer is higher than a predetermined threshold, CU-CP 172A determines to cause UE 102 to transition to a connected state. Otherwise, CU-CP 172A determines not to cause UE 102 to transition to a connected state. In yet another example, if the total data amount is above a predetermined threshold and the data amount for a specific radio bearer is above another predetermined threshold, the CU-CP 172A determines to transition the UE 102 to the connected state. Otherwise, the CU-CP 172A determines not to transition the UE 102 to the connected state.

[0152] Typically, each of events 506, 508, 510, and 512 is similar to Figure 3 Events 306, 308, 310, and 312 of the present invention are described in detail below, except for events 306, 308, 310, and 312 that occur when UE 102 is in an inactive state and as described below. In response to determining to transition UE 102 to a connected state, or thereafter, CU-CP 172A sends 506 a UE context request message (e.g., a UE context establishment request message or a UE context modification request message) to DU 174. In response, DU 174 sends 508 a UE context response message (e.g., a UE context establishment response message or a UE context modification response message) to CU-CP 172A. In some implementations, DU 174 includes a non-SDT DU configuration (i.e., a first non-SDT DU configuration) in the UE context response message. After receiving the UE context response message, CU-CP 172A sends 510 a CU-to-DU message including an RRC resume message (e.g., an RRCResume message or an RRCConnectionResume message) to DU 174. Then, the DU 174 sends 512 an RRC resume message to the UE 102 .

[0153] In some implementations, DU 174 sends 512 one or more PDUs including an RRC recovery message to UE 102. The PDU may be a MAC PDU or an RLC PDU. In some implementations, the CU to DU message is a DL RRC messaging message or a UE context modification request message. In some cases where the message is a UE context modification request message, in response, DU 174 sends a UE context modification response message to CU-CP 172A. In response to the RRC recovery message, UE 102 transitions 513 to a connected state and sends 514 an RRC recovery completion message (e.g., an RRCResumeComplete message or an RRCConnectionResumeComplete message) to DU 174. In the case where the UE context response message includes a non-SDT DU configuration, CU-CP 172A includes the non-SDT DU configuration in the RRC recovery message. DU 174 sends 516 a DU to CU message including an RRC recovery completion message to CU-CP 172A.

[0154] After determining to transition the UE 102 to the connected state, the CU-CP 172A sends 517 a bearer context request message (e.g., a bearer context setup request message or a bearer context modification request message) to the CU-UP 172B to instruct the CU-UP 172B to resume all suspended radio bearers of the UE 102. In response, the CU-UP 172B resumes all suspended radio bearers of the UE 102 and sends 519 a bearer context response message (e.g., a bearer context setup response message or a bearer context modification response message) to the CU-CP 172A. In some implementations, the CU-CP 172A sends 517 the bearer context request message after sending 506 a UE context request message, receiving 508 a UE context response message, sending 510 a CU to DU message, or receiving 516 a DU to CU message. In the event that CU-CP 172A determines that the radio bearers of UE 102 are not suspended when determining to transition UE 102 to the connected state, CU-CP 172A does not send the bearer context request message 517 to CU-UP 172B.

[0155] In some implementations, CU-CP 172A includes an indication indicating that DU 174 generates a non-SDT configuration in the UE context request message at event 506, and DU 174 includes the first non-SDT DU configuration in the UE context response message at event 508 in response to the indication. In other implementations, CU-CP 172A stores a non-SDT DU configuration (i.e., a second non-SDT DU configuration) used by a DU (e.g., DU 174 or another DU or base station) to communicate with UE 102. UE 102 may also store the second non-SDT DU configuration. In such a case, CU-CP 172A includes the second non-SDT DU configuration in the UE context request message, and DU 174 includes the first non-SDT DU configuration in the UE context response message in response to receiving the second non-SDT DU configuration. In some implementations, the first non-SDT DU configuration augments or replaces the second non-SDT DU configuration. Examples and implementations for the first non-SDT DU configuration and the second non-SDT DU configuration are similar to the non-SDT DU configuration described above. In some implementations, DU 174 sends an additional DU to CU message (e.g., UE context modification required message) including the first non-SDT DU configuration to CU-CP 172A instead of including the first non-SDT DU configuration in the UE context response message.

[0156] After transitioning to the connected state, the UE 102 communicates 518 UL data and / or DL ​​data with the CU-CP 172A and / or CU-UP 172B via the DU 174 using the non-SDT configuration. Depending on the implementation, the UL data includes UL data that triggers the UE to send a non-SDT indication and / or new UL data available for transmission. In a further implementation, the DL data includes DL data received from the CN 110 as described above and / or new DL data received from the CN 110. In the case where the RRC recovery message includes the first non-SDT DU configuration, the UE 102 communicates 518 with the DU 174 using the first non-SDT DU configuration. In some cases where the first non-SDT DU configuration does not completely replace the second non-SDT DU (i.e., the UE 102 does not release the second non-SDT DU configuration in response to the RRC resume message), the UE 102 communicates 518 with the DU 174 using configuration parameters in the second non-SDT DU configuration that are not extended by the first non-SDT DU configuration.

[0157] In some implementations, DU 174 does not provide the first non-SDT DU configuration to CU-CP 172A in the UE context response message and the attach DU to CU message. In such a case, the RRC resume message does not include the first non-SDT configuration, and UE 102 and DU 174 communicate 518 with each other using the second non-SDT DU configuration.

[0158] In some implementations, in response to an RRC recovery message or transitioning to a connected state, the UE 102 releases the SDT configuration (e.g., SDT CU configuration, SDT DU configuration, and / or CG-SDT configuration). In some implementations, in response to transitioning the UE 102 to a connected state, receiving 510 a CU to DU message, or sending 510, 512 an RRC recovery message, or thereafter, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration. In other implementations, in response to receiving an acknowledgment (e.g., RLC acknowledgment or HARQ acknowledgment) for a PDU including an RRC recovery message, or thereafter, the base station 104 releases the SDT configuration. In yet other implementations, in response to transmitting 506 a UE context request message or transmitting 508 a UE context response message, or thereafter, the base station 104 (e.g., CU-CP 172A and / or DU 174) releases the SDT configuration.

[0159] In other implementations, in response to receiving the RRC recovery message or transitioning to the connected state, the UE 102 retains the SDT configuration (e.g., SDT CU configuration, SDT DU configuration, and / or CG-SDT configuration). In some implementations, when operating in the connected state, the UE 102 avoids using the SDT configuration to communicate with the base station 104 (e.g., transmitting 514 an RRC recovery complete message and / or transmitting 518 data). In other implementations, when operating in the connected state, the UE 102 uses the SDT configuration to communicate with the base station 104 (e.g., transmitting 514 an RRC recovery complete message and / or transmitting 518 data).

[0160] In some implementations, in response to or after transitioning the UE 102 to the connected state or sending the RRC recovery message, the base station 104 retains the SDT configuration. In some implementations, the base station 104 avoids using the SDT configuration to communicate with the UE 102 operating in the connected state (e.g., transmitting 514 the RRC recovery complete message and / or transmitting 518 data). In other implementations, the base station 104 uses the SDT configuration to communicate with the UE 102 operating in the connected state (e.g., transmitting 514 the RRC recovery complete message and / or transmitting 518 data).

[0161] In some implementations, the non-SDT indication message is in an RRC message (e.g., a UEAssistanceInformation message or a new RRC message). In some such implementations, the UE 102 continues to perform 518 data communication with the base station 104 after sending the non-SDT indication. In some implementations, the UE 102 sends a ULMAC PDU including a non-SDT indication to the CU-CP 172A via DU 174. In some implementations, in addition to the non-SDT indication, the UE 102 also includes data in the UL MAC PDU. In other implementations, the UE avoids including the data in the UL MAC PDU. In some implementations, the UE 102 sends a non-SDT indication to the CU-CP 172A via DU 174 and SRB1. In such an implementation, in response to determining to send a non-SDT indication, the UE 102 avoids reestablishing the UE PDCP entity for SRB1. UE 102 generates an UL PDCP PDU including a non-SDT indication using the UE PDCP entity, and sends 503, 505 the UL PDCP PDU to CU-CP 172A via DU 174. Then, UE 102 receives 512 a DL PDCP PDU including an RRC recovery message using the UE PDCP entity without reestablishing the UE PDCP entity. CU-CP 172A receives 505 the UL PDCP PDU using the CU-CP PDCP entity. In response to receiving the non-SDT indication, CU-CP 172A avoids reestablishing the CU-CP PDCP entity for SRB1. CU-CP 172A generates a DL PDCP PDU using the CU-CP PDCP entity, and sends 510, 512 the DL PDCP PDU to UE 102 via DU 174 and SRB1. The UE 102 generates a UL PDCP PDU including an RRC recovery complete message using the UE PDCP entity, and transmits 514, 516 the UL PDCP PDU to the CU-CP 172A via DU 174 and SRB1. The CU-CP 172A receives 514, 516 the UL PDCP PDU from the UE 102 via DU 174 using the CU-CP PDCP entity. In such an implementation, the UE 102 and the CU-CP 172A transmit the PDCP PDU via SRB1 without reestablishing the UE PDCP entity and the CU-CP PDCP entity.

[0162] In other implementations, the non-SDT indication is in an RRC recovery request message (e.g., an RRCResumeRequest message or an RRCResumeConnectionRequest message). In some such implementations, the UE 102 stops 518 data communication with the base station 104 to send the non-SDT indication. In some implementations, the UE 102 sends the non-SDT indication to the CU-CP 172A via the DU 174 and SRB0. In some implementations, the UE 102 reestablishes the UE PDCP entity in response to determining to send a non-SDT indication. After reestablishing the UE PDCP entity, the UE 102 receives 512 a DL PDCP PDU using the UE PDCP entity. Similarly, after receiving the non-SDT indication, the CU-CP 172A reestablishes the CU-CP PDCP entity. After re-establishing the CU-CP PDCP entity, the CU-CP 172A generates DL PDCP PDUs using the CU-CP PDCP entity and transmits 510, 512 the DL PDCP PDUs to the UE 102 via DU 174 and SRB1. After re-establishing the UE PDCP entity, the UE 102 generates UL PDCP PDUs including an RRC recovery complete message using the UE PDCP entity and transmits 514, 516 the UL PDCP PDUs to the CU-CP 172A via DU 174 and SRB1. After re-establishing the CU-CP PDCP entity, the CU-CP 172A receives 514, 516 UL PDCP PDUs from the UE 102 via DU 174 using the CU-CP PDCP entity.

[0163] Prior to performing 592 the small data transfer procedure, the UE 102 operating 502 in the inactive state starts or restarts a first UE CG-SDT timer (e.g., CG-SDT-TAT), such as for Figure 3 and Figure 4 Described. In some implementations, in response to receiving a timing advance command from DU 174 during the small data transfer process 592, UE 102 starts or restarts a first UE CG-SDT timer. In some implementations, in response to receiving 512 to the RRC resume message, or thereafter, UE 102 maintains (e.g., keeps running or does not stop, start or restart) the first UE CG-SDT timer (e.g., CG-SDT-TAT). In other implementations, in response to receiving 512 to the RRC resume message, or thereafter, UE 102 stops the first UE CG-SDT timer.

[0164] Similarly, in some implementations, the DU 174 runs a first DU CG-SDT timer for the UE 102 operating 502 in the inactive state, such as for Figure 3 and Figure 4 Described. In some implementations, in response to sending (not shown) a timing advance command to UE 102, DU 174 starts or restarts a first DU CG-SDT timer. In some implementations, in response to receiving 506 a UE context request message, sending 508 a UE context response message, or sending 512 an RRC recovery message, or thereafter, DU 174 maintains (e.g., keeps running or does not stop, start, or restart) a first DU CG-SDT timer. In other implementations, in response to receiving 506 a UE context request message, sending 508 a UE context response message, or sending 512 an RRC recovery message, or thereafter, DU 174 stops the first DU CG-SDT timer. In some cases where the first DU CG-SDT timer expires, DU 174 releases the CG-SDT configuration. In other cases where the first DU CG-SDT timer expires, DU 174 retains the CG-SDT configuration and avoids receiving or attempting to receive UL transmissions (e.g., MAC PDUs) on CG resources. In some such cases, the DU 174 releases the CG resources or determines that the CG resources are invalid.

[0165] In some implementations, the UE 102 in an inactive state runs a second UE CG-SDT timer during the 592 small data transfer process, as described for process 492. In some implementations in which the second UE CG-SDT timer is running, in response to receiving 512 to an RRC recovery message or transitioning 513 to a connected state, or thereafter, the UE 102 stops the second UE CG-SDT timer. In some implementations, in response to receiving 512 to an RRC recovery message or transitioning 513 to a connected state, or thereafter, the UE 102 maintains the second UE CG-SDT timer running. In some implementations, the UE 102 receives an RRC setup message (e.g., an RRCSetup message) instead of an RRC recovery message. In response to receiving the RRC setup message, or thereafter, the UE 102 stops the second UE CG-SDT timer and sends an RRC setup complete message to the CU-CP 172A via the DU 174.

[0166] Similarly, depending on the implementation, DU 174 runs a second DU CG-SDT timer during the 592 small data transmission process. In some implementations, DU 174 starts or restarts the second DU CG-SDT timer when or after receiving a PUSCH transmission on the radio resources configured in the CG-SDT configuration from UE 102. In further implementations, when the second DU CG-SDT timer is running, DU 174 sends a PDCCH using the C-RNTI. While the second DU CG-SDT timer is running, DU 174 stops the second DU CG-SDT timer in response to receiving 506 a UE context request message, sending 508 a UE context response message, or sending 512 an RRC recovery message, or thereafter. In other implementations, DU 174 maintains the second DU CG-SDT timer in response to receiving 506 a UE context request message, sending 508 a UE context response message, or sending 512 an RRC recovery message, or thereafter. The DU 174 sends a PDCCH (DCI on PDCCH) to the UE 102 operating in the connected state using the C-RNTI regardless of the second DU CG-SDT timer (eg, running, expired, or stopped).

[0167] In some implementations, at a later time, the base station 104 performs 590 a non-SDT resource (re)configuration procedure with the UE 102 and performs 594 an SDT configuration procedure with the UE 102, similar to the procedures 390 and 394, respectively. The UE 102 transitions 536 to the inactive state in response to receiving the RRC release message in the procedure 594. Depending on the implementation, after transitioning to the inactive state, the UE 102 in the inactive state performs 593 a small data transfer procedure with the base station 104 and / or performs 595 an SDT completion procedure with the base station 104, similar to the procedures 492 and 494, respectively.

[0168] Next reference Figure 5B , scenario 500B is generally similar to scenario 500A, except that UE 102 initiates an RRC recovery procedure instead of performing 592 a small data transfer procedure. The differences between scenarios 500B and 500A are discussed below.

[0169] In response to initiating the RRC recovery process, the UE 102 in the inactive state sends 542 an RRC recovery request message to the DU 174, which in turn sends 544 an initial UL RRC messaging message including an RRC recovery request message (e.g., an RRCResumeRequest message or an RRCConnectionResumeRequest message) to the CU-CP 172A. In response to receiving the RRC recovery request message, the CU-CP 172A determines to transition the UE 102 to the connected state. In response to or after determining to transition the UE 102 to the connected state, the CU-CP 172A transitions the UE 102 to the connected state as described for scenario 500A.

[0170] In some implementations, the UE 102 generates a UL MAC PDU including the RRC recovery request message and sends 542 the UL MAC PDU to the DU 174. In further implementations, the UE 102 sends 542 the UL MAC PDU to the DU 174 on the radio resources configured for the SDT in the CG configuration. In other implementations, the UE 102 performs a random access procedure to send the UL MAC PDU, similar to event 404.

[0171] In some implementations, the UE 102 initiates an RRC recovery procedure to send non-SDT data (i.e., data that is not eligible for SDT). More specifically, an upper protocol layer (e.g., a NAS layer) of the UE 102 requests an RRC layer (e.g., RRC 214) of the UE 102 to initiate an RRC recovery procedure. In other implementations, the UE 102 receives a paging message from the DU 174 and initiates an RRC recovery procedure in response to the paging message. In some implementations, the RRC layer (e.g., RRC 214) initiates an RRC recovery procedure in response to the paging message. In yet other implementations, the UE 102 detects when a periodic RAN Notification Area Update (RNAU) timer expires, and initiates an RRC recovery procedure in response to the expiration of the periodic RNAU timer. In some implementations, the RRC layer (e.g., RRC 214) starts or restarts an RNAU timer, maintains the RNAU timer, and initiates an RRC recovery procedure in response to the expiration of the RNAU timer.

[0172] Next reference Figure 6, scenario 600 depicts a small data transfer, similar to scenario 400. Except for events 607 and 609, events 602, 604, 606, 608, 610, 612, 614, 615, 616, 618, 694, 636 are similar to events 402, 404, 406, 408, 410, 412, 414, 415, 416, 418, 494, 436. Figure 4 Examples and implementations can be applied to Figure 6 The following describes Figure 4 and Figure 6 The difference between.

[0173] In scenario 600, UE 102 initially operates 602 in an inactive state with an SDT configuration configured by base station 104, such as for Figure 3 or Figure 4 In some implementations, the SDU configuration includes a CG-SDT configuration. In some such cases, the UE 102 discards the CG-SDT configuration because the base station 106 does not configure the CG-SDT configuration for the UE 102, i.e., the CG-SDT configuration is invalid.

[0174] In response to receiving 606 the UL RRC message, or thereafter, the CU-CP 172A sends 607 a retrieve UE context request message to the base station 104. In response, the base station 104 sends 609 a retrieve UE context response message to the CU-CP 172A. After receiving the retrieve UE context response message, the CU-CP 172A sends 608 a UE context establishment request message to the DU 174, receives 610 a UE context establishment response message from the DU 174, and sends 612 an RRC recovery message to the DU 174. The CU-CP 172A sends 612 a bearer context establishment request message to the CU-UP 172B to request the CU-UP 172B to establish a bearer context for the SDT DRB configured in the SDT configuration. In response, the CU-UP 172B establishes a bearer context for the SDT DRB and sends 614 a bearer context establishment response message to the CU-CP 172A to confirm that the bearer context for the SDT DRB has been established.

[0175] In some implementations, the base station 104 includes the SDT configuration in the retrieval UE context response message. In some cases where the SDT configuration includes a CG-SDT configuration, the base station 104 excludes the CG-SDT configuration from the SDT configuration. Alternatively, the CU-CP 172A still includes the CG-SDT configuration from the SDT configuration. In some implementations, when the CU-CP 172A receives the CG-SDT configuration, the CU-CP 172A discards the CG-SDT configuration. In further implementations, such as when the CU-CP 172A does not support incremental configuration, the CU-CP 172A discards the SDT configuration. In some cases where the CU-CP 172A supports incremental configuration, when the CU-CP 172A determines that the UE is transitioned to an inactive state at the SDT completion process 694 similar to process 494, the CU-CP 172A takes the SDT configuration (e.g., the first SDT configuration) into account. In other implementations, the CU-CP 172A avoids including the SDT configuration in the retrieval UE context request message.

[0176] Next, refer to Figures 7 to 16 Several example methods that can be implemented in a UE, a base station, a DU of a base station, or a CU of a base station are discussed. Each of these methods can be implemented using processing hardware such as one or more processors to execute instructions stored on a non-transitory computer-readable medium such as a computer memory.

[0177] First reference Figure 7 , the method 700 can be implemented in a suitable RAN node such as a base station, and includes determining whether to generate an RRC release message including an SDT configuration based on whether the UE and the RAN node support RA-SDT communication. For clarity, the method 700 is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0178] At block 702, a RAN node communicates with a UE 102 (e.g., Figures 3 to 6 At block 704, while communicating with the UE 102, the RAN node determines to transition the UE 102 to an inactive or idle state or to maintain the UE 102 in an inactive or idle state (e.g., Figures 3 to 6At block 706, the base station 104 determines whether the UE 102 and a RAN node (such as the base station 104) support RA-SDT communications.

[0179] In some implementations, a RAN node (such as a base station 104) of the RAN 105 receives a UE capability IE (e.g., a UE-EUTRA-Capability IE, a UE-NR-Capability IE, or a UE-6G-Capability IE) of the UE 102. Depending on the implementation, the RAN node receives the UE capability IE from the UE 102, the base station 104, or the CN 110 (e.g., an AMF). In other implementations, the RAN node stores the UE capability IE and later receives a UE capability identifier that identifies the UE capability IE. Similarly, depending on the implementation, the RAN node receives an identifier from the UE 102, the base station 104, or the CN 110 (e.g., an AMF). If the UE capability IE includes an RA-SDT support indication, the RAN node determines that the UE 102 supports RA-SDT communication. Otherwise, the RAN node determines that the UE 102 does not support RA-SDT communication.

[0180] In a further implementation, the RAN node stores a flag indicating whether the RAN node supports SDT that relies on a random access procedure, such as RA-SDT communication. If the flag is set to a first value, the RAN node determines that the RAN node supports RA-SDT communication. Otherwise (e.g., the flag is set to a second value or the flag is not present), the RAN node determines that the node does not support RA-SDT communication. In yet other implementations, the RAN node is preconfigured to support RA-SDT communication. In such a case, the RAN node only determines whether the UE 102 supports RA-SDT communication.

[0181] In implementations where the UE 102 and the RAN node support RA-SDT communication, the flow continues to block 708. At block 708, the RAN node generates an SDT configuration including configurations common to multiple forms of SDT (i.e., an SDT common configuration), and further generates an RRC release message (e.g., Figures 3 to 6Events 332 / 334 / 394, 432 / 434 / 494, 594, and 694 of SDT). In some implementations, the RAN node uses the SDT common configuration to configure which DRBs are eligible for SDT and / or RA-SDT. In a further implementation, the SDT configuration includes a list of DRBs that support SDT. The process then continues to box 712. In some implementations, at box 708, the RAN node includes a RA-SDT specific configuration (e.g., a RA-SDT indication or a RA-SDT enable indication) in the SDT configuration to configure the UE 102 to enable RA-SDT communication. In other implementations, at box 708, the RAN node does not include a RA-SDT specific configuration, an RRC release message. In such an implementation, when the UE 102 receives the SDT common configuration, the UE 102 determines that the RAN node is configuring RA-SDT communication for the UE 102.

[0182] In implementations where the UE 102 or RAN node does not support RA-SDT communications, flow continues to block 710. At block 710, the RAN node generates an RRC release message (e.g., Figures 3 to 6 The flow then continues to block 712. At block 712, the RAN node sends an RRC release message to the UE 102 to cause the UE to transition to or remain in an inactive or idle state (e.g., Figures 3 to 6 Events 334 / 394, 434 / 494, 594 and 694).

[0183] In some implementations, in addition to whether the UE 102 and the RAN node support RA-SDT communication, the RAN node further determines whether to configure RA-SDT communication based on one or more conditions. In some implementations, the one or more conditions include whether the RAN node configures a specific DRB for the UE 102. For example, if the UE 102 and the RAN node support RA-SDT communication and the RAN node configures the specific DRB, the RAN node configures RA-SDT for the UE 102 at box 708. Otherwise, the RAN node avoids configuring RA-SDT for the UE 102 at box 710. For example, the specific DRB can be a first DRB associated with a first PDU session or a first QoS flow. In another example, if the UE 102 and the RAN node support RA-SDT communication and the RAN node does not configure the specific DRB, the RAN node configures RA-SDT for the UE 102 at box 708. Otherwise, the RAN node avoids configuring RA-SDT for the UE 102 at box 710. As a further example, the specific DRB may be a second DRB associated with a second PDU session or a second QoS flow.

[0184] Next reference Figure 8 The method 800 may be implemented in a suitable RAN node such as a base station and includes configuring RA-SDT for a UE. For clarity, the method 800 is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0185] At block 802, a RAN node communicates with a UE 102 (e.g., Figures 3 to 6 At block 804, the RAN node decides to configure RA-SDT for UE 102 when communicating with UE 102 (e.g., Figures 3 to 6 At block 806, in some implementations, the RAN node generates an SDT configuration (e.g., Figures 3 to 6 In other implementations, the RAN node generates the SDT configuration without the RA-SDT configuration. At block 808, the first RAN node sends an RRC release message including the generated SDT configuration to the UE (e.g., Figures 3 to 6 Events 334 / 394, 434 / 494, 594 and 694).

[0186] Next reference Fig.9A Method 900A is generally similar to method 700, except that the RAN node determines how to generate the RRC release message based on whether the UE and the RAN node support CG-SDT communication. Specifically, blocks 902, 904, 910, and 912 are similar to Figure 7 702, 704, 710 and 712 are similar. Therefore, Figure 7 The examples and implementations described in also apply to Fig.9A .

[0187] At blocks 902 and 904, the RAN node performs Figure 7 At block 906, the RAN node determines whether the UE 102 and the RAN node (such as the base station 104) support SDT, such as CG-SDT communication, that relies on resources previously allocated to the UE. In some implementations, the RAN node receives a UE capability IE (e.g., a UE-EUTRA-Capability IE, a UE-NR-Capability IE, or a UE-6G-Capability IE) of the UE 102, as described above with respect to Figure 7 If the UE capability IE includes a CG-SDT support indication (i.e., an indication indicating support for CG-SDT communications), the RAN node determines that the UE 102 supports CG-SDT communications. Otherwise (i.e., if the UE capability IE does not include a CG-SDT support indication), the RAN node determines that the UE 102 does not support CG-SDT communications. In a further implementation, the RAN node stores a flag indicating whether the node supports CG-SDT communications, generally similar to the above description of Figure 7 908. In an implementation where the UE 102 and the RAN node do support CG-SDT communication, the flow continues to block 909. In an implementation where the UE 102 and the RAN node do not support CG-SDT communication, the flow continues to block 910.

[0188] Next reference Fig. 9B , method 900B is substantially similar to method 900A, except that the RAN node determines how to generate the RRC release message based on whether the UE supports CG-SDT communication for the UL carrier frequency. Fig.9A The examples and implementations described in also apply to Fig. 9B .

[0189] At block 903, the RAN node communicates with the UE 102 via the cell on a DL carrier frequency and an UL carrier frequency (e.g., Figures 3 to 6 At block 905, the RAN node determines whether the UE 102 supports CG-SDT communications for the UL carrier frequency. In implementations where the UE 102 does support CG-SDT communications for the UL carrier frequency, the flow continues to block 908. In implementations where the UE 102 does not support CG-SDT communications for the UL carrier frequency, the flow continues to block 910. At block 913, the RAN node sends an RRC release message to the UE 102 via the cell to cause the UE 102 to transition to or remain in an inactive or idle state (e.g., Figures 3 to 6 Events 334 / 394, 434 / 494, 594 and 694).

[0190] In some implementations, the RAN node sends the RRC release message to the UE 102 on a DL carrier frequency. Depending on the implementation, the DL carrier frequency and the UL carrier frequency may belong to the first frequency band. In the case where the cell is a time division duplex (TDD) cell, the DL carrier frequency and the UL carrier frequency are the same carrier frequency. In the case where the cell is a frequency division duplex (FDD) cell, the DL carrier frequency and the UL carrier frequency are different carrier frequencies.

[0191] In a further implementation, the UE capability IE indicates whether the UE 102 supports CG-SDT communication, FDD operation and / or TDD operation for one or more frequency bands. The frequency band may be within frequency range 1 (FR1), frequency range 2-1 (FR2-1) and / or frequency range 2-2 (FR2-2). In some implementations, the UE capability includes a CG-SDT support indication for each frequency band supported by the UE 102. In other implementations, the UE 102 supports multiple frequency bands, and the UE 102 only supports CG-SDT communication for a portion of the multiple frequency bands. In such an implementation, the UE capability includes a CG-SDT support indication for each frequency band for which the UE 102 supports CG-SDT communication.

[0192] In some implementations, the UE 102 supports CG-SDT communication for FR1, FR2-1, and / or FR2-2, and the UE capability IE includes a CG-SDT support indication for FR1, FR2-1, and / or FR2-2, respectively. In a further implementation, the UE 102 supports CG-SDT communication for FR1 and does not support CG-SDT communication for FR2-1 and / or FR2-2. In such an implementation, the UE capability IE includes a CG-SDT support indication for FR1 and does not include a CG-SDT support indication for FR2-1 and / or FR2-2.

[0193] In some implementations, the UE 102 supports CG-SDT communication for FDD operation and / or TDD operation, and the UE capability IE includes a CG-SDT support indication for FDD operation and / or TDD operation. In yet other implementations, the UE 102 supports CG-SDT communication for one of FDD operation or TDD operation, and does not support CG-SDT communication for the other. In such an implementation, the UE capability IE includes a CG-SDT support indication for one of FDD operation and TDD operation, and does not include a CG-SDT support indication for the other.

[0194] In some implementations, at block 905, the RAN node determines whether the UE 102 supports CG-SDT communications for the UL carrier frequency by determining whether the UE 102 supports CG-SDT communications for the first frequency band. In implementations where the cell is a TDD cell, the RAN node determines whether the UE 102 supports CG-SDT communications for TDD operation. In implementations where the cell is an FDD cell, the RAN node determines whether the UE 102 supports CG-SDT communications for FDD operation. Similarly, when the first frequency band is within FR1, FR2-1, or FR2-2, the RAN node determines whether the UE 102 supports CG-SDT communications for FR1, FR2-1, or FR2-2, respectively.

[0195] In yet a further implementation, at block 905, the RAN node determines whether the RAN node supports CG-SDT communications for the UL carrier frequency or the first frequency band, similar to Fig.9A If the RAN node does support CG-SDT communications for the UL carrier frequency or the first frequency band, the process continues to block 908. Otherwise, if the RAN node does not support CG-SDT communications for the UL carrier frequency or the first frequency band, the process continues to block 910.

[0196] Next reference Fig. 10A, the method 1000A can be implemented in a suitable RAN node such as a base station, and includes determining whether to generate an RRC release message including an SDT configuration and a CG-SDT configuration and / or a RA-SDT configuration based on whether the UE and the RAN node support CG-SDT and RA-SDT communication. For clarity, the method 1000A is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0197] At block 1002, a RAN node communicates with a UE 102 (e.g., Figures 3 to 6 At block 1004, the RAN node determines to transition the UE 102 to an inactive or idle state, or to maintain the UE 102 in an inactive or idle state (e.g., Figures 3 to 6 At box 1006, the RAN node determines whether the UE 102 and the RAN node (such as the base station 104) support CG-SDT communication.

[0198] In implementations where the UE 102 and the RAN node support CG-SDT communications, flow continues to block 1008. At block 1008, the RAN node includes the SDT common configuration and the CG-SDT configuration in the SDT configuration (e.g., Figures 3 to 6 332 / 334 / 394, 432 / 434 / 494, 594 and 694). Flow then continues to block 1010. In implementations where the UE 102 and the RAN node do not support CG-SDT communications, flow instead continues directly to block 1010. At block 1010, the RAN node determines whether the UE 102 and the RAN node support RA-SDT communications.

[0199] In implementations where the UE 102 and the RAN node support RA-SDT communications, flow continues to block 1012. At block 1012, the RAN node includes the RA-SDT configuration in the SDT configuration (e.g., Figures 3 to 6 At block 1014, the RAN node generates an RRC release message (e.g., Figures 3 to 61014). The flow then continues to block 1018. In implementations where UE 102 and the RAN node do not support RA-SDT communications, the flow instead continues to block 1016. At block 1016, the RAN node generates an RRC release message without an SDT configuration (e.g., Figures 3 to 6 1018). At block 1018, the RAN node sends an RRC release message to the UE 102 to cause the UE 102 to transition to or remain in an inactive or idle state (e.g., Figures 3 to 6 Events 334 / 394, 434 / 494, 594 and 694).

[0200] Next reference Fig. 10B , method 1000B may be implemented in a suitable RAN node such as a base station, and includes determining whether to generate an RRC release message including an SDT configuration and a CG-SDT configuration and / or a RA-SDT configuration based on whether the UE and the RAN node support RA-SDT communication and whether the UE supports CG-SDT communication for the carrier frequency. For clarity, method 1000B is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0201] At block 1003, the RAN node communicates with the UE 102 via the cell on a DL carrier frequency and an UL carrier frequency (e.g., Figures 3 to 6 At block 1004, the RAN node determines to transition the UE 102 to an inactive or idle state, or to maintain the UE 102 in an inactive or idle state (e.g., Figures 3 to 6 At block 1005, the RAN node determines whether the UE 102 supports CG-SDT communications for the UL carrier frequency. In implementations where the UE 102 supports CG-SDT communications for the UL carrier frequency, the flow continues to block 1008. At block 1008, the RAN node includes the SDT common configuration and the CG-SDT configuration in the SDT configuration (e.g., Figures 3 to 6102. The process then continues to block 1010. In implementations where the UE 102 does not support CG-SDT communications for the UL carrier frequency, the process instead continues directly to block 1010.

[0202] At block 1010, the RAN node determines whether the UE 102 and the RAN node (such as the base station 104) support RA-SDT communication. In implementations where the UE 102 and the RAN node support RA-SDT communication, the flow continues to block 1012. At block 1012, the RAN node includes the RA-SDT configuration in the SDT configuration (e.g., Figures 3 to 6 At block 1014, the RAN node generates an RRC release message (e.g., Figures 3 to 6 1014). The flow then continues to block 1019. In implementations where UE 102 and the RAN node do not support RA-SDT communications, the flow instead continues to block 1016. At block 1016, the RAN node generates an RRC release message without an SDT configuration (e.g., Figures 3 to 6 The process then continues to block 1019. At block 1019, the RAN node sends an RRC release message to the UE 102 via the cell to cause the UE 102 to transition to or remain in an inactive or idle state (e.g., Figures 3 to 6 Events 334 / 394, 434 / 494, 594 and 694).

[0203] Next reference Fig.11 , method 1100 is generally similar to method 700, except that the CU determines how to generate the RRC release message based on whether the UE and the DU support RA-SDT communication. Specifically, except for the contents summarized below, blocks 1102, 1104, 1108, 1110, and 1112 are generally similar to Figure 7 702, 704, 708, 710 and 712. Therefore, in Figure 7 The examples and implementations described in also apply to Fig.11 .

[0204] At blocks 1102 and 1104, in addition to communicating with UE 102 via DU 174, CU 172 performs communication with Figure 7 The network node functions similarly to that described in blocks 702 and 704 of FIG. Figure 7 Compared to box 706 of , at box 1106, CU 172 determines whether UE 102 and DU 174 support RA-SDT communication. In some implementations, due to the distributed base station architecture, CU 172 receives a DU to CU message from DU 174, indicating whether DU 174 supports RA-SDT communication. If the DU to CU message indicates that DU 174 supports RA-SDT communication, CU 172 determines that DU 174 supports RA-SDT communication. Otherwise, CU 172 determines that DU 174 does not support RA-SDT communication. In some implementations, the DU to CU message can be an existing interface management message, such as an F1 setup request message, a gNB-DU configuration update message, and / or a gNB-CU configuration update confirmation message. In other implementations, the DU to CU message can be a new interface management message.

[0205] In other implementations, the CU 172 stores a flag indicating whether the DU 174 supports RA-SDT communication, similar to Figure 7 In a further implementation, DU 174 is preconfigured to support RA-SDT communication. In such a case, CU 172 only determines whether UE 102 supports RA-SDT communication.

[0206] In implementations where UE 102 and DU 174 support RA-SDT communication, flow continues to block 1108, similar to block 708, except that CU 172 performs the functions. In some implementations, at block 1109, CU 172 includes the RA-SDT configuration in the SDT configuration. In implementations where UE 102 and DU 174 do not support RA-SDT communication, flow continues to block 1110, similar to block 710, except that CU 172 performs the functions. At block 1112, CU 172 sends an RRC release message to UE 102 via DU 174, similar to Figure 7 Frame 712.

[0207] Next reference Fig. 12A , method 1200A is substantially similar to method 900A, except that the CU determines how to generate the RRC release message based on whether the UE and the DU support CG-SDT communication. Specifically, except for the contents summarized below, blocks 1202, 1204, 1208, 1210, and 1212 are substantially similar to Fig.9A 902, 904, 908, 910 and 912. Therefore, in Fig.9A The examples and implementations described in also apply to Fig. 12A .

[0208] At blocks 1202 and 1204, in addition to communicating with UE 102 via DU 174, CU 172 performs communication with Fig.9A 1206, the CU 172 determines whether the UE 102 and the DU 174 support CG-SDT communication. In some implementations, due to the distributed base station architecture, the CU 172 receives a DU to CU message from the DU 174 indicating whether the DU 174 supports CG-SDT communication. If the DU to CU message indicates that the DU 174 supports CG-SDT communication, the CU 172 determines that the DU 174 supports CG-SDT communication. Otherwise, the CU 172 determines that the DU 174 does not support CG-SDT communication. In some implementations, the DU to CU message is an existing interface management message, such as an F1 setup request message, a gNB-DU configuration update message, and / or a gNB-CU configuration update confirmation message. In other implementations, the DU to CU message is a new interface management message.

[0209] In other implementations, CU 172 stores a flag indicating whether DU 174 supports CG-SDT communication, similar to Fig.9A In yet other implementations, DU 174 is preconfigured to support CG-SDT communication. In such a case, CU 172 only determines whether UE 102 supports CG-SDT communication.

[0210] In implementations where UE 102 and DU 174 do support CG-SDT communications, flow continues to block 1207. At block 1207, CU 172 obtains the CG-SDT configuration (e.g., Figures 3 to 6 At block 1208, CU 172 generates an SDT configuration including an SDT common configuration and a CG-SDT configuration, similar to block 908, except that CU 172 performs the functions. In an implementation where UE 102 and DU 174 do not support CG-SDT communication, the flow continues to block 1210, similar to block 910, except that CU 172 performs the functions. At block 1212, CU 172 sends an RRC release message to UE 102 via DU 174, similar to block 912.

[0211] Next reference Fig. 12B, method 1200B is substantially similar to method 900B, except that the CU determines how to generate the RRC release message based on whether the UE supports CG-SDT communication for the UL carrier frequency. Specifically, except for the contents summarized below, blocks 1203, 1204, 1208, 1210, and 1212 are substantially similar to Fig.9A 903, 904, 908, 910, and 913. Similarly, method 1200B is similar to method 1200A, where the boxes match. Fig. 9B and Fig. 12A The examples and implementations described in also apply to Fig. 12B .

[0212] At blocks 1203 and 1204, CU 172 performs Fig. 9B At block 1205, CU 172 determines whether UE 102 supports CG-SDT communication for the UL carrier frequency. In an implementation where UE 102 does support CG-SDT communication for the UL carrier frequency, the flow continues to blocks 1207 and 1208, similar to Fig. 12A In implementations where UE 102 does not support CG-SDT communications for the UL carrier frequency, the flow continues to block 1210, also similar to Fig. 12A At block 1212, CU 172 sends an RRC release message to UE 102 via DU 174, similar to Fig. 9B Block 913 of CG-SDT. In some implementations, the SDT configuration includes downlink control information (DCI) to schedule the time and frequency for dynamic scheduling and transmission. The UE 102 then receives and / or retrieves the configured resources based on the SDT configuration and / or the DCI. In other implementations, the UE 102 does not receive the DCI, but transmits on the time and / or frequency resources based on the CG-SDT configuration.

[0213] Next reference Fig.13A , method 1300A is substantially similar to method 1000A, except that the CU determines how to generate the RRC release message based on whether the UE and DU support CG-SDT and RA-SDT communication. Specifically, except for the contents summarized below, blocks 1302, 1304, 1308, 1312, 1314, 1316 and 1318 are substantially similar to Fig. 10A 1002, 1004, 1008, 1012, 1014, 1016 and 1018. Therefore, in Fig. 10A The examples and implementations described in also apply to Fig.13A .

[0214] At blocks 1302 and 1304, CU 172 performs Fig. 10A The network nodes described in blocks 1002 and 1004 in FIG. Fig. 10A Compared to block 1006 of FIG. 1 , at block 1306, CU 172 determines whether UE 102 and DU 174 support CG-SDT communication. In an implementation where UE 102 and DU 174 support CG-SDT communication, the flow continues to block 1307. At block 1307, CU 172 obtains a CG-SDT configuration (e.g., Figures 3 to 6 At block 1308, CU 172 includes the SDT common configuration and the CG-SDT configuration in the SDT configuration, similar to block 1006. In implementations where UE 102 and DU 174 do not support CG-SDT communication, the flow proceeds directly to block 1310.

[0215] and Fig. 10A Compared to block 1010 of FIG. 1 , at block 1310, CU 172 determines whether UE 102 and DU 174 support RA-SDT communication. In an implementation where UE 102 and DU 174 support RA-SDT communication, the flow continues to blocks 1312 and 1314, similar to Fig. 10A 1012 and 1014, except that CU 172 performs the described functions. In an implementation where UE 102 and DU 174 do not support RA-SDT communication, the flow continues to block 1316, also similar to Fig. 10A 1016 of the embodiment, except that CU 172 performs the functions described. At block 1318, CU 172 then sends an RRC release message to UE 102 via DU 174, similar to block 1018.

[0216] Next reference Fig. 13B , method 1300B is substantially similar to method 1000B, except that the CU determines how to generate the RRC release message based on whether the UE and DU support RA-SDT communication and whether the UE supports CG-SDT communication for UL frequency. Specifically, except for the contents summarized below, blocks 1303, 1304, 1308, 1312, 1314, 1316, and 1318 are substantially similar to Fig. 10B 1003, 1004, 1008, 1012, 1014, 1016, and 1019. Similarly, method 1300B is similar to method 1300A, where the boxes match. Fig. 10A and Fig.13A The examples and implementations described in also apply to Fig.13A .

[0217] At blocks 1303 and 1304, CU 172 performs functions similar to those of the network node described in blocks 1003 and 1004. At block 1305, CU 172 determines whether UE 102 supports CG-SDT communication for the UL carrier frequency. In implementations where UE 102 supports CG-SDT communication for the UL carrier frequency, the flow continues as follows. Fig.13A In implementations where UE 102 does not support CG-SDT communications for the UL carrier frequency, flow proceeds directly to block 1310.

[0218] At block 1310, CU 172 determines whether UE 102 and DU 174 support RA-SDT communication, such as Fig.13A In an implementation where UE 102 and DU 174 support RA-SDT communications, the flow continues to blocks 1312 and 1314, similar to Fig.13A In implementations where UE 102 and DU 174 do not support RA-SDT communications, flow continues to block 1316, also similar to Fig.13A At block 1318, CU 172 then sends an RRC release message to UE 102 via DU 174, similar to Fig. 10B Box 1019.

[0219] Next reference Fig.14A , method 1400A can be implemented in a DU of a suitable RAN node such as a base station, and determines whether to send a CG-SDT configuration based on whether CG-SDT resources are available for the UE in response to a request from the CU. For clarity, method 1400A is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0220] At block 1402, the DU 174 communicates with the UE 102 and the CU 172 (e.g., Figures 3 to 6 At block 1404, DU 174 receives a CU-to-DU message (e.g., Figures 3 to 6At block 1406, DU 174 determines whether CG-SDT resources are available for UE 102. In implementations where CG-SDT resources are available for UE 102, flow proceeds to block 1408. Otherwise, flow proceeds to block 1410. At block 1408, DU 174 sends a DU to CU message including the CG-SDT configuration to CU 172 (e.g., Figures 3 to 6 At block 1410, in response to the CU-to-DU message, DU 174 sends a DU-to-CU message without a CG-SDT configuration to CU 172 (e.g., Figures 3 to 6 Events 330 / 394, 430 / 494, 594, and 694). In some implementations, at block 1410, the DU 174 includes an indication in the DU to CU message that the UE 102 does not support CG-SDT communications. Depending on the implementation, the indication may be an IE, a field, or a cause value.

[0221] In some implementations, in response to the CU to DU message, DU 174 sends a DU to CU message to CU 172. In further implementations, the CU to DU message and the DU to CU message are a UE context modification request message and a UE context modification response message, respectively. In other implementations, the CU to DU message and the DU to CU message are a UE context establishment request message and a UE context establishment response message, respectively. In yet other implementations, the CU to DU message and the DU to CU message are a UE context modification request message and a UE context modification requirement message, respectively. In such an implementation, DU 174 sends a UE context modification response message to CU 172 in response to the UE context modification request message.

[0222] In some implementations, at block 1410, the DU 174 includes an indication in the DU to CU message that CG-SDT resources are unavailable. Depending on the implementation, the indication may be an IE, field, or cause value.

[0223] Next reference Fig. 14B , method 1400B can be implemented in a DU of a suitable RAN node such as a base station, and includes determining whether to send a CG-SDT configuration based on whether the UE and the DU support CG-SDT communication in response to a request from the CU. For clarity, method 1400B is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0224] At block 1402, the DU 174 communicates with the UE 102 and the CU 172 (e.g., Figures 3 to 6 At block 1404, DU 174 receives a CU-to-DU message (e.g., Figures 3 to 6 At block 1405, DU 174 determines whether UE 102 and DU 174 support CG-SDT communication.

[0225] In some implementations, DU 174 receives the UE capability IE of UE 102 from CU 172, and determines whether UE 102 supports CG-SDT communication based on the UE capability IE as described above. For example, in some implementations, the CU to DU message includes the UE capability IE. In another example, DU 174 receives another CU to DU message (e.g., UE context establishment request message, UE context modification request message, or UE context modification confirmation message) including the UE capability IE from CU 172.

[0226] In implementations where UE 102 and DU 174 support CG-SDT communications, flow proceeds to block 1408. Otherwise, flow proceeds to block 1410. At block 1408, DU 174 sends a DU-to-CU message including a CG-SDT configuration to CU 172 (e.g., Figures 3 to 6 At block 1410, in response to the CU-to-DU message, DU 174 sends a DU-to-CU message without a CG-SDT configuration to CU 172 (e.g., Figures 3 to 6 Events 330 / 394, 430 / 494, 594 and 694).

[0227] Next reference Fig.15 , the method 1500 may be implemented in a suitable base station and includes managing small data transmissions with a UE. For clarity, the method 1500 is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0228] At block 1502, the base station 104 determines that the UE 102 should operate in a state of a protocol for controlling radio resources in which the UE 102 is not connected to the RAN 105 (e.g., Figures 3 to 13B1504). The state is either an inactive state or an idle state, depending on the implementation. At block 1504, the base station 104 generates a message that causes the UE 102 to transmit small data according to the capabilities of the UE 102 (e.g., Figures 3 to 13B Depending on the implementation, the base station 104 generates a radio resource message based on at least whether the UE 102 supports a first type of SDT (such as RA-SDT) that depends on a random access procedure and / or a second type of SDT (such as CG-SDT) that depends on resources previously allocated to the UE 102. At block 1506, the base station 104 sends a radio resource message to the UE 102 ( Figures 3 to 13B 334 / 394, 434 / 494, 594, 694, 712, 808, 912 / 913, 1018 / 1019, 1112, 1212, 1318).

[0229] Next reference Fig.16 , the method 1600 may be implemented in a suitable DU and includes managing small data transmissions with the UE. For clarity, the method 1600 is discussed with specific reference to the UE 102, the base station 104, the RAN 105, the CU 172, and the DU 174.

[0230] At block 1602, DU 174 receives a message from CU 172 requesting SDT resources for UE 102 for an SDT type that relies on resources previously allocated to UE 102 (e.g., CG-SDT). Figures 3 to 6 , Fig.14A and Fig. 14B At block 1604, DU 174 determines whether to include an SDT-type configuration in the response message to CU 172 (e.g., Figures 3 to 6 , Fig.14A and Fig. 14BAt block 1606, DU 174 sends a response message to CU 172 (e.g., Figures 3 to 6 , Fig.14A and Fig. 14B Events 330 / 394, 430 / 494, 594, 694 and 1408 / 1410).

[0231] Next reference Fig.17A , method 1700A can be implemented in a suitable RAN node (e.g., base station 104 or DU 174) and includes managing small data transmission with UE. For clarity, method 1700A is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172 and DU 174.

[0232] At block 1702, the RAN node determines to enable RA-SDT for a cell. At block 1704, the RAN node includes a timer value and / or a data volume threshold in an SDT configuration (e.g., Figures 3 to 6 In some implementations, the SDT configuration is sdt-ConfigCommon, SDT-ConfigCommonSIB, or SDT-ConfigCommonSIB-r17. In further implementations, the time timer value is t319a or t319a-r17 value (e.g., as described above). In yet further implementations, the data volume threshold is sdt-DataVolumeThreshold or sdt-DataVolumeThreshold-r17.

[0233] At block 1706, the RAN node includes the RA-SDT configuration in the SDT configuration (e.g., Figures 3 to 6Events 330 / 332 / 334 / 394, 430 / 432 / 434 / 494, 594, and 694). In some implementations, the RA-SDT configuration is a RA-SDT indication or a RA-SDT enable indication. In other implementations, the RA-SDT configuration is a random access configuration or a timer value for RA-SDT, such as logicalChannelSR-DelayTimer. In yet other implementations, the RA-SDT configuration is a signal strength or quality threshold configuration (e.g., sdt-RSRP-Threshold, sdt-RSRP-Threshold-r17, or RSRP-Range) for UE 102 to determine whether to initiate a RA-SDT process. For example, UE 102 obtains the signal strength or quality of a downlink path loss reference. Depending on the implementation, if the signal strength or quality is higher than the threshold in the threshold configuration, UE 102 initiates a RA-SDT process. Otherwise, UE 102 avoids initiating a RA-SDT process. At block 1708, the RAN node broadcasts a system information block (SIB) including the SDT configuration on the cell. In response to or after determining that RA-SDT is enabled for the cell, the RAN node proceeds to blocks 1704, 1706, and / or 1708, depending on the implementation.

[0234] Next reference Fig. 17B , method 1700B can be implemented in a suitable RAN node (e.g., base station 104 or DU 174) and includes managing small data transmission with UE. For clarity, method 1700B is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172 and DU 174.

[0235] At block 1703, the RAN node determines to enable CG-SDT only for the cell. At block 1704, the RAN node includes the timer value and / or data volume threshold in the SDT configuration, similar to Fig.17A At block 1707, the RAN node avoids including the RA-SDT configuration in the SDT configuration (e.g., Figures 3 to 6Events 330 / 332 / 334 / 394, 430 / 432 / 434 / 494, 594, and 694 of RA-SDT configuration). In some implementations, the RAN node includes a CG-SDT configuration in the SDT configuration instead of a RA-SDT configuration. In further implementations, the CG-SDT configuration is a CG-SDT indication or a CG-SDT enable indication. In other implementations, the CG-SDT configuration is a logicalChannelSR-DelayTimer. Depending on the implementation, in response to determining that CG-SDT is enabled only for the cell or after determining that CG-SDT is enabled only for the cell, the RAN node proceeds to blocks 1704, 1706, and / or 1708.

[0236] against Fig.17A The examples and implementations described can be applied to Fig. 17B .

[0237] Next reference Fig. 17C , method 1700C can be implemented in a suitable RAN node (e.g., base station 104 or DU 174) and includes managing small data transmission with UE. For clarity, method 1700C is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172 and DU 174.

[0238] At block 1701, the RAN node determines to enable SDT for a cell. At block 1704, the RAN node includes a timer value and / or a data volume threshold in an SDT configuration, similar to Fig.17A At block 1705, the RAN node determines whether RA-SDT is enabled for the cell. If the RAN node determines that RA-SDT is enabled for the cell, the RAN node proceeds to blocks 1706 and 1708, as described above. In some implementations, the RAN node avoids including a RA-SDT configuration, similar to Fig. 17B Box 1707.

[0239] against Fig.17A and Fig. 17B The examples and implementations described can be applied to Fig. 17C .

[0240] Next reference Fig.18 , the method 1800 may be implemented in a network node and includes managing small data transmissions on a cell. For clarity, the method 1800 is discussed with specific reference to UE 102, base station 104, RAN 105, CU 172, and DU 174.

[0241] At block 1802, a RAN node of the RAN 105 (such as the base station 104 or the DU 174) determines that a cell should facilitate small data transmissions on the cell (e.g., FIG. 17A to FIG. 17C At block 1804, the RAN node generates a data packet based at least on whether the network node determines to enable the cell to facilitate communication according to the SDT type that relies on the random access procedure, which when received by a UE (such as UE 102) enables UE 102 to transmit small data according to the capabilities of the cell (e.g., Figures 3 to 6 and FIG. 17A to FIG. 17C At block 1806, the RAN node broadcasts the data packet on the cell (e.g., FIG. 17A to FIG. 17C Event 1708).

[0242] The following list of examples reflects the various embodiments expressly contemplated by the present disclosure:

[0243] Example 1. A method for managing small data transmission (SDT) with a user equipment (UE), the method being implemented in a network node of a radio access network (RAN) and comprising: determining that the UE should operate in a state of a protocol for controlling radio resources, wherein the UE is not connected to the RAN; generating a message enabling the UE to transmit small data according to capabilities of the UE based at least on whether the UE supports a first type of SDT that depends on a random access procedure and / or a second type of SDT that depends on resources previously allocated to the UE; and sending the message to the UE.

[0244] Example 2. The method of Example 1, wherein generating the message comprises: generating an indication of the first type of SDT when the UE and the network node support the first type of SDT.

[0245] Example 3. The method of Example 2, wherein generating the message comprises: generating an SDT configuration common to the first type of SDT and the second type of SDT.

[0246] Example 4. The method of Example 2, wherein generating the message comprises generating an SDT configuration specific to the first type of SDT.

[0247] Example 5. The method of Example 4, wherein generating the message further comprises: generating an SDT configuration common to the first type of SDT and the second type of SDT.

[0248] Example 6. The method of Example 1, wherein generating the message comprises: when at least one of the UE or the network node does not support the first type of SDT, avoiding generating an SDT configuration.

[0249] Example 7. The method of any preceding example, wherein generating the message is further based on whether the network node has configured a data radio bearer (DRB) for the UE.

[0250] Example 8. The method of Example 7, wherein generating the message comprises generating an indication of the first type of SDT when (i) the UE and the network node support the first type of SDT and (ii) the network node has configured the DRB for the UE.

[0251] Example 9. The method of Example 7, wherein generating the message comprises: generating an indication of the first type of SDT when (i) the UE and the network node support the first type of SDT and (ii) the network node has not configured the DRB for the UE.

[0252] Example 10. The method of Example 1, wherein generating the message comprises: generating an indication of the second type of SDT when the UE and the network node support the second type of SDT.

[0253] Example 11. The method of Example 10, wherein the indication of the second type SDT comprises a CG-SDT configuration.

[0254] Example 12. The method of Example 10 or 11, wherein the message further includes an SDT configuration common to multiple types of SDT communications.

[0255] Example 13. The method of Example 1, wherein generating the message comprises: when at least one of the UE or the network node does not support the second type of SDT, refraining from generating an SDT configuration.

[0256] Example 15. The method of Example 1, wherein the generating is further based on whether the UE supports the second type of SDT for an uplink carrier frequency in a cell in which the UE is currently operating.

[0257] Example 16. The method of Example 15, wherein generating the message comprises generating an indication of the second type of SDT when the UE supports the second type of SDT for the uplink carrier frequency.

[0258] Example 17. The method of Example 16, wherein the indication of the second type of SDT includes a configuration specific to the second type of SDT.

[0259] Example 18. The method of Example 16 or 17, wherein the message further includes an SDT configuration common to the first type of SDT and the second type of SDT.

[0260] Example 19. The method of Example 15, wherein generating the message comprises: refraining from generating an SDT configuration when the UE does not support the second type of SDT for the uplink carrier frequency.

[0261] Example 20. The method as described in Example 1, wherein generating the message includes: generating an indication of the first type of SDT when the UE and the network node support the first type of SDT; and generating an indication of the second type of SDT when the UE and the network node support the second type of SDT.

[0262] Example 21. The method of Example 1, wherein generating the message comprises: avoiding generating an SDT configuration when (i) at least one of the UE or the network node does not support the first type of SDT and (ii) at least one of the UE or the network node does not support the second type of SDT.

[0263] Example 22. A method as described in Example 15, wherein generating the message includes: generating an indication of the first type of SDT when the UE and the network node support the first type of SDT; and generating an indication of the second type of SDT when the UE supports the second type of SDT for the uplink carrier frequency.

[0264] Example 23. The method of Example 15, wherein generating the message comprises: avoiding generating an SDT configuration when (i) at least one of the UE or the network node does not support the first type of SDT and (ii) the UE does not support the second type of SDT for the uplink carrier frequency.

[0265] Example 24. The method as described in any of the preceding examples further comprises: receiving a UE capability information element (IE); and determining whether the UE supports at least one of the first type of SDT or the second type of SDT based on the UE capability IE.

[0266] Example 25. A method as described in Example 24, wherein the UE supports at least the second type of SDT, the method further comprising: determining, based on the UE capability IE, whether the UE supports the second type of SDT for at least one of the following: (i) one or more frequency bands, (ii) frequency division duplex (FDD) operation, or (iii) time division duplex (TDD) operation.

[0267] Example 26. The method of Example 25, wherein the one or more frequency bands include at least one of: (i) frequency range 1 (FR1), (ii) frequency range 2-1 (FR2-1), or (iii) frequency range 2-2 (FR2-2).

[0268] Example 27. The method of any one of Examples 24 to 26, wherein the RAN stores the UE capability IE, the method further comprising: receiving a UE capability identifier; and identifying the UE capability IE based on the UE capability identifier.

[0269] Example 28. The method as described in any one of Examples 2 to 27 further includes: when the support flag is set to a first value, determining that the network node supports at least one of the first type of SDT or the second type of SDT; and when the support flag is set to a second value, determining that the network node does not support the first type of SDT or the second type of SDT.

[0270] Example 29. The method as described in any one of Examples 2 to 27 further includes: when the network node stores a support flag, determining that the network node supports at least one of the first type of SDT or the second type of SDT; and when the network node does not store the support flag, determining that the network node does not support the first type of SDT or the second type of SDT.

[0271] Example 30. A method as described in any of the preceding examples, wherein the network node is a non-distributed base station.

[0272] Example 31. A method as described in any of Examples 1 to 29, wherein the network node is a central unit (CU) of a distributed base station, and the distributed base station also includes a distributed unit (DU).

[0273] Example 32. The method of Example 31, wherein generating the message further comprises: when the UE and the DU support the first type of SDT, generating the message including an indication of the first type of SDT.

[0274] Example 33. The method of Example 31 or 32, wherein generating the message further comprises: retrieving an indication of the second type of SDT from the DU when the UE and the DU support the second type of SDT.

[0275] Example 34. The method of Example 32, wherein generating the message further comprises: retrieving an indication of the second type of SDT from the DU when the UE supports the second type of SDT for an uplink carrier frequency in a cell in which the UE is currently operating.

[0276] Example 35. The method as described in any one of Examples 32 to 34 further includes: when the support flag is set to a first value, determining that the DU supports at least one of the first type of SDT or the second type of SDT; and when the support flag is set to a second value, determining that the DU does not support the first type of SDT or the second type of SDT.

[0277] Example 36. The method as described in any one of Examples 32 to 34 further includes: when the network node stores the support flag, determining that the DU supports at least one of the first type of SDT or the second type of SDT; and when the network node does not store the support flag, determining that the DU does not support the first type of SDT or the second type of SDT.

[0278] Example 37. A method as described in any of the preceding examples, wherein: before determining that the UE should operate in an inactive state, the UE operates in an active state, and the message causes the UE to transition to the inactive state.

[0279] Example 38. A method as described in any one of Examples 1 to 32, wherein: before determining that the UE should operate in the inactive state, the UE operates in the inactive state, and the UE continues to operate in the inactive state in response to receiving the message.

[0280] Example 39. A method as described in any of the preceding examples, wherein the message is an RRC release message.

[0281] Example 40. A method for managing small data transmission (SDT) on a cell, the method being implemented in a network node of a radio access network (RAN) and comprising: determining that the cell should facilitate small data communication on the cell; generating a data packet based at least on whether the network node determines to enable the cell to facilitate communication according to an SDT type that depends on a random access procedure, the data packet, when received by a UE, enabling the UE to transmit small data according to the capabilities of the cell; and broadcasting the data packet on the cell.

[0282] Example 41. The method of Example 40, wherein generating the data packet comprises: when the network node determines to activate the cell, generating an indication to facilitate communication according to the SDT type.

[0283] Example 42. The method of Example 41, wherein generating the data packet comprises generating an SDT configuration specific to the SDT type.

[0284] Example 43. The method of Example 41 or 42, wherein the SDT type is a first SDT type, and generating the data packet comprises generating an SDT configuration common to the first SDT type and a second SDT type.

[0285] Example 44. The method of Example 40, wherein generating the data packet comprises: when the network node determines not to enable the cell, refraining from generating an indication to facilitate communication according to the SDT type.

[0286] Example 45. The method of any one of Examples 40 to 44, wherein the SDT type is a first SDT type, and generating the data packet includes: when the network node determines to enable the cell, generating an indication to facilitate communication according to a second SDT type.

[0287] Example 46. The method of any one of Examples 40 to 45, wherein the SDT type is a first SDT type, and generating the data packet includes: when the network node determines not to enable the cell, generating an indication to facilitate communication according to a second SDT type.

[0288] Example 47. A method as described in any of Examples 40 to 46, wherein the data packet includes a timer value.

[0289] Example 48. A method as described in any of Examples 40 to 47, wherein the data grouping includes a data volume threshold.

[0290] Example 49. The method of any one of Examples 40 to 48, wherein the data packet is a system information block (SIB).

[0291] Example 50. A method for managing a small data transmission (SDT) with a user equipment (UE), the method being implemented in a distributed unit (DU) of a distributed base station, the distributed base station also including a central unit (CU), the method comprising: receiving a message from the CU requesting SDT resources for the UE for an SDT type that depends on resources previously allocated to the UE; determining whether to include a configuration for the SDT type in a response message to the CU; and sending the response message to the CU.

[0292] Example 51. A method as described in Example 50, wherein the determination includes: when the SDT resources are available for the UE, determining that the configuration to be used for the SDT type is included in the response message, and when the SDT resources are not available for the UE, determining not to include the configuration to be used for the SDT type in the response message.

[0293] Example 52. A method as described in Example 51, wherein when the SDT resources are not available for the UE, the response message includes an indication that the SDT resources are not available in at least one of the following in the response message: (i) an IE value, (ii) a field value, or (iii) a cause value.

[0294] Example 53. A method as described in Example 51, wherein the determination includes: when the UE and the DU support the SDT type, determining that the configuration for the SDT type is included in the response message, and when at least one of the UE or the DU does not support the SDT type, determining not to include the configuration for the SDT type in the response message.

[0295] Example 54. A method as described in Example 53, wherein when the UE does not support the SDT type, the response message includes an indication that the UE does not support the SDT type in at least one of the following in the response message: (i) an IE value, (ii) a field value, or (iii) a cause value.

[0296] Example 55. The method as described in Example 53 or 54 further includes: receiving a UE capability information element (IE) from the CU; and determining whether the UE supports the SDT type based on the UE capability IE.

[0297] Example 56. A method as described in any of Examples 50 to 55, wherein the response message is at least one of the following: (i) a UE context modification message or (ii) a UE context establishment message.

[0298] Example 57. A network node comprising processing hardware and configured to implement any of the preceding examples.

[0299] The following description may be applicable to the above description.

[0300] In general, the description for any one of the above figures may apply to the other of the above figures. The above events or boxes may be optional or omitted. For example, the events or boxes with dotted lines in the figure may be optional. In some implementations, "message" is used, and "message" can be replaced with "information element (IE)", and vice versa. In some implementations, "IE" is used and "field" can be replaced with "IE", and vice versa. In some implementations, "configuration" or "configuration parameter" can be replaced with "configuration", and vice versa. In some implementations, "early data transmission (EDT)" can be replaced with "small data transmission", and "SDT" can be replaced with "EDT", and vice versa. In some implementations, "small data transmission" can be replaced with "small data communication", and vice versa. In some implementations, "stop" can be replaced with "pause".

[0301] In some implementations, the “second UE CG-SDT timer” may be replaced with the “CG-SDT retransmission timer (cg-SDT-RetransmissionTimer)”. In some implementations, “CG-SDT”, “CG”, and “SDT-CG” may be interchangeable.

[0302] The user device (e.g., UE 102) in which the technology of the present disclosure can be implemented can be any suitable device capable of wireless communication, such as a smart phone, a tablet computer, a laptop computer, a mobile game console, a point of sale (POS) terminal, a health monitoring device, a drone, a camera, a media streaming dongle or another personal media device, a wearable device such as a smart watch, a wireless hotspot, a femtocell or a broadband router. In addition, in some cases, the user device can be embedded in an electronic system, such as a head unit of a vehicle or an advanced driver assistance system (ADAS). Further, the user device can be operated as an Internet of Things (IoT) device or a mobile Internet device (MID). Depending on the type, the user device may include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0303] Certain embodiments are described in the present disclosure as including logic or multiple components or modules. A module may be a software module (e.g., a code or machine-readable instruction stored on a non-temporary machine-readable medium) or a hardware module. A hardware module is a tangible unit that is capable of performing certain operations and may be configured or arranged in a particular manner. A hardware module may include a dedicated circuit system or logic that is permanently configured to perform certain operations (e.g., as a dedicated processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.). A hardware module may also include a programmable logic or circuit system (e.g., as contained in a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in a dedicated and permanently configured circuit system or in a temporarily configured circuit system (e.g., configured by software) may be driven by cost and time considerations.

[0304] When implemented in software, the techniques may be provided as part of an operating system, a library used by multiple applications, a specific software application, etc. The software may be executed by one or more general-purpose processors or one or more special-purpose processors.

Claims

1. A method for managing a small data transfer (SDT) with a user equipment (UE), the method being implemented in a network node of a radio access network (RAN) and comprising: determining that the UE should operate in a state of a protocol for controlling radio resources, wherein the UE is not connected to the RAN; generating, based at least on whether the UE supports a SDT type that depends on a random access procedure, a message that enables the UE to transmit small data according to a capability of the UE for the SDT type; as well as The message is sent to the UE.

2. The method of claim 1, wherein generating the message comprises: When the UE and the network node support the SDT type, an indication of the SDT type is generated.

3. The method of claim 2, wherein generating the message comprises: An SDT configuration specific to the SDT type is generated.

4. The method of any one of the preceding claims, wherein the SDT type is a first SDT type, the method further comprising: Prior to generating the message, it is detected that the UE does not support a second SDT type that is dependent on resources previously allocated to the UE.

5. The method of any one of the preceding claims, wherein generating the message is further based on whether the network node has configured a data radio bearer (DRB) for the UE.

6. The method of claim 5, wherein generating the message comprises: An indication of the SDT type is generated when (i) the UE and the network node support the SDT type and (ii) the network node has configured the DRB for the UE.

7. The method of claim 5, wherein generating the message comprises: An indication of the SDT type is generated when (i) the UE and the network node support the SDT type and (ii) the network node has not configured the DRB for the UE.

8. The method of any one of the preceding claims, further comprising: Receive UE capability information element (IE); as well as Determining whether the UE supports the SDT type based on the UE capability IE.

9. The method of claim 8, wherein the RAN stores the UE capability IE, the method further comprising: receiving a UE capability identifier; as well as The UE capability IE is identified based on the UE capability identifier.

10. The method according to any of claims 1 to 9, wherein the network node is a central unit (CU) of a distributed network node, the distributed network node further comprising a distributed unit (DU).

11. A method for managing small data transmission (SDT) on a cell, the method being implemented in a network node of a radio access network (RAN) and comprising: determining that the cell should facilitate small data communications over the cell; generating a data packet based at least on whether the network node determines to enable the cell to facilitate communications according to an SDT type that relies on a random access procedure, the data packet, when received by a user equipment (UE), causing the UE to transmit small data according to capabilities of the cell; as well as The data packet is broadcast over the cell.

12. The method of claim 11, wherein generating the data packet comprises: When the network node determines to activate the cell, an indication for facilitating communication is generated according to the SDT type.

13. The method of claim 11, wherein generating the data packet comprises: When the network node determines not to activate the cell, avoiding generating an indication to facilitate communication according to the SDT type.

14. The method of any one of claims 11 to 13, wherein the SDT type is a first SDT type, and generating the data packet comprises: When the network node determines not to activate the cell, an indication to facilitate communication is generated according to a second SDT type.

15. A network node comprising processing hardware and configured to implement any of the preceding claims.