Wireless communication method, user equipment and base station for small data transmission SDT
By introducing the use of RRC_Inactive status and cell-specific or non-cell-specific identifiers in the 5G wireless communication network, user equipment can efficiently transmit small data in an inactive state, solving the problems of large signaling overhead and waiting time, and improving data Transmission efficiency.
Patent Information
- Application Number
- CN202380036579.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-27
- Filing Date
- 2023-04-20
- Publication Date
- 2024-12-06
AI Technical Summary
In 5G wireless communication network, when the user equipment (UE) is inactive, the signaling overhead and waiting time initiated by the mobile terminal are large, and the prior art fails to effectively support the mobile terminal termination in RRC_INACTIVE mode. Data transmission.
A new RRC_Inactive state has been introduced, and the user equipment (UE) can perform small data transmission by receiving downlink control information (DCI) and random access channel (RACH) resource configuration without switching to the RRC_CONNECTED state. The processor determines to use cell-specific or non-cell-specific user equipment identification, receives data priority indications through paging messages, and receives data transmissions on a physical shared channel.
The signaling overhead and waiting time in RRC_INACTIVE mode are reduced, and the data transmission efficiency of user equipment in the inactive state is improved, and unnecessary state transitions and power consumption are avoided.
Smart Images

Figure CN119096623A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to wireless communications, user equipment, base stations, and in a specific embodiment, to control signaling in a wireless communications network, and to handling small data transmission (SDT) to a user equipment (UE) in a radio access network (RAN) when a receiver of the user equipment (UE) is inactive. Background Art
[0002] In some wireless communication networks, user equipment (UE) and base stations perform wireless communication to send data to the base station and / or receive data from the base station. Wireless communication from user equipment (UE) to base station is called uplink (UL) communication. Wireless communication from base station to user equipment (UE) is called downlink (DL) communication. Wireless communication from a first user equipment (UE) to a second user equipment (UE) is called sidelink (SL) communication or device-to-device (D2D) communication.
[0003] WO 2021 031 112A1 discloses various aspects related to wireless communications. The present application describes that a user equipment (UE) can receive a paging communication from a base station (BS) when in an inactive mode. The paging communication can identify a random access channel (RACH) preamble for the UE. The UE can transmit a RACH preamble to the BS in a Msg1 communication based at least in part on receiving the paging communication. The UE can receive a Msg2 communication from the BS based at least in part on transmitting the RACH preamble in the Msg1 communication, the Msg2 communication including downlink data terminated by the mobile terminal and an indication that the UE will transition from an inactive mode to a connected mode with the BS. Many other aspects are provided.
[0004] WO 2021031103A1 describes that a user equipment (UE) can receive a paging communication from a base station (BS) when the UE is in an inactive mode or an idle mode. As part of a random access channel (RACH) process, the UE can transmit a first communication to the BS based at least in part on receiving the paging communication. The UE can receive a second communication from the BS based at least in part on transmitting the first communication, the second communication including downlink data terminated by the mobile end, an indication of uplink resources, and a radio resource control (RRC) release message. The RRC release message can enable the UE to remain in an inactive mode or an idle mode while receiving downlink data terminated by the mobile end. The UE can use uplink resources to transmit uplink data initiated by the mobile end. Many other aspects are provided.
[0005] WO 2021 157 895A1 provides a method and apparatus for small data transmission in an RRC inactive state in an MR-DC. In the DC of a wireless device, an MN transmits a paging message to the wireless device, the paging message including an indication related to an EDT process of the SN. The MN receives an AS-RAI related to the EDT process of the SN from the wireless device. Based on the received AS-RAI, the MN decides whether to continue the EDT process to send DL data to the wireless device or to transition the wireless device to an RRC-CONNECTED state.
[0006] US 10 264 622 B2 discloses that a base station receives (multiple) packets of a wireless device in an RRC inactive state from a first core network entity. The base station initiates a RAN paging procedure, which includes sending (multiple) RAN paging messages to (multiple) second base stations. The (multiple) RAN paging messages include a first identifier of the wireless device. The base station determines that the RAN paging procedure has failed in response to not receiving a response to the (multiple) RAN paging messages. In response to the failure of the RAN paging procedure, the base station sends a first message to the second core network entity. The base station receives a second message from the second core network entity in response to the first message. The second message includes a tunnel endpoint identifier of a third base station for forwarding the (multiple) packets. The base station sends the (multiple) packets to the third base station based on the tunnel endpoint identifier.
[0007] US 2021 127 414A1 describes a control signaling mechanism for supporting data transmission with a user equipment (UE) in an inactive state. In some embodiments, the inactive UE receives DCI, which includes: a cyclic redundancy check (CRC) scrambled by a radio network temporary identifier (RNTI) dedicated to a group of UEs, the group of UEs including the UE; and a resource assignment for data transmission to the UE. The data transmission is then received on a physical shared channel. In a further embodiment, the inactive UE receives DCI, which includes: a CRC scrambled by a paging RNTI; and a resource assignment for a paging message to the UE. The UE receives the data transmission in the paging message or in a further transmission scheduled by the paging message.
[0008] In 3GPP New Radio (NR), a user equipment (UE) can operate in one of three states: RRC_IDLE, RRC_CONNECTED, and RRC_INACTIVE.
[0009] In the RRC_CONNECTED state, the user equipment (UE) is connected to the network according to the connection establishment process. In the RRC_IDLE state, the user equipment (UE) is not connected to the network, but the network knows that the user equipment (UE) exists in the network. When the user equipment (UE) is not communicating with the network, switching to the RRC_IDLE state helps save network resources and user equipment (UE) power, such as battery life.
[0010] When the user equipment (UE) is not communicating with the network, the inactive mode (RRC_INACTIVE) state also helps save network resources and user equipment (UE) power. However, unlike the RRC_IDLE state, when the user equipment (UE) is in the inactive mode (RRC_INACTIVE) state, both the network and the user equipment (UE) store at least some configuration information to allow the user equipment (UE) to reconnect to the network faster.
[0011] To reduce signaling overhead and waiting time, 3GPP TS 38.331 Release 17 introduces support for SDT initiated by the mobile terminal in RRC inactive mode. Figure 1 A simplified schematic flow chart of SDT in this case is shown. When in the RRC_INACTIVE mode of operation, the user equipment (UE) determines whether it has data to transmit to the RAN. In the affirmative case ("yes" branch), the user equipment (UE) will perform a RACH procedure, which is an abbreviation for random access channel, and the RACH procedure is usually used to connect and synchronize the user equipment (UE) to the best base station (gNB) of the RAN. During the RACH procedure, a small amount of data can be transmitted without transitioning from the RRC_INACTIVE mode of operation to a fully connected state (ie, RRC CONNECTED).
[0012] Currently, the 3rd Generation Partnership Project (3GPP) is working on technical specifications for the next generation of cellular technology, also known as fifth generation (5G) or sixth generation (6G).
[0013] The current version of 3GPP TS 38.331 does not specify mobile-terminated small data transfers in RRC_INACTIVE mode, and any mobile-terminated data transfer requires the UE to transition to a fully connected state (ie, RRC_CONNECTED).
[0014] eMBB deployment scenarios may include indoor hotspots, dense cities, rural areas, urban macro and high-speed; URLLC deployment scenarios may include industrial control systems, mobile healthcare (remote monitoring, diagnosis and treatment), vehicle real-time control, smart grid wide-area monitoring systems; mMTC deployment scenarios may include scenarios where a large number of devices (such as smart wearable devices and sensor networks) transmit non-time-critical data. The similarities between eMBB and URLLC services are that they both require very wide bandwidths, however, the difference is that URLLC services may preferably require ultra-low latency. Traditionally, when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) state, data transmission to and from the user equipment (UE) is restricted. Summary of the invention
[0015] In 5G, they introduced a new RRC state named "RRC_Inactive" to minimize latency and reduce signaling load. Since the UE context is stored in the base station (gNB) and the UE, the transition from RRC_Inactive to Connected is very fast. NG signaling remains valid between the base station (gNB) to AMF and GTP-U also remains valid between the base station (gNB) to UPF. In case a DL small data transfer is ongoing and if during this process, the UE wants to initiate a UL data transfer (which can be UL small data or UL non-small data), the current UE behavior and process are not defined.
[0016] A non-limiting and exemplary embodiment helps provide a process for facilitating a user equipment (UE) to transmit small data (e.g., when the user equipment (UE) is in an inactive state). In an embodiment, the user equipment (UE) disclosed herein is characterized by a user equipment including the following. A processor of the user equipment (UE) determines that the transmission of small data is to be performed. The user equipment (UE) is in an inactive state and has at least one data connection with a radio base station that controls a radio cell in which the user equipment (UE) is located. The user equipment (UE) is assigned at least a cell-specific user equipment (UE) identifier and a non-cell-specific user equipment (UE) identifier. The processor determines which user equipment (UE) identifier is used for small data transmission based on whether the user equipment (UE) has moved from another radio cell to the current radio cell after transitioning to the inactive state. In the case where the user equipment (UE) has moved from another radio cell to the current radio cell, the processor determines that the non-cell-specific user equipment (UE) identifier is used for small data transmission. In the case where the user equipment (UE) has not moved from another radio cell to the current radio cell, the processor determines that the cell-specific user equipment (UE) identifier is used for small data transmission.
[0017] The user equipment (UE) receives an indication in a paging message whether the network has one downlink (DL) data transmission or multiple data transmissions. To create signaling, 1 bit is used to indicate such information (1 indicates multiple downlink (DL) data transmissions, 0 indicates a single downlink (DL) data transmission).
[0018] If the base station (gNB) indicates a downlink (DL) data transmission, the user equipment (UE) performs uplink (UL) data transmission after receiving the downlink (DL) data, such as Figure 1 shown.
[0019] The user equipment (UE) can use the RRC Release with Suspend procedure to transition from the RRC_Connected state to the RRC_Inactive state. The Suspend-config parameter is located in the RRC Release message, which provides information to the UE, such as RNA updates, paging cycles, etc.
[0020] Since NG signaling will be effective between AMF and base station (gNB), AMF can request UE status information from base station (gNB) through "Initial UE Context Setup Request or Modification Request", or base station (gNB) can provide subsequent updates to AMF through "RRC Inactive Transition Report". This will help AMF configure its supervision timer to get the response of DL notification.
[0021] The base station (gNB) will provide full (40-bit) I-RNTI (Inactive Radio Network Temporary Identity) and short (24-bit) I-RNTI. The base station (gNB) will use the full I-RNTI during the RRC paging message. The user equipment (UE) can use short I-RNTI or full I-RNTI depending on the coverage. UEs located at the edge of the cell with low coverage can use short I-RNTI (RRC Recovery Request can be sent as msg3 during RACH, which means it cannot be segmented and uses a single transport block). The message length is relatively short compared to RRC Recovery Request 1 (full I-RNTI).
[0022] If the base station (gNB) indicates multiple downlink (DL) data transmissions, the user equipment (UE) sends an indication of available uplink (UL) data to the network, such as Figure 2As shown. The user equipment (UE) uses a small data transmission based on configuration authorization (CG-SDT) resource or a small data transmission based on random access (RA-SDT) resource and sends an indication through a medium access control control element (MAC CE), wherein the small data transmission based on configuration authorization (CG-SDT) resource and the RA-SDT resource are broadcast through system information or configured through a dedicated signaling message. The user equipment (UE) further indicates whether the available uplink (UL) data is small data or non-small data and the priority.
[0023] Based on this information from the user equipment (UE), the base station (gNB) suspends downlink (DL) data transmission and resumes downlink data transmission after receiving uplink (UL) data from the user equipment (UE) in an inactive mode (RRC_INACTIVE) or RRC_CONNECTED mode.
[0024] A transmitter of the user equipment (UE) transmits a control message including the determined user equipment (UE) identity and transmits small data using one of the at least one data connection.
[0025] In the case where a downlink (DL) small data transmission is ongoing, and if during this process the user equipment (UE) wants to initiate an uplink (UL) data transmission (which can be uplink (UL) small data or uplink (UL) non-small data), the current user equipment (UE) behavior and procedures are not stably defined.
[0026] In general, the purpose of the present invention is to reduce the signaling overhead and waiting time of small data transmission initiated by the mobile terminal in RRC_INACTIVE mode.
[0027] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.
[0028] Additional benefits and advantages of the disclosed embodiments and different implementations will be apparent from the description and drawings. Benefits and / or advantages may be obtained individually through the various embodiments and features of the description and drawings, and it is not necessary to provide all of these embodiments and features in order to obtain one or more such benefits and / or advantages.
[0029] BRIEF DESCRIPTION OF THE DRAWINGS
[0030] Hereinafter, exemplary embodiments are described in more detail with reference to the accompanying drawings.
[0031] The systems, methods, and apparatus of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the claims below, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description of the Invention," one will understand how the features of the present disclosure provide advantages, including improved communications between access points and stations in a wireless network.
[0032] Certain aspects of the present disclosure generally relate to techniques for optimizing data transfer between user equipment and a radio network having at least one base station.
[0033] Certain aspects of the present disclosure provide a method for wireless communication. The method generally includes receiving, by a user equipment (UE) in an inactive state (RRC_INACTIVE), downlink control information (DCI), the downlink control information including: a cyclic redundancy check (CRC) scrambled by a radio network having at least one base station (gNB) with an identifier (C-RNTI) dedicated to a group of UEs, the group of UEs including the UE; and a resource assignment for data transmission from at least the base station (gNB) to the user equipment (UE); and
[0034] The data transmission is received on a physical shared channel by the user equipment (UE) in the inactive state (RRC_INACTIVE), wherein the user equipment (UE) receives more than one random access channel (RACH) resource configuration.
[0035] Certain aspects of the present disclosure provide a method for wireless communications in which a user equipment (UE) receives a priority indication of downlink (DL) data in a paging message.
[0036] Certain aspects of the present disclosure provide a method for wireless communications in which a user equipment (UE) receives an indication of a group ID in a paging message.
[0037] Certain aspects of the present disclosure provide a method for wireless communications in which a user equipment (UE) receives a mapping between priority and group IDs and random access channel (RACH) resource configurations.
[0038] Certain aspects of the present disclosure provide a method for wireless communications in which a user equipment (UE) receives a mapping in system information or a dedicated RRC message.
[0039] Certain aspects of the present disclosure provide a method for wireless communications in which a user equipment (UE) selects a random access channel (RACH) resource corresponding to a priority and / or group ID indicated in a paging message.
[0040] Certain aspects of the present disclosure provide a method for wireless communications in which a base station (gNB) configures more than one random access channel (RACH) resource for each synchronization signal block (SSB).
[0041] Certain aspects of the present disclosure provide a method for wireless communications in which a base station (gNB) configures a mapping of random access channel (RACH) resources based on at least one option.
[0042] Certain aspects of the present disclosure provide a method for wireless communication, wherein the option is a selection of priorities P1, P2, and P3, and priority P1 is linked to random access channel (RACH) resource 1, priority P2 is linked to random access channel (RACH) resource 2, and priority P3 is linked to random access channel (RACH) resource 3.
[0043] Certain aspects of the present disclosure provide a method for wireless communication, wherein the option is a selection of group ID1, group ID2, and group ID3, and group ID1 is linked to random access channel (RACH) resource 1, group ID2 is linked to random access channel (RACH) resource 2, and group ID3 is linked to random access channel (RACH) resource 3.
[0044] Certain aspects of the present disclosure provide a method for wireless communications, wherein the mapping is accomplished through system information or a dedicated RRC message.
[0045] Certain aspects of the present disclosure provide a method for wireless communications, wherein a base station (gNB) indicates priorities P1, P2, P3 and / or group ID1, group ID1, group ID2, group ID3 in a paging message, and a user equipment (UE) selects a random access channel (RACH) resource.
[0046] Certain aspects of the present disclosure provide a user equipment (UE) for wireless communications, the user equipment comprising:
[0047] a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to:
[0048] receiving a paging communication from a base station (gNB) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE);
[0049] transmitting, as part of a random access channel (RACH) procedure, a first communication to the base station (gNB) based at least in part on receiving the paging communication; and
[0050] receiving, from a base station (gNB), a second communication based at least in part on transmitting the first communication, the second communication comprising:
[0051] mobile terminated downlink data (DL), an indication of uplink (UL) resources, and a radio resource control (RRC) release message (DL), the radio resource control release message causing the user equipment (UE) to remain in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE) when receiving the mobile terminated downlink data; and when in the inactive mode or the idle mode, to transmit mobile originated uplink data to a base station (gNB) using the uplink (UL) resources,
[0052] Therein, the memory stores computer program instructions which, when executed by the microprocessor, configure the user equipment (UE) to implement the method as claimed in one or more of claims 1 to 13.
[0053] Certain aspects of the present disclosure provide a base station (gNB) for wireless communication, the base station comprising:
[0054] a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to:
[0055] transmitting a paging communication to a user equipment (UE) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE);
[0056] receiving a first communication from the user equipment (UE) based at least in part on transmitting the paging communication as part of a random access channel (RACH) procedure; and transmitting a second communication to the user equipment (UE) based at least in part on transmitting the first communication, the second communication comprising: mobile terminated downlink (DL) data, uplink (UL) resources to be used by the user equipment (UE) to transmit mobile initiated uplink data when in the inactive mode or the idle mode, and a radio resource control (RRC) release message, the radio resource control release message causing the user equipment (UE) to receive the mobile terminated downlink (DL) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE); and receiving mobile initiated uplink data from the user equipment (UE) in the uplink (UL) resources, the user equipment (UE) to transmit the mobile initiated uplink data when in the inactive mode or the idle mode,
[0057] The memory stores computer program instructions which, when executed by the microprocessor, configure the user equipment (UE) via the base station (gNB) to implement one or more of the methods described in claims 1 to 13.
[0058] Certain aspects of the present disclosure provide a non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising:
[0059] One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the one or more processors to:
[0060] receiving a paging communication from a base station (gNB) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE);
[0061] As part of a random access channel (RACH) procedure, transmitting a first communication to the base station (gNB) based at least in part on receiving the paging communication; and receiving a second communication from the base station (gNB) based at least in part on transmitting the first communication, the second communication comprising:
[0062] mobile-terminated downlink (DL) data, an indication of uplink (UL) resources, and a radio resource control (RRC) release message, the radio resource control release message causing the user equipment (UE) to remain in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE) when receiving the mobile-terminated downlink data; and when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), transmitting mobile-originated uplink (UL) data to the base station (gNB) using the uplink (UL) resources,
[0063] Therein, the non-transitory computer readable medium stores computer program instructions which, when executed by a microprocessor, configure the user equipment (UE) to implement the method as claimed in one or more of claims 1 to 13.
[0064] One or more instructions that, when executed by one or more processors of a base station (gNB), cause the one or more processors to perform the following operations:
[0065] When the user equipment (UE) is in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), transmitting a paging communication to the user equipment (UE);
[0066] as part of a random access channel (RACH) procedure, receiving a first communication from the user equipment (UE) based at least in part on transmitting the paging communication; and transmitting a second communication to the user equipment (UE) based at least in part on transmitting the first communication, the second communication comprising: mobile-terminated downlink (DL) data, uplink (UP) resources to be used by the user equipment (UE) to transmit mobile-initiated uplink (UP) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), and a radio resource control (RRC) release message that enables the user equipment (UE) to receive the mobile-terminated downlink (DL) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), and
[0067] receiving mobile-initiated uplink (UL) data from the user equipment (UE) in the uplink (UL) resource, the user equipment (UE) transmitting the mobile-initiated uplink (UL) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE),
[0068] Therein, the non-transitory computer readable medium stores computer program instructions which, when executed by a microprocessor, configure the user equipment (UE) to implement the method as claimed in one or more of claims 1 to 13.
[0069] Aspects generally include methods, apparatus, systems, computer-readable media, and processing systems as substantially described herein with reference to and as illustrated by the accompanying drawings.
[0070] To accomplish the foregoing and related ends, the one or more aspects include the features hereinafter fully described and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are indicative of only a few of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents.
[0071] Although the present invention is described with emphasis on a radio access network according to the 3GPP TS 38.211, TS 38.212, TS 38.213, TS 38.300, TS 38.321 and TS 38.331 series of standards (also known as 5G NR), the present invention may also be used for further developments thereof, such as the future 6G standard. Furthermore, although the present invention is described with emphasis on the RRC_INACTIVE mode of operation, the present invention is not limited thereto but may be used in all wireless systems in which the UE needs to be connected to a network infrastructure for data transmission and reception and disables the receiver when not actively communicating, and which provide a mechanism by which small amounts of data can be transmitted without being fully connected to the network infrastructure. In particular, any terminology used in this specification to identify a component or device, such as a gNB for a base station of a RAN, is not meant to limit the present invention to standards that use the same terminology for components or devices performing the same function. BRIEF DESCRIPTION OF THE DRAWINGS
[0072] Figure 1 A user equipment (UE) is shown sending an uplink (UL) small data transmission in an inactive mode (RRC_INACTIVE) state without moving to RRC_CONNECTED;
[0073] Figure 2 The downlink (DL) small data available to the base station (gNB) when the user equipment (UE) is in inactive mode (RRC_INACTIVE);
[0074] Figure 3 The user equipment (UE) enters the RRC_CONNECTED state to receive downlink data transmission from the base station (gNB);
[0075] Figure 4 It shows the configuration of a random access channel (RACH) resource for each synchronization signal block (SSB) by the base station (gNB);
[0076] Figure 5 It is shown that a base station (gNB) configures more than one random access channel (RACH) resource for each synchronization signal block (SSB);
[0077] Figure 6 A flowchart of the user equipment (UE) side provided is shown;
[0078] Figure 7 A flowchart on the provided base station (gNB) side is shown. DETAILED DESCRIPTION
[0079] To reduce signaling overhead, the base station (gNB) can schedule downlink transmissions without requiring the user equipment (UE) to be in a connected state. To this end, the user equipment (UE) can be scheduled using predefined cells and beams used for previous transmissions. The user equipment (UE) can receive this information in a dedicated RRC message or a paging message.
[0080] Figure 1 A user equipment (UE) is shown sending an uplink (UL) small data transmission in an inactive mode (RRC_INACTIVE) state without moving to RRC_CONNECTED.
[0081] In 5G, they introduced a new RRC state called "RRC Inactive" to minimize latency and reduce signaling load. Since the user equipment (UE) context is stored in the base station (gNB) and the user equipment (UE), the transition from RRC Inactive to Connected is very fast. NG signaling remains valid between the base station (gNB) to AMF, and GTP-U also remains valid between the base station (gNB) to UPF. The user equipment (UE) can use the RRC Release Suspend procedure to transition from the RRC Connected state to the Inactive state. The Suspend-config parameter is in the RRC Release message, which provides information to the user equipment (UE) (RNA updates, paging cycles, etc.).
[0082] Since NG signaling will be valid between AMF and gNB, AMF can request UE status information from gNB via “Initial UE Context Setup Request or Modification Request”, or gNB can provide subsequent updates to AMF via “RRC Inactive Transition Report”. This will help AMF configure its supervision timer to get the response of DL notification.
[0083] The gNB will provide both full (40-bit) I-RNTI (Inactive Radio Network Temporary Identity) and short (24-bit) I-RNTI. The gNB will use the full I-RNTI during the RRC paging message. The UE can use short I-RNTI or full I-RNTI depending on the coverage. The UE at the edge of the cell with low coverage can use short I-RNTI. The RRC recovery request can be sent as msg3 during RACH, which means it cannot be segmented and uses a single transport block. The message length is relatively short compared to the RRC recovery request 1 (full I-RNTI). If the gNB indicates a downlink (DL) data transmission, the UE performs an uplink (UL) data transmission after receiving the downlink (DL) data. In order to reduce signaling overhead and waiting time, 3GPP TS 38.331Release 17 introduces support for mobile-initiated SDT in RRC inactive mode. Figure 1 A simplified schematic flow chart of the SDT in this case is shown.
[0084] 5G NR system architecture and protocol stack
[0085] 3GPP has been working on the next versions of the 5th and 6th generation of cellular technology (abbreviated as 5G or 6G), including the development of a new radio access technology (NR) operating in the frequency range up to 100GHz. The first version of the 5G standard was completed in late 2017, allowing trials and commercial deployment of smartphones compliant with the 5G NR standard.
[0086] The current version of 3GPP TS 38.331 does not specify mobile-terminated small data transfers in RRC_INACTIVE mode, and any mobile-terminated data transfer requires the UE to transition to a fully connected state (ie, RRC_CONNECTED).
[0087] Among them, the entire system architecture adopts NG-RAN (Next Generation - Radio Access Network) including base stations (gNB), providing NG-radio access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol termination for user equipment (UE). The base stations (gNB) are connected to each other through the Xn interface. The base station (gNB) is also connected to the NGC (Next Generation Core) through the next generation (NG) interface, more specifically, to the AMF (Access and Mobility Management Function), for example, to a specific core entity that executes the AMF through the NG-C interface, and to the UPF (User Plane Function), for example, to a specific core entity that executes the UPF through the NG-U interface. The NG-RAN architecture is described in Section 4 of 3GPP TS 38.300v16.0.0.
[0088] The user plane protocol stack for NR (see 3GPP TS 38.300, Section 4.4.1) includes PDCP (Packet Data Convergence Protocol, see Section 6.4 of TS 38.300), RLC (Radio Link Control, see Section 6.3 of TS 38.300) and Medium Access Control (MAC) (Medium Access Control, see Section 6.2 of TS 38.300) sublayers, which terminate at the base station (gNB) on the network side. In addition, a new access stratum (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced on top of PDCP subclause 6.5 of 3GPP TS 38.300. A control plane protocol stack is also defined for NR, e.g. Section 4.4.2 of TS 38.300. An overview of Layer 2 functions is given in Subclause 6 of TS 38.300. The functions of the RRC layer are listed in Subclause 7 of TS 38.300.
[0089] The media access control layer handles logical channel multiplexing, scheduling and scheduling-related functions, including handling different parameter sets (numerology).
[0090] The physical layer (PHY) is responsible for, for example, coding, PHY HARQ processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. The physical layer also handles the mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used to transmit a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, physical channels are PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel) for uplink and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel) and PBCH (Physical Broadcast Channel) for downlink.
[0091] Use cases / deployment scenarios for NR may include enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), massive machine type communications (mMTC), which have different requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and user experience data rates that are approximately three times higher than those provided by IMT-Advanced. On the other hand, in the case of URLLC, more stringent requirements are imposed on ultra-low latency (user plane latency of 0.5ms each for uplink (UL) and downlink (DL)) and high reliability (1-1O5 within 1ms). Finally, mMTC may preferably require high connection density (1,000,000 devices / km2 in urban environments), large coverage in harsh environments, and extremely long-life batteries (15 years) for low-cost devices.
[0092] Therefore, a set of OFDM parameters (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is suitable for one use case may not be suitable for another use case. For example, low latency services may preferably require shorter symbol durations compared to mMTC services, thereby requiring larger subcarrier spacing and / or fewer symbols per scheduling interval (also known as TTI). In addition, deployment scenarios with large channel delay spread may preferably require longer CP durations than scenarios with short delay spread. The subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR can support more than one subcarrier spacing value. Accordingly, subcarrier spacings of 15kHz, 30kHz, and 60kHz are also now being considered. Symbol duration T u and subcarrier spacing A f By formula A f =1 / T u In a similar manner as in the LTE system, the term "resource element" may be used to denote a minimum resource unit consisting of one subcarrier of one OFDM / SC-FDMA symbol length.
[0093] In the new radio system 5G-NR, for each parameter set and carrier, a resource grid of subcarriers and OFDM symbols is defined for uplink (UL) and downlink (DL), respectively. Each element in the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211v16.0.0, e.g. Section 4). For example, downlink (DL) and uplink (UL) transmissions are organized into frames of 10ms duration, each of which consists of ten subframes of 1ms duration each. In the 5g NR implementation, the number of consecutive OFDM symbols per subframe depends on the subcarrier spacing configuration. For example, for a subcarrier spacing of 15kHz, assuming a normal cyclic prefix, the subframe has 14 OFDM symbols, similar to an implementation compliant with LTE. On the other hand, for a subcarrier spacing of 30kHz, the subframe has two slots, each of which includes 14 OFDM symbols.
[0094] Radio Resource Control (RRC)
[0095] The Radio Resource Control (RRC) protocol is used for the air interface. The main functions of the RRC protocol include connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility procedures, paging notification and release, and outer loop power control. Through the signaling function, RRC configures the user plane and control plane according to network conditions and allows the implementation of radio resource management strategies.
[0096] RRC services and functions
[0097] The main services and functions of the RRC sublayer include:
[0098] Broadcast system information related to AS and NAS
[0099] 5GC or NG-RAN initiates paging
[0100] Establishment, maintenance and release of the RRC connection between the user equipment (UE) and the NG-RAN, including
[0101] Addition, modification and release of carrier aggregation
[0102] Addition, modification and release of dual connectivity in NR or between E-UTRA and NR.
[0103] Security features, including key management
[0104] Establishment, configuration, maintenance and release of signalling radio bearers (SRBs) and data radio bearers (DRBs);
[0105] Mobility features, including:
[0106] Switching and context transfer
[0107] UE cell selection and reselection and control of cell selection and reselection
[0108] Inter-RAT mobility
[0109] QoS management function
[0110] UE measurement reporting and reporting control
[0111] Detection and recovery of radio link failures
[0112] • Transmitting NAS messages from UE to NAS or from NAS to UE.
[0113] The operation of the RRC is guided by a state machine, which defines certain specific states that the UE may be in. Different RRC states in this state machine have different amounts of radio resources associated with them, and these are the resources that can be used when the UE is in a given specific state.
[0114] RRC states in 5G New Radio (5GNR)
[0115] In addition to the RRC connected and RRC IDLE states, 5G NR introduces a new RRC state called the RRC inactive state.
[0116] NR-RRC CONNECTED
[0117] NR-RRC INACTIVE
[0118] NR-RRC IDLE
[0119] When the user equipment (UE) is powered on, it is in disconnected mode / idle mode and it can move to RRC connected by initial attach or connection establishment. If there is no activity from the user equipment (UE) for a short period of time, the user equipment can suspend its session by moving to RRC inactive and can move to RRC connected mode to resume its session.
[0120] The UE may move from the RRC connected or RRC inactive state to the RRC idle mode.
[0121] According to section 7.2 of the 38.300 specification, RRC supports the following states, which are characterized as follows.
[0122] RRC Idle Mode Operation:
[0123] PLMN selection
[0124] Broadcasting of system information
[0125] Cell reselection mobility
[0126] Mobile terminated data paging is initiated by 5GC
[0127] Paging in the mobile terminated data area is managed by 5GC
[0128] NAS-configured CN paging DRX
[0129] RRC Inactive Mode Operation:
[0130] Broadcasting of system information
[0131] Cell reselection mobility
[0132] Paging is initiated by NG-RAN (RAN paging)
[0133] RAN-based Notification Area (RNA) managed by NG-RAN
[0134] NG-RAN configured DRX for RAN paging
[0135] Establish 5GC–NG-RAN connection for UE (both C-plane and U-plane)
[0136] UE AS context is stored in NG-RAN and UE
[0137] NG-RAN knows the RNA to which the UE belongs
[0138] RRC connected mode operation:
[0139] Establish 5GC–NG-RAN connection for UE (both C-plane and U-plane)
[0140] UE AS context is stored in NG-RAN and UE
[0141] NG-RAN knows the cell to which the UE belongs
[0142] ·Transmit unicast data to / from UE
[0143] Network controlled mobility, including measurement
[0144] RRC state is a solution for system access, power saving and mobility optimization. 5G must support eMBB, URLLC and Massive IoT services at the same cost and energy consumption per area per day.
[0145] The services accessed and requested by the 5G system have different characteristics. The connection control of future services needs to be flexible and programmable. In order to meet these different service characteristics, it requires a new RRC state model.
[0146] To support URLLC services that transmit small packets requiring ultra-low latency and / or high reliability, MassiveIoT devices rarely wake up from power saving mode to transmit and receive small payloads.
[0147] The device needs to be in a low activity state and sporadically transmit uplink (UL) data and / or status reports with a small payload to the network.
[0148] The device requires periodic and / or sporadic downlink (DL) small packet transmissions. When the user equipment (UE) is in a connected state and sporadically transmits uplink (UL) data and / or status reports with small payloads to the network.
[0149] Smartphones and consumer devices, which may be eMBB User Equipment (UE), have periodic and / or sporadic uplink (UL) and / or downlink (DL) small packet transmissions and very high data rates.
[0150] 5G NR functional division between NG-RAN and 5GC
[0151] There is a functional division between NG-RAN and 5GC. The NG-RAN logical node is gNB or ng-eNB. 5GC has logical nodes AMF, UPF and SMF.
[0152] In particular, gNB and ng-eNB carry the following main functions:
[0153] Radio resource management functions, such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in uplink and downlink (scheduling);
[0154] · Perform IP header compression, encryption and integrity protection on data;
[0155] When the route to the AMF cannot be determined based on the information provided by the UE, the AMF is selected when the UE attaches;
[0156] Routing user plane data towards UPF(s);
[0157] Routing control plane information to the AMF;
[0158] Connection setup and release;
[0159] Scheduling and transmission of paging messages;
[0160] Scheduling and transmission of system broadcast information (from AMF or OAM);
[0161] Mobility and scheduling measurements and measurement reporting configuration;
[0162] Transport level packet marking in uplink;
[0163] Session management
[0164] Support network slicing;
[0165] CoS flow management and mapping to data radio bearers;
[0166] Support for UEs in RRC_INACTIVE state;
[0167] NAS message distribution function;
[0168] Radio access network sharing;
[0169] Dual connectivity;
[0170] Tight interworking between NR and E-UTRA.
[0171] The access and mobility management function (AMF) carries the following main functions: - Non-access stratum NAS signaling termination;
[0172] ○NAS signaling security;
[0173] ○Access layer AS security control;
[0174] ○ Inter-core CN node signaling for mobility between 3GPP access networks;
[0175] ○ Idle mode UE reachability (including control and execution of paging retransmissions);
[0176] ○Registration area management;
[0177] ○Support mobility within and between systems;
[0178] ○Access authentication;
[0179] ○ Access authorization, including checking roaming permissions;
[0180] ○ Mobility management control (subscription and policy);
[0181] ○Support network slicing;
[0182] ○Session management function SMF selection.
[0183] In addition, the user plane function UPF carries the following main functions:
[0184] ○ Anchor point for intra-RAT / inter-RAT mobility (if applicable);
[0185] ○ External PDU session point interconnected with the data network;
[0186] ○Packet routing and forwarding;
[0187] ○ User plane part of packet inspection and policy rule enforcement;
[0188] ○ Traffic usage report;
[0189] ○ Uplink classifiers that support routing of traffic flows to data networks;
[0190] ○Support branch points for multi-host PDU sessions;
[0191] ○ QoS handling in the user plane, e.g. packet filtering, gating, UL / DL rate enforcement;
[0192] ○ Uplink traffic verification (SDF to QoS flow mapping);
[0193] ○ Downlink packet buffering and downlink data notification triggering.
[0194] Finally, the session management function SMF carries the following main functions:
[0195] ○Session management;
[0196] ○UE IP address allocation and management;
[0197] ○Selection and control of UP function;
[0198] ○Configure traffic steering in the user plane function UPF to route the traffic to the correct destination;
[0199] ○Control part of policy implementation and QoS;
[0200] ○ Downlink data notification. RRC connection setup and reconfiguration process
[0201] Figure 2 It shows the downlink (DL) small data available to the base station (gNB) when the user equipment (UE) is in inactive mode (RRC_INACTIVE). This means that the user equipment (UE) stays in the inactive mode (RRC_INACTIVE) state and the downlink (DL) data is available on the base station (gNB) side. In this case, the definition of the user equipment (UE) is not set in a fixed way.
[0202] As already mentioned, RRC is a higher layer signaling (protocol) for configuration of the User Equipment (UE) and the Base Station (gNB). In particular, the transition involves the AMF preparing the User Equipment (UE) context data (including, for example, PDU session context, security keys, User Equipment (UE) radio capabilities and User Equipment (UE) security capabilities, etc.) and sending it to the Base Station (gNB) via an INITIAL CONTEXT SETUP REQUEST. The Base Station (gNB) then activates AS security with the UE, which is performed by the Base Station (gNB) transmitting a SecurityModeCommand message to the UE and the UE responding to the Base Station (gNB) with a SecurityModeComplete message. Afterwards, the Base Station (gNB) performs a reconfiguration to set up the Signaling Radio Bearer 2 SRB2 and (multiple) Data Radio Bearers DRB by transmitting an RRCReconfiguration message to the User Equipment (UE) and, in response, receiving an RRCReconfigurationComplete by the Base Station (gNB) from the User Equipment (UE). For pure signaling connections, since SRB2 and DRB are not set up, the steps related to RRCReconfiguration are skipped. Finally, the base station (gNB) notifies the AMF that the setup process is complete with INITIAL CONTEXT SETUP RESPONSE.
[0203] Therefore, in the present disclosure, there is provided an entity (e.g., AMF, SMF, etc.) of a 5th generation core (5GC), the entity comprising: a control circuit system, which establishes a next generation (NG) connection with a base station (gNB) in operation; and a transmitter, which transmits an initial context setup message to the base station (gNB) via the NG connection in operation to trigger a signaling radio bearer setup between the base station (gNB) and the user equipment (UE). In particular, the base station (gNB) transmits a radio resource control RRC signaling including a resource allocation configuration information element to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation configuration.
[0204] From a physical layer perspective, reliability can be improved in a number of possible ways. The current scope for improving reliability includes defining a separate CQI table for URLLC, more compact DCI formats, repetition of PDCCH, etc. However, as NR becomes more stable and developed (for NR URLLC key requirements), the scope for achieving ultra-reliability is likely to expand. Specific use cases for NR URLLC in Rel.15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.
[0205] In addition, the technical enhancements targeted by NR URLLC are aimed at improving latency and increasing reliability. Technical enhancements for improving latency include configurable parameter sets, non-slot-based scheduling with flexible mapping, unauthorized (configured authorization) uplinks, slot-level repetition of data channels, and downlink preemption. Preemption means that the transmission for which resources have been allocated is stopped, and the allocated resources are used for another transmission that is requested later but has lower latency / higher priority requirements. Therefore, the authorized transmission is preempted by the later transmission. The applicability of preemption is independent of the specific service type. For example, a transmission of service type A (URLLC) may be preempted by a transmission of service type B (such as eMBB). Technical enhancements for improving reliability include a dedicated CQI / MCS table for a target BLER of 1E-5.
[0206] The use case of mMTC (Massive Machine Type Communications) is characterized by a very large number of connected devices that typically transmit relatively small amounts of non-delay-sensitive data. The devices are required to be low cost and have very long battery life. From the NR perspective, utilizing very narrow bandwidth portions is a possible solution to achieve power savings and extend battery life from the UE perspective.
[0207] As mentioned above, the scope of reliability in NR is expected to become wider. A key requirement for all cases, especially for URLLC and mMTC, is high or ultra-reliability. Several mechanisms can be considered to improve reliability from both a radio perspective and a network perspective. In general, there are several key potential areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity in frequency, time, and / or spatial domains. These areas apply to general reliability regardless of the specific communication scenario.
[0208] For NR URLLC, other use cases with more stringent requirements have been identified, such as factory automation, transportation industry, and power distribution. The more stringent requirements are higher reliability (up to 106), higher availability, packet size up to 256 bytes, time synchronization down to a few picoseconds (where this value can be one or several picoseconds, depending on the frequency range), and short latency on the order of 0.5 to 1 ms (specifically a target user plane latency of 0.5 ms, depending on the use case).
[0209] In addition, for NR URLLC, several technical enhancements have been identified from a physical layer perspective. These include PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. In addition, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. In addition, PUSCH enhancements related to mini-slot level frequency hopping and retransmission / repetition enhancements have been identified. The term "mini-slot" refers to a transmission time interval (TTI) that includes fewer symbols than a slot (a slot including fourteen symbols).
[0210] QoS Control
[0211] The 5G QoS (Quality of Service) model is based on QoS flows and supports QoS flows that require guaranteed flow bit rates (GBR QoS flows) and QoS flows that do not require guaranteed flow bit rates (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the finest granularity of QoS differentiation in a PDU session. QoS flows are identified within a PDU session by the QoS Flow ID (QFI) carried in the encapsulation header on the NG-U interface.
[0212] For each UE, the 5GC establishes one or more PDU Sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) together with the PDU Session, and may subsequently configure (multiple) additional DRBs for (multiple) QoS flows of that PDU Session (NG-RAN decides when to do so). The NG-RAN maps packets belonging to different PDU Sessions to different DRBs. NAS-level packet filters in the UE and 5GC associate UL packets and DL packets with QoS flows, while AS-level mapping rules in the UE and NG-RAN associate UL QoS flows and DL QoS flows with DRBs.
[0213] TS 23.501v16.3.0 Section 4.2.3 describes the 5G NR non-roaming reference architecture. Exemplarily, an application function (AF), for example, an external application server hosting 5G services. Interacts with the 3GPP core network to provide services, such as supporting the impact of applications on traffic routing, accessing the network exposure function (NEF), or interacting with the policy framework for policy control (see policy control function PCF) (e.g., QoS control). Based on operator deployment, application functions trusted by the operator may be allowed to interact directly with related network functions. Application functions that the operator does not allow direct access to network functions interact with related network functions using an external exposure framework via NEF.
[0214] The functional units of the 5G architecture are well known, namely, Network Slice Selection Function (NSSF), Network Repository Function (NRF), Unified Data Management (UDM), Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF) and Data Network (DN), such as operator services, Internet access or 3rd party services. All or part of the core network functions and application services can be deployed and run in a cloud computing environment.
[0215] Therefore, in the present disclosure, an application server (e.g., AF of 5G architecture) is provided, which includes: a transmitter, which transmits a request containing QoS requirements of at least one of URLLC service, eMBB service and mMTC service to at least one function of 5GC (e.g., NEF, AMF, SMF, PCF.UPF, etc.) in operation, so as to establish a PDU session including radio bearer between gNodeB and UE according to the QoS requirement; and a control circuit system, which performs service using the established PDU session in operation.
[0216] Random access process
[0217] Similar to LTE, 5G NR provides a RACH (Random Access Channel) procedure (or simply the Random Access Procedure). For example, a UE can use the RACH procedure to access a cell it has found. The RACH procedure can also be used in other contexts within NR, such as:
[0218] · For handover when synchronization to a new cell is to be established;
[0219] Used to re-establish uplink synchronization with the current cell if synchronization is lost due to the absence of any uplink transmission from the device for too long;
[0220] If no dedicated scheduling request resource is configured for the device, it is used to request uplink scheduling.
[0221] There are many events that may trigger the UE to perform a random access procedure, as described in 3GPP TS 38.300 v16.0.0 section 9.2.6.
[0222] If the uplink transmission of the mobile terminal is time synchronized, the mobile terminal can be scheduled for uplink transmission. Therefore, the random access channel (RACH) process acts as an interface between an unsynchronized mobile terminal (UE) and the orthogonal transmission of the uplink radio access. For example, random access is used to achieve uplink time synchronization for user equipment that has not yet acquired or has lost its uplink synchronization. Once the user equipment has achieved uplink synchronization, the base station can schedule uplink transmission resources for it. A scenario related to random access is that a user equipment in the RRC_CONNECTED state switches from its current serving cell to a new target cell and performs a random access procedure to achieve uplink time synchronization in the target cell.
[0223] There may be two types of random access procedures, allowing contention-based access, meaning there is an inherent risk of collision, or contention-free access (non-contention-based).An exemplary definition of a random access procedure may be found in 3GPP TS 38.321 v15.8.0, section 5.1.
[0224] The RACH procedure will be described in more detail below. The procedure consists of four "steps" and can therefore be referred to as, for example, a 4-step RACH procedure. First, the user equipment transmits a random access preamble to the base station on the physical random access channel (PRACH) (i.e., message 1 of the RACH procedure). After the base station detects the RACH preamble, it sends a random access response (RAR) message on the PDSCH (physical downlink shared channel) (message 2 of the RACH procedure), which is addressed on the PDCCH, where the (random access) RA-RNTI identifies the time-frequency and time slot in which the preamble was detected. If multiple user equipment transmit the same RACH preamble in the same PRACH resource (this is also called a collision), they will receive the same random access response message. The RAR message can convey the detected RACH preamble, a timing alignment command (TA command) for synchronizing subsequent uplink transmissions based on the timing of the received preamble, an initial uplink resource assignment (grant) for the transmission of the first scheduled transmission, and an assignment of a temporary cell radio network temporary identifier (T-CRNTI). The base station uses this T-CRNTI to address the mobile station(s) whose RACH preamble was detected until the end of the RACH procedure, since the base station does not yet know the "real" identity of the mobile station.
[0225] The user equipment monitors the PDCCH within a given time window (e.g., referred to as the RAR reception window) to receive a random access response message, which time window may be configured by the base station. In response to the RAR message received from the base station, the user equipment transmits a first scheduled uplink transmission on the radio resources assigned by the grant in the random access response. The scheduled uplink transmission conveys an actual message with a specific function, such as an RRC connection request, an RRC recovery request, or a buffer status report.
[0226] In the event of a preamble collision in the first message of the RACH procedure (i.e., multiple user equipments have sent the same preamble on the same PRACH resource), the colliding user equipments will receive the same T-CRNTI in the random access response and will also collide in the same uplink resource when transmitting their scheduled transmissions in the third step of the RACH procedure. If the scheduled transmission from one user equipment is successfully decoded by the base station, the contention for (multiple) other user equipments remains unresolved. To resolve this type of contention, the base station sends a contention resolution message (fourth message) addressed to the C-RNTI or temporary C-RNTI. The process ends here.
[0227] The base station provides the user equipment with a dedicated preamble for random access in the first step, so that there is no risk of collision (i.e., multiple user equipments transmit the same preamble). Therefore, the user equipment will then send the preamble signaled by the base station on the PRACH resource in the uplink. Since the situation where multiple UEs send the same preamble is avoided for contention-free random access, the contention-free random access process is basically over after the UE successfully receives the random access response.
[0228] 3GPP is also studying a 2-step (contention-based) RACH procedure for 5G NR, where message 1 (called MSGA) is first transmitted, which corresponds to messages 1 and 3 in the four-step LTE / NR RACH procedure. The 2-step RACH type MSGA includes a preamble on the physical random access channel (PRACH) and a payload on the physical uplink shared channel (PUSCH). After the MSGA transmission, the UE monitors for a response from the base station (gNB) within a configured time window. The base station (gNB) will then respond with message 2 (called MSGB), which corresponds to messages 2 and 4 of the 4-step LTE / NR RACH procedure. This msgB may include, for example, a successful random access response (RAR), a fallback RAR, and an optional backoff indication. If contention resolution is successful after receiving a successful RAR, the UE ends the random access procedure; whereas, if a fallback RAR is received in the MSGB, the UE performs message 3 transmission (as in the 4-step RACH procedure) and monitors contention resolution. Some further exemplary assumptions are made for the 2-step RACH procedure, such as the UE, after deciding on the RACH type (e.g., 2-step RACH), continues to retry the same RACH type until failure. However, there may also be a possibility that the UE may switch to the 4-step RACH procedure after some retries of transmitting the MSGA.
[0229] In addition, the network may semi-statically determine the radio resources to be used to perform the mutually exclusive 2-step RACH procedure and the 4-step RACH procedure. The radio resources used to transmit the first message in the RACH procedure include at least the RACH opportunity and the preamble. For example, in the 2-step RACH procedure, the first message msgA uses not only the PRACH resources (e.g., the RACH opportunity and the preamble) but also the associated PUSCH resources.
[0230] UE Identification
[0231] RNTI stands for Radio Network Temporary Identifier. For example, RNTI can be used to distinguish and identify UEs in a radio cell. In addition, RNTI can also identify a specific radio channel, a group of UEs in the case of paging, a group of UEs for which the eNB issues power control, and system information transmitted by the 5G base station (gNB) for all UEs. 5G NR defines many different identities for UEs, some of which are shown in the following table (see 3GPP TS 38.321v15.8.0, section 7.1).
[0232]
[0233]
[0234] In addition to the above-mentioned RNTIs, there may be other IDs, such as Inactive-RNTI (I-RNTI) (see TS38.331v15.8.0, e.g., Section 6.3.2). Inactive-RNTI is used for UEs in RRC_INACTIVE state, for example, in the process of identifying and locating the suspended UE context of the UE. According to one embodiment, the network assigns an I-RNTI when the UE (e.g., from RRC_CONNECTED) moves to the RRC_INACTIVE state (e.g., as part of an RRCRelease message within SuspendConfig). There are two types of I-RNTIs, namely, full I-RNTI and short I-RNTI. The network can notify the UE (e.g., as part of SIB1, System Information Block 1) which I-RNTI to use when resuming the connection. The full I-RNTI is a bit string with a length of 40 bits, while the short I-RNTI is a bit string with a length of 24 bits.
[0235] RRC status (RRC_Connected, RRC_Inactive)
[0236] In LTE, the RRC state machine consists of only two states: the RRC idle state, which is mainly characterized by high power saving, UE autonomous mobility and no connection between the UE and the core network; and the RRC connected state, in which the UE can send user plane data while the network controls mobility to support lossless service continuity. In relation to 5G NR, the LTE-related RRC state machine can also be extended to have an inactive state (see, for example, TS 38.331v15.8.0, Figure 4 .2.1-2), similar to NR 5G explained below.
[0237] RRC in NR 5G (see TS 38.331v15.8.0, Section 4) supports the following three states: RRC Idle, RRC Inactive and RRC Connected. When an RRC connection is established, the UE is in the RRC_CONNECTED state or the RRC_INACTIVE state. If this is not the case, i.e., no RRC connection is established, the UE is in the RRC_INACTIVE state. The following state transitions are possible:
[0238] From RRC_INACTIVE to RRC_CONNECTED, following, for example, the "Connection Establishment" procedure;
[0239] From RRC_CONNECTED to RRC_IDLE, following, for example, the "Connection Release" procedure;
[0240] From RRC_CONNECTED to RRC_INACTIVE, follow, for example, the "Connection Release Suspend" procedure;
[0241] From RRC_INACTIVE to RRC_CONNECTED, following, for example, the "Connection Recovery" procedure;
[0242] From RRC_INACTIVE to RRC_IDLE (one-way), following, for example, the "Connection Release" procedure.
[0243] The new RRC state RRC Inactive is defined for the new radio technology of 5G 3GPP to provide benefits in supporting a wider range of services such as eMBB (enhanced mobile broadband), mMTC (massive machine type communication) and URLLC (ultra-reliable and low latency communication) which have very different requirements in terms of signaling, power saving, latency, etc. Therefore, the design of the new RRC Inactive state should allow minimizing signaling, power consumption and resource costs in the radio access network and the core network while still allowing, for example, data transfer to start with low latency.
[0244] According to an exemplary 5G NR implementation, the different states are characterized as follows (see Section 4.2.1 of TS 38.331):
[0245] RRC_IDLE:
[0246] -UE-specific DRX can be configured by upper layers;
[0247] - UE controlled mobility based on network configuration;
[0248] -UE:
[0249] - monitoring short messages transmitted via DCI using P-RNTI (see clause 6.5);
[0250] -Monitor the paging channel for CN paging using 5G-S-TMSI;
[0251] -Perform neighbor cell measurements and cell (re)selection;
[0252] - Gets system information and can send SI requests (if configured).
[0253] RRC_INACTIVE:
[0254] -UE-specific DRX can be configured by upper layers or RRC layer;
[0255] - UE controlled mobility based on network configuration;
[0256] -UE stores UE inactive AS context;
[0257] -RAN-based notification area is configured by the RRC layer;
[0258] UE:
[0259] - monitoring short messages transmitted via DCI using P-RNTI (see clause 6.5);
[0260] -Monitor the paging channel for CN paging using 5G-S-TMSI and RAN paging using full I-RNTI;
[0261] -Perform neighbor cell measurements and cell (re)selection;
[0262] -Perform RAN-based notification area updates periodically and upon movement outside the configured RAN-based notification area;
[0263] - Gets system information and can send SI requests (if configured).
[0264] RRC_CONNECTED:
[0265] -UE stores the AS context;
[0266] -Transmit unicast data to / from UE;
[0267] - At lower layers, the UE may be configured with UE-specific DRX;
[0268] -For UEs supporting CA, one or more SCells aggregated with SpCell are used to increase bandwidth;
[0269] -For UEs supporting DC, use one SCG aggregated with the MCG to increase bandwidth;
[0270] - Network controlled mobility within NR and to / from E-UTRA;
[0271] -UE:
[0272] - monitoring of short messages transmitted over DCI using P-RNTI (see clause 6.5), if configured;
[0273] - monitoring a control channel associated with a shared data channel to determine whether data is scheduled for it;
[0274] -Provide channel quality and feedback information;
[0275] -Perform neighbor cell measurements and measurement reporting;
[0276] -Get system information.
[0277] According to the characteristics of the RRC Inactive state, for an inactive UE, the connection with the RAN and the core network is maintained for both the user plane and the control plane. More specifically, in RRC Inactive, although the connection still exists, it is suspended, or in other words, the connection is no longer active. On the other hand, in the RRC Connected state, the connection exists and is active, for example in the sense that it is used for data transmission. In the RRC Idle state, the UE has no RRC connection with the RAN and the core network, which also means that for example the radio base station does not have any context for the UE and for example does not know the identity of the UE and has no security parameters related to the UE and therefore cannot correctly decode the data transmitted by the UE (security, for example ensuring the integrity of the transmitted data). The UE context may be available in the core network, but must first be acquired by the radio base station.
[0278] In addition, the paging mechanism (also referred to as, for example, a notification mechanism) for user equipment in the radio cell is based on a so-called notification area (RNA for short) based on the radio access network RAN. The radio access network should know the current RNA where the user equipment is located, and the user equipment can assist the base station (gNB) to track the UE moving between various RNAs. The RNA can be UE-specific.
[0279] An example of a subsequent RRC connection release procedure for transitioning to the RRC Inactive state is explained below (see TS 38.331 v15.8.0 section 5.3.8).
[0280] The purpose of this procedure is to release the RRC connection or suspend the RRC connection. For example, the network initiates the RRC connection release procedure to transition the UE in RRC_CONNECTED to RRC_IDLE or RRC_INACTIVE. The actions performed by the UE on the RRC connection release procedure disclosed in Section 5.3.8.3 of TS 38.331 include suspending all (multiple) SRBs (signaling radio bearers) and (multiple) DRBs (data radio bearers) except SRBO (if the release is completed by suspension (e.g., "RRC release includes suspendConfig")). Accordingly, a UE in RRC inactive state does not have any non-suspended or active DRBs (only suspended DRBs). The SRBO that remains active even in the RRC_INACTIVE state can be used by the UE, for example, to perform RACH procedures, for example, when carrying RRC messages such as RRCResumeRequest, RRCResumeRequest1, RRCSetupRequest.
[0281] In an exemplary embodiment in 5G NR, a signaling radio bearer (see TS 38.331v15.8.0 Section 4.2.2) is defined as a radio bearer used only for the transmission of RRC and NAS messages and may include SRBO (for RRC messages using CCCH logical channels), SRB1, SRB2, and SRB3. In an exemplary embodiment of 5G NR (see TS38.300v16.0.0 Section 12.1), the NG-RAN establishes at least one DRB together with the PDU session and may subsequently configure (multiple) additional DRBs for (multiple) QoS flows of the PDU session. The NG-RAN then maps packets belonging to different PDU sessions to different DRBs. The NG-RAN and 5GC ensure quality of service (e.g., reliability and target delay) by mapping packets to appropriate QoS flows and DRBs. In other words, DRBs are used to carry user data associated with a PDU session.
[0282] An overview of how the radio bearers related to logical channels, transport channels and different QoS flows are defined for downlink and uplink respectively can be found in 3GPP TS 38.300v16.0.0 section 6.1 where you can find the layer 2 architecture for downlink and uplink describing:
[0283] The physical layer provides transport channels to the MAC sublayer;
[0284] The MAC sublayer provides logical channels to the RLC sublayer;
[0285] The RLC sublayer provides RLC channels to the PDCP sublayer;
[0286] The PDCP sublayer provides radio bearers to the SDAP sublayer;
[0287] The SDAP sublayer provides QoS flows to the 5GC;
[0288] Comp refers to header compression, and segm. refers to segmentation;
[0289] • Control channels (PCCH, BCCH not depicted for clarity).
[0290] Radio bearers are divided into two groups: Data Radio Bearers (DRBs) for user plane data and Signalling Radio Bearers (SRBs) for control plane data.
[0291] Small data transfer
[0292] The characteristics of small data transmission targeted in this disclosure refer to any service with the following characteristics: data bursts in UL / DL are small and optionally quite infrequent, with no strict requirements on latency. The following table lists typical non-limiting examples of traffic characteristics (see TR 25.705v13.0.0 Section 5).
[0293] Characteristics of small data transmission
[0294]
[0295] Small data transmission of UE in RRC inactive state
[0296] The present invention provides an improved procedure that allows a UE in an RRC inactive state to transmit data, such as small data, and more specifically, does not require a change in the UE state.
[0297] In more detail, 5G NR supports the RRC_INACTIVE state, and UEs with infrequent (periodic and / or aperiodic) data transmissions are usually kept in the RRC_INACTIVE state by the network. Prior to Rel-16, the RRC_INACTIVE state did not support data transmission. Therefore, the UE had to restore the connection, for example, move to the RRC_CONNECTED state for any DL (mobile terminated) and UL (mobile originated) data. Every data transmission, no matter how small and infrequent the data packet is, requires a connection setup (or recovery) and subsequent release to the INACTIVE state. This results in unnecessary power consumption and signaling overhead.
[0298] Specific examples where data traffic is small and infrequent include the following use cases:
[0299] Smartphone App:
[0300] ○ Traffic from instant messaging services (WhatsApp, QQ, WeChat, etc.)
[0301] ○ Heartbeat / keep-alive traffic from IM / email clients and other apps
[0302] ○Push notifications from various apps
[0303] Non-smartphone applications:
[0304] ○Traffic from wearable devices (regular location information, etc.)
[0305] ○ Sensors (industrial wireless sensor networks that transmit temperature, pressure readings, etc. periodically or in an event-triggered manner)
[0306] ○Smart meters and smart meter networks send regular meter readings
[0307] An exemplary procedure of the prior art enabling a UE in the RRC Inactive state to transmit (small) data will be briefly explained, which in this case is a prior art solution compliant with 5G NR. It is assumed that the UE is in RRC_Inactive, which means that all data radio bearers of the UE and the base station (gNB) are suspended and no data can be transmitted to the base station (gNB). In order to enable the UE to transmit data, the UE must first transition to the RRC Connected state, which can be done by the UE requesting to resume the RRC connection (here transmitting RRCResumeRequest) as part of a RACH procedure (e.g., using a 4-step RACH procedure). In detail, the UE can transmit a preamble to the current gNB and then receive a corresponding random access response (with a small amount of UL radio resource grant), which the UE uses to transmit a RRCResumeRequest message as msg3 of the RACH procedure.
[0308] Assume that the UE moves from its previous anchor base station (gNB) to a new base station (gNB). Therefore, the new base station (gNB) does not yet have the appropriate context for the UE and must first obtain these contexts from the anchor base station (gNB).
[0309] Finally, the new base station (gNB) provides the UE with an RRC Resume message, and the UE then transitions to the RRC Connected state, including resuming all data radio bearers. In the RRC_Connected state, the UE is then able to transmit UL data.
[0310] Transitioning to the connected state before the UE can send any user data introduces latency and each transmission of user data consumes significant UE power.
[0311] In addition, the signaling overhead of small data packets from INACTIVE state UEs is a common problem, and with the increase of UEs in 5G NR, it will become a critical issue, affecting not only network performance and efficiency, but also UE battery performance. In general, any device that has intermittent small data packets in the INACTIVE state will benefit from enabling small data transmission in the INACTIVE state.
[0312] In 3GPP, no final agreement has been reached on a standardized method how to implement (small) data transfer for UEs staying in RRC inactive state. The inventors have identified the possibility to complete and / or improve the mechanisms and procedures involved in enabling UEs to transfer data while in RRC inactive state.
[0313] The task of the present invention is to overcome the problems listed and described, which involve that when a DL small data transmission is in progress and if during the process the UE wants to initiate an UL data transmission (which can be UL small data or UL non-small data), the current UE behavior and process will be set to a defined state.
[0314] Figure 3 A proposed inventive solution is provided.
[0315] Figure 4 The configuration of a random access channel (RACH) resource for each synchronization signal block (SSB) by the base station (gNB) is shown.
[0316] Generally speaking, when the network (NW) is congested, the conflicts between user equipments (UE) will increase and will cause the RACH procedure to fail. Therefore, for SDT UE, the signaling overhead as well as the power consumption will increase. SS Block (SSB) stands for Synchronization Signal Block, actually it refers to the Sync / PBCH Block, because the Sync signal and PBCH channels are packed into a single block that always moves together. The components of this block are as follows:
[0317] Synchronous signal:
[0318] PSS (primary synchronization signal), SSS (secondary synchronization signal)
[0319] PBCH:
[0320] PBCH DMRS and PBCH (data)
[0321] These are just two of the main components of the SS block, which carries a lot of detail.
[0322] Each SSB has an index that increases from 0 to Lmax.–1. The period (20 ms) can vary between 5 ms and 160 ms (5, 10, 20, 40, 80, 160 ms). The 3GPP standard recommends using a period of 20 ms for cell-defined SSBs. Higher periods (such as 80 ms or 160 ms) are preferably used for SSBs in mmWave networks to leave more time for transmitting a larger number of SSBs.
[0323] To reduce signaling overhead, the base station (gNB) can schedule downlink transmissions without requiring the user equipment (UE) to be in a connected state. To this end, the user equipment (UE) can be scheduled using predefined cells and beams used for previous transmissions. The user equipment (UE) can receive this information in a dedicated RRC message or a paging message.
[0324] If the user equipment (UE) determines that its current beam position is aligned with the preconfigured cell / beam, it does not trigger RA-SDT or CG-SDT. The user equipment (UE) will receive DL data after the configuration time on the predefined cell / beam expires.
[0325] The following description of the improved process for data transmission by a user equipment (UE) in an RRC inactive state focuses on the transmission of small data defined in the previous 5G NR study items and protocols. However, the present invention should not be limited to this, and when it is intended to transmit more data or other data than the small data generally considered, the present invention should also be applicable and follow the same principles listed below for small data transmission.
[0326] In the following, user equipment (UE), base stations (gNBs), and processes that meet these requirements will be described for new radio access technologies envisioned for 5G or 6G mobile communication systems, but the technology can also be used for LTE mobile communication systems. Different implementations and variants will also be explained. The discussions and findings described above facilitate the following disclosures, and the following disclosures may, for example, be based at least in part on these discussions and findings.
[0327] In summary, it should be noted that in order to be able to explain the basic principles of the present disclosure in a clear and understandable manner, many assumptions are made herein. However, these assumptions should be understood as examples made herein for illustrative purposes only and should not limit the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the following disclosure and the principles set forth in the claims can be applied to different scenarios and can be applied in ways that are not explicitly described herein.
[0328] In addition, some of the terms for processes, entities, layers, etc. used below are closely related to the terms used in the LTE / LTE-A system or the current 3GPP 5G standardization, although the specific terms used in the context of the new radio access technology of the next 3GPP 5G communication system have not yet been fully determined or may eventually change. Therefore, the terms may change in the future without affecting the functionality of the embodiments.
[0329] Therefore, those skilled in the art will appreciate that, due to the lack of updated or finally agreed-upon terms, these embodiments and their scope of protection should not be limited to the specific terms used illustratively herein, but should be more broadly understood based on the functions and concepts that form the basis of the functions and principles of the present disclosure.
[0330] For example, a mobile station or mobile node or user terminal or user equipment (UE) is a physical entity (physical node) within a communication network. A node may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a set of predetermined functions to other functional entities of the same or another node or network. A node may have one or more interfaces that attach the node to a communication facility or medium through which the node can communicate. Similarly, a network entity may have a logical interface that attaches the functional entity to a communication facility or medium through which the functional entity can communicate with other functional entities or communication nodes.
[0331] The term "base station" or "radio base station" here refers to a physical entity within a communication network. Like a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a set of predetermined functions to other functional entities of the same or another node or network. The physical entity performs some control tasks related to the communication device, including one or more of scheduling and configuration. Note that the base station functionality and the communication device functionality can also be integrated in a single device. A mobile terminal can also implement the functionality of a base station for other terminals. The terminology used in LTE is eNB (or eNodeB), while the terminology currently used in 5G NR is gNB-Base Station (gNB).
[0332] The term "data connection" as used herein may be understood as a connection over which data (e.g., small data) may be transmitted, e.g., between a user equipment (UE) and a radio base station. In more detail, a user equipment (UE) without a data connection, e.g., even if connected to a radio base station based on a signaling connection, cannot immediately transmit data. In this context, data may be broadly understood as user data, e.g., user data from an application running on the user equipment (UE), in contrast to, e.g., control information, which is more often transmitted using a signaling connection.
[0333] In an exemplary embodiment, according to the 5G NR standard, the data connection may be understood as a data radio bearer DRB, and the signaling connection may be understood as a signaling radio bearer SRB.
[0334] In some instances, the present application further distinguishes different conditions of data connections, such as non-existent, existing but suspended, existing but not used, which can also be referred to as non-suspended or inactive, and existing and currently used to transmit data can also be referred to as active. After this classification of data connections, a suspended data connection, although existing, cannot be used immediately to transmit data in the uplink (UL) because it is suspended by two endpoints (e.g., UE and radio base station) and needs to be resumed first. On the other hand, a non-suspended data connection can allow data transmission immediately, for example, without any further process, such as resuming the data connection.
[0335] For example, when referring to the exemplary 5G NR implementation currently defined in the 3GPP standard, a UE in the RRC inactive state will have one or more suspended data connections (DRBs are suspended); a UE in the RRC connected state may have one or more active data connections that are not currently in active use and possibly other non-suspended data connections; and a UE in the RRC idle state will have no data connection that is neither suspended nor active. On the other hand, according to the improved data transmission process explained below, unlike the 5G NR implementation currently defined in the 3GPP standard, a UE in the RRC inactive state will have one or more available non-suspended data connections, which will be inactive because no data is exchanged before the small data transmission.
[0336] In this case, the present application explains that, for example, UE uses a data connection to transmit small data. In the current scenario, a data connection is established between the UE and the base station. In an exemplary embodiment, the data connection should be broadly understood as being associated with certain parameters, which are related to coding, security, encryption, etc. Therefore, from the perspective of the transmission side, the UE applies these parameters associated with the data connection to the (small) data to be transmitted using the data connection. For example, this is done to ensure a specific quality of service. Accordingly, from the perspective of the receiving side, the receiver may need to apply processing opposite to the transmitting side (e.g., processing related to coding, security, encryption, etc.) in order to successfully decode data transmitted via the data connection.
[0337] Figure 4 A general, simplified and exemplary user equipment, also referred to as a communication device and a scheduling device, is shown, which is exemplarily assumed to be located in a base station (e.g., an eLTE eNB (alternatively referred to as ng-eNB) or a base station (gNB) in 5G NR). The UE and the eNB / gNB communicate with each other via a (wireless) physical channel using a transceiver, respectively.
[0338] The communication device may include a transceiver and a processing circuit system. The transceiver may include and / or act as a receiver and a transmitter. The processing circuit system may be one or more pieces of hardware, such as one or more processors or any LSI. There is an input / output point (or node) between the transceiver and the processing circuit system, through which the processing circuit system can control the transceiver when in operation, that is, control the receiver and / or transmitter and exchange receive / transmit data. As a transmitter and receiver, the transceiver may include an RF (radio frequency) front end, which includes one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuit system may implement control tasks, such as controlling the transceiver to transmit user data and control data provided by the processing circuit system and / or receiving user data and control data further processed by the processing circuit system. The processing circuit system may also be responsible for executing other processes, such as determining, deciding, calculating, measuring, etc. The transmitter may be responsible for executing the transmission process and other processes related thereto. The receiver may be responsible for executing the reception process and other processes related thereto (such as monitoring channels). An improved data transmission process will be described below. In said connection, an improved UE participating in an improved data transmission procedure is presented. Furthermore, an improved radio base station participating in the improved data transmission procedure is presented. Corresponding methods for UE behavior and base station behavior are also provided.
[0339] Figure 5 It is shown that a base station (gNB) configures more than one random access channel (RACH) resource for each synchronization signal block (SSB). The base station (gNB) configures more than one RACH resource for each SSB. The mapping of RACH resources is based on one of the following possible options:
[0340] Option 1: Priority (P1)
[0341] P1->RACH resource 1
[0342] P2->RACH resource 2
[0343] P3->RACH resource 3
[0344] Option 2: Group ID
[0345] Group ID 1 -> RACH resource 1
[0346] Group ID 2 -> RACH resource 2
[0347] Group ID 3 -> RACH resource 3
[0348] The mapping mentioned above is done through system information or dedicated RRC messages. The base station (gNB) indicates the priority / group ID in the paging message, and the user equipment (UE) selects the random access channel (RACH) resources accordingly. The base station (gNB) can change the number of random access channel (RACH) resources based on the overall load situation.
[0349] As an example, if the base station (gNB) indicates priority P1 in the paging message, the user equipment (UE) selects RACH resource 1 to perform the RACH process.
[0350] Similarly, if the base station (gNB) indicates group ID 3 in the paging message, the UE selects random access channel (RACH) resource 3 to perform the random access channel (RACH) procedure.
[0351] Figure 5 A simplified and exemplary user equipment (UE) structure according to an exemplary solution of the improved data transmission process is also presented, and can be based on the combination of Figure 4 The invention is implemented by the explained general user equipment (UE) structure. Figure 4 and Figure 5 The various structural elements of the user equipment (UE) shown in the figure can be interconnected with each other, for example, using corresponding input / output nodes (not shown), for example, to exchange control data and user data and other signals. Although not shown, the user equipment (UE) may include further structural elements. The user equipment (UE) may include a transmission data determination circuit system, a user equipment (UE) identity determination circuit system and a corresponding non-cell specific user equipment (UE) ID and a cell specific user equipment (UE) ID, as well as a control message and a small data transmitter.
[0352] In the present case, as will become apparent from the disclosure below, the processing circuit system can therefore be configured, for example, to at least partially perform one or more of determining that a small data transmission is to be performed, determining which UE identifier is to be used for small data transmission, determining one of a non-cell-specific UE ID and a cell-specific UE ID, and the like.
[0353] Thus, the transmitter may be exemplarily configured to at least partially perform one or more of transmitting small data and transmitting a selected UE ID, etc.
[0354] The processor of the UE determines to perform the transmission of small data. Exemplarily, it is assumed that the UE is in an inactive state and has at least one active data connection to a radio base station controlling the radio cell where the UE is located. The UE is assigned at least a cell-specific UE identity and a non-cell-specific UE identity. The processor determines which UE identity is used for small data transmission based on whether the UE has moved from another radio cell to the current radio cell after switching to the inactive state. In the case where the UE has moved from another radio cell to the current radio cell, the processor determines that the non-cell-specific UE identity is used for small data transmission. In the case where the UE has not moved from another radio cell to the current radio cell, the processor determines that the cell-specific UE identity is used for small data transmission. The transmitter of the UE transmits a control message including the determined UE identity and transmits small data using one of the at least one data connection.
[0355] Figure 6 A flow chart of the provided user equipment (UE) side is shown.
[0356] The user equipment (UE) receives a priority or group ID indication from the base station (gNB). After the reception, the user equipment (UE) selects a random access channel (RACH) resource corresponding to the priority or group ID.
[0357] When the user equipment (UE) receives the paging message, it provides the current beam position to the base station (gNB). After that, the base station (gNB) schedules DL small data transmission to indicate the beam of the user equipment (UE). For example, the user equipment (UE) reports beam 3 when receiving the paging message from the base station (gNB).
[0358] According to the improved data transmission procedure discussed herein, the UE also has at least one data connection when in an inactive state, which data connection can then be used to transmit data to the radio base station in a subsequent procedure.
[0359] According to an exemplary embodiment, when the UE moves to an inactive state, the corresponding radio base station also maintains the data connection.
[0360] In addition, the UE may have several identifiers, such as a cell-specific UE ID and a non-cell-specific UE ID. The cell-specific UE ID may be assigned by the radio base station where the UE is located and may be primarily used for the radio cell. When the UE moves between different radio cells, each radio base station controlling the corresponding radio cell may assign a different cell-specific UE ID to the UE. In addition, according to an example, the cell-specific UE ID may also be dedicated to small data transmissions, so that it will be used by the UE (and BS) associated with small data transmissions, and not for other types of data transmissions. Alternatively or in addition, the cell-specific UE ID may be dedicated to the inactive state of the UE, so that it is used by the UE when the UE is in the inactive state, but not used when, for example, the UE is in a connected state or an idle state.
[0361] On the other hand, the non-cell-specific UE ID may be assigned, for example, by a base station (gNB) of the radio cell in which the UE is located or an entity of the core network (such as an access and mobility management function AMF), and may be valid in a larger geographical area (such as a public land mobile network PLMN) than the radio cell. In an exemplary embodiment, the non-cell-specific UE ID may include an identifier of the radio base station and an identifier of the UE. In addition, according to another example, the non-cell-specific UE ID may be dedicated to the inactive state of the UE, so that it is used by the UE when the UE is in the inactive state, but not used when, for example, the UE is in a connected state or an idle state.
[0362] Typically, a cell-specific UE ID is shorter than a non-cell-specific UE ID, because a cell-specific UE ID only needs to distinguish UEs located in the same radio cell, respectively, whereas a non-cell-specific UE ID needs to distinguish more UEs located in more than one radio cell.
[0363] At some point in time when the UE is in the inactive state, it is assumed that small data becomes available for transmission, so that the UE determines to perform a small data transmission. Small data transmission also involves determining which UE identity to use. This is performed by the UE based on the current radio cell in which the UE is located, and more specifically, based on whether the UE has moved from another radio cell to the current radio cell after transitioning to the inactive state. In other words, determining which UE ID to use for small data transmission depends on whether the UE's current radio cell is the same as the radio cell when transitioning to the current inactive state. For example, a UE in radio cell A when transitioning to the inactive state may move between radio cells, and when small data becomes available for transmission, the UE may now be in another radio cell B.
[0364] Although in this exemplary improved data transmission procedure the current radio cell will be the primary basis for determining which UE identity to use for the small data transmission, other variants and implementations of the improved data transmission procedure may use alternative or additional information as a basis.
[0365] According to the UE behavior illustrated in Figure 16, when the UE determines that the UE has moved from another radio cell to the current radio cell (e.g., the UE has changed radio cells while in an inactive state), the UE determines a non-cell-specific UE ID. Conversely, when the UE determines that the UE has moved from another radio cell to the current radio cell (e.g., the UE has stayed in the same radio cell while in an inactive state), the UE determines a cell-specific UE ID.
[0366] After determining the UE ID, the UE may then proceed to perform small data transmission, which includes transmitting a control message including the determined UE ID, and includes transmitting the small data itself. The transmission of the small data may use one of the at least one non-suspended data connections available to the UE in the inactive state.
[0367] A UE in an inactive state can perform data transmission without having to transition to a connected state. This helps avoid the disadvantages mentioned above. In particular, the improved data transmission process helps avoid delays, saves a lot of UE power, and reduces data overhead caused by the necessary state transitions in the prior art.
[0368] Furthermore, the improved data transmission procedure appropriately selects the UE ID for small data transmissions. In particular, when the UE stays in the same radio cell, a cell-specific UE ID that is shorter than the non-cell-specific UE ID is selected, so that the radio base station still knows the cell-specific UE ID. In the prior art, the UE may have used a non-cell-specific UE ID regardless of which radio cell the UE is currently located in. Therefore, the improved data transmission procedure benefits from the use of a shorter cell-specific UE ID when useful, so that fewer data bits have to be transmitted. On the other hand, the improved data transmission ensures that when the UE moves to another radio cell, the radio base station where the UE is located can correctly identify the UE by using the non-cell-specific UE ID.
[0369] Figure 7 A flowchart on the provided base station (gNB) side is shown.
[0370] The base station (gNB) configures more than one (RACH) resource. After this step, the base station (gNB) provides a mapping between priority and / or group ID and (RACH).
[0371] The base station may include a control message and small data receiver, and a small data decoding processing circuit system. In the present case, it will be apparent from the following disclosure that the processing circuit system may therefore be exemplarily configured to at least partially perform one or more of decoding small data, etc. Therefore, the receiver may be exemplarily configured to at least partially perform one or more of receiving small data and receiving a control message (which includes a UE ID).
[0372] The radio base station comprises a receiver that receives a control message including a UE identity from a user equipment UE. The receiver also receives small data from the UE using a data connection established with the UE. The UE is in an inactive state, wherein the UE identity is a cell-specific UE identity or a non-cell-specific UE identity. The processor decodes the small data using a UE context associated with the UE and the one data connection.
[0373] Accordingly, the improved radio base station facilitates receiving small data from a UE in an inactive state without having to switch the UE to a connected state, thereby facilitating avoiding disadvantages associated therewith. The UE transmits data to the base station using a corresponding data connection in the inactive state, and the base station receives and decodes the small data using the corresponding data connection at the base station side. According to an exemplary solution, when the UE is in an inactive state, the base station also maintains a data connection with the UE so as to be able to correctly receive and decode the small data.
[0374] Grounds for participation in the improved data transfer process Figure 7 The improved base station can be: 1) the same old radio base station that the UE has been connected to while in the inactive state (in short, the old BS case), or 2) a new radio base station to which the UE has moved from the previous radio base station while in the inactive state (in short, the new BS case). Part of the behavior of the improved radio base station depends on whether the base station is the same old base station or a new base station.
[0375] Assume illustratively that the UE is initially in a connected state, and at least one data connection is established between the UE and the base station. Eventually, the base station decides to switch the UE to an inactive state, and accordingly provides instructions in the described aspect to the UE, and the UE follows the instructions and switches to the inactive state. As explained above, the UE will also have an available data connection when in the inactive state.
[0376] according to Figure 6, assuming that eventually the small data becomes available for transmission. The UE checks whether an indication of a downlink (DL) data transmission is received. If the result of the check is that an indication is given, the UE sends uplink (UL) data after the downlink (DL) data transmission is completed. According to the improved data transmission process, the UE determines which UE ID is transmitted with the small data. In the aspect, the UE concludes that it is still in the same radio cell as when it was in an inactive state (i.e., no radio cell change occurred when it was in an inactive state). Therefore, the UE selects a cell-specific UE ID assigned by the current base station. Therefore, the base station is able to clearly identify the UE based on the cell-specific UE ID. The UE then transmits a corresponding control message, including the selected cell-specific UE ID, and uses the data connection to transmit the small data. In one example, the control message and the small data are transmitted together to the base station, wherein the data connection is not necessarily used to transmit the control message with the cell-specific UE ID. For example, the control message and the small data are transmitted together in the same transmission block, but a signaling connection for the control message and a data connection for the data are used.
[0377] Regarding the case where a radio cell change occurs during the inactive state of the UE. In the same way, the UE is initially in the connected state, with at least one data connection established between the UE and the base station. Eventually, the base station decides to transition the UE to the inactive state and accordingly provides instructions to the UE in said regard, which the UE follows and transitions to the inactive state. As explained before, the UE will also have a data connection available to the (old) base station when in the inactive state.
[0378] In the inactive state, it is assumed that the UE moves from the old base station to the radio cell of the new base station. It is further assumed that after the radio cell change, small data eventually becomes available for transmission and the UE continues to perform Figure 5 . Accordingly, the UE concludes that it is located in a different radio cell than the one in which it was when it transitioned to the inactive state. Therefore, according to the UE behavior discussed above, the UE selects a non-cell-specific UE ID, which allows the base station to unambiguously identify the UE. The UE transmits a corresponding control message including the selected non-cell-specific UE ID and transmits small data using the data connection.
[0379] However, from the perspective of the new base station, there is no data connection with the UE yet, because the UE was previously connected to the old base station, not to the new base station. In order to decode the small data, the new base station may contact the old base station to obtain the corresponding context(s) of the UE. The old base station may be determined based on the non-cell-specific UE ID received in the control message. The new base station may transmit a request to the old BS to obtain the UE context, and in return, may receive a response including the requested UE context(s) from the old base station. Typically, the UE context includes information such as coding, security and encryption parameters associated with the UE and a data connection that may be used to decode the small data.
[0380] The radio base station presented above operates with a UE to perform an improved data transmission procedure. The control message received from the UE may include a UE ID, which may be a cell-specific UE ID or a non-cell-specific UE ID. The cell-specific UE ID is an ID assigned by a radio base station to identify the UE in its radio cell, for example by the radio base station to which the UE is now transmitting small data or by another radio base station to which the UE was previously connected and thus assigned a cell-specific UE ID.
[0381] According to another exemplary variant of the improved data transmission process (which can be combined with other variants and embodiments of the improved data transmission process), a new timer is operated for the cell-specific UE ID, as explained below. The radio base station that assigns the cell-specific UE ID to the UE needs to reserve the cell-specific UE ID for the UE, so it cannot be used to identify another UE. Since the cell-specific UE ID is usually and advantageously short, about 16 bits, there may be a problem that there are not enough cell-specific UE IDs assigned to UEs that are or have been connected to the base station. Therefore, the UE ID validity timer can be operated by the UE and the base station to set a time period as a time limit for the base station to reserve the cell-specific UE ID for the UE after the UE does not actively use the cell-specific UE ID because the UE is in an inactive state.
[0382] According to an exemplary implementation of this variant, when the UE generally transitions to an inactive state, a new UE ID validity timer may be started.
[0383] The period of the new UE ID validity timer may be determined, for example, by the base station and then notified to the UE, for example, in a control message such as an RRC message. The determination of the base station may, for example, depend on the number of unreserved cell-specific UE IDs that are still available for assignment to the UE. For example, the new UE ID validity timer may be configured to expire after 1024 seconds; but other values of the timer are equally possible. Alternatively, the value of the UE ID validity timer may be fixed by the corresponding 3GPP standard and may be hard-coded into the UE and the base station.
[0384] After the UE ID validity timer of a specific cell-specific UE ID expires, the base station considers the expired cell-specific UE ID no longer associated with the UE, but considers it available for new assignment to another UE. Therefore, after expiration, the base station will not be able to identify the UE based on the expired cell-specific UE ID.
[0385] Instead, the UE also operates a UE ID validity timer, preferably synchronized with the base station, so as to know when the cell-specific UE ID expires on the base station side. The UE should not use an expired cell-specific UE ID when contacting the base station, because the base station will no longer associate the expired cell-specific UE ID with the correct UE.
[0386] This variant of the improved data transmission procedure (using the new UE ID validity timer) provides the advantage that the cell-specific UE ID is masked by the UE transitioning to the inactive state only for a limited, configurable amount of time. On the other hand, by still allowing the cell-specific UE ID to be valid for a period of time, the UE can use the cell-specific UE ID for procedures with the base station, such as the improved data transmission procedure discussed herein.
[0387] Therefore, other variants of the improved data transmission procedure take into account a new UE ID validity timer, as will become apparent from the following. In particular, the UE behavior for determining a suitable UE ID to be transmitted with small data may depend on the UE ID validity timer.
[0388] The difference of this embodiment lies in the additional process of starting the UE ID validity timer for the cell-specific UE ID and the additional check whether the UE ID validity timer of the cell-specific UE ID has expired. In short, the cell-specific UE ID shall not be used when it expires (e.g. when the corresponding UE ID validity timer expires). In the described case, the UE will select a non-cell-specific UE ID even if it is still in the same radio cell as when it transitioned to the inactive state, which means it is not the case of the same old radio cell.
[0389] The checking sequence for determining the UE ID to be selected based on the current radio cell and the UE ID validity timer is a possible example, and different implementations are likewise possible.
[0390] For example, the UE may first check whether the UE ID validity timer of the cell-specific UE ID has expired, and then check whether it is located in the same old radio cell or a new radio cell. In another different embodiment, the UE may first check whether the UE ID validity timer of the cell-specific UE ID has expired. Then, in the case where the UE ID validity timer has expired, the UE may directly determine to use the non-cell-specific UE ID without further checking whether the UE is located in the same old radio cell or a new radio cell.
[0391] According to a further improvement of the new UE ID validity variant of the improved data transmission procedure, after the UE receives a response related to small data transmission from the base station, the UE can restart the timer. After the base station responds to the small data transmission performed by the UE, the base station can restart the same timer. Therefore, in the case of the UE transmitting small data, the restart of the timer can extend the validity time.
[0392] According to a further improved variant of the improved data transmission method, the control message that has included the UE ID may further include an indication that small data is being transmitted together with the control message. This helps the base station to correctly receive and decode the small data transmitted by the UE. Otherwise, the base station may not expect the small data and will not perform corresponding processing to decode the small data. The feature of this variant is that the control message is shown as including a small data indication. In one example, the small data indication can be a bit.
[0393] A more specific implementation of the small data indication will be explained later in conjunction with a 5G NR-based implementation of the improved data transmission process, see small data cause and small data indication in RRC message and MAC message.
[0394] Alternatively, another variant of the improved data transmission method does not have to rely on the small data indication in the control message. In the variant, the base station may always be ready to transmit small data together with the control message from the UE in the case where the corresponding small data indication is not used in the control message. Therefore, the base station may have to decode the received signal. If the small data is indeed transmitted together with the control message, the base station will successfully decode the small data. On the other hand, if no small data is transmitted together with the control message, the base station will not be able to successfully decode any data.
[0395] According to a further variant of the improved data transmission process that can be combined with other variants and embodiments of the improved data transmission process, the base station can decide to transmit a response message back to the UE in response to receiving a control message and small data. The base station can, for example, decide the state that the UE should be in, for example, staying in an inactive state, changing to a connected or idle state. The decision of the base station can be based on, for example, one or more of the following items: whether the base station can successfully obtain the context of the UE, whether the transmitted small data is the end of a traffic burst (for example, there is no more small data transmission after the small data transmission), and the reason indicated in the control message. According to an example, the base station can determine that there is no more small data based on whether there is a buffer status report after the small data. The buffer status report indicates that further small data is available for transmission, which may be a reason for converting the UE to a connected state.
[0396] Therefore, the response message may include the corresponding UE state indication of the UE. The UE receives the response message and follows the instructions therein to maintain or change to the indicated state.
[0397] According to a further variant that may be used in addition to the other variants, in case the base station determines that the small data that has been transmitted is not the end of a traffic burst, the response message from the base station to the UE may also schedule radio resources for the UE, which the UE may use to transmit further small data to the base station.
[0398] According to a further variant that may be used in addition to other variants, the response message from the base station to the UE may also indicate a new cell-specific UE ID newly assigned to the UE by the base station. For example, in a scenario where the new base station becomes a new anchor base station for the UE, the new anchor base station may assign a new cell-specific UE ID to the UE for use when the UE is inactive in the radio cell of the new anchor base station. Upon receiving the new cell-specific UE ID, the UE may replace the old invalid cell-specific UE ID (assigned by the old base station) with the newly assigned cell-specific UE ID and use it in future communications with the new anchor base station.
[0399] A further variant that may be used in addition to the other variants concerns how to react to a situation in which the base station fails to correctly identify the UE based on a cell-specific UE ID received from the UE together with the small data. In particular, it is exemplarily assumed that the UE stays in the same radio cell when inactive, but the base station (gNB) releases the cell-specific UE ID after a period of time so that it is no longer reserved for and associated with the UE. Assuming that this release is not visible to the UE, the UE will select the cell-specific UE ID for the small data transmission because it correctly determines that it is still located in the same old radio cell. However, the base station (gNB) fails to correctly identify the received cell-specific UE ID and therefore fails to retrieve the relevant UE context for decoding the small data. In response, the base station (gNB) may transmit a response message to the UE indicating the failure, in response to which the UE may then transmit back the non-cell-specific UE ID. Based on the non-cell-specific UE ID, the base station can now continue to retrieve the UE context and decode the small data.
[0400] In a further exemplary variation thereof, the base station may newly assign a cell-specific UE ID to the UE, and accordingly notify the UE of the newly assigned cell-specific UE ID for future communications.
[0401] In the variants and embodiments of the improved data transfer procedure described so far, it is assumed that when the UE is in an inactive state, the UE has an available data connection, which data connection can then be used for small data transfers. This can be achieved in different ways.
[0402] Typically, when a UE is in a connected state, it will have several active data connections for exchanging data, and possibly other non-suspended data connections that are not currently in use but are still immediately available for use when needed.
[0403] According to an additional optional embodiment, when in the inactive state, the UE does not suspend at least one of these data connections established by the UE when in the connected state. In other words, the UE keeps at least one data connection unsuspended so that it is immediately available during the inactive state. The remaining data connections established by the UE in the connected state may be suspended by the UE when in the inactive state. For example, the UE may decide not to suspend one or more data connections associated with an application that may result in small data transfers when in the inactive state. In another example, the UE may decide not to suspend a data connection that is configured by the base station as a default data connection that meets the minimum QoS requirements.
[0404] The base station will operate in a corresponding manner, and will not suspend at least one of the data connections established with the UE when the UE is in the connected state. The data connection maintained as non-suspended by the base station and the UE should be the same to facilitate the successful transmission and decoding of small data transmitted using the common non-suspended data connection.
[0405] According to an additional optional implementation, when in an inactive state, the UE does not suspend any data connection established by the UE and the base station, that is, the UE keeps all data connections as non-suspended. The base station will operate in a corresponding manner, and when the UE is in a connected state, it will not suspend any data connection established with the UE. Accordingly, when the UE needs to transmit small data when in an inactive state, the UE selects a data connection suitable for the small data, and uses the selected data connection to carry the data to the base station. Therefore, the base station will be able to correctly receive and decode the small data received via the data connection selected by the UE.
[0406] According to an additional optional embodiment, when in an inactive state, the UE and the base station both suspend all data connections in a connection state established between them. However, when in an inactive state, one or more new data connections may be created between the UE and the base station, and these data connections remain in a non-suspended state when the UE is in an inactive state. For example, a new data connection dedicated to small data transmission that may occur when the UE is in an inactive state may be created, for example, and the corresponding parameters associated with the new data connection are tailored for small data transmission.
[0407] The new data connection may also be implemented as a default inactive state specific data connection, available in a UE in an inactive state. For example, as defined by the 3GPP technical standard, parameters and settings related to the default data connection are hard-coded in the UE. Then, when the UE transitions to an inactive state, the UE and the base station may automatically create the default data connection using these parameters and settings.
[0408] According to additional optional embodiments, different variants and embodiments (and combinations thereof) of the described improved data transmission process can be implemented in existing communication systems (such as LTE, LTE-A, 5G NR communication systems). In the following, it is exemplarily described how to implement the improved data transmission process in a communication system according to the 5G NR standard.
[0409] According to the above-mentioned improved data transmission process, the UE transmits small data and control messages to the radio base station, including the previously determined UE ID. In an exemplary variant of the improved data transmission process (which can be combined with other variants), the small data and control messages are transmitted as part of the random access process. As presented in the previous part of the description referenced here, 3GPP 5G NR provides a 2-step RACH process and a 4-step RACH process. For example, when performing a 2-step RACH process, small data and control messages can be transmitted as part of the first message (msgA) of the 2-step RACH process. The remaining 2-step RACH processes currently defined in 3GPP (refer to the corresponding part of the above description) can be used for the improved data transmission process, for example, including the base station transmitting MSGB and the corresponding reception in the UE.
[0410] On the other hand, when a 4-step RACH procedure is performed, small data and control messages can be transmitted as part of the third message (msg3) of the 4-step RACH procedure. The remaining 4-step RACH procedure currently defined in 3GPP can be used for an improved data transmission procedure. For example, this includes a previous preamble transmission as a first step, then in a second step, receiving a RAR including a grant of limited radio resources for transmitting msg3 in a third step, and finally potential contention resolution in a fourth step. The UE uses the radio resources scheduled by the radio base station in the RAR to transmit small data and control messages as msg3. For example, a typical grant size is 72 bits for carrying control messages and small data. Therefore, the larger the control message, the less data can be used to be transmitted in the remaining msg3. Therefore, it is important that the control message and in particular the carried UE ID is as small as possible in order to carry more data in the remaining part of msg3 (e.g., in the same transport block constructed by the UE using the granted radio resources; different data / signaling radio bearers are multiplexed together in the same transport block in the MAC layer).
[0411] In the prior art RACH procedure, the base station (gNB) only expects msg3 of the 4-step RACH procedure and msgA of the 2-step RACH procedure to include RRC messages, such as the RRCResumeRequest message. Therefore, the base station (gNB) does not expect to transmit any small data with msg3 and msgA, respectively. On the other hand, the gNB according to the improved data transmission procedure should be prepared for both cases, namely, the case where msg3 / msgA carries only control messages and the case where msg3 / msgA carries control messages as well as small data.
[0412] As described above for the improved data transmission procedure, a non-cell specific UE ID or a cell specific UE ID is transmitted in a control message together with small data. In the following, many different possible UE IDs will be presented, which can be used as non-cell specific UE ID and cell specific UE ID, respectively.
[0413] In 5G NR, there are I-RNTI and short I-RNTI (see TS 38.331v15.8.0 section 6.3.2), each of which can be used as a non-cell-specific UE ID. The I-RNTI has 40 bits and its composition varies depending on the I-RNTI reference profile. On the other hand, the short I-RNTI has fewer bits than the full I-RNTI, specifically 24 bits.
[0414] The following table shows three different profiles for the full I-RNTI as described in 3GPP TS 38.300 v16.0.0 Annex C).
[0415]
[0416]
[0417] Obviously, the I-RNTI consists of different parts, namely the UE-specific reference (ID) and the NG-RAN node address (such as the base station (gNB) ID) and the PLMN-specific information of profile 2. The size of the full I-RNTI is quite large and therefore occupies a lot of space in the msg3 (e.g., 72 bits available in total) grant or the msgA PUSCH part (e.g., 200 bits available in total). As a result, less small data can be transmitted, making small data transmission less efficient. However, the full I-RNTI can uniquely identify the UE, for example, within a PLMN.
[0418] On the other hand, the short I-RNTI (also called truncated I-RNTI) is only 24 bits, for example, 12 LSB bits are taken from the UE-specific reference and 12 LSB bits are taken from the base station (gNB) ID. Accordingly, the size of the short I-RNTI is significantly smaller than that of the full I-RNTI, allowing more small data to be transmitted in msg3 or msgA. However, in specific deployment scenarios (such as when there are thousands of base stations (gNBs) within the PLMN and / or when there are thousands of inactive UEs camped on one base station (gNB)), UE ID conflicts are more likely to occur.
[0419] In the current 5G NR system, the UE is configured by the base station (gNB) to use the full I-RNTI or the short I-RNTI (e.g., as part of SIB1). Therefore, exemplarily, when performing the improved data transmission procedure and deciding to use the non-cell-specific UEID for small data transmission, the UE uses the full I-RNTI or the short I-RNTI according to the indication from the base station (gNB).
[0420] Regarding the cell-specific UE ID, there are several possibilities, such as using the UE-specific part of the I-RNTI, the C-RNTI or a small data-specific UE ID, which will be explained below. As discussed above, the cell-specific UE ID is used by the UE for small data transmission when the UE stays in the same radio cell where the cell-specific UE ID is valid. In other words, if possible, the cell-specific UE ID should not be used when the UE is in a new radio cell.
[0421] According to an additional optional embodiment, the UE-specific part of the I-RNTI (see the table above) is 20 bits long and can be used as a cell-specific UE ID in an improved data transmission process. Accordingly, the cell-specific UE ID is smaller than the two options for the non-cell-specific UE ID. However, which bits of the full I-RNTI identify the UE (and which bits identify the base station (gNB)) may not be visible to legacy UEs (according to Release 15 or 16). According to an exemplary embodiment of the aspect, the base station (gNB) can additionally indicate to the UE from which bit to which bit within the full I-RNTI identifies the UE.
[0422] According to a further second exemplary variant, a 16-bit long C-RNTI can be used as a cell-specific UE ID. The C-RNTI is even shorter than the UE-specific part of the I-RNTI discussed above, thus allowing further improvements in small data transmission. In current 5G NR communication systems, the base station (gNB) releases the C-RNTI of the UE when the UE moves to the RRC_INACTIVE state. However, for the improved data transmission method, the gNB needs to retain the C-RNTI even after the UE transitions to RRC INACTIVE in order to allow the UE to use the C-RNTI as a cell-specific UE ID.
[0423] According to another third exemplary variant, a new UE ID for small data transmission may be defined, which may be 16 bits or less. This allows further reduction of the number of bits used for UE ID in small data transmission, thereby allowing more small data to be transmitted. However, defining and maintaining another UE ID requires more processing on the base station (gNB) side. In particular, the base station (gNB) may maintain another cell-specific UE ID pool (similar to C-RNTI) used only to facilitate small data transmission when the UE is inactive.
[0424] According to the variant of the improved data transmission process discussed above in conjunction with the cell-specific UE ID, a new UE ID validity timer can be used to limit the time for which the base station (gNB) retains the cell-specific UE ID before releasing it to be available for reassignment to another UE. The UE ID validity timer can be used, for example, in conjunction with the C-RNTI and small data-specific UE ID (second and third variants) discussed above, so that when the C-RNTI (or small data-specific UE ID) is released can be controlled and exhaustion of the C-RNTI (or small data-specific UE ID) can be avoided. Considering that the UE-specific part of the I-RNTI (first variant) will not be reassigned, the UE ID validity timer can be but does not have to be operated when the UE-specific part of the I-RNTI is used as a cell-specific UE ID.
[0425] As described above for the improved data transmission procedure, the UE transmits a control message to the base station, including the selected UE ID. There are several different possibilities for how the control message can be implemented in a 5G NR communication system. In some exemplary embodiments, one or more of the following variants of the control message for paging can be implemented simultaneously, and then the UE decides which specific control message to use as the control message for the improved data transmission procedure.
[0426] The reception of the paging message by the UE may be indicated by an interpretation including one short DL data or multiple short DL data.
[0427] The small data indication or one-time downlink (DL) data will be 1 bit long. For example, when the new small data indication or one-time downlink (DL) data indication is true, the base station (gNB) expects additional small data (user data). Therefore, the base station (gNB) knows exactly when small data is transmitted and facilitates the decoding of small data or one-time downlink (DL) data.
[0428] According to the variant of the RRC control message, the RRCResumeRequest and PagingUE-Identity messages currently defined in 5G NR can be reused without any further modifications. Therefore, when receiving the request, the base station (gNB) does not know whether small data is also transmitted. Therefore, the gNB must be prepared for both cases, the first case is that no small data is transmitted with the RRCResumeRequest, and the second case is that small data is transmitted with the RRCResumeRequest. For example, the base station (gNB) will try to successfully decode any bits transmitted with the RRCResumeRequest to determine whether they constitute a transmission of small data or only spare bits.
[0429] According to an additional optional embodiment, an RRC message is defined for small data transmission when the UE is in an inactive state. Since this RRC message will be used by the UE for small data transmission, the base station (gNB) expects further user data (small data) to be attached after this new RRC message.
[0430] In the example of the PagingUE-Identity message, the UE-Identity information element (IE) uses a CHOICE structure to allow the UE to choose between different UE identification formats. To avoid repetition, refer to the above discussion on different 5G NR compatible implementations of non-cell-specific UE and cell-specific UE IDs, such as the full I-RNTI (in the above message "I-RNTI-Value"), the short I-RNTI (in the above message "shortI-RNTI-Value"), and the UE-specific part of the I-RNTI (in the above message "UE-I-RNTI-Value"). In the above example, the UE will select the full I-RNTI or the short I-RNTI as the non-cell-specific UE ID, and there is only one option for the cell-specific UE ID, in particular the UE-specific part of the I-RNTI.
[0431] In the above solution, the control message is a message of the RRC protocol. Other variants of the improved data transmission process use messages of the MAC protocol as control messages. It should be noted that MAC control elements are usually not integrity protected and are therefore not as secure as RRC messages. However, the size of the MAC message can be smaller, which results in less control overhead, so that more small data can be transmitted.
[0432] A possible implementation of the MAC control message is to carry one of the possible UE IDs mentioned above based on a new medium access control element (MAC CE) format. A new LCID (Logical Channel ID) value is reserved for the new medium access control element (MAC CE) to be indicated in the medium access control (MAC) subheader.
[0433] If C-RNTI is used as a cell-specific UE ID, an already existing C-RNTI media access control control element (MAC CE) may be reused (see TS 38.321 v15.8.0 section 6.1.3.2). However, by reusing this existing C-RNTI media access control control element (MAC CE), no additional small data indication or cause may be transmitted to the base station (gNB). Therefore, the base station (gNB) needs to be prepared to decode small data after receiving the C-RNTI media access control control element (MAC CE). However, the base station (gNB) may implicitly understand that the UE is transmitting small data when such a C-RNTI media access control control element (MAC CE) is received as part of a RACH procedure (which typically includes an RRC message).
[0434] According to a further variant, the base station (gNB) may decide which UE state is most suitable for the UE and then transmit the corresponding RRC UE state indication back to the UE as part of the response message (see the UE state indication variants discussed above). According to an exemplary embodiment, the decision of the base station (gNB) may be based on one or more of the following: the resumption cause indicated in the RRCResumeRequest, whether user data is attached after the RRCResumeRequest, and whether the attached user data is the end of the traffic.
[0435] The response message may be a new message defined for the purpose and capable of carrying the corresponding RRC UE status indication.
[0436] In other solutions, already existing RRC messages can be reused. For example, when using the RRCResumeRequest message as a control message, the base station (gNB) can respond with a RRCResume message, for example as part of a RACH procedure. The RRCResume message will indicate the RRC UE state the UE should be in. The RRCResume message for 5G NR currently defined in Section 6.2.2 of TS38.331v15.8.0 can be extended.
[0437] In different scenarios, the (possibly new) base station (gNB) is actually the anchor base station (gNB) for the UE, e.g. when the UE is located in a new radio cell, which belongs to the same base station (gNB) as the previous radio cell. Furthermore, in this case, the UE will transmit control messages with a non-cell-specific UE ID (e.g. full I-RNTI), although it could have used a cell-specific UE ID. In response to the control message, the base station (gNB) may respond by sending the cell-specific UE ID to the UE, thereby indicating that the base station (gNB) is also the anchor base station (gNB) for the UE for the new radio cell. Accordingly, the UE is thereby made aware that the new radio cell belongs to the same base station (gNB) as before, and in future communications (e.g. new small data transmissions), the UE may use the short cell-specific UE ID.
[0438] In the above-mentioned variants and embodiments of the improved data transmission process, when determining which UE ID to use for small data transmission, the UE determines whether it has moved to a new radio cell after transitioning to the inactive state. In an exemplary variant of the improved data transmission method, the determination of the radio cell in which the UE is currently located can be performed as follows. A radio base station can broadcast signals (such as synchronization signals or system information) in its radio cell, which allow the ID of the radio base station (or radio cell) to be determined. The UE receives the signal while in the inactive state and is able to determine the radio cell in which it is currently located. For example, in an exemplary 5G NR embodiment, the primary synchronization signal and the secondary synchronization signal (see SS / PBCH block; synchronization signal / physical broadcast channel block) are transmitted by the base station (gNB) and decoded by the corresponding UE, which allows the identification of the time slot and physical cell ID of the radio cell in which it is camped (see 3GPP TS 38.211v16.0.0, for example, Sections 7.4.2 and 7.4.3). In this 5G NR embodiment, the UE identifies the radio cell based on the physical cell ID (PCI), but does not identify the base station (gNB). In deployments where one base station (gNB) controls multiple radio cells, the UE will not be able to know that the new radio cell (after a cell change while inactive) belongs to the same base station (gNB) as the previous radio cell before the radio cell change (cell reselection). In the improved data transmission procedure, the UE will therefore still use the non-cell-specific UE ID for transmission together with the small data.
[0439] Many variants and implementations of the improved data transmission process have been described. Some of them have been described separately from each other to facilitate understanding of the benefits of the corresponding variants or implementations. However, two or more variants and implementations of the improved data transmission process can also be combined to form new variants and implementations of the improved data transmission process. Non-exhaustive, only a few are listed: small data indication variants, UE ID validity timer variants, UE status indication variants, fallback RAR variants, different variants of control messages, different variants of cell-specific UE ID and non-cell-specific UE ID, and different variants of UE data connections.
[0440] Further aspects
[0441] According to a first aspect, a method for wireless communication is provided, comprising the following steps: receiving downlink control information (DCI) by a user equipment (UE) in an inactive state (RRC_INACTIVE), the downlink control information comprising:
[0442] a cyclic redundancy check (CRC) scrambled by a radio network having at least one base station (gNB) with an identifier (C-RNTI) specific to a group of UEs,
[0443] The group of UEs includes the UE; and resource assignments for data transmission from at least a base station (gNB) to the user equipment (UE); and
[0444] receiving the data transmission on a physical shared channel by the user equipment (UE) in the inactive state (RRC_INACTIVE),
[0445] The user equipment (UE) receives more than one random access channel (RACH) resource configuration.
[0446] According to a second aspect provided in addition to the first aspect, wherein a user equipment (UE) receives a priority indication of downlink (DL) data in a paging message.
[0447] According to a third aspect provided in addition to the first aspect or the second aspect, wherein a user equipment (UE) receives an indication of the group ID in a paging message.
[0448] According to a fourth aspect provided in addition to one of the first aspect or the second aspect, wherein a user equipment (UE) receives a mapping between a priority and a group ID and a random access channel (RACH) resource configuration.
[0449] In an alternative implementation of the above MAC control message, the control message is a control message of a radio resource control RRC protocol, specifically one of the following:
[0450] an RRC recovery request message, comprising a reason for transmitting the RRC recovery request message, wherein the reason indicates a small data transmission as a reason for transmitting the RRC recovery request message,
[0451] an RRC recovery request message, including a reason for transmitting the RRC recovery request message and including a small data indication,
[0452] an RRC RECOVERY REQUEST message not including a small data indication, nor indicating a small data transmission as a reason for transmitting the RRC RECOVERY REQUEST message,
[0453] Small data specific RRC messages.
[0454] According to a fifth aspect provided in addition to one of the first to fourth aspects, wherein a user equipment (UE) receives the mapping in system information or a dedicated RRC message.
[0455] According to a sixth aspect provided in addition to one of the first to fifth aspects, a user equipment (UE) selects a random access channel (RACH) resource corresponding to a priority and / or a group ID indicated in a paging message.
[0456] According to the seventh aspect provided in addition to one of the first to sixth aspects, the base station (gNB) configures more than one random access channel (RACH) resources for each synchronization signal block (SSB).
[0457] In an optional embodiment, the response message further indicates uplink radio resources to be used for transmitting the data. The transmitter transmits further small data to the radio base station using the indicated uplink radio resources.
[0458] In another optional embodiment, the response message further indicates a new cell-specific UE ID, which is different from the already assigned cell-specific UE ID. The processor uses the newly assigned cell-specific UE ID in future communications instead of the previously assigned cell-specific UE ID.
[0459] According to an eighth aspect provided in addition to one of the first to seventh aspects, the base station (gNB) configures mapping of random access channel (RACH) resources based on at least one option.
[0460] In an optional embodiment, the receiver receives a new cell-specific UE ID from the radio base station, and the processor replaces the previous cell-specific UE ID with the newly assigned cell-specific UE ID. According to an eighth aspect provided in addition to one of the first to seventh aspects, when in an inactive state, the processor does not suspend at least one data connection maintained by the UE in a connected state. In an optional embodiment, the at least one non-suspended data connection is dedicated to the transmission of small data.
[0461] Alternatively, when transitioning to the inactive state, the processor does not suspend any data connection maintained by the UE in the connected state.
[0462] Alternatively, when transitioning to the inactive state, the processor suspends all data connections maintained by the UE in the connected state and creates a new data connection dedicated to the transmission of small data.
[0463] According to a ninth aspect, in addition to one of the first to eighth aspects, a method is provided, wherein the option is a selection of priorities P1, P2, and P3, and
[0464] Priority P1 is linked to random access channel (RACH) resource 1,
[0465] Priority P2 is linked to random access channel (RACH) resource 2,
[0466] Priority level P3 is linked to random access channel (RACH) resource 3.
[0467] According to the tenth aspect, in addition to one of the first to ninth aspects, a method is provided, the option being selection of group ID1, group ID2 and group ID3, and group ID1 is linked to random access channel (RACH) resource 1, group ID2 is linked to random access channel (RACH) resource 2, and group ID3 is linked to random access channel (RACH) resource 3.
[0468] According to the eleventh aspect, the mapping is accomplished via system information or a dedicated RRC message.
[0469] According to the twelfth aspect, in addition to one of the first to eleventh aspects, a method is provided, wherein the base station (gNB) indicates priority P1, P2, P3 and / or group ID1, group ID1, group ID2, group ID3 in a paging message, and the user equipment (UE) selects a random access channel (RACH) resource.
[0470] According to the thirteenth aspect, in addition to one of the first to twelfth aspects, a method is provided, in which a base station (gNB) changes the number of random access channel (RACH) resources based on the overall load situation.
[0471] According to a fourteenth aspect, a user equipment (UE) for wireless communication is provided, the user equipment comprising: a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: when the user equipment (UE) is in an inactive mode or an idle mode (RRC_IDLE), receive a paging communication from a base station (gNB); as part of a random access channel (RACH) procedure, transmit a first communication to the base station (gNB) based at least in part on receiving the paging communication; and receive a second communication from the base station (gNB) based at least in part on transmitting the first communication, the second communication comprising: downlink data terminated by the mobile end, an indication of uplink resources, and a radio resource control (RRC) release message, wherein the radio resource control release message causes the user equipment (UE) to remain in the inactive mode or the idle mode when receiving the downlink data terminated by the mobile end; and when in the inactive mode or the idle mode, use the uplink resources to transmit uplink data initiated by the mobile end to a base station (gNB), wherein the memory stores computer program instructions that, when executed by a microprocessor, configure the user equipment (UE) to implement one or more of the methods described in claims 1 to 13.
[0472] According to a fourteenth aspect, a base station (gNB) for wireless communication is provided, the base station comprising: a memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: transmit a paging communication to a user equipment (UE) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE); receive a first communication from the user equipment (UE) based at least in part on transmitting the paging communication as part of a random access channel (RACH) process; and transmit a second communication to the user equipment (UE) based at least in part on transmitting the first communication, the second communication comprising: downlink data terminated by a mobile terminal, a mobile terminal initiated downlink data to be transmitted by the user equipment (UE) when the user equipment (UE) is in the inactive mode or the idle mode The memory stores computer program instructions which, when executed by the microprocessor, configure the user equipment (UE) via the base station (gNB) to implement one or more of the methods described in claims 1 to 13.
[0473] According to a fifteenth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: one or more instructions that, when executed by one or more processors of a user equipment (UE), cause the one or more processors to perform the following operations: receiving a paging communication from a base station (gNB) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE);
[0474] As part of a random access channel (RACH) procedure, transmitting a first communication to the base station (gNB) based at least in part on receiving the paging communication; and receiving a second communication from the base station (gNB) based at least in part on transmitting the first communication, the second communication comprising:
[0475] downlink data terminated by the mobile terminal, an indication of uplink resources, and a radio resource control (RRC) release message, wherein the radio resource control release message causes the user equipment (UE) to remain in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE) when receiving the downlink data terminated by the mobile terminal; and when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), using the uplink resources to transmit uplink data (UL) initiated by the mobile terminal to the base station (gNB), wherein the non-transitory computer-readable medium stores computer program instructions, which when executed by a microprocessor configure the user equipment (UE) to implement one or more of the methods described in claims 1 to 13.
[0476] According to a sixteenth aspect, a non-transitory computer-readable medium is provided, the non-transitory computer-readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: one or more instructions, when executed by one or more processors of a base station (gNB), causing the one or more processors to perform the following operations: when a user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE), transmitting a paging communication to the user equipment (UE); receiving a first communication from the user equipment (UE) based at least in part on transmitting the paging communication as part of a random access channel (RACH) procedure; and transmitting a second communication to the user equipment (UE) based at least in part on transmitting the first communication, the second communication comprising:
[0477] mobile terminated downlink data, uplink (UP) resources to be used by the user equipment (UE) to transmit mobile initiated uplink (UP) data when the UE is in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), and
[0478] a radio resource control (RRC) release message, the radio resource control release message enabling the user equipment (UE) to receive the mobile-terminated downlink (DL) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), and
[0479] receiving mobile-initiated uplink (UL) data from the user equipment (UE) in the uplink (UL) resource, the user equipment (UE) to transmit the mobile-initiated uplink data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE),
[0480] Therein, the non-transitory computer readable medium stores computer program instructions which, when executed by a microprocessor, configure the user equipment (UE) to implement the method as claimed in one or more of claims 1 to 13.
[0481] According to a further advantageous aspect provided in addition to all other aspects, the UE is in a connected state, and at least one data connection has been established between the UE and the radio base station. The processor determines to switch the UE to an inactive state. The transmitter instructs the UE to switch to an inactive state. The processor determines not to suspend the at least one data connection that has been established between the UE and the radio base station in the connected state. The one data connection for small data transmission is one of the at least one data connection that is not suspended.
[0482] In an optional implementation, the at least one non-suspended data connection is dedicated to the transmission of small data.
[0483] According to a further advantageous aspect provided in addition to all other aspects, the UE context is either stored locally within the radio base station or fetched from another radio base station.
[0484] Alternatively, when switching the UE to the inactive state, the processor does not suspend all data connections that have been established between the UE and the radio base station in the connected state. The one data connection for small data transmission is one of the non-suspended data connections.
[0485] Alternatively, when the UE is switched to the inactive state, the processor suspends all data connections established between the UE and the radio base station in the connected state and establishes the one data connection with the UE, optionally wherein the newly established one data connection is dedicated to transmission of small data.
[0486] According to a further advantageous aspect provided in addition to all other aspects, the processor determines that the UE has moved from a different radio base station to the radio base station after transitioning to an inactive state based on a received UE identity, the UE identity being a non-cell-specific UE identity. The processor determines the different radio base station based on the non-cell-specific UE identity. The radio base station includes a transmitter that transmits a request for a context of the UE to the different radio base station. The receiver receives a response including the context of the UE from the different radio base station. The processor decodes the received small data using the received context of the UE.
[0487] According to a further beneficial aspect provided in addition to all other aspects, a cell-specific UE identity is assigned to the UE by the radio base station. The processor operates a UE ID validity timer for the cell-specific UE identity. When the UE transitions from a connected state to an inactive state, the processor starts the UE ID validity timer. When it is determined that the UEID validity timer for the cell-specific UE identity has expired, the processor considers that the value of the cell-specific UE identity is no longer associated with the UE, but can be used to associate with another UE. According to a fifteenth aspect provided in addition to one of the tenth to fourteenth aspects, the transmitter transmits a response message to the UE in response to the received control message. The response message includes an indication that the UE stays in the inactive state or transitions to one of a connected state or an idle state.
[0488] Hardware and Software Implementations of the Disclosure
[0489] The present disclosure can be implemented by software, hardware or software and hardware cooperation. Each functional block used in the description of each of the above embodiments can be partially or completely implemented by LSI (such as integrated circuit), and each process described in each embodiment can be partially or completely controlled by the same LSI or a combination of LSI. LSI can be formed as a chip alone, or a chip can be formed to include some or all functional blocks. LSI can include data input and output coupled thereto. Depending on the degree of integration, the LSI here can be referred to as IC (integrated circuit), system LSI, super LSI or super LSI. However, the technology for implementing integrated circuits is not limited to LSI, and can be implemented by using a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after manufacturing LSI or a reconfigurable processor in which the connection and setting of the circuit unit placed inside the LSI can be reconfigured can be used. The present disclosure can be implemented as digital processing or analog processing. If future integrated circuit technology replaces LSI due to the advancement of semiconductor technology or other derivative technologies, future integrated circuit technology can be used to integrate functional blocks. Biotechnology can also be applied.
[0490] The present disclosure may be implemented by any type of device, apparatus or system having a communication function (which is referred to as a communication device).
[0491] The communication device may include a transceiver and a processing / control circuit system. The transceiver may include and / or act as a receiver and a transmitter. As a transmitter and a receiver, the transceiver may include an RF (radio frequency) module, which includes an amplifier, an RF modulator / demodulator, etc. and one or more antennas.
[0492] Some non-limiting examples of such communication devices include phones (e.g., cellular phones, smart phones), tablet computers, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital cameras / camcorders), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and medicine) devices, and vehicles that provide communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.
[0493] Communication devices are not limited to portable or transportable, and may also include any kind of non-portable or fixed device, equipment, or system, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in an "Internet of Things (IoT)" network.
[0494] Communications may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.
[0495] The communication device may include a device such as a controller or a sensor that is coupled to a communication device that performs the communication functions described in the present disclosure. For example, the communication device may include a controller or a sensor that produces a control signal or a data signal that is used by the communication device that performs the communication functions of the communication device.
[0496] The communication device may also include infrastructure such as base stations, access points, and any other device, equipment, or system that communicates with or controls the devices in the above non-limiting examples.
[0497] Further, various embodiments may also be implemented by software modules executed by a processor or directly in hardware. Combinations of software modules and hardware implementations are also possible. Software modules may be stored on any type of computer-readable storage medium (e.g., RAM, EPROM, EEPROM, flash memory, registers, hard disk, CD-ROM, DVD, etc.). It should be further noted that the various features of different embodiments may be used alone or in any combination as the subject of another embodiment.
[0498] Those skilled in the art will appreciate that various changes and / or modifications may be made to the present disclosure as shown in the specific embodiments. Therefore, the present embodiments are considered in all aspects to be illustrative and not restrictive.
[0499] abbreviation:
[0500] Artificial Intelligence / Machine Learning (AI / ML)
[0501] Cell RNTI (C-RNTI)
[0502] Configuration-authorized small data transfer (CG-SDT)
[0503] Downlink (DL)
[0504] Radio Network Temporary Identifier (RNTI)
[0505] Random Access-based Small Data Transfer (RA-SDT)
[0506] Reference Signal Received Power (RSRP)
[0507] Reference Signal Received Quality (RSRQ)
[0508] Small Data Transfer (SDT)
[0509] Uplink (UL)
Claims
1. A wireless communication method, comprising the following steps: Downlink control information (DCI) is received by a user equipment (UE) in an inactive state (RRC_INACTIVE), the downlink control information including: a cyclic redundancy check (CRC) scrambled by a radio network having at least one base station (gNB) with a paging radio network temporary identifier (P-RNTI) of at least one user equipment (UE), the user equipment (UE) monitoring a paging message in an inactive state (RRC_INACTIVE) and decoding reception of the paging message using the paging radio network temporary identifier (P-RNTI), The user equipment (UE) receives more than one random access channel (RACH) resource configuration.
2. The method according to claim 1, wherein: The user equipment (UE) receives a priority indication for downlink (DL) data in a paging message.
3. The method according to claim 1 or 2, wherein: The user equipment (UE) receives an indication of the group ID in a paging message.
4. The method according to any one of claims 1 to 3, wherein: A user equipment (UE) receives a mapping between priority and group ID and a random access channel (RACH) resource configuration.
5. The method according to any one of claims 1 to 4, wherein the user equipment (UE) receives the mapping in system information or a dedicated RRC message.
6. The method according to claims 1 to 5, wherein: The user equipment (UE) selects a random access channel (RACH) resource corresponding to the priority and / or group ID indicated in the paging message.
7. The method according to claims 1 to 6, wherein: The base station (gNB) configures one or more random access channel (RACH) resources for each synchronization signal block (SSB).
8. The method according to claim 7, wherein: The base station (gNB) configures the mapping of these random access channel (RACH) resources based on at least one option.
9. The method according to claim 8, wherein: The option is a selection of priorities P1, P2 and P3, and Priority P1 is linked to random access channel (RACH) resource 1, Priority P2 is linked to random access channel (RACH) resource 2, Priority level P3 is linked to random access channel (RACH) resource 3.
10. The method according to claim 8, wherein: This option is a selection of group ID1, group ID2 and group ID3, and Group ID 1 is linked to random access channel (RACH) resource 1, Group ID 2 is linked to random access channel (RACH) resource 2, Group ID 3 is linked to random access channel (RACH) resource 3.
11. The method according to claim 8, wherein: The mapping is done via system information or dedicated RRC messages.
12. The method according to claims 8 to 11, The base station (gNB) indicates the priority levels P1, P2, P3 and / or group ID1, group ID1, group ID2, group ID3 in the paging message, and the user equipment (UE) selects a random access channel (RACH) resource.
13. The method according to claims 8 to 12, wherein: The base station (gNB) changes the number of random access channel (RACH) resources based on the overall load situation.
14. A user equipment (UE) for wireless communication, the user equipment comprising: Memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: receiving a paging communication from a base station (gNB) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE); transmitting, as part of a random access channel (RACH) procedure, a first communication to the base station (gNB) based at least in part on receiving the paging communication; and receiving, from a base station (gNB), a second communication based at least in part on transmitting the first communication, the second communication comprising: mobile terminated downlink data (DL), an indication of uplink (UL) resources, and a radio resource control (RRC) release message (DL), the radio resource control release message causing the user equipment (UE) to remain in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE) when receiving the mobile terminated downlink data; and when in the inactive mode or the idle mode, to transmit mobile originated uplink data to a base station (gNB) using the uplink (UL) resources, Therein, the memory stores computer program instructions which, when executed by the microprocessor, configure the user equipment (UE) to implement the method as claimed in one or more of claims 1 to 13.
15. A base station (gNB) for wireless communication, the base station comprising: Memory; and one or more processors coupled to the memory, the memory and the one or more processors being configured to: transmitting a paging communication to a user equipment (UE) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE); receiving a first communication from the user equipment (UE) based at least in part on transmitting the paging communication as part of a random access channel (RACH) procedure; and transmitting, based at least in part on transmitting the first communication, a second communication to the user equipment (UE), the second communication comprising: mobile-terminated downlink (DL) data, uplink (UL) resources to be used by the user equipment (UE) to transmit mobile-initiated uplink data when in the inactive mode or the idle mode, and a radio resource control (RRC) release message, the radio resource control release message enabling the user equipment (UE) to receive the mobile-terminated downlink (DL) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE); and receiving mobile-initiated uplink data from the user equipment (UE) in the uplink (UL) resources, the user equipment (UE) transmitting the mobile-initiated uplink data when in the inactive mode or the idle mode, The memory stores computer program instructions which, when executed by the microprocessor, configure the user equipment (UE) via the base station (gNB) to implement one or more of the methods described in claims 1 to 13.
16. A non-transitory computer readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a user equipment (UE), cause the one or more processors to: receiving a paging communication from a base station (gNB) when the user equipment (UE) is in an inactive mode (RRC_INACTIVE) or an idle mode (RRC_IDLE); transmitting, as part of a random access channel (RACH) procedure, a first communication to the base station (gNB) based at least in part on receiving the paging communication; and receiving, from the base station (gNB), a second communication based at least in part on transmitting the first communication, the second communication comprising: mobile-terminated downlink (DL) data, an indication of uplink (UL) resources, and a radio resource control (RRC) release message, the radio resource control release message causing the user equipment (UE) to remain in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE) when receiving the mobile-terminated downlink data; and when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), transmitting mobile-originated uplink (UL) data to the base station (gNB) using the uplink (UL) resources, Therein, the non-transitory computer readable medium stores computer program instructions which, when executed by a microprocessor, configure the user equipment (UE) to implement the method as claimed in one or more of claims 1 to 13.
17. A non-transitory computer readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a base station (gNB), cause the one or more processors to perform the following operations: When the user equipment (UE) is in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), transmitting a paging communication to the user equipment (UE); receiving a first communication from the user equipment (UE) based at least in part on transmitting the paging communication as part of a random access channel (RACH) procedure; and transmitting, based at least in part on transmitting the first communication, a second communication to the user equipment (UE), the second communication comprising: mobile-terminated downlink (DL) data, uplink (UP) resources to be used by the user equipment (UE) to transmit mobile-initiated uplink (UP) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), and a radio resource control (RRC) release message that enables the user equipment (UE) to receive the mobile-terminated downlink (DL) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), and receiving mobile-initiated uplink (UL) data from the user equipment (UE) in the uplink (UL) resource, the user equipment (UE) transmitting the mobile-initiated uplink (UL) data when in the inactive mode (RRC_INACTIVE) or the idle mode (RRC_IDLE), Therein, the non-transitory computer readable medium stores computer program instructions which, when executed by a microprocessor, configure the user equipment (UE) to implement the method as claimed in one or more of claims 1 to 13.
Citation Information
Patent Citations
Inactive state data forwarding
US10264622B2
Systems and methods for data transmission in an inactive state
US20210127414A1
Paging for mobile-terminated small data reception in idle and / or inactive mode
WO2021031103A1
Paging for mobile-terminated small data reception in idle and / or inactive mode
WO2021031112A1
Method and apparatus for small data transmission in RRC inactive state in mr-dc
WO2021157895A1
