Paging for mobile station terminated (MT) small data transmission (SDT)
By utilizing paging messages and pre-configured resources in the 5G NR system, the user equipment transmits small data in an inactive state, solving the problems of low efficiency and high power consumption of small and medium-sized data transmission in the prior art, and achieving efficient data Transmission and energy efficiency improvement.
Patent Information
- Application Number
- CN202380031254.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-28
- Filing Date
- 2023-03-24
- Publication Date
- 2024-11-12
AI Technical Summary
Prior Art In 5G NR systems, inactive mobile station terminated user equipment (UE) needs to frequently switch to the connection state when performing small data transmission, resulting in increased power consumption and signaling overhead, and cannot be used in non-instance. Efficiently handle small data transmission in active state.
By using paging messages and pre-configured resources to perform small data transmission between the user equipment (UE) and the network node, the user equipment remains inactive after receiving the paging message and uses pre-configured resources to perform small data transmission. , and send a response after the transmission is completed to avoid frequent transitions to the connection state.
It realizes efficient processing of small data transmission in an inactive state, reduces power consumption and signaling overhead, and improves the energy efficiency and performance of the system.
Smart Images

Figure CN118947188A_ABST
Abstract
Description
Background Art Technical Field
[0001] The present disclosure relates to the transmission and reception of signals in a communication system. In particular, the present disclosure relates to methods and apparatus for such transmission and reception.
[0002] Description of related technologies
[0003] The 3rd Generation Partnership Project (3GPP) works on technical specifications for the next generation of cellular technology, also known as fifth generation (5G), including "New Radio" (NR) radio access technology (RAT) operating in the frequency range up to 100 GHz. NR is a follower of the technology represented by Long Term Evolution (LTE) and LTE-Advanced (LTE-A).
[0004] For systems such as LTE and NR, further improvements and options may facilitate efficient operation of the communication systems as well as specific equipment related to the systems. Summary of the invention
[0005] One non-limiting and exemplary embodiment facilitates efficient handling of small mobile-terminated data transmissions in an inactive state.
[0006] In an embodiment, the technology disclosed herein is characterized by an apparatus (e.g., user equipment UE). The apparatus includes a transceiver and a circuit. The circuit receives a paging message while in an inactive state in operation. In response to the paging message, the circuit determines to remain in the inactive state to receive small data. While remaining in the inactive state, the circuit sends a response to the paging message to a network node within a transmission opportunity associated with a preconfigured resource.
[0007] It should be noted that the general or specific embodiments may be implemented as a system, method, integrated circuit, computer program, storage medium or any selective combination thereof. For example, an integrated circuit may control a process of a UE or a network node.
[0008] Additional benefits and advantages of the disclosed embodiments will become apparent from the description and drawings. Benefits and / or advantages can be obtained individually from various embodiments and features of the description and drawings, and these embodiments and features do not need to be provided in their entirety in order to obtain one or more such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Hereinafter, exemplary embodiments are described in more detail with reference to the accompanying drawings.
[0010] Figure 1 An exemplary architecture of a 3GPP NR system is shown;
[0011] Figure 2 is a schematic diagram showing the functional division between NG-RAN and 5GC;
[0012] Figure 3 It is a timing diagram of the RRC connection establishment / reconfiguration process;
[0013] Figure 4 is a schematic diagram illustrating usage scenarios of enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC);
[0014] Figure 5 is a block diagram illustrating an exemplary 5G system architecture for non-roaming;
[0015] Figure 6 and Figure 7 Shows contention-based and contention-free RACH procedures;
[0016] Figure 8 Possible RRC state changes are shown;
[0017] Fig. 9 shows the message exchange of the RRC recovery procedure;
[0018] Fig.10 and Fig.11 shows the message exchange of the RRC release procedure;
[0019] Fig.12 A prior art message exchange for uplink data transmission is shown, including a state change of a UE from an inactive state to a connected state;
[0020] Fig.13 and Fig.14 An exemplary four-step RACH or two-step RACH that may be used for small data uplink transmission for RRC_INACTIVE UEs is shown;
[0021] Fig.15 An exemplary paging procedure for downlink small data transmission is shown;
[0022] Fig.16 is a block diagram illustrating an exemplary functional structure of a network node and a user equipment;
[0023] Fig.17 It is shown that it can be included in Fig.16 A block diagram of an exemplary functional structure of a circuit for processing small data in an exemplary user equipment;
[0024] Fig.18 It is shown that it can be included in Fig.16 A block diagram of an exemplary functional structure of an SDT processing circuit in an exemplary scheduling device device;
[0025] Fig.19 is a flowchart illustrating exemplary steps performed by a user device according to a first exemplary embodiment;
[0026] Fig. 20 is a flow chart illustrating exemplary steps performed by a network node according to a first exemplary embodiment;
[0027] Fig.21 is a flowchart illustrating exemplary steps performed by a user device according to a second exemplary embodiment;
[0028] Fig. 22 is a flow chart illustrating exemplary steps performed by a network node according to a second exemplary embodiment;
[0029] Fig.23 An example embodiment of receiving a paging message including an indication of an SDT is shown. DETAILED DESCRIPTION
[0030] 5G NR system architecture and protocol stack
[0031] 3GPP has been working on the next version of the 5th generation of cellular technology, or 5G for short, including the development of a new radio access technology (NR) operating in the frequency range up to 100 GHz. The first version of the 5G standard was completed at the end of 2017, which allowed trials and commercial deployment of smartphones compliant with the 5G NR standard to continue.
[0032] The overall system architecture assumes that the NG-RAN (Next Generation Radio Access Network) including gNB provides NG-Radio Access user plane (SDAP / PDCP / RLC / MAC / PHY) and control plane (RRC) protocol terminals, etc. to the UE. The gNBs are interconnected with each other through the Xn interface. The gNB is also connected to the NGC (Next Generation Core) by means of the Next Generation (NG) interface, more specifically to the AMF (Access and Mobility Management Function) (e.g., a specific core entity that executes AMF) by means of the NG-C interface, and to the UPF (User Plane Function) (e.g., a specific core entity that executes UPF) by means of the NG-U interface. Figure 1 The NG-RAN architecture is shown in (see, for example, 3GPP TS 38.300 v15.6.0, section 4).
[0033] The user plane protocol stack for NR (see, e.g., 3GPP TS 38.300, Section 4.4.1) includes the PDCP (Packet Data Convergence Protocol, see Section 6.4 of TS 38.300), RLC (Radio Link Control, see Section 6.3 of TS 38.300) and MAC (Medium Access Control, see Section 6.2 of TS 38.300) sublayers, which terminate at the gNB on the network side. In addition, a new access stratum (AS) sublayer (SDAP, Service Data Adaptation Protocol) is introduced above PDCP (see, e.g., subclause 6.5 of 3GPP TS 38.300). A control plane protocol stack is also defined for NR (see, e.g., TS 38.300, Section 4.4.2). An overview of the Layer 2 functionality is given in subclause 6 of TS 38.300. The functionality of the PDCP, RLC and MAC sublayers are listed in Sections 6.4, 6.3 and 6.2 of TS 38.300, respectively. The functions of the RRC layer are listed in subclause 7 of TS 38.300.
[0034] For example, the medium access control layer handles logical channel multiplexing as well as scheduling and scheduling-related functions, including handling different sets of parameters.
[0035] The physical layer (PHY) is responsible for, for example, decoding, PHY HARQ processing, modulation, multi-antenna processing, and mapping signals to appropriate physical time-frequency resources. It also handles the mapping of transport channels to physical channels. The physical layer provides services to the MAC layer in the form of transport channels. A physical channel corresponds to a set of time-frequency resources used to transmit a specific transport channel, and each transport channel is mapped to a corresponding physical channel. For example, the physical channels are PRACH (Physical Random Access Channel), PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel) for uplink and PDSCH (Physical Downlink Shared Channel), PDCCH (Physical Downlink Control Channel) and PBCH (Physical Broadcast Channel) for downlink.
[0036] NR use cases / deployment scenarios may include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), massive machine type communications (mMTC), which have different requirements in terms of data rate, latency, and coverage. For example, eMBB is expected to support peak data rates (20Gbps for downlink and 10Gbps for uplink) and the data rate experienced by users is about three times that provided by Advanced IMT. On the other hand, in the case of URLLC, there is a strong demand for ultra-low latency (0.5ms for both UL and DL for user plane latency) and high reliability (1-10 Mbps within 1ms). -5) puts forward more stringent requirements. Finally, mMTC may preferably require high connection density (1,000,000 devices / km in urban environments) 2 ), wide coverage in harsh environments, and extremely long battery life (15 years) for low-cost devices.
[0037] Therefore, an OFDM parameter set (e.g., subcarrier spacing, OFDM symbol duration, cyclic prefix (CP) duration, number of symbols per scheduling interval) that is suitable for one use case may not be suitable for another use case. For example, low-latency services may preferably require shorter symbol duration (and therefore larger subcarrier spacing) and / or fewer symbols per scheduling interval (also called TTI) compared to mMTC services. In addition, deployment scenarios with large channel delay spread may preferably require longer CP duration than scenarios with short delay spread. The subcarrier spacing should be optimized accordingly to maintain similar CP overhead. NR can support more than one subcarrier spacing value. Accordingly, subcarrier spacings of 15kHz, 30kHz, 60kHz, ... are being considered at this time. Symbol duration T u and subcarrier spacing Δf by the formula Δf = 1 / T u In a similar manner as in the LTE system, the term "resource element" may be used to denote a minimum resource unit consisting of one subcarrier of the length of one OFDM / SC-FDMA symbol.
[0038] In the new radio system 5G-NR, for each parameter set and carrier, a resource grid of subcarriers and OFDM symbols is defined for uplink and downlink, respectively. Each element in the resource grid is called a resource element and is identified based on a frequency index in the frequency domain and a symbol position in the time domain (see 3GPP TS 38.211v15.6.0). For example, downlink and uplink transmissions are organized into frames with a duration of 10ms, each frame consisting of ten subframes with a duration of 1ms respectively. In a 5g NR implementation, the number of consecutive OFDM symbols per subframe depends on the subcarrier spacing configuration. For example, for a 15-kHz subcarrier spacing, a subframe has 14 OFDM symbols (similar to an implementation compliant with LTE, assuming a normal cyclic prefix). On the other hand, for a 30-kHz subcarrier spacing, a subframe has two slots, each of which includes 14 OFDM symbols.
[0039] Compared to the LTE parameter sets (subcarrier spacing and symbol length), NR supports multiple different types of subcarrier spacing, marked by the parameter μ (in LTE, there is only 15kHz subcarrier spacing, corresponding to μ=0 in NR). The NR parameter set types are summarized in 3GPP TS 38.211, v15.7.0.
[0040] 5G NR functional division between NG-RAN and 5GC
[0041] Figure 2 The functional division between NG-RAN and 5GC is shown. The NG-RAN logical node is gNB or ng-eNB. 5GC has logical nodes AMF, UPF and SMF.
[0042] In particular, gNB and ng-eNB have the following main functions:
[0043] Functions for radio resource management, such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in both uplink and downlink (scheduling);
[0044] IP header compression, data encryption and integrity protection;
[0045] When the route to the AMF cannot be determined from the information provided by the UE, the AMF is selected at UE attach;
[0046] Routing user plane data to UPF;
[0047] Routing control plane information to AMF;
[0048] Connection establishment and release;
[0049] Scheduling and transmission of paging messages;
[0050] Scheduling and transmission of system broadcast information (from AMF or OAM);
[0051] Measurements and measurement reporting configuration for mobility and scheduling;
[0052] Transport level packet marking in uplink;
[0053] Session management;
[0054] Support for network slicing;
[0055] QoS flow management and mapping to data radio bearers;
[0056] Support for UEs in RRC_INACTIVE state;
[0057] NAS message distribution function;
[0058] Radio access network sharing;
[0059] Dual connectivity;
[0060] Tight interworking between NR and E-UTRA.
[0061] The access and mobility management function (AMF) has the following main functions:
[0062] Non-access layer NAS signaling terminal;
[0063] NAS signaling security;
[0064] Access layer AS security control;
[0065] Core network CN inter-node signalling for mobility between 3GPP access networks;
[0066] Idle mode UE reachability (including control and execution of paging retransmissions);
[0067] Registration area management;
[0068] Support for intra-system and inter-system mobility;
[0069] Access authentication;
[0070] Access authorization, including roaming rights checks;
[0071] Mobility management control (subscription and policy);
[0072] Support for network slicing;
[0073] Session management function SMF selection.
[0074] In addition, the user plane function UPF has the following main functions:
[0075] Anchor point for intra-RAT / inter-RAT mobility (when applicable);
[0076] External PDU session point for interconnection to data network;
[0077] Packet routing and forwarding;
[0078] Packet inspection and user plane parts of policy rule enforcement;
[0079] Business usage reports;
[0080] An uplink classifier that supports routing of traffic flows to the data network;
[0081] Support branching points for multi-host PDU sessions;
[0082] QoS processing in the user plane, such as packet filtering, gating, UL / DL rate enforcement; uplink service verification (SDF to QoS flow mapping);
[0083] Downlink packet buffering and downlink data notification trigger.
[0084] Finally, the session management function SMF has the following main functions:
[0085] Session management;
[0086] UE IP address allocation and management;
[0087] UP function selection and control
[0088] Configure traffic steering at the user plane function (UPF) to route traffic to the appropriate destination; control part for policy enforcement and QoS;
[0089] Downlink data notification.
[0090] RRC connection establishment and reconfiguration process
[0091] Figure 3 Some interactions between the UE, gNB and AMF (5GC entity) in the context of the UE transitioning from RRC_IDLE to RRC_CONNECTED for the NAS part are shown (see TS 38.300v15.6.0).
[0092] RRC is a higher layer signaling (protocol) used for UE and gNB configuration. Specifically, this transition involves the AMF preparing UE context data (including, for example, PDU session context, security keys, UE radio capabilities and UE security capabilities, etc.) and sending it to the gNB along with the Initial Context Setup Request. The gNB then activates AS security with the UE, which is performed by the gNB sending a SecurityModeCommand message to the UE and by the UE responding to the gNB with a SecurityModeComplete message. Thereafter, the gNB performs reconfiguration to establish a signaling radio bearer 2 SRB2 and a data radio bearer DRB by sending an RRCReconfiguration message to the UE and receiving an RRCReconfigurationComplete from the UE by the gNB in response. For a signaling-only connection, the steps related to RRCReconfiguration are skipped since SRB2 and DRB are not set up. Finally, the gNB notifies the AMF of the completion of the establishment process with an Initial Context Setup Response.
[0093] Therefore, in the present disclosure, an entity (e.g., AMF, SMF, etc.) of a fifth generation core (5GC) is provided, the entity including a control circuit and a transmitter, the control circuit establishing a next generation (NG) connection with a gNodeB in operation, the transmitter sending an initial context establishment message to the gNodeB via the NG connection in operation so that a signaling radio bearer is set between the gNodeB and a user equipment (UE). Specifically, the gNodeB sends a radio resource control RRC signaling containing a resource allocation configuration information element to the UE via the signaling radio bearer. Then, the UE performs uplink transmission or downlink reception based on the resource allocation configuration.
[0094] IMT use cases in 2020 and beyond
[0095] Figure 4 Some use cases for 5G NR are shown. In the 3rd Generation Partnership Project New Radio (3GPP NR), three use cases are being considered that have been envisioned to support various services and applications by IMT-2020. The specification of Phase 1 of enhanced mobile broadband (eMBB) has been finalized. In addition to further extending eMBB support, current and future work will involve the standardization of ultra-reliable low-latency communications (URLLC) and massive machine-type communications. Figure 4 Some examples of envisaged usage scenarios for IMT for 2020 and beyond are shown (see for example ITU-R M.2083 Figure 2 ).
[0096] URLLC use cases have stringent requirements on capabilities such as throughput, latency, and availability, and have been envisioned as one of the enablers for future vertical applications such as wireless control of industrial manufacturing or production processes, telemedicine surgery, distribution automation in smart grids, transportation safety, etc. Ultra-reliability for URLLC will be supported by identifying technologies that meet the requirements set by TR 38.913. For NR URLLC in Release 15, key requirements include a target user plane latency of 0.5ms for UL (uplink) and a target user plane latency of 0.5ms for DL (downlink). The general URLLC requirement for one transmission of a packet is a BLER (block error rate) of 1E-5 for a packet size of 32 bytes with a user plane latency of 1ms.
[0097] From a physical layer perspective, reliability can be improved in a number of possible ways. The current scope for improving reliability involves defining a separate CQI table for URLLC, a more compact DCI (downlink control information) format, repetition of PDCCH, etc. However, as NR becomes more stable and mature (for NR URLLC key requirements), the scope for achieving ultra-reliability can be expanded. Specific use cases for NR URLLC in Rel.15 include augmented reality / virtual reality (AR / VR), e-health, e-safety, and mission-critical applications.
[0098] In addition, the technical enhancements targeted by NR URLLC are aimed at latency improvement and reliability improvement. Technical enhancements for latency improvement include configurable parameter sets, non-slot-based scheduling with flexible mapping, unlicensed (configured authorization) uplink, slot-level repetition for data channels, and downlink preemption. Preemption means that the transmission for which resources have been allocated is stopped, and the allocated resources are used for another transmission that has been requested later but has lower latency / higher priority requirements. Therefore, the authorized transmission is preempted by the later transmission. Preemption is applicable independently of the specific service type. For example, a transmission for service type A (URLLC) can be used for transmission preemption of service type B (e.g., eMBB). Technical enhancements for reliability improvement include a dedicated CQI / MCS table for a target BLER of 1E-5.
[0099] The use case of mMTC (massive machine type communication) is characterized by a very large number of connected devices that typically send relatively small amounts of non-delay sensitive data. The devices are required to be low cost and have very long battery life. From the NR perspective, utilizing very narrow bandwidth portions is a possible solution to save power from the UE's perspective and achieve long battery life.
[0100] As mentioned above, the reliability range in NR is expected to become wider. A key requirement for all cases, and especially for URLLC and mMTC, is high reliability or ultra-reliability. Several mechanisms can be considered to improve reliability from a radio perspective and a network perspective. In general, there are several key potential areas that can help improve reliability. These areas include compact control channel information, data / control channel repetition, and diversity in the frequency domain, time domain, and / or spatial domain. These areas are generally applicable to reliability, regardless of the specific communication scenario.
[0101] For NR URLLC, further use cases with more stringent requirements have been identified, such as factory automation, transportation industry and power distribution. The more stringent requirements are higher reliability (up to 10 -6level), higher availability, packet sizes up to 256 bytes, time synchronization down to the order of a few μs, where depending on the frequency range the value can be one μs or a few μs, and short latency on the order of 0.5 to 1 ms, in particular a target user plane latency of 0.5 ms, depending on the use case.
[0102] In addition, for NR URLLC, several technical enhancements have been identified from a physical layer perspective. These include PDCCH (Physical Downlink Control Channel) enhancements related to compact DCI, PDCCH repetition, and increased PDCCH monitoring. In addition, UCI (Uplink Control Information) enhancements are related to enhanced HARQ (Hybrid Automatic Repeat Request) and CSI feedback enhancements. In addition, PUSCH enhancements related to mini-slot level frequency hopping and retransmission / repetition enhancements have been identified. The term "mini-slot" refers to a transmission time interval (TTI) that includes a smaller number of symbols than a slot (a slot including fourteen symbols).
[0103] QoS Control
[0104] The 5G QoS (Quality of Service) model is based on QoS flows, and supports QoS flows that require guaranteed flow bit rates (GBR QoS flows) and QoS flows that do not require guaranteed flow bit rates (non-GBR QoS flows). Therefore, at the NAS level, QoS flows are the finest granularity of QoS differentiation in a PDU session. QoS flows are identified within a PDU session by the QoS Flow ID (QFI) carried in the encapsulation header on the NG-U interface.
[0105] For each UE, the 5GC establishes one or more PDU Sessions. For each UE, the NG-RAN establishes at least one Data Radio Bearer (DRB) together with the PDU Session, and additional DRBs for the QoS flows of that PDU Session may be subsequently configured (it depends on when the NG-RAN does so), e.g. as described above with reference to Figure 3 As shown. NG-RAN maps packets belonging to different PDU sessions to different DRBs. NAS-level packet filters in the UE and in the 5GC associate UL and DL packets with QoS flows, while AS-level mapping rules in the UE and in the NG-RAN associate UL and DL QoS flows with DRBs.
[0106] Figure 5 The 5G NR non-roaming reference architecture is shown (see TS 23.501 v16.1.0, section 4.23). Figure 4The application function (AF) (e.g., an external application server with 5G services) described in the example interacts with the 3GPP core network to provide services, such as to support application impact on service routing, access network exposure function (NEF), or interact with the policy framework (see Policy Control Function, PCF) for policy control (e.g., QoS control). Based on the operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Application functions that the operator does not allow direct access to network functions use the external exposure framework via NEF to interact with related network functions.
[0107] Figure 5 Other functional units of the 5G architecture are shown, namely, the network slice selection function (NSSF), the network repository function (NRF), the unified data management (UDM), the authentication server function (AUSF), the access and mobility management function (AMF), the session management function (SMF) and the data network (DN), such as operator services, Internet access or third-party services. All or part of the core network functions and application services can be deployed and run on a cloud computing environment.
[0108] Therefore, in the present disclosure, an application server (e.g., AF of 5G architecture) is provided, which includes a transmitter and a control circuit, wherein the transmitter sends a request containing QoS requirements of at least one of URLLC, eMMB and mMTC services to at least one of the functions of 5GC (e.g., NEF, AMF, SMF, PCF, UPF, etc.) in operation to establish a PDU session including a radio bearer between a gNodeB and a UE according to the QoS requirements, and the control circuit performs the service using the established PDU session in operation.
[0109] Control Signal
[0110] In the present disclosure, the downlink control signal (information) related to the present disclosure may be a signal (information) transmitted through the PDCCH of the physical layer, or may be a signal (information) transmitted through the MAC control element (CE) or RRC of a higher layer. The downlink control signal may be a predefined signal (information).
[0111] The uplink control signal (information) related to the present disclosure may be a signal (information) transmitted through the PUCCH of the physical layer, or may be a signal (information) transmitted through the MAC CE of the higher layer or RRC. In addition, the uplink control signal may be a predefined signal (information). The uplink control signal may be replaced by uplink control information (UCI), first stage link control information (SCI), or second stage SCI.
[0112] terminal
[0113] Terminal or user terminal or user equipment or mobile station or mobile node is referred to as user equipment (UE) in LTE and NR. This can be a mobile device or communication device, such as a wireless phone, a smart phone, a tablet computer or a USB (universal serial bus) stick with the function of a user device. However, the term mobile device is not limited to this, and in general, a repeater may also have the functionality of this mobile device, and the mobile device may also act as a repeater. For example, a terminal is a physical entity (physical node) within a communication network. In addition, a communication device may be a communication device of any machine type, such as an IoT device, etc. A node may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a predetermined set of functions to other functional entities of the same or another node or network. A node may have one or more interfaces that attach a node to a communication facility or medium through which the node can communicate. Similarly, a network entity may have a logical interface that attaches a functional entity to a communication facility or medium, through which the network entity can communicate with other functional entities or communication nodes.
[0114] Base Station
[0115] In the present disclosure, a base station may be, for example, a transmit receive point (TRP), a cluster head, an access point, a remote radio head (RRH), an eNodeB (eNB), a gNodeB (gNB), a base station (BS), a base transceiver station (BTS), a base station unit, or a gateway. In addition, in sidelink communication, a terminal may be used instead of a base station. A base station may be a relay device that relays communications between a higher node and a terminal. A base station may also be a roadside unit. A base station may be, for example, a scheduling node or a network node that forms part of a network for providing services to a terminal. In particular, a base station may provide wireless access to a terminal. Communications between a terminal and a base station are generally standardized and may be defined by different layers, such as PHY, MAC, RRC, and the like. In LTE and NR, the wireless interface protocol stack includes a physical layer, a medium access layer (MAC), and higher layers. In the control plane, a higher layer protocol radio resource control protocol is provided. Via RRC, the base station may control the configuration of the terminal, and the terminal may communicate with the base station to perform control tasks (such as connection and bearer establishment, modification, etc.), measurements, and other functions. The term used in LTE is eNB (or eNodeB), while the currently used term for 5G NR is gNB. The term base station or radio base station here refers to a physical entity within a communication network. Like a mobile station, a base station may have several functional entities. A functional entity refers to a software or hardware module that implements and / or provides a predetermined set of functions to other functional entities of the same or another node or network. The physical entity performs some control tasks regarding the communication device, including one or more of scheduling and configuration. Note that the base station functionality and the communication device functionality may also be integrated within a single device. For example, a mobile terminal may also implement the functionality of a base station for other terminals. The term used in LTE is eNB (or eNodeB), while the currently used term for 5G NR is gNB.
[0116] Uplink / Downlink / Sidelink
[0117] The present disclosure may be applied to any one of an uplink, a downlink, and a sidelink.
[0118] The present disclosure can be applied to, for example, uplink channels (such as PUSCH, PUCCH and PRACH), downlink channels (such as PDSCH, PDCCH and PBCH), and sidelink channels (such as physical sidelink shared channel (PSSCH), physical sidelink control channel (PSCCH) and physical sidelink broadcast channel (PSBCH)).
[0119] PDCCH, PDSCH, PUSCH and PUCCH are examples of downlink control channel, downlink data channel, uplink data channel and uplink control channel, respectively. PSCCH and PSSCH are examples of sidelink control channel and sidelink data channel, respectively. PBCH and PSBCH are examples of broadcast channels, respectively, and PRACH is an example of random access channel.
[0120] Data channel / control channel
[0121] The present disclosure may be applied to any one of a data channel and a control channel. The channels in the present disclosure may be replaced with data channels including PDSCH, PUSCH and PSSCH and / or control channels including PDCCH, PUCCH, PBCH, PSCCH and PSBCH.
[0122] Reference signal
[0123] In the present disclosure, a reference signal is a signal known to both a base station and a mobile station, and each reference signal may be referred to as a reference signal (RS) or sometimes referred to as a pilot signal. The reference signal may be any of a DMRS, a channel state information reference signal (CSI-RS), a tracking reference signal (TRS), a phase tracking reference signal (PTRS), a cell-specific reference signal (CRS), and a sounding reference signal (SRS).
[0124] Time interval
[0125] In the present disclosure, the time resource unit is not limited to one or a combination of a time slot and a symbol, and may be a time resource unit (such as a frame, a superframe, a subframe, a time slot, a time slot subslot, a microslot) or a time resource unit (such as a symbol, an orthogonal frequency division multiplexing (OFDM) symbol, a single carrier frequency division multiplexing access (SC-FDMA) symbol) or other time resource units. The number of symbols included in a time slot is not limited to any number of symbols exemplified in the above embodiments, and may be other numbers of symbols.
[0126] frequency band
[0127] The present disclosure is applicable to any of licensed frequency bands and unlicensed frequency bands.
[0128] communication
[0129] The present disclosure can be applied to any of the communication between a base station and a terminal (Uu link communication), the communication between terminals (side link communication), and the vehicle-to-everything (V2X) communication. The channels in the present disclosure can be replaced with PSCCH, PSSCH, physical sidelink feedback channel (PSFCH), PSBCH, PDCCH, PUCCH, PDSCH, PUSCH, and PBCH.
[0130] In addition, the present disclosure can be applied to any of a terrestrial network using a satellite or a high altitude pseudo-satellite (HAPS) or a network other than a terrestrial network (NTN: non-terrestrial network). In addition, the present disclosure can be applied to a network with a large cell size, and a terrestrial network with a large delay compared to a symbol length or a time slot length, such as an ultra-wideband transmission network.
[0131] Antenna Port
[0132] An antenna port refers to a logical antenna (antenna group) formed by one or more physical antennas. That is, an antenna port does not necessarily refer to one physical antenna, and sometimes refers to an array antenna formed by multiple antennas, etc. For example, it is not defined how many physical antennas form an antenna port, but an antenna port is defined as the minimum unit through which a terminal is allowed to send a reference signal. An antenna port can also be defined as the minimum unit for multiplication of precoding vector weights.
[0133] Downlink control channel monitoring PDCCH, DCI
[0134] Many functions operated by the UE involve monitoring a downlink control channel (eg, PDCCH, see 3GPP TS 38.300 v15.6.0, section 5.2.3) to receive, for example, specific control information or data destined for the UE.
[0135] A non-exhaustive list of these functions is given below:
[0136] Paging message monitoring function,
[0137] System information acquisition function,
[0138] ·Signaling monitoring operation of DRX function,
[0139] Inactive monitoring operation of the DRX function,
[0140] · Random access response reception of the random access function,
[0141] · Reordering function of the Packet Data Convergence Protocol PDCP layer.
[0142] As described above, PDCCH monitoring is performed by the UE in order to identify and receive information intended for the UE, such as control information and user traffic (eg, DCI on the PDCCH, and user data on the PDSCH indicated by the PDCCH).
[0143] The control information in the downlink (which may be referred to as downlink control information DCI) has the same purpose in 5G NR as DCI in LTE, namely a special set of control information for scheduling downlink data channels (e.g., PDSCH) or uplink data channels (e.g., PUSCH). In 5G NR, many different DCI formats have been defined (see TS38.212v15.6.0 Section 7.3.1).
[0144] The DCI format indicates a predetermined format for forming and transmitting corresponding information. In particular, DCI formats 0_1 and 1_1 are used for scheduling PUSCH and PDSCH in one cell, respectively.
[0145] The PDCCH monitoring of each of these functions serves a specific purpose and therefore starts and ends as described. PDCCH monitoring is usually controlled based on at least a timer operated by the UE. The timer has the purpose of controlling PDCCH monitoring, such as limiting the maximum amount of time the UE is to monitor the PDCCH. For example, the UE may not need to monitor the PDCCH indefinitely, but may stop monitoring after a period of time in order to be able to save power.
[0146] As mentioned above, one of the purposes of DCI on PDCCH is the dynamic scheduling of resources in the downlink or uplink or even the sidelink. In particular, some formats of DCI are provided to carry an indication of the resources (resource allocation, RA) allocated to the data channel of a specific user. Resource allocation may include resource specifications in the frequency domain and / or time domain.
[0147] UE Identification
[0148] RNTI stands for Radio Network Temporary Identifier. For example, RNTI can be used to distinguish and identify UEs in a radio cell. In addition, RNTI can also identify a specific radio channel, a group of UEs in case of paging, a group of UEs for which power control is issued by the eNB, system information sent by the 5G gNB for all UEs. 5G NR defines many different identities for UEs, some of which are given in the following table (see 3GPP TS 38.321v15.8.0, section 7.1).
[0149]
[0150] In addition to the RNTIs identified above, there may be additional IDs, such as an inactive RNTI (I-RNTI) (see TS 38.331v15.8.0, Section 6.3.2). The inactive RNTI is used for a UE in the RRC_INACTIVE state, and for example in the process of identifying and locating the suspended UE context of the UE. According to one embodiment, when the UE moves (e.g., from RRC_CONNECTED) to the RRC_INACTIVE state, the network allocates an I-RNTI (e.g., as part of the RRCRelease message within SuspendConfig). There are two types of I-RNTIs, namely full I-RNTI and short I-RNTI. The network can inform the UE (e.g., as part of SIB1 system information block 1) which I-RNTI to use when resuming the connection. The full I-RNTI is a bit string with a length of 40 bits, while the short I-RNTI is a bit string with a length of 24 bits.
[0151] Random access process
[0152] Similar to LTE, 5G NR provides a RACH (Random Access Channel) procedure (or just a Random Access Procedure). For example, a UE can use the RACH procedure to access a cell it has found. The RACH procedure can also be used in other contexts within NR, such as:
[0153] For handover, when synchronization with a new cell is to be established;
[0154] reestablishing uplink synchronization with the current cell if synchronization is lost due to too long a period without any uplink transmission from the device;
[0155] If no dedicated scheduling request resources are configured for the device, uplink scheduling is requested.
[0156] There are many events that can trigger the UE to perform a random access procedure (see 3GPP TS 38.300, Section 9.2.6), including the following. The random access procedure is triggered by multiple events:
[0157] - Initial access from RRC_IDLE;
[0158] -RRC connection reestablishment process;
[0159] - DL or UL data arrives during RRC_CONNECTED when the UL synchronization state is "unsynchronized";
[0160] - UL data arrival during RRC_CONNECTED when there are no PUCCH resources available for SR;
[0161] -SR failed;
[0162] - Requests made by RRC upon synchronous reconfiguration (e.g. handover);
[0163] - Transition from RRC_INACTIVE;
[0164] - Establish time alignment for the secondary TAG;
[0165] - request additional SI (see clause 7.3);
[0166] -Beam failure recovery;
[0167] -Continued UL LBT failure on SpCell.
[0168] If the uplink transmission of the mobile terminal is time synchronized, the mobile terminal can be scheduled for uplink transmission. Therefore, the random access channel (RACH) procedure acts as an interface between an unsynchronized mobile terminal (UE) and the orthogonal transmission of the uplink radio access. For example, random access is used to achieve uplink time synchronization of a user equipment that has not yet acquired or lost its uplink synchronization. Once the user equipment has achieved uplink synchronization, the base station can schedule uplink transmission resources for it. A scenario related to random access is that a user equipment in the RRC_CONNECTED state switches from its current serving cell to a new target cell, performing a random access procedure in order to achieve uplink time synchronization in the target cell.
[0169] There may be at least two types of random access procedures, allowing access to be contention-based (ie, implying an inherent risk of collision) or contention-free (non-contention-based). An exemplary definition of a random access procedure may be found in 3GPP TS 38.321, v16.1.0, section 5.1.
[0170] The following will refer to Figure 6 and Figure 7 The RACH process is described in more detail below. Figure 6The contention-based random access procedure is described in more detail. The procedure consists of four "steps" and can therefore be referred to as, for example, a 4-step RACH procedure. First, the user equipment sends a random access preamble to the base station on the physical random access channel (PRACH) (i.e., message 1 of the RACH procedure). After the base station detects the RACH preamble, it sends a random access response (RAR) message (message 2 of the RACH procedure) on the PDSCH (physical downlink shared channel) addressed on the PDCCH, where the (random access) RA-RNTI identifies the time-frequency and time slot in which the preamble was detected. If multiple user equipments send the same RACH preamble in the same PRACH resource (this is also called a collision), they will receive the same random access response message. The RAR message can convey the detected RACH preamble, a timing alignment command (TA command) for synchronizing subsequent uplink transmissions based on the timing of the received preamble, an initial uplink resource allocation (grant) for transmitting the first scheduled transmission, and an allocation of a temporary cell radio network temporary identifier (T-CRNTI). The base station uses the T-CRNTI to address a mobile station whose RACH preamble is detected before the end of the RACH procedure, since the base station does not yet know the "real" identity of the mobile station at this time.
[0171] The user equipment monitors the PDCCH to receive a random access response message within a given time window (e.g., referred to as a RAR reception window), which may be configured by the base station. In response to the RAR message received from the base station, the user equipment transmits a first scheduled uplink transmission on the radio resources assigned by the grant in the random access response. The scheduled uplink transmission conveys an actual message having certain functions, such as an RRC connection request, an RRC recovery request, or a buffer status report.
[0172] In the event of a preamble collision in the first message of the RACH procedure (i.e., multiple user equipments have sent the same preamble on the same PRACH resource), the colliding user equipments will receive the same T-CRNTI within the random access response and will also collide in the same uplink resource when sending their scheduled transmissions in the third step of the RACH procedure. In the event that the scheduled transmission from one user equipment is successfully decoded by the base station, the contention for the other user equipments remains unresolved. To resolve this type of contention, the base station sends a contention resolution message (fourth message) addressed to the C-RNTI or temporary C-RNTI. The process ends here.
[0173] Figure 7A simplified contention-free random access procedure compared to a contention-based random access procedure is shown. The base station provides a dedicated preamble for random access to the user equipment in a first step so that there is no risk of collision, i.e., multiple user equipments send the same preamble. Therefore, the user equipment then sends the preamble signaled by the base station in the uplink on the PRACH resource. Since the situation where multiple UEs send the same preamble is avoided for contention-free random access, the contention-free random access procedure is essentially completed after the UE successfully receives the random access response.
[0174] 3GPP also defines a 2-step (contention-based) RACH procedure for 5G NR, where Message 1 (called MsgA), which corresponds to Messages 1 and 3 in the 4-step LTE / NR RACH procedure, is first transmitted. MsgA of the 2-step RACH type includes a preamble on the physical random access channel (PRACH) and a payload on the physical uplink shared channel (PUSCH). After the MsgA transmission, the UE monitors for a response from the gNB within a configured time window. The gNB will then respond with Message 2 (called MsgB), which corresponds to Messages 2 and 4 of the 4-step LTE / NR RACH procedure. The MsgB may include, for example, a Success Random Access Response (RAR), a Fallback RAR, and optionally a Fallback Indication. If contention resolution is successful when a Success RAR is received, the UE ends the Random Access procedure; whereas, if a Fallback RAR is received in MsgB, the UE performs a Message 3 transmission (as in the 4-step RACH procedure) and monitors for contention resolution. Some further exemplary assumptions are made for the 2-step RACH procedure, such as the UE keeps retrying the same RACH type until failure after deciding on the RACH type (e.g., 2-step RACH). But there may also be a possibility that the UE may switch to the 4-step RACH procedure after some retries of sending MsgA.
[0175] In addition, the network may semi-statically determine mutually exclusive radio resources to be used for performing the 2-step RACH procedure and the 4-step RACH procedure. The radio resources used to send the first message in the RACH procedure include at least a RACH opportunity and a preamble. For example, in the 2-step RACH procedure, the first message MsgA uses not only PRACH resources (e.g., RACH opportunity and preamble) but also associated PUSCH resources.
[0176] Generally, for the RACH preamble, see, for example, 3GPP TS 38.211 V16.2.0, "Table 6.3.3.2-2: Random access configuration for FR1 and paired spectrum / supplementary uplink" and section 6.3.3.2, "Mapping to physical resources".
[0177] RRC status (RRC_Connected, RRC_Inactive, RRC_Idle)
[0178] In LTE, the RRC state machine consists of only two states, the RRC idle state (mainly characterized by high power saving, UE autonomous mobility and no established UE connectivity towards the core network) and the RRC connected state, in which the UE can send user plane data while mobility is network controlled to support lossless service continuity. In conjunction with 5G NR, the LTE-related RRC state machine is extended to inactive states (see, for example, TS 38.331v16.1.0, Figure 4 .2.1-1 and 4.2.1-2), as described below.
[0179] RRC in NR 5G (see TS 38.331, Section 4) supports idle, inactive and connected states, in particular RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED. When an RRC connection has been established, the UE is in the RRC_CONNECTED state or the RRC_INACTIVE state. If this is not the case, i.e. no RRC connection is established, the UE is in the RRC_IDLE state. Figure 8 As shown, the following state transitions are possible:
[0180] From RRC_IDLE to RRC_CONNECTED, follow, for example, the "Connection Establishment" procedure;
[0181] From RRC_CONNECTED to RRC_IDLE, follow, for example, the "Connection Release" procedure;
[0182] From RRC_CONNECTED to RRC_INACTIVE, follow, for example, the “Connection Release with Pause” procedure;
[0183] From RRC_INACTIVE to RRC_CONNECTED, follow, for example, the "Connection Recovery" procedure;
[0184] From RRC_INACTIVE to RRC_IDLE (one-way), follow, for example, the "Connection Release" procedure.
[0185] For 5G 3GPP's new radio technology defines a new RRC state (RRC_INACTIVE) to provide benefits in supporting a wider range of services such as eMBB (enhanced mobile broadband), mMTC (massive machine type communication) and URLLC (ultra-reliable low latency communication) which have very different requirements in terms of signaling, power saving, latency, etc. Therefore, the new RRC inactive state should be designed to allow minimizing signaling, power consumption and resource costs in the radio access network and the core network, while still allowing, for example, data transmission to start with low latency.
[0186] According to an exemplary 5G NR implementation, the different states are characterized as follows (see Section 4.2.1 of TS 38.331):
[0187] "-RRC_IDLE:
[0188] -UE-specific DRX can be configured by upper layers;
[0189] - UE controlled mobility based on network configuration;
[0190] -UE:
[0191] - monitor short messages sent via DCI together with P-RNTI;
[0192] -Monitoring of paging channels for CN paging using 5G-S-TMSI;
[0193] -Perform neighbor cell measurements and cell (re)selection;
[0194] - Get system information and can send SI request (if configured).
[0195] - The location and time of the UE performing the logging of available measurements and the measurement configuration used for the logging.
[0196] -RRC_INACTIVE:
[0197] -UE-specific DRX can be configured by upper layers or RRC layer;
[0198] - UE controlled mobility based on network configuration;
[0199] -UE stores UE inactive context;
[0200] -RAN-based notification area is configured by the RRC layer;
[0201] -UE:
[0202] - monitor short messages sent via DCI together with P-RNTI;
[0203] - Monitor the paging channel for CN paging using 5G-S-TMSI and RAN paging using fulI-I-RNTI;
[0204] -Perform neighbor cell measurements and cell (re)selection;
[0205] -Periodically and when moving outside the configured RAN-based notification area
[0206] RAN-based notification area updates;
[0207] - Get system information and can send SI request (if configured).
[0208] - The location and time of the UE performing the logging of available measurements and the measurement configuration used for the logging.
[0209] -RRC_CONNECTED:
[0210] -UE stores the AS context;
[0211] -Transmit unicast data to / from UE;
[0212] - At lower layers, the UE may be configured with UE-specific DRX;
[0213] - For UEs supporting CA, one or more SCells aggregated with SpCell are used to increase
[0214] Increase bandwidth;
[0215] -For UEs supporting DC, use one SCG aggregated with the MCG to increase bandwidth;
[0216] - Network controlled mobility within NR and to / from E-UTRA;
[0217] -UE:
[0218] - If configured, monitor short messages sent with P-RNTI via DCI (see
[0219] Clause 6.5);
[0220] - monitoring a control channel associated with a shared data channel to determine whether data is scheduled for it;
[0222] -Provide channel quality and feedback information;
[0223] -Perform neighbor cell measurements and measurement reporting;
[0224] -Get system information;
[0225] - Perform immediate MDT measurements and position reporting where available.
[0226] According to the characteristics of the RRC Inactive state, for an inactive UE, the connection with the RAN and the core network is maintained (for both the user plane and the control plane). More specifically, in RRC Inactive, although the connection still exists, it is suspended, or in other words, the connection is no longer active. In NR, when the UE is in the RRC_Inactive state, the NG (Next Generation) signaling remains active between the gNB to the AMF. The GTP-U (GPRS Tunneling Protocol User Plane) also remains active between the gNB to the UPF. The UE context is stored at the UE and the gNB. On the other hand, in the RRC_CONNECTED state, the connection exists and is active, for example in the sense that it is used for data transmission. In the RRC_IDLE state, the UE has no RRC connection with the RAN and the core network, which also means that, for example, the radio base station does not have any context for the UE and, for example, does not know the identity of the UE and does not have security parameters related to the UE to be able to correctly decode the data sent by the UE (security, for example, ensures the integrity of the data sent). The UE context may be available in the core network, but must first be acquired by the radio base station.
[0227] A UE in RRC_IDLE or RRC_CONNECTED listens for paging messages. This paging mechanism includes logical channels and transport channels for paging. The Paging Control Channel (PCCH) is a logical downlink channel used to send paging information from the network to the device. The Paging Channel (PCH) is a transport channel used to carry paging information from the PCCH logical channel. PCH supports discontinuous reception DRX to enable the UE to save battery power by waking up at specific times to receive PCH. PCH is mapped to PDSCH in NR.
[0228] Additionally, the paging mechanism (also referred to as, for example, a notification mechanism) for user equipment in a radio cell is based on a so-called notification area (RNA for short) based on the radio access network RAN. The radio access network should know the current RNA where the user equipment is located, and the user equipment can help the gNB to track the UE moving between various RNAs. The RNA can be UE-specific.
[0229] Reference below Fig. 9 An example of an RRC recovery procedure is explained to move the UE from the RRC_Inactive state to the RRC_Connected state (see TS 38.331 Section 5.3.13). The purpose of this procedure is to resume a suspended RRC connection (which may include resuming signaling and data radio bearers).
[0230] The process allows sending an RRCResumeRequest message or a RRCResumeRequest1 message. When sending the RRCResumeRequest message, a short I-RNTI (e.g., a truncated I-RNTI) is used as the UE identity (exemplarily referred to as "resumeIdentity"). The UE checks the indication "useFullResumeID" in SIB1 and determines to send an RRCResumeRequest or RRCResumeRequest1 message. If "useFullResumeID" indicates "true", the UE will send an RRCResumeRequest1 with a complete I-RNTI; otherwise, the UE will send an RRCreSumeRequest with a short I-RNTI. The actions performed by the UE for the RRC resumption procedure (see Section 5.3.13.4 of TS 38.331) include resuming SRB2 and all DRBs (which are suspended when entering the RRC inactive state, see the release procedure below).
[0231] The RRCResume procedure can also be used to perform RNA updates when the UE moves out of the configured RNA. Fig.10 As shown, in this case, the network sends RRCRelease instead of RRCResume as a response to the RRCResumeRequest / RRCResumeRequest1 message. The UE remains in RRC_INACTIVE after receiving the RRCRelease message.
[0232] Reference below Fig.11An example of a subsequent RRC connection release procedure for transitioning a UE from an RRC_Connected state to an RRC_Inactive state is explained (see Section 5.3.8 of TS 38.331). The purpose of the procedure is to release an RRC connection or to suspend an RRC connection. For example, the network initiates an RRC connection release procedure to transition a UE in RRC_CONNECTED to RRC_IDLE or RRC_INACTIVE. The actions performed by the UE for the RRC connection release procedure (see Section 5.3.8.3 of TS 38.331) include: suspending all SRBs (signaling radio bearers) and DRBs (data radio bearers) except SRB0 in the case where the release is completed with suspension (e.g., "RRCRelease includes suspendConfig"). Accordingly, a UE in an RRC inactive state does not have any non-suspended or active DRBs (the UE only has suspended DRBs). SRB0, which remains active even in RRC inactive state, may also be used by the UE, for example for performing RACH procedures, for example when carrying RRC messages such as RRCResumeRequest, RRCResumeRequest1, RRCSetupRequest.
[0233] The term "inactive state" as used in this application should be broadly understood as a state in which regular and extensive data exchange between a UE and a base station is not possible or common. For example, when in an inactive state, a UE (e.g., referred to as an "inactive UE") may not have an actively used data connection, but still have one or more inactive data connections (e.g., which may also be referred to as existing but not currently in use) that allow (small) data transmission without first restoring a data connection. For completion, a UE in an idle state has no data connection through which the UE can send data to a base station, while a UE in a connected state has one or more active data connections that can be immediately used to carry data to the base station.
[0234] Small data transfers
[0235] The characteristics of small data transmission targeted in this disclosure refer to any service with the following characteristics: the data bursts in UL / DL are small and optionally quite infrequent, with no strict requirements on latency. For example, a single data transmission that is small enough to be sent by the UE in one transmission (e.g., in RACH or one CG opportunity, see below) can be considered a small data transmission. Typical non-limiting examples of service characteristics for small data transmission are captured in the following table (see TR 25.705v13.0.0 Section 5).
[0236] Characteristics of small data transmission
[0237]
[0238] Another different possible exemplary definition may depend on the configuration of the gNB. For example, the gNB may define that data below a certain threshold (e.g., 1000 kilobytes) may be considered small data, while data above the threshold may not be considered small data. The threshold may be defined, for example, in conjunction with the buffer status of the UE.
[0239] Alternatively, the definition of what small data is may also be fixed by an appropriate 3GPP standard, for example providing similar data amount thresholds as described above.
[0240] Data transmission by UE in RRC inactive state - SDT procedure
[0241] In more detail, 5G NR supports the RRC_INACTIVE state, and UEs with infrequent (periodic and / or aperiodic) data transmission are typically maintained in the RRC_INACTIVE state by the network. Prior to Rel-16, the RRC_INACTIVE state did not support data transmission. Small data transmission in an inactive state is considered in 3GPP TSG-RAN2Meeting#117e R2-2204216 (see Section 5.x). Therefore, the UE must restore the connection (e.g., move to the RRC_CONNECTED state) for any DL (mobile terminated) and UL (mobile originated) data. For each data transmission, a connection establishment (or recovery) must occur and then released to the RRC_INACTIVE state, but the packets are small and infrequent. This results in unnecessary power consumption and signaling overhead.
[0242] Specific examples of small and infrequent data traffic include the following use cases:
[0243] Smartphone App:
[0244] -Business from instant messaging services (WhatsApp, QQ, WeChat, etc.)
[0245] - Heartbeat / keep-alive services from IM / email clients and other applications
[0246] - Push notifications from various apps
[0247] Featured smartphone apps:
[0248] -Services from wearable devices (periodic positioning information, etc.)
[0249] - Sensors (industrial wireless sensor networks that send temperature, pressure readings periodically or in an event-triggered manner, etc.)
[0250] - Smart meters and smart meter networks that send periodic meter readings
[0251] Small data transmission can support various packet sizes and can have different business requirements.
[0252] For example, for heartbeat services / keep-alive services, the packet size is approximately 50 bytes to 100 bytes. In addition, heartbeat messages arrive every 5 minutes or on the order of seconds. For smart meters that periodically send meter readings, the packet size for periodic transmission is approximately 12 to 100 bytes. For sensors that send periodic services or event-triggered services (non-periodic services), the packet size is approximately 8 bytes to 128 bytes. Instant messaging (the service model is not deterministic) can deliver text, photos, videos, etc., and the packet size ranges from 100 bytes to 1000 bytes. For push notifications, the service model
[0253] The following will refer to Fig.12 An exemplary procedure for enabling a UE in RRC Inactive state to send (small) data after transitioning to RRC Connected state is briefly described (in this case a prior art solution compliant with 5G-NR). As is apparent from the figure, assuming that the UE is in RRC_Inactive state, this may for example involve the UE (and the gNB) having all data radio bearers suspended and no data can be sent to the gNB. In order for the UE to be able to send data, the UE must first transition to RRC Connected state, which can be accomplished by the UE requesting to resume the RRC connection (here sending RRCResumeRequest) as part of a RACH procedure (in Fig.12 This may be accomplished, for example, using a 4-step RACH process).
[0254] In detail, the UE may send a preamble to the current gNB and then receive a corresponding random access response with a (small) UL grant of radio resources, which the UE uses to send an RRCResumeRequest message of msg3 as a RACH procedure. Finally, the new gNB provides the RRCResume message to the UE, which then transitions to the RRC_CONNECTED state, including resuming all data radio bearers. In the RRC_Connected state, the UE is then able to send UL data.
[0255] After the UL small data transmission, the gNB may decide that the UE should indeed transition to the RRC_CONNECTED state. Thus, control of the aspect may rely on the gNB, although the UE may request to resume the RRC connection. One exemplary possibility is that the gNB considers a buffer status report that the UE may send, for example in Msg3 or MsgA, to decide whether the UE should transition to the RRC_CONNECTED state. The buffer status report indicates the actual amount of data in the UE buffer. For example, if the buffer status report indicates a large amount of data in the UE buffer, the gNB may decide to transition the UE from RRC_INACTIVE to RRC_CONNECTED state (e.g., by sending a RRCResume message by the gNB). On the other hand, if the buffer status report only indicates a small amount of data in the UE buffer, the gNB may decide to keep the UE in the RRC_INACTIVE state (e.g., by sending a RRCRelease message by the gNB). In addition, the absence of a buffer status report in Msg3 / MsgA may also provide an indication to the gNB, such as that no further data is available in the UE buffer and the UE may remain in RRC_INACTIVE.
[0256] from Fig.12 As can be understood from the description, the UE first needs to transition from an inactive state to a connected state so that the UE can send any user data in the uplink. The above process introduces latency and consumes significant UE power for each transmission of user data. In addition, the signaling overhead caused for inactive UEs when sending small packets is a general problem and will even be exacerbated with more UEs in 5G NR.
[0257] Therefore, 3GPP aims to enable RRC_Inactive UEs to send (small) data in the uplink without changing the UE state to RRC_CONNECTED. In general, any device with intermittent (small) packets when in the inactive state will benefit from enabling (small) data transmission in the inactive state.
[0258] against Fig.13 and Fig.14 The following assumptions made in the subsequent description of concepts, solutions and variations are to be considered as exemplary only and not limiting for RACH-based small data transmission.
[0259] In addition, when RACH-based small data uplink transmission is assumed as an example, the UE can use 2-step RACH or 4-step RACH to send small data in the uplink (see MsgA or Msg3), and the simplified and exemplary RACH-based small data uplink transmission process is shown in FIG. Fig.13 and Fig.14 In Fig.13 and Fig.14 In the example, it is assumed that the UE is already in the RRC_INACTIVE state and has small data available for transmission. Fig.13 A 4-step RACH procedure is assumed and it is shown how the UE sends small data using Msg3. Fig.14 A 2-step RACH procedure is assumed and it is shown how a UE sends small data using MsgA.
[0260] According to an example, the control message and the small data are sent together to the base station, e.g., together in the same transport block, where the UE builds the transport block using resources and multiplexes the data and signaling together in the same transport block at the MAC layer. For the 4-step RACH case, the small data is sent in Msg3, e.g., based on the radio resources granted by the uplink grant received from the gNB in Msg2. For the 2-step RACH case, the small data is sent in MsgA, e.g., using the radio resources selected by the UE from some previously configured radio resources, e.g., in conjunction with the selected RACH preamble.
[0261] also, Fig.13 and Fig.14 It is shown that the buffer status report can be included in Msg3 and MsgA respectively, although the BSR is shown only in brackets to reflect that including the BSR is only an exemplary possibility. Fig.13 In the example, it is assumed that the gNB decides to keep the UE in the RRC_Inactive state, for example because the BSR does not exist or only indicates a small amount of uplink data in the UE buffer. Accordingly, an RRCRelease message is sent for Msg4. On the other hand, in Fig.14 In the example, it is assumed that the gNB decides to transition the UE to the RRC_Connected state, for example because the BSR indicates a large amount of uplink data in the UE buffer that must be sent by the UE. Accordingly, an RRCResume message is sent for MsgA.
[0262] In addition, despite the Fig.13 In the example, the uplink grant is shown separately from the random access response of Msg2, but in Fig.13 In the embodiment and similar embodiments below, the uplink grant may also be considered to belong to and be part of the random access response.
[0263] In summary, possible exemplary implementations of small data uplink transmission for RRC_INACTIVE UEs are possible and may be based on, for example, a RACH procedure, whether a 2-step or 4-step RACH procedure (see Fig.13 and Fig.14 ).
[0264] In the above, a single small data uplink transmission (e.g., Msg3 / MsgA using RACH) was discussed. In addition, 3GPP agrees that a UE in the RRC_INACTIVE state should be able to send (and possibly receive) multiple UL (and accordingly DL) transmissions using the same procedure without transitioning to the RRC_CONNECTED state.
[0265] For example, the network node may inform the UE of a downlink SDT (DL-SDT) (i.e., mobile terminated SDT (MT-SDT)) if one or more of the following conditions are met:
[0266] All pending data at a network node (in DL) is mapped to a radio bearer (RB) configured for SDT.
[0267] The amount of DL data to be processed across all RBs configured for SDT is less than or equal to the data amount threshold of the network node,
[0268] The reference signal received power (RSRP) of the DL is less than the RSRP threshold of the SDT process,
[0269] The UE supports SDT.
[0270] Therefore, the term SDT process or a process for sending SDT DRB data refers to a process for sending data in an inactive state (e.g., RRC_INACTIVE), and does not necessarily refer to the amount of data sent by the SDT process. Therefore, the terms small data and SDT DRB data refer to data that can be sent in an inactive state (of the UE), and not necessarily the size of the data. In particular, small data or SDT DRB data can be any data of a DRB configured for transmission in an inactive state (such a DRB is also referred to herein as an SDT DRB). Similarly, the term non-SDT DRB data refers to data that cannot be sent in an inactive state (of the UE) and / or data that can only be sent in a connected state (of the UE). Specifically, non-SDT DRB data can be any data of a DRB that is not configured for transmission in an inactive state (such a DRB is also referred to herein as a non-SDT DRB).
[0271] The process for sending SDT DRB data may be a process based on a RACH process and / or initiated in a RACH process. Specifically, the RACH process may be a 4-step RACH or a 2-step RACH process. More specifically, the SDT process based on the RACH process here refers to an SDT process initiated in a RACH process. This includes an SDT process in which only a single transmission of small data is performed. For example, in Fig.13 and Fig.14During the RACH procedure shown, as well as SDT procedures in which more than one transmission of small data is performed during and / or after the RACH procedure. In addition, this also includes SDT procedures that do not terminate with the RACH procedure in which they were initiated.
[0272] In summary, the SDT process based on the RACH process or initiated in the RACH process can therefore be a process of performing one or more transmissions of data in an inactive state, and i) at least one of the one or more transmissions is performed by the UE together with a message of the RACH process, and / or ii) an indication is sent by the UE together with a message of the RACH process, the indication indicating a request for resource authorization for small data transmission.
[0273] However, the term SDT procedure is not limited to the RACH-based SDT procedure, as it also includes data transmission in an inactive state using a Configuration Grant (CG).
[0274] It is possible to allow multiple devices (UEs) to share periodic radio resources, called Configuration Grant (CG) (this helps to reduce the waste of periodic radio resources compared to LTE SPS). On the other hand, there is also the possibility for the gNB to define periodic radio resources in a way that they are not shared or fully shared between multiple UEs. The gNB allocates the radio resources of the Configuration Grant to one or more UEs, which then utilize these periodic radio resources randomly when they have to send data (e.g. small data, see later chapters). With the CG, the network eliminates the packet transmission delays caused by the specific scheduling request procedure that would otherwise have to be performed before the data can be sent. Thereby, the utilization of the allocated periodic radio resources can also be increased.
[0275] 3GPP Release 16 supports two types of authorization-free configuration schemes, namely Type 1 and Type 2 (see 3GPP 38.300 v16.6.0: "NR; NR and NG-RAN Overall Description; Stage 2 (Release 16)", Section 10.3).
[0276] According to the exemplary embodiment of TS 38.300, using Type 1 CG, the RRC directly provides the configured uplink grant to the UE, for example including its periodicity.
[0277] With type 2 configured grants, RRC defines the periodicity of the configured uplink grant, and a PDCCH message addressed to the UE's CS-RNTI can signal and activate the configured uplink grant, or deactivate it; a PDCCH indication addressed to the CS-RNTI can implicitly reuse the uplink grant according to the periodicity defined by RRC until deactivated. In other words, additional L1 signaling (e.g., PDCCH) is introduced, where the uplink is semi-persistently scheduled by an RRC-based uplink grant, which is activated / deactivated by an activation (deactivation) DCI. RRC provides higher-layer parameters for CG configuration.
[0278] In both cases, according to an exemplary 3GPP implementation, the RRC provides the grant configuration to the UE via a higher layer parameter called ConfiguredGrantConfigure (see TS 38.331 v16.5.0, section 6.3.2 "Radio Resource Control Information Elements").
[0279] The resource configuration for the CG may include, for example, physical resources and / or reference signal (RS) parameters in the time domain and / or frequency domain. The configuration parameters may also include a modulation and coding scheme (MCS) and / or a number of repetitions and / or a cycle period and / or a transport block size.
[0280] More specifically, the UE can initiate a CG-based SDT process by sending a corresponding indication to the scheduling device using the configured CG resources. The UE can start the transmission of SDT DRB data together with the indicated transmission, or start the transmission of SDT DRB data together with a later transmission, and the later transmission can also use the CG resources. For example, when the SDT DRB data arrives, the UE can multiplex the SDT DRB data with the RRCResumeRequest message and send them in the nearest CG resources. CG resources are those UL grants that appear periodically and are configured to the UE before / after the UE enters an inactive state by the scheduling device.
[0281] Data connectivity
[0282] The term "data connection" as used herein may be understood as a connection over which data (e.g., small data) may be transmitted, e.g., between a UE and a radio base station. In more detail, a UE without a data connection, e.g., even if connected to a radio base station based on a signaling connection, cannot immediately send data. Data in this context may be broadly understood as, e.g., user data from an application running on the UE, as opposed to, e.g., control information to be transmitted using a signaling connection.
[0283] In an exemplary embodiment, according to the 5G NR standard, the data connection may be understood as a data radio bearer DRB and the signaling connection may be understood as a signaling radio bearer SRB.
[0284] In some cases, the present application also distinguishes different conditions of data connections, such as non-existent, existing but suspended, existing but not used (also referred to as non-suspended or inactive), existing and currently used to transmit data (also referred to as active). Following this classification of data connections, a suspended data connection, although existing, cannot be used immediately to send data (e.g., in the uplink) because it is suspended by both endpoints (e.g., UE and radio base station) and needs to be resumed first. On the other hand, a non-suspended data connection can allow immediate data transmission (e.g., without any further processes, such as resuming the data connection). For example, when referring to the exemplary 5G NR implementation currently defined in the 3GPP standard, a UE in the RRC_INACTIVE state will have one or more suspended data connections (DRBs are suspended); a UE in the RRC_CONNECTED state may have one or more active data connections and possibly other non-suspended data connections (currently inactively used); and a UE in the RRC_IDLE state will have no data connection (neither suspended nor active). On the other hand, according to the improved data transfer procedure explained below, unlike the 5G NR implementation currently defined in the 3GPP standards, a UE in the RRC Inactive state will have one or more available non-suspended data connections (these will be inactive because no data is exchanged before the small data transfer).
[0285] In the context, the application explains that, for example, UE uses a data connection to send and / or receive small data. In this scenario, a data connection is established between UE and a base station. In an exemplary embodiment, a data connection should be broadly understood to be associated with certain parameters, which relate to coding, security, encryption, etc. Therefore, from the perspective of the transmitting side, UE applies these parameters associated with the data connection to the (small) data to be sent using the data connection. This can be done, for example, to ensure a specific quality of service. Accordingly, from the perspective of the receiving side, the receiver may need to apply processing opposite to the transmitting side (e.g., related to coding, security, encryption, etc.) in order to successfully decode the data sent via the data connection.
[0286] the term
[0287] In the following, UE, base station and process will be described for the new radio access technology envisioned for 5G mobile communication system, but it can also be used in LTE mobile communication system. Different implementations and variants will also be explained. The following disclosure is facilitated by the discussion and discovery as described above, and may be based on at least a portion thereof, for example.
[0288] Generally, it should be noted that many assumptions have been made herein so that the basic principles of the present disclosure can be explained in a clear and understandable manner. However, these assumptions should be understood as examples made herein for illustrative purposes only and should not limit the scope of the present disclosure.
[0289] In addition, some of the terms for processes, entities, layers, etc. used below are closely related to the terms used in LTE / LTE-A systems or the current 3GPP 5G standardization, even though the specific terms used in the context of new radio access technologies for the next 3GPP 5G communication system have not yet been fully determined or may eventually change. Therefore, the terms may be changed in the future without affecting the functionality of the embodiments. Therefore, the technicians realize that the embodiments and their scope of protection should not be limited to the specific terms used exemplarily herein due to the lack of updated or finally agreed terms, but should be understood more broadly in terms of the functions and concepts that form the basis of the functions and principles of the present disclosure.
[0290] Implementation
[0291] Generally, as already indicated above, it may be desirable for a UE in an inactive state to use a procedure to receive multiple DL transmissions without transitioning to a connected state.
[0292] In view of this, the present disclosure provides a technique to facilitate efficient initialization of DL transmission of small data. Specifically, the disclosed process enables the use of paging messages and / or indications for small data to notify the UE of a mobile terminated (i.e., downlink) small data transmission (MT-SDT). Enabling MT-SDT in an inactive state can save UE power and reduce signaling overhead.
[0293] The present disclosure provides a network node and user equipment and corresponding methods and programs. For example, an integrated circuit can control the process of a UE or a base station. Fig.16 As shown, a user equipment 1710 and a network node 1760 can communicate with each other through a wireless channel 1750 in a wireless communication system. For example, the user equipment can be an NR user equipment, and the network node can be a base station or a scheduling node, such as an eNB or an NRgNB, in particular a gNB in a non-terrestrial network (NTN) NR system. An example of such a communication system is Fig.16The communication system 1700 may be a wireless communication system according to the technical specifications of 5G, in particular, a NR communication system. However, the present disclosure is not limited to 3GPP NR and may also be applied to other wireless or cellular systems, such as NTN. Fig.16 A general, simplified and exemplary block diagram of a user device 1710 (also referred to as a communication device) and a network node 1760 is shown. However, in general, in the case of a side link connection between two terminals, the scheduling device may also be a terminal. In addition, particularly with regard to URLLC use cases; the user device 1710 may also be a sensor device, a wearable device or a connected vehicle, or a controller of an automated machine in an industrial plant. In addition, the user device 1710 may be capable of serving as a relay between the network node 1760 and another communication device (e.g., the present disclosure is not limited to a communication "terminal" or a user "terminal").
[0294] The UE and the eNB / gNB communicate with each other via a (wireless) physical channel 1750 using their transceivers 1720 (UE side) and 1770 (network node side), respectively. The network node 1760 and the terminal 1710 together form a communication system 1700. The communication system 1700 may also include other entities such as Figure 1 Those entities shown in .
[0295] like Fig.16 As shown in (left hand side), according to a first exemplary embodiment, a user equipment (UE) 1710 is provided. The UE 1710 includes a transceiver 1720 and a circuit 1730. In operation, the circuit 1730 receives a paging message when the UE is in an inactive state. In response to the paging message, the circuit remains in the inactive state to receive small data. When the UE remains in the inactive state, a response to the paging message is sent to the network node within a transmission opportunity associated with a pre-configured resource. Fig.15 Such paging while remaining in inactive mode is exemplarily shown in FIG.
[0296] Typically, the circuit 1730 may control the transceiver 1720 to receive and / or send data. This is illustrated by arrow 1725, which schematically represents an interface between the circuit 1730 and the transceiver 1720, through which control is performed. For example, the circuit 1730 may instruct 1725 the transceiver 1720 to send the response to the paging message. Similarly, the circuit 1730 may control the transceiver 1720 to receive a paging message, and receive the paging message from the transceiver through the interface 1725.
[0297] Fig.17An exemplary functional structure of circuit 1730 is shown, in particular, circuit 1735 for processing small data. As shown, SDT processing circuit 1735 may include paging message detection circuit 1736 and response sending circuit 1737. More specifically, circuit 1736 detects paging messages, for example, by monitoring pre-configured paging resources. Circuit 1736 may also determine whether the arrival of small data is expected. Response sending circuit 1737 may determine whether to respond to the received paging message.
[0298] Corresponding to the above-mentioned UE, according to a first exemplary embodiment, a communication method performed by a UE in an inactive state is provided. Fig.19 As shown, the method comprises the following steps:
[0299] receiving (S1910) a paging message;
[0300] In response to the paging message, maintaining (S1920) an inactive state to receive the small data; and
[0301] While remaining in the inactive state, a response to the paging message is sent (S1930) to the network node within a transmission opportunity associated with the preconfigured resources.
[0302] Also like Fig.16 As shown in FIG. 1 (right-hand side), according to a first exemplary embodiment, a network node 1760 is provided. The network node 1760 includes a transceiver 1770 and a circuit 1780. In operation, the circuit 1780 sends a paging message to a UE in an inactive state and receives a response from the UE in an inactive state, the response indicating that the UE is ready to receive small data in an inactive state.
[0303] Typically, the circuit 1780 may control the transceiver 1770 to receive and / or transmit data. This is illustrated by arrow 1775, which schematically represents an interface between the circuit 1780 and the transceiver 1770, through which control is performed. For example, the circuit 1780 may instruct 1775 the transceiver 1770 to transmit the paging message. Similarly, the circuit 1780 may control the transceiver 1770 to receive a response to the paging message, and receive the response from the transceiver through the interface 1775.
[0304] Fig.18 1830 shows an exemplary functional structure of the SDT processing circuit 1785. Specifically, the SDT processing circuit 1785 may include a paging message transmission circuit 1836 and a UE response detection circuit 1837. The circuit 1836 may be responsible for sending a paging message and / or an indication for SDT. In addition, the circuit 1837 may be responsible for receiving a response from a UE in an inactive state.
[0305] In addition, corresponding to the above-mentioned base station, a communication method performed by a network node is provided. Fig. 20 As shown, the method comprises the following steps:
[0306] sending (S2010) a paging message to a UE in an inactive state; and
[0307] A response is received (S2020) from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
[0308] The UL response may serve as feedback to the network node that the UE has initiated SDT. Initiating SDT may include, for example, starting a timer (e.g., the SDT timer is started and running). Thus, the UE, for example, expects DL-SDT data (e.g., including monitoring a control channel associated with a downlink shared data channel).
[0309] UE 1710 may include a transceiver 1720 and a (processing) circuit 1730, and network node 1760 may include a transceiver 1770 and a (processing) circuit 1780. Transceiver 1710 may in turn include and / or function as a receiver and / or transmitter. In the present disclosure, in other words, the term "transceiver" is used for hardware and software components that allow communication device 1710 or base station 1760 to send and / or receive radio signals through wireless channel 1750, respectively. Therefore, a transceiver corresponds to a receiver, a transmitter, or a combination of a receiver and a transmitter. Generally, it is assumed that base stations and communication devices are capable of sending and receiving radio signals. However, in particular with respect to some applications of eMBB, mMTC, and URLLC (smart home, smart city, industrial automation, etc.), it is conceivable that a device (such as a sensor) only sends a signal. In addition, the term "circuit" includes a processing circuit formed by one or more processors or processing units, etc. Circuits 1730 and 1780 (or processing circuits) may be one or more hardware, such as one or more processors or any LSI. There are input / output points (or nodes) between the transceiver and the processing circuit, through which the processing circuit can control the transceiver when in operation, ie control the receiver and / or transmitter and exchange receive / transmit data.
[0310] As a transceiver and transmitter, a receiver may include an RF (radio frequency) front end, which includes one or more antennas, amplifiers, RF modulators / demodulators, etc. The processing circuit may perform control tasks, such as controlling the transceiver to send user data and control data provided by the processing circuit and / or receiving user data and control data further processed by the processing circuit. The processing circuit may also be responsible for performing other processing, such as determining, deciding, calculating, measuring, etc. The transmitter may be responsible for performing the transmission process and other processes related thereto. The receiver may be responsible for performing the reception process and other processes related thereto, such as monitoring the channel.
[0311] It is further noted that any steps / operations / methods described below may be performed or controlled by circuit 1730 (on the UE side) and / or circuit 1780 (on the network node side).
[0312] In further description, unless explicitly stated or context indicates otherwise, the details and embodiments apply to each of the user equipment, network node and method. In addition, it is noted that any steps described below can be included as code instructions in a program, which can be executed by one or more processors (e.g., circuit 1730 and / or circuit 1780).
[0313] MT-SDT Paging
[0314] At some point in time when UE 1710 is in an inactive state, it is assumed that small data becomes available for transmission from network node 1760 to UE 1710.
[0315] When small data for downlink transmission arrives, the UE 1710 in the inactive state receives S1910 a paging message from the network node 1760. For example, paging can be performed via CN paging or RAN paging: for example, the UE uses 5G-S-TMSI to monitor a paging channel for CN paging, or uses a full I-RNTI to monitor a paging channel for RAN paging. More details can be found in the RRC state section.
[0316] In the 5G NR standard, the inactive state corresponds to, for example, the RRC_INACTIVE state. The paging message may be a paging message defined by current and / or future standards. For example, the paging message may be interpreted by a UE that does not have SDT capability as an indication of resuming to a connected state (e.g., RRC_CONNECTED state).
[0317] In response to receiving such a paging message, according to the present disclosure, a UE 1710 with SDT capability maintains S1920 in an inactive state to receive small data. Specifically, a UE 1710 with SDT capability may determine to remain in an inactive state according to the definition of the standard, the (default) configuration of the UE, etc. For example, the standard may specify that the UE always remains in an inactive state upon receiving a paging message. Accordingly, the UE determines to remain in an inactive state. In another example, the standard may implement the configurability of UE behavior upon receiving a paging message. This configurability may include, for example, a default configuration, such as remaining in an inactive state. The UE may determine its configuration based on a paging message (e.g., whether it arrives via PDCCH or PDSCH), or may receive a configuration from a network node, etc.
[0318] In other words, upon receiving such a paging message, the UE 1710 in the inactive state detects the possibility of small data arrival. The UE 1710 with SDT capability interprets such a (standard) paging message as an indication of the possibility of receiving a small data transmission; the UE 1710 with SDT capability according to the present disclosure may not interpret the paging as an indication to restore to the connected state.
[0319] The term "arrival" here refers to arrival from a higher layer. Therefore, in other words, the small data becomes available for transmission. In addition, the term "detected" includes detecting the actual arrival of data as well as detecting / determining the expected small data arrival for transmission.
[0320] UE 1710, while remaining in the inactive state, responds to the paging message by sending S1930 a response to the network node 1760. The response is sent within a transmission opportunity associated with pre-configured resources. Pre-configured resources include, for example, resources used for transmission of a RACH process and resources allocated to the UE via a configuration grant (CG) process. The transmission opportunity comes from the definition and implementation of the process. The RACH process and the CG process are explained in detail above in the data transmission section of the UE in the RRC inactive state. However, the present disclosure is not limited to the RACH process or the CG process, and any current or future process for sending an UL response in an inactive state may be used.
[0321] Thus, the response to the paging message may include at least one of a random access small data transmission (RA-SDT), a configuration grant small data transmission (CG-SDT), or a mobile terminated small data transmission (MT-SDT). The decision on whether to use RA-SDT or CG-SDT for the UL response may be performed according to UL-SDT, which is explained in the data transmission section performed by the UE in the RRC inactive state. MT-SDT provides an example of a contemplated process for future 3GPP 5G NR releases. MT-SDT may cover not only UL transmissions (as in the current RA-SDT and CG-SDT), but may also include DL transmissions for UEs in an inactive state. MT-SDT may include elements of RA-SDT and / or CG-SDT or a hybrid combination of both RA-SDT and CG-SDT. MT-SDT may be a new type of UL and / or DL transmission designed specifically for UEs operating in an inactive state.
[0322] In response to the paging message, UE 1710 may receive small data from network node 1760 while remaining in an inactive state. For example, the small data may be a message carrying a payload. A specific example of small data carrying a payload is given above in the subsection Small Data Transmission. For example, the small data may include an indication that UE 1710 is to transition to a connected state. In other words, the network node may send a resume message (e.g., RRC_RESUME) to an SDT-capable UE using the MT-SDT procedure.
[0323] In other words, in the case where the incoming DL data is normal (non-SDT) data, the network node (eNB / gNB) can respond with RRCResume upon receiving an UL response from the UE to instruct the SDT-capable UE 1710 to transition to RRC_CONNECTED mode.
[0324] As described above, the remaining portion in the inactive state is determined according to the UE configuration. Such a configuration may be a pre-stored configuration that may be received from a network node, or may be a default configuration of the UE, etc.
[0325] UE Configuration
[0326] The (default) UE configuration of UE 1710 includes settings for default behavior when a paging message is received. This "UE configuration" describes the current configuration of the UE. The UE configuration can be, for example, a default initial configuration, which is set according to a standard and / or by the network or by the UE itself according to UE capabilities. The UE configuration can be, for example, configured (adopted) or reconfigured based on a configuration received (e.g., via RRC). An exemplary implementation of setting and / or receiving and / or sending the UE configuration (information) is explained below. The exemplary embodiments can be performed individually and in combination.
[0327] 1. Based on UE capabilities
[0328] The above UE configuration enables the initialization of SDT by default during paging. For example, such a UE configuration is set for UE 1710 according to the capabilities of UE 1710. In this case, UE 1710 determines its capabilities and sets its configuration according to the capabilities. UE 1710 indicates its capabilities to network node 1760 when in a connected state. For example, such UE capabilities may include attributes and / or requirements of the UE. For example, UE SDT capabilities may be defined based on SDT types. Such SDT types may include, for example, RA-SDT, CG-SDT, or new SDT types for DL (e.g., MT-SDT). For example, an inactive UE may initiate SDT by default during paging according to a UE category that supports SDT and / or is configured with SDT. Such a UE category may define the combined uplink and downlink capabilities of a UE specified by current or future standards.
[0329] For example, the UE reports its capabilities via a UECapabilityInformation message.UECapabilityInformation is an RRC message sent by the UE 1710 to the network node 1760 (eg, during an initial registration procedure or upon request from the network node). The UECapabilityInformation message includes detailed information about the capabilities of the UE.
[0330] For example, the network node 1760 may request capability information including sending a UECapabilityEnquiry message to the UE 1710. The UECapabilityEnquiry is an RRC message sent by the network node 1760 to request detailed information about the capabilities of the UE. The UE 1710 receives the query and reports its capabilities via a UECapabilityInformation message.
[0331] In other words, the UE 1710 with SDT capability is configured to remain in an inactive state upon receiving a paging message and respond to the network node as described above. The UE with SDT capability informs the network of its configuration when in a connected state. The network node may request information about the UE capability and receive the information from the UE in a connected state.
[0332] 2. Based on the semi-static information received by the UE
[0333] The network node 1760 may send a configuration for MT-SDT to the UE 1710 in the connected state. Such a sent configuration may, for example, include settings according to a standard, according to a configuration of the network node, according to a configuration of the network, etc. or a combination thereof. The UE 1710 may, for example, receive the configuration before transitioning from the connected state to the inactive state. The UE 1710 configures (adopts) the UE configuration accordingly. The configuration may be received from the network node 1760. In general, the configuration may be received from the network node at any time, for example, during a period when the UE 1710 is in the connected state.
[0334] However, the present disclosure is not limited thereto, and it is contemplated that the UE may receive such a configuration even in an inactive mode, for example, at some time within a small data.
[0335] In the context of NR in particular, the network node may send the configuration semi-statically. The term "semi-static" in NR refers to higher layer signaling, and in particular to RRC. This signaling is not dynamic, as shared channel control signaling is used to indicate resource allocations (e.g., via PDCCH). However, it may still be received after a connection is established or generally during a connection (e.g., in connected mode).
[0336] For example, when the UE 1710 is instructed to transition to RRC_INACTIVE, the network node 1760 provides semi-static information related to the (default) UE configuration to the UE 1710. When the UE 1710 in RRC_CONNECTED receives an RRCRelease with Suspend message to enter RRC_INACTIVE, the semi-static information (e.g., information element SDT-Config) is included in the same message.
[0337] The default configuration regarding the UE default behavior / state for triggering MT-SDT upon paging (e.g., the "sdt-Paging" field) may be included together in the SDT-Config (an example is shown below). The SDT-Config may be included in the SuspendConfig field carried in the RRC Release (with Suspend).
[0338] Such a SuspendConfig is also shown below.
[0339]
[0340] An exemplary SDT-Config includes a field called sdt-Paging. In the case where SDT-Paging is set to "true", a UE receiving the configuration is thereby instructed to adopt the configuration to initiate SDT upon paging. An exemplary SuspendConfig includes a field sdt-Config, which may be set to include the value sdt-Config:
[0341] The ASN.1 signaling field examples shown are not limited to enumeration types, but may also include other types, such as Boolean type, etc.
[0342] After transitioning to RRC_INACTIVE, UE 1710 is configured to initiate SDT upon paging and send a response as described above.
[0343] 3. According to UE's preference
[0344] Alternatively or additionally, UE 1710 may inform network node 1760 of the preferred UE configuration. Thus, UE 1710 sends information about the preferred UE configuration to network node 1760 when in a connected state. For example, UE 1710 may include an indication in a UEAssistanceInformation message. An example of such a message is given below.
[0345]
[0346] This exemplary SDTPreference includes a preferred state (eg, connected or inactive) for receiving small data.
[0347] Such a message indicates the preference of UE 1710 whether to initiate SDT or non-SDT when paging. Such a preference may be indicated by a standard, UE capability, type of UE, etc.
[0348] In response to receiving the message, the network node 1760 may notify the UE 1710 of the decision regarding the default state (initiating SDT or non-SDT upon paging) before the UE 1710 transitions to the inactive state. Such notification may be performed as explained in detail above for the configuration according to the semi-static information received by the UE. The decision of the network node may include a determination according to a standard, according to a configuration of the network node, according to a configuration of the network, etc., or a combination thereof.
[0349] UE 1710 may send information about its SDT preference when the paging network is initiated (eg, via an RRCReconfiguration procedure) or when the UE is initiated (eg, if the UE is configured to provide SDT preference in response to paging).
[0350] 4. According to the configuration of radio bearer
[0351] The UE configuration may be configured or reconfigured based on the configuration of the radio bearers. For example, in the case where all DRBs in a plurality of data radio bearers and / or at least one SRB in a plurality of signaling radio bearers (SRBs) are configured for SDT, the UE configuration may include that the default behavior of the UE is to initiate SDT upon paging.
[0352] The plurality of SRBs may include SRB0, SRB1, and SRB2. For example, one or more of SRB1 and SRB2 may be configured for SDT purposes. Then, the UE 1710 may be configured or reconfigured to initiate SDT upon paging.
[0353] The configuration of the UE in the inactive state may include the configuration of multiple DRBs (including one or more DRBs). If all DRBs in the multiple DRBs are configured for SDT, the UE 1710 may be configured or reconfigured to initiate SDT by default upon paging.
[0354] 5. Change instructions according to SI
[0355] UE 1710 may receive (along with all UEs in the same cell) a system information (SI) change indication. UEs in an inactive state may receive the SI change indication via paging, for example, using a short message sent with the P-RNTI via DCI.
[0356] UE 1710 performs an SI acquisition procedure and updates its SDT configuration based on what is received in a system information block (SIB). This SI acquisition procedure may be initiated by a network node or a UE. For example, the SI may be periodically broadcast by a network node to all UEs in a cell. For example, a UE may request SI transmission.
[0357] For example, the SDT default configuration may be included in SIB1 as shown below.
[0358]
[0359] An exemplary SDT-ConfigCommonSIB includes a field called sdt-Paging. In case SDT-Paging is set to "true", a UE receiving the configuration is thereby instructed to adopt the configuration to initiate SDT upon paging.
[0360] This configuration is a common configuration for all UEs in the cell.
[0361] Based on the received SI change indication, UE 1710 configures or reconfigures the UE configuration.
[0362] Therefore, the UE 1710 initiates SDT upon paging by default and sends a UL response to the network node 1760 as described above.
[0363] MT-SDT indication in paging message or short message
[0364] In a second exemplary embodiment for implementing paging for downlink small data transmission, an indication is sent to the UE. Thus, the UE receives an indication for receiving small data from the network node.
[0365] Fig.16 The exemplary UE shown (left hand side) and described in detail above may be configured to perform MT-SDT according to the second exemplary embodiment.
[0366] Fig.16 The UE 1710 in the embodiment includes a transceiver 1720 and a circuit 1730. The circuit 1730 receives an indication of receiving small data from a network node in operation. In response to receiving the indication, the UE 1710 remains in an inactive state to receive the small data. While remaining in the inactive state, the UE sends a response to the indication to the network node.
[0367] Typically, the circuit 1730 may control the transceiver 1720 to receive and / or transmit data. This is illustrated by arrow 1725, which schematically represents an interface between the circuit 1730 and the transceiver 1720, through which the control is performed. For example, the circuit 1730 may instruct 1725 the transceiver 1720 to transmit said response to an indication for SDT. Similarly, the circuit 1730 may control the transceiver 1720 to receive a paging message, and receive said indication from the transceiver through said interface 1725.
[0368] Corresponding to the above-mentioned UE, according to a second exemplary embodiment, a communication method performed by a UE in an inactive state is provided. Fig.21 As shown, the method comprises the following steps:
[0369] Receiving (S2110) an indication of receiving small data from a network node;
[0370] In response to the paging message, maintaining (S2120) in an inactive state to receive small data; and
[0371] While remaining in the inactive state, a response to the paging message is sent (S2130) to the network node.
[0372] Such a method for performing MT-SDT according to the second exemplary embodiment may be implemented in the UE alone, or may be implemented in addition to the method according to the first exemplary embodiment.
[0373] Also like Fig.16 As exemplarily shown in (right hand side), a network node 1760 according to a second exemplary embodiment is provided. The network node 1760 includes a transceiver 1770 and a circuit 1780. The circuit 1780 sends an indication of receiving small data to a UE in an inactive state in operation. The network node receives a response from the UE in an inactive state, the response indicating that the UE is ready to receive small data in an inactive state.
[0374] Typically, the circuit 1780 may control the transceiver 1770 to receive and / or transmit data. This is illustrated by arrow 1775, which schematically represents an interface between the circuit 1780 and the transceiver 1770, through which control is performed. For example, the circuit 1780 may instruct 1775 the transceiver 1770 to transmit the indication. Similarly, the circuit 1780 may control the transceiver 1770 to receive a response to the indication, and receive the response from the transceiver through the interface 1775.
[0375] Furthermore, corresponding to the above-mentioned base station, a communication method performed by a network node according to a second exemplary embodiment is provided. Fig. 22 As shown, the method comprises the following steps:
[0376] Sending (S2210) an indication of receiving small data to the UE in an inactive state; and
[0377] A response is received (S2220) from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
[0378] As described above, UE 1710 responds to the indication by sending S1930 a response to network node 1760 while remaining in the inactive state. The response is sent within a transmission opportunity associated with pre-configured resources. Pre-configured resources include, for example, resources used for transmission of a RACH process and resources allocated to the UE via a configuration grant (CG) process. The transmission opportunity comes from the definition and implementation of the process. The RACH process and the CG process are explained in detail above in the data transmission section of the UE in the RRC inactive state. However, the present disclosure is not limited to the RACH process or the CG process, and any current or future process for sending an UL response in the inactive state may be used.
[0379] The steps performed by the UE according to the second exemplary embodiment (including responding to the network node and receiving small data) can be performed similarly to the first exemplary embodiment. In addition, the steps performed by the network node according to the second exemplary embodiment (including receiving a response from the UE and sending small data) can also be performed similarly to the first exemplary embodiment.
[0380] Thus, the response to the paging message may include at least one of a random access small data transfer (RA-SDT), a configuration grant small data transfer (CG-SDT), or a mobile terminated small data transfer (MT-SDT).
[0381] In response to the paging message, UE 1710 may receive small data from network node 1760 while remaining in an inactive state. For example, the small data may be a message carrying a payload. A specific example of small data carrying a payload is given above in the section Small Data Transmission.
[0382] The received indication is interpreted by the UE to identify the incoming DL traffic as a small data transmission and the UE does not need to transition to the connected state.
[0383] The indication for receiving small data may be included in, for example, a paging message or a short message. However, the present disclosure is not limited to these examples; the indication for receiving small data may be included in any current or future message received by the UE in the inactive state.
[0384] The indication for SDT may be carried, for example, in a paging message (in the PCCH logical channel), for example, in a PagingRecord. An example is provided below.
[0385]
[0386] The exemplary PagingRecord includes a signaling field "SDT" which is set to "true" if a small data transfer is indicated. The signaling field examples shown are not limited to enumeration types, but may also include other types, such as Boolean, etc.
[0387] As described above, a short message may also be used to indicate MT-SDT. A short message is sent on the PDCCH using a P-RNTI with or without an associated paging message (e.g., DCI format 1_0). According to 3GPP TS 38.331, the short message field has a length of 8 bits, of which bits 4-8 are currently not used. For example, bit 4 may be used to indicate MT-SDT as shown below.
[0388]
[0389] Bit 4 in this example indicates sdtPaging, specifically, the bit set to 1 provides the UE with an indication to initiate SDT.
[0390] However, the present disclosure is not limited to such exemplary short messages. For example, different RNTIs and / or different DCI formats may be used for the indication of MT-SDT. Such different RNTIs may be existing RNTIs or new RNTIs, such as sdt-RNTIs.
[0391] Fig.23 Steps of an exemplary embodiment according to a second exemplary embodiment are provided. A UE in an RRC_INACTIVE state monitors S2310 a paging occasion and receives a paging message. The UE determines S2320 whether the paging message includes an SDT indication. If the paging message includes the indication ("Yes" in S2320), the UE initiates S2330 an SDT and sends a response to the network node. If the paging message does not include the indication ("No" in S2320), the UE initiates S2340 a recovery procedure and transitions to a connected state.
[0392] Hardware and software implementations of the present disclosure
[0393] The present disclosure can be implemented by software, hardware or software in collaboration with hardware. Each functional block used in the description of each of the above embodiments can be partially or completely implemented by an LSI such as an integrated circuit, and each process described in each embodiment can be partially or completely controlled by the same LSI or a combination of LSIs. LSI can be formed as a chip alone, or a chip can be formed to include some or all of the functional blocks. LSI may include data input and output coupled thereto. According to the difference in integration, the LSI here may be referred to as IC, system LSI, super LSI or ultra LSI. However, the technology for implementing integrated circuits is not limited to LSI, and can be implemented by using a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after manufacturing LSI or a reconfigurable processor that can reconfigure the connection and setting of the circuit unit inside the LSI can be used. The present disclosure can be implemented as digital processing or analog processing. If future integrated circuit technology replaces LSI due to the advancement of semiconductor technology or other derivative technologies, future integrated circuit technology can be used to integrate functional blocks. Biotechnology can also be applied.
[0394] The present disclosure may be implemented by any kind of device, apparatus, or system having a communication function, which is referred to as a communication device.
[0395] The communication device may include a transceiver and a processing / control circuit. The transceiver may include and / or function as a receiver and a transmitter. As a transceiver and a transmitter, the receiver may include an RF (radio frequency) module including an amplifier, an RF modulator / demodulator, etc., and one or more antennas.
[0396] Some non-limiting examples of such communication devices include phones (e.g., cellular (cell) phones, smart phones), tablets, personal computers (PCs) (e.g., laptops, desktop computers, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (remote health and medicine) devices, and vehicles providing communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.
[0397] Communication devices are not limited to portable or transportable, and may also include any kind of device, equipment, or system that is non-portable or fixed, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in an "Internet of Things (IoT)" network.
[0398] Communications may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.
[0399] The communication apparatus may include a device such as a controller or a sensor coupled to a communication device that performs the communication functions described in the present disclosure. For example, the communication apparatus may include a controller or a sensor that generates a control signal or a data signal used by the communication device that performs the communication functions of the communication apparatus.
[0400] The communication apparatus may also include infrastructure facilities such as base stations, access points, and any other apparatus, device, or system that communicates with or controls apparatuses such as those in the above non-limiting examples.
[0401] In addition, various embodiments can also be implemented by means of software modules executed by a processor or directly in hardware. Combinations of software modules and hardware implementations are also possible. Software modules can be stored on any kind of computer-readable storage medium. In particular, according to another embodiment, a non-transitory computer-readable recording medium is provided. The recording medium stores a program that, when executed by one or more processors, causes one or more processors to perform the steps of the method according to the present disclosure.
[0402] By way of example and not limitation, such computer-readable storage media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage, flash memory, or any other medium that can be used to store the desired program code in the form of instructions or data structures and can be accessed by a computer. In addition, any connection is appropriately referred to as a computer-readable medium. For example, if instructions are transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of the medium. However, it should be understood that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other temporary media, but are actually directed to non-temporary tangible storage media. As used herein, disks and optical disks include compact disks (CDs), laser disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.
[0403] It should also be noted that the various features of the different embodiments may be used alone or in any combination as the subject of another embodiment. It will be appreciated by those skilled in the art that many changes and / or modifications may be made to the disclosure as shown in the specific embodiments. Therefore, the present embodiments are considered to be illustrative and non-restrictive in all respects.
[0404] Other aspects
[0405] According to a first aspect, a user equipment (UE) is provided. The UE comprises a transceiver and a circuit. The circuit receives a paging message when in an inactive state in operation. The circuit determines to remain in an inactive state to receive small data in response to the paging message in operation. The circuit sends a response to the paging message to a network node within a transmission opportunity associated with a pre-configured resource while remaining in the inactive state.
[0406] According to a second aspect provided in addition to the first aspect, the circuit is operable to receive the small data within a small data transmission (SDT) from a network node while remaining in an inactive state.
[0407] According to a third aspect provided in addition to one of the first to second aspects, the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
[0408] According to a fourth aspect provided in addition to one of the first to third aspects, the maintaining of the inactive state is determined according to UE configuration.
[0409] According to a fifth aspect provided in addition to the fourth aspect, the UE configuration is set for the UE according to the UE capability of the UE.
[0410] According to a sixth aspect provided in addition to one of the fourth to fifth aspects, the circuit receives a configuration before transitioning from a connected state to an inactive state in operation, and configures the UE configuration accordingly.
[0411] According to a seventh aspect provided in addition to one of the fourth to sixth aspects, the circuit, in operation, sends information about a preferred UE configuration to the network node when the network node is in a connected state.
[0412] According to the eighth aspect provided in addition to one of the fourth to seventh aspects, the circuit is operable to configure or reconfigure the UE configuration based on the configuration of radio bearers.
[0413] According to a ninth aspect provided in addition to the eighth aspect, the configuration of the radio bearer includes whether at least one of a plurality of data radio bearers (DRBs) and / or a plurality of signaling radio bearers (SRBs) is configured for SDT.
[0414] According to the tenth aspect provided in addition to one of the fourth to ninth aspects, the circuit receives a system information (SI) change indication in operation, and configures or reconfigures the UE configuration according to the SI change indication.
[0415] According to an eleventh aspect provided in addition to one of the first to tenth aspects, the response to the paging message to the network node comprises using at least one of:
[0416] Random access small data transfer (RA-SDT),
[0417] Configure Granted Small Data Transfer (CG-SDT), or
[0418] Mobile Terminated Small Data Transfer (MT-SDT).
[0419] According to a twelfth aspect, a network node is provided. The network node comprises a transceiver and a circuit. The circuit is operable to send a paging message to a UE in an inactive state. The circuit is operable to receive a response from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
[0420] According to the thirteenth aspect provided in addition to the twelfth aspect, the circuit is operable to further transmit the small data to the UE in the inactive state within a small data transmission (SDT).
[0421] According to the fourteenth aspect provided in addition to one of the twelfth to thirteenth aspects, the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
[0422] According to the fifteenth aspect provided in addition to one of the twelfth to fourteenth aspects, the circuit receives information about UE configuration.
[0423] According to the sixteenth aspect provided in addition to one of the twelfth to fifteenth aspects, the circuit, in operation, sends a configuration to the UE before the UE transitions from a connected state to an inactive state.
[0424] According to the seventeenth aspect provided in addition to one of the twelfth to sixteenth aspects, the circuit receives information about a preferred UE configuration from the UE in a connected state in operation.
[0425] According to the eighteenth aspect provided in addition to one of the twelfth to seventeenth aspects, the circuit sends a system information (SI) change indication in operation, and the SI change indication includes an indication to configure or reconfigure the UE configuration.
[0426] According to a nineteenth aspect provided in addition to one of the twelfth to eighteenth aspects, the received response to the paging message comprises using at least one of:
[0427] Random access small data transfer (RA-SDT),
[0428] Configure Granted Small Data Transfer (CG-SDT), or
[0429] Mobile Terminated Small Data Transfer (MT-SDT).
[0430] According to a twentieth aspect, a method for a user equipment (UE) in an inactive state is provided. The method comprises the following steps:
[0431] Receive paging messages;
[0432] In response to the paging message, determining to remain in the inactive state to receive the small data; and
[0433] While remaining in the inactive state, a response to the paging message is sent to a network node within a transmission opportunity associated with preconfigured resources.
[0434] According to a twenty-first aspect, a method for sending small data by a network node is provided. The method comprises the following steps:
[0435] Sending a paging message to an inactive UE;
[0436] A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
[0437] According to a twenty-second aspect, there is provided an integrated circuit, which in operation controls a process of a user equipment, the process comprising the following steps performed by the user equipment:
[0438] Receive paging messages;
[0439] In response to the paging message, determining to remain in an inactive state to receive small data; and
[0440] While remaining in the inactive state, a response to the paging message is sent to a network node within a transmission opportunity associated with preconfigured resources.
[0441] According to a twenty-third aspect, there is provided an integrated circuit which, in operation, controls a process of a network node, the process comprising the following steps performed by the network node:
[0442] Sending a paging message to an inactive UE;
[0443] A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
[0444] According to a twenty-fourth aspect, a program stored on a storage medium and comprising code instructions, the code instructions, when executed on one or more processors of a user device, cause the one or more processors to perform the following steps:
[0445] Receive paging messages;
[0446] In response to the paging message, determining to remain in the inactive state to receive small data; and
[0447] While remaining in the inactive state, a response to the paging message is sent to a network node within a transmission opportunity associated with preconfigured resources.
[0448] According to a twenty-fifth aspect, a program stored on a storage medium and comprising code instructions, the code instructions, when executed on one or more processors of a network node, cause the one or more processors to perform the following steps:
[0449] Sending a paging message to an inactive UE;
[0450] A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
[0451] According to a twenty-sixth aspect, a user equipment (UE) is provided. The UE includes a transceiver and a circuit. The circuit receives an indication of receiving small data from a network node in operation. In response to receiving the indication, the circuit determines to remain in the inactive state to receive the small data. While remaining in the inactive state, the circuit sends a response to the indication to the network node.
[0452] According to the twenty-seventh aspect provided in addition to the twenty-sixth aspect, the indication is included in a paging message or a short message.
[0453] According to the 28th aspect provided in addition to one of the 26th to 27th aspects, the indication is included in a physical layer on a radio network temporary identifier RNTI and / or downlink control information DCI and / or a physical downlink control channel PDCCH.
[0454] According to the twenty-ninth aspect provided in addition to one of the twenty-sixth to twenty-eighth aspects, the circuit, in operation, receives the small data within a small data transmission (SDT) from a network node while remaining in an inactive state.
[0455] According to the thirtieth aspect provided in addition to one of the twenty-sixth to twenty-ninth aspects, the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
[0456] According to the 31st aspect provided in addition to one of the 26th to 30th aspects, the response to the paging message to the network node comprises using at least one of:
[0457] Random access small data transfer (RA-SDT),
[0458] Configure Granted Small Data Transfer (CG-SDT), or
[0459] Mobile Terminated Small Data Transfer (MT-SDT).
[0460] According to a thirty-second aspect, a network node is provided. The network node comprises a transceiver and a circuit. The circuit sends an indication of receiving small data to a UE in an inactive state in operation. The circuit receives a response from the UE in the inactive state in operation, the response indicating that the UE is ready to receive the small data in the inactive state.
[0461] According to the thirty-third aspect provided in addition to the thirty-second aspect, the indication is included in a paging message or a short message.
[0462] According to the thirty-fourth aspect provided in addition to one of the thirty-second to thirty-third aspects, the circuit, in operation, also sends the small data within a small data transmission (SDT) from the network node while remaining in an inactive state.
[0463] According to the thirty-fifth aspect provided in addition to one of the thirty-second to thirty-fourth aspects, the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
[0464] According to a thirty-sixth aspect provided in addition to one of the thirty-second to thirty-fifth aspects, the response to the paging message to the network node comprises using at least one of:
[0465] Random access small data transfer (RA-SDT),
[0466] Configure Granted Small Data Transfer (CG-SDT), or
[0467] Mobile Terminated Small Data Transfer (MT-SDT).
[0468] According to a thirty-seventh aspect, a method for a user equipment (UE) in an inactive state is provided. The method comprises the following steps:
[0469] receiving an indication of receiving small data from a network node;
[0470] In response to receiving the indication, determining to remain in the inactive state to receive the small data;
[0471] While remaining in the inactive state, a response regarding the indication is sent to a network node.
[0472] According to a thirty-eighth aspect, a method for sending small data by a network node is provided. The method comprises the following steps:
[0473] Sending an indication of receiving small data to a UE in an inactive state;
[0474] A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
[0475] According to a thirty-ninth aspect, there is provided an integrated circuit, which in operation controls a process of a user equipment, the process comprising the following steps performed by the user equipment:
[0476] receiving an indication of receiving small data from a network node;
[0477] In response to receiving the indication, determining to remain in the inactive state to receive the small data;
[0478] While remaining in the inactive state, a response regarding the indication is sent to a network node.
[0479] According to a fortieth aspect, there is provided an integrated circuit, in operation, controlling a process of a network node, the process comprising the following steps performed by the network node:
[0480] Sending an indication of receiving small data to a UE in an inactive state;
[0481] A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
[0482] According to a forty-first aspect, a program stored on a storage medium and comprising code instructions, the code instructions, when executed on one or more processors of a user device, cause the one or more processors to perform the following steps:
[0483] receiving an indication of receiving small data from a network node;
[0484] In response to receiving the indication, determining to remain in the inactive state to receive the small data;
[0485] While remaining in the inactive state, a response regarding the indication is sent to a network node.
[0486] According to a forty-second aspect, a program stored on a storage medium and comprising code instructions, the code instructions, when executed on one or more processors of a network node, cause the one or more processors to perform the following steps:
[0487] Sending an indication of receiving small data to a UE in an inactive state;
[0488] A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
[0489] In summary, the present disclosure relates to a user equipment (UE), a network node, and corresponding methods for the UE and the network node. The UE includes a transceiver and a circuit. The circuit receives a paging message when in an inactive state in operation. In response to the paging message, the circuit determines to remain in the inactive state to receive small data. While remaining in the inactive state, the circuit sends a response to the paging message to the network node within a transmission opportunity associated with a pre-configured resource.
Claims
1. A user equipment (UE), comprising: Transceiver; as well as Circuit, the circuit in operation: Receive paging messages when inactive; In response to the paging message, determining to remain in the inactive state to receive small data; as well as While remaining in the inactive state, a response to the paging message is sent to a network node within a transmission opportunity associated with preconfigured resources.
2. The UE of claim 1, wherein the circuit is further operable to receive the small data within a small data transmission (SDT) from the network node while remaining in the inactive state.
3. The UE according to any one of claims 1 to 2, wherein the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
4. The UE according to any one of claims 1 to 3, wherein the remaining in the inactive state is determined according to UE configuration.
5. The UE according to claim 4, wherein the UE configuration is set for the UE according to the UE capability of the UE.
6. The UE according to any one of claims 4 to 5, wherein The circuit in operation: Prior to transitioning from a connected state to an inactive state, receiving a configuration; and configuring the UE configuration accordingly.
7. The UE according to any one of claims 4 to 6, wherein The circuit in operation: Information about a preferred UE configuration is sent to the network node while in a connected state.
8. The UE according to any one of claims 4 to 7, wherein The circuit in operation: The UE configuration is configured or reconfigured based on the configuration of the radio bearers.
9. The UE according to claim 8, wherein the configuration of the radio bearer includes whether all of a plurality of data radio bearers (DRBs) and / or at least one of a plurality of signaling radio bearers (SRBs) are configured for SDT.
10. The UE according to any one of claims 4 to 9, wherein The circuit in operation: Receiving a system information SI change indication; and The UE configuration is configured or reconfigured according to the SI change indication.
11. The UE according to any one of claims 1 to 10, wherein the response to the paging message to the network node comprises using at least one of: - Random Access Small Data Transfer (RA-SDT) -Configuration Granted Small Data Transfer (CG-SDT), or - Mobile Terminated Small Data Transfer (MT-SDT).
12. A network node, comprising: Transceiver; as well as The circuit, said circuit in operation: Sending a paging message to an inactive UE; A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
13. The network node of claim 12, wherein the circuit is further operable to send the small data to the UE in the inactive state within a small data transmission (SDT).
14. The network node according to any one of claims 12 or 13, wherein the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
15. The network node according to any one of claims 12 to 14, wherein the circuit receives information about UE configuration.
16. A network node according to any one of claims 12 to 15, wherein the circuit is operable to send a configuration to the UE before the UE transitions from a connected state to an inactive state.
17. A network node according to any one of claims 12 to 16, wherein the circuit is operable to receive information about a preferred UE configuration from the UE in a connected state.
18. A network node according to any one of claims 12 to 17, wherein the circuit is operable to send a system information (SI) change indication, the SI change indication comprising an indication to configure or reconfigure a UE configuration.
19. The network node according to any one of claims 12 to 18, wherein the received response to the paging message comprises using at least one of: - Random Access Small Data Transfer (RA-SDT), -Configuration Granted Small Data Transfer (CG-SDT), or - Mobile Terminated Small Data Transfer (MT-SDT).
20. A method for receiving small data by a user equipment (UE) in an inactive state, the method comprising: receiving paging messages; In response to the paging message, determining to remain in the inactive state to receive the small data; as well as While remaining in the inactive state, a response to the paging message is sent to a network node within a transmission opportunity associated with preconfigured resources.
21. A method for sending small data by a network node, the method comprising: Sending a paging message to an inactive UE; A response is received from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
22. An integrated circuit, wherein the integrated circuit is in operation A process for controlling a user equipment, the process comprising the following steps performed by the user equipment: - Receive paging messages; - in response to the paging message, determining to remain in an inactive state to receive small data; and - while remaining in said inactive state, sending a response to said paging message to a network node within a transmission opportunity associated with preconfigured resources.
23. An integrated circuit, wherein the integrated circuit, in operation, A process for controlling a network node, the process comprising the following steps performed by the network node: - Sending a paging message to an inactive UE; - receiving a response from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
24. A program stored on a storage medium and comprising code instructions which, when executed on one or more processors of a user device, cause the one or more processors to perform the following steps: - Receive paging messages; - in response to the paging message, determining to remain in the inactive state to receive small data; and - while remaining in said inactive state, sending a response to said paging message to a network node within a transmission opportunity associated with preconfigured resources.
25. A program stored on a storage medium and comprising code instructions which, when executed on one or more processors of a network node, cause the one or more processors to perform the following steps: - Sending a paging message to an inactive UE; - receiving a response from the UE in the inactive state, the response indicating that the UE is ready to receive small data in the inactive state.
26. A user equipment UE, comprising: Transceiver; as well as The circuit, which in operation: receiving an indication of receiving small data from a network node; In response to receiving the indication, determining to remain in the inactive state to receive the small data; While remaining in the inactive state, a response regarding the indication is sent to a network node.
27. The UE of claim 26, wherein the indication is included in a paging message or a short message.
28. The UE according to any one of claims 26 or 27, wherein the indication is included in a radio network temporary identifier (RNTI) and / or downlink control information (DCI) and / or a physical layer on a physical downlink control channel (PDCCH).
29. The UE according to any one of claims 26 to 28, wherein the circuit is also operable to receive the small data within a small data transmission (SDT) from the network node while remaining in the inactive state.
30. The UE according to any one of claims 26 to 29, wherein the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
31. The UE of any one of claims 26 to 30, wherein the response to the paging message to a network node comprises using at least one of: - Random Access Small Data Transfer (RA-SDT), -Configuration Granted Small Data Transfer (CG-SDT), or - Mobile Terminated Small Data Transfer (MT-SDT).
32. A network node, comprising: Transceiver; as well as The circuit, said circuit in operation: An indication of receiving small data is sent to a UE in an inactive state, and the circuit is operable to receive a response from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
33. The network node of claim 32, wherein the indication is included in a paging message or a short message.
34. A network node according to any one of claims 32 or 33, wherein the circuit is also operable to send the small data within a small data transfer (SDT) from the network node while remaining in the inactive state.
35. The network node according to any one of claims 32 to 34, wherein the small data is a message carrying a payload or an indication that the UE is to transition to a connected state.
36. A network node according to any one of claims 32 to 35, wherein the response to the paging message to the network node comprises using at least one of: - Random Access Small Data Transfer (RA-SDT), -Configuration Granted Small Data Transfer (CG-SDT), or - Mobile Terminated Small Data Transfer (MT-SDT).
37. A method for a user equipment (UE) in an inactive state, the method comprising: - receiving an indication of receiving small data from a network node; - in response to receiving the indication, determining to remain in the inactive state to receive the small data; - while remaining in said inactive state, sending a response to said indication to a network node.
38. A method for sending small data by a network node, the method comprising: -Sending an indication of receiving small data to an inactive UE; - receiving a response from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
39. An integrated circuit, the integrated circuit being operable to control a process of a user equipment, the process comprising the following steps performed by the user equipment: - receiving an indication of receiving small data from a network node; - in response to receiving the indication, determining to remain in the inactive state to receive the small data; - while remaining in said inactive state, sending a response to said indication to a network node.
40. An integrated circuit operable to control a process of a network node, the process comprising the following steps performed by the network node: -Sending an indication of receiving small data to an inactive UE; - receiving a response from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
41. A program stored on a storage medium and comprising code instructions which, when executed on one or more processors of a user device, cause the one or more processors to perform the following steps: - receiving an indication of receiving small data from a network node; - in response to receiving the indication, determining to remain in the inactive state to receive the small data; - while remaining in said inactive state, sending a response to said indication to a network node.
42. A program stored on a storage medium and comprising code instructions which, when executed on one or more processors of a network node, cause the one or more processors to perform the following steps: -Sending an indication of receiving small data to an inactive UE; - receiving a response from the UE in the inactive state, the response indicating that the UE is ready to receive the small data in the inactive state.
