Method and apparatus for data transmission in RRC inactivity
Patent Information
- Application Number
- CN202380030198.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-29
- Filing Date
- 2023-03-28
- Publication Date
- 2024-11-12
AI Technical Summary
In the RRC_INACTIVE state of the 5G mobile communication system, it is difficult to effectively perform data transmission, resulting in transmission efficiency and delay problems.
Receive the pause configuration information and CG-SDT configuration information in the RRC release message through the terminal, start the timer related to small data transmission, identify the conditions that meet the small data transmission standard, and synchronize the signal block with high RSRP when the timer is running. When the corresponding authorization time is unavailable, a random access small data transmission process is performed.
Effective data transmission is realized in the RRC_INACTIVE state, which improves transmission efficiency and reduces latency, ensuring the reliability of the system under low power consumption and low latency conditions.
Smart Images

Figure CN118947198A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a wireless communication system, and more particularly to an apparatus, method and system for data transmission in RRC_INACTIVE. Background Art
[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "sub-6 GHz" bands such as 3.5 GHz, but also in "above 6 GHz" bands called mmWave including 28 GHz and 39 GHz. In addition, 6G mobile communication technology (called super 5G system) has been considered to be implemented in terahertz bands (e.g., 95 GHz to 3 THz bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of 5G mobile communication technology.
[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC), standardization has been underway on various technologies: beamforming and massive MIMO for mitigating radio wave path loss in millimeter waves and increasing radio wave transmission distance, support parameter sets for dynamic operation of efficient utilization of millimeter wave resources and time slot formats (e.g., operation of multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large-scale data transmission and polar codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.
[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions are ongoing on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on various technologies such as: V2X (Vehicle to Everything) for assisting driving determination of autonomous vehicles based on information on the location and status of the vehicle sent by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation designed to comply with various regulatory requirements in unlicensed bands, NR UE power saving, a non-terrestrial network (NTN) as UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable, and positioning.
[0005] In addition, in terms of air interface architecture / protocol, standardization is being conducted on various technologies such as the Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (NR's 2-step RACH) for simplifying the random access procedure. In terms of system architecture / services, standardization is also being conducted on various technologies such as the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location.
[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research related to the following technologies is scheduled: extended reality (XR) for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
[0007] In addition, such development of 5G mobile communication systems will serve not only as a basis for developing new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas), metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable smart surface), but also as a basis for developing full-duplex technology for improving the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services with a complexity level that exceeds the capacity limitations of UE operations by utilizing ultra-high performance communication and computing resources.
[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above is applicable as prior art with respect to the present disclosure. Summary of the invention
[0009] Technical issues
[0010] Aspects of the present disclosure are to address at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Accordingly, one aspect of the present disclosure is to provide a method and system for data transmission in RRC_INACTIVE.
[0011] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.
[0012] Solution to the problem
[0013] According to one aspect of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving a radio resource control (RRC) release message including suspension configuration information and configured grant-small data transmission (CG-SDT) configuration information, starting a timer associated with a time alignment (TA) for CG-SDT based on the CG-SDT configuration information, identifying a standard for a small data transmission (SDT) process, and performing a RA-SDT process when any configured grant (CG) opportunity corresponding to a synchronization signal block (SSB) with a reference signal received strength (RSRP) above a threshold is unavailable when the timer associated with the TA for CG-SDT is running and the standard for a random access-small data transmission (RA-SDT) process is met.
[0014] According to another aspect of the present disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver and a controller. The controller is configured to receive an RRC release message including suspension configuration information and CG-SDT configuration information via the transceiver, start a timer associated with a TA for CG-SDT based on the CG-SDT configuration information, identify the criteria for the SDT process, and perform the RA-SDT process when any CG opportunity corresponding to an SSB with an RSRP higher than a threshold is unavailable while the timer associated with the TA for CG-SDT is running and the criteria for the RA-SDT process are met.
[0015] Other aspects, advantages, and salient features of the present disclosure will become apparent to those skilled in the art from the following detailed description which, in conjunction with the accompanying drawings, discloses various embodiments of the present disclosure.
[0016] Advantageous Effects of the Invention
[0017] According to an embodiment of the present disclosure, data transmission may be effectively performed in the RRC_INACTIVE state. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:
[0019] Figure 1 is an example signaling flow for small data transmission using 4-step random access (RA) according to an embodiment of the present disclosure;
[0020] Figure 2 shows a signaling flow for small data transmission using 2-step RA according to an embodiment of the present disclosure;
[0021] Figure 3 A signaling flow for small data transmission using pre-configured physical uplink data channel (PUSCH) resources (or configured grant-based SDT (CG-SDT)) according to an embodiment of the present disclosure is shown;
[0022] Figure 4 A scenario of CG-SDT timer expiration after an initial hybrid automatic repeat request (HARQ) transmission of a first uplink (UL) medium access control (MAC) protocol data unit (PDU) carrying an RRC recovery request according to an embodiment of the present disclosure is shown;
[0023] Figure 5 A scenario in which a CG-SDT timer expires before an initial HARQ transmission of a first UL MAC PDU carrying an RRC recovery request according to an embodiment of the present disclosure is shown;
[0024] Figure 6 A scenario before initial HARQ transmission of a first ULMAC PDU carrying an RRC resume request using a suitable SSB according to an embodiment of the present disclosure is shown;
[0025] Figure 7 The operation of the UE according to an embodiment of the present disclosure is shown;
[0026] Figure 8 The operation of the UE according to an embodiment of the present disclosure is shown;
[0027] Fig. 9 is a block diagram of a terminal according to an embodiment of the present disclosure; and
[0028] Fig.10 is a block diagram of a base station according to an embodiment of the present disclosure.
[0029] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION
[0030] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these details should be considered as merely exemplary. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and conciseness.
[0031] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.
[0032] It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.
[0033] The term "substantially" means that the characteristic, parameter or value described need not be achieved precisely, but may deviate or vary by an amount that does not eliminate the effect that the characteristic is intended to provide, including, for example, tolerances, measurement errors, measurement precision limitations and other factors known to those skilled in the art.
[0034] It is known to those skilled in the art that the combination of the blocks and flow charts of a flow chart (or sequence diagram) can be represented and executed by computer program instructions. These computer program instructions can be loaded on a processor of a general-purpose computer, a special-purpose computer, or a programmable data processing device. When the loaded program instructions are executed by the processor, they create equipment for performing the functions described in the flow chart. Because computer program instructions can be stored in a non-transitory computer-readable memory available in a special-purpose computer or a programmable data processing device, an article of manufacture that performs the functions described in the flow chart can also be created. Because computer program instructions can be loaded on a computer or a programmable data processing device, when executed as a process, they can perform the operations of the functions described in the flow chart.
[0035] The blocks of the flow chart may correspond to a module, segment or code containing one or more executable instructions that implement one or more logical functions, or may correspond to a portion thereof. In some cases, the functions described by the blocks may be performed in an order different from the order listed. For example, two blocks listed in order may be performed simultaneously or in reverse order.
[0036] In this specification, the words "unit", "module", etc. may refer to software components or hardware components, such as, for example, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) that can perform a function or operation. However, "unit", etc. are not limited to hardware or software. Units, etc. may be configured to reside in an addressable storage medium or drive one or more processors. Units, etc. may refer to software components, object-oriented software components, class components, task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided by components and units may be a combination of smaller components and units, and may be combined with other components and units to form larger components and units. Components and units may be configured to drive devices or one or more processors in a secure multimedia card.
[0037] Before the detailed description, terms or definitions necessary for understanding the present disclosure are described. However, these terms should be interpreted in a non-limiting manner.
[0038] A “base station (BS)” is an entity that communicates with a user equipment (UE) and may be referred to as a BS, base transceiver station (BTS), node B (NB), evolved NB (eNB), access point (AP), 5GNB (5GNB), or next-generation node B (gNB).
[0039] A “UE” is an entity communicating with a BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.
[0040] In recent years, several broadband wireless technologies have been developed to meet the growing number of broadband subscribers and provide more and better applications and services. The second generation wireless communication system has been developed to provide voice services while ensuring the mobility of users. The third generation wireless communication system supports not only voice services but also data services. In recent years, the fourth wireless communication system has been developed to provide high-speed data services. However, at present, the fourth generation wireless communication system suffers from a lack of resources to meet the growing demand for high-speed data services. Therefore, the fifth generation wireless communication system (also referred to as next generation radio or NR) is being developed to meet the growing demand for high-speed data services, supporting ultra-reliability and low-latency applications.
[0041] The fifth generation wireless communication system supports not only low frequency bands, but also higher frequency (mmWave) bands, such as 10 GHz to 100 GHz bands, in order to achieve higher data rates. In order to mitigate the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies are considered in the design of the fifth generation wireless communication system. In addition, the fifth generation wireless communication system is expected to address different use cases with completely different requirements in terms of data rate, latency, reliability, mobility, etc. However, the design of the air interface of the fifth generation wireless communication system is expected to be flexible enough to serve UEs with completely different capabilities, depending on the use cases and market segments that the UE provides services to end customers. Several example use cases that the fifth generation wireless communication system is expected to address are enhanced mobile broadband (eMBB), massive machine type communication (m-MTC), ultra-reliable low latency communication (URLL), etc. eMBB requirements such as tens of Gbps data rates, low latency, and high mobility address the market segments representing traditional wireless broadband subscribers who always need Internet connections anywhere. m-MTC requirements such as very high connection density, infrequent data transfer, very long battery life, low mobility, etc. address the market segment representing the Internet of Things (IoT) / Internet of Everything (IoE) (connection of billions of devices is envisioned). URLL requirements such as very low latency, very high reliability, and variable mobility address the market segment representing industrial automation applications, vehicle-to-vehicle / vehicle-to-infrastructure communications expected to be one of the enablers of autonomous vehicles.
[0042] In the fifth generation wireless communication system operating in the high frequency (mmWave) band, the UE and the gNB communicate with each other using beamforming. Beamforming technology is used to mitigate propagation path loss and increase propagation distance for communications at higher frequency bands. Beamforming uses high-gain antennas to enhance transmission and reception performance. Beamforming can be classified into transmission (TX) beamforming performed in the transmitting end and reception (RX) beamforming performed in the receiving end. Generally, TX beamforming increases directivity by allowing the area reached by propagation to be densely located in a specific direction using multiple antennas. In this case, the aggregation of multiple antennas can be referred to as an antenna array, and each antenna included in the array can be referred to as an array element. The antenna array can be configured in various forms, such as a linear array, a planar array, and the like. The use of TX beamforming leads to an increase in signal directivity, thereby increasing the propagation distance. In addition, since the signal is hardly sent in directions other than the directional direction, the signal interference acting on the other receiving end is significantly reduced. The receiving end can perform beamforming on the RX signal by using an RX antenna array. RX beamforming increases the RX signal strength sent in a specific direction by allowing propagation to be concentrated in a specific direction, and excludes signals sent in directions other than the specific direction from the RX signal, thereby providing the effect of blocking interference signals. By using beamforming technology, the transmitter can generate multiple transmit beam patterns in different directions. Each of these transmit beam patterns may also be referred to as a transmit (TX) beam. Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals in a cell because each narrow TX beam provides coverage to part of the cell. The narrower the TX beam, the higher the antenna gain, and therefore the greater the propagation distance of the signal sent using beamforming. The receiver may also generate multiple receive (RX) beam patterns in different directions. Each of these receive patterns may also be referred to as a receive (RX) beam.
[0043] Carrier aggregation (CA) / multiple connections in the fifth generation wireless communication system: The fifth generation wireless communication system supports independent operation mode as well as dual connection (DC). In DC, multiple Rx / Tx UEs can be configured to utilize resources provided by two different nodes (or NBs) connected via a non-ideal backhaul. One node acts as a master node (MN) and the other node acts as a secondary node (SN). The MN and the SN are connected via a network interface, and at least the MN is connected to the core network. NR also supports multi-RAT dual connection (MR-DC) operation, whereby a UE in RRC_CONNECTED (RRC connection) is configured to utilize radio resources provided by two different schedulers located in two different nodes connected via a non-ideal backhaul, and provides Evolved Universal Terrestrial Radio Access (E-UTRA) (ie, if the node is ng-eNB) or NR access (ie, if the node is gNB). In NR, for a UE in RRC_CONNECTED that is not configured with CA / DC, there is only one serving cell including a primary cell (PCell). For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cell" is used to refer to a set of cells including special cells and all secondary cells. In NR, the term Master Cell Group (MCG) refers to a set of serving cells associated with a master node, including a PCell and optionally one or more secondary cells (SCells). In NR, the term Secondary Cell Group (SCG) refers to a set of serving cells associated with a secondary node, including a primary SCG cell (PSCell) and optionally one or more SCells. In NR, a primary cell (PCell) refers to a serving cell in an MCG operating on a primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. In NR, for a UE configured with CA, an Scell is a cell that provides additional radio resources on top of a special cell. A primary SCG cell (PSCell) refers to a serving cell in an SCG, where the UE performs random access when performing a Reconfiguration with Sync procedure. For dual connectivity operation, the term special cell (SpCell) refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term special cell refers to the PCell.
[0044] System Information Acquisition in Fifth Generation Wireless Communication Systems: In fifth generation wireless communication systems, a Node B (gNB) or base station broadcasts synchronization signals and physical broadcast channel (PBCH) blocks (SSBs) consisting of a primary synchronization signal (PSS), a secondary synchronization signal (SSS) and system information in a cell. The system information includes common parameters required for communication in a cell. In fifth generation wireless communication systems (also known as next generation radio or NR), system information (SI) is divided into a master information block (MIB) and multiple system information blocks (SIBs), where:
[0045] *MIB is always sent on BCH with a periodicity of 80ms and repetitions within 80ms, and it includes the parameters required to obtain SIB1 from the cell.
[0046] *SIB1 is sent on the downlink shared channel (DL-SCH) with a periodicity of 160 ms and variable transmission repetition. The default transmission repetition period of SIB1 is 20 ms, but the actual transmission repetition period depends on the network implementation. The scheduling information in SIB 1 includes the mapping between SIBs and SI messages, the periodicity of each SI message, and the SI window length. The scheduling information in SIB 1 includes an indicator for each SI message, which indicates whether the concerned SI message is being broadcast. If at least one SI message is not being broadcast, SIB1 may include random access resources (physical random access channel (PRACH) preamble and PRACH resources) for requesting the gNB to broadcast one or more SI messages.
[0047] *SIBs other than SIB1 are carried in system information (SI) messages, which are sent on DL-SCH. Only SIBs with the same period can be mapped to the same SI message. Each SI message is sent within a time domain window that occurs periodically (referred to as an SI window with the same length for all SI messages). Each SI message is associated with an SI window, and the SI windows of different SI messages do not overlap. That is, within one SI window, only the corresponding SI message is sent. Using the indication in SIB1, any SIB other than SIB1 can be configured as cell-specific or area-specific. Cell-specific SIBs are only applicable within the cell where the SIB is provided, while area-specific SIBs are applicable within an area called an SI area, which consists of one or more cells and is identified by a systemInformationAreaID (system information area ID).
[0048] Physical downlink control channel (PDCCH) in fifth generation wireless communication systems: In fifth generation wireless communication systems, the physical downlink control channel (PDCCH) is used to schedule DL transmissions on PDSCH and UL transmissions on PUSCH, wherein the downlink control information (DCI) on the PDCCH includes: downlink assignments containing at least modulation and coding formats, resource allocations and HARQ information related to DL-SCH; uplink scheduling grants containing at least modulation and coding formats, resource allocations and HARQ information related to UL-SCH. In addition to scheduling, the PDCCH can be used for: activation and deactivation of configured PUSCH transmissions with configured grants; activation and deactivation of PDSCH semi-persistent transmissions; notification of time slot formats to one or more UEs; notification of PRBs and OFDM symbols to one or more UEs, where the UE can assume that no transmission is intended for the UE; transmission of TPC commands for PUSCH and PUCCH; transmission of one or more TPC commands for SRS transmission by one or more UEs; switching of the active bandwidth portion of the UE; initiation of a random access procedure. The UE monitors a set of PDCCH candidates in the configured monitoring opportunities in one or more configured control resource sets (CORESETs) according to the corresponding search space configuration. A CORESET consists of a set of PRBs with a duration of 1 to 3 OFDM symbols. Resource unit resource element groups (REGs) and control channel elements (CCEs) are defined within a CORESET, where each CCE consists of a set of REGs. The control channel is formed by aggregation of CCEs. Different code rates for the control channel are achieved by aggregating different numbers of CCEs. Interleaved and non-interleaved CCE to REG mapping are supported in a CORESET. Polarization coding is used for PDCCH. Each resource element group carrying PDCCH carries its own DMRS. Quadrature phase shift keying (QPSK) modulation is used for PDCCH.
[0049] In the fifth generation wireless communication system, a list of search space configurations is signaled by the gNB for each configured BWP, where each search configuration is uniquely identified by an identifier. The identifier of the search space configuration to be used for a specific purpose (such as paging reception, SI reception, random access response reception) is explicitly signaled by the gNB. In NR, the search space configuration includes the parameters Monitoring-periodicity-PDCCH-slot, Monitoring-offset-PDCCH-slot, Monitoring-symbols-PDCCH-within-slot and duration. The UE uses the parameters PDCCH monitoring period (Monitoring-periodicity-PDCCH-slot), PDCCH monitoring offset (Monitoring-offset-PDCCH-slot) and PDCCH monitoring mode (Monitoring-symbols-PDCCH-within-slot) to determine the PDCCH monitoring timing within the timeslot. The PDCCH monitoring opportunity exists in slots 'x' to x+duration, where the slot with number 'x' in the radio frame with number 'y' satisfies the following Equation 1:
[0050] [Equation 1]
[0051] (y*(number of slots in a radio frame)+x-Monitoring-offset-PDCCH-slot)mod(Monitoring-periodicity-PDCCH-slot)=0;
[0052] The starting symbol of the PDCCH monitoring opportunity in each slot with a PDCCH monitoring opportunity is given by Monitoring-symbols-PDCCH-within-slot. The length of the PDCCH monitoring opportunity (in symbols) is given in the coreset associated with the search space. The search space configuration includes an identifier of the coreset configuration associated with it. The gNB signals a list of coreset configurations for each configured BWP, where each coreset configuration is uniquely identified by an identifier. Note that each radio frame has a duration of 10ms. A radio frame is identified by a radio frame number or a system frame number. Each radio frame includes a number of slots, where the number of slots in a radio frame and the duration of the slots depend on the subcarrier spacing. The number of slots in a radio frame and the duration of the slots are predefined in NR depending on the radio frame used for each supported SCS. Each coreset configuration is associated with a list of transmission configuration indicator (TCI) states. Each TCI state configures a DL RS ID (SSB or channel state information reference signal (CSI RS)). The gNB signals the list of TCI states corresponding to the coreset configuration via RRC signaling. One of the TCI states in the list of TCI states is activated by the gNB and indicated to the UE. The TCI state indicates the DL TX beam used by the gNB for transmission of PDCCH in the PDCCH monitoring occasion of the search space (DL TX beam with SSB / CSI RS QCL of TCI state).
[0053] BWP operation in the fifth generation wireless communication system: In the fifth generation wireless communication system, bandwidth adaptation (BA) is supported. In the case of BA, the reception and transmission bandwidth of the UE does not need to be as large as the bandwidth of the cell and can be adjusted: the width can be commanded to change (for example, shrink during low activity periods to save power); the position can be moved in the frequency domain (for example, to increase scheduling flexibility); and the subcarrier spacing can be commanded to change (for example, to allow different services). A subset of the total cell bandwidth of a cell is called a bandwidth part (BWP). BA is implemented by configuring an RRC-connected UE with a BWP and telling the UE which of the configured BWPs is currently the active BWP. When BA is configured, the UE only needs to monitor the PDCCH on one active BWP, that is, it does not have to monitor the PDCCH on the entire DL frequency of the serving cell. In the RRC_CONNECTED state, the UE is configured with one or more DL and UL BWPs for each configured serving cell (ie, PCell or SCell). For an activated serving cell, there is always one active UL BWP and DL BWP at any point in time. BWP switching of the serving cell is used to activate the inactive BWP and deactivate the active BWP at one time. When initiating the random access procedure, the BWP switching is controlled by the PDCCH indicating the downlink assignment or uplink grant, bwp-InactivityTimer, RRC signaling, or the MAC entity itself. When adding a SpCell or activating an SCell, the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id (first active downlink BWP-Id) and firstActiveUplinkBWP-Id (first active uplink BWP-Id), respectively, are active without receiving a PDCCH indicating a downlink assignment or uplink grant. The active BWP of the serving cell is indicated by RRC or PDCCH. For unpaired spectrum, the DL BWP is paired with the UL BWP, and the BWP switching is common to both UL and DL. When the BWP inactivity timer expires, the UE switches the active DL BWP to the default DL BWP or the initial DL BWP (if the default DL BWP is not configured).
[0054] Random access in the fifth generation wireless communication system: In the 5G wireless communication system, random access (RA) is supported. Random access (RA) is used to achieve uplink (UL) time synchronization. RA is used during initial access, handover, radio resource control (RRC) connection reestablishment process, scheduling request transmission, secondary cell group (SCG) addition / modification, beam failure recovery, and data or control information transmission in the UL by an unsynchronized UE in the RRC_CONNECTED state. Several types of random access procedures are supported.
[0055] Contention-based random access (CBRA): This is also known as 4-step CBRA. In this type of random access, the UE first sends a random access preamble (also known as Msg1) and then waits for the RAR in the random access response (RAR) window. The RAR is also known as Msg2. The next generation Node B (gNB) sends the RAR on the physical downlink shared channel (PDSCH). The PDCCH that schedules the PDSCH carrying the RAR is addressed to the RA-Radio Network Temporary Identifier (RA-RNTI). The RA-RNTI identifies the time-frequency resources (also known as physical RA channel (PRACH) opportunity or PRACH transmission (TX) opportunity or RA channel (RACH) opportunity) where the gNB detects the RA preamble. RA-RNTI is calculated as follows: RA-RNTI = 1 + s_id + 14 * t_id + 14 * 80 * f_id + 14 * 80 * 8 * ul_carrier_id, where s_id is the index of the first orthogonal frequency division multiplexing (OFDM) symbol of the PRACH opportunity in which the UE has sent Msg1 (i.e., RA preamble); 0 ≤ s_id < 14; t_id is the index of the first time slot of the PRACH opportunity (0 ≤ t_id < 80); f_id is the index of the PRACH opportunity within the time slot in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for normal UL (NUL) carrier, and 1 for supplementary UL (SUL) carrier). Several RARs for various random access preambles detected by the gNB can be multiplexed by the gNB in the same RAR media access control (MAC) protocol data unit (PDU). If the RAR includes the RA preamble identifier (RAPID) of the RA preamble sent by the UE, then the RAR in the MAC PDU corresponds to the RA preamble transmission of the UE. If the RAR corresponding to its RA preamble transmission is not received during the RAR window, and the UE has not sent the RA preamble for a configurable (configured by the gNB in the RACH configuration) number of times, then the UE returns to the first step, i.e. selecting a random access resource (preamble / RACH opportunity) and sending the RA preamble. A backoff may be applied before returning to the first step.
[0056] If a RAR corresponding to its RA preamble transmission is received, the UE sends a message 3 (Msg3) in the UL grant received in the RAR. Msg3 includes messages such as RRC connection request, RRC connection reestablishment request, RRC handover confirmation, scheduling request, SI request, etc. It may include a UE identity (i.e., a cell-radio network temporary identifier (C-RNTI) or a system architecture evolution (SAE)-temporary mobile subscriber identity (S-TMSI) or a random number). After sending Msg3, the UE starts a contention resolution timer. While the contention resolution timer is running, if the UE receives a physical downlink control channel (PDCCH) addressed to the C-RNTI included in Msg3, contention resolution is considered successful, the contention resolution timer stops and the RA procedure is completed. While the contention resolution timer is running, if the UE receives a contention resolution MAC control element (CE) including the UE's contention resolution identity (the first X bits of the common control channel (CCCH) service data unit (SDU) sent in Msg3), contention resolution is considered successful, the contention resolution timer stops and the RA procedure is completed. If the contention resolution timer expires and the UE has not sent a RA preamble for a configurable number of times, the UE returns to the first step, i.e. selecting random access resources (preamble / RACH opportunity) and sending a RA preamble. A backoff may be applied before returning to the first step.
[0057] Contention-free random access (CFRA): This is also called traditional CFRA or 4-step CFRA. The CFRA procedure is used for scenarios such as handovers that require low latency, timing advance establishment of secondary cells (Scells), etc. The evolved Node B (eNB) assigns a dedicated random access preamble to the UE. The UE sends a dedicated RA preamble. The ENB sends a RAR on the PDSCH addressed to the RA-RNTI. The RAR conveys the RA preamble identifier and timing alignment information. The RAR may also include a UL grant. Similar to the contention-based RA (CBRA) procedure, the RAR is sent in the RAR window. After receiving the RAR including the RA preamble identifier (RAPID) of the RA preamble sent by the UE, the CFRA is considered to be successfully completed. In the case where RA is initiated for beam failure recovery, if the PDCCH addressed to the C-RNTI is received in the search space for beam failure recovery, the CFRA is considered to be successfully completed. If the RAR window expires and the RA is not completed successfully, and the UE has not sent the RA preamble for a configurable (configured by the gNB in the RACH configuration) number of times, the UE resends the RA preamble.
[0058] For certain events, such as handover and beam failure recovery, if a dedicated preamble is assigned to the UE, during the first step of random access, i.e., during random access resource selection for Msg1 transmission, the UE determines whether to send a dedicated preamble or a non-dedicated preamble. Dedicated preambles are typically provided for a subset of SSB / CSI RSs. If there is no SSB / CSI RS with DL RSRP above a threshold among the SSB / CSI RSs for which the gNB provides contention-free random access resources (i.e., dedicated preambles / random access opportunities (ROs)), the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, during the RA procedure, one random access attempt may be CFRA, while the other random access attempt may be CBRA.
[0059] 2-step Contention-Based Random Access (2-step CBRA): In the first step, the UE sends a random access preamble on PRACH and a payload (i.e., MAC PDU) on PUSCH. The random access preamble and payload transmission is also referred to as MsgA. In the second step, after the MsgA transmission, the UE monitors for a response from the network (i.e., gNB) within a configured window. The response is also referred to as MsgB. The next generation Node B (gNB) sends MsgB on the Physical Downlink Shared Channel (PDSCH). The PDCCH scheduling the PDSCH carrying MsgB is addressed to the MsgB-Radio Network Temporary Identifier (MSGB-RNTI). The MSGB-RNTI identifies the time-frequency resources (also referred to as Physical RA Channel (PRACH) Opportunities or PRACH Transmission (TX) Opportunities or RA Channel (RACH) Opportunities) where the gNB detects the RA preamble. MsgB-RNTI is calculated as follows: MsgB-RNTI=1+s_id+14*t_id+14*80*f_id+14*80*8*ul_carrier_id+14×80×8×2, where s_id is the index of the first orthogonal frequency division multiplexing (OFDM) symbol of the PRACH opportunity in which the UE has sent Msg1 (i.e., RA preamble); 0≤s_id<14; t_id is the index of the first time slot of the PRACH opportunity (0≤t_id<80); f_id is the index of the PRACH opportunity within the time slot in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for normal UL (NUL) carrier, and 1 for supplementary UL (SUL) carrier).
[0060] If the CCCH SDU is sent in the MsgA payload, the UE performs contention resolution using the contention resolution information in MsgB. If the contention resolution identifier received in MsgB matches the first 48 bits of the CCCH SDU sent in MsgA, contention resolution is successful. If the C-RNTI is sent in the MsgA payload, contention resolution is successful if the UE receives a PDCCH addressed to the C-RNTI. If contention resolution is successful, the random access procedure is considered to be successfully completed. Instead of the contention resolution information corresponding to the sent MsgA, MsgB may include fallback information corresponding to the random access preamble sent in MsgA. If the fallback information is received, the UE sends Msg3 and performs contention resolution using Msg4, as in the CBRA process. If contention resolution is successful, the random access procedure is considered to be successfully completed. If contention resolution fails at fallback (i.e., when sending Msg3), the UE resends MsgA. If the configured window in which the UE monitors the network response after sending MsgA expires and the UE has not received MsgB including contention resolution information or backoff information as described above, the UE resends MsgA. If the random access procedure is not successfully completed even after sending msgA a configurable number of times, the UE falls back to the 4-step RACH procedure, i.e., the UE only sends the PRACH preamble.
[0061] The MsgA payload may include one or more of the following: a common control channel (CCCH) service data unit (SDU), a dedicated control channel (DCCH) SDU, a dedicated traffic channel (DTCH) SDU, a buffer status report (BSR) MAC control element (CE), a power headroom report (Power Headroom Report, PHR) MAC CE, SSB information, C-RNTI MAC CE, or padding. MsgA may include a UE ID (e.g., a random ID, S-TMSI, C-RNTI, recovery ID, etc.) and the preamble in the first step. The UE ID may be included in the MAC PDU of MsgA. A UE ID such as a C-RNTI may be carried in a MAC CE, where the MAC CE is included in the MAC PDU. Other UE IDs (such as a random ID, S-TMSI, C-RNTI, recovery ID, etc.) may be carried in a CCCH SDU. The UE ID may be one of a random ID, S-TMSI, C-RNTI, recovery ID, IMSI, idle mode ID, inactive mode ID, etc. The UE ID may be different in different scenarios where the UE performs a RA procedure. When the UE performs RA after power-on (before it attaches to the network), the UE ID is a random ID. When the UE performs RA in an idle state after it attaches to the network, the UE ID is an S-TMSI. If the UE has an assigned C-RNTI (for example, in a connected state), the UE ID is a C-RNTI. In the case where the UE is in an inactive state, the UE ID is a recovery ID. In addition to the UE ID, some additional ctrl (control) information may also be sent in MsgA. The control information may be included in the MAC PDU of MsgA. The control information may include a connection request indication, a connection recovery request indication, an SI request indication, a buffer status indication, beam information (for example, one or more DL TX beam IDs or SSB IDs), a beam failure recovery indication / information, a data indicator, a cell / BS / TRP switching indication, a connection reconstruction indication, a reconfiguration completion or switching completion message, and the like. One or more.
[0062] 2-step Contention-Free Random Access (2-step CFRA): In this case, the gNB assigns the UE a dedicated random access preamble and PUSCH resources for MsgA transmission. The RO to be used for preamble transmission may also be indicated. In the first step, the UE sends a random access preamble on PRACH and payload on PUSCH using contention-free random access resources (i.e., dedicated preamble / PUSCH resources / RO). In the second step, after MsgA transmission, the UE monitors for a response from the network (i.e., gNB) within the configured window. This response is also called MsgB.
[0063] The next generation Node B (gNB) transmits MsgB on the physical downlink shared channel (PDSCH). The PDCCH scheduling the PDSCH carrying MsgB is addressed to the MsgB-Radio Network Temporary Identifier (MSGB-RNTI). The MSGB-RNTI identifies the time-frequency resource (also called physical RA channel (PRACH) opportunity or PRACH transmission (TX) opportunity or RA channel (RACH) opportunity) where the gNB detects the RA preamble. MsgB-RNTI is calculated as follows: MsgB-RNTI=1+s_id+14*t_id+14*80*f_id+14*80*8*ul_carrier_id+14×80×8×2, where s_id is the index of the first orthogonal frequency division multiplexing (OFDM) symbol of the PRACH opportunity in which the UE has sent Msg1 (i.e., RA preamble); 0≤s_id<14; t_id is the index of the first time slot of the PRACH opportunity (0≤t_id<80); f_id is the index of the PRACH opportunity within the time slot in the frequency domain (0≤f_id<8), and ul_carrier_id is the UL carrier used for Msg1 transmission (0 for normal UL (NUL) carrier, and 1 for supplementary UL (SUL) carrier).
[0064] The random access procedure is considered to be successfully completed if the UE receives a PDCCH addressed to the C-RNTI. The random access procedure is considered to be successfully completed if the UE receives backoff information corresponding to the preamble it sent.
[0065] For certain events, such as handover and beam failure recovery, if dedicated preamble and PUSCH resources are assigned to the UE, during the first step of random access, i.e., during random access resource selection for MsgA transmission, the UE determines whether to send a dedicated preamble or a non-dedicated preamble. Dedicated preambles are usually provided for a subset of SSB / CSI RSs. If there is no SSB / CSI RS with DL RSRP above a threshold among the SSB / CSI RSs for which the gNB provides contention-free random access resources (i.e., dedicated preamble / RO / PUSCH resources), the UE selects a non-dedicated preamble. Otherwise, the UE selects a dedicated preamble. Therefore, during the RA procedure, one random access attempt can be a 2-step CFRA, while the other random access attempt can be a 2-step CBRA.
[0066] When initiating a random access procedure, the UE first selects a carrier (SUL or NUL). If the carrier for the random access procedure is explicitly signaled by the gNB, the UE selects the signaled carrier for performing the random access procedure. If the gNB does not explicitly signal the carrier for the random access procedure; and if the serving cell for the random access procedure is configured with a supplementary uplink and if the RSRP referenced by the downlink path loss is less than rsrp-ThresholdSSB-SUL: The UE selects the SUL carrier for performing the random access procedure. Otherwise, the UE selects the NUL carrier for performing the random access procedure. When selecting the UL carrier, the UE determines the UL and DLBWP for the random access procedure, as specified in Section 5.15 of TS 38.321. The UE then determines whether to perform a 2-step RACH or a 4-step RACH for the random access procedure.
[0067] *If the random access procedure is initiated by a PDCCH order and if the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000, the UE selects 4-step RACH.
[0068] * Otherwise, if the gNB signals 2-step contention-free random access resources for this random access procedure, the UE selects 2-step RACH.
[0069] * Otherwise, if the gNB signals 4-step contention-free random access resources for this random access procedure, the UE selects 4-step RACH.
[0070] * Otherwise, if the UL BWP selected for this random access procedure is configured with only 2-step RACH resources, the UE selects 2-step RACH.
[0071] * Otherwise, if the UL BWP selected for this random access procedure is configured with only 4-step RACH resources, the UE selects 4-step RACH.
[0072] * Otherwise, if the UL BWP selected for this random access procedure is configured with both 2-step RACH resources and 4-step RACH resources,
[0073] **If the RSRP referenced by the downlink path loss is below the configured threshold, the UE selects 4-step RACH. Otherwise, the UE selects 2-step RACH.
[0074] In a fifth generation (also known as NR or New Radio) wireless communication system, a UE may be in one of the following RRC states: RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED. The RRC state may be further characterized as follows:
[0075] - In RRC_IDLE state, UE-specific DRX can be configured by upper layers (i.e. NAS). The UE monitors short messages sent via DCI together with P-RNTI; monitors the paging channel for CN paging using 5G-S-TMSI; - performs neighbor cell measurements and cell (re)selection; obtains system information and can send SI requests (if configured).
[0076] -In RRC_INACTIVE state, UE-specific DRX can be configured by upper layers or by the RRC layer; in this state, the UE stores the UE inactive AS context. The RAN-based notification area is configured by the RRC layer. The UE monitors short messages sent via DCI together with the P-RNTI; monitors the paging channel for CN paging using 5G-S-TMSI and RAN paging using full I-RNTI; performs neighbor cell measurements and cell (re)selection; performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area; obtains system information and can send SI requests (if configured).
[0077] - In RRC_CONNECTED, the UE stores the AS context. Unicast data is sent to / received from the UE. At low layers, the UE may be configured with UE-specific DRX. The UE monitors the short message sent with the P-RNTI via the DCI (if configured); monitors the control channel associated with the shared data channel to determine if data is scheduled for it; provides channel quality and feedback information; performs neighbor cell measurements and measurement reports; obtains system information.
[0078] The NR-based 5G or Next Generation Radio Access Network (NG-RAN) consists of NG-RAN nodes, where the NG-RAN node is the gNB, providing the NR user plane and control plane protocol termination to the UE. The gNB is also connected to the 5GC by means of the NG interface, more specifically to the AMF (Access and Mobility Management Function) by means of the NG-C interface and to the UPF (User Plane Function) by means of the NG-U interface. In the fifth generation (also known as NR or New Radio) wireless communication system, the UE can use discontinuous reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. In the RRC_IDLE / RRC_INACTIVE state, the UE wakes up at regular intervals (i.e., every DRX cycle) in a short period of time to receive paging, receive SI update notifications, and receive emergency notifications. The paging message is sent using the physical downlink shared channel (PDSCH). If there is a paging message in the PDSCH, the physical downlink common control channel (PDCCH) is addressed to the P-RNTI. The P-RNTI is common to all UEs or a group of UEs. The UE identity (i.e., S-TMSI for RRC_IDLE UE or I-RNTI for RRC_INACTIVE UE) is included in the paging message to indicate paging for a specific UE. The paging message may include multiple UE identities to page multiple UEs. The paging message is broadcast on the data channel (i.e., PDSCH) (i.e., PDCCH is masked with P-RNTI). SI updates and emergency notifications are included in the DCI, and the PDCCH carrying the DCI is addressed to the P-RNTI. In RRC idle / inactive mode, the UE monitors one paging occasion (PO) per DRX cycle. In RRC idle / inactive mode, the UE monitors PO in the initial DL BWP. In the RRC_CONNECTED state, the UE monitors one or more Pos to receive SI update notifications and to receive emergency notifications. In the RRC_CONNECTED state, the UE may monitor any PO in the paging DRX cycle and monitor at least one PO in the SI modification cycle. In RRC idle / inactive mode, the UE monitors PO in its active DL BWP every DRX cycle. PO is a set of "S" PDCCH monitoring opportunities for paging, where "S" is the number of SSBs transmitted in the cell (i.e., synchronization signal and PBCH blocks (SSBs) consist of primary and secondary synchronization signals (PSS, SSS) and PBCH). The UE first determines the paging frame (PF) and then determines the PO relative to the determined PF. One PF is a radio frame (10ms).
[0079] Small data transmission in the fifth generation wireless communication system: In the 5G wireless communication system, small data transmission (SDT) under RRC_INACTIVE is supported. Uplink data can be sent in Msg3 in the case of a 4-step RA process, and can be sent in MsgA in the case of a 2-step RA process.
[0080] Figure 1 is an example signaling flow for small data transmission using 4-step RA according to an embodiment of the present disclosure.
[0081] 0. The criteria for initiating a 4-step RA for SDT are met. The UE selects a preamble / RO from the preambles / ROs for SDT. The UE sends (S100) a random access preamble and receives (S105) a RAR including a UL grant for Msg3 transmission.
[0082] 1. The UE sends (S110) RRCResumeRequest / RRCResumeRequest1 to the gNB (same as the last serving gNB) on SRB 0. It includes full / short I-RNTI (resumeIdentity), resume cause (resumeCause) and authentication token (resumeMAC-I). The I-RNTI (short or full I-RNTI) is used for context identification and its value may be the same as the I-RNTI that the UE has received from the last serving gNB in the RRCRelease message with suspendConfig. ResumeMAC-I is a 16-bit message authentication token that the UE may calculate using the integrity algorithm (NIA or EIA) in the stored AS security context negotiated between the UE and the last serving gNB and the KRRCint from the stored AS security context with the following inputs:
[0083] * - Key: It can be set to the current KRRCint;
[0084] *-Bearer: All or at least one of its bits may be set to 1.
[0085] *-Direction: its bit can be set to 1;
[0086] * - count: all or at least one of its bits may be set to 1;
[0087] *-Message: It can be set to VarResumeMAC-Input with the following input:
[0088] **- Source Physical Cell Identity (PCI) (set to the physical cell identity of the PCell to which the UE was connected before the suspension of the RRC connection)
[0089] **- Target Cell-ID (set to the cell-identity of the first PLMN-Identity included in the PLMN-IdentityInfoList broadcasted in SIB1 of the target cell (i.e. the cell to which the UE is sending small data)
[0090] **-Source C-RNTI (set to the C-RNTI that the UE had in the PCell to which it was connected before the suspension of the RRC connection).
[0091] The UE resumes SRBs and DRBs, derives new security keys using the NextHopChainingCount provided in the RRCRelease message of the previous RRC connection, and reestablishes AS security. User data is encrypted and integrity protected (only for DRBs configured with UP integrity protection) and sent on DTCH, which is multiplexed with the RRCResumeRequest / RRCResumeRequest1 message on CCCH / CCCH1.
[0092] 2. The gNB verifies resumeMAC-I and transmits uplink data (S115) to the UPF.
[0093] 3. The gNB sends (S125) a RRCRelease message to keep the UE in RRC_INACTIVE. The PDCCH is addressed to the TC-RNTI. If downlink data is available, it is sent (S120) encrypted and integrity protected (only for DRBs configured with UP integrity protection) on the DTCH, multiplexed with the RRCRelease message on the DCCH. The gNB may decide not to send the RRCRelease message with the contention resolution identifier. In this case, upon completion of random access, the UE monitors the PDCCH addressed to the C-RNTI. UL / DL data may be exchanged between the UE and the gNB until the RRCRelease message is received or the SDT procedure is terminated.
[0094] Figure 2 A signaling flow for small data transmission using 2-step RA according to an embodiment of the present disclosure is shown.
[0095] 0. The criteria for initiating a 2-step RA for SDT are met. The UE selects a preamble / RO / PO from the preambles / RO / PO for SDT. The UE (S200) sends a random access preamble.
[0096] 1. The UE sends (S205) RRCResumeRequest / RRCResumeRequest1 to the gNB (same as the last serving gNB) on SRB 0 in the MsgA payload. It includes the full / short I-RNTI (resumeIdentity), the resume cause (resumeCause) and the authentication token (resumeMAC-I). The I-RNTI (short or full I-RNTI) is used for context identification and its value may be the same as the I-RNTI that the UE has received from the last serving gNB in the RRCRelease message with suspendConfig. ResumeMAC-I is a 16-bit message authentication token that the UE may calculate using the integrity algorithm (NIA or EIA) in the stored AS security context negotiated between the UE and the last serving gNB and the KRRCint from the stored AS security context with the following inputs:
[0097] * - Key: It can be set to the current KRRCint;
[0098] *-Bearer: All or at least one of its bits may be set to 1.
[0099] *-Direction: its bit can be set to 1;
[0100] * - count: all or at least one of its bits may be set to 1;
[0101] *-Message: It can be set to VarResumeMAC-Input with the following input:
[0102] **- Source PCI (set to the physical cell identity of the PCell to which the UE was connected before the suspension of the RRC connection)
[0103] **-Target Cell-ID (set to the cell identity (cellIdentity) of the first PLMN-Identity included in the PLMN-IdentityInfoList broadcasted in SIB1 of the target cell (i.e., the cell to which the UE is sending small data))
[0104] **-Source C-RNTI (set to the C-RNTI that the UE had in the PCell to which it was connected before the suspension of the RRC connection).
[0105] The UE recovers all or at least one of the SRBs and DRBs, derives new security keys using the NextHopChainingCount provided in the RRCRelease message of the previous RRC connection, and reestablishes AS security. User data is encrypted and integrity protected (only for DRBs configured with UP integrity protection) and sent on DTCH, which is multiplexed with the RRCResumeRequest / RRCResumeRequest1 message on CCCH / CCCH1.
[0106] 2. The gNB verifies ResumeMAC-I and transmits uplink data (S210) to the UPF.
[0107] 3. The gNB sends (S220) an RRCRelease message in MsgB to keep the UE in RRC_INACTIVE, as well as successRAR. The PDCCH is addressed to the C-RNTI. If downlink data is available, it is sent (S215) encrypted and integrity protected on the DTCH (only for DRBs configured with UP integrity protection), multiplexed with the RRCRelease message on the DCCH. The gNB may decide not to send the RRCRelease message together with the successRAR. In this case, upon completion of random access, the UE monitors the PDCCH addressed to the C-RNTI. UL / DL data can be exchanged between the UE and the gNB until the RRCRelease message is received or the SDT procedure is terminated.
[0108] Figure 3 A signaling flow for small data transmission using pre-configured PUSCH resources (or configured grant-based SDT (CG-SDT)) according to an embodiment of the present disclosure is shown.
[0109] The criteria for initiating SDT using pre-configured PUSCH resources are met.
[0110] In the preconfigured PUSCH resources, the UE sends (S300) RRCResumeRequest / RRCResumeRequest1 to the gNB (same as the last serving gNB) on SRB 0. It includes full / short I-RNTI (resumeIdentity), resume cause (resumeCause) and authentication token (resumeMAC-I). The I-RNTI (short or full I-RNTI) is used for context identification and its value can be the same as the I-RNTI that the UE has received from the last serving gNB in the RRCRelease message with suspendConfig. ResumeMAC-I is a 16-bit message authentication token that the UE can calculate using the integrity algorithm (NIA or EIA) in the stored AS security context negotiated between the UE and the last serving gNB and the KRRCint from the stored AS security context with the following inputs:
[0111] * - Key: It can be set to the current KRRCint;
[0112] *-Bearer: All or at least one of its bits may be set to 1.
[0113] *-Direction: its bit can be set to 1;
[0114] * - count: all or at least one of its bits may be set to 1;
[0115] *-Message: It can be set to VarResumeMAC-Input with the following input:
[0116] **- Source PCI (set to the physical cell identity of the PCell to which the UE was connected before the suspension of the RRC connection)
[0117] **- Target Cell-ID (set to the cell identity of the first PLMN-Identity included in the PLMN-IdentityInfoList broadcasted in SIB1 of the target cell (i.e. the cell to which the UE is sending small data)
[0118] **-Source C-RNTI (set to the C-RNTI that the UE had in the PCell to which it was connected before the suspension of the RRC connection).
[0119] The UE recovers all or at least one of the SRBs and DRBs, derives new security keys using the NextHopChainingCount provided in the RRCRelease message of the previous RRC connection, and reestablishes AS security. User data is encrypted and integrity protected (only for DRBs configured with UP integrity protection) and sent on the DTCH, which is multiplexed with the RRCResumeRequest / RRCResumeRequest1 message on the CCCH.
[0120] *The UE may instead send its small data by using one of the following options:
[0121] **RRCResumeRequest (or new RRC message). resumeIdentity, ResumeMAC-I, resumeCause, NAS container in RRCResumeRequest / RRCResumeRequest1. NAS container includes UL data.
[0122] **New MAC CE (resumeIdentity, ResumeMAC-I) + uplink data (on DTCH). resumeIdentity is provided for UE identification purposes. ResumeMAC-I is for security.
[0123] 2. The gNB verifies resumeMAC-I and transmits uplink data (S305) to the UPF.
[0124] 3. The gNB sends (S315) an RRCRelease message to keep the UE in RRC_INACTIVE. The PDCCH is addressed to the C-RNTI. The C-RNTI is the C-RNTI used by the UE in the cell from which it receives pre-configured PUSCH resources. Alternatively, the C-RNTI may be assigned together with the pre-configured PUSCH resources. If downlink data is available, it is sent (S310) encrypted and integrity protected (only for DRBs configured with UP integrity protection) on the DTCH, multiplexed with the RRCRelease message on the DCCH.
[0125] In response to the small data transmission, the UE may receive a signal (RRC message or DCI) for the purpose of releasing the preconfigured PUSCH or switching to a recovery procedure (ie, RRC_CONNECTED).
[0126] The UE is in RRC_CONNECTED. The UE receives an RRC Release with a suspension configuration and CG-SDT (Configured Grant-based SDT) resources. The UE enters the RRC_INACTIVE state. The UE starts the CG-SDT-Timer. At some point in the RRC_INACTIVE state, the SDT criteria are met (the DL RSRP of the cell is above the RSRP threshold, the data available for the SDT radio bearer (RB) is below the data volume threshold, etc.) and the criteria indicating CG-SDT are met and the UE initiates CG-SDT. The UE initiates CG-SDT only if the cell has not changed (i.e., the UE is in the same cell from which the UE last received an RRC Release message) and the time alignment (TA) is valid (i.e., the CG-SDT-Timer is running) and the CG resources for SDT are configured and at least one SSB associated with the CG resources is above the configured threshold. The CG resources occur periodically with a period P configured by the network.
[0127] Figure 4 A scenario is shown in which the CG-SDT timer expires after the initial HARQ transmission of the first UL MAC PDU carrying the RRC recovery request according to an embodiment of the present disclosure.
[0128] refer to Figure 4 , the CG-SDT timer may expire after the initial HARQ transmission of the first UL MAC PDU carrying the RRC recovery request. As a result, the UE has no opportunity to perform HARQ retransmission in the event that the initial HARQ transmission has failed. According to the current procedure, if the CG-SDT timer expires before receiving a response to the first UL MAC PDU transmission from the network during the CG-SDT, the UE transitions to RRC idle. Therefore, during Figure 4 In the scenario of , the UE transitions to RRC idle. This is inefficient, and the UE will need to initiate a connection establishment procedure in RRC idle to send data, resulting in increased latency and UE power consumption.
[0129] Figure 5 A scenario in which the CG-SDT timer expires before the initial HARQ transmission of the first UL MAC PDU carrying the RRC recovery request according to an embodiment of the present disclosure is illustrated.
[0130] refer to Figure 5, the CG-SDT timer may expire before the initial HARQ transmission of the first UL MAC PDU carrying the RRC resume request. As a result, the UE does not have the opportunity to send the first UL MAC PDU. According to the current procedure, if the CG-SDT timer expires before receiving a response to the first UL MAC PDU transmission from the network during the CG-SDT, the UE transitions to RRC idle. Therefore, during Figure 5 In the scenario of , the UE transitions to RRC idle. This is inefficient, and the UE will need to initiate a connection establishment procedure in RRC idle to send data, resulting in increased latency and UE power consumption.
[0131] Figure 6 A scenario before the initial HARQ transmission of the first ULMAC PDU carrying the RRC resume request using a suitable SSB according to an embodiment of the present disclosure is shown.
[0132] refer to Figure 6 , the CG-SDT timer may expire prior to the initial HARQ transmission of the first UL MAC PDU carrying the RRC resume request using a suitable SSB. In this example, the suitable SSB (SSB with SS-RSRP>threshold) is SSB 3, and the CG-SDT timer expires after initiation of the CG-SDT before the first CG opportunity corresponding to SSB 3 is available. As a result, the UE does not have the opportunity to send the first UL MAC PDU. According to the current procedure, if the CG-SDT timer expires before receiving a response to the first UL MAC PDU transmission from the network during the CG-SDT, the UE transitions to RRC idle. Therefore, during Figure 6 In the scenario of , the UE transitions to RRC idle. This is inefficient, and the UE will need to initiate a connection establishment procedure in RRC idle to send data, resulting in increased latency and UE power consumption.
[0133] According to an embodiment, a method for handling expiration of a CG-SDT timer during an ongoing CG-SDT process is provided.
[0134] Figure 7 The operation of the UE according to an embodiment of the present disclosure is shown. Figure 7 The operations shown in FIG. 1 are shown only for ease of understanding and may be omitted if they are not related to essential features of the present disclosure.
[0135] The UE is in the RRC_CONNECTED state. In operation S700, the UE may receive an RRCRelease message with a suspension configuration from the gNB. The RRCRelease message indicates CG resources for SDT. The UE may enter the RRC_INACTIVE state upon receiving the RRCRelease message with the suspension configuration.
[0136] Alternatively, the UE may be in the RRC_INACTIVE state. In operation S700, the UE may receive an RRCRelease message with a suspension configuration from the gNB during the SDT process in the RRC_INACTIVE state. The RRCRelease message may indicate the CG resources used for the SDT.
[0137] In operation S705, the UE may start a CG-SDT timer (also referred to as a timing alignment timer for CG-SDT) upon receiving the RRCRelease message including the CG resources for SDT. The value of the CG-SDT timer may be received in the RRCRelease message.
[0138] In operation S710, when in the RRC_INACTIVE state, upon the arrival of data for one or more SDT RBs, the SDT criteria are met (the DL RSRP of the cell is higher than the RSRP threshold, the data available for the SDT RB is lower than the data volume threshold, etc.) and the criteria for initiating CG-SDT are met, in operation S715, the UE may initiate a CG-SDT procedure. The UE may initiate a CG-SDT only if the cell has not changed (i.e., the UE is in the same cell from which the UE last received an RRC release message) and the TA is valid (e.g., the CG-SDT-Timer is running) and the CG resources for SDT are configured and at least one SSB associated with the CG resources is higher than the configured threshold. When initiating the SDT procedure, the UE may start an SDT timer or an SDT error detection timer. Note that the SDT timer may be different from the CG-SDT timer. The SDT timer may be stopped upon completion of the SDT procedure.
[0139] In operation S720, when the CG-SDT process is in progress, the CG-SDT timer may expire. In this embodiment of the present disclosure, when the CG-SDT process is in progress, the UE operation when the CG-SDT timer expires is as follows:
[0140] * The UE may stop using CG-SDT resources; and / or
[0141] *If the UE has not sent an initial UL MAC PDU including a CCCH message (which may include RRCResumeRequest / RRCResumeRequest1) during the ongoing SDT procedure, as determined in operation S722:
[0142] ** In operation S725, the UE may terminate the ongoing CG-SDT process. The UE may remain in the RRC_INACTIVE state. If the RA-SDT criteria are met, the UE may initiate a random access-based SDT process, as described above in Figure 1 and Figure 2 If the RA-SDT criteria are not met, the UE may initiate a non-SDT connection recovery procedure.
[0143] * Otherwise (i.e., if the UE has sent an initial UL MAC PDU including a CCCH message during the ongoing SDT procedure), as determined in operation S722:
[0144] **If the UE has not received a response from the network to the initial UL MAC PDU including the CCCH message sent by the UE (e.g., a hybrid automatic repeat request (HARQ) acknowledgement (ACK), or an L1-ACK or PDCCH addressed to the C-RNTI / SDT-RNTI, or the UE has received an RRC message or a DCCH SDU, or a PDCCH addressed to the C-RNTI / SDT-RNTI scheduling a new uplink transmission or downlink transmission, etc.), as determined in operation S724:
[0145] *** In operation S730, the UE may terminate the ongoing SDT process; and / or
[0146] ***In the example, upon termination, the UE may enter RRC_IDLE, stop the SDT timer; reset MAC; if the variable pendingRNA-Update is set to true, set it to false; discard UE inactive AS context, if any; release suspendConfig, if configured; discard KgNB key, KRRCenc key, KRRCint key, KUPint key and KUpenc key, if any; release all or at least one of the radio resources, including releasing RLC entities, MAC configurations and associated PDCP entities and SDAPs for all or at least one of the established RBs. In another example, upon termination, the UE may continue to be in RRC_INACTIVE; stop the SDT timer; reset the MAC; if the variable pendingRNA-Update is set to true, set it to false; discard the UE inactive AS context, if any; release the suspendConfig, if configured; discard the KgNB key, KRRCenc key, KRRCint key, KUpint key and KUpenc key, if any; suspend the radio bearers and SRB1 configured for SDT; in RRC_INACTIVE, the UE may initiate a RA-SDT procedure or initiate a traditional RRC recovery procedure.
[0147] **Otherwise (i.e., if the UE has received a response), as determined in operation S724, the UE may:
[0148] *** In operation S735, the ongoing SDT process is not terminated (continued); and / or
[0149] ***Suspend UL TX (except RA preamble and MsgA transmission); and / or
[0150] ***Wait for PDCCH command from gNB; and / or
[0151] *** Upon receiving the PDCCH command, a random access procedure is initiated (in an alternative example, instead of waiting for the PDCCH command, the UE may initiate a random access procedure. Details of the random access procedure are as explained in the background); and / or
[0152] *** Upon completion of the random access procedure, resume UL TX; and / or
[0153] ***During the SDT procedure, for SDT, a dynamic grant (DG) is used, i.e., a grant allocated to the UE using a PDCCH addressed to the C-RNTI / SDT-RNTI.
[0154] Criteria for RA-SDT: If all or at least one of the following conditions is met, the RA-SDT criteria can be considered to be met.
[0155] 1) Available data amount <= data amount threshold (the data amount threshold is signaled by the gNB and may be specific to RA-SDT or common to CG-SDT and RA-SDT).
[0156] 2) RSRP (cell quality or path loss referenced RSRP) is greater than or equal to the configured threshold (the threshold is signaled by the gNB and can be specific to RA-SDT or common for CG-SDT and RA-SDT).
[0157] 3) A set of random access resources for performing RA-SDT is selected on the selected UL carrier.
[0158] *If SUL is not configured in the cell, the selected carrier can be NUL.
[0159] *If SUL is configured in the cell, but RA resources / RO for SDT are not configured for SUL, the selected carrier may be NUL.
[0160] *If SUL is configured in the cell and RSRP is greater than a threshold (the threshold is signaled by the gNB), the selected carrier can be NUL.
[0161] *If SUL is configured in the cell and RSRP is not greater than a threshold (the threshold is signaled by the gNB), the selected carrier may be SUL.
[0162] *If SUL is configured in the cell, but RA resources / RO for SDT are not configured for NUL, the selected carrier may be SUL.
[0163] *For each UL transmission, if RA resources / RO are first available for SUL in time, SUL may be selected for that UL transmission. If RA resources / RO are first available for NUL in time, NUL may be selected for that UL transmission.
[0164] Criteria for selecting CG-SDT: If all or at least one of the following conditions is met, the CG-SDT criteria can be considered to be met.
[0165] 1) Available data amount <= data amount threshold (the data amount threshold is signaled by the gNB and can be specific to CG-SDT or common to CG-SDT and RA-SDT).
[0166] 2) RSRP (cell quality or path loss referenced RSRP) is greater than or equal to the configured threshold (the threshold is signaled by the gNB and can be specific to CG-SDT or common for CG-SDT and RA-SDT).
[0167] 3) CG-SDT resources are configured on the selected UL carrier and are valid (e.g., TA is valid (TAT-SDT timer is running), the UE's cell is the same as the cell from which the CG resources are received).
[0168] *If SUL is not configured in the cell, the selected carrier can be NUL.
[0169] *If SUL is configured in the cell, but the CG resources for SDT are not configured for SUL, the selected carrier can be NUL.
[0170] *If SUL is configured in the cell and RSRP is greater than a threshold (the threshold is signaled by the gNB), the selected carrier can be NUL.
[0171] *If SUL is configured in the cell and RSRP is not greater than a threshold (the threshold is signaled by the gNB), the selected carrier may be SUL.
[0172] *If SUL is configured in the cell, but CG resources for SDT are not configured for NUL, the selected carrier may be SUL.
[0173] *For each UL transmission, if CG resources are first available in time for SUL, then SUL may be selected for that UL transmission. If CG resources are first available in time for NUL, then NUL may be selected for that UL transmission.
[0174] Figure 8 The operation of the UE according to an embodiment of the present disclosure is shown. Figure 8 The operations shown in FIG. 1 are shown only for ease of understanding and may be omitted if they are not related to essential features of the present disclosure.
[0175] refer to Figure 8 , the UE may be in the RRC_CONNECTED state. In operation S800, the UE may receive an RRCRelease message with a suspension configuration from the gNB. The RRCRelease message may indicate CG resources for SDT. The UE may enter the RRC_INACTIVE state upon receiving the RRCRelease message with the suspension configuration.
[0176] Alternatively, the UE may be in the RRC_INACTIVE state. In operation S800, the UE may receive an RRCRelease message with a suspension configuration from the gNB during the SDT process in the RRC_INACTIVE state. The RRCRelease message may indicate the CG resources used for the SDT.
[0177] In operation S805, the UE may start a CG-SDT timer (also referred to as a timing alignment timer for CG-SDT) upon receiving the RRCRelease message including the CG resources for SDT. The value of the CG-SDT timer may be received in the RRCRelease message.
[0178] In operation S810, when in the RRC_INACTIVE state, upon arrival of data for one or more SDT RBs, if the SDT criteria are met (DL RSRP of the cell is higher than the RSRP threshold, data available for the SDT RB is lower than the data amount threshold, etc.):
[0179] * The UE may check the remaining time of the CG-SDT-Timer; and / or
[0180] *If during the remaining time, at least "N" (≥1) CG opportunities corresponding to suitable SSBs (i.e., SSBs whose SS-RSRP is above the threshold) are not available, as determined in operation S812:
[0181] **In operation S815, the UE may not trigger CG-SDT. If the RA-SDT criteria are met, the UE may initiate RA-SDT. If the RA-SDT criteria are not met, the UE may initiate a non-SDT connection recovery procedure.
[0182] **Parameter N may be predefined or configured by the network (RRC signaling, such as RRCRelease message or RRCReconfiguration message or SI)
[0183] * Otherwise (i.e., if during the remaining time, at least "N" CG opportunities corresponding to suitable SSBs (i.e., SSBs whose SS-RSRP is above the threshold) are available), as determined in operation S812:
[0184] **In operation S820, the UE may trigger the CG-SDT if all or at least one of the other criteria for initiating the CG-SDT is met, and the UE may initiate the CG-SDT procedure. The UE may initiate the CG-SDT only if the cell has not changed (i.e., the UE is in the same cell from which the UE last received an RRC release message) and the TA is valid (e.g., the CG-SDT-Timer is running) and the CG resources for SDT are configured and at least one SSB associated with the CG resources is above the configured threshold. When initiating the SDT procedure, the UE may start an SDT timer or an SDT error detection timer. Note that the SDT timer may be different from the CG-SDT timer. The SDT timer may be stopped when the SDT procedure is completed.
[0185] Above Figure 7 An example of a standard for RA-SDT or CG-SDT is described in .
[0186] According to an embodiment, a method for radio link management (RLM) and / or beam failure detection (BFD) is provided.
[0187] In 5G, RLM is supported. The UE is configured with RLM-RS resources. On each RLM-RS resource, the UE estimates the downlink radio link quality and compares it with thresholds Qout and Qin. Qout: The level at which the downlink radio link cannot be reliably received, and corresponds to the out-of-sync block error rate (BLERout). Qin: The level at which the downlink radio link quality can be received with higher reliability, and corresponds to the in-sync block error rate (BLERin). Signaling BLERout and BLERin. When the downlink radio link quality on all or at least one of the configured RLM-RS resources is worse than Qout, an out-of-sync indication is generated. When the downlink radio link quality on at least one of the configured RLM-RS resources is better than Qin, a synchronization indication is generated. The RRC layer in the UE performs RLM based on these indications. When N310 consecutive "out-of-sync" indications are received from the lower layer SpCell when T300, T301, T304, T311, T316 and T319 are not running, the UE starts timer T310 for the corresponding SpCell. When N311 consecutive "in-sync" indications are received from the lower layer SpCell when T310 is running, the UE may: stop timer T310 for the corresponding SpCell. If T310 expires, RLF is declared. Frequent evaluations for RLM may increase UE power consumption for low mobility UEs. Therefore, 5G supports RLM relaxation, in which the UE can relax measurements for RLM when certain criteria (low mobility and / or good serving cell quality) are met.
[0188] In 5G, BFD is supported. The UE is configured with BFD-RS resources. On each BFD-RS resource, the UE estimates the downlink radio link quality and compares it with the threshold Qout_LR. Qout: The level at which the downlink radio link cannot be reliably received and corresponds to the block error rate (BLERout_LR is 10%). When the downlink radio link quality on all or at least one of the configured BFD-RS resources is worse than Qout_LR, a beam failure instance indication is generated. The MAC layer detects beam failure based on the indication and initiates beam failure recovery. Frequent evaluations for BFD may increase UE power consumption for low mobility UEs. Therefore, 5G supports BFD relaxation, where the UE can relax measurements for BFD when certain criteria (low mobility and / or good serving cell quality) are met.
[0189] In 5G, the relaxed measurement criterion for low mobility is defined as follows:
[0190] The relaxed measurement criteria for UEs with low mobility in RRC_CONNECTED are met when:
[0191] *(SS-RSRPRef-SS-RSRP) <SSearchDeltaP-Connected,
[0192] in:
[0193] *SS-RSRP = current L3 RSRP measurement of the SpCell based on SSB (dB).
[0194] *SS-RSRPRef = Reference L3 RSRP measurement of the SSB-based SpCell (dB), set as follows:
[0195] **After receiving a low mobility criteria configuration, or
[0196] **After applying reconfigurationWithSync in the CG's spCellConfig while low mobility criteria are configured, after the CG's MAC successfully completes the random access procedure, or
[0197] **If (SS-RSRP-SS-RSRPRef)>0, or
[0198] **If the relaxed measurement criteria are not yet met for TSearchDeltaP-Connected:
[0199] ***UE can set the value of SS-RSRPRef to the current SS-RSRP value of SpCell.
[0200] **SSearchDeltaP-Connected is signaled by gNB in RRCReconfiguration message
[0201] **TSearchDeltaP-Connected is signaled by gNB in RRCReconfiguration message
[0202] In 5G, the relaxed measurement criteria for good serving cell quality are defined as follows:
[0203] After receiving the good serving cell quality criterion configuration, starting to evaluate the relaxed measurement criterion for the good serving cell quality of the RLM, and satisfying the relaxed measurement criterion when the downlink radio link quality on the configured RLM-RS resources is evaluated to be better than a threshold value Qin+XdB, wherein
[0204] *Qin is specified in section 8.1 of TS 38.133.
[0205] *X is the parameter offset in goodServingCellEvaluationRLM (good serving cell evaluation RLM), where goodServingCellEvaluationRLM is signaled by the gNB in the serving cell configuration of the SpCell.
[0206] After receiving the good serving cell quality criterion configuration, starting to evaluate the relaxed measurement criterion for the good serving cell quality for BFD, and when the downlink radio link quality on the configured BFD-RS resources is evaluated to be better than the threshold Qin+XdB, the relaxed measurement criterion is met, where
[0207] *Qin is specified in section 8.1 of TS 38.133.
[0208] *X is the parameter offset in goodServingCellEvaluationBFD (good serving cell evaluation BFD) where goodServingCellEvaluationBFD is signaled by the gNB in the serving cell configuration of the serving cell.
[0209] In an example, the UE may:
[0210] 1> If configured to provide a relaxation state for RLM measurements of a cell group, then:
[0211] 2> if the UE has not sent a UEAssistanceInformation message with rlm-MeasRelaxationState since it was configured to provide a relaxation state of RLM measurements for a cell group; or
[0212] 2> If the relaxation state of RLM measurements for the cell group has changed since the last transmission of a UEAssistanceInformation message including the rlm-MeasRelaxationState for the cell group, and the timer T34x associated with the cell group is not running,:
[0213] 3> Start timer T34x with the timer value set to rlm-RelaxtionReportingProhibitTimer (signalled by gNB in RRCReconfiguration message);
[0214] 3> Initiate the transmission of the UEAssistanceInformation message to provide the relaxation status of the RLM measurement of the cell group;
[0215] 1> If it is configured to provide the relaxed state of BFD measurement of the serving cell of the cell group:
[0216] 2> if the UE has not sent a UEAssistanceInformation message with bfd-MeasRelaxationState since it was configured to provide a relaxation state of BFD measurements for a cell group; or
[0217] 2> If the relaxation state of BFD measurements in any serving cell of the cell group has changed since the last transmission of a UEAssistanceInformation message including the bfd-MeasRelaxationState of the cell group, and timer T34y associated with the cell group is not running:
[0218] 3> start timer T34y with the timer value set to bfd-RelaxtionReportingProhibitTimer (signalled by gNB in RRCReconfiguration message);
[0219] 3> Initiate transmission of a UEAssistanceInformation message to provide the relaxed status of the BFD measurement of the serving cell of the cell group.
[0220] 1> If it is configured to provide the relaxed state of BFD measurement of the serving cell of the cell group:
[0221] 2> if the UE has not sent a UEAssistanceInformation message with bfd-MeasRelaxationState since it was configured to provide a relaxation state for BFD measurements for a cell group; or
[0222] 2> if the relaxation state of BFD measurements in any SCell of the cell group has changed since the last transmission of a UEAssistanceInformation message including bfd-MeasRelaxationState for the cell group, and timer T34y associated with the cell group is not running; or
[0223] 2> If the relaxation state of BFD measurements in the SpCell of the cell group has changed since the last transmission of the UEAssistanceInformation message including the bfd-MeasRelaxationState of the cell group:
[0224] 3> Start timer T34y with the timer value set to bfd-RelaxtionReportingProhibitTimer (signalled by gNB in RRCReconfiguration message);
[0225] 3> Initiate the transmission of the UEAssistanceInformation message to provide the relaxed status of the BFD measurement of the serving cell of the cell group.
[0226] 1> If the transmission of the UEAssistanceInformation message is initiated to provide the relaxation status of the RLM measurement for the cell group:
[0227] 2> If the UE performs RLM measurement relaxation for a cell group:
[0228] 3> Set rlm-MeasRelaxationState to true;
[0229] 2> Otherwise:
[0230] 3> Set rlm-MeasRelaxationState to false;
[0231] 1> If the transmission of the UEAssistanceInformation message is initiated to provide the relaxation status of the BFD measurement for the cell group:
[0232] 2> For each serving cell of the cell group:
[0233] 3> If the UE performs BFD measurement relaxation on the serving cell:
[0234] 4> Set the nth bit of bfd-MeasRelaxationState to '1', where n is equal to the servCellIndex (serving cell index) value of the serving cell + 1;
[0235] 3> Otherwise:
[0236] 4> Set the nth bit of bfd-MeasRelaxationState to '0', where n is equal to the servCellIndex value of the serving cell + 1.
[0237] If the relaxation state of RLM measurements for a cell group has changed since the last transmission of a UEAssistanceInformation message including rlm-MeasRelaxationState for the cell group and timer T34x associated with the cell group is running, the UE shall not send a UEAssistanceInformation message including rlm-MeasRelaxationState. As a result, the UE and gNB will not be synchronized with respect to the relaxation state for RLM.
[0238] If the relaxation state of BFD measurements in any serving cell of the cell group has changed since the last transmission of a UEAssistanceInformation message including bfd-MeasRelaxationState for the cell group and timer T34y associated with the cell group is running: The UE shall not send a UEAssistanceInformation message including bfd-MeasRelaxationState. As a result, the UE and the gNB will not be synchronized with respect to the relaxation state for BFD.
[0239] Solution 1
[0240] If the relaxation state of the RLM measurements for a cell group has been changed from "relaxed" to "not relaxed" for the cell group (i.e. the criteria for relaxation (low mobility and / or good serving cell quality) are no longer met) and the timer T34x associated with the cell group is running:
[0241] * In one example, the UE immediately enters the no-relaxation mode, i.e. it stops applying RLM relaxations.
[0242] *In another example, the UE continues to apply relaxations until a timer T34x associated with the cell group expires.
[0243] Solution 2
[0244] If the relaxation state of the RLM measurements for a cell group has been changed from "not relaxed" to "relaxed" for the cell group (i.e. the criteria for relaxation (low mobility and / or good serving cell quality) are met) and the timer T34x associated with the cell group is running:
[0245] * In one example, the UE immediately enters relaxation mode, i.e. it starts applying RLM relaxation.
[0246] *In another example, the UE continues to not apply relaxation until the timer T34x associated with the cell group expires.
[0247] Solution 3
[0248] If the relaxation state of BFD measurements for cells of a cell group has been changed from "relaxed" to "not relaxed" for a cell (i.e. the criteria for relaxation (low mobility and / or good serving cell quality) are no longer met) and the timer T34y associated with the cell group is running:
[0249] * In one example, the UE immediately enters the no-relaxation mode, i.e. it stops applying BFD relaxations.
[0250] *In another example, the UE continues to apply relaxations until the timer T34y associated with the cell group expires.
[0251] Solution 4
[0252] If, for a cell group, the relaxation state of BFD measurements for cells of the cell group has been changed from "not relaxed" to "relaxed" (i.e., the criteria for relaxation (low mobility and / or good serving cell quality) are met) and the timer T34y associated with the cell group is running:
[0253] * In one example, the UE immediately enters relaxation mode, i.e. it starts applying BFD relaxation.
[0254] *In another example, the UE continues to not apply relaxation until the timer T34y associated with the cell group expires.
[0255] Fig. 9 is a block diagram of a terminal according to an embodiment of the present disclosure.
[0256] refer to Fig. 9 The terminal includes a transceiver 910, a controller 920, and a memory 930. The controller 920 may refer to a circuit, an application specific integrated circuit (ASIC), or at least one processor. The transceiver 910, the controller 920, and the memory 930 are configured to execute the drawings (for example, Figures 1 to 8 ) or the operation of the UE described above. Although the transceiver 910, the controller 920, and the memory 930 are shown as separate entities, they may be implemented as a single entity, such as a single chip. Alternatively, the transceiver 910, the controller 920, and the memory 930 may be electrically connected or coupled to each other.
[0257] The transceiver 910 may transmit and receive signals to and from other network entities (eg, a base station).
[0258] The controller 920 may control the UE to perform the function according to one of the above-described embodiments.
[0259] For example, the controller 920 is configured to receive an RRC release message including pause configuration information and CG-SDT configuration information via the transceiver, start a timer associated with the TA for CG-SDT based on the CG-SDT configuration information, identify that the criteria for the SDT process are met, and perform the RA-SDT process when any CG opportunity corresponding to an SSB with an RSRP higher than a threshold is unavailable while the timer associated with the TA for CG-SDT is running, and the criteria for the RA-SDT process are met.
[0260] In an embodiment, the operation of the terminal can be implemented using a memory 930 storing corresponding program codes. Specifically, the terminal can be equipped with a memory 930 to store program codes that implement the desired operation. In order to perform the desired operation, the controller 920 can read and execute the program codes stored in the memory 930 by using a processor or a central processing unit (CPU).
[0261] Fig.10 is a block diagram of a base station according to an embodiment of the present disclosure.
[0262] refer to Fig.10 , the base station includes a transceiver 1010, a controller 1020 and a memory 1030. The transceiver 1010, the controller 1020 and the memory 1030 are configured to execute the drawings (for example, Figures 1 to 8 ) or described above. Although transceiver 1010, controller 1020, and memory 1030 are shown as separate entities, they may be implemented as a single entity, such as a single chip. Transceiver 1010, controller 1020, and memory 1030 may be electrically connected or coupled to each other.
[0263] The transceiver 1010 may transmit and receive signals to and from other network entities (eg, terminals).
[0264] The controller 1020 may control the base station to perform the function according to one of the above embodiments. The controller 1020 may refer to a circuit, an ASIC, or at least one processor.
[0265] For example, the controller 1020 is configured to transmit an RRC release message including the suspension configuration information and the CG-SDT configuration information via the transceiver, and perform the RA-SDT procedure or the CG-SDT procedure.
[0266] In an embodiment, the operation of the base station can be implemented using a memory 1030 storing corresponding program codes. Specifically, the base station can be equipped with a memory 1030 to store program codes that implement the desired operation. In order to perform the desired operation, the controller 1020 can read and execute the program code stored in the memory 1030 by using a processor or CPU.
[0267] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.
[0268] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.
Claims
1. A method performed by a terminal in a wireless communication system, the method include: receiving a radio resource control (RRC) release message, the RRC release message including suspension configuration information and configured grant-small data transfer (CG-SDT) configuration information; Starting a timer related to time alignment (TA) for CG-SDT based on the CG-SDT configuration information; Identify criteria that meet the requirements for a small data transfer (SDT) process; as well as The RA-SDT procedure is performed when any configured grant (CG) opportunity corresponding to a synchronization signal block (SSB) with a reference signal received strength (RSRP) above a threshold is not available while a timer associated with a TA for CG-SDT is running, and the criteria for a random access-small data transfer (RA-SDT) procedure are met.
2. The method according to claim 1, further comprising: include: The CG-SDT process is performed when at least one CG opportunity corresponding to an SSB with an RSRP above a threshold is available while a timer associated with a TA for CG-SDT is running and the criteria for the CG-SDT process are met.
3. The method according to claim 1, in, In case any CG opportunity corresponding to an SSB with RSRP above the threshold is not available while the timer associated with the TA for CG-SDT is running and the criteria for the RA-SDT process is not met, the SDT process is not initiated.
4. The method according to claim 1, in, The threshold is configured by CG-SDT configuration information.
5. The method according to claim 1, in, In case the data amount of at least one radio bearer (RB) configured for the SDT procedure is less than or equal to a data amount threshold and the downlink RSRP is above an RSRP threshold, the criteria for the SDT procedure are met.
6. The method according to claim 1, further comprising: include: Entering the RRC inactive state based on the suspension configuration information.
7. The method according to claim 1, in, The RA-SDT procedure is performed based on 2-step random access or 4-step random access.
8. The method according to claim 2, in, The CG-SDT procedure is performed on the same cell on which the RRC release message was received.
9. A terminal in a wireless communication system, the terminal include: Transceiver; as well as The controller is configured as: receiving, via the transceiver, a radio resource control (RRC) release message, the RRC release message including suspension configuration information and configured grant-small data transfer (CG-SDT) configuration information, Starting a timer related to time alignment (TA) for CG-SDT based on the CG-SDT configuration information, Identify criteria that meet the criteria for a Small Data Transfer (SDT) process, and The RA-SDT procedure is performed when any configured grant (CG) opportunity corresponding to a synchronization signal block (SSB) with a reference signal received strength (RSRP) above a threshold is not available while a timer associated with a TA for CG-SDT is running, and the criteria for a random access-small data transfer (RA-SDT) procedure are met.
10. The terminal according to claim 9, in, The controller is also configured to: The CG-SDT process is performed when at least one CG opportunity corresponding to an SSB with an RSRP above a threshold is available while a timer associated with a TA for CG-SDT is running and the criteria for the CG-SDT process are met.
11. The terminal according to claim 9, in, In case any CG opportunity corresponding to an SSB with RSRP above the threshold is not available while the timer associated with the TA for CG-SDT is running and the criteria for the RA-SDT process is not met, the SDT process is not initiated.
12. The terminal according to claim 9, in, The threshold is configured by the CG-SDT configuration information, and The RA-SDT process is performed based on 2-step random access or 4-step random access.
13. The terminal according to claim 9, in, In case the data amount of at least one radio bearer (RB) configured for the SDT procedure is less than or equal to a data amount threshold and the downlink RSRP is above an RSRP threshold, the criteria for the SDT procedure are met.
14. The terminal according to claim 9, in, The controller is also configured to: Entering the RRC inactive state based on the suspension configuration information.
15. The terminal according to claim 10, in, The CG-SDT procedure is performed on the same cell on which the RRC release message was received.
