KR20230158238A - Method and Apparatus for uplink transmission in RRC_INACTIVE state - Google Patents

Abstract

According to the present disclosure, a method and apparatus for RRC_INACTIVE state uplink transmission in a wireless mobile communication system are provided.

Description

Method and apparatus for uplink transmission in RRC_INACTIVE state in a wireless mobile communication system {Method and Apparatus for uplink transmission in RRC_INACTIVE state}

This disclosure relates to a method and apparatus for uplink transmission in RRC_INACTIVE state in a wireless mobile communication system.

To meet the increasing demand for wireless data traffic following the commercialization of the 4G communication system, the 5G communication system was developed. To achieve high data rates, 5G communication systems have introduced ultra-high frequency (mmWave) bands (such as the 60-gigabit (60GHz) band). In order to alleviate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, the 5G communication system uses beamforming, massive array multiple input/output (massive MIMO), and full dimension multiple input/output (FD-MIMO). ), array antenna, analog beam-forming, and large scale antenna technologies are used. In the 5G communication system, scalability is increased by dividing the base station into a central unit and a distributed unit. Additionally, the 5G communication system aims to support extremely high data rates and extremely low transmission delays in order to support a variety of services.

As a way to achieve low transmission delay, uplink transmission from a terminal in an inactive state is required.

The present disclosure seeks to provide a method and device for uplink transmission in RRC_INACTIVE state in a wireless mobile communication system.

.

The disclosed embodiment provides a method and apparatus for RRC connected state uplink transmission and RRC_INACTIVE state uplink transmission in a wireless mobile communication system.

FIG. 1A is a diagram illustrating the structure of a 5G system and NG-RAN according to an embodiment of the present disclosure.
FIG. 1B is a diagram illustrating a wireless protocol structure in an NR system according to an embodiment of the present disclosure.
FIG. 1C is a diagram illustrating transitions between RRC states according to an embodiment of the present disclosure.
Figure 1d is a diagram showing bandwidth portion adjustment and bandwidth portion.
Figure 1e is a diagram explaining the search interval and control resource set.
FIG. 2A is a diagram illustrating the operation of a terminal and a base station according to an embodiment of the present disclosure.
FIG. 3A is a flowchart for explaining the operation of a terminal according to an embodiment of the present disclosure.
Figure 4a is a block diagram showing the internal structure of a terminal to which the present invention is applied.
Figure 4b is a block diagram showing the internal structure of a base station to which the present invention is applied.

Hereinafter, embodiments of the present invention will be described in detail with the accompanying drawings. Additionally, when describing the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description will be omitted. The terms described below are defined in consideration of the functions in the present invention, and may vary depending on the intention or custom of the user or operator. Therefore, the definition should be made based on the contents throughout this specification.

Terms used in the following description to identify a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, and a term referring to various types of identification information. The following are examples for convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meaning may be used.

For convenience of description below, the present invention uses terms and names defined in the 3rd Generation Partnership Project (3GPP) standard, which is the latest standard among currently existing communication standards. However, the present invention is not limited by the above terms and names, and can be equally applied to systems complying with other standards.

Table 1 lists the abbreviations used in the present invention.

Acronym Full name Acronym Full name 5GC 5G Core Network RACH Random Access Channel ACK Acknowledgment RAN Radio Access Network A.M. 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 R.L.C. 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 C.A.G. Closed Access Group RRM Radio Resource Management CG Cell Group RSRP Reference Signal Received Power C-RNTIs Cell RNTI RSRQ Reference Signal Received Quality CSI Channel State Information RSSI Received Signal Strength Indicator DCI Downlink Control Information SCell Secondary Cell D.R.B. (user) Data Radio Bearer SCS Subcarrier Spacing DRX Discontinuous Reception SDAP Service Data Adaptation Protocol HARQ Hybrid Automatic Repeat Request SDU Service Data Unit I.E. 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 S.R.B. Signaling Radio Bearer NR NR Radio Access SRS Sounding Reference Signal PBR Prioritized Bit Rate SSB SS/PBCH block PCell Primary Cell SSS Secondary Synchronization 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 PLMN Public Land Mobile Network PRS Positioning Reference Signal PRACH Physical Random Access Channel CS-RNTI Configured Scheduling-RNTI PRB Physical Resource Block TAG Timing Advance Group P.S.S. Primary Synchronization 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

Table 2 defines terms frequently used in the present invention.

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 selection 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 signaling 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 identify an NR cell. It is comprised 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 C.E. 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 signaling 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. S.R.B. 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 fulfills the first bullet above.
- The cell selection criterion S is fulfilled (ie 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.

In the present invention, “trigger” or “is triggered” and “initiate” or “is initiated” may be used with the same meaning. In the present invention, “radio bearer for which the second resumption procedure is allowed”, “radio bearer for which the second resumption procedure is configured”, and “radio bearer for which the second resumption procedure is enabled” may all be used with the same meaning.

In the present invention, the second restart procedure may be used in the same sense as SDT (Small Data Transmission).

In the present invention, terminal and UE may be used with the same meaning. In the present invention, base station and NG-RAN node may be used with the same meaning.

FIG. 1A is a diagram illustrating the structures of a 5G system and NG-RAN according to an embodiment of the present disclosure.

The 5G system consists of NG-RAN (1a-01) and 5GC (1a-02). The NG-RAN node is one of the two below.

1: gNB providing NR user plane and control plane towards UE; or

2: ng-eNB providing E-UTRA user plane and control plane towards UE.

gNB (1a-05 to 1a-06) and ng-eNB (1a-03 to 1a-04) are interconnected through the Xn interface. The gNB and ng-eNB are connected to the Access and Mobility Management Function (AMF) (1a-07) and the User Plane Function (UPF) (1a-08) through the NG interface. AMF (1a-07) and UPF (1a-08) can be configured as one physical node or as separate physical nodes.

gNB (1a-05 to 1a-06) and ng-eNB (1a-03 to 1a-04) host the functions listed below.

Radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in uplink, downlink and sidelink (scheduling), IP and Ethernet header compression, uplink data decompression and encryption of user data streams, Selection of AMF if the AMF cannot be selected with the information provided, routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (from AMF or O&M);

Configuration of measurements and measurement reporting for mobility and scheduling, session management, QoS flow management and mapping for data radio bearers, RRC_INACTIVE support, radio access network sharing;

Tight interaction between NR and E-UTRA, support for network slicing.

AMF (1a-07) hosts functions such as NAS signaling, NAS signal security, AS security control, S-GW selection, authentication, mobility management, and location management.

UPF (1a-08) hosts functions such as packet routing and forwarding, transport level packet marking on the uplink and downlink, QoS management, and mobility anchoring for mobility.

Figure 1b- is a diagram showing the wireless protocol structure of the 5G system.

The user plane protocol stack is SDAP (1b-01 to 1b-02), PDCP (1b-03 to 1b-04), RLC (1b-05 to 1b-06), MAC (1b-07 to 1b-08), PHY It consists of (1b-09 to 1b-10). The control name protocol stack consists of NAS (1b-11 to 1b-12), RRC (1b-13 to 1b-14), PDCP, RLC, MAC, and PHY.

Each protocol sublayer performs functions related to the operations listed in Table 3.

Sublayer Functions NAS Authentication, mobility management, security control, etc. RRC System information, paging, RRC connection management, security functions, signaling radio bearer and data radio bearer management, mobility management, QoS management, detection and recovery from radio link failure, NAS message transmission, etc. SDAP Mapping between QoS flows and data radio bearers, QoS flow ID (QFI) marking of DL and UL packets. PDCP Data transmission, header compression and restoration, encryption and decryption, integrity protection and integrity verification, redundant transmission, ordering and ordered delivery, etc. R.L.C. Transmission of upper layer PDU, error correction through ARQ, segmentation and re-division of RLC SDU, reassembly of SDU, re-establishment of RLC, etc. MAC Mapping between logical channels and transport channels, multiplexing/demultiplexing MAC SDUs belonging to one or another logical channel in the transport block (TB) delivered at the physical layer, information reporting schedule, priority processing between UEs, priority between single UE logical channels Ranking processing, etc. PHY Channel coding, physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

The terminal supports three RRC states. Table 4 lists the characteristics of each state.

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. 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.

Figure 1c is a diagram showing RRC state transition.

Between RRC_CONNECTED (1c-11) and RRC_INACTIVE (1c-13), a state transition occurs through the exchange of a Resume message and a Release message containing a Suspend IE.

Between RRC_ CONNECTED (1c-11) and RRC_IDLE (1c-15), state transition occurs through RRC connection establishment and RRC connection release.

A state transition from RRC_INACTIVE (1c-13) to RRC_IDLE (1c-15) occurs through RRC disconnection.

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 change between base stations. If the terminal has enough data to transmit, these additional procedures can be fully justified, but if not, network efficiency may be reduced due to excessive overhead.

The present invention introduces a new resume procedure that allows data transmission and reception without transitioning to RRC_CONNECTED. Hereinafter, the resumption procedure aimed at transitioning the terminal in the RRC_INACTIVE state to the RRC_CONNECTED state is referred to as the first resumption procedure, and the procedure in which the terminal in the RRC_INACTIVE state transmits and receives data while maintaining the RRC_INACTIVE state is referred to as the second resumption procedure. Through the first resume procedure, the terminal can resume the suspended RRC connection, and through the second resume procedure, the terminal can resume data transmission and reception. The terminal may switch to the first resume procedure while performing the second resume procedure.

The second resumption process may proceed through a random access process or through a configured grant. These are called RA-SDT and CG-SDT, respectively.

RRC_INACTIVE UE generally does not transmit uplink signals such as SRS and does not receive downlink signals such as PDCCH.

FIG. 1D is a diagram illustrating an example of a bandwidth part.

Bandwidth adaptation (BA) allows the UE's receive and transmit bandwidth to be adjusted so that it is not necessarily as large as the cell's bandwidth. It can also be commanded to change in width (e.g., scale back during periods of low activity to save power) or move its location in the frequency domain (e.g. to increase scheduling flexibility). Subcarrier spacing may also be changed (e.g. to allow different services). A subset of a cell's total cell bandwidth is called BWP(s). BA is achieved by configuring multiple BWPs for the UE and telling the UE which of the configured BWPs is active. In Figure 1d, a scenario in which three different BWPs are configured is shown below.

1: BWP1 (1d-11 to 1d-19) with a width of 40 MHz and a subcarrier spacing of 15 kHz

2: BWP2 (1d-13 to 1d-17) with a width of 10MHz and a subcarrier spacing of 15kHz

3: BWP3 (1d-15) with subcarrier spacing of 20 MHz wide and 60 kHz

Figure 1e is a diagram illustrating an example of a search interval and control resource set.

Multiple SSs can be set in one BWP. The terminal monitors PDCCH candidates according to the SS settings of the currently activated BWP. One SS consists of an SS identifier, a CORESET identifier indicating the associated CORESET, the period and offset of the slot to be monitored, the slot unit duration, the symbol to be monitored within the slot, and the SS type. The information may be set explicitly and individually, or may be set as a predetermined index related to predetermined values.

One CORESET consists of a CORESET identifier, frequency domain resource information, symbol unit duration, and TCI status information.

Basically, CORESET can be understood as providing frequency domain information to be monitored by the terminal, and SS provides time domain information to be monitored by the terminal.

CORESET#0 and SS#0 can be set in IBWP. One CORESET and multiple SS can be additionally set in IBWP. When the terminal receives MIB (1e-01), it recognizes CORESET#0 (1e-02) and SS#0 (1e-03) for receiving SIB1 using predetermined information included in the MIB. The terminal receives SIB1 (1e-05) through CORESET#0 (1e-02) and SS#0 (1e-03). SIB1 contains information for setting CORESET#0 (1e-06) and SS#0 (1e-07) and information for setting another CORESET, such as CORESET#n (1e-11) and SS#m (1e-13). may be included. The terminal uses the CORESETs and SSs set in SIB1 to receive necessary information from the base station before the terminal enters the RRC connection state, such as receiving SIB2, receiving paging, and receiving a random access response message. CORESET#0 (1e-02) set in MIB and CORESET#0 (1e-06) set in SIB1 may be different from each other, and the former is called 1st CORESET#0 and the latter is called 1st CORESET#0. SS#0 (1e-03) set in MIB and SS#0 (1e-07) set in SIB1 may be different, and the former is called the first SS#0 and the latter is called the second SS#0. SS#0 and CORESET#0 set for the RedCap terminal are called 3rd SS#0 and 3rd CORESET#0. 1st SS#0, 2nd SS#0, and 3rd SS#0 may be the same or different from each other. The first CORESET#0, the second CORESET#0, and the third CORESET#0 may be the same or different from each other. SS#0 and CORESET#0 are each indicated with a 4-bit index. The 4-bit index indicates a setting predetermined in the standard. Except for SS#0 and CORESET#0, the detailed configuration of SS and CORSESET are set as individual information elements.

When an RRC connection is established, additional BWPs may be configured for the terminal.

A serving cell may consist of one or multiple BWPs.

The UE may be configured with multiple DL BWPs and multiple UL BWPs for one serving cell. If the serving cell operates in a paired spectrum (i.e., FDD band), the number of DL BWPs and the number of UL BWPs may be different. If the serving cell operates in an unpaired spectrum (i.e., TDD band), the number of DL BWPs and the number of UL BWPs are the same.

SIB1 includes DownlinkConfigCommonSIB, UplinkConfigCommonSIB, and tdd-UL-DL-ConfigurationCommon.

tdd-UL-DL-ConfigurationCommon is the cell-specific TDD UL/DL configuration. It consists of subfields such as referenceSubcarrierSpacing, pattern1, and pattern2.

referenceSubcarrierSpacing is a reference SCS used to determine time domain boundaries in UL-DL patterns.

pattern1 and pattern2 are TDD uplink and downlink patterns. It consists of subfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

dl-UL-TransmissionPeriodicity represents the period of the DL-UL pattern.

nrofDownlinkSlots indicates the number of consecutive full DL slots in each DL-UL pattern.

nrofDownlinkSymbols indicates the number of consecutive DL symbols from the start of the slot following the last full DL slot.

nrofUplinkSlots indicates the number of consecutive full UL slots in each DL-UL pattern.

nrofUplinkSymbols indicates the number of consecutive UL symbols at the end of the slot before the first full UL slot.

The slot between the last full DL slot and the first full UL slot is a flexible slot. A full UL slot is also called a static UL slot. In this disclosure, the UL slot is a static UL slot.

DownlinkConfigCommonSIB contains BWP-DownlinkCommon for the initial DL BWP. UplinkConfigCommonSIB contains BWP-UplinkCommon for the initial UL BWP. The BWP-id of initialDownlinkBWP is 0.

The RRCReconfiguration message includes multiple BWP-Downlinks, multiple BWP-Uplinks, firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id, and BWP-DownlinkDedicated for the initial DL BWP.

BWP-Downlink includes bwp-Id, BWP-DownlinkCommon, and BWP-DownlinkDedicated.

BWP-Uplink includes bwp-Id, BWP-UplinkCommon, and BWP-UplinkDedicated.

bwp-Id is an integer between 0 and 4. bwp-Id 0 is only used for BWP indicated in SIB1. bwp-Id1 ~ 4 can be used for the BWP indicated in the RRCReconfiguration message.

BWP-DownlinkCommon contains the following information: frequency domain location and bandwidth of this portion of bandwidth, subcarrier spacing to be used in this BWP, cell-specific parameters for the PDCCH of this BWP, and cell-specific parameters for the PDSCH of this BWP.

BWP-UplinkCommon contains the following information: frequency domain location and bandwidth of this portion of bandwidth, subcarrier spacing to be used in this BWP, cell-specific parameters for the PUCCH of this BWP, cell-specific parameters for the PUSCH of this BWP, cell Certain random access parameters.

BWP-DownlinkDedicated is used to configure dedicated (UE-specific) parameters of the downlink BWP. This includes cell-specific parameters for the PDCCH of this BWP, and cell-specific parameters for the PDSCH of this BWP.

BWP-UplinkDedicated is used to configure dedicated (UE-specific) parameters of the uplink BWP.

firstActiveDownlinkBWP-Id contains the ID of the DL BWP to be activated when performing RRC (re)configuration.

defaultDownlinkBWP-Id is the ID of the downlink bandwidth portion to be used when the BWP inactivity timer expires.

bwp-InactivityTimer is the duration in ms after the UE falls back to its default bandwidth portion.

SDT (Small Data Transmission) is a procedure that allows data and/or signaling transmission while maintaining the RRC_INACTIVE state (i.e., without transitioning to the RRC_CONNECTED state).

The SDT procedure begins with a transmission over the RACH (configured via system information) or a Type 1 CG resource (configured via a dedicated signal in RRCRlease). SDT resources can be configured in the initial BWP for both RACH and CG. RACH and CG resources for SDT may be configured on either or both 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 level 2 and/or level 4 RA resources for SDT. If both level 2 and level 4 random access resources for SDT are configured, the UE selects the random access type.

The initial PUSCH transmission during the SDT procedure includes at least a CCCH message. When using CG resources for initial SDT transmission, the UE may perform 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. . After the initial PUSCH transmission, subsequent transmissions are handled differently depending on the type of resource used to start the SDT procedure.

When using CG resources, the network can schedule subsequent UL transmissions using dynamic grants or they can be transmitted on the next CG resource occasion. DL transmissions are scheduled using dynamic allocation. The UE can start subsequent UL transmission only after receiving confirmation (dynamic UL grant or downlink assignment) for the initial PUSCH transmission from the network. For subsequent UL transmission, the UE cannot initiate retransmission through CG resources.

When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic uplink grant and downlink assignment, respectively, after the RA procedure is completed.

During the SDT procedure, if data occurs in the buffer of a radio bearer that is not SDT enabled, the UE uses the UEAssistanceInformation message to send an indication of non-SDT data arrival to the network and, if possible, includes a reason for resumption.

The SDT procedure for CG resources can start with a valid UL timing alignment. UL timing alignment is maintained by the UE based on an SDT-specific timing alignment timer configured by the network through dedicated signaling, and for initial CG-SDT transmissions as well, the configured number of highest ranked SSBs are above the configured RSRP threshold. Maintained by DL RSRP. When the SDT specific timing alignment timer expires, the CG resource is released while maintaining the CG resource configuration.

Logical channel restrictions configured by the network while in the RRC_CONNECTED state and/or in the RRCRlease message for radio bearers active for SDT are applied by the UE during the SDT procedure.

The network may configure the UE to initiate SDT in a cell where the UE receives RRCRlease and transition to RRC_INACTIVE state, or to apply ROHC continuity to SDT when the UE initiates SDT in a cell in RNA.

The network can configure the UE to apply EHC continuity to SDT when the UE receives RRCRlease and starts SDT in a cell that has transitioned to RRC_INACTIVE state, or when the UE starts SDT in a cell in RNA.

The EHC protocol is based on the EHC (Ethernet Header Compression) framework. The Ethernet Header Compression (EHC) protocol compresses Ethernet headers. The fields compressed (i.e., removed from the Ethernet header) by the EHC protocol are DESTINATION ADDRESS, SOURCE ADDRESS, 802.1Q TAG, and LENGTH/TYPE. The EHC compressor and EHC decompressor save the original header field information as "EHC context". Each EHC context is identified with a unique identifier called a context ID (CID). The EHC context must be synchronized between the EHC compressor and EHC decompressor. Otherwise, the EHC decompressor will incorrectly decompress the "Compressed Header (CH)" packet.

The PDCP entity associated with the DRB may be configured by upper layers to use EHC. Each PDCP entity carrying user plane data can be configured to use EHC. Every PDCP entity uses at most one EHC compressor instance and at most one EHC decompressor instance.

FIG. 2A is a diagram explaining the operation of a terminal and a base station according to an embodiment of the present disclosure.

In a wireless communication system including a terminal (2a-01), a first base station (2a-03), and a second base station (2a-05), the terminal and the base station operate as follows.

In step 2a-09, the UE selects a first cell of the first base station based at least in part on the reference signal received power of the first cell. The UE may perform a random access procedure in the first cell for state transition to RRC_CONNECTED.

In steps 2a-11, the terminal reports performance to the first base station or another base station. The UE capability information delivery procedure consists of a step where, when the serving base station transmits an RRC message requesting UE capability information to the UE, the UE transmits an RRC control message called UECapabilityInformation containing UE capability information to the serving base station. UECapabilityInformation includes the following parameters.

inactiveState indicates whether the UE supports RRC_INACTIVE. This is a UE-specific function.

ra-SDT indicates whether the UE supports transmission of data and/or signaling through a radio bearer allowed in RRC_INACTIVE state through a random access procedure (i.e. RA-SDT). This is a UE-specific function.

srb-SDT indicates whether the UE supports the use of signaling radio bearer SRB2 via RA-SDT or CG-SDT. This is a UE-specific function.

cg-SDT indicates whether the UE supports transmission of data and/or signaling over a radio bearer allowed in RRC_INACTIVE state via configured grant type 1 (i.e. CG-SDT). This is a function for each band.

UE-specific functional parameters are signaled for each UE. Band-specific functional parameters are signaled band-specific. When signaled to a UE, the corresponding UE-specific function is supported in all frequency bands supported by the UE. Band-specific functions are supported in a band if signaled for that band.

The UE and the serving base station transmit and receive data in the RRC_CONNECTED state, and when data transmission and reception is completed, the serving base station decides to transition the UE's state to the RRC_INACTIVE state.

In step 2a-13, the first base station transmits an RRCRelease message to the terminal. The RRCRelease message includes SuspendConfig IE, and SuspendConfig includes the fields below.

<SuspendConfig>

1. First terminal identifier: Identifier of the terminal that can be included in the ResumeRequest when the state transitions to RRC_CONNECTED. It has a length of 40 bits.

2. Second terminal identifier: A terminal identifier that can be included in the ResuemeRequest when the state transitions to RRC_CONNECTED. It has a length of 24 bits.

3. ran-PagingCycle: Paging cycle to apply in RRC_INACTIVE state

4. ran-NotificationAreaInfo: Configuration information of ran-NotificationArea consisting of a list of cells, etc. The terminal starts the restart procedure when ran_NotificationArea is changed.

5. t380: Timer associated with periodic resume procedure

6. NCC (nextHopChaningCount): Counter used to derive a new security key after performing the resume procedure.

7. sdt-Config: Configuration information for SDT.

In steps 2a-14, the terminal performs a set of SuspendConfig operations. The SuspendConfig action set is applied at a given point in time. When the SuspendConfig action set is performed, the following actions are performed sequentially.

<SuspendConfig action set>

1: Reset MAC and unconfigure default MAC cell group (if present).

2: Apply the received suspendConfig, excluding the received nextHopChainingCount and the received sdt-Config.

3: Determine the DRB to be configured for SDT based on sdt-DRB-List.

4: Based on sdt-DRB2-Indication, determine whether SRB2 will be configured for SDT.

5: Determine if SRB1 is configured for SDT based on sdt-Config being included in SuspendConfig (or based on sdt-Config containing either sdt-DRB-List or sdt-DRB2-Indication or both).

6: Reset of RLC entities in SRB2.

7: Perform SDU discard for PDCP entity in SRB1.

8: If SRB2 is configured for SDT, perform SDU discard for the PDCP entity of SRB2.

9: Reset RLC entity of SRB1.

10: nextHopChainingCount received in RRCRlease message in UE INACTIVE AS context, current security key, EHC state, C-RNTI used in source PCell, PDCP configuration of radio bearer configured for SDT, RLC configuration of radio bearer configured for SDT, Stores the logical channel configuration of radio bearers configured with SDT, PDCP configuration of radio bearers not configured with SDT, RLC configuration of radio bearers not configured with SDT, logical channel configuration of radio bearers not configured with SDT, etc.

11: Suspend all radio bearers configured for SDT.

12: Suspend all radio bearers not configured for SDT.

13: Enter RRC_INACTIVE state and perform cell selection.

The predetermined time point is as follows.

The earlier of 100 ms after receiving the RRCRelease message or when the lower layer successfully notifies receipt of the RRCRelease message.

In step 2a-15, the terminal selects the second cell of the second base station as a result of cell selection. The terminal can compare the wireless signal quality of the serving cell and neighboring cells and reselect the neighboring cell with better wireless signal quality. Alternatively, you can select a cell whose 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.

In step 2a-17, the terminal receives system information including SIB1 from the second cell.

In steps 2a-19, an event occurs that triggers the resume procedure. The resumption procedure may be triggered when a higher layer or AS requests resumption of a suspended RRC connection or when new data occurs.

The UE determines whether an SDT can be triggered and which SDT should be triggered between RA-SDT and CG-SDT.

The UE starts the resumption procedure for SDT when all of the following conditions are met:

1: The upper layer requests RRC connection resumption and

2: SIB1 contains sdt-ConfigCommon

3: sdt-Config is configured and

4: All pending data in UL is mapped to radio bearers configured for SDT and

5: The data volume of pending UL data across all RBs configured for SDT is less than or equal to sdt-DataVolumeThreshold and

6: RSRP based on downlink path loss is higher than sdt-RSRP-Threshold.

The UE decides to start CG-SDT when the following conditions are met.

1: CG-SDT is configured on the selected UL carrier and the TA of the configured grant type 1 resource is valid, and

2: You can use one or more SSBs configured for CG-SDT with SS-RSRP higher than cg-SDT-RSRP-ThresholdSSB.

CG-SDT is released when the time alignment timer expires or when the UE selects or reselects a cell different from the cell for which CG-SDT is set.

The UE decides to start RA-SDT when the following conditions are met.

1: SDT is started but CG-SDT is not started

2: At least one of the random access resource sets for RA-SDT is available on the selected uplink carrier.

One random access resource set corresponds to one RACH-ConfigCommon or one RACH-ConfigCommon-fc.

The UE determines that it can use the random access resource set of RACH-ConfigCommon-fc for RA-SDT if that RACH-ConfigCommon-fc is associated with an SDT and not with RedCap and CovEng. The UE selects RACH-ConfigCommon-fc for RA-SDT.

The UE determines a random access resource set of RACH-ConfigCommon available for RA-SDT if there is no RACH-ConfigCommon-fc available for RA-SDT. The UE selects the default RACH-ConfigCommon for RA-SDT.

The UE selects RACH-ConfigCommon corresponding to the set of random access resources available for RA-SDT.

If the RA-SDT procedure or CG-SDT procedure is initiated in step 2a-23, the terminal performs an SDT preliminary operation.

/Start SDT preliminary operation/

The UE applies the first predefined PDCP configuration, the first predefined RLC configuration, the first predefined logical channel configuration1 and the first predefined logical channel configuration2 to SRB1.

The UE applies the first predefined BSR configuration and the first predefined PHR configuration.

UE applies timeAlignmentTimerCommon included in SIB1

The UE restores the nextHopChainingCount, current security key, and EHC state received in the RRCRlease message in the UE INACTIVE AS context.

The UE sets resumeMAC-I to the lowest 16 bits of MAC-I calculated based on the restored security key.

The UE derives a new security key based on nextHopChainingCount.

The UE configures the lower layer to apply security protection to all radio bearers except SRB0 based on the new security key.

The UE resets the PDCP entity for SRB1.

UE resumes SRB1.

The UE restores the PDCP configuration and radio bearer RLC configuration of the second radio bearer group in the UE INACTIVE AS context.

The UE restores the saved logical channel configuration 2 of the radio bearer of the third radio bearer group in the UE INACTIVE AS context.

The UE applies the second predefined logical channel configuration 1 and the first predefined logical channel configuration 2 to SRB2.

The UE applies the third default logical channel configuration 1 to the radio bearer of the third radio bearer group.

The UE resets the PDCP entity for the radio bearer of the second radio bearer group without triggering a PDCP status report.

The UE resumes the radio bearer configured in the second radio bearer group.

/SDT Preliminary Task End/

By performing the SDT preliminary operation, the UE prepares the radio bearer configured for SDT for data reception and transmission.

As a result of the above operation, the following settings are applied to each radio bearer configured for SDT. PDCP entities and RLC entities are located in a central device, so configurations stored for PDCP and RLC can be applied to SRB2 and DRB. The MAC entity is located on a distributed device. The MAC entity may not know which UE is performing SDT. The default configuration for MAC applies to SRB1 and SRB2 and DRB.

a first SRB configured for SDT; SRB1 a second SRB configured for SDT; SRB2 DRB configured for SDT; DRB in sdt -DRB-List PDCP Configuration Composition of the first default PDCP Saved PDCP configuration on SRB2 Saved PDCP configuration for that DRB RLC configuration Composition of the first RLC Saved RLC configuration for SRB2 Saved RLC configuration for that DRB Logical Channel Configuration1 (Priority, PBR, LCG, Remaining LCP Limit) First default logical channel configuration 1 Second default logical channel configuration 1 Third default logical channel configuration 1 Logical Channel Configuration 2 (CG-related LCP limitations) First default logical channel configuration 2 First default logical channel configuration 2 Saved Logical Channel Configuration2 for that DRB/Logical Channel

The configuration of the various defaults is described in the table below.

Composition of the first default PDCP t-Reordering = infinity, pdcp -SN- SizeDL = len12bits, pdcp -SN- SizeUL = len12bits, moreThanOneRLC = None Composition of the first RLC sn-FieldLength=size12, t-PollRetransmit=ms45, pollByte=Infinity, t-Reassembly=ms35 First default logical channel configuration 1 priority = 1, priorityedBitRate = infinity, logicalChannelGroup = 0, allowedServingCells = none/not configured, allowedSCS -List = none/not configured, maxPUSCH -Duration = none/not configured. Second default logical channel configuration 1 priority = 2, priorityedBitRate = infinity, logicalChannelGroup = 0, allowedServingCells = none/not configured, allowedSCS -List = none/not configured, maxPUSCH -Duration = none/not configured Third default logical channel configuration 1 priority = 3, priorityedBitRate = kBps0, logicalChannelGroup = 1, allowedServingCells = absent/not configured, allowedSCS -List = absent/not configured, maxPUSCH -Duration = absent/not configured First default logical channel configuration 2 configureGrantType1Allowed = true , allowedCG -List = None Configuration of the first basic BSR periodicBSR-Timer = sf10, retxBSR-Timer = sf80 1st default PHR composition phr-PeriodicTimer = sf10, phr-ProhibitTimer = sf10, multiplePHR = false, phr-Type2OtherCell = false

allowedCG-List indicates that the configured grant is applicable to this logical channel. If present, the UL MAC SDU for this logical channel may only be mapped to the indicated configured grant configuration. If the field is not present, the UL MAC SDU for this logical channel may be mapped to the configured grant configuration.

allowedSCS-List indicates the SCS applicable to this logical channel. If present, the UL MAC SDU for this logical channel may only be mapped to the indicated SCS. Otherwise, the UL MAC SDU of this logical channel can be mapped to any SCS.

allowedServingCells indicates serving cells applicable to this logical channel. If present, the UL MAC SDU of this logical channel can only be mapped to serving cells indicated in this list. Otherwise, the UL MAC SDU of this logical channel may be mapped to any configured serving cell in this cell group.

configureGrantType1Allowed indicates whether a Type 1 configured grant is applicable to this logical channel. If present, the UL MAC SDU of this logical channel may be transmitted in the configured grant type 1. Otherwise, the UL MAC SDU of this logical channel cannot be transmitted with the configured grant type 1.

maxPUSCH-Duration indicates the PUSCH duration applicable to this logical channel. If present, UL MAC SDUs from this logical channel may be transmitted using an uplink grant resulting in the PUSCH duration being less than or equal to the duration indicated by this field. Otherwise, UL MAC SDUs from this logical channel may be transmitted using any uplink grant resulting in any PUSCH period.

The priority is the logical channel priority. Lower values indicate higher priority. Higher priority logical channels can use more resources than lower priority logical channels.

PrioritisedBitRate represents the priority data rate of the logical channel. The value kBps0 corresponds to 0 kbps/s.

logicalChannelGroup is the ID of the logical channel group to which the logical channel belongs.

The priority value of the first predefined logical channel configuration 1 is lower than the priority value of the second predefined logical channel configuration 1. The priority value of the second predefined logical channel configuration 1 is lower than the priority value of the third predefined logical channel configuration 1.

The PrioritisedBitRate value of the first predefined logical channel configuration 1 is the same as the PrioritisedBitRate value of the second predefined logical channel configuration 1. The priorityedBitRate value of the second predefined logical channel configuration 1 is greater than the priorityedBitRate value of the third predefined logical channel configuration 1.

The logicalChannelGroup value of the first predefined logical channel configuration 1 is the same as the logicalChannelGroup value of the second predefined logical channel configuration 1. The logicalChannelGroup value of the second predefined logical channel configuration 1 is different from the logicalChannelGroup value of the third predefined logical channel configuration 1.

periodBSR-Timer represents the number of subframes for periodic BSR reporting. The value sf10 corresponds to 10 subframes.

retxBSR-Timer indicates the number of subframes for BSR retransmission. The value sf80 corresponds to 80 subframes.

phr-PeriodicTimer represents the number of subframes for periodic PHR reporting. The value sf10 corresponds to 10 subframes.

phr-ProhibitTimer represents the number of subframes to prohibit PHR reporting. The value sf80 corresponds to 80 subframes.

multiplePHR indicates whether power headroom should be reported using a single-entry PHR MAC control element or a multi-entry PHR MAC control element. True means use a multi-entry PHR MAC control element and False means use a single-entry PHR MAC control element.

phr-Type2OtherCell indicates whether the UE will report PHR Type 2 for the SpCell of another MAC entity. If set to false, the UE will not report PHR type 2 for SpCells of other MAC entities.

In step 2a-25, the UE performs the RA-SDT operation when the RA-SDT starts and performs the CG-SDT operation when the CG-SDT procedure starts.

<RA-SDT operation>

The UE performs the RA-SDT procedure as follows.

The UE first performs initial PUSCH transmission and then performs subsequent transmission.

Initial PUSCH transmission for RA-SDT is performed as follows.

/Start initial PUSCH transmission for RA-SDT/

The UE selects the uplink on which RA-SDT will be performed based at least in part on rsrp-ThresholdSSB-SUL indicated in the default RACH-ConfigCommon of a given uplink. The predetermined uplink is NUL.

If the RSRP of the downlink path loss reference is less than rsrp-ThresholdSSB-SUL, the UE selects a NUL carrier to perform RA-SDT.

If the RSRP of the downlink path loss reference is more than rsrp-ThresholdSSB-SUL, the UE selects a Supplementary Uplink (SUL) carrier to perform RA-SDT.

The downlink path loss reference may be the SSB with the best RSRP among the cell's SSBs. Alternatively, any SSB in the cell can be a downlink path loss reference.

The UE selects one RACH-ConfigCommon among zero or one or more RACH-ConfigCommon-fc and the default RACH-ConfigCommon of the selected uplink carrier for RA-SDT.

The UE selects the SSB based at least in part on rsrp-ThresholdSSB.

The terminal uses rsrp-ThresholdSSB of the selected RACH-ConfigCommon of the selected uplink carrier. For example, if SUL's default RACH-ConfigCommon is selected, the terminal applies rsrp-ThresholdSSB of SUL's default RACH-ConfigCommon. If the nth RACH-ConfigCommon-fc of the NUL is selected, the terminal applies the rsrp-ThresholdSSB of the second RACH-ConfigCommon included in the nth RACH-ConfigCommon-fc of the NUL.

The UE selects a preamble group based at least in part on the selected RACH-ConfigCommon of the selected uplink carrier.

A total of 64 preambles are defined. They can be divided into two groups. A UE with large data and good channel conditions can select Preamble Group B so that the GNB can allocate a larger UL grant. UEs with small data or poor channel conditions can select Preamble Group A so that the GNB can allocate a general UL grant.

Potential Msg3 size (transmissible UL data, MAC subheader(s) and MAC CE if required) is greater than ra-Msg3SizeGroupA and path loss is preambleReceivedTargetPower, msg3-DeltaPreamble in PCMAX (of the serving cell where RA-SDT procedure is performed) and messagePowerOffsetGroupB subtracted, the UE selects random access preamble group B. Otherwise, the terminal selects random access preamble group A.

One msg3-DeltaPreamble can be included in PUSCH-ConfigCommon, and one msg3-DeltaPreamble can be included in each RACH-ConfigCommon-fc.

If the default RACH-ConfigCommon of an uplink carrier is selected, the terminal selects a random access preamble group using msg3-DeltaPreamble of the PUSCH-ConfigCommon of the selected uplink carrier and Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB of the default RACH-ConfigCommon. If msg3-DeltaPreamble is not included in PUSCH-ConfigCommon, the terminal uses 0.

If the nth RACH-ConfigCommon-fc of one uplink carrier is selected, the terminal creates a random access preamble group using msg3-DeltaPreamble, Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB included in the selected RACH-ConfigCommon-fc of the selected uplink. Choose. If msg3-DeltaPreamble is not included in the RACH-ConfigCommon-fc, the terminal uses msg3-DeltaPreamble0 in PUSCH-ConfigCommon of the selected uplink carrier.

The UE randomly selects a preamble with equal probability among the preambles associated with the selected SSB and the selected preamble group. The UE sets PREAMBLE_INDEX to ra-PreambleIndex corresponding to the selected preamble.

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 among consecutive PRACH opportunities indicated by the PRACH configuration index of the selected RACH-ConfigCommon of the specific BWP of the selected uplink carrier. The specific BWP is the initial uplink BWP.

The UE transmits the selected preamble at the selected PRACH opportunity in the selected uplink.

The UE sets PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × powerRampingStep + POWER_OFFSET_2STEP_RA.

The UE sets the transmission power of the preamble to the sum of PREAMBLE_RECEIVED_TARGET_POWER and path loss.

If the default RACH-ConfigCommon of an uplink carrier is selected for RA-SDT, the terminal uses preambleReceivedTargetPower and powerRampingStep of the default RACH-ConfigCommon of the selected uplink carrier. The UE sets POWER_OFFSET_2STEP_RA to 0. The UE sets DELTA_PREAMBLE according to the preamble format determined from prach-ConfigurationIndex indicated in the default RACH-ConfigCommon. DELTA_PREAMBLE is default for each preamble format. PREAMBLE_POWER_RAMPING_COUNTER is initialized to 1 and increases by 1 for each preamble transmission.

If the nth RACH-ConfigCommon-fc of an uplink carrier is selected for RA-SDT, the terminal uses preambleReceivedTargetPower and powerRampingStep of the nth RACH-ConfigCommon-fc of the selected uplink carrier. The UE sets POWER_OFFSET_2STEP_RA to 0. The UE sets DELTA_PREAMBLE according to the preamble format determined from prach-ConfigurationIndex indicated in the RACH-ConfigCommon-fc. DELTA_PREAMBLE is default for each preamble format. PREAMBLE_POWER_RAMPING_COUNTER is initialized to 1 and increases by 1 for each preamble transmission.

The UE receives an uplink grant from RAR.

To receive RAR, the UE starts ra-ResponseWindow configured in RACH-ConfigCommon at the first PDCCH opportunity after the random access preamble transmission ends. The UE monitors the PDCCH of the SpCell for random access response(s) identified by the RA-RNTI while ra-ResponseWindow is running.

In PDCCH monitoring, the UE applies the searchSpace indicated by ra-SearchSpace in PDCCH-ConfigCommon.

The set of PDCCH candidates to be monitored by the UE is defined as the PDCCH search interval set. The search interval set may be a Common Search Space (CSS) set or a UE specific Search Space (USS) set. The UE monitors PDCCH candidates in the search interval set by ra-SearchSpace of PDCCH-ConfigCommon.

The UE considers reception of the random access response to be successful if the random access response includes a MAC subPDU with a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX.

The MAC subPDU includes MAC RAR. MAC RAR includes fields such as Timing Advance Command, Uplink Grant, and Temporary C-RNTI. The Timing Advance Command field indicates an index value used to control the amount of timing adjustment that the UE should apply. The size of the Timing Advance Command field is 12 bits. The terminal adjusts the uplink transmission timing based on the Timing Advance Command field and starts timeAlignmentTimer. The timeAlignmentTimer is set to timeAlignmentTimerCommon. The Uplink Grant field indicates resources to be used in the uplink. The size of the UL Grant field is 27 bits. The temporary C-RNTI field indicates a temporary ID used by the UE during random access. The size of the temporary C-RNTI field is 16 bits.

The uplink grant field further includes a PUSCH time resource allocation field. The PUSCH time resource allocation field is 4 bits.

One pusch-TimeDomainAllocationList may be included in the PUSCH-ConfigCommon of one uplink carrier.

The PUSCH time resource allocation field indicates the pusch-TimeDomainResourceAllocation of the pusch-TimeDomainResourceAllocationList included in the PUSCH-ConfigCommon of the selected uplink carrier (or the uplink on which the preamble was transmitted).

If the PUSCH-ConfigCommon of the selected uplink carrier does not include pusch-TimeDomainResourceAllocationList, the PUSCH time resource allocation field indicates an indexed row of the default PUSCH time domain resource allocation table illustrated in the table below.

Row index K ₂ S L One j 0 14 2 j 0 12 3 j 0 10 4 j 2 10 5 j 4 10 6 j 4 8 7 j 4 6 8 j+1 0 14 9 j+1 0 12 10 j+1 0 10 11 j+2 0 14 12 j+2 0 12 13 j+2 0 10 14 j 8 6 15 j+3 0 14 16 j+3 0 10

j is a value specific to the PUSCH subcarrier spacing and is defined in the table below.

PUSCH subcarrier spacing j 15 kHz One 30 kHz One 60kHz 2 120kHz 3

When the UE transmits a PUSCH scheduled by RAR, a specific delta is applied to the PUSCH subcarrier spacing in addition to k2. Delta is defined in the table below.

PUSCH subcarrier spacing delta 15 kHz 2 30 kHz 3 60kHz 4 120kHz 6

The UE determines K2 based at least in part on h, the value indicated in the PUSCH time resource allocation field.

When PUSCH-ConfigCommon includes the first pusch-TimeDomainResourceAllocationList, h represents the (h+1)th entry of the first pusch-TimeDomainResourceAllocationList.

If PUSCH-ConfigCommon does not include the first pusch-TimeDomainResourceAllocationList, h represents the row index (h+1) of the default PUSCH time domain resource allocation table.

Each row of the default PUSCH time domain resource allocation table is associated with k2, which is a function of j. and i. The UE determines j according to the PUSCH subcarrier spacing. The UE determines i based at least in part on h. The UE determines k2 by adding the determined j and the determined i. In other words, the UE determines k2 based at least in part on a row index determined in part based on j and h determined in part based on the PUSCH subcarrier spacing.

The PUSCH subcarrier spacing is determined by the subcarrier spacing IE included in the BWP-UplinkCommon IE of the selected uplink carrier. If the UE is in RRC_IDLE or RRC_INACTIVE, BWP-UplinkCommon is indicated in SIB1 and is for the initial uplink BWP. If the UE is in RRC_CONNECTED, BWP-UplinkCommon is for the currently active uplink BWP.

The UE determines the time slot for PUSCH transmission scheduled by RAR. When the UE receives a PDSCH with a RAR message ending in slot n for the PRACH transmission from that UE, the UE transmits the PUSCH in slot (n + k2 + delta). k2 and delta are specific to the subcarrier spacing and are determined as follows.

If pusch-TimeDomainResourceAllocationList is not included in PUSCH-ConfigCommon of ServingCellConfigCommonSIB, k2 is determined based on h, j, and i. j is determined based at least in part on the subcarrier spacing IE included in the BWP-UplinkCommon IE of ServingCellConfigCommonSIB. If the subcarrier spacing IE represents 15kHz or 30kHz, j is 1. If the subcarrier spacing IE represents 60kHz, j is 2. If the subcarrier spacing IE represents 120kHz, j is 3.

Delta is determined based at least in part on the subcarrier spacing IE included in the BWP-UplinkCommon IE of ServingCellConfigCommonSIB. If the subcarrier spacing IE represents 15 kHz, delta is 2. If the subcarrier spacing IE represents 30 kHz, delta is 3. If the subcarrier spacing IE represents 60kHz, delta is 4. If the subcarrier spacing IE represents 120kHz, delta is 6.

S is the symbol where PUSCH transmission begins. L is the length of PUSCH expressed in number of symbols.

The UE transmits Msg 3 in the determined slot according to the UL grant in the received RAR.

The UE determines the PUSCH transmit power by summing the offset, path loss, and other parameters related to the number of PRBs and power control commands.

The offset is the sum of preambleReceivedTargetPower and msg3-DeltaPreamble.

If the default RACH-ConfigCommon of an uplink carrier is selected, the terminal uses msg3-DeltaPreamble of the PUSCH-ConfigCommon of the selected uplink carrier and preambleReceivedTargetPower of the default RACH-ConfigCommon.

If the nth RACH-ConfigCommon-fc of one uplink carrier is selected, the terminal uses msg3-DeltaPreamble and preambleReceivedTargetPower included in the RACH-ConfigCommon-fc of the selected uplink carrier.

The UE generates Msg3. When SDT is applied, Msg3 (or MAC PDU scheduled by RAR) includes RRC message and DRB data and BSR and PHR. The RRC message is not encrypted and the DRB data is encrypted with a security key derived from the security key stored in the UE AS Inactive context. The RRC message is included in the first MAC SDU and the DRB data is included in the second MAC SDU. The first MAC SDU and the second MAC SDU consist of a MAC subheader and MAC payload. The MAC payload of the second MAC SDU includes DRB data (MAC SUD generated in the DRB of the third radio bearer group). The MAC subheader is not encrypted. The second MAC SDU is located after the first MAC SDU. The RRC message is an RRRCesumeRequest message. BSR is included in the first MAC CE. PHR is included in the second MAC CE. The first MAC CE is located after the first MAC SDU. The second MAC CE is located after the first MAC CE.

The UE transmits Msg3. The UE starts contention-ResolutionTimer. The timer is set to the value indicated in the selected RACH-ConfigCommon of the selected uplink carrier.

GNB receives Msg 3 and processes the contents. When the RRC message requests connection resumption, the GNB performs call admission control and takes action according to the results. GNB processes DRB data in Msg 3. GNB handles BSR and PHR within Msg 3.

The LCG field of the BSR is determined based at least in part on the third predefined logical channel configuration 1.

The format of the PHR is determined based at least in part on the first predefined PHR format.

If the UL grant of the RAR can accommodate all transmittable data pending transmission, but is not sufficient to additionally accommodate the BSR MAC CE and its subheaders, the BSR is canceled. All data waiting to be transmitted is PDCP entity and RLC entity data and does not include MAC CE and its subheaders.

There is an ongoing SDT procedure and the UL grant in the RAR can accommodate all transmittable data waiting to be transmitted and (if the BSR is triggered and not canceled) the BSR MAC CE and its subheaders, but additionally the PHR MAC CE and subheaders. If there is not enough to accommodate, the PHR will be cancelled.

The UE receives Msg 4 from the base station. Msg 4 contains CR MAC CE.

The UE receives the DCI on the PDCCH addressed to the temporary C-RNTI based at least in part on the ra-SearchSpace. The DCI includes a time domain resource allocation field. Temporary C-RNTI is allocated from RAR.

To receive DCI from the PDCCH addressed to the temporary C-RNTI, the UE applies the searchSpace indicated in ra-SearchSpace.

PDSCH-ConfigCommon can contain one pdsch-TimeDomainAllocationList.

If pdsch-TimeDomainAllocationList is included in PDSCH-ConfigCommon, the terminal determines the time domain relationship between PDCCH and PDSCH using the pdsch-TimeDomainAllocationList in PDSCH-ConfigCommon.

If pdsch-TimeDomainAllocationList is not included in PDSCH-ConfigCommon, the terminal determines the time domain relationship between the PDCCH and PDSCH using the default PDSCH time domain resource allocation table.

The PDSCH time resource allocation field indicates pdsch-TimeDomainResourceAllocation of the pdsch-TimeDomainResourceAllocationList included in PDSCH-ConfigCommon.

If PDSCH-ConfigCommon does not include pdsch-TimeDomainResourceAllocationList, the PDSCH time resource allocation field indicates an indexed column of the default PDSCH time domain resource allocation table, illustrated in the table below.

Row index dmrs-TypeA-Position PDSCH mapping type K ₀ S L One 2 Type A 0 2 12 3 Type A 0 3 11 2 2 Type A 0 2 10 3 Type A 0 3 9 3 2 Type A 0 2 9 3 Type A 0 3 8 4 2 Type A 0 2 7 3 Type A 0 3 6 5 2 Type A 0 2 5 3 Type A 0 3 4 6 2 Type B 0 9 4 3 Type B 0 10 4 7 2 Type B 0 4 4 3 Type B 0 6 4 8 2,3 Type B 0 5 7 9 2,3 Type B 0 5 2 10 2,3 Type B 0 9 2 11 2,3 Type B 0 12 2 12 2,3 Type A 0 One 13 13 2,3 Type A 0 One 6 14 2,3 Type A 0 2 4 15 2,3 Type B 0 4 7 16 2,3 Type B 0 8 4

The UE determines k0, S, and L based at least in part on h, the value indicated in the time resource allocation field.

When PDSCH-ConfigCommon includes pdsch-TimeDomainResourceAllocationList, h represents the (h+1)th entry of the first pdsch-TimeDomainResourceAllocationList.

Each item of pdsch-TimeDomainResourceAllocationList (or each pdsch-TimeDomainResourceAllocation of pdsch-TimeDomainResourceAllocationList) is associated with k0 and S and L. The UE determines k0, S, and L for PDSCH reception by the k0, S, and L values associated with pdsch-TimeDomainResourceAllocation, denoted by h.

If PDSCH-ConfigCommon does not include pdsch-TimeDomainResourceAllocationList, h represents the row index (h+1) of the default PDSCH time domain resource allocation table.

If the MAC PDU is received based at least in part on the ra-SearchSpace and Temporary C-RNTI and the MAC PDU is successfully decoded, the UE stops the ra-ContentionResolutionTimer.

If the MAC PDU contains the UE Contention Resolution Identity MAC CE and the UE Contention Resolution Identity of the MAC CE matches the CCCH SDU (i.e. RRCResumeRequest) transmitted in Msg3, the UE considers this contention resolution successful and sends the C-RNTI Set to the value of TEMPORARY_C-RNTI (i.e., the temporary C-RNTI assigned to the RAR becomes the UE's C-RNTI).

Upon successful contention resolution, the UE starts subsequent transmission for RA-SDT.

/End initial PUSCH transmission for RA-SDT/

Subsequent transmissions for RA-SDT are as follows:

The UE monitors the PDCCH addressed by the C-RNTI based at least in part on the sdt-SearchSpace if sdt-SearchSpace is configured in sdt-ConfigCommon.

The UE monitors the PDCCH addressed by the C-RNTI based at least in part on the ra-SearchSpace if sdt-SearchSpace is not configured in sdt-ConfigCommon.

The first uplink carrier is the uplink carrier selected for the most recent preamble transmission, the uplink carrier selected for initial PUSCH transmission for RA-SDT, or the uplink carrier on which initial PUSCH transmission for RA-SDT was performed.

Upon receiving a DCI containing an uplink grant, the UE (if pusch-TimeDomainResourceAllocationList is included in the PUSCH-ConfigCommon of the first uplink carrier) at least partially configures the pusch-TimeDomainResourceAllocationList in the PUSCH-ConfigCommon of the first uplink carrier. Based on or (if pusch-TimeDomainResourceAllocationList is not included in the PUSCH-ConfigCommon of the first uplink carrier) or based at least in part on a basic PUSCH time domain resource allocation table, determine the time domain relationship between the PDCCH and the PUSCH.

If msg3-DeltaPreamble is not included in the PUSCH-ConfigCommon of the first uplink carrier and the default RACH-Configcommon is selected for the RA-SDT, the UE determines the Determine the uplink transmission power of PUSCH.

msg3-DeltaPreamble is not included in the PUSCH-ConfigCommon of the first uplink carrier, msg3-DeltaPreamble is not included in the selected RACH-ConfigCommon-fc of the first uplink carrier, and RACH-ConfigCommon-fc is selected for RA-SDT Then, the UE determines the uplink transmit power of the PUSCH based at least in part on the preambleReceivedTargetPower of the selected RACH-ConfigCommon-fc of the first uplink carrier.

If msg3-DeltaPreamble is included in the PUSCH-ConfigCommon of the first uplink carrier and the default RACH-ConfigCommon is selected for the RA-SDT, the UE receives preambleReceivedTargetPower in the default RACH-ConfigCommon of the first uplink carrier and the default RACH-ConfigCommon of the first uplink carrier. Determine the uplink transmission power of the PUSCH based at least in part on the msg3-DeltaPreamble in the PUSCH-ConfigCommon.

If msg3-DeltaPreamble is included in the selected RACH-ConfigCommon-fc of the first uplink carrier and RACH-ConfigCommon-fc is selected for RA-SDT, the UE will receive the preambleReceivedTargetPower and Determine the uplink transmission power of the PUSCH based at least in part on msg3-DeltaPreamble.

The UE determines the PUSCH transmit power by summing the offset, path loss, and other parameters related to the number of PRBs and power control commands.

The offset is the sum of preambleReceivedTargetPower and msg3-DeltaPreamble.

The UE performs PUSCH transmission based at least in part on the transmit power and time domain relationship determined above.

Upon receiving the DCI containing the downlink assignment, the UE determines the time domain relationship between the PDCCH and PDSCH based at least in part on X.

If PDSCH-ConfigCommon includes pdsch-TimeDomainResourceAllocationList, X is pdsch-TimeDomainResourceAllocationList in PDSCH-ConfigCommon.

If PUSCH-ConfigCommon does not include pdsch-TimeDomainResourceAllocationList, X is the default PDSCH time domain resource allocation table.

The time domain relationship between the PDCCH and the PDSCH is indicated (or associated) by the subframe for the PDSCH, the start symbol of the PDSCH, and the number of symbols in the PDSCH.

The UE receives the PDSCH based at least in part on the time domain relationship determined above.

During subsequent transmissions for RA-SDT, the UE starts and restarts the inactivityTimer when receiving a MAC SDU or transmitting a MAC SDU.

When the inactivityTimer expires, the UE moves to RRC_IDLE and performs work.

The inactivityTimer is configured by RRCRlease received in the first cell.

During subsequent transmissions for RA-SDT, the UE restarts monitoringTimer upon receiving the monitoringTimer MAC CE.

MAC CE consists of only MAC subheaders. The MAC subheader consists of two R bits, an LCID field, and an eLCID field.

MonitoringTimer starts when the RA-SDT procedure starts.

When the RRCRlease message is received, the monitoringTimer is stopped.

monitoringTimer is configured by SIB1 received from the second cell.

<CG-SDT operation>

The UE performs the CG-SDT procedure as follows.

The UE first performs initial PUSCH transmission and then performs subsequent transmission.

Initial PUSCH transmission for CG-SDT is performed as follows.

<Initial PUSCH transmission for CG-SDT>

/start/

The UE generates a MAC PDU for the first PUSCH transmission for CG-SDT. The MAC PDU for the first PUSCH transmission may include an RRC message, DRB data, BSR, and PHR. RRC messages are not encrypted and DRB data is encrypted with a security key stored in the UE AS Inactive context. The RRC message is included in the first MAC SDU and the DRB data is included in the second MAC SDU. The first MAC SDU and the second MAC SDU consist of a MAC subheader and MAC payload. The MAC payload of the second MAC SDU includes DRB data. The MAC subheader is not encrypted. The second MAC SDU is located after the first MAC SDU. The RRC message is an RRRCesumeRequest message. BSR is included in the first MAC CE. PHR is included in the second MAC CE. The first MAC CE is located after the first MAC SDU. The second MAC CE is located after the first MAC CE.

The UE transmits the MAC PDU. The UE starts cg-SDT-RetransmissionTimer and configuredGrantTimer. The timers are in the BWP-Uplink-Dedicated-SDT of the selected uplink carrier in sdt-Config in RRCRelease. They are set with the values indicated in cg-SDT-RetransmissionTimer and configuredGrantTimer, respectively.

The LCG field of the BSR is determined based at least in part on the third predefined logical channel configuration 1.

The format of the PHR is determined based at least in part on the first predefined PHR format.

If the configured grant can accommodate all transmittable data pending transmission, but is not sufficient to accommodate additional BSR MAC CE and its subheaders, the BSR is canceled. All data waiting to be transmitted is PDCP entity and RLC entity data and does not include MAC CE and its subheaders.

If there is an ongoing CG-SDT procedure and the established grant can accommodate all transmittable data waiting to be transmitted and (if the BSR is triggered and not canceled) the BSR MAC CE and its subheaders, but in addition the PHR MAC CE and subheaders If there is not enough to accommodate, the PHR will be cancelled.

configureGrantTimer is to control initial PUSCH transmission for SDT. configureGrantTimer starts on initial transmission for the configured grant. configureGrantTimer is per HARQ process. configureGrantTimer is stopped when the first downlink allocation is received after initial transmission for CG-SDT with CCCH message. If configureGrantTimer expires, the SDT procedure is considered failed and the UE moves to RRC_IDLE to perform the operation.

cg-SDT-RetransmissionTimer is for controlling retransmission during initial PUSCH transmission for SDT. The cg-SDT-RetransmissionTimer starts when the configured uplink grant is used for retransmission of the initial transmission of CG-SDT with CCCH message. A retransmission is triggered on the configured grant while cg-SDT-RetransmissionTimer is running.

After transmitting the MAC PDU for the initial PUSCH transmission, the UE determines the Monitors the addressed PDCCH.

If downlink allocation is received through PDCCH for C-RNTI and it is the first downlink allocation after initial transmission for CG-SDT containing a CCCH message, the UE receives the CCCH message for which initial PUSCH transmission for CG-SDT has been successfully completed. With this, cg-SDT-RetransmissionTimer and configureGrantTimer are stopped for the corresponding HARQ process for initial transmission, and initial PUSCH transmission for CG-SDT is successfully completed.

The UE determines the time domain relationship between the PDCCH and PDSCH based at least in part on Y.

If pdsch-TimeDomainResourceAllocationList is included in the PDSCH-Config of BWP-Downlink-Dedicated-SDT of RRCRlease received in the first cell, Y is pdsch-TimeDomainResourceAllocationList of PDSCH-Config.

If pdsch-TimeDomainResourceAllocationList is not included in the PDSCH-Config of the BWP-Downlink-Dedicated-SDT of the RRCRlease received in the first cell, and pdsch-TimeDomainResourceAllocationList is included in the PDSCH-ConfigCommon in SIB1 of the second cell, Y is pdsch-TimeDomainResourceAllocationList is PDSCH-ConfigCommon.

If pdsch-TimeDomainResourceAllocationList is not included in the PDSCH-Config of BWP-Downlink-Dedicated-SDT of RRCRlease received in the first cell and pdsch-TimeDomainResourceAllocationList is not included in PDSCH-ConfigCommon of SIB1 of the second cell, Y is the default PDSCH time This is a resource allocation table.

<Subsequent transmission for SG-SDT>

The UE monitors the PDCCH addressed by the C-RNTI and CS-RNTI based at least in part on the sdt-cg-SearchSpace.

Upon receiving the DCI containing the uplink grant, the UE determines the time domain relationship between the PDCCH and PUSCH based at least in part on Z.

If pusch-TimeDomainResourceAllocationList is included in the PUSCH-Config of the BWP-Uplink-Dedicated-SDT of the uplink carrier selected in RRCRlease received in the first cell, Z is the pusch-TimeDomainResourceAllocationList of PUSCH-Config.

The pusch-TimeDomainResourceAllocationList is not included in the PUSCH-ConfigCommon of SIB1 received from the 2nd cell, and the pusch-TimeDomainResourceAllocationList is included in the PUSCH-Config of the BWP-Uplink-Dedicated-SDT of the uplink carrier selected in RRCRlease received from the 2nd cell. If not included, Z is the default PUSCH time domain resource allocation table.

The UE determines the uplink transmission power of the PUSCH at least partially in W.

If sdt-P0-PUSCH and sdt-Alpha are included in the CG-SDT-Configuration of the BWP-Uplink-Dedicated-SDT of the uplink carrier selected in RRCRlease, W is the BWP-Uplink-Dedicated-SDT of the uplink carrier selected in RRCRlease. These are sdt-P0-PUSCH and sdt-Alpha of SDT's CG-SDT-Configuration.

If sdt-P0-PUSCH and sdt-Alpha are not included in the CG-SDT-Configuration of the BWP-Uplink-Dedicated-SDT of the uplink carrier selected in RRCRlease, W is the BWP-Uplink-Dedicated of the selected uplink carrier in RRCRlease -P0-PUSCH and Alpha of SDT's PUSCH-Config.

The UE determines the PUSCH transmit power by summing the offset, path loss, and other parameters related to the number of PRBs and power control commands.

Offset is the sum of P0-PUSCH and Alpha or the sum of sdt-P0-PUSCH and sdt-Alpha.

The UE performs PUSCH transmission based at least in part on the transmit power and time domain relationship determined above.

The UE determines the time domain relationship between the PDCCH and PDSCH based at least in part on XX.

If pdsch-TimeDomainResourceAllocationList is included in the PDSCH-Config of BWP-Downlink-Dedicated-SDT of RRCRlease received in the first cell, XX is pdsch-TimeDomainResourceAllocationList of PDSCH-Config.

If pdsch-TimeDomainResourceAllocationList is not included in the PDSCH-Config in BWP-Downlink-Dedicated-SDT of RRCRlease received in the first cell and pdsch-TimeDomainResourceAllocationList is included in PDSCH-ConfigCommon in SIB1 of the second cell, XX is the PDSCH -ConfigCommon's pdsch-TimeDomainResourceAllocationList.

If pdsch-TimeDomainResourceAllocationList is not included in the PDSCH-Config in the BWP-Downlink-Dedicated-SDT of the RRCRlease received in the first cell and pdsch-TimeDomainResourceAllocationList is not included in the PDSCH-ConfigCommon in SIB1 of the second cell, XX is This is the default PDSCH time domain resource allocation table.

During subsequent transmissions for RA-SDT, the UE starts and restarts the inactivityTimer when receiving a MAC SDU or transmitting a MAC SDU. When the inactivityTimer expires, the UE moves to RRC_IDLE and performs work.

The inactivityTimer is configured by RRCRlease received in the first cell.

During subsequent transmissions for CG-SDT, the UE restarts monitoringTimer upon receiving the monitoringTimer MAC CE. MAC CE consists of only MAC subheaders. The MAC subheader consists of two R bits, an LCID field, and an eLCID field.

MonitoringTimer starts when the CG-SDT procedure starts.

When the RRCRlease message is received, the monitoring timer is stopped.

The monitoring timer is configured by SIB1 received from the second cell.

In step 2a-27, the UE performs an SDT fallback operation if data appears in the buffer of a radio bearer for which SDT is not activated (or not configured).

<SDT fallback operation>

/start/

The UE starts sending a UEAssistanceInformation message to provide nonSDT-DataIndication when data and/or signaling mapped to a radio bearer not configured for SDT becomes available during SDT.

The UE transmits UEAssistanceInformation including nonSDT-DataIndication through SRB1.

If RA-SDT is in progress, the UE transmits UEAssistanceInformation based on C-RNTI and sdt-SearchSpace.

If CG-SDT is in progress, the UE transmits UEAssistanceInformation based on C-RNTI, CS-RNTI, and cg-sdt-SearchSpace.

nonSDT-DataIndication contains an IE that indicates why data became available on a radio bearer that is not configured for SDT.

When the IE is included in UEAssistanceInformation, the IE indicates one of the following values: Emergency, highPriorityAccess, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess.

When the IE is included in a RRCResumeRequest, the IE represents one of the following values: Emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, mcs-PriorityAccess.

That is, when the IE is included in UEAssistanceInformation, mt-Access and rna-Update are not used.

The UE monitors the PDCCH based at least in part on sdt-SearchSpace or sdt-cg-SerachSpace for reception of RRCResume.

The UE receives the RRCResume message and completes the fallback operation.

/end/

SIB1

SIB1 includes ServingCellConfigCommonSIB. ServingCellConfigCommonSIB includes 1 DownlinkConfigCommonSIB and 2 UplinkConfigCommonSIB. One UplinkConfigCommonSIB is for normal uplink (NUL, Normal Uplink) and the other UplinkConfigCommonSIB is for supplementary uplink (SUL, Supplementary Uplink). UplinkConfigCommonSIB for NUL is located before UplinkConfigCommonSIB for SUL.

DownlinkConfigCommonSIB includes FrequencyInfoDL-SIB and BWP-DownlinkCommon. BWP-DownlinkCommon is for the initial DL BWP and includes PDCCH-ConfigCommon and PDSCH-ConfigCommon.

UplinkConfigCommonSIB includes FrequencyInfoUL-SIB and TimeAlignmentTimer and BWP-UplinkCommon. BWP-UplinkCommon is for the initial UL BWP. BWP-UplinkCommon includes RACH-ConfigCommon, PUSCH-ConfigCommon, PUCCH-ConfigCommon, and a plurality of RACH-ConfigCommon_fc.

DownlinkConfigCommonSIB is the common downlink configuration of the serving cell. It consists of subfields such as FrequencyInfoDL-SIB and BWP-DownlinkCommon.

FrequencyInfoDL-SIB is the basic parameter of the downlink carrier. It consists of subfields such as frequency band list and carrier bandwidth for each SCS.

BWP-DownlinkCommon is a configuration of the second downlink IBWP. It consists of subfields such as BWP, PDCCH-ConfigCommon, and PDSCH-ConfigCommon. The first IBWP has a frequency domain corresponding to the first CORESET#0 of the MIB and has subcarrier spacing indicated in the MIB. The first IBWP is an IBWP indicated in MIB and receives SIB1, and the second IBWP is an IBWP indicated in SIB1 and receives SIB2, paging, random access response message, etc.

BWP is an IE that configures the general parameters of BWP. It consists of subfields such as locationAndBandwidth, which indicates the bandwidth and location of the BWP, and subcarrierSpacing, which indicates the SCS of the BWP.

SIB1 also includes the sdt-ConfigCommonSIB field.

The sdt-Config field contains SDT-Config IE. SDT-Config IE includes the fields sdt-DRB-List, sdt-SRB2-Indication, sdt-MAC-PHY-CG-Config, and sdt-DRB-ContinueEHC.

sdt-DRB-ContinueEHC contains IE representing either cell or rna. This field indicates whether the PDCP entity for the radio bearer configured for SDT continues or resets the EHC header compression protocol during PDCP reset during the SDT procedure. The Value cell indicates that ROHC header compression continues when SDT is resumed in the same cell as the PCell upon receipt of the RRCRlease message. The rna value indicates that EHC header compression continues when resuming for SDT in a cell belonging to the same RNA as the PCell upon receipt of the RRCRlease message. If the field is missing, the PDCP entity for the radio bearer configured for SDT will reset the EHC header compression protocol during PDCP reset during the SDT procedure.

sdt-DRB-List contains 0 or more DRB-Identities. This field indicates the ID of the DRB configured for SDT. If the size of the sequence is 0, the UE assumes that DRB is not configured for SDT.

sdt-SRB2-Indication contains an IE indicating that it is allowed. This field indicates whether SRB2 is configured for SDT. If the field is missing, SRB2 is not configured for SDT.

The sdt-MAC-PHY-CG-Config field contains SDT-MAC-PHY-CG-Config IE. SDT-MAC-PHY-CG-Config IE contains the following fields: a cg-SDT-Config-LCH-restrictionToAddModList, a cg-SDT-Config-Initial-BWP-NUL, a cg-SDT-Config-Initial- BWP-SUL, cg-SDT-Config-Initial-BWP-DL, cg-SDT-TimeAlignmentTimer, cg-SDT-RSRP-ThresholdSSB, C-RNTI, CS-RNTI.

cg-SDT-Config-LCH-restrictionToAddModList contains one or more CG-SDT-Config-LCH-restriction IEs. CG-SDT-Config-LCH-restriction IE includes logicalChannelIdentity field and configuredGrantType1Allowed field. CG-SDT-Config-LCH-restriction IE indicates whether the logical channel indicated by the logicalChannelIdentity field can use the type1 configuration grant.

cg-SDT-Config-Initial-BWP-NUL contains BWP-Uplink-Dedicated-SDT IE.

cg-SDT-Config-Initial-BWP-SUL contains BWP-Uplink-Dedicated-SDT IE.

BWP-Uplink-Dedicated-SDT IE includes PUSCH-Config IE and ConfiguredGrantConfigToAddModList IE.

PUSCH-Config IE is used to configure UE-specific PUSCH parameters applicable to the initial BWP of the first cell.

ConfiguredGrantConfigToAddModList IE contains one or more ConfiguredGrantConfigToAddMod IEs.

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.

PDCCH-Config IE is used to configure UE-specific PDCCH parameters applicable to the initial BWP of the first cell.

PDSCH-Config IE is used to configure UE-specific PDSCH parameters applicable to the initial BWP of the first cell.

cg-SDT-TimeAlignmentTimer includes TimeAlignmentTimer IE. This field represents the TAT value for CG-SDT.

cg-SDT-RSRP-ThresholdSSB includes RSRP-Range IE. This field indicates the configured RSRP threshold for SSB selection for CG-SDT.

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 normal uplink of the first cell and secondary uplink of the first cell and dynamic allocation in the downlink of the first cell.

CS-RNTI includes the RNTI value IE. This field indicates the RNTI value for the type1 configured grant to be used during CG-SDT. The CS-RNTI indicated in this field is valid for type 1 configured grants in the normal uplink of the first cell and the secondary uplink of the first cell.

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).

If SDT-Config without sdt-MAC-PHY-CG-Config is included in RRCRlease, the UE considers RA-SDT to be configured. The UE also considers RA-SDT to be applicable to the third cell. The third cell is a cell where SIB1 including SDT-ConfigCommonSIB is broadcast.

If SDT-Config with sdt-MAC-PHY-CG-Config is included in RRCRlease, the UE considers CG-SDT to be configured. The UE also considers CG-SDT to be applicable in the first cell and RA-SDT to be applicable in the third cell. The first cell is the PCell that received the RRCRlease message including SDT-Config.

The sdt-ConfigCommonSIB field includes the sdt-RSRP-Threshold field and the sdt-DataVolumeThreshold field.

sdt-RSRP-Threshold indicates the RSRP threshold for determining whether the UE will perform the SDT procedure.

sdt-DataVolumeThreshold represents the data volume threshold used to determine whether SDT can be started.

PDCCH-ConfigCommon is a cell-specific PDCCH parameter of the initial BWP of the second cell. It consists of subfields such as controlResourceSetZero, commonControlResourceSet, searchSpaceZero, commonSearchSpaceList, searchSpaceOtherSystemInformation, pagingSearchSpace, and ra-SearchSpace.

controlResourceSetZero is defined as an integer between 0 and 15. Displays one of the default CORESET#0 configurations. The controlResourceSetZero included in the MIB corresponds to the first CORESET#0, and the controlResourceSetZero included in the PDCCH-ConfigCommon of the servingCellConfigCommon of SIB1 corresponds to the second CORESET#0.

searchSpaceZero is defined as an integer between 0 and 15. Indicates one of the default SS#0 configurations. The searchSpaceZero included in the MIB corresponds to the first SS#0, and the controlResourceSetZero included in the PDCCH-ConfigCommon of servingCellConfigCommon of SIB1 corresponds to the second SS#0.

commonControlResourceSet is a common CORESET defined as ControlResourceSet IE. Defines additional CORESETs that can be used for paging reception, random access response reception, system information reception, etc.

commonSearchSpaceList is a list of common SSs. Joint SS can be used to receive paging, receive random access responses, receive system information, etc.

searchSpaceOtherSystemInformation is defined with SS identifier IE. If it is 0, it displays the second SS#0, and if it is a value other than 0, it displays one of the SS defined in commonSearchSpaceList.

pagingSearchSpace is defined with SS identifier IE. If it is 0, it displays the second SS#0, and if it is a value other than 0, it displays one of the SS defined in commonSearchSpaceList.

ra-SearchSpace is defined with SS identifier IE. If it is 0, it displays the second SS#0, and if it is a value other than 0, it displays one of the SS defined in commonSearchSpaceList.

PDCCH-ConfigCommon configures one or more TYPE 1 CSS (Common Search Space) and TYPE2 CSS.

TYPE1 CSS is applied and used for both RRC_INACTIVE UE and RRC_IDLE UE. The configuration of the TYPE1 CSS is either predefined (in the case of searchSpaceZero) or referenced by one of the commonSearchSpaceList. searchSpaceZero and searchSpaceOtherSystemInformation and pagingSearchSpace and ra-SearchSpace are TYPE1 CSS. CommonSearchSpaceList contains one or more SearchSpace IEs.

TYPE2 CSS is applied and used only for RRC_INACTIVE UE. type2 CSS is constructed by SearchSpace2 IE.

sdt-SearchSpace is TYPE2 CSS.

PDCCH-Config is used to configure UE-specific PDCCH parameters such as control resource set (CORESET), search space and additional parameters for acquiring PDCCH.

It consists of fields such as controlResourceSetToAddModList, searchSpacesToAddModList and tpc-SRS.

The controlResourceSetToAddModList field contains a list of UE-specifically configured CORESETs (Control Resource Sets) to be used by the UE.

The searchSpacesToAddModList field contains a list of UE specifically configured search spaces.

The tpc-SRS field enables and configures reception of group TPC commands for SRS. The tpc-SRS field includes SRS-TPC-CommandConfig IE. SRS-TPC-CommandConfig is used to configure the UE to extract the TPC command for SRS from the DCI's group-TPC message.

PDCCH-Config of RRCReconfiguration configures TYPE1 USS (UE specific Search Space).

PDCCH-Config of sdt-MAC-PHY-CG in RRCRlease's sdt-Config configures TYPE2 USS (also known as sdt-CG-SearchSpace).

TYPE1 USS is configured by SearchSpace IE. TYPE2 USS is configured by SearchSpace2 IE.

TYPE1 USS applies and is used only for RRC_CONNECTED UE. TYPE2 USS applies and is used only for RRC_INACTIVE UE. TYPE1 USS is stored in AS UE Inactive CONTEXT when changing state from RRC_CONNECTED to RRC_INATIVE. TYPE2 USS is discarded/released when the state changes from RRC_INACTIVE to RRC_CONNECTED.

SearchSpace IE defines how/where to search for PDCCH candidates. SearchSpace IE includes fields such as searchSpaceId, controlResourceSetId, monitoringSlotPeriodicityAndOffset, period, and searchSpaceType.

SearchSpace2 IE defines how/where to search for PDCCH candidates. SearchSpace IE includes fields such as controlResourceSetId, monitoringSlotPeriodicityAndOffset, period, and searchSpaceType2.

controlResourceSetId represents the CORESET applicable to this SearchSpace. MonitoringSlotPeriodicityAndOffset represents a slot for PDCCH monitoring consisting of periodicity and offset. duration represents the number of consecutive slots for which the SearchSpace lasts in all cases. searchSpaceType indicates whether this is a common or UE-specific search space and the DCI type to be monitored.

searchSpaceType2 indicates whether this is a specific CSS (e.g. sdt-SearchSpace) or a specific USS (e.g. sdt-CG-SearchSpace).

searchSpaceId is used to identify the search space. It is an integer between 0 and 39.

Since there is only one TYPE2 CSS and one TYPE2 USS, searchSpace2 IE does not use searchSpaceId.

PDSCH-ConfigCommon consists of pdsch-TimeDomainAllocationList with cell-specific PDSCH parameters of the initial BWP of the second cell. pdsch-TimeDomainAllocationList is a list consisting of multiple pdsch-TimeDomainAllocations.

pdsch-TimeDomainAllocation configures the time domain relationship between PDCCH and PDSCH. It consists of subfields such as K0 and startSymbolAndLength. K0 is the slot offset between DCI and scheduled PDSCH. startSymbolAndLength is an index indicating a combination of a valid start symbol and length.

pcch-Config is a configuration related to paging. It consists of subfields such as base station paging cycle, PF-related parameters, and PO-related parameters.

bcch-config is a configuration related to system information. It consists of subfields such as modificationPeriodCoeff, which indicates the length of the modification period.

UplinkConfigCommonSIB is the common uplink configuration of the serving cell. It consists of subfields such as frequencyInfoUL, initialUplinkBWP, and timeAlignmentTimerCommon.

FrequencyInfoUL-SIB is the basic parameter of the uplink carrier. It consists of subfields such as frequency band list and carrier bandwidth for each SCS.

BWP-UplinkCommon is a configuration of the second uplink IBWP. It consists of subfields such as BWP, rach-ConfigCommon, pusch-ConfigCommon, and pucch-ConfigCommon.

PDSCH-Config IE is used to configure UE-specific PDSCH parameters. It consists of the dataScramblingIdentityPDSCH field, pdsch-TimeDomainAllocationList field, and mcs-Table field.

The dataScramblingIdentityPDSCH field represents an identifier used to initialize data scrambling (c_init) for PDSCH.

The mcs-Table field indicates the MCS table that the UE will use for PDSCH. If there is no field, the UE applies the 64QAM value. The value 64QAM means MCS table for 64QAM. The value 256QAM refers to the MCS table for 256QAM.

rach-ConfigCommon is a cell-specific random access parameter of the initial BWP of the second cell. It consists of subfields such as prach-ConfigurationIndex, msg1-FrequencyStart, preambleReceivedTargetPower, ra-ResponseWindow, preambleTransMax, msg1-SubcarrierSpacing, rsrp-ThresholdSSB, rsrp-ThresholdSSB-SUL, ra-ContentionResolutionTimer, and featureCombination.

RACH-ConfigCommon-fc is a RACH-ConfigCommon associated with at least one feature combination. The default RACH-ConfigCommon is a RACH-ConfigCommon that is not associated with a feature combination.

prach-ConfigurationIndex is the PRACH configuration index. One PRACH configuration corresponds to pattern information about 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.

msg1-FrequencyStart is the offset from PRB0 of the lowest PRACH transmission opportunity. This is information indicating PRACH transmission resources in the frequency domain. PRB0 is the lowest frequency PRB among the PRBs of the corresponding carrier.

preambleReceivedTargetPower is the target power level of the network receiving end. This is a parameter related to transmission output control during the random access procedure.

ra-ResponseWindow is the length of the random access response window expressed in the number of slots.

preambleTransMax is the maximum number of random access preamble transmissions.

msg1-SubcarrierSpacing. is the SCS of PRACH. Commonly applied to general terminals and RedCap UE.

rsrp-ThresholdSSB is the SSB selection criterion. The terminal selects a preamble corresponding to the selected SSB and performs random access.

rsrp-ThresholdSSB-SUL is the SUL selection criterion. The terminal selects a SUL carrier to perform random access based at least in part on this threshold.

ra-ContentionResolutionTimer is the initial value of the contention resolution timer. Displays the number of subframes.

pusch-ConfigCommon consists of subfields such as pusch-TimeDomainAllocationList with cell-specific PUSCH parameters of the initial BWP of the second cell. pusch-TimeDomainAllocationList is a list composed of multiple pusch-TimeDomainAllocations.

pusch-TimeDomainAllocation configures the time domain relationship between PDCCH and PUSCH. It consists of subfields such as K2 and startSymbolAndLength. K2 is the slot offset between DCI and scheduled PUSCH. startSymbolAndLength is an index indicating a valid combination of start symbol and length.

PUSCH-Config is used to configure UE-specific PUSCH parameters applicable to the initial BWP of the second cell.

It consists of the dataScramblingIdentityPUSCH field, pusch-PowerControl field, pusch-TimeDomainAllocationList field, mcs-Table field, and frequencyHopping field.

The dataScramblingIdentityPUSCH field represents an identifier used to initialize data scrambling (c_init) for PUSCH. If there is no field, the UE applies the physical cell ID.

The mcs-Table field indicates the MCS table that the UE will use for PUSCH. If there is no field, the UE applies the 64QAM value.

frequencyHopping indicates the frequency hopping method to be applied. The intraSlot value enables 'frequency hopping within a slot' and the interSlot value enables 'frequency hopping between slots'. Without a field, no frequency hopping is configured.

PUSCH-PowerControl is used to configure UE-specific power control parameters for PUSCH. It consists of the p0-AlphaSet field and the p0-NominalWithoutGrant field.

The p0-AlphaSets field includes multiple P0-PUSCH-AlphaSet IEs. P0-PUSCH-AlphaSet IE includes a p0-PUSCH-AlphaSetId field and a p0 field.

The p0 field indicates the P0 value for PUSCH with grants (excluding msg3) in 1dB units. When there is no field, the UE applies the value 0.

The p0-NominalWithoutGrant field indicates the P0 value for uplink grant-free PUSCH (configured grant-based PUSCH).

pucch-ConfigCommon is a cell-specific PUCCH parameter of the initial BWP of the second cell. It consists of subfields such as pucch-ResourceCommon, p0-norminal, etc.

pucch-ResourceCommon is an index corresponding to the parameter of the cell-specific PUCCH resource. One index corresponds to the PUCCH format, PUCCH time section, PUCCH frequency section, PUCCH code, etc.

p0-norminal is the power offset applied when transmitting PUCCH. It is defined as an integer between -202 and 24 that increases by 2. The unit is dBm.

pucch-ConfigCommon is used to configure UE-specific PUCCH parameters. It consists of fields such as the dl-DataToUL-ACK field and the resourceSetToAddModList field.

The dl-DataToUL-ACK field contains a timing list for the PDSCH given in DL ACK.

resourceSetToAddModList contains a list for adding a PUCCH resource set.

tdd-UL-DL-ConfigurationCommon is the cell-specific TDD UL/DL configuration. It consists of subfields such as referenceSubcarrierSpacing, pattern1, and pattern2.

referenceSubcarrierSpacing is a reference SCS used to determine time domain boundaries in UL-DL patterns.

pattern1 and pattern2 are TDD uplink and downlink patterns. It consists of subfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

dl-UL-TransmissionPeriodicity represents the period of the DL-UL pattern.

nrofDownlinkSlots indicates the number of consecutive full DL slots in each DL-UL pattern.

nrofDownlinkSymbols indicates the number of consecutive DL symbols from the start of the slot following the last full DL slot.

nrofUplinkSlots indicates the number of consecutive full UL slots in each DL-UL pattern.

nrofUplinkSymbols indicates the number of consecutive UL symbols at the end of the slot before the first full UL slot.

The operations of the terminal and base station are listed below.

Below, one or more means one or more.

The terminal transmits a UECapabilityInformation message to the base station.

The base station receives the UECapabilityInfomation message.

The UECapabilityInformation message includes 0 or 1 Capability_Information_1 (inactiveState), 0 or 1 Capability_Information_2 (ra-SDT), 0 or 1 Capability_Information_3 (srb-SDT), and 0 or more capability-information_4 (cg-SDT).

Capability_Information_1 is a terminal-specific function. Capability_Information_1 indicates whether the terminal supports RRC_INACTIVE. The presence of Capability_Information_1 indicates that the terminal supports RRC_INACTIVE.

Capability_Information_2 is a terminal-specific function. Capability_Information_2 indicates whether the terminal supports signaling and/or data transmission through a radio bearer allowed in RRC_INACTIVE state through a random access procedure. The presence of Capability_Information_2 indicates that the terminal supports transmission of data and/or signaling through a radio bearer allowed in RRC_INACTIVE state through a random access procedure.

Capability_Information_3 is a terminal-specific function. Capability_Information_3 indicates whether the terminal supports the use of signaling radio bearer SRB2 through RA-SDT or CG-SDT. The presence of Capability_Information_3 indicates that the terminal supports the use of signaling radio bearer SRB2 through RA-SDT or CG-SDT.

Capability_Information_4 is a band-specific function. Capability_Information_4 indicates whether the UE supports data transmission and/or signaling through a radio bearer allowed in RRC_INACTIVE state through the configured grant type 1. The presence of Capability_Information_4 for a band indicates that the terminal supports transmission of data and/or signaling through a radio bearer allowed in the RRC_INACTIVE state through grant type 1 configured in the corresponding band.

The terminal receives an RRCRlease message from the base station in the first cell.

The base station transmits an RRCRlease message to the terminal in the first cell.

RRCRlease contains 0 or 1 third search space. The third search space is associated with the second SDT procedure. The third search space is a UE-specific search space.

The RRCRlease message includes Configuration_Information_1_1 (sdt-Config). Configuration_Information_1_1(sdt-Config) is connected to Configuration_Information_1_2(sdt-DRB-List) and Configuration_Information_1_3(sdt-SRB2-Indication) and Configuration_Information_1_4(sdt-CG-Config) and Configuration_Information_1_5 (sdt-DRB-ContinueEHC-UL) and Configuration_Information_1_6 (sdt-DRB -ContinueEHC-DL) is included.

Configuration_Information_1_2(sdt-DRB-List) contains 0 or one or more DRB-Identities. Configuration_Information_1_2(sdt-DRB-List) represents the DRB configured for SDT.

Configuration_Information_1_3(sdt-SRB2-Indication) indicates whether SRB2 is configured for SDT.

Configuration_Information_1_4 (sdt-CG-Config) is a first Configuration_Information_1_4_1 (BWP-Uplink-Dedicated-SDT) and a second Configuration_Information_1_4_1 (BWP-Uplink-Dedicated-SDT) and Configuration_Information_1_4_3 (BWP-Downlink-In a Configuration_Information_1_4_ 3) and Configuration_Information_1_4_4 (cg- SDT-TimeAlignmentTimer) and Configuration_Information_1_4_5 (cg-SDT-RSRP-ThresholdSSB) and Configuration_Information_1_4_6 (C-RNTI) and Configuration_Information_1_4_7 (CS-RNTI).

Configuration_Information_1_5 (sdt-DRB-ContinueEHC-UL) in Configuration_Information_1_1 (sdt-Config) in RRCRlease determines whether the PDCP entity of the data radio bearer configured for SDT continues or resets the uplink EHC header compression protocol during PDCP reset during the SDT procedure in RRC_INACTIVE. Indicates whether or not.

Configuration_Information_1_6 (sdt-DRB-ContinueEHC-DL) in Configuration_Information_1_1 (sdt-Config) in RRCRlease determines whether the PDCP entity of the data radio bearer configured for SDT continues or resets the downlink EHC header compression protocol during PDCP reset during the SDT procedure in RRC_INACTIVE. Indicates whether or not.

Configuration_Information_1_5 (sdt-DRB-ContinueEHC-UL) of PDCP-Config in RRCReconfiguration indicates whether the PDCP entity of the corresponding DRB continues or resets the uplink EHC header compression protocol during PDCP reset in RRC_CONNECTED.

Configuration_Information_1_6 (sdt-DRB-ContinueEHC-DL) in PDCP-Config of RRCReconfiguration indicates whether the PDCP entity of the corresponding DRB continues or resets the downlink EHC header compression protocol during PDCP reset in RRC_CONNECTED.

Configuration_Information_1_4 (sdt-MAC-PHY-CG-Config) is used for the second SDT (CG-SDT).

Configuration_Information_1_2 (sdt-DRB-List), Configuration_Information_1_3 (sdt-SRB2-Indication), and Configuration_Information_1_5 (sdt-DRB-ContinueEHC) are used in both the first SDT (RA-SDT) and the second SDT (CG-SDT).

Configuration_Information_1_4_1 (BWP-Uplink-Dedicated-SDT) contains zero or one Configuration_Information_1_4_1_1 (PUSCH-Config) and one or more Configuration_Information_1_4_1_2 (ConfiguredGrantConfig).

Configuration_Information_1_4_1_1 (PUSCH-Config) is used to configure terminal-specific PUSCH parameters. Configuration_Information_1_4_1_1(PUSCH-Config) contains 0 or 1 Configuration_Information_1_4_1_1_1(PUSCH-TimeDomainAllocationList).

Configuration_Information_1_4_1_1_1(PUSCH-TimeDomainAllocationList) is used to configure the time domain relationship between PDCCH and PUSCH.

Configuration_Information_1_4_1_1_1(PUSCH-TimeDomainAllocationList) consists of one or more PUSCH-TimeDomainResourceAllocations.

PUSCH-TimeDomainResourceAllocation consists of k2 and startsSymbolAndLength.

k2 is the number of symbols and represents the distance between PDCCH and PUSCH.

startsSymbolAndLength indicates the index of the start symbol and length.

Configuring_Information_1_4_1_2(ConfiguredGrantConfig) is used to configure uplink transmission without dynamic grant.

Configuration_Information_1_4_1_2 (ConfiguredGrantConfig) configureGrantTimer (indicates the initial value of the configured grant timer in multiples of the period) and frequencyDomainAllocation (indicates frequency domain resource allocation) and period (period for UL transmission without UL grant) and timeDomainAllocation (start symbol and length and PUSCH represents the combination of mapping types) and sdt-P0-PUSCH (represents the P0 value for PUSCH for CG SDT in 1 dB units) and sdt-Alpha (represents the alpha value for PUSCH for CG SDT) and ConfiguredGrantConfigIndex (BWP It is composed of (representing the index of the Configured Grant configuration within).

The UE selects one of a plurality of Configuration_Information_1_4_1_2 for transmission of the first uplink MAC PDU when the second SDT is triggered.

Configuration_Information_1_4_3 (BWP-Downlink-Dedicated-SDT) consists of PDCCH-config and PDSCH-config.

PDCCH-config is used to configure UE-specific PDCCH parameters such as control resource set and search space. PDCCH-config of Configuration_Information_1_4_3 (BWP-Downlink-Dedicated-SDT) may include sdt-cg-searchSpace.

sdt-cg-searchSpace is controlled by controlResourceSetId (represents the CORESET applicable to this SearchSpace), monitoringSlotPeriodicityAndOffset (represents the slot for PDCCH monitoring consisting of period and offset) and duration (represents the number of consecutive slots for which the SearchSpace will last) and duration (indicates the number of consecutive slots for which the SearchSpace lasts in all opportunities) and searchSpaceType (indicates whether the search space is a common search space or a ue-specific search space).

searchSpoaceType for sdt-cg-searchSpace represents a ue specific search space.

Configuration_Information_1_4_4(cg-SDT-TimeAlignmentTimer) represents the TimeAlignmentTimer value for CG-SDT.

Configuration_Information_1_4_5(cg-SDT-RSRP-ThresholdSSB) indicates the RSRP threshold configured for SSB selection for CG-SDT.

Configuration_Information_1_4_6 (C-RNTI) represents the C-RNTI to be used in the first SDT procedure and the second SDT procedure. Corresponds to the third identifier.

Configuration_Information_1_4_7 (CS-RNTI) indicates the CS-RNTI to be used in the second SDT procedure. Corresponds to the fourth identifier.

The first bearer group (radio bearers configured for SDT), the second bearer group (radio bearers configured for SDT except SRB1) and the third bearer group (data radio bearers configured for SDT except SRB1 and SRB2) are configured in Configuration_Information_1_2 ( sdt-DRB-List) and Configuration_Information_1_3 (sdt-SRB2-Indication).

The third bearer group is determined based at least in part on Configuration_Information_1_2 (sdt-DRB-List).

The second bearer group is determined based at least in part on Configuration_Information_1_2 (sdt-DRB-List) and Configuration_Information_1_3 (sdt-SRB2-Indication).

The first bearer group is determined based at least in part on Configuration_Information_1_2 (sdt-DRB-List) and Configuration_Information_1_3 (sdt-SRB2-Indication).

The RLC entity of SRB2 is reset when Configuration_Information_1_3 (sdt-SRB2-Indication) is included in the RRCRlease message.

The first PDCP operation (SDU discard operation) on the PDCP entity of SRB2 is performed when Configuration_Information_1_3 (sdt-SRB2-Indication) is included in the RRCRlease message.

The RLC entity of SRB1 is reset.

The terminal triggers the PDCP entity of SRB1 to discard all stored PDCP SDUs and PDCP PDUs.

If sdt-SRB2-Indication is configured in sdt-Config of RRCRlease, the UE triggers the PDCP entity of SRB2 to discard all PDCP SDUs and PDCP PDUs stored.

The terminal performs cell selection and selects the second cell.

The terminal receives SIB1 from the base station in the second cell.

The base station transmits SIB1 in the second cell.

SIB1 includes 1 or 2 first search spaces and 0 or 1 second search spaces. Each of the first search spaces is associated with a regular uplink carrier or an additional uplink carrier. The first search space is associated with the random access procedure and the second search space is associated with the SDT procedure. The first search space and the second search space are a common search space.

SIB1 includes Configuration_Information_2_1 (sdt-ConfigCommon) and Configuration_Information_2_2 (ServingCellConfigCommonSIB).

Configuration_Information_2_1(sdt-ConfigCommon) includes Configuration_Information_2_1_1(sdt-RSRP-Threshold) and Configuration_Information_2_1_2(sdt-DataVolumeThreshold) and Configuration_Information_2_1_3(t319a).

Configuration_Information_2_1_1 (sdt-RSRP-Threshold) indicates the RSRP threshold for determining whether the UE will perform the SDT procedure.

Configuration_Information_2_1_2(sdt-DataVolumeThreshold) represents the data volume threshold used to determine whether SDT can be started.

Configuration_Information_2_2 (ServingCellConfigCommonSIB) includes Configuration_Information_2_2_1 (DownlinkConfigCommonSIB), a first Configuration_Information_2_2_2 (UplinkConfigCommonSIB of NUL), and a second Configuration_Information_2_2_2 (UplinkConfigCommonSIB of SUL).

Configuration_Information_2_2_1(DownlinkConfigCommonSIB) includes Configuration_Information_2_2_1_1(BWP-DownlinkCommon). Configuration_Information_2_2_1_1 (BWP-DownlinkCommon) includes Configuration_Information_2_2_1_1_1 (PDCCH-ConfigCommon) and Configuration_Information_2_2_1_1_2 (PDSCH-ConfigCommon).

Configuration_Information_2_2_1_1_1 (PDCCH-ConfigCommon) includes Configuration_Information_2_2_1_1_1_1 (ra-SearchSpace) and Configuration_Information_2_2_1_1_1_2 (sdt-SearchSpace).

Configuration_Information_2_2_1_1_1_1(ra-SearchSpace) represents the ID of the search space for the random access procedure.

Configuration_Information_2_2_1_1_1_2(sdt-SearchSpace) includes configuration information of a common search space for the first SDT procedure and the second SDT procedure.

sdt-SearchSpace consists of controlResourceSetId (represents the CORESET applicable to this SearchSpace), monitoringSlotPeriodicityAndOffset (represents the slot for PDCCH monitoring, consisting of period and offset), and period (represents the number of consecutive slots that the SearchSpace will last at every opportunity). do. ) and searchSpaceType (indicating whether the search space is a common search space or a ue-specific search space).

searchSpoaceType for sdt-searchSpace represents a common search space.

Configuration_Information_2_2_1_1_2(PDSCH-ConfigCommon) includes Configuration_Information_2_2_1_1_2_1(PDSCH-TimeDomainResourceAllocationList).

Configuration_Information_2_2_1_1_2_1(PDSCH-TimeDomainResourceAllocationList) is used to configure the time domain relationship between PDCCH and PDSCH.

Configuration_Information_2_2_1_1_2_1(PDSCH-TimeDomainResourceAllocationList) consists of one or more PDSCH-TimeDomainResourceAllocation.

PUSCH-TimeDomainResourceAllocation consists of k0 and startsSymbolAndLength.

k0 represents the distance between PDCCH and PDSCH by the number of symbols.

startsSymbolAndLength indicates the index of the start symbol and length.

Configuration_Information_2_2_2(UplinkConfigCommonSIB) includes Configuration_Information_2_2_2_1(BWP-UplinkCommon).

Configuration_Information_2_2_2_1 (BWP-UplinkCommon) includes one or more Configuration_Information_2_2_2_1_1 (RACH-ConfigCommon) and Configuration_Information_2_2_2_1_2 (PUSCH-ConfigCommon).

One or more Configuration_Information_2_2_2_1_1 (RACH-ConfigCommon) each containing Configuration_Information_2_2_2_1_1_1 (rsrp-ThresholdSSB-SUL used for uplink carrier selection) and one or more Configuration_Information_2_2_2_1_1_2 (_1S_Information_Information used for SSBrp-Threshold) _2_2_2_1_1_2) and Configuration_Information_2_2_2_1_1_3 (bit unit for RACH preamble group selection Msg3SizeGroupA representing the transport block size threshold) and Configuration_Information_2_2_2_1_1_4 (preambleReceivedTargetPower representing the target power level at the network receiver side) and Configuration_Information_2_2_2_1_1_5 (powerRampingStep for PRACH) and Configuration_Information_2_2_2_1_1_6 (representing the PRACH configuration) -ConfigurationIndex) and Configuration_Information_2_2_2_1_1_7 (RAR window length ra-ResponseWindow, indicating the number of slots) and Configuration_Information_2_2_2_1_1_8 (ContentionResolutionTimer, indicating the initial value for the contention resolution timer) and 0 or more Configuration_Information_2_2_2_1_1_9 (featureCombination) and 0 or more Configuration_Information_2_2_2_1_1_A (threshold for preamble selection) messagePowerOffsetGroupB) with a value of 0 or Contains one or more Configuration_Information_2_2_2_1_1_B (deltaPreamble indicating power offset between msg3 and RACH preamble transmission).

Configuration_Information_2_2_2_1_1_9(featureCombination) represents the combination of features to be associated with the random access partition (or RACH-ConfigCommon). featureCombination is redCap (if present, this field indicates that RedCap is part of this feature combination) and smallData (if present, this field indicates that Small Data is part of this feature combination) and sliceGroup (if present, this field indicates that Small Data is part of this feature combination) (indicates the slice group that is part of the feature combination) and covEnh (if present, this field indicates that the coverage enhancement is part of this feature combination).

Configuration_Information_2_2_2_1_2(PUSCH-ConfigCommon) includes Configuration_Information_2_2_2_1_2_1(pusch-TimeDomainAllocationList) and Configuration_Information_2_2_2_1_2_2(msg3-DeltaPreamble).

Configuration_Information_2_2_2_1_2_1 is used to configure the time domain relationship between PDCCH and PUSCH.

Configuration_Information_2_2_2_1_2_1 consists of one or more PUSCH-TimeDomainResourceAllocation.

PUSCH-TimeDomainResourceAllocation consists of k2 and startsSymbolAndLength.

k2 is the number of symbols and represents the distance between PDCCH and PUSCH.

startsSymbolAndLength indicates the index of the start symbol and length.

Configuration_Information_2_2_2_1_2_2(msg3-DeltaPreamble) indicates the power offset between msg3 and RACH preamble transmission.

The default RACH-ConfigCommon is the RACH-ConfigCommon located first among the plurality of RACH-Configcommons in the BWP-UplinkCommon of the selected uplink carrier. Configuration_Information_2_2_2_1_1_9(featureCombination) is not included in the default RACH-Configcommon.

SIB1 includes a PUSCH-ConfigCommand and one or more RACH-ConfigCommon for the first uplink and a PUSCH-ConfigCommon and one or more RACH-ConfigCommon for the second uplink.

SIB1 includes T319a.

Each RACH-ConfigCommon includes rsrp-ThresholdSSB-SUL and Contention-ResolutionTimer.

The terminal decides to start the first SDT procedure or the second SDT procedure in the second cell.

The terminal is connected to sdt-RSRP-Threshold and sdt-DataVolumeThreshold of Configuration_Information_2_1 (sdt-ConfigCommon) of SIB1 received from the second cell and cg-SDT-RSRP-ThresholdSSB of Configuration_Information_1_1 (sdt-Config) of RRCRlease received from the first cell. Based, at least in part, on the decision to begin the SDT procedure.

The first cell and the second cell are different cells.

The terminal is based at least in part on the first rsrp threshold (sdt-RSRP-Threshold) of SIB1 received in the second cell and the second threshold of RRCRelease (cg-SDT-RSRP -ThresholdSSB) received in the first cell. It is decided to initiate the second SDT procedure.

The UE determines to initiate a second SDT procedure based at least in part on the fact that the BWP-Uplink-Dedicated-SDT for the selected uplink carrier is included in the sdt-Config of RRCRlease.

The first preset PDCP configuration and the first preset RLC configuration and the first preset logical channel configuration1 and the first preset logical channel configuration2 are applied to SRB1.

The BSR configuration of the first default and the PHR configuration of the first default are applied.

The PDCP entity for SRB1 is reset.

SRB1 resumes.

The UE restores the PDCP configuration and RLC configuration of the radio bearer of the second radio bearer group from the UE Inactive AS Context.

The terminal restores the stored logical channel configuration 2 of the radio bearer of the third radio bearer group from the UE Inactive AS Context.

The second logical channel configuration 1 and the predefined first logical channel configuration 2 are applied to SRB2.

The third predefined logical channel configuration 1 is applied to radio bearers of the third radio bearer group.

The PDCP entity for the radio bearer of the second radio bearer group is reset without triggering a PDCP status report.

If drb-ContinueEHC is not included in RRCRlease's sdt-Config, the terminal resets the EHC protocol for the radio bearer of the third radio bearer group.

If drb-ContinueEHC-UL is not configured in sdt-Config of RRCRlease, the terminal resets the uplink EHC protocol for uplink for one or more DRBs configured for SDT.

If drb-ContinueEHC-DL is not configured in sdt-Config of RRCRlease, the terminal resets the downlink EHC protocol for downlink for one or more DRBs configured for SDT.

The radio bearer of the second radio bearer group is resumed.

The first and second variables of the PDCP entity of SRB1 are set to 0, and if SRB2 is configured for SDT, the first and second variables of the PDCP entity of SRB2 are set to 0.

The first variable represents the COUNT value of the next PDCP SDU to be transmitted. The initial value is 0.

The second variable represents the COUNT value of the next PDCP SDU expected to be received. The initial value is 0.

If the first default PDCP configuration is applied, the reorder timer is set to infinite and the sequence number field is set to 12 bits.

If the first default RLC configuration is applied, the reassembly timer is set to the first value and the sequence number field is indicated with 12 bits.

If the predefined first logical channel configuration 2 is applied, ConfiguredGrantType1Allowed is set to allow and allowedCG-List is set to absent.

The priority value of the first predefined logical channel configuration 1 is lower than the priority value of the second predefined logical channel configuration 1. The priority value of the second predefined logical channel configuration 1 is lower than the priority value of the third predefined logical channel configuration 1.

The PrioritisedBitRate value of the first predefined logical channel configuration 1 is the same as the PrioritisedBitRate value of the second predefined logical channel configuration 1. The priorityedBitRate value of the second predefined logical channel configuration 1 is greater than the priorityedBitRate value of the third predefined logical channel configuration 1.

The logicalChannelGroup value of the first predefined logical channel configuration 1 is the same as the logicalChannelGroup value of the second predefined logical channel configuration 1. The logicalChannelGroup value of the second predefined logical channel configuration 1 is different from the logicalChannelGroup value of the third predefined logical channel configuration 1.

When the first default BSR configuration is applied, periodBSR-Timer is set to a first value and retxBSR-Timer is set to a second value.

If the first default PHR configuration is applied, multiplePHR is set to false.

The terminal selects an uplink carrier based at least in part on a specific rsrp-ThresholdSSB-SUL among a plurality of rsrp-ThresholdSSB-SUL. The specific rsrp-ThresholdSSB-SUL is included in the first RACH-ConfigCommon IE among the plurality of RACH-ConfigCommon IEs for the first uplink.

The uplink carrier is selected based at least in part on a specific rsrp-ThresholdSSB-SUL.

The terminal selects a RACH-ConfigCommon IE for RA-SDT from a plurality of RACH-ConfigCommon IEs of the selected uplink carrier.

Among the plurality of RACH-ConfigCommon IEs of the selected uplink carrier, one RACH-ConfigCommon IE is selected for RA-SDT.

The terminal selects the SSB based at least in part on rsrp-ThresholdSSB. rsrp-ThresholdSSB is included in the selected RACH-ConfigCommon of the selected uplink carrier.

The SSB is selected based at least in part on rsrp-ThresholdSSB. rsrp-ThresholdSSB is included in the selected RACH-ConfigCommon of the selected uplink carrier.

When the default RACH-ConfigCommon is selected, the terminal selects a preamble group based at least in part on the selected RACH-ConfigCommon of the selected uplink and the PUSCH-ConfigCommon of the selected uplink.

When RACH-ConfigCommon-fc is selected, the terminal selects a preamble group based at least in part on the selected RACH-ConfigCommon of the selected uplink.

If the selected RACH-ConfigCommon of the selected carrier does not include a deltaPreamble, the preamble group is selected based at least in part on preambleReceivedTargetPower in the selected RACH-ConfigCommon of the selected uplink carrier and msg3-DeltaPreamble in the PUSCH-ConfigCommon of the selected uplink carrier.

If the selected RACH-ConfigCommon of the selected uplink carrier includes deltaPreamble, the preamble group is selected based at least in part on preambleReceivedTargetPower and deltaPreamble of the selected RACH-ConfigCommon of the selected uplink carrier.

The terminal transmits a preamble to the base station based at least in part on the transmission power-related parameters of the selected RACH-ConfigCommon of the selected uplink carrier.

The base station receives a preamble from the terminal based at least in part on transmission power-related parameters in the selected RACH-ConfigCommon of the selected uplink carrier.

The terminal receives RAR from the base station in response to the transmitted preamble.

The base station transmits RAR to the terminal in response to the received preamble.

The terminal determines the time domain relationship based at least in part on the time resource allocation field of the RAR and the pusch-TimeDomainResourceAllocationList of the PUSCH-ConfigCommon of the selected uplink carrier when the PUSCH-ConfigCommon of the selected uplink carrier includes pusch-TimeDomainResourceAllocationList.

If the PUSCH-ConfigCommon of the selected uplink carrier does not include pusch-TimeDomainResourceAllocationList, the terminal determines the time domain relationship based at least in part on the time resource allocation field of the RAR and the subcarrier spacing of the initial uplink BWP of the selected uplink carrier. .

The time domain relationship is determined based at least in part on the time resource allocation field of the RAR and the pusch-TimeDomainResourceAllocationList of the PUSCH-ConfigCommon of the selected uplink carrier if the PUSCH-ConfigCommon of the selected uplink carrier includes pusch-TimeDomainResourceAllocationList.

The time domain relationship is determined based at least in part on the subcarrier spacing of the initial uplink BWP of the selected uplink carrier and the time resource allocation field of the RAR if the selected uplink carrier's PUSCH-ConfigCommon does not include pusch-TimeDomainResourceAllocationList.

The terminal determines the time domain relationship.

When the default RACH-ConfigCommon is selected, the terminal determines the transmission power based at least in part on the selected RACH-ConfigCommon of the selected uplink and the PUSCH-ConfigCommon of the selected uplink.

When RACH-ConfigCommon-fc is selected, the terminal determines transmission power based at least in part on the selected RACH-ConfigCommon of the selected uplink.

The terminal transmits the first uplink MAC PDU to the base station based at least in part on the determined time relationship and the determined transmit power.

The base station receives the first uplink MAC PDU from the terminal based at least in part on the determined time relationship and the determined transmit power.

The first uplink MAC PDU includes a first CCCH SDU and optionally a BSR and optionally a PHR and optionally a MAC SDU from a third radio bearer group. The first CCCH SDU is RRCResumeRequest.

The UE receives DCI on the PDCCH addressed by the temporary C-RNTI. DCI includes a time domain resource allocation field.

The base station transmits DCI on the PDCCH addressed by the temporary C-RNTI. DCI includes a time domain resource allocation field.

The terminal determines the time domain relationship based at least in part on the time resource allocation field of the DCI and the pdsch-TimeDomainResourceAllocationList of the PDSCH-ConfigCommon when the PDSCH-ConfigCommon includes the pdsch-TimeDomainResourceAllocationList.

The terminal determines the time domain relationship based at least in part on the time resource allocation field of the DCI and the default time resource allocation table when PDSCH-ConfigCommon does not include pdsch-TimeDomainResourceAllocationList.

The default time resource allocation table consists of a plurality of fixed values.

The time domain relationship is determined based at least in part on the time resource allocation field of the DCI and the pdsch-TimeDomainResourceAllocationList of the PDSCH-ConfigCommon if the PDSCH-ConfigCommon includes a pdsch-TimeDomainResourceAllocationList.

If PDSCH-ConfigCommon does not include pdsch-TimeDomainResourceAllocationList, the time domain relationship is determined based at least in part on the DCI's time resource allocation field and the default time resource allocation table.

The default time resource allocation table consists of a plurality of fixed values. Each fixed value is the same or different from each other.

The terminal receives the second downlink MAC PDU (Msg 4) from the base station based at least in part on the determined time relationship.

The base station transmits the second downlink MAC PDU (Msg 4) to the terminal based at least in part on the determined time relationship.

The UE receives DCI from the PDCCH addressed by the C-RNTI. DCI includes a time domain resource allocation field for uplink grant.

The base station transmits DCI on the PDCCH addressed by the C-RNTI. DCI includes a time domain resource allocation field for uplink grant.

When the PUSCH-ConfigCommon of the first uplink carrier includes pusch-TimeDomainResourceAllocationList, the terminal establishes a time domain relationship based at least in part on the time resource allocation field of the DCI and the pusch-TimeDomainResourceAllocationList of the PUSCH-ConfigCommon of the first uplink carrier. decide

If the PUSCH-ConfigCommon of the first uplink carrier does not include the pusch-TimeDomainResourceAllocationList, the terminal establishes a time domain relationship based at least in part on the time resource allocation field of the DCI and the subcarrier spacing of the initial uplink BWP of the first uplink carrier. Decide.

The first uplink carrier is the uplink carrier selected for initial PUSCH transmission for RA-SDT.

When the default RACH-ConfigCommon is the 1st RACH-ConfigCommon, the terminal determines the transmission power based at least in part on the 1st RACH-ConfigCommon of the first uplink carrier and the PUSCH-ConfigCommon of the first uplink carrier.

When RACH-ConfigCommon-fc is the first RACH-ConfigCommon, the terminal determines the transmission power based at least in part on the first RACH-ConfigCommon of the first uplink carrier.

The first RACH-ConfigCommon is the RACH-ConfigCommon used for initial PUSCH transmission for RA-SDT.

The terminal transmits the second uplink MAC PDU to the base station based at least in part on the determined time relationship and the determined transmit power.

The first uplink MAC PDU includes a CCCH SDU, and the second uplink MAC PDU does not include a CCCH SDU.

The UE determines the transmission power based at least in part on sdt-P0-PUSCH and sdt-Alpha in the first configured GrantConfig of BWP-Uplink-Dedicated-SDT in RRCRlease.

The first ConfiguredGrantConfig is one of multiple configuredGrantConfigs in BWP-Uplink-Dedicated-SDT of RRCRlease.

If the ConfiguredGrantConfig has the earliest configured grant for data from a radio bearer configured for SDT, then that configured GrantConfig is selected as the first configured GrantConfig.

The terminal transmits the first uplink MAC PDU to the base station based at least in part on the determined transmission power.

If a downlink assignment is received on the PDCCH for the C-RNTI and this is the first downlink assignment after the initial transmission to the CG-SDT with a CCCH message, the initial PUSCH transmission to the CG-SDT is terminated and the subsequent PUSCH to the CG-SDT Transmission begins.

The UE monitors the PDCCH for the CSS configured by ra-SearchSpace for the DCI with the CRC scrambled by the first identifier (RA-RNTI) during the first period of the first SDT procedure.

The UE monitors the PDCCH for the CSS configured by sdt-SearchSpace for the DCI with a CRC scrambled by the second identifier (implicit C-RNTI) during the second period of the first SDT procedure.

The UE configures the PDCCH for the USS by sdt-cg-SearchSpace for the DCI with a CRC scrambled by the third or fourth identifier (explicit C-RNTI or explicit CS-RNTI, respectively) during the second SDT procedure. monitor.

(Or) The terminal monitors the PDCCH for the CSS configured by sdt-SearchSpace for the DCI with a CRC scrambled by the third identifier or fourth identifier during the second SDT procedure.

The base station transmits the PDCCH for the CSS configured by ra-SearchSpace for the DCI with a CRC scrambled by the first identifier (RA-RNTI) during the first period of the first SDT procedure.

The base station transmits the PDCCH for CSS configured by sdt-SearchSpace for the DCI with a CRC scrambled by the second identifier (implicit C-RNTI) during the second period of the first SDT procedure.

The base station transmits for the USS configured by sdt-cg-SearchSpace for the DCI with a CRC scrambled by the third or fourth identifier (explicit C-RNTI or explicit CS-RNTI, respectively) during the second SDT procedure. do.

(Or) The base station transmits the PDCCH for CSS configured by sdt-SearchSpace for the DCI with a CRC scrambled by the third identifier or fourth identifier during the second SDT procedure.

When the first SDT procedure is performed, the UE monitors the PDCCH for the CSS configured by sdt-SearchSpace for the DCI with a CRC scrambled by the second identifier (implicit C-RNTI).

When the second SDT procedure is performed, the UE transmits the PDCCH for the CSS configured by sdt-SearchSpace for the DCI with a CRC scrambled by the third identifier (explicit C-RNTI) or fourth identifier (explicit CS-RNTI). Monitor.

The base station transmits the PDCCH for the CSS configured by sdt-SearchSpace for the DCI with a CRC scrambled by the second identifier (implicit C-RNTI) when the first SDT procedure is performed.

When the second SDT procedure is performed, the base station transmits the PDCCH for CSS configured by sdt-SearchSpace for DCI with a CRC scrambled by the third identifier (explicit C-RNTI) or fourth identifier (explicit CS-RNTI). do.

ra-SearchSpace and sdt-SearchSpace are displayed/included in PDCCH-ConfigCommon of SIB1 received in the second cell.

sdt-cg-SearchSpace is displayed/included in the RRCRlease message received in the first cell.

During the first period, initial PUSCH transmission for CCCH messages is performed based at least in part on a random access procedure. Subsequent PUSCH transmissions during the second period are performed based at least in part on the dynamic uplink grant.

sdt-SearchSpace is displayed in PDCCH-ConfigCommon of SIB1 received in the second cell.

sdt-cg-SearchSpace is indicated in the RRCRlease message received in the first cell.

The first identifier (RA-RNTI) is common for multiple terminals and has a fixed value. The second identifier (C-RNTI) is unique to the terminal and is assigned by RAR. The third identifier (C-RNTI) is unique to the terminal and is assigned in the RRCRlease message. The fourth identifier (CS-RNTI) is unique to the terminal and is assigned in the RRCRlease message. The second and third identifiers are used for dynamic scheduling. The fourth identifier is used for Semi-Persistent Scheduling.

When the first SDT procedure starts, the terminal starts Contention-ResolutionTimer when the first uplink MAC PDU is transmitted.

The first uplink MAC PDU includes a CCCH SDU and optionally a MAC SDU from a radio bearer configured for the first BSR and optionally the first PHR and optionally the SDT.

The UE stops ContentionResolutionTimer when the PDCCH addressed to the second identifier (TC-RNTI) is received during the first SDT procedure.

If the ContentionResolutionTimer expires during the first SDT procedure, the terminal considers the SDT procedure to be unsuccessful. If the SDT procedure is not successful, the terminal performs the task of moving to RRC_IDLE.

ContentionResolutionTimer is displayed in the corresponding field of the selected RACH-ConfigCommon of the uplink carrier selected in SIB1 received in the second cell.

When the second SDT procedure starts, the terminal starts configureGrantTimer when the first uplink MAC PDU is transmitted.

The UE stops ConfiguredGrantTimer when the PDCCH addressed to the third identifier (C-RNTI) is received during the second SDT procedure.

The terminal considers the procedure to be unsuccessful if configureGrantTimer expires during the second SDT procedure. If the SDT procedure is not successful, the terminal performs the task of moving to RRC_IDLE.

ConfiguredGrantTimer is displayed in the corresponding field of BWP-Uplink-Dedicated-SDT of the uplink selected in sdt-Config of RRCRlease.

The terminal starts the T319a timer when the SDT procedure starts. The terminal restarts T319a when it receives a MAC SDU or transmits a MAC SDU during the SDT procedure. The terminal performs the task of moving to RRC_IDLE when T319a expires. The terminal stops T319a when RRCRlease or RRCReject or RRCResume or RRCSetup is received.

The T319a timer is displayed in the corresponding field in sdt-ConfigCommon of SIB1 received from the second cell.

Contention-ResolutionTimer starts when the first uplink MAC PDU is received when the first SDT procedure starts.

The first uplink MAC PDU includes a CCCH SDU and optionally a MAC SDU from a radio bearer configured for the first BSR and optionally the first PHR and optionally the SDT.

ContentionResolutionTimer is stopped when the PDCCH addressed to the second identifier (TC-RNTI) is received during the first SDT procedure.

If ContentionResolutionTimer expires during the first SDT procedure, the SDT procedure fails.

ContentionResolutionTimer is displayed in the corresponding field of the selected RACH-ConfigCommon of the uplink carrier selected in SIB1 received in the second cell.

ConfiguredGrantTimer starts when the first uplink MAC PDU is transmitted when the second SDT procedure starts.

The ConfiguredGrantTimer is stopped when the PDCCH addressed to the third identifier (C-RNTI) is received during the second SDT procedure.

If configureGrantTimer expires during the second SDT procedure, the procedure fails.

ConfiguredGrantTimer is displayed in the corresponding field of BWP-Uplink-Dedicated-SDT of the uplink selected in sdt-Config of RRCRlease.

The T319a timer starts when the SDT procedure begins. T319a is restarted when receiving a MAC SDU or transmitting a MAC SDU during the SDT procedure. The operation when switching to RRC_IDLE is performed when T319a expires. T319a stops when RRCRlease or RRCReject or RRCResume or RRCSetup is sent.

The T319a timer is indicated in the corresponding field of sdt-ConfigCommon of SIB1 received from the second cell.

One or more ContentionResolutionTimer fields and one T319a field are included in SIB1, and one or more ContentionResolutionTimer fields are included in RRCRelease.

The tasks when moving to RRC_IDLE include releasing SDT-config, stopping the first timer, discarding the second identifier (implicit C-RNTI) and third identifier (explicit C-RNTI) and entering RRC_IDLE.

The first timer includes Contention-ResolutionTimer and ConfiguredGrantTimer.

The terminal transmits the first uplink MAC PDU to the base station based at least in part on the determined time relationship and the determined transmit power.

The base station receives the first uplink MAC PDU from the terminal based at least in part on the determined time relationship and the determined transmit power.

The first uplink MAC PDU includes a first CCCH SDU and optionally a first BSR and optionally a first PHR from a third radio bearer group and optionally a MAC SDU.

The format of the first PHR is determined based at least in part on a predefined first PHR configuration.

There is an ongoing SDT procedure and the UL grant in the RAR can accommodate all pending data available for transmission and the 1st BSR MAC CE and its subheaders, but cannot accommodate additional 1st PHR MAC CE and its subheaders. If it is not sufficient, the first PHR is canceled.

RRCRlease includes PUSCH-Config and one or more ConfiguredGrantConfig for a first uplink carrier and PUSCH-Config and one or more ConfiguredGrantConfig for a second uplink carrier.

The UE triggers the PDCP entity of SRB2 to discard all stored PDCP SDUs and PDCP PDUs if RRCRlease is received and sdt-SRB2-Indication is configured.

When SDT is started and SRB2 is configured for SDT, the first and second variables of SRB2's PDCP entity are set to 0.

The first variable represents the COUNT value of the next PDCP SDU to be transmitted, and the second variable represents the COUNT value of the next PDCP SDU to be received.

RRCRlease contains 0 or 1 DRB-ContinueEHC-UL and 0 or 1 DRB-ContinueEHC-DL.

DRB-ContinueEHC-UL in sdt-Config of RRCRlease indicates whether one or more PDCP entities in the DRB configured for SDT continue or reset the uplink EHC header compression protocol during PDCP reset in the SDT procedure of RRC_INACTIVE.

DRB-ContinueEHC-DL in sdt-Config of RRCRlease indicates whether one or more PDCP entities in the DRB configured for SDT continue or reset the downlink EHC header compression protocol during PDCP reset in the SDT procedure of RRC_INACTIVE.

DRB-ContinueEHC-UL in PDCP-Config of RRCReconfiguration indicates whether the PDCP entity of the corresponding DRB continues or resets the uplink EHC header compression protocol during PDCP reset in RRC_CONNECTED.

DRB-ContinueEHC-DL in PDCP-Config of RRCReconfiguration indicates whether the PDCP entity of the corresponding DRB continues or resets the downlink EHC header compression protocol during PDCP reset in RRC_CONNECTED.

The terminal determines that SRB2 is configured for SDT if sdt-SRB2-Indication is included in sdt-Config of RRCRlease.

The terminal determines that a DRB is configured for SDT if the corresponding DRB-Identity is included in the sdt-DRB-List in sdt-Config of RRCRlease.

The first uplink carrier is a normal uplink (NUL) and the second uplink carrier is a supplementary uplink carrier (SUL).

The first SDT procedure begins with transmission over the RACH and continues transmission based at least in part on dynamic scheduling.

The second SDT procedure begins with transmission over a Type 1 CG resource and continues transmission based at least in part on dynamic scheduling or based at least in part on configured grants.

The terminal performs PUSCH transmission based at least in part on the determined time domain relationship.

The base station performs PUSCH reception based at least in part on the determined time domain relationship.

If the selected RACH-ConfigCommon does not include deltaPreamble, the terminal selects a preamble group based at least in part on preambleReceivedTargetPower of the selected RACH-ConfigCommon of the selected uplink carrier and msg3-DeltaPreamble of the PUSCH-ConfigCommon of the selected uplink carrier.

If the selected RACH-ConfigCommon includes deltaPreamble, the terminal selects a preamble group based at least in part on preambleReceivedTargetPower and deltaPreamble of the selected RACH-ConfigCommon of the selected uplink carrier.

The terminal starts transmitting a UEAssistanceInformation message to provide nonSDT-DataIndication when data and/or signaling mapped to a radio bearer not configured for SDT become available during the first SDT procedure or the second SDT procedure.

nonSDT-DataIndication contains an IE indicating the cause value.

The terminal transmits the fourth uplink MAC PDU based at least in part on the determined transmission power. The fourth uplink MAC PDU includes UEAssistanceInformation (DCCH/SRB1 SDU).

The base station receives the fourth uplink MAC PDU based at least in part on the determined transmit power. The fourth uplink MAC PDU includes UEAssistanceInformation (DCCH/SRB1 SDU).

When the first SDT is performed, the uplink transmit power of the fourth uplink MAC PDU is determined based at least in part on preambleReceivedTargetPower and delta in the first RACH-ConfigCommon of the first uplink carrier.

If deltaPreamble is included in the first RACH-ConfigCommon of the first uplink carrier, delta is deltaPreamble in the first RACH-ConfigCommon of the first uplink carrier.

If deltaPreamble is not included in the first RACH-ConfigCommon of the first uplink carrier, delta is msg3-DeltaPreamble in the PUSCH-ConfigCommon of the first uplink carrier.

The first RACH-ConfigCommon is a RACH-ConfigCommon used (or selected) for initial PUSCH transmission for RA-SDT (or first uplink MAC PDU including CCCH/SRB0 SDU).

The first uplink carrier is an uplink carrier used (or selected) for initial PUSCH transmission for RA-SDT (or first uplink MAC PDU including CCCH/SRB0 SDU).

The uplink transmit power of the fourth uplink MAC PDU is at least partially dependent on p0-NominalWithoutGrant in the PUSCH-Config of the selected uplink carrier and sdt-P0-PUSCH in the ConfiguredGrantConfig of the configured grant used in the fourth uplink MAC PDU. It is decided based on

p0-NominalWithoutGrant is an offset for PUSCH transmission without an uplink grant.

The first RACH-ConfigCommon is the RACH-ConfigCommon used (or selected) in the initial PUSCH transmission for RA-SDT (or the first uplink MAC PDU including CCCH/SRB0 SDU).

The first uplink carrier is an uplink carrier used (or selected) for initial PUSCH transmission for RA-SDT (or first uplink MAC PDU including CCCH/SRB0 SDU).

The first uplink carrier is an uplink carrier indicated by a UL/SUL indicator in DCI for scheduling of PUSCH.

The terminal determines the transmission power for the first uplink MAC PDU.

The terminal transmits the first uplink MAC PDU based at least in part on the determined transmit power.

The terminal receives DCI for scheduling PDSCH in PDCCH.

DCI includes a time domain resource allocation field.

The terminal performs PDSCH reception based at least in part on the determined time domain relationship.

If the PDSCH-ConfigCommon of SIB1 received in the second cell includes pdsch-TimeDomainResourceAllocationList and the first SDT procedure is being performed, the time domain relationship is the pdsch-TimeDomainResourceAllocationList of PDSCH-ConfigCommon and the time resource of the DCI received for the second identifier. The determination is based at least in part on the assignment field.

If the PDSCH-ConfigCommon of SIB1 received in the second cell does not include pusch-TimeDomainResourceAllocationList and the first SDT procedure is being performed, the time domain relationship is the default time resource allocation table and the time resource of the DCI received for the second identifier. The determination is based at least in part on the assignment field.

If the PDSCH-Config of the RRCRelease received in the first cell includes pdsch-TimeDomainResourceAllocationList, and the second SDT procedure is being performed, the time domain relationship is for the pdsch-TimeDomainResourceAllocationList of the PDSCH-Config and the third or fourth identifier. The determination is made based at least in part on the time resource allocation field of the received DCI.

If the PDSCH-Config of RRCRelease received in the first cell does not include pdsch-TimeDomainResourceAllocationList, the PDSCH-ConfigCommon of SIB1 received in the second cell includes pusch-TimeDomainResourceAllocationList, and the second SDT procedure is being performed, time The domain relationship is determined based at least in part on the pdsch-TimeDomainResourceAllocationList of PDSCH-ConfigCommon and the time resource allocation field of the DCI received for the third or fourth identifier.

If the PDSCH-Config of RRCRelease received in the first cell does not include pdsch-TimeDomainResourceAllocationList, and the PDSCH-ConfigCommon of SIB1 received in the second cell does not include pusch-TimeDomainResourceAllocationList, and the second SDT procedure is performed, The time domain relationship is determined based at least in part on the default time resource allocation table and the time resource allocation field of the DCI received for the third or fourth identifier.

When RA-SDT is performed, the uplink transmit power of the first uplink MAC PDU is determined based at least in part on the preambleReceivedTargetPower and delta of the selected RACH-ConfigCommon of the selected uplink carrier.

If deltaPreamble is included in the RACH-ConfigCommon of the selected uplink carrier, delta is deltaPreamble in the selected RACH-ConfigCommon of the selected uplink carrier.

If deltaPreamble is not included in the RACH-ConfigCommon of the selected uplink carrier, delta is msg3-DeltaPreamble in the PUSCH-ConfigCommon of the selected uplink carrier.

The uplink transmit power of the first uplink MAC PDU is at least partially dependent on p0-NominalWithoutGrant in the PUSCH-Config of the selected uplink carrier and sdt-P0-PUSCH in the ConfiguredGrantConfig of the configured grant used in the first uplink MAC PDU. It is decided based on

p0-NominalWithoutGrant is an offset for PUSCH transmission without uplink grant.

If the PUSCH-ConfigCommon of the selected uplink carrier of SIB1 includes pusch-TimeDomainResourceAllocationList and the first SDT procedure is in progress, the time domain relationship is received for the pusch-TimeDomainResourceAllocationList and the second identifier in the PUSCH-ConfigCommon of the selected uplink carrier. It is determined based at least in part on the time resource allocation field of the uplink grant.

If the PUSCH-ConfigCommon of the selected uplink carrier of SIB1 does not include pusch-TimeDomainResourceAllocationList and the first SDT procedure is in progress, the time domain relationship is the time resource allocation field of the received uplink grant for the second identifier and the selected uplink It is determined based at least in part on the subcarrier spacing of the carrier's initial uplink BWP.

If the PUSCH-Config of the selected uplink of RRCRelease includes the pusch-TimeDomainResourceAllocationList and the second SDT procedure is in progress, the time domain relationship is the received for the pusch-TimeDomainResourceAllocationList and the third identifier in the PUSCH-Config of the selected uplink carrier. It is determined based at least in part on the time resource allocation field of the uplink grant.

If the PUSCH-Config of the selected uplink of RRCRelease does not include pusch-TimeDomainResourceAllocationList, the PUSCH-ConfigCommon of the selected uplink carrier of SIB1 includes pusch-TimeDomainResourceAllocationList, and the second SDT procedure is in progress, the time domain relationship is selected It is determined based at least in part on the pusch-TimeDomainResourceAllocationList in the PUSCH-ConfigCommon of the uplink carrier and the time resource allocation field of the received uplink grant for the third identifier.

If the PUSCH-Config of the selected uplink of RRCRelease does not contain pusch-TimeDomainResourceAllocationList, the PUSCH-ConfigCommon of the selected uplink carrier of SIB1 does not contain pusch-TimeDomainResourceAllocationList, and the second SDT procedure is in progress, the time domain relationship is It is determined based at least in part on the subcarrier spacing of the initial uplink BWP of the selected uplink carrier and the time resource allocation field of the received uplink grant for the third identifier.

Each ConfiguredGrantConfig includes configuredGrantTimer.

Figure 3a is a diagram showing the operation of the terminal.

In step 3a-05, the terminal receives an RRCRelease message from the first cell.

In step 3a-10, the terminal receives SIB1 from the second cell after selecting a cell as the second cell.

In step 3a-15, the terminal selects an uplink carrier based on SIB information.

In step 3a-20, the terminal decides to initiate the SDT procedure.

In step 3a-23, the time domain relationship is determined by the terminal based at least in part on the time resource allocation field of the DCI and the pdsch-TimeDomainResourceAllocationList of the PDSCH-ConfigCommon if the PDSCH-ConfigCommon includes the pdsch-TimeDomainResourceAllocationList.

If PDSCH-ConfigCommon does not include pdsch-TimeDomainResourceAllocationList, the time domain relationship is determined by the terminal based at least in part on the time resource allocation field of the DCI and the default time resource allocation table.

The default time resource allocation table consists of a plurality of fixed values. Each fixed value is the same or different from each other.

In step 3a-25, the terminal receives a downlink MAC PDU.

Figure 4a is a block diagram showing the internal structure of a terminal to which the present invention is applied.

Referring to the drawing, 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).

The control unit 4a-01 controls 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 into the storage unit 4a-02. For this purpose, 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 application programs. The control unit (4a-01) controls the storage unit and the transceiver to perform the terminal operations of FIGS. 2A and 3A. The transceiver is also called a transmitter and receiver.

The storage unit 4a-02 stores data such as basic programs, application programs, and setting information for operation of the terminal. The storage unit 4a-02 provides stored data upon request from the control unit 4a-01.

The transver (4a-03) includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions to transmit and receive signals through wireless channels, such as converting the signal band and amplifying it. That is, the RF processing unit up-converts the baseband signal provided from the baseband processing unit into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), 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 baseband signals and bit strings 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 transmission bit stream. Additionally, when receiving data, the baseband processing unit restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit. The transceiver is also called a transmitter and receiver.

The main processor (4a-04) controls overall operations excluding mobile communication-related operations. The main processor (4a-04) processes the user's input transmitted from the input/output unit (4a-05), stores the necessary data in the storage unit (4a-02), and controls the control unit (4a-01) to enable mobile communication. It performs related operations and transmits output information to the input/output unit (4a-05).

The input/output unit 4a-05 is composed of a device that receives user input, such as a microphone or screen, and a device that provides information to the user, and inputs and outputs user data under the control of the main processor.

Figure 4b is a block diagram showing the configuration of a base station according to the present invention.

As shown in the figure, the base station includes a control unit (4b-01), a storage unit (4b-02), a transceiver (4b-03), and a backhaul interface unit (4b-04).

The control unit 4b-01 controls 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 into the storage unit 4b-02. For this purpose, the control unit 4b-01 may include at least one processor. The control unit 4b-01 is a transceiver so that the base station operation shown in FIG. 2A is performed. storage unit. Controls the backhaul interface unit.

The storage unit 4b-02 stores data such as basic programs, applications, and setting information for operation of the main base station. In particular, the storage unit 4b-02 can store information about bearers assigned to the connected terminal, measurement results reported from the connected terminal, etc. Additionally, the storage unit 4b-02 can store information that serves as a criterion for determining whether to provide or suspend multiple connections to the terminal. And, the storage unit 4b-02 provides stored data according to the request of the control unit 4b-01.

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 band conversion and amplification of signals. That is, the RF processing unit upconverts the baseband signal provided from the baseband processing unit into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmission filter, reception filter, amplifier, mixer, oscillator, DAC, ADC, etc. The RF processing unit can perform downlink MIMO operation by transmitting one or more layers. The baseband processing unit performs a conversion function between baseband signals and bit strings according to physical layer standards. For example, when transmitting data, the baseband processing unit generates complex symbols by encoding and modulating the transmission bit stream. Additionally, when receiving data, the baseband processing unit restores the received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit. The transceiver is also called a transmitter and receiver.

The backhaul interface unit 4b-04 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 4b-04 converts a bit string transmitted from the main base station to another node, for example, an auxiliary base station, a core network, etc., into a physical signal, and converts the physical signal received from the other node into a bit string. Convert to heat.

Claims (1)

Method for RRC_INACTIVE state uplink transmission in a wireless mobile communication system.