Method and Apparatus for resuming connections in RRC_INACTIVE state
The method and apparatus for resuming connections in the RRC_INACTIVE state through SDT procedures address the challenge of efficient data transfer in 5G systems by using RACH and CG resources, optimizing network efficiency and reducing overhead.
Patent Information
- Application Number
- KR1020220121387
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2022-09-26
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2042-09-26
AI Technical Summary
Existing 5G communication systems face challenges in enabling efficient uplink and downlink data transmission and reception in the RRC_INACTIVE state without transitioning to the RRC_CONNECTED state, leading to network efficiency degradation due to excessive overhead.
A method and apparatus for resuming a connection in the RRC_INACTIVE state through Small Data Transmission (SDT) procedures, utilizing Random Access Channel (RACH) and Configured Grant (CG) resources, allowing data transmission and reception without transitioning to RRC_CONNECTED, including configurations for Phase 2 and Phase 4 random access resources and dynamic grants.
Enables efficient data transmission and reception in the RRC_INACTIVE state, reducing network overhead and maintaining network efficiency by allowing data transfer without full state transitions, thereby optimizing resource utilization.
Smart Images

Figure 112022100863208-PAT00004_ABST
Abstract
Description
Technology Field
[0001] The present disclosure relates to a method and apparatus for resuming a connection in an RRC_INACTIVE state in a wireless mobile communication system. Background Technology
[0003] 5G communication systems were developed to meet the increasing demand for wireless data traffic following the commercialization of 4G communication systems. To achieve high data transmission rates, 5G communication systems introduced the mmWave band (e.g., the 60 GHz band). To mitigate path loss and increase transmission distance in the mmWave band, 5G communication systems utilize technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas. In 5G communication systems, base stations are divided into central and distributed units to enhance scalability. Furthermore, 5G communication systems aim to support extremely high data transmission rates and extremely low transmission latency to support a wide range of services.
[0004] As a measure to achieve low transmission delay, uplink data transmission and downlink data reception by an inactive terminal are required. The problem to be solved
[0006] The present disclosure aims to provide a method and apparatus for transmitting and receiving data in an RRC_INACTIVE state in a wireless mobile communication system. means of solving the problem
[0008] According to one embodiment of the present disclosure, in a terminal method, the terminal receives an RRCRelease from a base station, the RRCRelease includes a SuspendConfig, the terminal enters an RRC_INACTIVE state in response to receiving the RRCRelease message and performs cell selection, the terminal receives a SIB1 in the selected cell, the SIB1 includes one or more RACH-ConfigCommons, each of the one or more RACH-ConfigCommons includes one or more FeatureCombinationPreambles IEs, each of the one or more FeatureCombinationPreambles IEs includes one FeatureCombination, the terminal starts a random access procedure in the cell, and the terminal selects a set of random access resources for the random access procedure. Effects of the invention
[0011] The disclosed embodiment provides a method and apparatus for an inactive terminal to perform uplink data transmission and downlink data reception in a wireless mobile communication system. Brief explanation of the drawing
[0013] FIG. 1a is a diagram illustrating the structure of a 5G system and an NG-RAN according to one embodiment of the present disclosure. FIG. 1b is a diagram illustrating a wireless protocol structure in an NR system according to one embodiment of the present disclosure. FIG. 1c is a diagram illustrating a transition between RRC states according to one embodiment of the present disclosure. FIG. 2a is a diagram illustrating the operation of a terminal and a base station according to the present disclosure. FIG. 2b is a diagram illustrating the RRC connection resumption operation according to the present disclosure. FIG. 3a is a flowchart for explaining the operation of a terminal according to one embodiment of the present disclosure. FIG. 4a is a block diagram illustrating the internal structure of a terminal to which the present invention is applied. FIG. 4b is a block diagram illustrating the internal structure of a base station to which the present invention is applied. Specific details for implementing the invention
[0014] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings. Furthermore, in describing the present invention, detailed descriptions of related known functions or configurations are omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the invention. Additionally, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification.
[0015] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0016] For the convenience of the following explanation, the present invention uses terms and names defined in the 3GPP (3rd Generation Partnership Project) standard, which is the most recent standard among currently existing communication standards. However, the present invention is not limited by the above terms and names and can be applied in the same way to systems conforming to other standards.
[0017] Table 1 lists the abbreviations used in the present invention.
[0019] Acronym Full name Acronym Full name 5GC 5G Core Network RACH Random Access Channel ACK Acknowledgement RAN Radio Access Network AM Acknowledged Mode RA-RNTI Random Access RNTI AMF Access and Mobility Management Function RAT Radio Access Technology ARQ Automatic Repeat Request RB Radio Bearer AS Access Stratum RLC Radio Link Control ASN.1 Abstract Syntax Notation One RNA RAN-based Notification Area BSR Buffer Status Report RNAU RAN-based Notification Area Update BWP Bandwidth Part RNTI Radio Network Temporary Identifier CA Carrier Aggregation RRC Radio Resource Control CAG Closed Access Group RRM Radio Resource Management CG Cell Group RSRP Reference Signal Received Power C-RNTI Cell RNTI RSRQ Reference Signal Received Quality CSI Channel State Information RSSI Received Signal Strength Indicator DCI Downlink Control Information SCell Secondary Cell DRB (user) Data Radio Bearer SCS Subcarrier Spacing DRX Discontinuous Reception SDAP Service Data Adaptation Protocol HARQ Hybrid Automatic Repeat Request SDU Service Data Unit IE Information element SFN System Frame Number LCG Logical Channel Group S-GW Serving Gateway MAC Medium Access Control SI System Information MIB Master Information Block SIB System Information Block NAS Non-Access Stratum SpCell Special Cell NG-RAN NG Radio Access Network SRB Signalling Radio Bearer NR NR Radio Access SRS Sounding Reference Signal PBR Prioritised Bit Rate SSB SS / PBCH block PCell Primary Cell SSS Secondary Synchronisation Signal PCI Physical Cell Identifier SUL Supplementary Uplink PDCCH Physical Downlink Control Channel TM Transparent Mode PDCP Packet Data Convergence Protocol UCI Uplink Control Information PDSCH Physical Downlink Shared Channel UE User Equipment PDU Protocol Data Unit UM Unacknowledged Mode PHR Power Headroom Report MT-SDT Mobile Terminated-SDT PLMN Public Land Mobile Network MO=SDT Mobile Originated-SDT PRACH Physical Random Access Channel CS-RNTI Configured Scheduling-RNTI PRB Physical Resource Block TAG Timing Advance Group PSS Primary Synchronisation Signal SDT Small Data Transmission PUCCH Physical Uplink Control Channel RA-SDT Random Access-SDT PUSCH Physical Uplink Shared Channel CG-SDT Configured Grant-SDT PTAG Primary TAG STAG Secondary TAG
[0020] Table 2 defines the terms frequently used in the present invention.
[0021] Terminology Definition allowedCG-List List of configured grants for the corresponding logical channel. This restriction applies only when the UL grant is a configured grant. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated configured grant configuration. If the size of the sequence is zero, then UL MAC SDUs from this logical channel cannot be mapped to any configured grant configurations. If the field is not present, UL MAC SDUs from this logical channel can be mapped to any configured grant configurations. allowedSCS-List List of allowed sub-carrier spacings for the corresponding logical channel. If present, UL MAC SDUs from this logical channel can only be mapped to the indicated numerology. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured numerology. allowedServingCells List of allowed serving cells for the corresponding logical channel. If present, UL MAC SDUs from this logical channel can only be mapped to the serving cells indicated in this list. Otherwise, UL MAC SDUs from this logical channel can be mapped to any configured serving cell of this cell group. Carrier frequency center frequency of the cell. Cell combination of downlink and optionally uplink resources. The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information transmitted on the downlink resources. Cell Group in dual connectivity, a group of serving cells associated with either the MeNB or the SeNB. Cell reselection A process to find a better suitable cell than the current serving cell based on the system information received in the current serving cell Cell selection A process to find a suitable cell either blindly or based on the stored information Dedicated signalling Signalling sent on DCCH logical channel between the network and a single UE. discardTimer Timer to control the discard of a PDCP SDU. Starting when the SDU arrives. Upon expiry, the SDU is discarded. F The Format field in MAC subheader indicates the size of the Length field. Field The individual contents of an information element are referred to as fields. Frequency layer set of cells with the same carrier frequency. Global cell identity An identity to uniquely identifying an NR cell. It is consisted of cellIdentity and plmn-Identity of the first PLMN-Identity in plmn-IdentityList in SIB1. gNB node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. Handover procedure that changes the serving cell of a UE in RRC_CONNECTED. Information element A structural element containing single or multiple fields is referred as information element. L The Length field in MAC subheader indicates the length of the corresponding MAC SDU or of the corresponding MAC CE LCID 6 bit logical channel identity in MAC subheader to denote which logical channel traffic or which MAC CE is included in the MAC subPDU MAC-I Message Authentication Code - Integrity. 16 bit or 32 bit bit string calculated by NR Integrity Algorithm based on the security key and various fresh inputs Logical channel a logical path between a RLC entity and a MAC entity. There are multiple logical channel types depending on what type of information is transferred e.g. CCCH (Common Control Channel), DCCH (Dedicate Control Channel), DTCH (Dedicate Traffic Channel), PCCH (Paging Control Channel) LogicalChannelConfig The IE LogicalChannelConfig is used to configure the logical channel parameters. It includes priority, prioritisedBitRate, allowedServingCells, allowedSCS-List, maxPUSCH-Duration, logicalChannelGroup, allowedCG-List etc logicalChannelGroup ID of the logical channel group, as specified in TS 38.321, which the logical channel belongs to MAC CE Control Element generated by a MAC entity. Multiple types of MAC CEs are defined, each of which is indicated by corresponding LCID. A MAC CE and a corresponding MAC sub-header comprises MAC subPDU Master Cell Group in MR-DC, a group of serving cells associated with the Master Node, comprising of the SpCell (PCell) and optionally one or more SCells. maxPUSCH-Duration Restriction on PUSCH-duration for the corresponding logical channel. If present, UL MAC SDUs from this logical channel can only be transmitted using uplink grants that result in a PUSCH duration shorter than or equal to the duration indicated by this field. Otherwise, UL MAC SDUs from this logical channel can be transmitted using an uplink grant resulting in any PUSCH duration. NR NR radio access PCell SpCell of a master cell group. PDCP entity reestablishment The process triggered upon upper layer request. It includes the initialization of state variables, reset of header compression and manipulating of stored PDCP SDUs and PDCP PDUs. The details can be found in 5.1.2 of 38.323 PDCP suspend The process triggered upon upper layer request. When triggered, transmitting PDCP entity set TX_NEXT to the initial value and discard all stored PDCP PDUs. The receiving entity stop and reset t-Reordering, deliver all stored PDCP SDUs to the upper layer and set RX_NEXT and RX_DELIV to the initial value PDCP-config The IE PDCP-Config is used to set the configurable PDCP parameters for signalling and data radio bearers. For a data radio bearer, discardTimer, pdcp-SN-Size, header compression parameters, t-Reordering and whether integrity protection is enabled are configured. For a signaling radio bearer, t-Reordering can be configured PLMN ID Check the process that checks whether a PLMN ID is the RPLMN identity or an EPLMN identity of the UE. Primary Cell The MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Primary SCG Cell For dual connectivity operation, the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure. priority Logical channel priority, as specified in TS 38.321. an integer between 0 and 7. 0 means the highest priority and 7 means the lowest priority PUCCH SCell a Secondary Cell configured with PUCCH. Radio Bearer Logical path between a PDCP entity and upper layer (i.e. SDAP entity or RRC) RLC bearer RLC and MAC logical channel configuration of a radio bearer in one cell group. RLC bearer configuration The lower layer part of the radio bearer configuration comprising the RLC and logical channel configurations. RX_DELIV This state variable indicates the COUNT value of the first PDCP SDU not delivered to the upper layers, but still waited for. RX_NEXT This state variable indicates the COUNT value of the next PDCP SDU expected to be received. RX_REORD This state variable indicates the COUNT value following the COUNT value associated with the PDCP Data PDU which triggered t-Reordering. Serving Cell For a UE in RRC_CONNECTED not configured with CA / DC there is only one serving cell comprising of the primary cell. For a UE in RRC_CONNECTED configured with CA / DC the term 'serving cells' is used to denote the set of cells comprising of the Special Cell(s) and all secondary cells. SpCell primary cell of a master or secondary cell group. Special Cell For Dual Connectivity operation the term Special Cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term Special Cell refers to the PCell. SRB Signalling Radio Bearers" (SRBs) are defined as Radio Bearers (RBs) that are used only for the transmission of RRC and NAS messages. SRB0 SRB0 is for RRC messages using the CCCH logical channel SRB1 SRB1 is for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using DCCH logical channel; SRB2 SRB2 is for NAS messages and for RRC messages which include logged measurement information, all using DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by the network after AS security activation; SRB3 SRB3 is for specific RRC messages when UE is in (NG)EN-DC or NR-DC, all using DCCH logical channel SRB4 SRB4 is for RRC messages which include application layer measurement reporting information, all using DCCH logical channel. Suitable cell A cell on which a UE may camp. Following criteria apply - The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list- The cell is not barred- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas for Roaming" (TS 22.011
[18] ), which belongs to a PLMN that fulfils the first bullet above.- The cell selection criterion S is fulfilled (i.e. RSRP and RSRQ are better than specific values t-Reordering Timer to control the reordering operation of received PDCP packets. Upon expiry, PDCP packets are processed and delivered to the upper layers. TX_NEXT This state variable indicates the COUNT value of the next PDCP SDU to be transmitted. UE Inactive AS Context UE Inactive AS Context is stored when the connection is suspended and restored when the connection is resumed. It includes information below.the current KgNB and KRRCint keys, the ROHC state, the stored QoS flow to DRB mapping rules, the C-RNTI used in the source PCell, the cellIdentity and the physical cell identity of the source PCell, the spCellConfigCommon within ReconfigurationWithSync of the NR PSCell (if configured) and all other parameters configured except for:- parameters within ReconfigurationWithSync of the PCell;- parameters within ReconfigurationWithSync of the NR PSCell, if configured;- parameters within MobilityControlInfoSCG of the E-UTRA PSCell, if configured;- servingCellConfigCommonSIB; TAG A group of Serving Cells that is configured by RRC and that, for the cells with a UL configured, using the same timing reference cell and the same Timing Advance value. A Timing Advance Group containing the SpCell of a MAC entity is referred to as Primary Timing Advance Group (PTAG), whereas the term Secondary Timing Advance Group (STAG) refers to other TAGs.
[0022] In the present invention, "trigger" or "is triggered" and "initiate" or "is initiated" may be used interchangeably. In the present invention, "wireless bearer with SDT allowed," "wireless bearer with SDT set," and "wireless bearer with SDT enabled" may be used interchangeably.
[0023] In the present invention, the terminal and the UE can be used interchangeably. In the present invention, the base station, the NG-RAN node, and the GNB can be used interchangeably.
[0024] In the present invention, set, group, and set can be used interchangeably.
[0026] FIG. 1a is a diagram illustrating the structure of a 5G system and an NG-RAN according to one embodiment of the present disclosure.
[0027] The 5G system consists of NG-RAN (1a-01) and 5GC (1a-02). The NG-RAN node is one of the following two.
[0028] 1: gNB providing NR user plane and control plane to the UE; or
[0029] 2: ng-eNB providing E-UTRA user plane and control plane to the UE.
[0030] gNB (1a-05 to 1a-06) and ng-eNB (1a-03 to 1a-04) are interconnected via an Xn interface. gNB and ng-eNB are connected to an Access and Mobility Management Function (AMF) (1a-07) and a User Plane Function (UPF) (1a-08) via an NG interface. The AMF (1a-07) and UPF (1a-08) may consist of a single physical node or separate physical nodes.
[0031] gNB (1a-05 to 1a-06) and ng-eNB (1a-03 to 1a-04) host the functions listed below.
[0032] Radio bearer control, radio acceptance control, connection mobility control, dynamic allocation of resources to UEs in uplink, downlink, and sidelink (scheduled), IP and Ethernet header compression, uplink data decompression and encryption of user data streams, selection of AMF when an AMF cannot be selected with information provided by the terminal, routing of user plane data to the UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (originating from AMF or O&M);
[0033] Measurement and measurement reporting configuration for mobility and scheduling, session management, QoS flow management and mapping for data wireless bearers, RRC_INACTIVE support, wireless access network sharing;
[0034] Close interaction between NR and E-UTRA, support for network slicing.
[0036] AMF (1a-07) hosts functions such as NAS signaling, NAS signal security, AS security control, S-GW selection, authentication, mobility management, and location management.
[0037] UPF (1a-08) hosts functions such as packet routing and forwarding, transport-level packet marking for uplink and downlink, QoS management, and mobility anchoring for mobility.
[0039] Figure 1b is a diagram illustrating the wireless protocol structure of a 5G system.
[0040] The user plane protocol stack consists of SDAP (1b-01 to 1b-02), PDCP (1b-03 to 1b-04), RLC (1b-05 to 1b-06), MAC (1b-07 to 1b-08), and PHY (1b-09 to 1b-10). The control plane protocol stack consists of NAS (1b-11 to 1b-12), RRC (1b-13 to 1b-14), PDCP, RLC, MAC, and PHY.
[0041] Each protocol sublayer performs functions related to the operations listed in Table 3.
[0042] Sublayer Functions NAS Authentication, mobility management, security control, etc. RRC System information, paging, RRC connection management, security features, signaling wireless bearer and data wireless bearer management, mobility management, QoS management, detection and recovery from wireless link errors, NAS message transmission, etc. SDAP Mapping between QoS flows and data wireless bearers, marking of QoS flow IDs (QFI) of DL and UL packets. PDCP Data transmission, header compression and decompression, encryption and decryption, integrity protection and verification, redundant transmission, reordering and order delivery, etc. RLC Upper layer PDU transmission, error correction via ARQ, splitting and re-splitting of RLC SDUs, reassembly of SDUs, RLC re-establishment, etc. MAC Mapping between logical channels and transmission channels, multiplexing / demultiplexing MAC SDUs belonging to one or another logical channel from a transmission block (TB) delivered at the physical layer, information reporting schedules, priority processing between UEs, priority processing between single UE logical channels, etc. PHY Channel coding, physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.
[0043] The terminal supports three RRC states. The characteristics of each state are listed in Table 4.
[0044] RRC state Characteristic RRC_IDLE PLMN selection;Broadcast of system information;Cell re-selection mobility;Paging for mobile terminated data is initiated by 5GC;DRX for CN paging configured by NAS. RRC_INACTIVE PLMN selection;Broadcast of system information;Cell re-selection mobility;Paging is initiated by NG-RAN (RAN paging);RAN-based notification area (RNA) is managed by NG- RAN;DRX for RAN paging configured by NG-RAN;5GC - NG-RAN connection (both C / U-planes) is established for UE;The UE AS context is stored in NG-RAN and the UE;NG-RAN knows the RNA which the UE belongs to to. RRC_CONNECTED 5GC - NG-RAN connection (both C / U-planes) is established for UE;The UE AS context is stored in NG-RAN and the UE;NG-RAN knows the cell which the UE belongs to;Transfer of unicast data to / from the UE;Network controlled mobility including measurements.
[0045] FIG. 1c is a diagram illustrating the RRC state transition.
[0046] Between RRC_CONNECTED (1c-11) and RRC_INACTIVE (1c-13), a state transition occurs through the exchange of a resumption message and a Release message containing a Suspend IE.
[0047] Between RRC_CONNECTED (1c-11) and RRC_IDLE (1c-15), a state transition occurs through the establishment and disconnection of the RRC connection.
[0048] A state transition from RRC_INACTIVE(1c-13) to RRC_IDLE(1c-15) occurs through RRC disconnection.
[0050] The state transition from RRC_INACTIVE to RRC_CONNECTED involves not only signal exchange between the terminal and the base station but also context transfer and data path changes between base stations. While these additional procedures may be fully justified if the terminal has a sufficient amount of data to transmit, network efficiency may be degraded due to excessive overhead otherwise.
[0051] The present invention introduces a new resumption procedure that enables data transmission and reception without transitioning to RRC_CONNECTED. Hereinafter, the resumption procedure aimed at transitioning a terminal in the RRC_INACTIVE state to the RRC_CONNECTED state is named the first resumption procedure / RRC CONNECTION RESUME1, the procedure for a terminal in the RRC_INACTIVE state to transmit data while maintaining the RRC_INACTIVE state is named the second resumption procedure / RRC CONNECTION RESUME2, and the procedure for a terminal in the RRC_INACTIVE state to receive data while maintaining the RRC_INACTIVE state is named the third resumption procedure / RRC CONNECTION RESUME3.
[0052] SDT (Small Data Transmission) is a procedure that allows the transmission of data and / or signaling while maintaining the RRC_INACTIVE state (i.e., without transitioning to the RRC_CONNECTED state).
[0053] The SDT procedure is initiated by transmission via RACH (configured via system information) or Type 1 CG resources (configured via the dedicated signal of RRCRlease). SDT resources can be configured in the initial BWP for both RACH and CG. RACH and CG resources for SDT can be configured on one or both of the NUL and SUL carriers. CG resources for SDT are valid only within a cell UE that has received RRCRlease and transitioned to the RRC_INACTIVE state. For RACH, the network can configure Phase 2 and / or Phase 4 RA resources for SDT. If both Phase 2 and Phase 4 random access resources for SDT are configured, the UE selects a random access type.
[0054] The initial PUSCH transmission during the SDT procedure includes at least a CCCH message. When using CG resources for the initial SDT transmission, the UE may perform an autonomous retransmission of the initial transmission if the UE does not receive an acknowledgment (dynamic uplink grant or downlink assignment) from the network before the configured timer expires. Subsequent transmissions after the initial PUSCH transmission are handled differently depending on the type of resource used to initiate the SDT procedure.
[0055] When using CG resources, the network schedules subsequent UL transmissions using dynamic grants, or they may be transmitted in the case of the next CG resource. DL transmissions are scheduled using dynamic allocation. A UE can initiate a subsequent UL transmission only after receiving an acknowledgment (dynamic UL grant or downlink assignment) for the initial PUSCH transmission from the network. For a subsequent UL transmission, a UE cannot initiate a retransmission through a CG resource.
[0056] When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic uplink grants and downlink assignments, respectively, after the RA procedure is completed.
[0057] If data is generated in the buffer of a wireless bearer for which SDT is not enabled during the SDT procedure, the UE uses a UEAssistanceInformation message to send a non-SDT data arrival indication to the network and, if possible, includes the cause for resumption.
[0058] The SDT procedure for a CG resource can be initiated with valid UL timing alignment. UL timing alignment is maintained by the UE based on an SDT-specific timing alignment timer configured by the network via dedicated signaling, and is also maintained by a configured number of DL RSRPs of the highest-ranking SSB that are above the configured RSRP threshold value, even in the case of the initial CG-SDT transmission. When the SDT-specific timing alignment timer expires, the CG resource is released while maintaining the CG resource configuration.
[0059] Logical channel limits configured by the network while in the RRC_CONNECTED state and / or in the RRCRlease message for a wireless bearer enabled for SDT are applied by the UE during the SDT procedure.
[0060] SDT (Small Data Transmission) is a procedure that allows the transmission of data and / or signaling while maintaining the RRC_INACTIVE state (i.e., without transitioning to the RRC_CONNECTED state).
[0061] The SDT procedure is initiated by transmission via RACH (configured via system information) or Type 1 CG resources (configured via the dedicated signal of RRCRelease). SDT resources can be configured in the initial BWP for both RACH and CG. RACH and CG resources for SDT can be configured on one or both of the NUL and SUL carriers. CG resources for SDT are valid only within a cell UE that has received RRCRelease and transitioned to the RRC_INACTIVE state. For RACH, the network can configure Phase 2 and / or Phase 4 RA resources for SDT. If both Phase 2 and Phase 4 random access resources for SDT are configured, the UE selects a random access type.
[0062] The initial PUSCH transmission during the SDT procedure includes at least a CCCH message. When using CG resources for the initial SDT transmission, the UE may perform an autonomous retransmission of the initial transmission if the UE does not receive an acknowledgment (dynamic uplink grant or downlink assignment) from the network before the configured timer expires. Subsequent transmissions after the initial PUSCH transmission are handled differently depending on the type of resource used to initiate the SDT procedure.
[0063] When using CG resources, the network schedules subsequent UL transmissions using dynamic grants, or they may be transmitted in the case of the next CG resource. DL transmissions are scheduled using dynamic allocation. A UE can initiate a subsequent UL transmission only after receiving an acknowledgment (dynamic UL grant or downlink assignment) for the initial PUSCH transmission from the network. For a subsequent UL transmission, a UE cannot initiate a retransmission through a CG resource.
[0064] When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic uplink grants and downlink assignments, respectively, after the RA procedure is completed.
[0065] If data is generated in the buffer of a wireless bearer for which SDT is not enabled during the SDT procedure, the UE uses a UEAssistanceInformation message to send a non-SDT data arrival indication to the network and, if possible, includes the cause for resumption.
[0066] The SDT procedure for a CG resource can be initiated with a valid UL timing alignment. The UL timing alignment is maintained by the UE based on an SDT-specific timing alignment timer configured by the network via dedicated signaling, and is also maintained by a configured number of DL RSRPs of the highest-ranking SSB that are above the configured RSRP threshold value, even in the case of the initial CG-SDT transmission. When the SDT-specific timing alignment timer expires, the CG resource is released while maintaining the CG resource configuration.
[0067] Logical channel limits configured by the network while in the RRC_CONNECTED state and / or RRCRelease message for a wireless bearer enabled for SDT are applied by the UE during the SDT procedure.
[0068] SDT is divided into SDT1 and SDT2.
[0069] In SDT1, the terminal transmits the first MAC PDU containing the first CCCH SDU and DCCH data or DTCH data. In the first SDT, the terminal sets one of the first predefined values in the resumeCause field.
[0070] In SDT2, the terminal transmits only the first CCCH SDU in the MAC PDU transmitted for the first time. In SDT2, the terminal sets a predefined second value in the resumeCause field. The second value is not the same as any of the first values.
[0071] The base station determines SDT1 based on the resources transmitted by the uplink signal that the terminal first transmits.
[0072] The base station determines SDT2 based on the second value being set in the resumeCause field.
[0073] The RRC CONNECTION RESUME is intended to resume a interrupted RRC connection or start an SDT. RRC CONNECTION RESUME1 is for resuming an interrupted RRC connection. RRC CONNECTION RESUME2 is for starting the first SDT. RRC CONNECTION RESUME3 is for starting the second SDT.
[0074] RA-SDT1 is an SDT1 in which uplink data is transmitted through random access procedures and dynamic grants.
[0075] CG-SDT1 is an SDT1 in which uplink data is transmitted through a configured Type 1 grant.
[0076] RA-SDT2 is an SDT2 in which uplink data is transmitted through random access procedures and dynamic grants.
[0077] CG-SDT2 is an SDT2 in which uplink data is transmitted through a configured Type 1 grant.
[0079] RRC CONNECTION RESUME2 and SDT1 can be used interchangeably.
[0080] RRC CONNECTION RESUME3 and SDT2 can be used interchangeably.
[0081] CG-SDT1 and Type 1 RRC CONNECTION RESUME2 can be used interchangeably.
[0082] RA-SDT1 and Type 2 RRC CONNECTION RESUME2 can be used interchangeably.
[0083] CG-SDT2 and Type 1 RRC CONNECTION RESUME3 can be used interchangeably.
[0084] RA-SDT2 and Type 2 RRC CONNECTION RESUME3 are interchangeable.
[0086] FIG. 2a is a diagram illustrating the operation of a terminal and a base station according to one embodiment of the present invention.
[0087] In step 2a-11, the terminal transmits UECapabilityInformation from the first cell to the base station and transmits a NAS message to the AMF. The NAS message is a TRACKING AREA UPDATE or an ATTACH REQUEST.
[0088] UECapabilityInformation includes zero or one ra-SDT IE and zero or one or more cg-SDT IEs.
[0089] ra-SDT indicates whether the UE supports the transmission of data and / or signaling over an allowed radio bearer in the RRC_INACTIVE state via the Random Access Procedure (i.e., RA-SDT). This is a UE-specific feature. If this IE is present in UECapabilityInformation, it means that the UE supports RA-SDT in the frequency bands supported by the UE. If this IE is not present in UECapabilityInformation, it means that the UE does not support RA-SDT in the frequency bands supported by the UE.
[0090] cg-SDT indicates whether the UE supports the transmission of data and / or signaling over a radio bearer allowed in the RRC_INACTIVE state through the configured Grant Type 1 (i.e., CG-SDT). It is a band-specific function.
[0091] If this IE exists for a frequency band in UECapabilityInformation, it means that the UE supports CG-SDT for that frequency band. If this IE does not exist for a frequency band in UECapabilityInformation, it means that the UE does not support CG-SDT for that frequency band.
[0092] The NAS message contains the UE NETWORK CAPABILITY IE. The UE NETWORK CAPABILITY IE contains 11 octets. A specific bit of the 11th octet indicates whether the UE supports RRC CONNECTION RESUME3. Each bit of the 11 octets indicates whether the UE supports a specific function.
[0093] If RA-SDT1, CG-SDT1, RA-SDT2 and CG-SDT2 are supported, the UE includes both ra-SDT IE and cg-SDT IE in UECapabilityInformation and sets a specific bit of UE NETWORK CAPABILITY IE in the NAS message to 1.
[0094] If RA-SDT1 and CG-SDT1 are supported and RA-SDT2 and CG-SDT2 are not supported, the UE includes both ra-SDT IE and cg-SDT IE in UECapabilityInformation and sets a specific bit of UE NETWORK CAPABILITY IE in the NAS message to 0.
[0095] If RA-SDT1 and RA-SDT2 are supported and CG-SDT1 and CG-SDT2 are not supported, the UE includes ra-SDT IE in UECapabilityInformation, does not include cg-SDT IE, and sets a specific bit in UE NETWORK CAPABILITY IE of the NAS message to 1.
[0096] In step 2a-16, the UE receives an RRCReconfiguration message from the base station. The RRCReconfiguration message includes various configuration information to be applied to the first cell.
[0097] In step 2a-21, the terminal and the base station perform data transmission in the RRC_CONNECTED state based on the configuration information in RRCReconfiguration.
[0098] In 2a-26, the UE receives an RRCRelease message from the base station in the first cell. The base station sends an RRCRelease message to release the RRC connection (and make the UE RRC_IDLE) or to suspend the RRC connection (and make the UE RRC_INACTIVE). If the base station anticipates that data activity for the UE will occur in the near future, the base station decides to suspend the RRC connection. In this case, the RRCRelease message includes a SuspendConfig IE, and SuspendConfig includes the following fields.
[0099] <suspendconfig>
[0100] 1. First UE Identifier: An identifier of the terminal that can be included in the ResumeRequest during the state transition to RRC_CONNECTED. It has a length of 40 bits.
[0101] 2. Second UE Identifier: An identifier of the terminal that can be included in the Request during the state transition to RRC_CONNECTED. It has a length of 24 bits.
[0102] 3. ran-PagingCycle: Paging cycle to apply in RRC_INACTIVE state
[0103] 4. ran-NotificationAreaInfo: Configuration information of ran-NotificationArea consisting of a list of cells, etc. When ran_NotificationArea changes, the terminal initiates a resumption procedure.
[0104] 5. t380: Timer associated with the periodic resumption procedure
[0105] 6. NCC (nextHopChaningCount): A counter used to derive a new security key after performing the resumption procedure.
[0106] 7. sdt-Config: Configuration information for SDT.
[0107] In step 2a-31, the terminal performs the SuspendConfig action set. The SuspendConfig action set is applied at a predetermined time. When the SuspendConfig action set is performed, the following actions are performed sequentially.
[0108] <SuspendConfig 동작 집합>
[0109] 1: Reset the MAC and disable the default MAC-CellGroupConfig (if present).
[0110] 2: Apply the received suspendConfig, excluding the received nextHopChainingCount and received sdt-Config.
[0111] 3: Determine the DRB to be configured for SDT based on the sdt-DRB-List.
[0112] 4: Determine whether SRB2 is configured for SDT based on sdt-DRB2-Indication.
[0113] 5: Determine whether SRB1 is configured for SDT based on whether sdt-Config is included in SuspendConfig (or based on whether one or both of sdt-DRB-List or sdt-DRB2-Indication are included in sdt-Config).
[0114] 6: Reset RLC entities of SRB2.
[0115] 7: Perform SDU disposal for PDCP entities on SRB1.
[0116] 8: If SRB2 is configured for SDT, perform SDU disposal for the PDCP entity of SRB2.
[0117] 9: Reset RLC entity of SRB1.
[0118] 10: Store nextHopChainingCount received from the RRCRelease message, current security key, EHC status, C-RNTI used in the source PCell, PDCP configuration of the wireless bearer configured for SDT, RLC configuration of the wireless bearer configured for SDT, logical channel configuration of the wireless bearer configured for SDT, PDCP configuration of the wireless bearer not configured for SDT, RLC configuration of the wireless bearer not configured for SDT, logical channel configuration of the wireless bearer not configured for SDT, etc. in the UE INACTIVE AS context. SuspendConfig is also stored.
[0119] 11: Suspend all wireless bearers configured for SDT.
[0120] 12: Suspend all wireless bearers not configured for SDT.
[0121] 13: Enter RRC_INACTIVE state and perform cell selection.
[0123] In step 2a-36, the terminal selects the second cell of the second base station as a result of cell selection. The terminal may re-select the surrounding cell with better wireless signal quality by comparing the wireless signal quality of the serving cell and the surrounding cell. Alternatively, it may select a cell where the wireless signal quality is above a certain standard. The first cell and the second cell may be the same or different. The first base station and the second base station may be the same or different.
[0124] The UE receives system information including SIB1 from the second cell.
[0125] In step 2a-41, the UE monitors Paging Occasions (PO) in the second cell. The PO is determined based on the third UE identifier and SIB1's PCCH-configCommon.
[0126] The UE receives a paging message from the paging channel of the second cell. The paging message includes a first list and a second list. The first list includes one or more entry1s, and the second list includes one or more entry2s. Each entry1 includes a first UE identifier or a third UE identifier. Entry2 is a type 1 entry2 or a type 2 entry2. A type 1 entry2 consists of first information indicating that it is an entry2. A type 2 entry2 consists of first information and second information. The second information indicates that the paging is for RRC CONNECTION RESUME3.
[0127] The number of entry2 in the second list is the same as the number of entry1 in the first list. Entry2 in the second list and entry1 in the first list are listed in the same order.
[0128] If the first UE identifier included in entry1 of the first list matches the stored first UE identifier of the UE and the second information is included in the corresponding entry2 of the second list, the UE starts the RRC CONNECTION RESUME3 procedure with resumeCause set to RESUME3.
[0129] If the first UE identifier included in entry1 of the first list matches the first UE identifier stored in the UE and the corresponding entry2 of the second list does not contain the second information, the UE sets resumeCause to mt-Access and starts the RRC CONNECTION RESUME1 procedure.
[0130] If the third UE identifier included in entry1 of the first list matches the UE ID assigned by the upper layer, the UE performs the first set of actions.
[0131] If none of the entries in the first list match the UE's stored first identifier or the UE ID assigned by the upper layer, the UE continues to monitor the paging channel.
[0133] FIG. 2b is a diagram illustrating the operation for an RRC CONNECTION RESUME.
[0134] An event that triggers the RRC CONNECTION RESUME PROCEDURE occurs in step 2b-06. The RRC CONNECTION RESUME PROCEDURE may be triggered when a higher layer or AS requests the resumption of a suspended RRC connection, when new data occurs, when the first paging message is received, or when the second paging message is received.
[0135] The first paging message is a paging message in which the first UE identifier included in entry1 of the first list matches the first UE identifier stored in the terminal, and the second information is included in the corresponding entry2 of the second list.
[0136] The second paging message is a paging message in which the first UE identifier included in entry1 of the first list matches the first UE identifier stored in the terminal, and the second information is not included in the corresponding entry2 of the second list.
[0137] The UE initiates Type 1 RRC CONNECTION RESUME2 when all of the following conditions are met.
[0138] 1: The upper layer requests the resumption of the RRC connection and
[0139] 2: SIB1 includes sdt-ConfigCommon and
[0140] 3: sdt-Config is configured and
[0141] 4: All UL hold data is mapped to a wireless bearer configured for SDT and
[0142] 5: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0143] 6: The RSRP based on downlink path loss is higher than the sdt-RSRP-Threshold
[0144] 7: The CG-SDT is configured on the selected UL carrier, and the TA of the established Grant Type 1 resource is valid, and
[0145] 8: One or more SSBs configured for CG-SDT with an SS-RSRP higher than cg-SDT-RSRP-ThresholdSSB are available.
[0147] The UE initiates Type 2 RRC CONNECTION RESUME2 when all of the following conditions are met.
[0148] 1: The upper layer requests the resumption of the RRC connection and
[0149] 2: SIB1 includes sdt-ConfigCommon and
[0150] 3: sdt-Config is configured and
[0151] 4: All UL hold data is mapped to a wireless bearer configured for SDT and
[0152] 5: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0153] 6: The RSRP based on downlink path loss is higher than the sdt-RSRP-Threshold
[0154] 7: CG-SDT is not configured on a selected UL carrier, or the TA of the configured Grant Type 1 resource is invalid, or no SSB configured for a CG-SDT with an SS-RSRP higher than cg-SDT-RSRP-ThresholdSSB is available (or Type 2 RRC CONNECTION RESUME2 is not initiated)
[0155] 8: At least one set of random access resources on the selected uplink is available for Type 2 RRC CONNECTION RESUME2.
[0157] The UE starts Type 1 RRC CONNECTION RESUME3 when all of the following conditions are met.
[0158] 1: The first paging message is received, and
[0159] 2: SIB1 includes sdt-ConfigCommon and
[0160] 3: sdt-Config is configured and
[0161] 4: All UL hold data is mapped to a wireless bearer configured for SDT and
[0162] 5: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0163] 6: The RSRP based on downlink path loss is higher than the sdt-RSRP-Threshold
[0164] 7: The cell's downlink channel quality is higher than the sdt-CQI-Threshold, and
[0165] 8: The TA of the Grant Type 1 resource configured and set on the selected UL carrier is valid.
[0167] Alternatively, the UE initiates Type 2 RRC CONNECTION RESUME3 if all of the following conditions are met.
[0168] 1: The first paging message is received, and
[0169] 2: The cell's downlink channel quality is higher than the sdt-CQI-Threshold, and
[0170] 3: The TA of the Grant Type 1 resource configured and set on the selected UL carrier is valid.
[0172] The UE initiates Type 2 RRC CONNECTION RESUME3 when all of the following conditions are met.
[0173] 1: The first paging message is received, and
[0174] 2: SIB1 includes sdt-ConfigCommon and
[0175] 3: sdt-Config is configured and
[0176] 4: All UL hold data is mapped to a wireless bearer configured for SDT and
[0177] 5: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0178] 6: The RSRP based on downlink path loss is higher than the sdt-RSRP-Threshold
[0179] 7: The cell's downlink channel quality is higher than the sdt-CQI-Threshold, and
[0180] 8: CG-SDT is not configured on a selected UL carrier, or the TA of the configured Grant Type 1 resource is invalid, or no SSB configured for CG-SDT is available with an SS-RSRP higher than cg-SDT-RSRP-ThresholdSSB (or Type 1 RRC CONNECTION RESUME3 is not initiated).
[0182] Alternatively, the UE starts TYPE2 RRC CONNECTION RESUME3 if all of the following conditions are met.
[0183] 1: The first paging message is received, and
[0184] 2: The cell's downlink channel quality is higher than the sdt-CQI-Threshold.
[0186] Alternatively, the UE initiates Type 2 RRC CONNECTION RESUME3 regardless of whether CG-SDT is configured (i.e., only RA-SDT applies to RRC CONNECTION RESUME3).
[0188] RRC CONNECTION RESUME2 is a procedure for the UE to transmit uplink data without transitioning to RRC_CONNECTED. This is why the uplink data volume and uplink channel quality are tested before initiating RRC CONNECTION RESUME2.
[0189] RRC CONNECTION RESUME3 is a procedure for the UE to receive downlink data without transitioning to RRC_CONNECTED. This is the reason for testing the downlink channel quality before initiating RRC CONNECTION RESUME3.
[0191] The UE starts RRC CONNECTION RESUME1 when one of the following conditions is met.
[0192] 1: When a second paging message is received or
[0193] 2: RNA renewal is triggered by T380 expiration or
[0194] 3: RNA renewal is triggered by RNA changes
[0196] A UE of RRC_INACTIVE starts RRC CONNECTION RESUME2 when both the upper-level condition set for initiating RRC CONNECTION RESUME2 and the lower-level condition set for initiating RRC CONNECTION RESUME2 are satisfied.
[0197] The upper-level condition set for initiating RRC CONNECTION RESUME2 is satisfied when all of the following conditions are met.
[0198] 1: The upper layer requests the resumption of the RRC connection and
[0199] 2: SIB1 includes sdt-ConfigCommon and
[0200] 3: sdt-Config is configured and
[0201] 4: All UL hold data is mapped to a wireless bearer configured for SDT and
[0202] 5: The data volume of pending UL data across all RBs configured for SDT is less than or equal to sdt-DataVolumeThreshold.
[0204] The set of lower-level conditions for initiating RRC CONNECTION RESUME2 is satisfied in CASE1, CASE2, CASE3, and CASE4.
[0206] <CASE 1>
[0207] 1: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0208] 2: The RSRP based on downlink path loss is higher than the sdt-RSRP-Threshold
[0209] 3: The CG-SDT is configured on the selected UL carrier, and the TA of the set Grant Type 1 resource is valid, and
[0210] 4: One or more SSBs configured for CG-SDT with an SS-RSRP higher than the cg-SDT-RSRP-ThresholdSSB are available.
[0212] <CASE 2>
[0213] 1: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0214] 2: sdt-RSRP-Threshold is not set and
[0215] 3: The CG-SDT is configured on the selected UL carrier, and the TA of the set Grant Type 1 resource is valid, and
[0216] 4: One or more SSBs configured for CG-SDT with an SS-RSRP higher than the cg-SDT-RSRP-ThresholdSSB are available.
[0218] <CASE 3>
[0219] 1: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0220] 2: The RSRP based on downlink path loss is higher than the sdt-RSRP-Threshold
[0221] 3: CG-SDT is not configured on the selected UL carrier, or the TA of the configured Grant Type 1 resource is invalid and
[0222] 4: At least one set of random access resources is available on the selected uplink for Type 2 RRC CONNECTION RESUME2.
[0224] <CASE 4>
[0225] 1: The data volume of pending UL data across all RBs configured for the SDT is less than or equal to sdt-DataVolumeThreshold and
[0226] 2: sdt-RSRP-Threshold is not set and
[0227] 3: CG-SDT is not configured on the selected UL carrier, or the TA of the configured Grant Type 1 resource is invalid and
[0228] 4: At least one set of random access resources is available on the selected uplink for Type 2 RRC CONNECTION RESUME2.
[0230] The TA of a configured Grant Type 1 resource is valid in the following cases.
[0231] 1: The RSRP values for the saved downlink path loss reference and the current downlink path loss reference are valid. And
[0232] 2: Compared to the saved downlink path loss reference RSRP value, the current RSRP value of the downlink path loss reference has not increased or decreased by more than cg-SDT-RSRP-ChangeThreshold.
[0233] 3: cg-SDT-TimeAlignmentTimer is running.
[0235] When the UE receives the CG-SDT configuration, it stores the RSRP of the downlink path loss reference for the serving cell.
[0236] When the UE receives RRCRelease containing sdt-MAC-PHY-CG-Config, it starts cg-SDT-TimeAlignmentTimer.
[0238] The UE of RRC_INACTIVE starts RRC CONNECTION RESUME3 when the upper-level conditions for starting RRC CONNECTION RESUME3 are satisfied.
[0239] The upper-level conditions for RRC CONNECTION RESUME 3 are satisfied when all of the following conditions are met.
[0240] 1: The first paging message is received and
[0241] 2: The SIB1 of the cell that received the first paging message includes sdt-ConfigCommon
[0242] 3: sdt-Config is configured (i.e., the RRCRelease message includes sdt-Config)
[0243] 4: Excluding CCCH SDU from UL, there is no pending data.
[0245] In step 2b-11, the UE transmits the first CCCH SDU to the base station.
[0246] The first CCCH SDU is an RRCResumeRequest in the following cases.
[0247] 1: RRC CONNECTION RESUME1 starts.
[0248] 2: Type 1 RRC CONNECTION RESUME2 starts.
[0249] 3: Type 2 RRC CONNECTION RESUME2 starts.
[0250] The RRCResumeRequest includes the following fields and IE.
[0251] Field IE Description resumeIdentity I-RNTI-Value First UE identifier provided by RRCRelease resumeMAC-I 16-bit BIT STRING Authentication tokens that facilitate UE authentication resumeCause Resume Cause It can represent one of the predefined first values. The predefined first values are Emergency, mt-Access, mo-Signalling, mo-Data, etc.
[0253] The first CCCH SDU is RRCResumeRequest2 in the following cases.
[0254] 1: Type 1 RRC CONNECTION RESUME3 starts.
[0255] 2: Type 2 RRC CONNECTION RESUME3 starts.
[0256] RRCResumeRequest2 includes the following fields and IE.
[0258] Field IE Description resumeIdentity ShortI-RNTI-Value Second UE identifier provided by RRCRelease resumeMAC-I 16-bit BIT STRING Authentication tokens that facilitate UE authentication resumeCause Resume Cause Represents a predefined second value. The predefined second value is RRC CONNECTION RESUME3. ChannelQualityIndicator 4-bit BIT STRING Each of the 16 code points of the downlink channel quality indicator of the initial BWP of the cell where the random access procedure is performed (or the CCCH SDU is transmitted) corresponds to a predefined combination of modulation, code rate, and transmission block size. MeasQuantityResults RSRP-Range RSRP of the serving cell derived based on a specific SS / PBCH block of the cell where the random access procedure is performed (or the CCCH SDU is transmitted). The SS / PBCH block selected for the transmission of the random access preamble is the specific SS / PBCH block.
[0259] To transmit the first CCCH SDU, a random access procedure is performed in the following cases.
[0260] 1: RRC CONNECTION RESUME1 starts.
[0261] 2: Type 2 RRC CONNECTION RESUME2 starts.
[0262] 3: Type 2 RRC CONNECTION RESUME3 starts.
[0264] To transmit the 1st CCCH SDU, use the configured grant / resource in the following cases.
[0265] 1: Type 1 RRC CONNECTION RESUME2 starts.
[0266] 2: Type 1 RRC CONNECTION RESUME3 starts.
[0269] In step 2b-16, the UE performs data transmission with the base station after the first CCCH SDU transmission. Uplink data transmission is performed in RRC CONNECTION RESUME2. Downlink data transmission is performed in RRC CONNECTION RESUME3.
[0270] The first C-RNTI is used for data transmission in Type 2 RRC CONNECTION RESUME2 and Type 2 RRC CONNECTION RESUME3.
[0271] The first CS-RNTI is used for data transmission in Type 1 RRC CONNECTION RESUME2 and Type 1 RRC CONNECTION RESUME3.
[0272] The first C-RNTI is received in the random access response.
[0273] The first CS-RNTI is received from RRCRelease.
[0276] In step 2b-21, the UE receives a first DL RRC message to terminate the RRC CONNECTION RESUME PROCEDURE. The first DL RRC message of RRC CONNECTION RESUME1 is RRCSetUp. The first DL RRC message of RRC CONNECTION RESUME2 is RRCRelease. The first DL RRC message of RRC CONNECTION RESUME3 is RRCRelease.
[0278] The random access procedure is explained below.
[0279] When a random access procedure for an RRC CONNECTION RESUME (i.e., RRC CONNECTION RESUME1 or or Type 2 RRC CONNECTION RESUME2 or Type 2 RRC CONNECTION RESUME3) is initiated from a cell, the UE selects an uplink based on the information contained in the cell's SIB1.
[0280] If a serving cell for a random access procedure is set as an additional uplink and the RSRP of the downlink path loss reference is smaller than rsrp-ThresholdSSB-SUL, the UE selects a SUL carrier to perform the random access procedure.
[0281] If the serving cell for the random access procedure is not configured with an additional uplink, or if the RSRP of the downlink path loss reference is greater than or equal to rsrp-ThresholdSSB-SUL, the UE selects a NUL carrier to perform the random access procedure.
[0282] The UE selects a set of random access resources applicable to the current random access procedure based on one or more RACH-ConfigCommon IEs and features applicable to the random access procedure in the cell's SIB1.
[0283] If one or more features including RedCap and / or specific NSAG and / or RESUME2 and / or MSG3 iterations are applicable to this random access procedure, and none of the sets of random access resources are available for any feature applicable to the current random access procedure, the UE selects a set(s) of random access resources not associated with the feature indication for this random access procedure.
[0284] If one or more features including RedCap and / or specific NSAG and / or RESUME2 and / or MSG3 iterations are applicable to this random access procedure, and there is one set of random access resources available for all features triggering this random access procedure, the UE selects this set of random access resources for this random access procedure.
[0285] If there are no features applicable to this random access procedure, the UE selects a set of random access resources that are not associated with any feature indication for the current random access procedure.
[0286] If the UE is a RedCap UE, RedCap features are applied to the current Random Access procedure. RedCap UEs have reduced features compared to non-RedCap UEs to lower complexity. RedCap UEs must support a maximum UE channel bandwidth of 20 MHz in FR1 and 100 MHz in FR2.
[0287] If a BWP for a random access procedure consists of a set of random access resources with MSG3 repeat marks, the MSG3 repeat feature is applicable to the current random access procedure.
[0288] When a random access procedure is initiated for Type 2 RRC CONNECTION RESUME2, the RESUME2 feature is applied to the current random access procedure.
[0289] The UE performs a random access procedure based on a set of random access resources selected for the current random access procedure, a set of parameters 1 associated with the set of random access resources, and a set of parameters 2 associated with the set of random access resources.
[0290] A set of random access resources is associated (or corresponds) with a FeatureCombinationPreambles IE.
[0291] A parameter set 1 is associated with one or more FeatureCombinationPreambles IEs. Parameter set 1 applies commonly to one or more sets of random access resources. The one or more sets of random access resources are associated with one or more FeatureCombinationPreambles IEs.
[0292] A parameter set 1 associated with a set of random access resources is included in the non-extended part of RACH-ConfigCommon that includes one or more associated FeatureCombinationPreambles IE.
[0293] Parameter set 2 is associated with a single FeatureCombinationPreambles IE. Parameter set 2 is included in the associated FeatureCombinationPreambles IE. Parameter set 2 applies to a set of random access resources associated with the FeatureCombinationPreambles IE.
[0294] FeatureCombinationPreamble IE is included in the extension part of RACH-ConfigCommon.
[0295] Parameter set 1 includes fields such as prach-ConfigurationIndex, msg1-FrequencyStart, preambleReceivedTargetPower, ra-ResponseWindow, preambleTransMax, msg1-SubcarrierSpacing, rsrp-ThresholdSSB, rsrp-ThresholdSSB-SUL, and ra-ContentionResolutionTimer.
[0296] Parameter set 2 includes fields such as messagePowerOffsetGroupB, rsrp-ThresholdSSB, deltaPreamble, and ra-SizeGroupA.
[0297] The UE selects an SSB based on the rsrp-ThresholdSSB of parameter set 2 associated with the set of random access resources selected for this random access procedure.
[0298] The UE selects an SSB without relying on the rsrp-ThresholdSSB of parameter set 1 associated with the set of random access resources selected for this random access procedure.
[0299] The UE selects a preamble group based on ra-Msg3SizeGroupA (or ra-SizeGroupA), messagePowerOffsetGroupB, and numberOfRA-PreamblesGroupA of FeatureCombinationPreambles IE, which are associated with the set of random access resources selected for the current random access procedure.
[0300] A total of 64 preambles are defined. They can be divided into two groups. UEs with large data and good channel conditions can select Preamble Group B so that the GNB can allocate larger UL grants. UEs with small data or poor channel conditions can select Preamble Group A so that the GNB can allocate standard UL grants.
[0301] If the potential Msg3 size (transmittable UL data, MAC subheader(s), and MAC CE if necessary) is greater than ra-Msg3SizeGroupA (or ra-SizeGroupA) and the path loss is less than the preambleReceivedTargetPower and msg3-DeltaPreamble or deltaPreamble and messagePowerOffsetGroupB subtracted from PCMAX (of the serving cell performing the random access procedure), the UE selects random access preamble group B.
[0302] A random access procedure is initiated for a CCCH logical channel, and if the CCCH SDU size and MAC subheader are larger than ra-Msg3SizeGroupA (or ra-SizeGroupA), the UE selects random access preamble group B.
[0303] If a random access procedure is not initiated for a CCCH logical channel and the potential Msg3 size (UL data and MAC subheader(s) available for transmission and MAC CE if necessary) is not larger than ra-Msg3SizeGroupA (or ra-SizeGroupA), the UE selects random access preamble group A.
[0304] When a random access procedure is initiated for a CCCH logical channel and the potential Msg3 size (UL data available for transmission + MAC subheader(s) and MAC CE if necessary) is not larger than ra-Msg3SizeGroupA (or ra-SizeGroupA), the UE selects random access preamble group A.
[0305] If a random access procedure has not been initiated for a CCCH logical channel and the potential Msg3 size (UL data and MAC subheader(s) available for transmission and MAC CE if necessary) is greater than ra-Msg3SizeGroupA (or ra-SizeGroupA), and the path loss is not less than the preambleReceivedTargetPower minus msg3-DeltaPreamble or deltaPreamble minus messagePowerOffsetGroupB at PCMAX (of the serving cell performing the random access procedure), then the UE selects a random access preamble group A.
[0306] For this random access procedure, preambleReceivedTargetPower of parameter set1, associated with the set of random access resources selected, is used.
[0307] For this random access procedure, messagePowerOffsetGroupB of parameter set2, which is associated with the set of selected random access resources, is used.
[0308] If deltaPreamble is included in parameter set 2 associated with the set of random access resources selected for this random access procedure, deltaPreamble is used.
[0309] If deltaPreamble is not included in parameter set 2 associated with the set of random access resources selected for this random access procedure, msg3-DeltaPreamble included in PUSCH-ConfigCommon of the uplink initial BWP is used.
[0310] If there exists a parameter set 2 (or FeatureCombinationPreambles IE) associated with the set of random access resources selected for this random access procedure, ra-SizeGroupA of parameter set 2 is used.
[0311] If parameter set 2 (or FeatureCombinationPreambles IE) associated with the set of random access resources selected for this random access procedure does not exist, ra-Msg3SizeGroupA of parameter set 1 is used.
[0312] If no features are applied to this random access procedure, there is no parameter set 2 (or FeatureCombinationPreambles IE) associated with the set of random access resources selected for this random access procedure.
[0314] The UE randomly selects a preamble with equal probability from among the preambles associated with the selected SSB and the selected preamble group. The UE sets PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected preamble.
[0315] The UE determines the next available PRACH opportunity from the PRACH opportunity corresponding to the selected SSB. The UE must randomly select a PRACH opportunity with equal probability from a series of PRACH opportunities indicated by the PRACH configuration index of parameter set 1 associated with the set of random access resources selected for this random access procedure.
[0316] The UE transmits the selected preamble to the selected PRACH opportunity on the selected uplink.
[0317] The UE sets PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × powerRampingStep + POWER_OFFSET_2STEP_RA.
[0318] The UE sets the transmission power of the preamble to the sum of PREAMBLE_RECEIVED_TARGET_POWER and the path loss of the downlink path loss reference.
[0319] For this random access procedure, preambleReceivedTargetPower of parameter set1, associated with the set of random access resources selected, is used.
[0320] The UE sets DELTA_PREAMBLE according to the preamble format determined by the prach-ConfigurationIndex indicated in parameter set 1 associated with the set of random access resources selected for this random access procedure. DELTA_PREAMBLE is predefined for each preamble format. PREAMBLE_POWER_RAMPING_COUNTER is initialized to 1 and increments by 1 for each preamble transmission.
[0321] The UE receives an uplink grant from the RAR.
[0322] To receive RAR, the UE starts the ra-ResponseWindow configured in RACH-ConfigCommon on the first PDCCH opportunity after the random access preamble transmission ends. While the ra-ResponseWindow is running, the UE monitors the SpCell's PDCCH for random access response(s) identified by RA-RNTI.
[0323] For this random access procedure, the ra-ResponseWindow of parameter set 1 associated with the set of selected random access resources is used.
[0324] The UE considers the reception of a random access response successful if it contains a MAC subPDU with a random access preamble identifier corresponding to the PREAMBLE_INDEX to which the random access response was transmitted.
[0325] The MAC subPDU contains a MAC RAR. The MAC RAR includes fields such as Timing Advance Command, Uplink Grant, and Temporary C-RNTI. The Timing Advance Command field represents an index value used to control the amount of timing adjustment the UE must apply. The size of the Timing Advance Command field is 12 bits. Based on the Timing Advance Command field, the terminal adjusts the uplink transmission timing and starts the timeAlignmentTimer. The timeAlignmentTimer is set to timeAlignmentTimerCommon, and the same timeAlignmentTimerCommon is applied to all feature combinations of a single uplink. The Uplink Grant field indicates the resources to be used on the uplink. The size of the Uplink Grant field is 27 bits. The Temporary C-RNTI field represents a temporary ID used by the UE during random access. The size of the Temporary C-RNTI field is 16 bits.
[0326] The uplink grant field additionally includes the PUSCH time resource allocation field. The PUSCH time resource allocation field is 4 bits.
[0327] The UE performs the transmission of Msg 3 in the slot determined above according to the UL grant in the received RAR.
[0328] The UE determines the PUSCH transmission power by summing the offset, path loss, PRB number, and other parameters associated with power control commands.
[0329] The offset is the sum of preambleReceivedTargetPower and msg3-DeltaPreamble or deltaPreamble.
[0330] For this random access procedure, preambleReceivedTargetPower of parameter set1, associated with the set of random access resources selected, is used.
[0331] If deltaPreamble is included in parameter set 2 associated with the set of random access resources selected for this random access procedure, deltaPreamble is used.
[0332] If deltaPreamble is not included in parameter set 2 associated with the set of random access resources selected for this random access procedure, msg3-DeltaPreamble included in PUSCH-ConfigCommon of the uplink initial BWP is used.
[0333] The UE generates Msg3. If RRC CONNECTION RESUME2 is applied, Msg3 (or a MAC PDU scheduled by RAR) contains an RRC message and DRB data. The RRC message is not encrypted, and the DRB data is encrypted with a security key stored in the UE AS context. The RRC message is included in the first MAC SDU, and the DRB data is included in the second MAC SDU. The first and second MAC SDUs consist of a MAC subheader and a MAC payload. The MAC payload of the second MAC SDU contains the DRB data. The MAC subheader is not encrypted. The second MAC SDU follows the first MAC SDU.
[0334] The UE sends Msg3. The UE starts the contention-ResolutionTimer. The timer is set to the value displayed in the selected RACH-ConfigCommon of the selected uplink carrier.
[0335] If RRC CONNECTION RESUME3 is applied, Msg3 contains an RRC message. The RRC message is not encrypted.
[0336] The GNB receives Msg 3 and processes the content. If there is an RRC message requesting a connection setup, the GNB performs call acceptance control and takes action based on the result.
[0337] The UE receives Msg 4 from the base station. Msg 4 contains MAC CE. If the UE contention resolution identity in the MAC CE matches the CCCH SDU transmitted in Msg3, the UE considers this contention resolution successful.
[0339] Various messages and IEs are explained below.
[0340] The UE receives SIB1 from a suitable cell. The GNB includes various information in SIB1. SIB1 contains information relevant to evaluating whether the UE can access the cell and defines the scheduling of other system information. It also includes radio resource configuration information common to all UEs. Additionally, it includes radio resource configuration information common to feature combinations.
[0341] SIB1 includes ServingCellConfigCommonSIB IE. ServingCellConfigCommonSIB IE includes the downlinkConfigCommon field, the uplinkConfigCommon field, the SupplementaryUplink field, and the uplinkConfigCommon-v1700 field. The downlinkConfigCommon field includes DownlinkConfigCommonSIB IE. The uplinkConfigCommon field includes UplinkConfigCommonSIB IE. The SupplementaryUplink field includes UplinkConfigCommonSIB. The uplinkConfigCommon-v1700 field includes UplinkConfigCommon-v1700 IE.
[0343] DownlinkConfigCommonSIB provides common downlink parameters for the cell. DownlinkConfigCommonSIB IE includes the initialDownlinkBWP field, the bcch-Config field, the pcch-Config field, and the initialDownlinkBWP-RedCap field.
[0344] The initialDownlinkBWP field contains BWP-DownlinkCommon IE. It provides the initial downlink BWP configuration for the PCell.
[0345] The bcch-Config field includes BCCH-Config IE.
[0346] The pcch-Config field includes PCCH-Config IE.
[0347] The initialDownlinkBWP-RedCap-r17 field contains BWP-DownlinkCommon IE. It provides the initial downlink BWP configuration for the PCell for RedCap UEs.
[0349] PCCH-Config IE is a configuration associated with paging. It consists of sub-fields such as base station paging cycle, parameters associated with PF, and parameters associated with PO.
[0350] BCCH-config IE is a configuration associated with system information. It consists of sub-fields such as modificationPeriodCoeff, which indicates the length of the modification period.
[0351] BWP-DownlinkCommon IE is a configuration of the downlink BWP. It includes the BWP IE, PDCCH-ConfigCommon IE, and PDSCH-ConfigCommon IE fields.
[0353] PDCCH-ConfigCommon is a cell-specific PDCCH parameter of this BWP. It consists of sub-fields such as controlResourceSetZero, commonControlResourceSet, searchSpaceZero, commonSearchSpaceList, searchSpaceOtherSystemInformation, pagingSearchSpace, and ra-SearchSpace.
[0354] controlResourceSetZero contains an integer between 0 and 15. It indicates one of the predefined CORESET#0 configurations.
[0355] commonControlResourceSet is a common CORESET defined as ControlResourceSet IE. It defines additional CORESETs that can be used for receiving pagination, receiving random access responses, receiving system information, etc.
[0356] commonSearchSpaceList is a list of shared SSs. Shared SSs can be used for receiving pagination, receiving random access responses, receiving system information, etc.
[0357] searchSpaceOtherSystemInformation includes the SS identifier IE.
[0358] pagingSearchSpace includes the SS identifier IE.
[0359] ra-SearchSpace includes the SS identifier IE.
[0361] PDSCH-ConfigCommon IE is configured as pdsch-TimeDomainAllocationList as a cell-specific PDSCH parameter of this BWP. pdsch-TimeDomainAllocationList contains one or more pdsch-TimeDomainAllocations.
[0362] pdsch-TimeDomainAllocation is the time domain relationship between PDCCH and PDSCH. It consists of fields such as K0 and startSymbolAndLength. K0 is the slot offset between the DCI and the scheduled PDSCH. startSymbolAndLength is an index representing a valid combination of start symbol and length.
[0364] The UplinkConfigCommonSIB IE in the uplinkConfigCommon field provides the cell's common uplink parameters for general uplinks.
[0365] The UplinkConfigCommonSIB IE in the SupplementaryUplink field provides the cell's common uplink parameters for the auxiliary uplink.
[0366] UplinkConfigCommon-v1700 IE provides common uplink parameters for cells for RedCap UE.
[0368] UplinkConfigCommonSIB IE is the common uplink configuration for the serving cell. It includes fields such as frequencyInfoUL, initialUplinkBWP, and timeAlignmentTimerCommon.
[0370] UplinkConfigCommon-v1700 IE is the common uplink configuration for serving cells for RedCap UEs. It includes the initialUplinkBWP-RedCap field.
[0372] The FrequencyInfoUL-SIB IE in the frequencyInfoUL field is the basic parameter of the uplink carrier. This includes fields such as the frequency band list and carrier bandwidth for each SCS.
[0373] The BWP-UplinkCommon IE in the initialUplinkBWP and initialUplinkBWP-RedCap fields is the configuration of the uplink initial BWP. This includes IEs such as BWP, RACH-ConfigCommon (within the rach-ConfigCommon field), PUSCH-ConfigCommon, PUCCH-ConfigCommon, and AdditionalRACH-ConfigList (within the additionalRACH-ConfigList field).
[0374] timeAlignmentTimerCommon is a timer applied when a terminal performs random access for the RRC connection establishment and re-establishment procedures. It starts running the timer when the UE receives a RAR and stops running the timer if contention fails.
[0376] AdditionalRACH-ConfigList IE contains a list of RACH settings by feature or combination of features. This includes one or more RACH-ConfigCommon IEs.
[0378] RACH-ConfigCommon IE (in the rach-ConfigCommon field or in the additionalRACH-ConfigList field) is a cell-specific random access parameter of this BWP. It includes fields such as rach-ConfigurationIndex, msg1-FrequencyStart, preambleReceivedTargetPower, ra-ResponseWindow, preambleTransMax, msg1-SubcarrierSpacing, rsrp-ThresholdSSB, rsrp-ThresholdSSB-SUL, ra-ContentionResolutionTimer, and optionally the featureCombinationPreamblesList field.
[0379] The prach-ConfigurationIndex is a PRACH configuration index. A single PRACH configuration corresponds to pattern information regarding PRACH transmission opportunities in the time domain (information indicating which symbol in which slot of which radio frame PRACH transmission is possible) and the transmission format of the Preamble, etc.
[0380] msg1-FrequencyStart is the offset from PRB0 of the lowest PRACH transmission opportunity. It is information indicating the PRACH transmission resource in the frequency domain. PRB0 is the PRB of the lowest frequency among the PRBs of the corresponding carrier.
[0381] preambleReceivedTargetPower is the target power level of the network receiver. It is a parameter associated with transmission output control during the random access procedure.
[0382] ra-ResponseWindow is the length of the random access response window represented by the number of slots.
[0383] preambleTransMax is the maximum number of random access preamble transmissions.
[0384] msg1-SubcarrierSpacing. is the SCS of PRACH. It applies to both standard terminals and RedCap UEs.
[0385] rsrp-ThresholdSSB is the criterion for selecting an SSB. The terminal selects a preamble corresponding to the selected SSB and performs random access.
[0386] rsrp-ThresholdSSB-SUL is the SUL selection criterion. The terminal selects a SUL carrier to perform random access based at least partially on this threshold.
[0387] ra-ContentionResolutionTimer is the initial value of the contention resolution timer. It displays the number of subframes.
[0388] The featureCombinationPreambleList field contains one or more FeatureCombinationPreambles IEs.
[0389] FeatureCombinationPreambles IE is associated with a set of random access resources.
[0390] FeatureCombinationPreambles IE includes the following fields and IE.
[0391] Field name IE Description featureCombination Feature Combination This field indicates the combination of features associated with the preamble displayed by this IE. startPreambleForThisPartition INTEGER (1..64) Defines the first preamble associated with the feature combination. numberOfPreamblesForThisPartition NTEGER (1..64) Determine the number of consecutive preambles associated with the feature combination. ra-SizeGroupA ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800, b1000, b72, spare6, spare5,spare4, spare3, spare2, spare1} Bitwise transmission block size threshold at which the UE must use the competition-based RA preamble of Group A. messagePowerOffsetGroupB ENUMERATED { minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18} This is the threshold for preamble selection. The value is in dB. The -infinity value corresponds to -infinity. numberOfRA-PreamblesGroupA INTEGER (1..64) Determine how many consecutive preambles per SSB are connected to group A. rsrp-ThresholdSSB RSRP-Range L1-RSRP threshold used to determine whether the UE can use a candidate beam deltaPreamble INTEGER (-1..6) Power offset between msg3 and RACH preamble transmission
[0393] FeatureCombination IE represents a feature or combination of features to be associated with a set of random access resources.
[0394] featureCombination indicates the feature combination to which this RACH configuration is applied. featureCombination IE includes the redCap, RESUME2, covEnh, and slicing fields. The redCap, RESUME2, and covEnh fields are 1-bit fields listed as a single value of "true". If these fields are present, they indicate that redcap, RESUME2, or coverage Enhancement is one of the features in this feature combination.
[0396] The UE that receives the information applies the timeAlignmentTimerCommon received from SIB1 to the timeAlignmentTimer before initiating the transmission of a predetermined uplink RRC message.
[0397] The aforementioned predetermined uplink RRC message may be an RRCSetupRequest, an RRCReestablishmentRequest, or an RRCResumeRequest. An RRC_IDLE terminal transmits an RRCSetupRequest message to establish an RRC connection. An RRC_INACTIVE terminal transmits an RRCResumeRequest message to resume the RRC connection. An RRC_CONNECTED terminal transmits an RRCReestablishmentRequest message to re-establish the RRC connection.
[0398] When the transmission of the above uplink RRC message is initiated, the random access procedure is initiated.
[0400] There are two types of transfers without dynamic grants.
[0401] Set grant type 1, where the uplink grant is provided by the RRC and stored as the set uplink grant;
[0402] Set grant type 2, which is saved or cleared as a set uplink grant based on L1 signaling indicating uplink grant activation or deactivation provided by PDCCH.
[0403] Type 1 and Type 2 are configured per BWP by RRC for the serving cell. Multiple settings can be enabled simultaneously in the same BWP. For Type 2, enabling and disabling are independent between serving cells.
[0404] RRC sets the following parameters when the configured grant type 1 is configured.
[0405] cs-RNTI: CS-RNTI for retransmission;
[0406] Periodicity: Periodicity of configured Grant Type 1;
[0407] timeDomainOffset: Offset of resource for SFN = timeReferenceSFN in time domain;
[0408] timeDomainAllocation: Uplink grant allocation configured in a time domain containing startSymbolAndLength or startSymbol;
[0409] nrofHARQ-Processes: Number of HARQ processes for the configured grant;
[0410] timeReferenceSFN: An SFN used to determine the offset of a resource in the time domain. The UE uses the nearest numbered SFN prior to receiving the configured grant configuration.
[0411] frequencyHopping: The value intraSlot enables 'frequency hopping within a slot', and the value interSlot enables 'frequency hopping between slots'. If the field is absent, frequency hopping is not configured.
[0412] p0-PUSCH-Alpha: This field contains an index representing the p0 value.
[0413] When the configured grant type 2 is configured, RRC configures the following parameters.
[0414] cs-RNTI: CS-RNTI for enable, disable, and retransmission;
[0415] Periodicity: Periodicity of configured Grant Type 2;
[0416] nrofHARQ-Processes: Number of HARQ processes for the configured grant;
[0417] cs-RNTI is included in PhysicalCellGroupConfig IE or SuspendConfig IE.
[0418] Periodicity, timeDomainOffset, timeDomainAllocation, nrofHARQ-Processes, frequencyHopping, p0-PUSCH-Alpha, and timeReferenceSFN are included in ConfiguredGrantConfig.
[0419] If ConfiguredGrantConfig IE is included in the second part of SuspendConfig of the RRCRelease message, ConfiguredGrantConfig IE may additionally include the sdt-P0-PUSCH field. Instead of the value specified in the PO-PUSCH field of PUSCH-Config IE, the value specified in the sdt-P0-PUSCH field is applied to the initial transfer based on the grant set in the RRC_INACTIVE state.
[0420] The RRCReconfiguration message includes one PhysicalCellGroupConfig IE and multiple ConfiguredGrantConfig IEs.
[0421] The RRCRelease message contains zero or one cs-RNTI field. The RRCRelease message contains zero or one or more ConfiguredGrantConfigs.
[0423] The sdt-Config field includes SDT-Config IE. SDT-Config IE includes the sdt-DRB-List, sdt-SRB2-Indication, sdt-MAC-PHY-CG-Config, and sdt-DRB-ContinueEHC fields.
[0424] sdt-DRB-ContinueEHC includes an IE indicating either cell or rna. This field indicates whether the PDCP entity for a wireless bearer configured for SDT continues or resets the EHC header compression protocol during PDCP reset in the SDT procedure. The value 'cell' indicates that ROHC header compression continues when resuming SDT in the same cell as the PCell upon receiving the RRCRelease message. The 'rna' value indicates that EHC header compression continues when resuming SDT in a cell belonging to the same RNA as the PCell upon receiving the RRCRelease message. If the field is absent, the PDCP entity for the wireless bearer configured for SDT resets the EHC header compression protocol during PDCP reset in the SDT procedure.
[0425] The sdt-DRB-List contains zero or more DRB-Identities. This field indicates the IDs of the DRBs set for the SDT. If the size of the sequence is 0, the UE assumes that no DRBs are set for the SDT.
[0426] sdt-SRB2-Indication includes an IE indicating that it is allowed. This field indicates whether SRB2 is configured for SDT. If the field is missing, SRB2 is not set for SDT.
[0427] The sdt-MAC-PHY-CG-Config field contains SDT-MAC-PHY-CG-Config IE. SDT-MAC-PHY-CG-Config IE contains the following fields: cg-SDT-Config-LCH-restrictionToAddModList, cg-SDT-Config-Initial-BWP-NUL, cg-SDT-Config-Initial-BWP-SUL, cg-SDT-Config-Initial-BWP-DL, cg-SDT-TimeAlignmentTimer, cg-SDT-RSRP-ThresholdSSB, C-RNTI, CS-RNTI.
[0428] cg-SDT-Config-LCH-restrictionToAddModList contains one or more CG-SDT-Config-LCH-restriction IEs. A CG-SDT-Config-LCH-restriction IE contains a logicalChannelIdentity field and a configuredGrantType1Allowed field. A CG-SDT-Config-LCH-restriction IE indicates whether the logical channel indicated by the logicalChannelIdentity field is allowed to use a Type1 configured grant.
[0429] cg-SDT-Config-Initial-BWP-NUL includes BWP-Uplink-Dedicated-SDT IE.
[0430] cg-SDT-Config-Initial-BWP-SUL includes BWP-Uplink-Dedicated-SDT IE.
[0431] BWP-Uplink-Dedicated-SDT IE includes PUSCH-Config IE and ConfiguredGrantConfigToAddModList IE.
[0432] PUSCH-Config IE is used to configure UE-specific PUSCH parameters applicable to the initial BWP of the first cell.
[0433] ConfiguredGrantConfigToAddModList IE contains one or more ConfiguredGrantConfigToAddMod IEs.
[0434] cg-SDT-Config-Initial-BWP-DL includes BWP-Downlink-Dedicated-SDT IE. BWP-Downlink-Dedicated-SDT IE includes PDCCH-Config IE and PDSCH-Config IE.
[0435] PDCCH-Config IE is used to configure UE-specific PDCCH parameters applicable to the initial BWP of the first cell.
[0436] PDSCH-Config IE is used to configure UE-specific PDSCH parameters applicable to the initial BWP of the first cell.
[0437] cg-SDT-TimeAlignmentTimer includes TimeAlignmentTimer IE. This field represents the TAT value for CG-SDT.
[0438] cg-SDT-RSRP-ThresholdSSB includes RSRP-Range IE. This field indicates the RSRP threshold configured for SSB selection for CG-SDT.
[0439] C-RNTI includes the RNTI value IE. This field indicates the RNTI value for dynamic grant and dynamic allocation used during CG-SDT. The C-RNTI indicated in this field is valid for dynamic grant in the first cell's general uplink and the first cell's secondary uplink, and for dynamic allocation in the first cell's downlink.
[0440] CS-RNTI includes the RNTI value IE. This field indicates the RNTI value for the Type 1 set grant to be used during CG-SDT. The CS-RNTI displayed in this field is valid for the Type 1 set grant in the general uplink of the first cell and the auxiliary uplink of the first cell.
[0441] The RNTI value IE represents the wireless network temporary ID. It represents an integer between 0 (=0000 0000 0000 0000) and 65535 (=1111 1111 1111 1111).
[0442] If an SDT-Config without sdt-MAC-PHY-CG-Config is included in RRCRelease, the UE considers that RA-SDT is configured. The UE also considers that RA-SDT is applicable to a third cell. The third cell is the cell to which SIB1 containing SDT-ConfigCommonSIB is broadcast.
[0443] If an SDT-Config containing sdt-MAC-PHY-CG-Config is included in RRCRelease, the UE considers that CG-SDT is configured. The UE also considers that CG-SDT is applicable in the first cell and RA-SDT is applicable in the third cell. The first cell is the PCell that received the RRCRelease message containing SDT-Config.
[0444] The sdt-ConfigCommon field includes the sdt-RSRP-Threshold field, the sdt-DataVolumeThreshold field, and the sdt-CQI-Threshold field.
[0445] sdt-RSRP-Threshold represents the RSRP threshold for determining whether the UE will perform SDT1.
[0446] sdt-DataVolumeThreshold represents the data volume threshold used to determine whether SDT1 can be initiated.
[0447] sdt-CQI-Threshold represents the downlink channel quality threshold used to determine whether a UE can initiate SDT2.
[0448] Or sdt-CQI-Threshold is included in the first paging message. In this case, the corresponding entry2 of the second list includes the first information, the second information, and sdt-CQI-Threshold.
[0449] The operation of the terminal and base station is explained below.
[0451] Operations related to terminal performance reporting
[0452] The terminal transmits UECapabilityInformation to the base station. UECapabilityInformation includes zero or one ra-SDT (Type 2 SDT) field and zero or more cg-SDT (Type 1 SDT) fields. The ra-SDT field indicates whether the terminal supports data transmission over a radio bearer allowed in the RRC_INACTIVE state through a random access procedure. Each of the zero or one or more cg-SDT fields indicates whether the terminal supports data transmission over a radio bearer allowed in the RRC_INACTIVE state through a Grant Type 1 set in the relevant frequency band.
[0453] The terminal sends a NAS message to the AMF. The NAS message includes UE NETWORK CAPABILITY IE. UE NETWORK CAPABILITY IE includes multiple octets. A specific bit of a specific octet indicates whether the UE supports RRC CONNECTION RESUME3.
[0454] The terminal transmits UECapabilityInformation to the base station. UECapabilityInformation includes Type 1 SDT support information (RA-SDT support information) and Type 2 SDT support information (CG-SDT support information).
[0455] The terminal sends a NAS message to the AMF. The NAS message includes a bit indicating whether RRC CONNECTION RESUME3 is supported.
[0457] If the terminal supports TYPE2 RRC CONNECTION RESUME3, TYPE2 RRC CONNECTION RESUME2, and TYPE1 RRC CONNECTION RESUME2, it includes ra-SDT support information and cg-SDT support information in UECapabilityInformation and sets the bit of the configuration NAS message to the first value.
[0459] If the terminal supports TYPE2 RRC CONNECTION RESUME3 and TYPE2 RRC CONNECTION RESUME2 but does not support TYPE1 RRC CONNECTION RESUME2, the UECapabilityInformation includes ra-SDT support information and does not include cg-SDT support information, and the above bit of the NAS message is set to the first value.
[0461] If the terminal supports TYPE1 RRC CONNECTION RESUME2 and TYPE2 RRC CONNECTION RESUME2 but does not support TYPE2 RRC CONNECTION RESUME3, the UECapabilityInformation includes ra-SDT support information and cg-SDT support information, and the above bit of the NAS message is set to the second value.
[0463] If TYPE2 RRC CONNECTION RESUME2 is supported at the terminal but TYPE2 RRC CONNECTION RESUME3 and TYPE1 RRC CONNECTION RESUME2 are not supported at the terminal, it includes information on ra-SDT support and does not include information on cg-SDT support. In UECapabilityInformation, the above bit of the NAS message is set to the second value.
[0465] Operation upon receiving RRCRelease
[0466] The terminal receives RRCRelease from the base station. The RRCRelease suspends the RRC connection and includes SuspendConfig. SuspendConfig includes a first UE identifier, a second UE identifier, t380, and sdt-Config. sdt-Config includes sdt-DRB-List, sdt-SRB2-Indication, and sdt-MAC-PHY-CG-Config, and
[0467] sdt-MAC-PHY-CG-Config includes cg-SDT-ConfigInitialBWP-NUL, cg-SDT-ConfigInitialBWP-SUL, cg-SDT-ConfigInitialBWP-DL, cg-SDT-TimeAlignmentTimer, cg-SDT-RSRP-ThresholdSSB, and cg-SDT-CS-RNTI.
[0469] In response to the reception of RRCRelease, the second set of operations (UE operations upon reception of RRCRelease) is performed.
[0470] The second set of operations includes releasing zero or more first set grants (the zero or more first set grants are set grants configured and not cleared when RRCRelease is received), determining zero or more DRBs configured for SDT based on sdt-DRB-List, determining whether SRB2 is configured for SDT based on sdt-SRB2-Indication, setting zero or more second set grants (the zero or more second set grants are indicated in configureGrantConfigToAddModList of cg-SDT-ConfigInitialBWP-NUL and configureGrantConfigToAddModList of cg-SDT-ConfigInitialBWP-SUL), and starting cg-SDT-TimeAlignmentTimer and starting T380. The T380 timer value is set to t380.
[0472] Action upon receiving Paging
[0473] The terminal receives a paging message from the paging channel of the second cell. The paging message includes a first list and a second list, wherein the first list includes one or more entry1s and the second list includes one or more entry2s.
[0474] Each of one or more entry1 includes a first UE identifier or a third UE identifier.
[0475] Each of one or more entry2s is either a Type 1 entry2 or a Type 2 entry2. A Type 1 entry2 consists of first information indicating that it is an entry2. A Type 2 entry2 consists of first information and second information. The second information indicates that the paging is for RRC CONNECTION RESUME3.
[0476] The number of entry2 in the second list is the same as the number of entry1 in the first list. Entry2 in the second list and entry1 in the first list are listed in the same order.
[0478] If the first UE identifier included in entry1 of the first list matches the first UE identifier stored in the terminal and the second information is included in the corresponding entry2 of the second list, the terminal sets resumeCause to the first value and starts RRC CONNECTION RESUME3.
[0480] If the first UE identifier included in entry1 of the first list matches the first UE identifier stored in the terminal and the second information is not included in the corresponding entry2 of the second list, the terminal sets rersumeCause to the second value and starts RRC CONNECTION RESUME1.
[0482] If the third UE identifier included in entry1 of the first list matches the UE ID assigned by the upper layer, the terminal performs the first set of actions (UE actions when going to RRC_IDLE). The first set of actions includes clearing resources configured for CG-SDT (resources configured as specified in configureGrantConfigToAddModList within RRCRelease) and stopping T380. The UE ID assigned by the upper layer is specified in a specific NAS message, such as ATTACH ACCEPT. The UE ID assigned by the upper layer is 5G-S-TMSI. NG-5G-S-TMSI is a temporary terminal identifier provided by 5GC that uniquely identifies the UE within the tracking area.
[0486] If none of the entries in the first list match the terminal's stored first UE identifier or the UE ID assigned by the upper layer, the terminal continues to monitor the paging channel.
[0488] Actions related to the start of the Resume procedure
[0489] The terminal resumes the interrupted RRC CONNECTION in RRC CONNECTION RESUME1.
[0490] The terminal performs data and / or signaling transmission while maintaining RRC_INACTIVE in RRC CONNECTION RESUME2 and RRC CONNECTION RESUME3. RRC CONNECTION RESUME2 is a procedure initiated by the mobile. RRC CONNECTION RESUME3 is a procedure terminated by the mobile.
[0491] RRC CONNECTION RESUME1 is initiated by the reception of the second paging message or by the terminal.
[0492] RRC CONNECTION RESUME2 is initiated by the terminal.
[0493] R RC CONNECTION RESUME3 is initiated by the reception of the first paging message.
[0495] The terminal initiates RRC CONNECTION RESUME1 when one or more conditions of CONDITION SET1 are met. CONDITION SET1 includes receiving a second paging message, T380 expiration, and RNA change.
[0496] The second paging message includes a first UE identifier that matches the first UE identifier stored in the first list, and the corresponding entry2 in the second list does not include the second information.
[0497] The terminal sets the resumeCause in the first CCCH SDU to one of the first predefined values, and the first predefined values include mt-Access, mo-Signaling, and mo-Data.
[0499] The terminal starts RRC CONNECTION RESUME2 when all conditions of CONDITION SET2 are met. CONDITION SET2 includes UPPER LAYER CONDITION SET1 and LOWER LAYER CONDITION SET.
[0500] UPPER LAYER CONDITION SET1 includes a request from the upper layer for the resumption of the RRC connection and sdt-Config is configured, sdt-ConfigCommon is included in SIB1, and all pending data of the uplink is mapped to the radio bearer configured for SDT.
[0501] The LOWER LAYER CONDITION SET includes the data volume of pending uplink data across all RBs configured for SDT being less than or equal to sdt-DataVolumeThreshold and the RSRP of the downlink path loss reference being higher than sdt-RSRP-Threshold.
[0502] The terminal sets the resumeCause in the first CCCH SDU to one of the first predefined values, and the first predefined values include mt-Access, mo-Signaling, and mo-Data.
[0504] The terminal initiates RRC CONNECTION RESUME3 when all conditions of CONDITION SET3 are met. CONDITION SET3 includes UPPER LAYER CONDITION SET2, and
[0505] UPPER LAYER CONDITION SET2 includes the reception of the first paging message, the configuration of sdt-Config, the inclusion of sdt-ConfigCommon in SIB1, and no pending data on the uplink except for the CCCH SDU.
[0506] The first paging message includes a first entry1 of the first list and a first entry2 of the second list. The first entry1 includes a first UE identifier that matches the stored first UE identifier. The first entry2 includes second information. The first entry2 corresponds to the first entry1. The order of the first entry1 of the first list is the same as the order of the first entry2 of the second list.
[0507] The terminal sets resumeCause in the first CCCH SDU to a second predefined value. The second predefined value represents RRC CONNECTION RESUME3.
[0509] The terminal starts RRC CONNECTION RESUME2 when the first UPPER LAYER CONDITION SET and LOWER LAYER CONDITION SET are satisfied.
[0510] The terminal starts RRC CONNECTION RESUME3 when the second UPPER LAYER CONDITION SET is satisfied.
[0511] When RRC CONNECTION RESUME2 is triggered, the terminal starts RRC CONNECTION RESUME1 if the first UPPER LAYER CONDITION SET is not satisfied or the LOWER LAYER CONDITION SET is not satisfied.
[0512] When RRC CONNECTION RESUME3 is triggered, the terminal starts RRC CONNECTION RESUME1 if the second UPPER LAYER CONDITION SET is not satisfied.
[0513] The UPPER LAYER CONDIITONS SET is a set of conditions checked in the RRC layer.
[0514] The LOWER LAYE CONDITION SET is a set of conditions checked at the MAC layer.
[0516] When the RRC CONNECTION RESUME starts, the terminal transmits the first MAC PDU to the base station.
[0517] The first MAC PDU includes a first MAC SDU and a second MAC SDU when the RRC CONNECTION RESUME is RRC CONNECTION RESUME2. The first MAC SDU includes a first CCCH SDU, and the second MAC SDU includes an RLC PDU from a logical channel associated with a wireless bearer configured for SDT.
[0519] The first MAC PDU includes only the first MAC SDU when the RRC CONNECTION RESUME is RRC CONNECTION RESUME1. The first MAC SDU includes the first CCCH SDU.
[0521] The first MAC PDU includes only the third MAC SDU when the RRC CONNECTION RESUME is RRC CONNECTION RESUME3. The third MAC SDU includes the second CCCH SDU.
[0523] The first CCCH SDU (RRCResumeRequest) includes a resumeCause field. The resumeCause field represents a value selected from a predefined first value. The predefined first values include Emergency, mt-Access, and mo-Data.
[0525] The second CCCH SDU (RRCResumeRequest2) includes a resumeCause field. The resumeCause field represents a predefined second value. The predefined second value represents an RRC CONNECTION RESUME3, and the predefined second value is not equal to any value of the predefined first value.
[0527] The CCCH SDU includes a first UE identifier, and the second CCCH SDU includes a second UE identifier.
[0528] CCCH SDU includes fields associated with downlink channel quality derived based on specific SS / PBCH blocks.
[0530] Selection of a set of random access resources
[0531] The terminal initiates a random access procedure for the RRC CONNECTION RESUME.
[0533] Terminal selects a first set of random access resources for this random access procedure if one or more features are applicable to this random access procedure, and if none of the sets of random access resources are available for any feature of the one or more features applicable to the current random access procedure.
[0534] The set of first random access resources is not associated with any of the one or more features of this random access procedure.
[0536] If one or more features are applicable to this random access procedure and a set of random access resources is available for all of the one or more features applicable to the current random access procedure, the terminal selects the set of random access resources for this random access procedure.
[0538] If no feature is applied to this random access procedure, the terminal selects a set of second random access resources for this random access procedure.
[0539] The set of second random access resources is not associated with any feature.
[0541] RedCap features are applicable to the current Random Access procedure when the terminal is a RedCap UE. RedCap UEs have reduced performance compared to non-RedCap UEs to lower complexity.
[0543] The MSG3 repeat feature can be applied to the current random access procedure if the BWP for the random access procedure consists of a set of random access resources with MSG3 repeat marks.
[0545] The RESUME2 feature can be applied to the current random access procedure if a random access procedure has been initiated for Type 2 RRC CONNECTION RESUME2.
[0547] The set of random access resources consists of a set of random access preambles and a set of PRACH opportunities. The set of random access preambles is indicated in the associated parameter set 2. The set of PRACH opportunities is indicated in the associated parameter set 1.
[0548] A set of random access resources is associated with a set of random access parameters. Parameter set 1 is associated with one or more sets of random access resources. One parameter set 2 is connected to one set of random access resources.
[0550] Parameter set 1 is included in the first part of the first RACH-ConfigCommon.
[0551] The first RACH-ConfigCommon includes one or more FeatureCombinationPreambles IEs. One of the one or more FeatureCombinationPreambles IEs in the first RACH-ConfigCommon is associated with a set of random access resources associated with the parameter set 1.
[0552] Parameter set 2 is included in one of the one or more FeatureCombinationPreambles IEs within the first RACH-ConfigCommon. The one or more FeatureCombinationPreambles IEs are included in the second part of the first RACH-ConfigCommon. Parameter set 2 is included in the second part of the first RACH-ConfigCommon.
[0553] In the first RACH-ConfigCommon, the first part is located before the second part.
[0554] The above first part is a non-extended part of the above first RACH-ConfigCommon.
[0555] The above second part is an extension of the above first RACH-ConfigCommon.
[0556] Select SSB
[0557] The terminal selects an SSB based on rsrp-ThresholdSSB of parameter set 2.
[0559] Preamble group selection
[0560] The terminal selects a preamble group based on ra-SizeGroupA, messagePowerOffsetGroupB, and numberOfRA-PreamblesGroupA.
[0561] ra-SizeGroupA, messagePowerOffsetGroupB, and numberOfRA-PreamblesGroupA are included in parameter set2.
[0563] The terminal selects random access preamble group B if deltaPreamble does not exist in parameter set 2, the potential Msg 3 size is greater than ra-SizeGroupA, and the path loss is less than PCMAX - preambleReceivedTargetPower - msg3 - DeltaPreamble - messagePowerOffsetGroupB.
[0564] The terminal selects random access preamble group B if deltaPreamble exists in parameter set 2, the potential Msg 3 size is greater than ra-SizeGroupA, and the path loss is less than PCMAX - preambleReceivedTargetPower - deltaPreamble - messagePowerOffsetGroupB.
[0565] msg3-DeltaPreamble is included in the PUSCH-ConfigCommon IE of the initial uplink BWP of the selected uplink.
[0566] preambleReceivedTargetPower is included in parameter set1.
[0567] deltaPreamble is included in parameter set 2.
[0568] The terminal selects random access preamble group B if there is no parameter set 2 (or FeatureCombinationPreambles IE) associated with the set of random access resources selected for this random access procedure, the potential Msg 3 size is greater than ra-Msg3szeGroupA, and the path loss is less than PCMAX-preambleReceivedTargetPower-msg3-DeltaPreamble-messagePowerOffsetGroupB.
[0569] ra-Msg3szeGroupA is included in parameter set 1.
[0571] The terminal selects a preamble based on the selected SSB and the selected preamble group.
[0572] The terminal transmits the selected preamble based on preambleReceivedTargetPower and DELTA_PREAMBLE.
[0573] DELTA_PREAMBLE is determined based on prach-ConfigurationIndex. prach-ConfigurationIndex is included in parameter set 1.
[0574] preambleReceivedTargetPower is included in parameter set1.
[0576] The terminal monitors the PDCCH based on ra-ResponseWindow to receive RAR.
[0577] ra-ResponseWindow is included in parameter set1.
[0579] The terminal determines the PUSCH transmission power for Msg 3 based on the first offset, path loss, and the number of PRBs.
[0580] The first offset is the sum of preambleReceivedTargetPower and msg3-DeltaPreamble when deltaPreamble is not included in the parameter set 2 of the current random access procedure.
[0581] The first offset is the sum of preambleReceivedTargetPower and deltaPreamble when deltaPreamble is included in the parameter set 2 of the current random access procedure.
[0583] Parameter Set 1 and Parameter Set 2
[0584] When the current random access procedure is initiated for RRC CONNECTION RESUME2, parameter set 1 is associated with the set of first random access resources. When the current random access procedure is initiated for RRC CONNECTION RESUME3, parameter set 1 is associated with the set of second random access resources.
[0585] When the current random access procedure is initiated for RRC CONNECTION RESUME2, parameter set 2 is associated with the set of first random access resources. When the current random access procedure is initiated for RRC CONNECTION RESUME3, parameter set 2 is associated with the set of second random access resources.
[0586] The RESUME2 feature is applied to the first set of random access resources. The FeatureCombination IE of the FeatureCombinationPreamble associated with the first set of random access resources includes the RESUME2 field set to true.
[0587] The RESUME2 feature does not apply to the set of second random access resources. The FeatureCombination IE of the FeatureCombinationPreamble IE associated with the set of second random access resources does not include the RESUME2 field.
[0589] The terminal generates message 3.
[0590] If the current random access procedure is initiated for RRC CONNECTION RESUME1, message 3 contains the first MAC SDU.
[0591] Message 3 includes the first MAC SDU and the second MAC SDU when the current random access procedure is initiated for RRC CONNECTION RESUME2.
[0592] If the current random access procedure is initiated for RRC CONNECTION RESUME3, Message 3 contains a third MAC SDU. In this case, Message 3 contains information related to the downlink channel quality.
[0593] The first MAC SDU includes an RRCResumeRequest, the second MAC SDU includes an RLC PDU generated from a specific data radio bearer, and the third MAC SDU includes an RRCResumeRequest2.
[0594] The 1st MAC SDU and the 3rd MAC SDU are not encrypted. The 2nd MAC SDU is encrypted based on a stored security key.
[0596] When sdt-P0-PUSCH exists in the first ConfiguredGrantConfig and the current random access procedure is started for Type 1 RRC CONNECTION RESUME2 (or Type 1 RRC CONNECTION RESUME3), the terminal determines the PUSCH transmission power based on p0-NominalWithoutGrant and sdt-P0-PUSCH in the first ConfiguredGrantConfig.
[0597] The above p0-NominalWithoutGrant is included in the RRCRelease message within the sdt-MAC-PHY-CG IE within the PUSCH-Config IE.
[0598] The first ConfiguredGrantConfig IE is selected from one or more ConfiguredGrantConfig IEs within the sdt-MAC-PHY-CG IE in the RRCRelease message.
[0599] If deltaPreamble is not included in parameter set 1 of the current random access procedure and the current random access procedure was initiated for Type 2 RRC CONNECTION RESUME3, the terminal determines the PUSCH transmission power based on PreambereceivedTargetPower and MSG3-DeltapReamble.
[0600] If deltaPreamble is included in parameter set 1 of the current random access procedure and the current random access procedure was initiated for Type 2 RRC CONNECTION RESUME 3, the terminal determines the PUSCH transmission power based on PreambereceivedTargetPower and deltaPreamble.
[0602] The terminal monitors the PDCCH with the first RNT when RRC CONNECTION RESUME1 is in progress.
[0603] The terminal monitors the PDCCH with the second RNTI when Type 1 RRC CONNECTION RESUME2 is in progress.
[0604] The terminal monitors the PDCCH with the third RNTI when Type 2 RRC CONNECTION RESUME3 is in progress.
[0605] The first RNTI is a temporary RNTI that is instructed to the terminal during a random access procedure.
[0606] The second RNTI is instructed to the terminal in RRCRelease.
[0607] The third RNTI is instructed to the terminal in a valid RAR.
[0609] In step 3a-05, the terminal receives RRCRelease from the base station. The RRCRelease includes SuspendConfig.
[0610] In step 3a-10, the terminal enters the RRC_INACTIVE state in response to receiving the RRCRelease message and performs cell selection.
[0611] In step 3a-15, the terminal receives SIB1 from a selected cell. The SIB1 includes one or more RACH-ConfigCommons. Each of the one or more RACH-ConfigCommons includes zero or one or more FeatureCombinationPreambles IEs. Each of the zero or one or more FeatureCombinationPreambles IEs includes one FeatureCombination. The FeatureCombination may include a field corresponding to a first feature.
[0612] In step 3a-20, the terminal initiates a random access procedure in the cell.
[0613] In step 3a-25, the terminal selects a set of random access resources for the random access procedure.
[0615] If the above random access procedure is initiated for RRC CONNECTION RESUME2, a set of random access resources corresponding to FeatureCombinationPreambles IE, including FeatureCombination IE where a field corresponding to the first feature exists, is selected. If the above random access procedure is initiated for RRC CONNECTION RESUME3, a set of random access resources corresponding to FeatureCombinationPreambles IE, including FeatureCombination IE where a field corresponding to the first feature does not exist, is selected.
[0624] .
[0625] FIG. 4a is a block diagram illustrating the internal structure of a terminal to which the present invention is applied.
[0626] Referring to the drawing above, the terminal includes a control unit (4a-01), a storage unit (4a-02), a transceiver (4a-03), a main processor (4a-04), and an input / output unit (4a-05).
[0627] The control unit (4a-01) controls the overall operations of the UE related to mobile communication. For example, the control unit (4a-01) transmits and receives signals through the transceiver (4a-03). Additionally, the control unit (4a-01) writes and reads data to and from the storage unit (4a-02). To this end, the control unit (4a-01) may include at least one processor. For example, the control unit (4a-01) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications. The control unit (4a-01) controls the storage unit and the transceiver so that the terminal operations of FIGS. 2a, 2b, and 3a are performed. The transceiver is also referred to as a transceiver.
[0628] The storage unit (4a-02) stores data such as basic programs, application programs, and setting information for the operation of the terminal. The storage unit (4a-02) provides the stored data in response to a request from the control unit (4a-01).
[0629] The above transver (4a-03) includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit upconverts the baseband signal provided by the baseband processing unit into an RF band signal, transmits it through the antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog converter), an ADC (analog to digital converter), etc. The RF processing unit can perform MIMO and can receive multiple layers when performing MIMO operation. The baseband processing unit performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit generates complex symbols by encoding and modulating the transmitted bit sequence. In addition, upon receiving data, the baseband processing unit recovers the received bit sequence through demodulation and decoding of the baseband signal provided by the RF processing unit. The transceiver is also referred to as a transceiver.
[0630] The main processor (4a-04) controls overall operations excluding mobile communication-related operations. The main processor (4a-04) processes user input transmitted by the input / output unit (4a-05), stores necessary data in the storage unit (4a-02), controls the control unit (4a-01) to perform mobile communication-related operations, and transmits output information to the input / output unit (4a-05).
[0631] The above input / output unit (4a-05) is composed of a device that accepts user input, such as a microphone or a screen, and a device that provides information to the user, and performs input and output of user data under the control of the main processor.
[0632] FIG. 4b is a block diagram showing the configuration of a base station according to the present invention.
[0633] As illustrated in the drawing above, the base station is configured to include a control unit (4b-01), a storage unit (4b-02), a transceiver (4b-03), and a backhaul interface unit (4b-04).
[0634] The control unit (4b-01) controls the overall operations of the base station. For example, the control unit (4b-01) transmits and receives signals through the transceiver (4b-03) or through the backhaul interface unit (4b-04). Additionally, the control unit (4b-01) writes and reads data to and from the storage unit (4b-02). To this end, the control unit (4b-01) may include at least one processor. The control unit (4b-01) controls the transceiver, storage unit, and backhaul interface unit so that base station operations illustrated in FIG. 2a, etc. are performed.
[0635] The storage unit (4b-02) stores data such as basic programs, application programs, and configuration information for the operation of the main station. In particular, the storage unit (4b-02) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (4b-02) can store information that serves as a criterion for determining whether to provide or disconnect multiple connections to the terminals. Furthermore, the storage unit (4b-02) provides the stored data in response to a request from the control unit (4b-01).
[0636] The transceiver (4b-03) includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit upconverts a baseband signal provided by the baseband processing unit into an RF band signal and transmits it through the antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. The RF processing unit may perform down-MIMO operations by transmitting one or more layers. The baseband processing unit performs a conversion function between a baseband signal and a bit sequence according to physical layer specifications. For example, when transmitting data, the baseband processing unit generates complex symbols by encoding and modulating the transmitted bit sequence. In addition, upon receiving data, the baseband processing unit recovers the received bit sequence through demodulation and decoding of the baseband signal provided by the RF processing unit. The transceiver is also referred to as a transceiver.
[0637] The above backhaul interface unit (4b-04) provides an interface for performing communication with other nodes within the network. That is, the above backhaul communication unit (4b-04) converts a bit sequence transmitted from the main base station to another node, e.g., an auxiliary base station, a core network, etc., into a physical signal, and converts a physical signal received from the other node into a bit sequence.< / suspendconfig>
Claims
Claim 1 A method performed by a wireless device, wherein the method comprises: receiving a first RRC message from a base station in a first cell, wherein the first RRC message comprises: a first UE identifier for paging reception and CCCH transmission; a timer value for t380 controlling periodic RRC connection resumption; and first configuration information for SDT; receiving system information (SI) from a base station in a second cell, wherein the SI comprises one or more common RACH configuration information, wherein the common RACH configuration information comprises: a first set of random access parameters; and one or more second sets of random access parameters; and one or more sets of random access resources; initiating a small data transmission (SDT) procedure in the second cell; and selecting a set of random access resources. The method comprises the step of performing a random access procedure based on a selected set of random access resources and random access parameters of a first set and random access parameters of a first and second set, wherein the set of random access resources is selected based on a first feature set when the SDT procedure is a first SDT procedure, and the set of random access resources is selected based on a second feature set when the SDT procedure is a second SDT procedure, wherein the first SDT procedure is initiated in at least the following cases: all data pending on the uplink is mapped to a radio bearer configured for the SDT, and the amount of data of the uplink data pending on all radio bearers configured for the SDT is less than or equal to a data amount threshold, and the system information of the second cell includes second configuration information for the SDT, and the second SDT procedure is initiated in at least the following cases: a paging message is received in the second cell, and the paging message includes SDT-related information, and the system information of the second cell includes second configuration information for the SDT. Claim 2 A method according to claim 1, wherein the first set of features includes at least small data transmission, and the second set of features does not include small data transmission. Claim 3 A method according to claim 1, wherein the first set of features includes small data transmission, and the second set of features does not include any features. Claim 4 A method according to claim 1, wherein the first set of random access parameters comprises: rsrp-ThresholdSSB; preambleReceivedTargetPower; and PRACH configuration index; and the second set of random access parameters comprises: deltaPreamble; rsrp-ThresholdSSB; and numberOfRA-PreamblesGroupA. Claim 5 A method according to claim 1, wherein the random access resource set is associated with a feature set, the random access parameter of the first set is associated with one or more random access resource sets, and the random access parameter of the second set is associated with the random access resource set. Claim 6 The method of claim 1, wherein the step of selecting a random access resource set comprises: selecting a first random access resource set if applicable to all features, and selecting a second random access resource set to which no features are assigned if applicable to any features. Claim 7 A method according to claim 1, wherein the step of performing a random access procedure comprises: selecting a synchronization signal block (SSB) based on rsrp-ThresholdSSB specified in a first and second set of random access parameters, and selecting a preamble group based on numberOfRA-PreamblesGroupA of the first and second sets and preambleReceivedTargetPower of the first first set. Claim 8 A method according to claim 7, wherein the step of performing the random access procedure further comprises: transmitting a preamble according to the PRACH configuration index of the first set and monitoring a physical downlink control channel according to the ra-ResponseWindow of the first set. Claim 9 A method according to claim 1, wherein the random access parameter of the first and second sets is a random access parameter of the second set associated with a selected random access resource set, and the random access parameter of the first first set is a random access parameter of the first set associated with the random access parameter of the first and second sets. Claim 10 A method according to claim 1, wherein the first configuration information for the SDT comprises: a list of data radio bearer (DRB) identifiers configured for the SDT; and a signaling radio bearer 2 (SRB2) related indicator indicating that an SRB2 is configured for the SDT. Claim 11 A method according to claim 1, wherein the second configuration information for the SDT comprises: a downlink threshold for the first SDT procedure; a downlink threshold for the second SDT procedure; and a data amount threshold for the first SDT procedure. Claim 12 In a wireless communication system, a wireless device comprises: a transceiver configured to transmit and receive signals; and a control unit, wherein the control unit receives a first RRC message from a base station in a first cell, the first RRC message comprises: a first UE identifier for paging reception and CCCH transmission; a timer value for t380 controlling periodic RRC connection resumption; and first configuration information for an SDT; receives system information (SI) from a base station in a second cell, the SI comprises one or more common RACH configuration information, the common RACH configuration information comprises: a first set of random access parameters; and one or more second sets of random access parameters. A wireless device characterized by: one or more sets of random access resources; initiating a small data transmission (SDT) procedure in a second cell, selecting a set of random access resources, and performing a random access procedure based on the selected set of random access resources and random access parameters of a first set and random access parameters of a first set, wherein the set of random access resources is selected based on a first set of features when the SDT procedure is a first SDT procedure, and the set of random access resources is selected based on a second set of features when the SDT procedure is a second SDT procedure, wherein the first SDT procedure is initiated in at least the following cases: all data pending on the uplink is mapped to a radio bearer configured for the SDT, and the amount of data of the uplink data pending on all radio bearers configured for the SDT is below a data amount threshold, and the system information of the second cell includes second configuration information for the SDT, and the second SDT procedure is initiated in at least the following cases: a paging message is received in the second cell, and the paging message includes SDT-related information, and the system information of the second cell If it includes second configuration information for SDT.
Citation Information
Patent Citations
Small data transmission (SDT)
WO2021163394A1
Release message in small data transmission procedure
WO2022066892A1
Downlink data of small data transmission procedure
WO2022087115A1
