KR102533613B1 - Method and Apparatus for RRC_CONNECTED state uplink transmission and RRC_INACTIVE uplink transmission in wireless mobile communication system - Google Patents

Abstract

According to an embodiment of the present disclosure, in a method of a terminal, the terminal receives an RRCReconfiguration message from a base station, and the terminal receives a MAC PDU from the base station based at least in part on downlink allocation for a first C-RNTI. Step, by the terminal, based at least in part on SRS activation information group 1 of the SP positioning SRS activation/deactivation MAC CE received when the SP positioning SRS activation/deactivation MAC CE is included in the MAC PDU and the A/D field is set to 1 activating the positioning SRS resource set at the first SRS activation time, wherein the terminal activates/deactivates the SP positioning SRS received when the SP positioning SRS activation/deactivation MAC CE is included in the MAC PDU and the A/D field is set to 0 Deactivating the positioning SRS resource set at the first SRS activation time based at least in part on SRS activation information group 1 of the MAC CE, receiving, by the UE, an RRCRelease message for switching the UE from RRC_CONNECTED to RRC_INACTIVE, 2 C -receiving a MAC PDU by a UE from a base station based at least in part on a downlink allocation for an RNTI, wherein the UE receives when the A/D field is set to 1 and a third timer is running at the time of activation of the third SRS activating a positioning SRS resource set at a third SRS activation time based at least in part on SRS activation information group 2 of the configured SP positioning SRS activation/deactivation MAC CE, and when the A/D field is set to 0, the terminal receives Activating/Deactivating the SP Positioning SRS Deactivating the positioning SRS resource set at a third SRS activation time based at least in part on the SRS activation information group 2 of the MAC CE.

Description

Method and Apparatus for RRC_CONNECTED state uplink transmission and RRC_INACTIVE uplink transmission in wireless mobile communication system}

The present disclosure relates to a method and apparatus for uplink transmission in an RRC connection state and uplink transmission in an RRC_INACTIVE state in a wireless mobile communication system.

In order to meet the growing demand for wireless data traffic after the commercialization of 4G communication systems, 5G communication systems have been developed. In order to achieve a high data rate, the 5G communication system has introduced a very high frequency (mmWave) band (eg, such as the 60 GHz band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), 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 distribution unit. In addition, the 5G communication system aims to support very high data rates and very low transmission delays in order to support various services.

As a method for realizing low transmission delay, uplink transmission of an inactive terminal is required.

The present disclosure is intended to provide a method and apparatus for uplink transmission in an RRC connection state and uplink transmission in an RRC_INACTIVE state in a wireless mobile communication system.

According to an embodiment of the present disclosure, in a method of a terminal, the terminal receives an RRCReconfiguration message from a base station, and the terminal receives a MAC PDU from the base station based at least in part on downlink allocation for a first C-RNTI. Step, by the terminal, based at least in part on SRS activation information group 1 of the SP positioning SRS activation/deactivation MAC CE received when the SP positioning SRS activation/deactivation MAC CE is included in the MAC PDU and the A/D field is set to 1 activating the positioning SRS resource set at the first SRS activation time, wherein the terminal activates/deactivates the SP positioning SRS received when the SP positioning SRS activation/deactivation MAC CE is included in the MAC PDU and the A/D field is set to 0 Deactivating the positioning SRS resource set at the first SRS activation time based at least in part on SRS activation information group 1 of the MAC CE, receiving, by the UE, an RRCRelease message for switching the UE from RRC_CONNECTED to RRC_INACTIVE, 2 C -receiving a MAC PDU by a UE from a base station based at least in part on a downlink allocation for an RNTI, wherein the UE receives when the A/D field is set to 1 and a third timer is running at the time of activation of the third SRS activating a positioning SRS resource set at a third SRS activation time based at least in part on SRS activation information group 2 of the configured SP positioning SRS activation/deactivation MAC CE, and when the A/D field is set to 0, the terminal receives Activating/Deactivating the SP Positioning SRS Deactivating the positioning SRS resource set at a third SRS activation time based at least in part on the SRS activation information group 2 of the MAC CE.

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

1A is a diagram illustrating the structure of a 5G system and an NG-RAN according to an embodiment of the present disclosure.
1B is a diagram illustrating a radio protocol structure in a NR system according to an embodiment of the present disclosure.
1c is a diagram illustrating transitions between RRC states according to an embodiment of the present disclosure.
1g is a diagram illustrating operations of a terminal and a base station according to an embodiment of the present disclosure.
1H is a diagram illustrating a first resumption procedure and a second resumption procedure according to an embodiment of the present disclosure.
2A is a diagram illustrating operations of a terminal and a base station according to an embodiment of the present disclosure.
3A is a flowchart for explaining an operation of a terminal according to an embodiment of the present disclosure.
4A is a block diagram showing the internal structure of a terminal to which the present invention is applied.
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 accompanying drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of a user or operator. Therefore, the definition should be made based on the contents throughout this specification.

A term 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 entities, and a term referring to various types of identification information. Etc. are illustrated for convenience of description. Therefore, the present invention is not limited to the terms described below, and other terms indicating objects having equivalent technical meanings 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 most up-to-date among existing communication standards. However, the present invention is not limited by the above terms and names, and may be equally applied to systems conforming to 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 AM Acknowledged Mode RA-RNTI Random Access RNTI AMF Access and Mobility Management Function RAT Radio Access Technology ARQ Automatic Repeat Request RB Radio Bearer AS Access Stratum RLC Radio Link Control ASN.1 Abstract Syntax Notation One RNA RAN-based Notification Area BSR Buffer Status Report RNAU RAN-based Notification Area Update BWP Bandwidth Part RNTI Radio Network Temporary Identifier CA Carrier Aggregation RRC Radio Resource Control CAG Closed Access Group RRM Radio Resource Management CG Cell Group RSRP Reference Signal Received Power C-RNTI Cell RNTI RSRQ Reference Signal Received Quality CSI Channel State Information RSSI Received Signal Strength Indicator DCI Downlink Control Information SCell Secondary Cell DRB (user) Data Radio Bearer SCS Subcarrier Spacing DRX Discontinuous Reception SDAP Service Data Adaptation Protocol HARQ Hybrid Automatic Repeat Request SDU Service Data Unit IE Information element SFN System Frame Number LCG Logical Channel Group S-GW Serving Gateway MAC Medium Access Control SI System Information MIB Master Information Block SIB System Information Block NAS Non-Access Stratum SpCell Special Cell NG-RAN NG Radio Access Network SRB 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 Uplinks 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 PDUs 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 PSS 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 tags

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 reselection A process to find a better suitable cell than the current serving cell based on the system information received in the current serving cell Cell selection A process to find a suitable cell either blindly or based on the stored information Dedicated signaling Signaling 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 consisted of cellIdentity and plmn-Identity of the first PLMN-Identity in plmn-IdentityList in SIB1. gNB node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. Handover procedure that changes the serving cell of a UE in RRC_CONNECTED. Information element A structural element containing single or multiple fields is referred as information element. L The Length field in MAC subheader indicates the length of the corresponding MAC SDU or of the corresponding MAC CE LCID 6 bit logical channel identity in MAC subheader to denote which logical channel traffic or which MAC CE is included in the MAC subPDU MAC-I Message Authentication Code - Integrity. 16 bit or 32 bit bit string calculated by NR Integrity Algorithm based on the security key and various fresh inputs Logical channel a logical path between a RLC entity and a MAC entity. There are multiple logical channel types depending on what type of information is transferred e.g. CCCH (Common Control Channel), DCCH (Dedicate Control Channel), DTCH (Dedicate Traffic Channel), PCCH (Paging Control Channel) LogicalChannelConfig The IE LogicalChannelConfig is used to configure the logical channel parameters. It includes priority, prioritisedBitRate, allowedServingCells, allowedSCS-List, maxPUSCH-Duration, logicalChannelGroup, allowedCG-List etc logicalChannelGroup ID of the logical channel group, as specified in TS 38.321, which the logical channel belongs to MAC CE Control Element generated by a MAC entity. Multiple types of MAC CEs are defined, each of which is indicated by corresponding LCID. A MAC CE and a corresponding MAC sub-header comprises a 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. SRB Signaling 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 "triggered" and "start" or "start" may be used in the same meaning. In the present invention, "radio bearer for which the second resume procedure is allowed", "radio bearer for which the second resume procedure is set", and "radio bearer for which the second resume procedure is enabled" may all be used in the same meaning.

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

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

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

The 5G system consists of NG-RAN (1a-01) and 5GC (1a-02). An 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 to UE side.

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

gNBs (1a-05 to 1a-06) and ng-eNBs (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 on the uplink, downlink and sidelink (schedule), IP and Ethernet header compression, uplink data decompression and encryption of user data streams, AMF selection, routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (originating from AMF or O&M), when AMF selection is not possible with the information provided;

Measurement and measurement report configuration for mobility and scheduling, session management, QoS flow management and mapping to data radio bearers, RRC_INACTIVE support, radio access network sharing;

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

AMF (1a-07) hosts functions such as NAS signaling, NAS signaling 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 radio protocol structure of a 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 (1b-09 to 1b-10). The control clearing 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, recovery from radio link failure detection and recovery, 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 decompression, encryption and decryption, integrity protection and integrity verification, redundant transmission, ordering and out-of-order delivery, etc. RLC Higher layer PDU transmission, error correction through ARQ, RLC SDU division and re-division, SDU reassembly, RLC re-establishment, etc. MAC Mapping between logical channels and transport channels, multiplexing/demultiplexing MAC SDUs belonging to one or another logical channel in a transport block (TB) carried in 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 UE 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 illustrating RRC state transitions.

State transition occurs between RRC_CONNECTED (1c-11) and RRC_INACTIVE (1c-13) by exchanging a resume message and a release message containing the suspend IE.

State transition occurs between RRC_ CONNECTED (1c-11) and RRC_IDLE (1c-15) through RRC connection establishment and RRC connection release.

State transition occurs from RRC_INACTIVE (1c-13) to RRC_IDLE (1c-15) through RRC connection release.

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 the base stations. If the terminal has a sufficiently large amount of data to transmit, these additional procedures can be fully justified, but otherwise, the efficiency of the network may deteriorate due to excessive overhead.

In the present invention, a new resume procedure capable of transmitting and receiving data without transitioning to RRC_CONNECTED is introduced. Hereinafter, a resume procedure for the purpose of transitioning a terminal in an RRC_INACTIVE state to an RRC_CONNECTED state is referred to as a first resume procedure, and a procedure in which a terminal in an RRC_INACTIVE state transmits/receives data while maintaining the RRC_INACTIVE state is referred to as a second resume procedure. Through the first resume procedure, the UE can resume the suspended RRC connection, and through the second resume procedure, the UE can resume data transmission and reception. The terminal may switch to the first resume procedure while performing the second resume procedure.

The second resume procedure may proceed through a random access procedure or may proceed through a configured grant. These are referred to as 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.

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 need not be as large as the cell's bandwidth. It can also be commanded to change width (e.g. collapse during periods of low activity to conserve power) or move position in the frequency domain (e.g. increase scheduling flexibility). Also, the sub-carrier interval may be changed (eg to allow other services). A subset of the cell's total cell bandwidth is called BWP(s). BA is achieved by configuring several BWPs to the UE and telling the UE which of the configured BWPs is active. In FIG. 1D, a scenario in which three different BWPs are configured is shown below.

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

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

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

1E is a diagram illustrating an example of a search period and a control resource set.

A plurality of SSs may be set in one BWP. The UE monitors PDCCH candidates according to the SS configuration of the currently activated BWP. One SS consists of an SS identifier, a CORESET identifier indicating a related CORESET, a period and offset of a slot to be monitored, a duration in units of slots, a symbol to be monitored within a slot, and an SS type. The information may be explicitly and individually set, or may be set to a predetermined index related to predetermined values.

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

Basically, it can be understood that CORESET provides 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. In IBWP, one CORESET and a plurality of SSs can be additionally set. When the terminal receives the 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 the CORESET#0 (1e-02) and SS#0 (1e-03). SIB1 includes information for setting CORESET#0 (1e-06) and SS#0 (1e-07) and information for setting another CORESET, for example, CORESET#n (1e-11) and SS#m (1e-13). may be included. The terminal receives necessary information from the base station before entering the RRC connected state, such as SIB2 reception, paging reception, and random access response message reception, using the CORESETs and SSs configured in SIB1. 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 referred to as first CORESET#0 and the latter as first CORESET#0. SS#0 (1e-03) set in MIB and SS#0 (1e-07) set in SIB1 may be different from each other, and the former is referred to as first SS#0 and the latter as second SS#0. SS#0 and CORESET#0 configured for the RedCap terminal are referred to as 3rd SS#0 and 3rd CORESET#0. The first SS#0, the second SS#0, and the third SS#0 may be identical to or different from each other. The first CORESET#0, the second CORESET#0, and the third CORESET#0 may be identical to or different from each other. SS#0 and CORESET#0 are instructed to set with a 4-bit index, respectively. 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 is indicated by individual information elements.

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

A serving cell may consist of one or several BWPs.

A UE may be configured with a plurality of DL BWPs and a plurality of UL BWPs for one serving cell. When the serving cell operates in a paired spectrum (ie, FDD band), the number of DL BWPs and the number of UL BWPs may be different. When the serving cell operates in an unpaired spectrum (ie, 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 a cell specific TDD UL/DL configuration. It consists of subfields such as referenceSubcarrierSpacing, pattern1, and pattern2.

referenceSubcarrierSpacing is a reference SCS used to determine the time domain boundary in the UL-DL pattern.

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 indicates a period of a 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.

Slots between the last full DL slot and the first full UL slot are flexible slots. A full UL slot is also referred to as a static UL slot. In this disclosure, the UL slot is a static UL slot.

DownlinkConfigCommonSIB includes BWP-DownlinkCommon for initial DL BWP. UplinkConfigCommonSIB includes BWP-UplinkCommon for initial UL BWP. 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 used only for the BWP indicated in SIB1. bwp-Id1 to 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 bandwidth portion, subcarrier spacing to be used by this BWP, cell specific parameters for PDCCH of this BWP, cell specific parameters for PDSCH of this BWP.

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

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

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

firstActiveDownlinkBWP-Id includes the ID of the DL BWP to be activated when RRC (re)configuration is performed.

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 the default bandwidth portion.

1F is a diagram showing the structure of ServingCellConfigCommonSIB included in SIB1.

SIB1 (1f-03) includes ServingCellConfigCommonSIB (1f-05). ServingCellConfigCommonSIB includes one DownlinkConfigCommonSIB (1f-07) and two UplinkConfigCommonSIBs. One UplinkConfigCommonSIB (1f-09) is for normal uplink (NUL) and another UplinkConfigCommonSIB (1f-11) is for supplementary uplink (SUL). UplinkConfigCommonSIB (1f-09) for NUL is located before UplinkConfigCommonSIB (1f-11) for SUL.

DownlinkConfigCommonSIB includes FrequencyInfoDL-SIB and BWP-DownlinkCommon (1f-13). BWP-DownlinkCommon is for initial DL BWP and includes PDCCH-ConfigCommon (1f-15) and PDSCH-ConfigCommon (1f-17).

UplinkConfigCommonSIB includes FrequencyInfoUL-SIB, TimeAlignmentTimer (1f-21) and BWP-UplinkCommon (1f-23). BWP-UplinkCommon is for initial UL BWP. BWP-UplinkCommon includes RACH-ConfigCommon (1f-25), PUSCH-ConfigCommon (1f-27), PUCCH-ConfigCommon (1f-29), and a plurality of RACH-ConfigCommon_fc (1f-31).

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

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

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

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

PDCCH-ConfigCommon is a cell specific PDCCH parameter for this BWP. 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. Indicates one of the predefined CORESET#0 configurations. ControlResourceSetZero included in MIB corresponds to first CORESET#0, and controlResourceSetZero included in PDCCH-ConfigCommon of servingCellConfigCommon of SIB1 corresponds to second CORESET#0.

searchSpaceZero is defined as an integer between 0 and 15. Indicates one of the predefined SS#0 configurations. searchSpaceZero included in MIB corresponds to 1st SS#0, and controlResourceSetZero included in PDCCH-ConfigCommon of servingCellConfigCommon of SIB1 corresponds to 2nd 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. The common SS may be used for paging reception, random access response reception, system information reception, and the like.

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

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

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

PDSCH-ConfigCommon consists of pdsch-TimeDomainAllocationList as the cell specific PDSCH parameter of this BWP. The pdsch-TimeDomainAllocationList is a list composed of a plurality of pdsch-TimeDomainAllocations.

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

pcch-Config is a configuration related to paging. It consists of sub-fields 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 sub-fields such as modificationPeriodCoeff indicating the length of the modification period.

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

FrequencyInfoUL-SIB is a basic parameter of an uplink carrier. It consists of sub-fields such as frequency band list and carrier bandwidth for each SCS.

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

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

prach-ConfigurationIndex is the PRACH configuration index. One PRACH configuration corresponds to pattern information on PRACH transmission opportunities in the time domain (information indicating that PRACH transmission is possible in which symbol in which slot of which radio frame) and the transmission format of the preamble.

msg1-FrequencyStart is an 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 PRBs of the corresponding carrier.

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

ra-ResponseWindow is the length of the random access response window represented by 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 UEs.

rsrp-ThresholdSSB is an SSB selection criterion. The UE performs random access by selecting a preamble corresponding to the selected SSB.

rsrp-ThresholdSSB-SUL is the SUL selection criterion. The UE selects an SUL carrier for random access based at least in part on this threshold.

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

push-ConfigCommon is a cell-specific PUSCH parameter of this BWP and consists of sub-fields such as push-TimeDomainAllocationList. The push-TimeDomainAllocationList is a list composed of a plurality of push-TimeDomainAllocations.

pushch-TimeDomainAllocation constitutes a time domain relationship between PDCCH and PUSCH. It consists of sub-fields such as K2 and startSymbolAndLength. K2 is the slot offset between DCI and scheduled PUSCH. startSymbolAndLength is an index representing a valid combination of start symbol and length.

pucch-ConfigCommon is a cell specific PUCCH parameter for this BWP. It consists of sub-fields such as pucch-ResourceCommon and p0-norminal.

pucch-ResourceCommon is an index corresponding to a cell-specific PUCCH resource parameter. One index corresponds to a PUCCH format, a PUCCH time period, a PUCCH frequency period, a PUCCH code, and the like.

p0-normal is a power offset applied during PUCCH transmission. It is defined as an integer between -202 and 24 in increments of 2. Unit is dBm.

timeAlignmentTimerCommon is a timer applied when the UE performs random access for RRC connection establishment procedure and RRC connection re-establishment procedure. When the UE receives the RAR, it starts driving the timer, and stops driving the timer when contention fails.

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

referenceSubcarrierSpacing is a reference SCS used to determine the time domain boundary in the UL-DL pattern.

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 indicates a period of a 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.

1G is a diagram illustrating operations of a terminal and a base station for small data transmission.

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

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

<UECapabilityInformation>

1. First information related to RRC_INACTIVE: 1-bit information indicating whether the terminal supports RRC_INACTIVE. Regardless of the number of bands supported by the terminal, only one is reported.

2. Second information related to RRC_INACTIVE: Information indicating whether the second resumption procedure is supported. Whether or not the second resume procedure is supported may be indicated for each band supported by the terminal. If the terminal supports n bands, n pieces of 1-bit information are reported.

3. Various types of performance information related to data transmission and reception between the terminal and the base station (for example, whether or not a specific decoding is supported).

A UE supporting RRC_INACTIVE supports the first resumption procedure in all frequency bands supported by the UE. That is, first information related to RRC_INACTIVE support is information applied to a plurality of bands, and second information related to RRC_INACTIVE is information applied to one band. A UE that does not support RRC_INACTIVE does not support the second resumption procedure in any frequency band that it supports. The serving base station refers to the performance of the UE and provides appropriate NR configuration information to the UE. 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 determines to transition the state of the terminal to the RRC_INACTIVE state.

In step 1g-13, the first base station transmits an RRCRelease message to the terminal. The RRCRelease message contains the SuspendConfig IE and the SuspendConfig contains the following information.

<SuspendConfig>

1. First UE identifier: UE identifier that can be included in ResumeRequest when state transitions to RRC_CONNECTED. It is 40 bits long.

2. Second terminal identifier: An identifier of a terminal that can be included in 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 composed of a list of cells and the like. The terminal initiates a resume 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 resumption procedure

7. Information related to the second resume procedure: a list of DRBs in which the second resume procedure is set (sdt-DRBlist), and 1-bit information indicating whether the second resume procedure is set in SRB2 (sdt-SRB2Indication). 1-bit information indicating whether the second resume procedure is set in SRB4 (sdt-SRB4Indication). The second LCG list (sdt-LCGList) of the bearer for which the second resume procedure is set, the data size threshold of the second resume procedure (hereinafter, the dedicated data threshold), and the reference signal reception strength threshold of the second resume procedure (hereinafter, the dedicated reference signal reception strength threshold)

Among SRB1, SRB2, SRB3, and SRB4, SRB1 transmits and receives the most important RRC control message, so it is important to quickly transmit the RRC control message as a second resume procedure, and it can be seen that the second resume procedure is highly effective. Although SRB2 and SRB4 are less important than SRB1 because relatively large messages can occur, the effectiveness of the second resume procedure is high because they still transmit important control messages. SRB3 is not used in a state where multiple connections are not established. Therefore, in the present invention, the second resume procedure is explicitly set for SRB2 and SRB4, and whether or not the second resume procedure is set is not set for SRB1 and SRB3. However, if the second resume procedure is set for at least one radio bearer, SRB1 It is defined that the second resumption procedure is set even in , and the second resumption procedure is not set for SRB3 under any conditions.

In step 1g-14, the terminal performs SuspendConfig action set. The SuspendConfig action set is applied at a predetermined first or second time point. When the SuspendConfig action set is executed, the following actions are performed sequentially.

<SuspendConfig action set>

1. Apply suspendConfig

2. MAC Reset

3. Reset RLC Entity of SRB1

4. Suspend all SRBs and DRBs

5. Start T380 set to t380

6. Enter RRC_INACTIVE state

The terminal applies the first point of view if the second resumption-related information is included, and applies the second point of view if it is not included.

The first point of view is as follows.

The earlier of the time when 100 ms has elapsed since the reception of the RRCRelease message and the time when the lower layer successfully notified the reception of the RRCRelease message

The second viewpoint is as follows.

The earlier of the time when 60 ms has elapsed after receiving the RRCRelease message or the time when the lower layer successfully notified the receipt of the RRCRelease message.

Since the reliability of the RRCRelease message including the second resumption-related information must be higher than the reliability of the RRCRelease message without the second resumption information, different time points are used.

In step 1g-15, the UE moves to a new cell. The terminal may reselect a neighboring cell having better radio signal quality by comparing the radio signal quality of the serving cell and the neighboring cell. Alternatively, a cell having a radio signal quality equal to or higher than a predetermined standard may be selected.

In step 1g-17, the UE receives system information including SIB1 in the new cell. SIB1 may include at least the following two pieces of information.

<SIB1>

1. T319 value

2. 1-bit information indicating whether the second resume procedure is allowed (or set or enabled)

If the second resume procedure is allowed, the following information is included in system information other than SIB1 (hereinafter referred to as SIB X) and broadcasted.

<SIBX>

1. Data size threshold of the second resume procedure (hereinafter referred to as common data threshold)

2. Reference signal reception strength threshold of the second resumption procedure (hereinafter referred to as common reference signal reception strength threshold)

3. Random access transmission resource information for the second resume procedure

4.t319ext

The UE receives the SIB X if at least one radio bearer for which the second resume procedure is configured exists, that is, if the second resume procedure is configured in at least one DRB or if the second resume procedure is configured in SRB2 or SRB4. .

Upon receiving necessary system information including SIB1, the UE performs the RRC_INACTIVE operation shown in Table 5 in the cell.

In step 1g-19, an event triggering the resume procedure occurs. A resumption procedure may be triggered when a higher layer or AS requests resumption of a suspended RRC connection or when new data is generated.

In step 1g-21, the UE triggers one of the first resume procedure and the second resume procedure. If any one of the first set of resume conditions is satisfied, the first resume procedure is triggered.

<First Resumption Condition Set>

1. The upper layer requests resumption of the suspended RRC connection.

2. Receive RAN paging including the first identifier

3. RNA update occurs.

4. Data has occurred in a radio bearer for which the second resumption procedure trigger is permitted, but the second resumption conditions are not all satisfied.

If all of the second set of resume conditions are satisfied, the second resume procedure is triggered.

<Second Set of Resumption Conditions>

1. Transmittable data is generated in a bearer belonging to the first bearer set.

2. The amount of transmittable data of a bearer belonging to the first bearer set is less than the final data threshold.

3. The reference signal reception strength of the current serving cell is higher than the final reference signal reception strength threshold.

4. The current serving cell provides transmission resources for the second resume procedure.

A radio bearer for which the second resume procedure trigger is allowed (or for which the second resume procedure is allowed) means a DRB for which the second resume procedure is allowed and an SRB for which the second resume procedure is allowed. In SRB3, the second resume procedure is not allowed, and in SRB2 and SRB4, whether to allow the second resume procedure is explicitly indicated. When the second resume procedure is allowed for at least one radio bearer, the second resume procedure is automatically allowed for SRB1.

The final data threshold is the lower of the dedicated data threshold and the common data threshold. Alternatively, if both the dedicated data threshold and the joint data threshold exist, the dedicated data threshold is the final data threshold, and if there is only one, it is the final data threshold. Alternatively, if both the dedicated data threshold and the common data threshold exist, the common data threshold is the final data threshold, and if there is only one, it is the final data threshold.

The final reference signal reception strength threshold is the higher of the dedicated reference signal reception strength threshold and the common reference signal reception strength threshold. Alternatively, if both the dedicated reference signal reception strength threshold and the common reference signal reception strength threshold exist, the dedicated reference signal reception strength threshold is the final reference signal reception strength threshold, and if there is only one, it is the final data threshold. Alternatively, if both the dedicated reference signal reception strength threshold and the common reference signal reception strength threshold are present, the common reference signal reception strength threshold is the final reference signal reception strength threshold, and if there is only one, it is the final data threshold.

When at least one of the first set of conditions is satisfied and both of the second set of conditions are satisfied, that is, when both the first and second resume procedures are triggered, the UE selects the second resume procedure.

In step 1g-23, the terminal performs the first resume procedure or the second resume procedure with the base station.

1H is a diagram illustrating a first resumption procedure and a second resumption procedure according to an embodiment of the present disclosure.

The first resumption procedure is as follows.

In step 1h-11, the UE performs the first resume operation set 1. The first resume action set 1 is the action taken when the first resume procedure is initiated and is as follows. By performing the first resume operation set 2, the terminal can receive a downlink control message from the base station through SRB1.

<First resume action set 1>

1. Apply default SRB1 settings

2. Apply default MAC Cell Group settings

3. Start T319 set to t319 received from SIB1

The default SRB1 configuration is as follows.

Name Value SRB1 SRB2 SRB3 PDCP-Config
>t-Reordering
infinity RLC-Config CHOICE Am ul-AM-RLC>sn-FieldLength
>t-PollRetransmit
>pollPDUs
>pollByte
>maxRetxThreshold
size12
ms45
infinity
infinity
t8 dl-AM-RLC>sn-FieldLength>t-Reassembly
>t-StatusProhibit
size12
ms35
ms0 logicalChannelIdentity One 2 3 LogicalChannelConfig >priority One 3 One >prioritisedBitRate infinity >logicalChannelGroup 0

The default MAC Cell Group settings are as follows.

Name Value MAC Cell Group configuration bsr-Config >periodicBSR-Timer sf10 >retxBSR-Timer sf80 phr-Config >phr-PeriodicTimer sf10 >phr-ProhibitTimer sf10 >phr-Tx-PowerFactorChange dB1

T319, which is set to t319, is a timer driven so that a follow-up action, such as transition to RRC_IDLE, can be performed if the first resume procedure fails. T319 set to t319 is stopped when RRCResume is received. If RRCResume is not received until T319 set to t319 expires, the terminal performs the T319 expiration action set. <T319 expiration action set>

1. MAC Reset

2. Abandon UE Inactive AS Context

3. Disable suspendConfig

4. Security key destruction

5. Release all RLC Entities, PDCP Entities, and SDAP Entities

6. Transition to RRC_IDLE and perform cell selection operation

In step 1h-13, the terminal performs operation set 2 of the first resume procedure. The first resume procedure action set 2 is an action taken before sending a ResumeRequest.

<First resume procedure action set 2>

0. Restore RRC settings of UE Inactive AS context excluding masterCellGroup and PDCP-config

1. Calculate resumeMAC-I: A 16-bit message verification code is calculated using the first security key (the security key used in the previous RRC_CONNECTED state or the security key used at the time of receiving RRCRelease).

2. Derivation of the second base station security key using NCC. The second security key, the third security key, the fourth security key, and the fifth security key are derived from the security key of the second base station.

3. Setting all radio bearers except SRB0 to use the second security key and the third security key or the fourth security key and the fifth security key

3. Reset PDCP Entity on SRB 1

4. SRB1 resume

In step 1h-15, the terminal transmits a ResumeRequest message to the second base station. The MAC PDU containing the ResumeRequest message does not include data of other radio bearers. ResumeRequest includes the following information.

<ResumeRequest>

1. First identifier or second identifier: Among the first identifier and second identifier given in SuspendConfig, an identifier indicated in system information is included.

2. resumeMAC-I: 16-bit message verification code to ensure integrity of resumeRequest message. The terminal calculates resumeMAC-I using the previous security key (the security key used in the previous RRC_CONNECTED state or the security key used at the time of receiving the RRCRelease).

3. resumeCause: 4 representing one of emergency, highPriorityAccess, mt-Access, mo-Signalling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, mps-PriorityAccess, mcs-PriorityAccess, SmallDataTransmission bit information.

The terminal performing the first resume procedure selects one of the values other than smallDataTransmission as resumeCause. This is so that the base station can determine whether or not to resume the second resume procedure through resumeCause.

In step 1h-17, the UE receives RRCResume. RRCResume contains the following information.

<RRCResume>

1. masterCellGroup: CellGroupConfig for the master cell group, including RLC bearer information, MAC configuration information, PHY configuration information, and SpCell configuration information.

2. radioBearerConfig: This is radio bearer configuration information and includes SRB configuration information and DRB configuration information.

In step 1h-19, the UE performs the first resume procedure action set 3.

<first resume procedure action set 3>

1. Stop T319

2: Stop T380

3: Restore and apply masterCellGroup of UE Inactive AS Context

4: Apply RRCResume's CellGroupConfig and radioBearerConfig

5. Restart SRB2, SRB3 and all DRBs

6. Transition to RRC_CONNECTED state

7. Stop the cell reselection process

In step 1h-21, the terminal transmits an RRCResumeComplete message to the second base station. The RRCResumeComplete message includes PLMN identifier information selected by the UE.

In step 1h-23, the terminal and the second base station transmit and receive data. At this time, the terminal may transmit MAC CE such as BSR or PHR to the base station together. When the BSR trigger condition is satisfied, the UE multiplexes the BSR to the uplink MAC PDU and transmits the same. When the PHR trigger condition is met, the UE multiplexes the PHR MAC CE with the uplink MAC PDU and transmits the multiplexed PHR MAC CE. BSR trigger conditions include generation of new data with high priority, expiration of a periodic timer, and the like. The PHR trigger condition includes a change in reception strength of a reference signal greater than or equal to a predetermined standard, activation of a new secondary cell, and the like.

In step 1h-25, when data transmission and reception with the terminal is completed, the second base station transmits RRCRelease including SuspendConfig to the terminal to transition the terminal to the RRC_INACTIVE state.

Upon receiving the RRCRelease message including SuspendConfig in step 1h-27, the terminal starts T380.

The second resumption procedure is as follows.

In step 1h-31, the UE performs the second resume operation set 1. The second resume action set 1 is the action taken when the second resume procedure is triggered and is as follows. By performing the second resume operation set 1, the UE receives a downlink control message from the base station through SRB1, and the radio bearer for which the second resume procedure is allowed (or data transmission is possible in the INACTIVE state, or the second resume procedure is set) It is possible to transmit uplink data of and receive downlink data.

<Second resume action set 1>

0: Restore all RRC settings of UE Inactive AS Context (including radio bearer settings of the first bearer set, masterCellGroup, and PDCP-config)

1. Start T319ext set to t319ext

2. Stop the T380

3. Calculate resumeMAC-I: A 16-bit MAC-I is calculated using the previous K_RRCint, that is, the first security key (K_RRCint used in the previous RRC_CONNECTED state or K_RRCint used when RRCRelease was received).

4. Derivation of the second base station security key using the first base station security key and NCC. The second security key, the third security key, the fourth security key, and the fifth security key are derived from the security key of the second base station.

5. Configuration to use the 2nd security key and the 3rd security key or the 4th security key and the 5th security key for the 1st bearer set

6. PDCP entity reset of the first bearer set

7. Resuming radio bearers of the first bearer set

8. Stop the cell reselection process

9. Second cell reselection procedure initiated

T319ext set to t319ext is a timer driven so that follow-up measures, such as transition to RRC_IDLE, can be performed if the second resume procedure fails. The T319, T319ext and T380 have the following features.

First Reopening Procedure T380 T319 setting RRCRelease SIB1 start Receive RRCRelease Between the time of applying the default SRB1 setting after the first resume procedure is initiated and the time of resuming SRB1 stop RRCResume is received and before cell group configuration information is applied. After receiving RRCResume and before applying cell group configuration information Behavior on expiration Initiate cyclic RNA renewal procedure in current cell T319 expiration action set Second Reopening Procedure T380 T319ext setting RRCRelease SIBX start Receive RRCRelease Between the time of applying the SRB1 configuration stored in the UE Inactive AS Context after the start of the second resume procedure and the time of resuming SRB1 stop Between the time of applying the SRB1 configuration stored in the UE Inactive AS Context after the start of the second resume procedure and the time of resuming SRB1 When RRCRelease is received or before RRCResume is received and cell group configuration information is applied Behavior on expiration Determining whether to initiate a periodic RNA renewal procedure in the current cell T319ext expiration action set

In the first resume procedure, starting T380 and T319 after receiving the RRCResume message and before setting cell group configuration information is to stop the timers as the first operation after receiving the RRCResume message to prevent unnecessary subsequent operations due to expiration of the timer from starting. The reason why T319 is started in the first resume procedure between the application time of the default SRB1 setting and the resume time of SRB1 after the start of the first resume procedure is to start T319 at a time point closest to the SRB1 available time.

In the second resume procedure, T319ext is performed between the time of applying the SRB1 settings stored in the UE Inactive AS Context and the time of resuming SRB1 in order to start T319ext at a time point closest to the time SRB1 is available.

In the second resume procedure, between the time of applying the SRB1 setting stored in the UE Inactive AS Context to T380 and the time of resuming SRB1, T380 and T319ext are defined to start at the most similar time to reduce the load related to timer processing of the terminal It is for

The timing of applying the SRB1 configuration stored in the UE Inactive AS Context and the timing of applying the radio bearer configuration of the first bearer set stored in the UE Inactive AS Context are the same. The timing of resuming the SRB1 is the same as the timing of resuming the radio bearers of the first bearer set.

If RRCResume is not received until T319ext set to t319ext expires, the terminal may perform the T319ext expiration action set or the T319 expiration action set. The base station may set which of the T319ext expiration action set and the T319 expiration action set to select in SuspendConfig or system information.

<T319ext expiration action set>

1. MAC Reset

2. Maintaining UE Inactive AS Context

3. Maintain suspendConfig

4. The first base station security key and the first security key are discarded in the UE Inactive AS Context, and the second base station security key and the third security key are stored in the UE UE Inactive AS Context.

5. Suspend all SRBs and DRBs

6. Start T380 set to t380

7. Stop Second Cell Reselection Procedure

8. Execute the cell selection procedure

9. Initiate the RNA renewal process after selecting a suitable cell

The first bearer set is a set of radio bearers for which the second resume procedure is explicitly or implicitly established, and is composed of SRB1 and radio bearers related to the second resume procedure. A radio bearer related to the second resumption procedure means a radio bearer to which the second resumption procedure is explicitly allowed or a radio bearer to which the second resumption procedure is explicitly set.

Stopping the cell reselection procedure means stopping the existing cell reselection procedure performed before proceeding with the second resumption procedure. In the existing cell reselection procedure, the cell reselection priority provided by the base station is applied to select a frequency to preferentially camp, and each cell is ranked in consideration of the reference signal reception strength and various offsets of cells within the selected frequency, This is a procedure for reselecting the cell with the highest rank.

When the second cell reselection procedure starts, the terminal stops using the cell reselection priorities and offsets indicated by the base station and uses the following parameters.

<Second Cell Reselection Procedure>

1. Increase the cell reselection priority of the current serving frequency to the highest priority

2. Increase the first Qhyst by a predetermined value. Or apply 2nd Qhyst

When determining the cell priority, the UE puts a weight equal to Qhyst on the current serving cell. That is, the priority is determined by adding Qhyst to the reference signal reception strength of the actual serving cell. The first Qhyst is included in SIB2 and broadcasted. The second Qhyst or the predetermined value is included in SIBX and broadcasted.

In step 1h-33, the UE transmits a MAC PDU including a first SDU including a ResumeRequest message and a second SDU including data of the first bearer set (or data of a bearer for which the second resume procedure is set) to the second base station. The terminal performing the second resume procedure selects smallDataTransmission as ResumeCause. The UE may include a priority-based BSR MAC CE and a PHR MAC CE in the MAC PDU. When the BSR/PHR inclusion condition is satisfied and the BSR/PHR cancellation condition is not satisfied, the UE transmits the priority-based BSR MAC CE and PHR MAC CE in the MAC PDU. Even if the BSR/PHR inclusion condition is satisfied, the UE transmits the MAC PDU without the priority-based BSR and PHR if the BSR/PHR cancellation condition is satisfied.

<Conditions for including BSR/PHR>

Subsequent data to be transmitted after transmission of the MAC PDU including the ResumeRequest (or the first uplink MAC PDU of the second resume procedure) exists, or there is an uplink grant for transmission of the MAC PDU including the ResumeRequest (or the first uplink grant of the second resume procedure) Not accepting all transmittable data

<BSR/PHR Cancellation Conditions>

Transmitted if the uplink grant for MAC PDU transmission including the ResumeRequest (or the first uplink grant of the second resume procedure) does not include at least one of a subheader corresponding to the triggered BSR and a subheader corresponding to the triggered PHR All possible data can be accommodated, but all transmittable data cannot be accommodated if at least one of the subheader corresponding to the triggered BSR and the subheader corresponding to the triggered PHR is included.

In step 1h-35, the terminal and the base station transmit and receive data of the first bearer set. Data of the first bearer set is scheduled by C-RNTI, and the UE monitors the frequency domain and time period for transmitting and receiving small amount of data (or for transmitting and receiving data of the second resume procedure) indicated by SIB X.

When data transmission is completed, the base station determines to end the second resume procedure.

In step 1h-37, the second base station transmits RRCRelease including SuspendConfig to the terminal to terminate the second resume procedure. When the terminal performing the second resume procedure receives the RRCRelease including SuspendConfig, it performs second resume procedure operation set 2 to end the second resume procedure.

<Second resume action set 2>

1. Stop monitoring the frequency domain and time period for transmitting and receiving small amounts of data, as indicated by SIB X

2. MAC Reset

3. Update suspendConfig with newly received information

4. In the UE Inactive AS Context, the first base station security key and the first security key are discarded and the second base station security key and the third security key are stored.

5. Suspend all SRBs and DRBs except SRB0

6. Start the T380 configured with the newly received t380

7. Stop Second Cell Reselection Procedure

8. Initiation of the first cell reselection procedure

2A is a diagram illustrating operations of a terminal and a base station according to an embodiment of the present disclosure.

After power is turned on, the terminal performs cell selection and camps on the first cell.

In 2a-11, the UE receives system information (MIB, SIB1, SIB2 and other SIBs) in the first cell.

In 2a-13, the UE and the GNB perform a random access procedure based on system information.

The terminal establishes an RRC connection with the base station. The terminal and the base station exchange an RRCRequest message, an RRCSetup message, and an RRCSetupComplete message through a random access process. When the terminal receives the RRCSetup message from the base station, an RRC connection is established.

In 2a-17, UE transmits UECapabilityInformation and GNB receives UECapabilityInformation.

UECapabilityInformation includes capability information for SDT and capability information for a plurality of SRSs. Each capability information for a plurality of SRSs indicates whether the UE supports SRS transmission in a specific frequency band in the RRC_INACTIVE state.

GNB determines the configuration to apply to the UE based on UECapabilityInformation.

In 2a-19, the GNB transmits an RRCReconfiguration message and the UE receives it.

The RRCReconfiguration message includes multiple BWP-Downlinks, multiple BWP-Uplinks, firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id, BWP-DownlinkDedicated for initial DL BWP, and BWP-UplinkDedicated for initial UL 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 used only for the BWP indicated in SIB1. bwp-Id1 to 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 bandwidth portion, subcarrier spacing to be used by this BWP, cell specific parameters for PDCCH of this BWP (PDCCH-ConfigCommon), cell for PDSCH of this BWP A specific parameter (PDSCH-ConfigCommon).

BWP-UplinkCommon contains the following information: frequency domain location and bandwidth of this bandwidth portion, subcarrier spacing to be used by this BWP, cell specific parameters for PUCCH of this BWP (PUCCH-ConfigCommon), cell for PUSCH of this BWP Specific parameters (PUSCH-ConfigCommon), cell specific random access parameters (RACH-ConfigCommon).

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

BWP-UplinkDedicated is used to configure dedicated (UE specific) parameters of uplink BWP. This includes this BWP's PUCCH-Config, this BWP's PUSCH-Config, this BWP's configuredGrantConfig, and this BWP's SRS-Config.

firstActiveDownlinkBWP-Id includes the ID of the DL BWP to be activated when RRC (re)configuration is performed.

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 the default bandwidth portion.

The RRCReconfiguration message may further include the following IEs: DRBToAddMod IE and SRBToAddMod IE.

The DRB-ToAddModList IE includes a plurality of DRB-ToAddMod IEs. DRB-ToAddMod IE includes PDCP configuration and SDAP configuration and drb-Identity. The UE configures multiple DRBs based on the DRB-ToAddModList IE.

The SRB-ToAddModList IE includes a plurality of SRB-ToAddMod IEs. The SRB-ToAddMod IE includes PDCP configuration and srb-Identity. The UE configures a plurality of SRBs based on the SRB-ToAddModList IE.

The RRCReconfiguration message may include a plurality of SRS settings (SRS-config).

GNB and UE perform data transmission through the DRB and logical channels configured by the RRCReconfiguration message.

GNB and UE perform data transmission based on the configured grant. GNB and UE perform SRS transmission and reception based on SRS-config.

At some point GNB decides to transition the state from RRC_CONNECTED to RRC_INACTIVE.

GNB generates a RRCRlease message containing suspendConfig.

In 2a-21, the GNB transmits the RRCRlease message and the UE receives it. The RRCRlease message contains the SuspendConfig IE.

SuspendConfig IE includes the following fields in the non-extension part.

<Fields included in non-extended part of SuspendConfig>

1. fullI-RNTI: UE identifier that can be included in ResumeRequest when the state transitions to RRC_CONNECTED. It is 40 bits long.

2. shortI-RNTI: UE identifier that can be included in 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 composed of a list of cells and the like. The terminal initiates a resume 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 resumption procedure

If the GNB decides to activate the SDT for the UE, the suspendConfig IE may include the SDT-Config IE in the first extension part. The SDT-Config IE contains the following fields.

sdt-DRB-List indicates IDs of DRBs configured for SDT.

sdt-SRB2-Indication indicates whether SRB2 is configured for SDT.

The sdt-MAC-PHY-CG-Config field indicates CG-SDT specific configuration. The sdt-MAC-PHY-CG-Config field includes the following fields.

cg-SDT-TimeAlignmentTimer: This field contains the TimeAlignmentTimer IE. The UE uses this value for grant-related tasks configured in RRC_INACTIVE.

cg-SDT-TA-ValidationConfig: This field contains configuration for RSRP based TA validation. This includes information on the number of SSBs to be averaged for CG-SDT verification and the RSRP threshold for CG-SDT resource verification.

cg-SDT-Config-Initial-BWP-NUL: This field contains PUCCH-Config IE and PUSCH-Config IE and ConfiguredGrantConfigToAddModList IE. The UE applies this IE for grant-related operations configured in the NUL of RRC_INCATIVE.

cg-SDT-Config-Initial-BWP-SUL: This field contains PUCCH-Config IE and PUSCH-Config IE and ConfiguredGrantConfigToAddModList IE. The UE applies these IEs for grant-related operations configured in the SUL of RRC_INCATIVE.

cg-SDT-Config-Initial-BWP-DL: This field contains PDCCH-Config IE and PDSCH-Config IE. The UE applies these IEs for grant-related operations configured in RRC_INACTIVE.

CS-RNTI: This field contains the RNTI value for the uplink grant configured during the RRC_INACTIVE state. RNTI values are 16 bits long.

When GNB determines to enable SRS transmission, the suspendConfig IE includes the SRS-PosRRC-InactiveConfig IE in the second extension part.

srs-Config: This field contains SRS-Config for RRC_INACTIVE state.

bwp: This field is a BWP configuration for SRS for Positioning during RRC_Inactive state. If no field is present, the UE is configured with SRS for positioning relative to the initial UL BWP and transmitted within the initial UL BWP with the same CP and SCS as configured for the initial UL BWP during the RRC_INACTIVE state.

srs-TimeAlignmnetTimer: This field contains the TimeAlignmentTimer IE for SRS for positioning transmission during RRC inactive state.

srs-PosRRC-ValidationConfig: This field includes configuration for RSRP-based TA validation for SRS transmission. This includes information on the average number of SSBs for SRS resource verification and the RSRP threshold for SRS resource verification.

C-RNTI: This field contains the RNTI value for SRS activation/deactivation during the RRC_INACTIVE state. RNTI values are 16 bits long.

When suspendConfig is received (or suspendConfig is included in RRCRlease), the UE does the following:

The UE applies the non-extended part of suspendConfig.

UE Reset MAC.

UE applies remaining suspendConfig

The UE resets the RLC entity for SRB1.

The UE suspends all SRB(s) and DRB(s) except SRB0.

The UE enters RRC_INACTIVE and performs cell selection.

In the cell selection process, the UE selects an appropriate cell and camps on. The selected suitable cell is the second cell. The first cell and the second cell may be the same cell or different cells.

At 2a-23, the UE receives system information from the second cell. If the first cell and the second cell are the same, the UE receives the first system information and applies the stored second system information. When the first cell and the second cell are different, the UE receives the first system information and the second system information. The first system information is MIB. The second system information includes SIB1 and other related system information.

In 2a-25, the UE performs an INACTIVE operation in the second cell. The UE and GNB can perform SRS transmission and reception in the INACTIVE state based on the RRCRlease message and MAC CE.

At 2a-27, the UE starts the SDT procedure in the second cell. During the SDT procedure, the UE and the GNB may transmit and receive configured uplink grants based on the RRCRlease message.

Upon MAC reset, the UE:

The UE stops all timers (if running).

The UE considers all timeAlignmentTimers to be expired.

If there is a UE, it stops the random access procedure in progress.

The UE flushes soft buffers for all DL HARQ processes.

timeAlignmentTimer handling

During the random access procedure, the UE starts timeAlignmentTimer when the timing advance command is received in the random access response message. The timeAlignmentTimerCommon field included in SIB1 is applied to timeAlignmentTimer.

The UE receives an RRCSetup message during a random access procedure. The RRCSetup (or RRCReconfiguration) message may include one or more timeAlignmentTimer fields. The UE applies the first timeAlignmentTimer field to timeAlignmentTimer when the timer is restarted. The first timeAlignmentTimer field is a timeAlignmentTimer field related to tag-Id 0.

When the UE receives a timing advance command MAC CE or an Absolute timing advance command MAC CE, the UE applies a Timing Advance command for the indicated TAG and starts or restarts the timeAlignmentTimer associated with the indicated TAG.

The timing advance command MAC CE is identified by the MAC subheader with the LCID. Timing Advance Command MAC CE consists of a 2-bit TAG identity field and a 6-bit timing advance command field.

The Absolute timing advance command MAC CE is identified by the MAC subheader with the eLCID. Absolute Timing Advance Command The MAC CE consists of 4 reserved bits and a 12-bit timing advance command.

The timing advance command of the Random Access Response message indicates an index value that controls the amount of timing adjustment. The index represents the absolute value. The length of the field is 12 bits.

Timing Advance Command A timing advance command in the MAC CE indicates an index value that controls a timing adjustment amount. The index indicates a relative value compared with the current timing adjustment amount. The length of the field is 6 bits.

Absolute Timing Advance Command A timing advance command in the MAC CE indicates an index value that controls a timing adjustment amount. The index represents the absolute value. The length of the field is 12 bits.

When the timeAlignmentTimer associated with the PTAG expires, the UE does the following.

The UE flushes all HARQ buffers for all serving cells.

The UE releases PUCCH for all serving cells, if configured.

The UE releases SRS, if configured, for all serving cells.

The UE deletes the configured downlink assignment and the configured uplink grant.

The UE deletes all PUSCH resources for semi-persistent CSI reporting.

The UE considers all running timeAlignmentTimers to be expired.

When the timeAlignmentTimer associated with the STAG expires, the UE performs the following for all serving cells belonging to the TAG.

The UE flushes all HARQ buffers.

The UE releases PUCCH if configured.

The UE releases SRS if configured.

The UE deletes the configured downlink assignment and the configured uplink grant.

The UE deletes all PUSCH resources for semi-persistent CSI reporting.

There are two types of transfers without dynamic grants.

configured grant type 1 where the uplink grant is provided by the RRC and stored as a configured uplink grant;

Configured grant type 2, in which the uplink grant is provided by PDCCH and stored or erased as configured uplink grant based on L1 signaling indicating configured uplink grant activation or deactivation.

Type 1 and Type 2 are configured by RRC for the serving cell per BWP. Multiple configurations can be active simultaneously on the same BWP. In the case of type 2, activation and deactivation are independent between serving cells.

RRC configures the following parameters when configured grant type 1 is configured:

cs-RNTI: CS-RNTI for retransmission;

Periodicity: periodicity of configured acknowledgment type 1;

timeDomainOffset: Offset of resource to SFN = timeReferenceSFN in time domain;

timeDomainAllocation: uplink grant allocation configured in time domain with startSymbolAndLength or startSymbol;

nrofHARQ-Processes: Number of HARQ processes for approval configured;

timeReferenceSFN: SFN used to determine the resource's offset in the time domain. The UE uses the closest numbered SFN prior to receiving the configured grant configuration.

frequencyHopping: The value intraSlot enables 'frequency hopping within slots' and the value interSlot enables 'frequency hopping between slots'. If there is no field, no frequency hopping is constituted.

p0-PUSCH-Alpha: This field contains an index representing the p0 value.

When configured grant type 2 is configured, RRC configures the following parameters:

cs-RNTI: CS-RNTI for activation, deactivation and retransmission;

Periodicity: periodicity of configured acknowledgment type 2;

nrofHARQ-Processes: Number of HARQ processes for approval configured;

cs-RNTI is included in PhysicalCellGroupConfig IE or SuspendConfig IE.

Periodicity, timeDomainOffset, timeDomainAllocation, nrofHARQ-Processes, frequencyHopping, p0-PUSCH-Alpha and timeReferenceSFN are included in ConfiguredGrantConfig.

When the ConfiguredGrantConfig IE is included in the second part of SuspendConfig of the RRCRlease message, the ConfiguredGrantConfig IE may further include an sdt-P0-PUSCH field. Instead of the value indicated in the PO-PUSCH field of the PUSCH-Config IE, the value indicated in the sdt-P0-PUSCH field is applied to initial transmission based on the grant configured in the RRC_INACTIVE state.

The RRCReconfiguration message includes one PhysicalCellGroupConfig IE and a plurality of ConfiguredGrantConfig IEs.

The RRCRlease message contains 0 or 1 cs-RNTI field. The RRCRlease message contains zero or more ConfiguredGrantConfigs.

SRS setting can be provided for each UL BWP, and SRS setting consists of one or more SRS-PosResourceSets (hereinafter referred to as SRS positioning resource sets). One SRS positioning resource set is composed of one or more SRS-PosResources (hereinafter referred to as SRS positioning resources).

SRS positioning resource is defined as srs-PosResourceId (SRS positioning resource identifier), startPosition, nrofSymbols, freqDomainShift, freqHopping, periodicityAndOffset-sp, spatialRelationInfoPos, etc.

startPosition and nrofSymbols represent the start position of a symbol through which the SRS is transmitted and the number of symbols through which the SRS is transmitted in the position SRS slot.

freqDomainShift and freqHopping define the frequency resource through which the SRS is transmitted in contrast to the frequency domain of the corresponding BWP.

periodicityAndOffset-sp indicates the slot and period at which the position SRS slot starts. The location SRS slot refers to a slot in which a location SRS resource is set or a slot through which the location SRS is transmitted.

spatialRelationInfoPos defines a spatial domain transmission filter to be applied to location SRS transmission, and may be set to a downlink reference signal index of a serving cell, an SSB index of a neighboring cell, and the like. For RRC_INACTIVE UEs, spatialRelationInfoPos is always set to index 0 (ie, PCell). For an RRC_CONNECTED UE, any serving cell or neighboring cell may be used.

The SRS positioning resource set consists of an SRS positioning resource set identifier, an SRS positioning resource identifier list, a resource type, alpha, p0, and pathlossReferenceRS-Pos.

The SRS positioning resource identifier list is a list of identifiers of SRS positioning resources constituting the SRS positioning resource set.

The resource type indicates one of periodic, semi-persistent, and aperiodic. In this disclosure, a semi-permanent SRS positioning resource set is described as an example. In the case of an SRS positioning resource set with a semi-permanent resource type, transmission of the position SRS belonging to the SR positioning resource set starts only when a predetermined control message instructs transmission. Only periodic or semi-permanent is applicable to a UE in RRC_INACTIVE state.

alpha, p0 and pathlossReferenceRS-Pos are parameters for controlling the transmission output of the position SRS. It is a reference signal to

The UE receives a Positioning SRS Activation/Deactivation MAC CE indicating transmission of a specific SRS positioning resource set from the base station.

Positioning SRS Activation/Deactivation MAC CE consists of an A/D field, a Cell ID field, a BWP ID field, a SUL field, and a Positioning SRS Resource Set ID.

The A/D field indicates whether to activate or deactivate the displayed SRS positioning resource set.

The Cell ID field represents an identifier of a serving cell to which an SRS positioning resource set to be activated/deactivated belongs.

The BWP ID field indicates an identifier of a BWP to which an SRS positioning resource set to be activated/deactivated belongs.

The SUL field indicates whether MAC CE is applied to a NUL carrier or SUL carrier configuration. Alternatively, it indicates whether the SRS positioning resource set to be activated or deactivated is an SRS positioning resource set of SUL or an SRS positioning resource set of NUL.

The Positoining SRS Resource Set ID field is the identifier of the SRS positioning resource set to be activated or deactivated.

NUL (Normal Uplink) is general uplink, and SUL (Supplementary Uplink) is supplementary uplink. One serving cell may have only normal uplink or may have normal uplink and auxiliary uplink. Auxiliary uplink is set in a low frequency band in flight in general uplink to widen the uplink range of a cell.

The UE transmits a positioning SRS in an activated SRS positioning resource set. The terminal transmits the position SRS in SRS positioning resources belonging to the SRS positioning resource set by applying the transmission power control parameter of the SRS resource set. The SRS positioning resources occur periodically according to periodicityAndOffset-sp.

timeAlignmentTimerCommon is a timer applied when the UE performs random access for RRC connection establishment procedure and RRC connection re-establishment procedure. When the UE receives the RAR, it starts driving the timer, and stops driving the timer when contention fails.

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

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

BWP-DownlinkCommon is a configuration of the second downlink IBWP. It consists of sub-fields 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 a subcarrier spacing indicated in the MIB. The first IBWP is an IBWP indicated by MIB and receiving SIB1, and the second IBWP is an IBWP indicated by SIB1 and receiving SIB2, paging, random access response messages, and the like.

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

PDCCH-ConfigCommon is a cell specific PDCCH parameter for this BWP. 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. Indicates one of the predefined CORESET#0 configurations. ControlResourceSetZero included in MIB corresponds to first CORESET#0, and controlResourceSetZero included in PDCCH-ConfigCommon of servingCellConfigCommon of SIB1 corresponds to second CORESET#0.

searchSpaceZero is defined as an integer between 0 and 15. Indicates one of the predefined SS#0 configurations. searchSpaceZero included in MIB corresponds to 1st SS#0, and controlResourceSetZero included in PDCCH-ConfigCommon of servingCellConfigCommon of SIB1 corresponds to 2nd 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. The common SS may be used for paging reception, random access response reception, system information reception, and the like.

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

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

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

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

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

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

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

The tpc-SRS field enables and configures reception of group TPC commands for SRS. The tpc-SRS field includes the 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.

PDSCH-ConfigCommon consists of pdsch-TimeDomainAllocationList as the cell specific PDSCH parameter of this BWP. The pdsch-TimeDomainAllocationList is a list composed of a plurality of pdsch-TimeDomainAllocations.

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

pcch-Config is a configuration related to paging. It consists of sub-fields 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 sub-fields such as modificationPeriodCoeff indicating the length of the modification period.

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

FrequencyInfoUL-SIB is a basic parameter of an uplink carrier. It consists of sub-fields such as frequency band list and carrier bandwidth for each SCS.

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

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

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

The mcs-Table field indicates an MCS table to be used by the UE for PDSCH. If there is no field, the UE applies the 64QAM value. A value of 64QAM means an MCS table for 64QAM. A value of 256QAM means an MCS table for 256QAM.

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

prach-ConfigurationIndex is the PRACH configuration index. One PRACH configuration corresponds to pattern information on PRACH transmission opportunities in the time domain (information indicating that PRACH transmission is possible in which symbol in which slot of which radio frame) and the transmission format of the preamble.

msg1-FrequencyStart is an 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 PRBs of the corresponding carrier.

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

ra-ResponseWindow is the length of the random access response window represented by 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 UEs.

rsrp-ThresholdSSB is an SSB selection criterion. The UE performs random access by selecting a preamble corresponding to the selected SSB.

rsrp-ThresholdSSB-SUL is the SUL selection criterion. The UE selects an SUL carrier for random access based at least in part on this threshold.

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

push-ConfigCommon is a cell-specific PUSCH parameter of this BWP and consists of sub-fields such as push-TimeDomainAllocationList. The push-TimeDomainAllocationList is a list composed of a plurality of push-TimeDomainAllocations.

pushch-TimeDomainAllocation constitutes a time domain relationship between PDCCH and PUSCH. It consists of sub-fields such as K2 and startSymbolAndLength. K2 is the slot offset between DCI and scheduled PUSCH. startSymbolAndLength is an index representing a valid combination of start symbol and length.

IE PUSCH-Config is used to configure UE-specific PUSCH parameters applicable to a specific BWP.

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

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

The mcs-Table field indicates an MCS table to be used by the UE 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 activates 'intra-slot frequency hopping' and the interSlot value activates 'inter-slot frequency hopping'. If there is no field, no frequency hopping is constituted.

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

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

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

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

pucch-ConfigCommon is a cell specific PUCCH parameter for this BWP. It consists of sub-fields such as pucch-ResourceCommon and p0-norminal.

pucch-ResourceCommon is an index corresponding to a cell-specific PUCCH resource parameter. One index corresponds to a PUCCH format, a PUCCH time period, a PUCCH frequency period, a PUCCH code, and the like.

p0-normal is a power offset applied during PUCCH transmission. It is defined as an integer between -202 and 24 in increments of 2. 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 includes a timing list for a PDSCH given in DL ACK.

resourceSetToAddModList includes a list for adding a PUCCH resource set.

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

referenceSubcarrierSpacing is a reference SCS used to determine the time domain boundary in the UL-DL pattern.

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 indicates a period of a 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.

Operations of the terminal and the base station are as follows.

The terminal receives system information through the downlink channel of the first cell. System information includes a timeAlignmentTimer IE and one or two PUSCH-ConfigCommon IEs. Applying the timeAlignmentTimer IE included in the system information to the first timer. The terminal receives a random access response through the downlink channel of the first cell. The random access response includes a timing advance command field and a temporary C-RNTI field. The timing advance command field includes the first TA command. Apply the 1st TA command received from the RAR and start the 1st timer. If the UE Contention Resolution Identity of the MAC CE matches the CCCH SDU transmitted in Msg 3, the UE sets the C-RNTI to the temporary C-RNTI value received from the RAR.

Step of the terminal receiving the RRCSetup message from the base station. The RRCSetup message includes a radioBearerConfig field and a masterCell group field.

Step of the terminal receiving the RRCReconfiguration message from the base station. The RRCReconfiguration message includes an RNTI-Value IE for the first CS-RNTI, a plurality of configureGrantConfig IEs, a plurality of PUSCH-Config IEs, and a plurality of SRS-Config IEs. Each of the plurality of configureGrantConfig IEs is associated with an uplink BWP of NUL or an uplink BWP of SUL, each of the plurality of PUSCH-Config IEs is associated with an uplink BWP of NUL or an uplink BWP of SUL, and each of the plurality of PUSCH-Config IEs is associated with a plurality of SRS-Config IEs Each is associated with uplink BWP of NUL or uplink BWP of SUL.

Receiving, by a terminal, a MAC PDU from a base station based at least in part on a downlink assignment for a primary C-RNTI. If the MAC PDU includes the TAC MAC CE, applying the second TA command received from the TAC MAC CE and restarting the first timer by the terminal.

The terminal determines a first subframe and a first symbol based at least in part on a first ConfiguredGrantConfig IE selected from a plurality of configureGrantConfig IEs. The UE determines a second subframe and a second symbol based at least in part on the received dynamic grant for the first CS-RNTI.

The UE in RRC_CONNECTED performs initial uplink transmission for a grant configured in the first symbol of the first subframe based at least in part on the first p0-NominalWithoutGrant and the first p0 and the first dataScramblingIdentityPUSCH and the first frequencyHopping. Performing, by a terminal in RRC_CONNECTED, uplink retransmission in a second symbol of a second subframe based at least in part on the first p0-NominalWithoutGrant and the first p0 and the first dataScramblingIdentityPUSCH and the second frequency Hopping. The first p0-NominalWithoutGrant is included in the first PUSCH-Config. The first p0 is determined based at least in part on the first ConfiguredGrantConfig and the first PUSCH-Config. The first p0 is determined by the p0-PUSCH-Alpha field of the first ConfigurdGrantConfig and the corresponding p0 field of the first PUSCH-Config. The first dataScramblingIdentityPUSCH is included in the first PUSCH-Config. The first FrequencyHopping is included in the first ConfiguredGrantConfig. The second frequencyHopping is included in the first PUSCH-Config.

Receives an RRCRelease message for the terminal to switch the terminal from RRC_CONNECTED to RRC_INACTIVE. The RRCRlease message includes the SuspendConfig IE. The SuspendConfig IE includes the first IE group, the second IE group 1, the second IE group 2, and the third IE group. The first IE group includes the I-RNTI-Value IE, the ShortI-RNTI-Value IE, the pagingCycle IE, and the RAN-NotificationAreaInfo IE. The second IE group 1 is composed of an sdt-DRB-List field and an sdt-SRB2-Indication field. The second IE group 2 is composed of a cs-RNTI field and an sdt-MAC-PHY-CG-Config field. The cs-RNTI field includes the RNTI-Value IE for the second CS-RNTI. The sdt-MAC-PHY-CG-Config field includes a TimeAlignmentTimer IE, a BWP-Downlink-Dedicated-SDT IE, one or two BWP-Uplink-Dedicated-SDT IEs, and a CG-SDT-TA-ValidationConfig IE. The BWP-Downlink-Dedicated-SDT IE includes a PDCCH-Config IE and a PDSCH-Config IE. The BWP-Uplink-Dedicated-SDT IE includes a PUCCH-Config IE and a PUSCH-Config IE and one or more ConfiguredGrantConfig IEs. The ConfiguredGrantConfig IE is associated with the initial uplink BWP of NUL or the initial uplink BWP of SUL. The ConfiguredGrantConfig IE includes a timeDomainOffset field, a timeDomainAllocation field, a frequencyHopping field, and a p0-PUSCH-Alpha field. ConfiguredGrantConfig optionally includes an sdt-P0-PUSCH field. The p0-PUSCH-Alpha field includes an index indicating a first P0 value. The sdt-P0-PUSCH field includes a value indicating the second P0 value. If the sdt-P0-PUSCH field is included in configureGrantConfig IE, the second P0 value is applied.

The PUSCH-Config IE includes a dataScramblingIdentityPUSCH field, a push-PowerControl field, and a frequencyHopping field. The pushch-PowerControl field consists of the p0-AlphaSets field and the p0-NominalWithoutGrant field. The p0-AlphaSets field includes a plurality of P0-PUSCH-AlphaSet IEs. The P0-PUSCH-AlphaSet IE includes a p0-PUSCH-AlphaSetId field and a p0 field.

The third IE group includes the SRS-Config IE of the srs-Config field, the BWP IE of the bwp field, the TimeAlignmentTimer IE of the srs-TimeAlignmentTimer field, and the RNTI-Value IE of the c-RNTIforSRSActivation field. The BWP IE represents the frequency domain location and bandwidth and subcarrier spacing for SRS transmission during the RRC_INACTIVE state. The subframe for the configured grant is determined based at least in part on the timeDomainOffset IE. The symbol for the configured grant is determined based at least in part on the timedomainAllocation IE and the HARQ process ID for the configured grant is determined based at least in part on the nrofHARQ-Processes IE.

If the RRCRlease message (or suspendConfig IE) includes the first IE group, does not include the second IE group, and does not include the third IE group, the first set of operations is performed.

The first set of actions consists of: Step to apply the received suspendConfig. Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Release the SRS-Resource instance configured in SRS-Config. Release the SchedulingRequestResourceConfig instance configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells. Clear all PUSCH resources for semi-permanent CSI reporting. Storing the C-RNTI used in the source PCell in the UE inactive AS context. Enter RRC_INACTIVE state. Perform cell selection.

If the RRCRlease message (or suspendConfig IE) includes the first IE group and the second IE group and does not include the third IE group, the second set of actions is performed. The second set of actions consists of the following. Applying the first IE group of the received suspendConfig. Identifying a radio bearer to be configured for SDT based at least in part on the second IE group 1 . Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Release SRS-Resource instances configured in SRS-Config. Release SchedulingRequestResourceConfig instances configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells except configured uplink grants configured based on the second IE group 2 of the received RRCRlease message. Clearing all PUSCH resources for semi-permanent CSI reporting. configuring a grant resource configured based at least in part on the second IE group2. Start cg-SDT-TimeAlignmentTimer if included in the second part of the received SuspendConfig. Store the C-RNTI used by the source PCell in the UE non-active AS context. Storing the CS-RNTI received in SuspendConfig (if received) or used (if used and not received) in the source PCell in the UE inactive AS context. Enter RRC_INACTIVE state. Perform cell selection. Alternatively, when the cell receiving the RRCRlease message is selected, the second IE group is applied after cell selection.

If the RRCRlease message (or suspendConfig IE) includes the first IE group and the third IE group and does not include the second IE group, the third set of actions is performed. The third set of actions consists of the following. Applying the first IE group of the received suspendConfig. Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Releasing SRS-Resource instances configured in SRS-Config except for SRS-Resources configured based on the third IE group in the received RRCRlease. Release the SchedulingRequestResourceConfig instance configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells. Deleting all PUSCH resources for semi-permanent CSI reporting. Configuring an SRS resource based at least in part on the third IE group. Start srs-TimeAlignmentTimer. Storing the C-RNTI received in SuspendConfig (if received) and the C-RNTI used in the source PCell (if not received) in the UE inactive AS context. Enter RRC_INACTIVE state. Perform cell selection.

Alternatively, when the cell receiving the RRCRelease message is selected, the third IE group is applied after cell selection. If the RRCeRlease message (or suspendConfig IE) includes the first IE group, the second IE group, and the third IE group, the fourth set of operations is performed. The fourth set of actions consists of: Applying the first IE group of the received suspendConfig. Identifying a radio bearer to be configured for SDT based at least in part on the second IE group 1 . Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Releasing the SRS-Resource instances configured in the SRS-Config except for the SRS-Resource configured based on the third IE group in the received RRCRelease. Release the SchedulingRequestResourceConfig instance configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells except configured uplink grants configured based on the second IE group 2 of the received RRCRelease message. Clearing all PUSCH resources for semi-permanent CSI reporting. Applying the second IE group of the received suspendConfig. Applying a third IE group of the received suspendConfig. Configuring SRS resources based at least in part on the third IE group. Start srs-TimeAlignmentTimer. configuring a grant resource configured based at least in part on the second IE group2. Start cg-SDT-TimeAlignmentTimer if included in the second part of the received SuspendConfig. Storing the C-RNTI received in SuspendConfig (if received) and the C-RNTI used in the source PCell in the UE inactive AS context. Storing the CS-RNTI received in SuspendConfig (if received) or used (if used and not received) in the source PCell in the UE inactive AS context. Enter RRC_INACTIVE state. Perform cell selection. Alternatively, when the cell receiving the RRCRelease message is selected, the second IE group and the third IE group are applied after cell selection.

The terminal selects a second cell based at least in part on RSRP and RSRQ. The UE receives MIB and SIB1 from the downlink channel of the second cell. The terminal determines whether the second cell is different from the first cell based at least in part on the received SIB1. If the second cell is different from the first cell, considering that cg-SDT-TimeAlignmentTimer has expired, the terminal releases the configured grant resource. If the second cell is different from the first cell, the UE considers that the srs-TimeAlignmentTimer has expired and releases the SRS resource. The terminal determines a third subframe and a third symbol for initial uplink transmission based at least in part on the ConfiguredGrantConfig IE included in the second IE group 2. Determining, by the terminal, a fourth subframe and a fourth symbol for uplink retransmission based at least in part on the dynamic grant received for the second CS-RNTI in RRC_INACTIVE. The second CS-RNTI is included in the suspendConfig extension part of the RRCRlease message.

When certain conditions are met, the RRC_INACTIVE UE initiates the SDT procedure. When the SDT procedure is initiated, select between SUL and NUL based at least in part on rsrp-ThresholdSSB-SUL in RACH-ConfigCommon. Validate the TA of the initial CG-SDT transmission based at least in part on cg-SDT-Config-Initial-BWP-SUL if SUL was selected, and based at least in part on cg-SDT-Config-Initial-BWP-NUL if NUL was selected Based on , the TA of the initial CG-SDT transmission is verified. The RACH-ConfigCommon is included in SIB1. The SIB1 is received in the second cell. this is used The cg-SDT-Config-Initial-BWP-SUL and cg-SDT-Config-Initial-BWP-NUL included in the extended part of SuspendConfig of RRCRelease received from the first cell are included in SuspendConfig of the RRCRelease message. The RRCRelease message is received in the primary cell.

The UE in the RRC_INACTIVE state monitors the PDCCH based at least in part on the first discovery interval indicated in the PDCCH-ConfigCommon during the first time interval. During the second time period, the PDCCH is monitored based at least in part on the second discovery period indicated in PDCCH-ConfigCommon, and during the third time period, the PDCCH is monitored based at least in part on the third discovery period indicated in PDCCH-Config. . The first time period is a time period during which RA-SDT and CG-SDT are not in progress. That is, from the time of entering the RRC_INACTIVE state to the time of SDT triggering. The second time period is a period in which RA-SDT is performed. That is, it is a period from the time when the SDT is started and the random access preamble is transmitted to the time when the RA-SDT is completed. The third time period is a period in which CG-SDT proceeds. That is, it is a period from the time when SDT is initiated and initial transmission is performed with the configured grant to the time when CG-SDT is completed.

The PDCCH-ConfigCommon is included in SIB1. The SIB1 is received in the second cell. The PDCCH-Config is included in SuspendConfig of the RRCRelease message. The RRCRelease message is received in the first cell. The first search interval is indicated in PagingSearchSpace of the PDCCH-ConfigCommon. The second search interval is indicated in ra-searchSpace of the PDCCH-ConfigCommon. The third discovery interval is indicated in the PDCCH-Config. The first search interval and the search interval are joint search intervals. The third discovery period is a terminal-specific discovery period.

The UE in the RRC_INACTIVE state monitors the PDCCH based at least in part on the first control resource set indicated by the PDCCH-ConfigCommon during the first time period. During the second time period, the PDCCH is monitored based at least in part on the first set of control resources indicated in PDCCH-ConfigCommon, and the PDCCH is monitored based at least in part on the second set of control resources indicated in PDCCH-Config during the third time period. watch over

The first control resource set is CORESET#0 and the second control resource set is a control resource set indicated in PDCCH-Config. PDCCH-Config of RRCReconfiguration may include a plurality of control resource sets. PDCCH-Config of RRCRelease may include one control resource set.

RRC_INACTIVE The UE monitors the PDCCH based at least partially on the P-RNTI during the first time period. The RRC_INACTIVE UE monitors the PDCCH during the second time interval at least partially based on the second C-RNTI. RRC_INACTIVE The UE monitors the PDCCH at least partially based on the second CS-RNTI during the third time period. The second C-RNTI is indicated by the RRCRelease message. The third C-RNTI is indicated by the RRCRelease message. The UE of RRC_INACTIVE, in the third symbol of the third subframe based at least in part on the third p0-NominalWithoutGrant and the third p0 and the third dataScramblingIdentityPUSCH and the third frequencyHopping Perform initial uplink transmission for configured grants. The UE of RRC_INACTIVE performs uplink retransmission for the grant configured in the fourth symbol of the fourth subframe based at least in part on the third p0-NominalWithoutGrant and the third p0 and the third dataScramblingIdentityPUSCH and the fourth frequencyHopping. The third p0-NominalWithoutGrant is included in the second PUSCH-Config. The third p0 is at least partially the value indicated in the p0-PUSCH-alpha field and the presence of the sdt-P0-PUSCH field of the second IE group and the value indicated in the sdt-P0-PUSCH field and the corresponding p0 of the second PUSCH-Config. is determined based on

The third dataScramblingIdentityPUSCH is included in the second PUSCH-Config. The third frequencyHopping is included in the second ConfiguredGrantConfig IE of the second IE group 2. The fourth frequencyHopping is included in the second PUSCH-Config.

Receiving, by the terminal, a MAC PDU from the base station based at least in part on the downlink allocation for the first C-RNTI. The MAC PDU includes an SP positioning SRS activation/deactivation MAC CE and RRCRlease message. When the A/D field is set to 1, the UE activates the positioning SRS resource set at the second SRS activation time based at least in part on SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received. The activation time of the second SRS is slot n + k + m. The HARQ ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n. k is the number of second slots corresponding to 60 ms. Alternatively, k is the number of slots determined based at least in part on when the SRS-Config included in the RRCRlease message is applied (or received). The second slot is a slot of UL BWP configured by the BWP field of the third IE group. The length of the second slot is determined based at least in part on the subcarrierSpacing IE included in the third IE group. SRS activation information group 2 includes a SUL field and a positioning SRS resource set ID. The SRS resource is activated in the cell in which the RRCRlease message is received and in the UL BWP configured by the RRCRlease message.

Receiving, by a terminal, a MAC PDU from a base station based at least in part on a downlink assignment for a second C-RNTI. The MAC PDU contains the SP positioning SRS activation/deactivation MAC CE. When the terminal has the A/D field set to 1 and the third timer is running at the time of activating the third SRS, the third SRS is based at least in part on SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received. Activate the positioning SRS resource set at the time of activation. When the A/D field is set to 0, the UE deactivates the positioning SRS resource set at the third SRS activation time based at least in part on SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received. The third SRS activation time is slot n + h. The HARQ ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n. h is the number of second slots corresponding to 3 ms. The second slot is a slot of the UL BWP configured by the third IE group. The length of the second slot is determined based at least in part on the subcarrierSpacing IE included in the third IE group. SRS activation information group 2 includes a SUL field and a positioning SRS resource set ID. The SRS resource is activated in the cell in which the RRCRlease message is received and in the uplink indicated by the SUL field and the UL BWP configured by the RRCRlease message.

Receiving, by a terminal, a MAC PDU from a base station based at least in part on a downlink assignment. The MAC PDU includes SP positioning SRS activation/deactivation MAC CE and RRCRlease messages. When the UE has the A/D field set to 1, the third timer is running at the third SRS activation time, and the MAC PDU is received for the second C-RNTI, the SRS of the received SP Positioning SRS activation/deactivation MAC CE The positioning SRS resource set is activated at a third SRS activation time based at least in part on activation information group 2. When the UE has the A/D field set to 1 and the MAC PDU is received for the first C-RNTI, the second SRS activation information group 2 of the received SP Positioning SRS activation/deactivation MAC CE is at least partially based on the received MAC PDU. Activate the positioning SRS resource set at the time of SRS activation.

Receiving, by a terminal, a MAC PDU from a base station based at least in part on a downlink assignment for a primary C-RNTI. When the UE includes the SP positioning SRS activation/deactivation MAC CE in the MAC PDU and the A/D field is set to 1, the UE performs a first step based at least in part on SRS activation information group 1 of the SP positioning SRS activation/deactivation MAC CE received when the A/D field is set to 1. Positioning SRS resource set active at the time of SRS activation. When the UE includes the SP positioning SRS activation/deactivation MAC CE in the MAC PDU and the A/D field is set to 0, the terminal performs a first step based at least in part on SRS activation information group 1 of the SP positioning SRS activation/deactivation MAC CE received when the A/D field is set to 0. Deactivation of the positioning SRS resource set at the time of SRS activation. The first SRS activation time is slot n + m. The HARQ ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n. m is the number of first slots corresponding to 3 ms. The first slot is a slot of a currently activated UL BWP. SRS activation information group 1 includes a cell ID field of the positioning SRS resource set, a BWP ID and SUL field of the positioning SRS resource set, and a positioning SRS resource set ID. The SRS resource is activated in the cell indicated by the cell ID of the positioning SRS resource set, the uplink indicated by the SUL field, and the UL BWP indicated by the BWP ID of the positioning SRS resource set. If the cell, the TA of the initial CG-SDT transmission is verified based at least in part on the first downlink path loss reference RSRP value and the cg-SDT-RSRP-ChangeThreshold and the second downlink path loss reference RSRP value.

The first downlink path loss criterion RSRP value is the value of the first cell at the time when the second timer is configured (or starts, or RRCRlease message including cg-SDT-TimeAlignmentTimer is received or RRCRlease message including second ConfiguredGrantConfig IE is received) This is the downlink path loss reference RSRP value. The second downlink path loss reference RSRP value is the downlink path loss reference RSRP value of the second cell.

The ConfiguredGrantConfig IE includes a periodicity field, a timeDomainOffset field, a timeDomainAllocation field, a frequencyHopping field, and p0-PUSCH-Alpha. The first ConfiguredGrantConfig IE is selected from a plurality of ConfiguredGrantConfig IEs included in the RRCReconfiguration message. The first ConfiguredGrantConfig IE is associated with an active uplink BWP. The first ConfiguredGrantConfig is used in RRC_CONNECTED. The first ConfiguredGrantConfig IE includes a periodicity field, a timeDomainOffset field, a timeDomainAllocation field, a frequencyHopping field, and a p0-PUSCH-Alpha field. The second ConfiguredGrantConfig IE is included in the SuspendConfig extension part of the RRCRlease message. The second ConfiguredGrantConfig IE is associated with the initial uplink BWP. The second ConfiguredGrantConfig is used in RRC_INACTIVE. The second ConfiguredGrantConfig IE includes a periodicity field, a timeDomainOffset field, a timeDomainAllocation field, a frequencyHopping field, a p0-PUSCH-Alpha field, and an sdt-P0-PUSCH field.

The first subframe is determined based at least in part on a value indicated in the timeDomainOffset field of the first ConfiguredGrantConfig. The first symbol is determined based at least in part on a value indicated in the timeDomainAllocation field of the first ConfiguredGrantConfig. The third subframe is determined based at least in part on a value indicated in the timeDomainOffset field of the second ConfiguredGrantConfig. The third symbol is determined based at least in part on a value indicated in the timeDomainAllocation field of the second ConfiguredGrantConfig.

The second subframe is determined based at least in part on the received dynamic grant for the first CS-RNTI. The second symbol is determined based at least in part on the received dynamic grant for the first CS-RNTI. The fourth subframe is based at least in part on the dynamic grant received for the second CS-RNTI (if the second CS-RNTI is available) or the third CS-RNTI (if the second CS-RNTI is unavailable). It is decided. The fourth symbol is determined based at least in part on the received dynamic grant for the 2nd CS-RNTI (if the 2nd CS-RNTI is available) or the 3rd CS-RNTI (if the 2nd CS-RNTI is not available) do. The p0-PUSCH-Alpha field includes an index indicating a P0 value. The first PUSCH-Config IE is selected from a plurality of PUSCH-Config IEs included in the RRCReconfiguration message. The first PUSCH-Config IE is associated with an active uplink BWP. The first PUSCH-Config IE is used in RRC_CONNECTED. The first PUSCH-Config IE includes a dataScramblingIdentityPUSCH field, a frequencyHopping field, a p0-AlphaSets field, and a p0-NominalWithoutGrant field. The second PUSCH-Config IE is included in the RRCRlease message. The second PUSCH-Config IE is associated with the initial uplink BWP. The second PUSCH-Config IE is used in RRC_INACTIVE. The second PUSCH-Config IE includes a dataScramblingIdentityPUSCH field, a frequencyHopping field, a p0-AlphaSets field, and a p0-NominalWithoutGrant field.

The p0-AlphaSets field includes a plurality of p0-PUSCH-AlphaSetId fields and a plurality of p0 fields. The p0 field includes a p0 value for PUSCH in units of 1 dB. Each p0-PUSCH-AlphaSetId is associated with one p0.

The RNTI-Value IE contains an integer representing the wireless network temporary identity. The first CS-RNTI is included in the RRCReconfiguration message. The first CS-RNTI is used in the RRC_CONNECTED state. One 1st CS-RNTI for MCG is included in the RRCReconfiguration message. The first CS-RNTI is used in the RRC_CONNECTED state. The first C-RNTI is determined by the temporary C-RNTI received from the RAR at the time of receiving the UE Contention Resolution Identity MAC CE. The first C-RNTI is used in the RRC_CONNECTED state. The second CS-RNTI is included in the extension part of the SuspendConfig IE in the RRCRlease message. One CS-RNTI is included in the RRCRlease message. The second CS-RNTI is used in the RRC_INACTIVE state. The second C-RNTI is included in the extension part of the SuspendConfig IE in the RRCRlease message. One C-RNTI is included in the RRCRlease message. The second C-RNTI is used in the RRC_INACTIVE state. The third CS-RNTI is a CS-RNTI used in the source PCell and stored in the UE Inactive AS Context. The third CS-RNTI is used in the RRC_INACTIVE state. The third C-RNTI is a C-RNTI used in the source PCell and stored in the UE Inactive AS Context. The third C-RNTI is used in the RRC_INACTIVE state.

The first IE group includes a fullI-RNTI field, a shortI-RNTI field, a ran-PagingCycle field, and a ran-NotificationAreaInfo field. The second IE group 1 includes an sdt-DRB-List field and an sdt-SRB2-Indication field. The 2nd IE group 2 includes the cg-SDT-TimeAlignmentTimer field, the cg-SDT-TA-ValidationConfig field, the cg-SDT-Config-Initial-BWP-NUL field, the cg-SDT-Config-Initial-BWP-SUL field, and the cg- SDT-Config-Initial-BWP-DL field and CS-RNTI field are included. The cg-SDT-TimeAlignmentTimer field includes a TimeAlignmentTimer IE for the second timer. The cg-SDT-TA-ValidationConfig field includes the cg-SDT-TA-ValidityThresholdSSB field. The cg-SDT-TA-ValidityThresholdSSB field represents an RSRP threshold for validation of a CG-SDT resource. The cg-SDT-Config-Initial-BWP-NUL field includes PUCCH-Config IE, PUSCH-Config IE and ConfiguredGrantConfig IE. cg-SDT-Config-Initial-BWP-NUL is for the initial uplink BWP of normal uplink. If NUL is selected, cg-SDT-Config-Initial-BWP-NUL is used in RRC_INACTIVE. The cg-SDT-Config-Initial-BWP-SUL field includes PUCCH-Config IE, PUSCH-Config IE and ConfiguredGrantConfig IE. cg-SDT-Config-Initial-BWP-SUL is for the initial uplink BWP of the secondary uplink. cg-SDT-Config-Initial-BWP-SUL is used in RRC_INACTIVE when SUL is selected. The cg-SDT-Config-Initial-BWP-DL field includes PDCCH-Config IE and PDSCH-Config IE. cg-SDT-Config-Initial-BWP-DL is for initial downlink BWP and is used in RRC_INACTIVE. The CS-RNTI field includes the RNTI-Value IE for the second CS-RNTI. The third IE group is included in the third part of the SuspendConfig IE. The third part is the extension part of SuspendConfig. The third IE group includes a srs-Config field, a bwp field, a srs-TimeAlignmnetTimer field, a srs-PosRRC-ValidationConfig field, and a C-RNTI field. The SuspendConfig IE includes a first IE group, a second IE group 1, a second IE group 2, and a third IE group. The first IE group is included in the first part of the SuspendConfig IE. The first part is the unextended part of SuspendConfig. The second IE group 1 is included in the second part of the SuspendConfig IE. The second part is the first extension part of SuspendConfig.

The second IE group 2 is included in the second part of the SuspendConfig IE. The second part is the second extended part of SuspendConfig. The first extension portion is located before the second extension portion. timAlignmentTimer IE points to one of multiple numeric values or a non-numeric value representing infinity. The first TA command is included in the RAR. The first TA command indicates an absolute quantity. The first TA command is received based at least in part on the RA-RNTI. The second TA command is included in the TAC MAC CE. The second TA command indicates a relative amount. The 2nd TA command is a 2nd C-RNTI in RRC_INACTIVE (when the 2nd C-RNTI is received in the extended part of the suspendConfig IE in the RRCRlease message) or a 2nd CS-RNTI (when the 2nd C-RNTI is suspendConfig in the RRCRlease message) not received in the extended part of the IE and the second CS-RNTI is received based at least in part on the suspendConfig IE extended part in the RRCRlease message) or the tertiary C-RNTI, and in RRC_CONNTECT the first C-RNTI Received based at least in part on the RNTI.

The terminal applies the value indicated in the timeAlignmentTimer IE of system information block 1 to the first timer. The UE applies the 1st TA command received from the RAR and starts the 1st timer. Receiving, by a terminal, a MAC PDU based at least in part on a downlink assignment for a first C-RNTI from a base station. If the MAC PDU includes the TAC MAC CE, the UE applies the second TA command received from the TAC MAC CE and restarts 1 timer. When the first timer expires, the UE releases the first resource. The first resource is a PUCCH-CSI-Resources configured in CSI-ReportConfig, an SRS-Resource instance configured in SRS-Config, a SchedulingRequestResourceConfig instance configured in PUCCH-Config, configured downlink assignment, configured uplink grant, and semi-permanent CSI reporting. Includes all PUSCH resources.

The first resource is configured by the RRCReconfiguration message and used in RRC_CONNECTED.

The first resource is configured in the first uplink BWP. The first uplink BWP is the active uplink BWP.

The value indicated in the timeAlignmentTimer IE of the cg-sdt-TimeAlignmentTimer field of the received RRCRlease is applied to the second timer, and the terminal starts the second timer

Receiving, by a terminal, a MAC PDU based at least in part on a downlink assignment for a second CS-RNTI from a base station.

When the MAC PDU includes the TAC MAC CE, the UE applying the second TA command received from the TAC MAC CE and restarting the second timer.

Release the second resource when the second timer expires. The second resource includes a configured grant configured by the second IE group2. The second resource is configured by RRCRlease and used in RRC_INACTIVE. The second resource is configured in the second uplink BWP. The second uplink BWP is the initial uplink BWP. The value indicated in the timeAlignmentTimer IE of the srs-TimeAlignmentTimer field of the received RRCRlease is applied to the third timer, and the terminal starts the third timer. Receiving, by a terminal, a MAC PDU based at least in part on a downlink assignment for a second C-RNTI from a base station.

If the MAC PDU includes the TAC MAC CE, applying the second TA command received in the TAC MAC CE and restarting the third timer by the terminal. Release the third resource when the third timer expires. The third resource includes an SRS-Resource instance (individual SRS resource configured in SRS-Config) configured in SRS-Config of the third IE group. The third resource is configured by RRCRlease and used in RRC_INACTIVE. A third resource is configured in the third uplink BWP. The third uplink BWP is configured by the BWP IE included in the third IE group of the RRCRlease message. Receiving, by a terminal, a MAC PDU from a base station based at least in part on the downlink assignment. If the MAC PDU includes the TAC MAC CE and the downlink assignment is for the second C-RNTI and the UE is in the RRC_INACTIVE state, applying the second TA command received from the TAC MAC CE and restarting the plurality of timers by the UE . The plurality of timers include a first timer (when driving), a second timer (when driving), and a third timer (when driving). If the MAC PDU includes the TAC MAC CE and the downlink assignment is for the first C-RNTI and the UE is in the RRC_CONNECTED state, applying the second TA command received from the TAC MAC CE and restarting the first timer by the UE .

RRC_CONNECTED UE performs initial uplink transmission for the grant configured in the first symbol of the first subframe. RRC_CONNECTED UE performs initial uplink transmission for the grant configured in the first symbol of the first subframe. The RRC_CONNECTED UE performs uplink retransmission in the second symbol of the second subframe. The UE in RRC_CONNECTED performs an initial uplink transmission for the grant configured in the first symbol of the first subframe based at least in part on the first p0. The UE in RRC_CONNECTED performing uplink retransmission in a second symbol of a second subframe based at least in part on the first p0.

The first p0 is determined based at least in part on the first ConfiguredGrantConfig and the first PUSCH-Config. The first p0 is determined by the p0-PUSCH-Alpha field of the first ConfigurdGrantConfig and the corresponding p0 field in the first PUSCH-Config.

RRC_CONNECTED UE, if the positioning SRS is activated, the fourth UL BWP is activated, and the first timer associated with the fourth cell is running, SRS transmission based at least in part on the positioning SRS resource set in the fourth UL BWP of the fourth cell Do it.

The fourth UL BWP is a BWP indicated in the BWP ID field of the SP Positioning SRS Activation/Deactivation MAC CE. The common configuration of the 4th UL BWP is provided in the RRCReconfiguration message and the dedicated configuration of the 4th UL BWP is provided in the RRCReconfiguration. PUCCH-ConfigCommon and PUSCH-ConfigCommon of the 4th UL BWP are provided in the 1st DL message, and PUCCH-Config and PUSCH-Config of the 4th UL BWP are provided in RRCReconfiguration or RRCSetup. The fourth cell is a cell indicated in the Cell ID field of the SP Positioning SRS Activation/Deactivation MAC CE.

RRC_INACTIVE UE performing SRS transmission based at least in part on the positioning SRS resource set in the third UL BWP of the first cell when the positioning SRS is activated and the third timer is running.

RRC_INACTIVE UE performing SRS transmission based at least in part on a positioning SRS resource set in a third UL BWP of a first cell when the type of positioning SRS is periodic and a third timer is running

The third UL BWP is the initial UL BWP. The common configuration of the 3rd UL BWP is provided in the RRCReconfiguration message and the dedicated configuration of the 3rd UL BWP is provided in the RRCRlease. PUCCH-ConfigCommon and PUSCH-ConfigCommon of the third UL BWP are provided in the first DL message, and PUCCH-Config and PUSCH-Config of the third UL BWP are provided in the second DL message. The first DL message is SIB1 or RRCSetup or RRCReconfiguration. The second DL message is RRCRlease. The first cell is a cell that receives the first RRCRlease message. The first RRCRlease message includes the second IE group 2 or the third IE group.

The base station transmits system information through the downlink channel of the first cell. System information includes a timeAlignmentTimer IE and one or two PUSCH-ConfigCommon IEs. The base station transmits a random access response through the downlink channel of the first cell. The random access response includes a timing advance command field and a temporary C-RNTI field. The timing advance command field includes the first TA command.

Transmitting, by the base station, an RRCSetup message to the terminal. The RRCSetup message includes a radioBearerConfig field and a masterCell group field. Transmitting, by the base station, an RRCReconfiguration message to the terminal. The RRCReconfiguration message includes an RNTI-Value IE for the first CS-RNTI, a plurality of configureGrantConfig IEs, a plurality of PUSCH-Config IEs, and a plurality of SRS-Config IEs. Each of the plurality of configureGrantConfig IEs is associated with an uplink BWP of NUL or an uplink BWP of SUL. Each of the plurality of PUSCH-Config IEs is associated with an uplink BWP of NUL or an uplink BWP of SUL. Each of the plurality of SRS-Config IEs is associated with an uplink BWP of NUL or an uplink BWP of SUL.

Transmitting, by the base station, a MAC PDU to the terminal based at least in part on the downlink assignment for the first C-RNTI. Applying a second TA command transmitted from the TAC MAC CE when the MAC PDU includes the TAC MAC CE, and restarting the first timer by the base station.

The base station determines a first subframe and a first symbol based at least in part on a first ConfiguredGrantConfig IE selected from the plurality of configureGrantConfig IEs. The base station determines a second subframe and a second symbol based at least in part on the received dynamic grant for the first CS-RNTI.

For an RRC_CONNECTED terminal, the base station performs initial uplink reception for a grant configured in the first symbol of the first subframe based at least in part on the first p0-NominalWithoutGrant and the first p0 and the first dataScramblingIdentityPUSCH and the first frequencyHopping. For an RRC_CONNECTED terminal, the base station performing uplink reception on a second symbol of a second subframe based at least in part on the first p0-NominalWithoutGrant and the first p0 and the first dataScramblingIdentityPUSCH and the second frequency Hopping.

The first p0-NominalWithoutGrant is included in the first PUSCH-Config. The first p0 is determined based at least in part on the first ConfiguredGrantConfig and the first PUSCH-Config. The first p0 is determined by the p0-PUSCH-Alpha field of the first ConfigurdGrantConfig and the corresponding p0 field of the first PUSCH-Config. The first dataScramblingIdentityPUSCH is included in the first PUSCH-Config.

The first FrequencyHopping is included in the first ConfiguredGrantConfig. The second frequencyHopping is included in the first PUSCH-Config. The base station transmits an RRCRelease message to switch the terminal from RRC_CONNECTED to RRC_INACTIVE.

The RRCRlease message includes the SuspendConfig IE. The SuspendConfig IE includes the first IE group, the second IE group 1, the second IE group 2, and the third IE group.

If the RRCRlease message (or suspendConfig IE) includes the first IE group, does not include the second IE group, and does not include the third IE group, the first set of operations is performed. The first set of actions consists of: Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Release the SRS-Resource instance configured in SRS-Config. Release the SchedulingRequestResourceConfig instance configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells. Clear all PUSCH resources for semi-permanent CSI reporting. Storing the C-RNTI used in the source PCell in the UE inactive AS context.

If the RRCRlease message (or suspendConfig IE) includes the first IE group and the second IE group and does not include the third IE group, the second set of operations is performed. The second set of actions consists of: Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Release the SRS-Resource instance configured in SRS-Config. Release the SchedulingRequestResourceConfig instance configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells except configured uplink grants configured based on the second IE group 2 of the received RRCRlease message. Clearing all PUSCH resources for semi-permanent CSI reporting. configuring a grant resource configured based at least in part on the second IE group2. Start cg-SDT-TimeAlignmentTimer if included in the second part of the received SuspendConfig. Store the C-RNTI used by the source PCell in the UE non-active AS context. Storing the CS-RNTI sent in SuspendConfig (if received) or used (if used and not sent) in the source PCell to the UE inactive AS context.

If the RRCRlease message (or suspendConfig IE) includes the first IE group and the third IE group and does not include the second IE group, the third set of operations is performed. The third set of actions consists of: Applying the first IE group of the received suspendConfig. Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Releasing SRS-Resource instances configured in SRS-Config except for SRS-Resources configured based on the third IE group in the received RRCRlease. Release the SchedulingRequestResourceConfig instance configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells. Deleting all PUSCH resources for semi-permanent CSI reporting. Configuring an SRS resource based at least in part on the third IE group. Start srs-TimeAlignmentTimer. Storing the C-RNTI received in SuspendConfig (if received) and the C-RNTI used in the source PCell (if not transmitted) in the UE inactive AS context.

If the RRCRlease message (or suspendConfig IE) includes the first IE group, the second IE group, and the third IE group, the fourth set of operations is performed. The fourth set of operations consists of the following. Stop all timers related to the MAC function. Release PUCCH-CSI-Resources configured in CSI-ReportConfig. Releasing SRS-Resource instances configured in SRS-Config except for SRS-Resources configured based on the third IE group in the received RRCRlease. Release the SchedulingRequestResourceConfig instance configured in PUCCH-Config. Clearing configured downlink assignments and configured uplink grants in all BWPs of all serving cells except configured uplink grants configured based on the second IE group 2 of the received RRCRlease message. Clearing all PUSCH resources for semi-permanent CSI reporting. Applying the second IE group of the received suspendConfig. Applying a third IE group of the received suspendConfig. Configuring SRS resources based at least in part on the third IE group. Start srs-TimeAlignmentTimer. configuring a grant resource configured based at least in part on the second IE group2. Start cg-SDT-TimeAlignmentTimer if included in the second part of the received SuspendConfig. Storing the C-RNTI received in SuspendConfig (if received) and the C-RNTI used in the source PCell in the UE inactive AS context. Storing the CS-RNTI sent in SuspendConfig (if received) or used (if used and not sent) in the source PCell to the UE inactive AS context.

The base station transmits MIB and SIB1 through the downlink channel of the second cell. The base station determines a third subframe and a third symbol for initial uplink reception based at least in part on the ConfiguredGrantConfig IE included in the second IE group2. Determining, by the base station, a fourth subframe and a fourth symbol for uplink reception based at least in part on a received dynamic grant for a second CS-RNTI in RRC_INACTIVE. The second CS-RNTI is included in the suspendConfig extension part of the RRCRlease message.

For an RRC_INACTIVE terminal, the base station performs initial uplink reception for a grant configured in the third symbol of the third subframe based at least in part on the third p0-NominalWithoutGrant and the third p0 and the third dataScramblingIdentityPUSCH and the third frequencyHopping. Performing, by the base station, uplink reception for a grant configured in a fourth symbol of a fourth subframe based at least in part on a third p0-NominalWithoutGrant, a third p0 and a third dataScramblingIdentityPUSCH, and a fourth frequencyHopping for an RRC_INACTIVE UE. .

The third p0-NominalWithoutGrant is included in the second PUSCH-Config. The third p0 is at least partially the value indicated in the p0-PUSCH-alpha field and the presence of the sdt-P0-PUSCH field of the second IE group and the value indicated in the sdt-P0-PUSCH field and the corresponding p0 of the second PUSCH-Config. is determined based on

The third dataScramblingIdentityPUSCH is included in the second PUSCH-Config. The third frequencyHopping is included in the second ConfiguredGrantConfig IE of the second IE group 2. The fourth frequencyHopping is included in the second PUSCH-Config.

Transmitting, by the base station, a MAC PDU to the terminal based at least in part on the downlink assignment for the first C-RNTI. The MAC PDU includes SP positioning SRS activation/deactivation MAC CE and RRCRlease messages. The base station activates the positioning SRS resource set at the second SRS activation time point based at least in part on the SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received when the A/D field is set to 1. The activation time of the second SRS is slot n + k + m. A HARQ ACK corresponding to the PDSCH carrying an activation command is received in slot n. k is the number of second slots corresponding to 60 ms. Alternatively, k is the number of slots determined based at least in part on when the SRS-Config included in the RRCRlease message is applied (or transmitted). The second slot is a slot of UL BWP configured by the BWP field of the third IE group. The length of the second slot is determined based at least in part on the subcarrierSpacing IE included in the third IE group. SRS activation information group 2 includes a SUL field and a positioning SRS resource set ID. The SRS resource is activated in the cell in which the RRCRlease message is received and in the UL BWP configured by the RRCRlease message.

Transmitting, by the base station, a MAC PDU to the terminal based at least in part on the downlink assignment for the second C-RNTI. The MAC PDU contains the SP positioning SRS activation/deactivation MAC CE. The base station, when the A/D field is set to 1 and the third timer is running at the time of activating the third SRS, the third SRS is based at least in part on SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received. Activate the positioning SRS resource set at the time of activation. The base station deactivates the positioning SRS resource set at the third SRS activation time based at least in part on SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received when the A/D field is set to 0. The third SRS activation time is slot n + h. A HARQ ACK corresponding to the PDSCH carrying an activation command is received in slot n. h is the number of second slots corresponding to 3 ms. The second slot is a slot of the UL BWP configured by the third IE group. The length of the second slot is determined based at least in part on the subcarrierSpacing IE included in the third IE group. SRS activation information group 2 includes a SUL field and a positioning SRS resource set ID. The SRS resource is activated in the cell in which the RRCRlease message is received and in the UL BWP configured by the RRCRlease message.

Transmitting, by the base station, a MAC PDU to the terminal based at least in part on the downlink assignment. The MAC PDU includes SP positioning SRS activation/deactivation MAC CE and RRCRlease messages. The base station, when the A/D field is set to 1, the third timer is running at the third SRS activation time, and the MAC PDU is received for the second C-RNTI, the SRS of the received SP Positioning SRS activation/deactivation MAC CE The positioning SRS resource set is activated at a third SRS activation time based at least in part on activation information group 2. The base station, when the A / D field is set to 1 and the MAC PDU is received for the first C-RNTI, based at least in part on the SRS activation information group 2 of the SP Positioning SRS activation / deactivation MAC CE received, the second Activate the positioning SRS resource set at the time of SRS activation.

Transmitting, by the base station, a MAC PDU to the terminal based at least in part on the downlink assignment for the first C-RNTI. The base station, when the SP positioning SRS activation / deactivation MAC CE is included in the MAC PDU and the A / D field is set to 1, performs a first step based on at least part of SRS activation information group 1 of the SP positioning SRS activation / deactivation MAC CE received when the A / D field is set to 1 Positioning SRS resource set active at the time of SRS activation. When, by the base station, the SP positioning SRS activation/deactivation MAC CE is included in the MAC PDU and the A/D field is set to 0, a first step is performed at least partially based on SRS activation information group 1 of the SP positioning SRS activation/deactivation MAC CE received. Deactivation of the positioning SRS resource set at the time of SRS activation. The first SRS activation time is slot n + m. A HARQ ACK corresponding to the PDSCH carrying an activation command is received in slot n. m is the number of first slots corresponding to 3 ms. The first slot is a slot of a currently activated UL BWP. SRS activation information group 1 includes a cell ID field of the positioning SRS resource set, a BWP ID and SUL field of the positioning SRS resource set, and a positioning SRS resource set ID.

The second TA command is included in the TAC MAC CE. The second TA command indicates a relative amount. The 2nd TA command is a 2nd C-RNTI (if the 2nd C-RNTI is transmitted in the extended part of the suspendConfig IE in the RRCRlease message) or a 2nd CS-RNTI (the 2nd C-RNTI is suspendConfig in the RRCRlease message) in RRC_INACTIVE If not transmitted in the extended part of the IE and the second CS-RNTI is received in the extended part of the suspendConfig IE in the RRCRlease message) or based at least in part on the tertiary C-RNTI, and in RRC_CONNTECT, the first C-RNTI Based at least in part on the RNTI.

The base station applies the value indicated in the timeAlignmentTimer IE of system information block 1 to the first timer. The base station applies the 1st TA command transmitted by the RAR and starts the 1st timer. Transmitting, by the base station, a MAC PDU to the terminal based at least in part on the downlink assignment for the first C-RNTI. If the MAC PDU includes the TAC MAC CE, the base station applies a second TA command transmitted from the TAC MAC CE and restarts a 1 timer. When the first timer expires, the base station releases the first resource.

Transmitting, by the base station, the MAC PDU to the terminal based at least in part on the downlink assignment. If the MAC PDU includes the TAC MAC CE and the downlink assignment is for the second C-RNTI and the UE is in the RRC_INACTIVE state, applying the second TA command received from the TAC MAC CE and restarting the plurality of timers by the UE . The plurality of timers include a first timer (when driving), a second timer (when driving), and a third timer (when driving). If the MAC PDU includes the TAC MAC CE and the downlink assignment is for the first C-RNTI and the UE is in the RRC_CONNECTED state, applying the second TA command received from the TAC MAC CE and restarting the first timer by the UE .

For the RRC_CONNECTED UE, the base station performs initial uplink reception for the grant configured in the first symbol of the first subframe. For the RRC_CONNECTED UE, the base station performs initial uplink reception for the grant configured in the first symbol of the first subframe. The RRC_CONNECTED base station performs uplink reception on the second symbol of the second subframe. For the RRC_CONNECTED terminal, the base station performs initial uplink reception for the grant configured in the first symbol of the first subframe based at least in part on the first p0. Performing, by the base station, uplink reception on a second symbol of a second subframe based at least in part on the first p0 for an RRC_CONNECTED terminal.

The first p0 is determined based at least in part on the first ConfiguredGrantConfig and the first PUSCH-Config. The first p0 is determined by the p0-PUSCH-Alpha field of the first ConfigurdGrantConfig and the corresponding p0 field in the first PUSCH-Config.

Based at least in part on the positioning SRS resource set in the fourth UL BWP of the fourth cell, if the base station for the RRC_CONNECTED terminal, the positioning SRS is activated, the fourth UL BWP is activated, and the first timer associated with the fourth cell is running to perform SRS reception. For an RRC_INACTIVE UE, the base station performing SRS reception based at least in part on the positioning SRS resource set in the third UL BWP of the first cell when the positioning SRS is activated and the third timer is running

The first cell is a cell that has transmitted the first RRCRlease message. The first RRCRlease message includes the second IE group 2 or the third IE group.

The UE's PUSCH transmission power for the configured grant is determined at least in part based on p0-NominalWithoutGrant and p0 and path loss and transmission format and transmission bandwidth. The transmission power of PUSCH scheduled by RAR in RA-SDT is determined at least in part based on p0-NominalWithGrant and path loss and transmission format and transmission bandwidth.

PUSCH transmissions are scrambled based on dataScramblingIdentityPUSCH.

Whether or not frequency hopping is applied to a PUSCH transmission is determined based at least in part on frequencyHopping.

Figure 3a illustrates the operation of the terminal.

In step 3a-11, the terminal receives an RRCReconfiguration message from the base station.

The RRCReconfiguration message includes an RNTI-Value IE for the first CS-RNTI, a plurality of configureGrantConfig IEs, a plurality of PUSCH-Config IEs, and a plurality of SRS-Config IEs, each of which is a NUL uplink BWP or SUL is associated with an uplink BWP of NUL, each of a plurality of PUSCH-Config IEs is associated with an uplink BWP of NUL or an uplink BWP of SUL, and each of a plurality of SRS-Config IEs is associated with uplink BWP of NUL or uplink BWP of SUL. is related to

In step 3a-13, the UE receives a MAC PDU from the base station based at least in part on the downlink assignment for the primary C-RNTI.

In step 3a-15, if the SP positioning SRS activation/deactivation MAC CE is included in the MAC PDU and the A/D field is set to 1, the UE sends at least SRS activation information group 1 of the SP positioning SRS activation/deactivation MAC CE The positioning SRS resource set is activated at the first SRS activation time based on the part.

In step 3a-17, if the SP positioning SRS activation/deactivation MAC CE is included in the MAC PDU and the A/D field is set to 0, the UE adds at least SRS activation information group 1 of the SP positioning SRS activation/deactivation MAC CE received The positioning SRS resource set is deactivated at the first SRS activation time based on the part.

The first SRS activation time is slot n + m, the HARQ ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n, m is the number of first slots corresponding to 3 ms, and the first slot is currently activated UL is the slot of the BWP,

SRS activation information group 1 includes a cell ID field of the positioning SRS resource set, a BWP ID and SUL field of the positioning SRS resource set, and a positioning SRS resource set ID.

In step 3a-19, the terminal receives an RRCRelease message for switching the terminal from RRC_CONNECTED to RRC_INACTIVE.

The RRCRlease message includes a SuspendConfig IE, and the SuspendConfig IE includes a first IE group, a second IE group 1, a second IE group 2, and a third IE group.

In step 3a-21, the terminal receives a MAC PDU from the base station based at least in part on the downlink assignment for the second C-RNTI. The MAC PDU contains the SP positioning SRS activation/deactivation MAC CE.

In step 3a-23, if the A/D field is set to 1 and the third timer is running at the time of the third SRS activation, the UE at least partially adds SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received Based on , the positioning SRS resource set is activated at the third SRS activation time point.

In step 3a-25, when the A/D field is set to 0, the UE sets the positioning SRS resource at the third SRS activation time based at least in part on SRS activation information group 2 of the SP positioning SRS activation/deactivation MAC CE received when the A/D field is set to 0. disable

The third SRS activation time is slot n + h, the HARQ ACK corresponding to the PDSCH carrying the activation command is transmitted in slot n, h is the number of second slots corresponding to 3 ms, and the second slot is the third IE group is a slot of the UL BWP configured by, the length of the second slot is determined based at least in part on the subcarrierSpacing IE included in the third IE group, and the SRS activation information group 2 includes a SUL field and a positioning SRS resource set ID . The SRS resource is activated in the cell in which the RRCRlease message is received and in the UL BWP configured by the RRCRlease message.

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 controller 4a-01 controls overall operations of the UE related to mobile communication. For example, the controller 4a-01 transmits and receives signals through the transceiver 4a-03. Also, the controller 4a-01 writes and reads data in the storage unit 4a-02. To this end, the controller 4a-01 may include at least one processor. For example, the controller 4a-01 may include a communication processor (CP) that controls communication and an application processor (AP) that controls upper layers such as application programs. The controller 4a-01 controls the storage unit and the transceiver so that the terminal operations of FIGS. 2A and 3A are performed. The transceiver is also referred to as a transceiver.

The storage unit 4a-02 stores data such as a basic program for operation of the terminal, an application program, and setting information. The storage unit 4a-02 provides stored data according to the request of 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 for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processing unit up-converts the baseband signal provided from the baseband processing unit into an RF band signal, transmits the signal 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 transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter (ADC), and the like. The RF processing unit may perform MIMO, and may receive multiple layers when performing MIMO operation. The baseband processing unit performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the system. For example, during data transmission, the baseband processing unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, when data is received, the baseband processing unit demodulates and decodes the baseband signal provided from the RF processing unit to restore a received bit stream. The transceiver is also referred to as a transceiver.

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

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

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 controller 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 the backhaul interface unit 4b-04. Also, the controller 4b-01 writes and reads data in the storage unit 4b-02. To this end, the controller 4b-01 may include at least one processor. The controller 4b-01 is a transceiver so that the operation of the base station shown in FIG. 2A is performed. storage. Controls the backhaul interface.

The storage unit 4b-02 stores data such as a basic program for the operation of the main base station, an application program, and setting information. In particular, the storage unit 4b-02 may store information on bearers assigned to the connected terminal, measurement results reported from the connected terminal, and the like. In addition, the storage unit 4b-02 may store information that is a criterion for determining whether to provide or stop multiple connections to the terminal. And, the storage unit 4b-02 provides the 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 processor upconverts the baseband signal provided from the baseband processor into an RF band signal, transmits the signal through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. The RF processing unit may perform a downlink MIMO operation by transmitting one or more layers. The baseband processing unit performs a conversion function between a baseband signal and a bit string according to the physical layer standard. For example, during data transmission, the baseband processing unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit demodulates and decodes the baseband signal provided from the RF processing unit to restore a received bit stream. The transceiver is also referred to as a transceiver.

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, a secondary 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

delete

delete

Claims (5)

In a wireless communication system, in a terminal method,
Receiving, by the UE, an RRCRelease in a first cell in an RRC_CONNECTED state;
In the RRC_CONNECTED state, the terminal stopping a first timer when the RRCRelease includes SuspendConfig, the first timer is set to timeAlignmentTimer of RRCSetup,
Starting a second timer to which the TimeAlignmentTimer is applied when the RRCRelease includes the TimeAlignmentTimer in the RRC_CONNECTED state;
Selecting, by the terminal, a second cell;
In an RRC_INACTIVE state, the UE starts transmitting a Sounding Reference Signal (SRS) in a first BWP at a specific time point,
If the BWP setting information exists in the RRCRelease, the first BWP is set by the BWP setting information, and if the BWP setting information does not exist in the RRCRelease, the first BWP is set by system information,
The specific time point is determined based on a predefined fixed time length and a time point at which an HARQ ACK corresponding to a PDSCH carrying an activation command is transmitted and a subcarrierSpacing in RRCRelease.
A method characterized in that an SRS is transmitted based on an SRS configuration in RRCRelease in a first uplink of a first bandwidth part (BWP).
According to claim 1,
SRS transmission of RRC_INACTIVE is stopped when the first timer expires.
In a terminal in a wireless communication system,
A transmitting and receiving unit configured to transmit and receive signals; and
It includes a control unit,
The control unit,
Receiving an RRCRelease from the first cell in the RRC_CONNECTED state;
In the RRC_CONNECTED state, when the RRCRelease includes SuspendConfig, the first timer is stopped, the first timer is set to timeAlignmentTimer of RRCSetup,
In the RRC_CONNECTED state, if the RRCRelease includes TimeAlignmentTimer, start a second timer to which the TimeAlignmentTimer is applied,
Select the second cell,
In the RRC_INACTIVE state, the first BWP is set to start transmitting a Sounding Reference Signal (SRS) at a specific time point,
If BWP setting information exists in the RRCRelease, the first BWP is set by the BWP setting information, and if BWP setting information does not exist in the RRCRelease, the first BWP is set by system information,
The specific time point is determined based on a predefined fixed time length and a time point at which an HARQ ACK corresponding to a PDSCH carrying an activation command is transmitted and a subcarrierSpacing in RRCRelease.
In a wireless communication system, in a base station method,
Transmitting, by the base station, RRCRelease in the first cell to the terminal in the RRC_CONNECTED state;
Stopping, by the base station, a first timer for the terminal in the RRC_CONNECTED state when RRCRelease includes SuspendConfig, the first timer being set to timeAlignmentTimer of RRCSetup,
Applying, by a base station, a first TimeAlignmentTimer value to a first timer of the terminal in an RRC_CONNECTED state, the first TimeAlignmentTimer value is included in the SuspendConfig,
A base station starting to receive a Sounding Reference Signal (SRS) based on information included in RRCRelease at a specific time from the terminal in the RRC_INACTIVE state,
If BWP setting information exists in the RRCRelease, the first BWP is set by the BWP setting information, and if BWP setting information does not exist in the RRCRelease, the first BWP is set by system information;
The specific time point is determined based on a predefined fixed time length and a time point at which an HARQ ACK corresponding to a PDSCH carrying an activation command is transmitted and a subcarrierSpacing in RRCRelease.

Images