Data transmission method and device
By configuring processors and timers in RAN nodes, the non-SDT data arrival time and low signaling overhead during MT-SDT program are achieved, and the non-SDT data arrival time and low signaling overhead during MT-SDT program in 3GPP 5G system is solved. The problem of large signaling overhead improves data transmission efficiency.
Patent Information
- Application Number
- CN202280094742.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-15
- Publication Date
- 2024-11-22
AI Technical Summary
In 3GPP 5G systems, non-SDT data arrival during MT-SDT programs has problems with large delays and high signaling overhead, and it is difficult to distinguish whether signaling is subject to SDT or non-SDT.
By configuring the processor in the RAN node, low latency and low signaling overhead for non-SDT data arrival during the MT-SDT program are achieved, timer and priority mechanisms are used to overwrite or cancel RAN pages, and CU CP Communication between CU UP to distinguish SDT and non-SDT data.
It reduces the non-SDT data transmission delay and signaling overhead during the MT-SDT program, and effectively distinguishes whether signaling is subject to SDT or non-SDT, improving data transmission efficiency.
Smart Images

Figure CN119014067A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present application generally relate to wireless communication technology, and more particularly, to a method and apparatus for data transmission. Background Art
[0002] In the 3GPP (3rd Generation Partnership Project) 5G system, small data transmission (SDT) is introduced for several application scenarios. For example, according to the agreement of 3GPP TSG RAN meeting #86, small data transmission can be used for smartphone applications including services from instant messaging services or for non-smartphone applications including services from wearable devices. Small data transmission may also be referred to as small data packets or the like. In general, any device with intermittent small data transmission in a non-connected state (e.g., a radio resource control (RRC) inactive state or an RRC idle state) will benefit from implementing small data transmission in a non-connected state.
[0003] New Radio (NR) Release (Rel)-17 specifies Mobile Oriented (MO)-SDT to allow small packet transmission for packets oriented to the uplink (UL). For the downlink (DL), Mobile Terminated (MT)-SDT (i.e., DL Triggered Small Data) allows similar benefits, such as reducing signaling overhead and user equipment (UE) power consumption by not transitioning to RRC_CONNECTED and reducing latency by allowing fast transmission of (small and infrequent) packets, such as for positioning. In Rel-18, it was agreed to specify the following support for paging triggered SDT, such as MT-SDT according to RP-213583:
[0004] -MT-SDT triggering mechanism for UEs in RRC_INACTIVE, supporting Random Access (RA)-SDT and Configured Grant (CG)-SDT as UL responses; and
[0005] -MT-SDT procedure for initial DL data reception and subsequent UL / DL data transmission in RRC_INACTIVE.
[0006] However, several issues regarding MT-SDT have not been discussed. For example, if DL non-SDT arrives at the radio access network (RAN) during the MT-SDT procedure, the transmission of non-SDT data requires large delay and high signaling overhead.
[0007] In view of the above, the industry desires improved techniques associated with small data transmissions, especially with MT-SDT. Summary of the invention
[0008] One object of embodiments of the present application is to provide a technical solution for data transmission, such as a technical solution for supporting the arrival of non-SDT data during the MT-SDT procedure with small delay and low signaling overhead.
[0009] Some embodiments of the present application provide a radio access network (RAN) node, such as an anchor gNB or a last serving gNB, comprising: a transceiver; and a processor, which is coupled to the transceiver, wherein the processor is configured to: transmit a first RAN paging for MT-SDT via the transceiver; receive downlink non-SDT data of the UE via the transceiver after transmitting the first RAN paging; and transmit information of the arrival of non-SDT data via the transceiver for transmitting the downlink non-SDT data.
[0010] In some embodiments of the present application, the information of the arrival of non-SDT data is transmitted in response to the arrival of the downlink non-SDT data within the running time of the timer. In an example, the information of the arrival of non-SDT data is a second RAN paging for non-SDT transmitted to the UE to overwrite the first RAN paging. In another example, the information of the arrival of non-SDT data is a second RAN paging for non-SDT transmitted to a receiving BS of the UE to overwrite the first RAN paging. The second RAN paging may have a higher priority than the first RAN paging. In yet another example, the information of the arrival of non-SDT data is an indication of overwriting the first RAN paging in the second RAN paging for non-SDT transmitted to the receiving BS of the UE.
[0011] In some embodiments of the present application, the information of the arrival of non-SDT data is transmitted if a request message in response to the first RAN paging is received within the running time of a timer. The processor is configured to buffer the received downlink non-SDT data before receiving the request message. The processor is configured to: initialize a second RAN paging for non-SDT to transmit the downlink non-SDT data if the request message is not received before the timer expires. In an example, the request message is an RRC recovery request from the UE, and the information of the arrival of non-SDT data is an RRC recovery message to the UE to enter an RRC connected state. In another example, the request message may be a retrieve UE context request from a receiving BS of the UE, and the information of the arrival of non-SDT data is an indication of the arrival of non-SDT data in a retrieve UE context response message to the receiving BS.
[0012] In some embodiments of the present application, the timer starts in response to any data of the SDT data being received or the first RAN page being transmitted.
[0013] In some embodiments of the present application, the timer is configured according to at least one of a paging discontinuous reception (DRX) cycle of a receiving BS of the UE, an identifier (ID) of the UE, or a default paging DRX cycle of the UE.
[0014] In some embodiments of the present application, a RAN node includes a central unit (CU) control plane (CP) and a CU user plane (UP) coupled to the CU CP, wherein the CU UP transmits information indicating whether the downlink data arrival is an SDT data arrival or a non-SDT data arrival to the CU CP in response to downlink data arrival, and the CU CP transmits the first RAN paging in response to the information indicating the SDT data arrival. In an example, the information indicating whether the downlink data arrival is an SDT data arrival or a non-SDT data arrival may be an indication of SDT data arrival, and the CUUP transmits the indication of SDT data arrival to the CUCP in response to a data amount of received data being less than or equal to a threshold. In another example, the information indicating whether the downlink data arrival is an SDT data arrival or a non-SDT data arrival is an ID of a data radio bearer (DRB) or an ID of a protocol data unit (PDU) session or an ID of a quality of service (QoS) flow. In another example, the information indicating whether the downlink data arrival is SDT data arrival or non-SDT data arrival is the data amount of each received SDT DRB or each PDU session or each QoS flow or the data amount of all received SDT DRBs or all received PDU sessions or all QoS flows.
[0015] In some embodiments of the present application, the MT-SDT is for a signaling radio bearer (SRB) and the processor is configured to: receive an indication indicating whether signaling released to the UE in an RRC non-connected state is subject to SDT; and transmit the first RAN paging if the signaling is indicated to be subject to SDT.
[0016] Some embodiments of the present application provide another RAN node, such as a receiving gNB or a new serving gNB, comprising: a transceiver; and a processor, which is coupled to the transceiver, wherein the processor is configured to: receive a first RAN paging for MT-SDT from a last serving BS of the UE via the transceiver; receive information of the arrival of non-SDT data from the last serving BS via the transceiver; and transmit a message overwriting the first RAN paging to the UE via the transceiver in response to the information of the arrival of non-SDT data if the first RAN paging has not yet been transmitted.
[0017] In some embodiments of the present application, the information of non-SDT data arrival is a second RAN paging for non-SDT for overwriting the first RAN paging, and the message is the second RAN paging. The second RAN paging may have a higher priority than the first RAN paging.
[0018] In some embodiments of the present application, the information of arrival of non-SDT data is an indication to overwrite the first RAN paging in a second RAN paging for non-SDT, and the message is the second RAN paging.
[0019] In some embodiments of the present application, the processor is configured to transmit a retrieve UE context request, the information of the arrival of non-SDT data is an indication of the arrival of non-SDT data in a retrieve UE context response message in response to the retrieve UE context request, and the message is an RRC recovery message.
[0020] In some embodiments of the present application, in the event that the first RAN page has been transmitted to the UE before receiving the information that non-SDT data has arrived, the processor is configured to ignore the information that non-SDT data has arrived or to transmit feedback to the last serving BS indicating that the first RAN page has been transmitted to the UE.
[0021] Some other embodiments of the present application provide a remote device, such as a UE, comprising: a transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receive a first RAN paging for MT-SDT via the transceiver; receive a second RAN paging overwriting the first RAN paging via the transceiver; and initialize an RRC recovery procedure in response to the second RAN paging if the MT-SDT procedure in response to the first RAN paging has not been initialized.
[0022] In some embodiments of the present application, the processor is configured to initiate the MT-SDT procedure by the RRC layer in response to the first RAN paging before receiving the second RAN paging. The RRC layer may instruct the media access control (MAC) layer to initiate the MT-SDT procedure.
[0023] In some embodiments of the present application, when the MT-SDT procedure is initialized in a layer higher than the MAC layer, the MAC entity does not use the data volume threshold sdt-DataVolumeTrehsold.
[0024] The embodiments of the present application provide a method and apparatus for data transmission, which can solve problems related to MT-SDT, such as how to support the arrival of non-SDT data during the MT-SDT procedure with low latency and low signaling overhead, and how to distinguish whether the signaling is subject to SDT or non-SDT in the case of MT-SDT for signaling radio bearer (SRB), etc. Therefore, the present application can promote and improve the implementation of NR. BRIEF DESCRIPTION OF THE DRAWINGS
[0025] To describe the manner in which the advantages and features of the present application can be obtained, the description of the present application is presented with reference to specific embodiments thereof, which are illustrated in the accompanying drawings. These drawings depict only exemplary embodiments of the present application and are therefore not to be considered limiting of its scope.
[0026] Figure 1 A wireless communication system according to some embodiments of the present application is described.
[0027] Figure 2 A schematic diagram illustrating the internal structure of a RAN node according to some embodiments of the present application.
[0028] Figure 3 is a schematic diagram illustrating the internal structure of a BS according to some other embodiments of the present application.
[0029] Figure 4 is a flowchart illustrating an exemplary procedure of a method of data transmission according to some embodiments of the present application.
[0030] Figure 5 is a flowchart illustrating an exemplary procedure of a method of data transmission in scenario 1 according to some embodiments of the present application.
[0031] Figure 6 is a flowchart illustrating an exemplary procedure of a method for small data transmission in scenario 1 according to some other embodiments of the present application.
[0032] Figure 7 is a flowchart illustrating an exemplary procedure of a method for small data transmission in scenario 2 according to some embodiments of the present application.
[0033] Figure 8 is a flowchart illustrating an exemplary procedure of a method for small data transmission in scenario 2 according to some other embodiments of the present application.
[0034] Fig. 9 A block diagram illustrating an apparatus for small data transmission according to some embodiments of the present application.
[0035] Fig.10A block diagram illustrating an apparatus for small data transmission according to some other embodiments of the present application. DETAILED DESCRIPTION
[0036] The detailed description of the accompanying drawings is intended as a description of the preferred embodiments of the present application and is not intended to represent the only form in which the present application can be practiced. It should be understood that the same or equivalent functions can be accomplished by different embodiments that are intended to be included in the spirit and scope of the present application.
[0037] Reference will now be made in detail to some embodiments of the present application, examples of which are illustrated in the accompanying drawings. To facilitate understanding, embodiments are provided under specific network architectures and new service scenarios (e.g., 3GPP 5G, 3GPP Long Term Evolution (LTE), etc.). It is contemplated that all embodiments in the present application may also be applied to similar technical problems as network architectures and new service scenarios develop. In addition, the terms listed in the present application may be changed, which should not affect the principles of the present application.
[0038] Figure 1 A schematic diagram illustrating an exemplary wireless communication system 100 in accordance with some embodiments of the present application.
[0039] like Figure 1 As shown in FIG. 1 , the wireless communication system 100 includes at least one BS 101 and at least one UE 102. Specifically, for the purpose of illustration, the wireless communication system 100 includes one BS 101 and two terminal devices 102 (eg, UE 102a and UE 102b). Figure 1 The specific number of BSs and terminal devices is described in FIG. 1 , but it is considered that in some other embodiments of the present application, the wireless communication system 100 may include more or fewer BSs and terminal devices.
[0040] The wireless communication system 100 is compatible with any type of network capable of sending and receiving wireless communication signals. For example, the wireless communication system 100 is compatible with the following: a wireless communication network, a cellular telephone network, a network based on time division multiple access (TDMA), a network based on code division multiple access (CDMA), a network based on orthogonal frequency division multiple access (OFDMA), an LTE network, a network based on 3GPP, a 3GPP 5G network, a satellite communication network, a high altitude platform network, and / or other communication networks.
[0041] BS 101 may communicate with a core network (CN) node (not shown) via an interface, such as a mobile management entity (MME) or a serving gateway (S-GW), an access and mobility management function (AMF) or a user plane function (UPF), etc. BSs are also referred to as access points, access terminals, base stations, macro cells, Node-Bs, enhanced Node-Bs (eNBs), gNBs, home Node-Bs, relay nodes or devices or described using other terms used in the art. In 5G NR, BSs may also be referred to as RAN nodes. Each BS may serve a number of UEs within a service area, such as a cell or a cell sector, via wireless communication links. Neighboring BSs may communicate with each other as needed (e.g., during a handover procedure of a UE).
[0042] The terminal device (or remote equipment) 102 (e.g., UE 102a and UE 102b) may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (e.g., a router, a switch, and a modem), or the like. According to an embodiment of the present application, the terminal device may include a portable wireless communication device, a smart phone, a cellular phone, a flip phone, a device with a user identification module, a personal computer, a selective call receiver, or any other device capable of sending and receiving communication signals on a wireless network. In some embodiments, the terminal device may include a wearable device, such as a smart watch, a fitness bracelet, an optical head-mounted display, or the like. In addition, the terminal device may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a wireless terminal, a fixed terminal, a subscriber station, a user terminal, or a device, or described using other terms used in the art. Herein (throughout the specification), although "UE" is exemplarily used as a classic terminal device to explain a terminal device, it should be understood as any type of terminal device.
[0043] Figure 2 is a schematic diagram illustrating the internal structure of a RAN node (eg, BS) according to some embodiments of the present application.
[0044] refer to Figure 2 In the RAN architecture based on CU-DU partitioning, the internal structure of the RAN node (e.g., BS 101) can be divided into a CU 200 and at least one DU 202 (e.g., Figure 2 ). Although Figure 2 A specific number of DUs 202 is depicted in FIG. 2 , but it is contemplated that any number of DUs 202 may be included in a BS.
[0045] CU 200 and DU 202 are connected to each other through an interface called F1, as specified in 3GPP standard documents. RRC layer functions, service data adaptation protocol (SDAP) functions, and packet data convergence protocol (PDCP) layer functions are located in CU 200. Radio link control (RLC) layer functions, medium access control (MAC) layer functions, and physical (PHY) layer functions are located in DU 202.
[0046] According to some embodiments of the present application, a CU may be separated into a central unit control plane (CU CP or CU-CP) unit and at least one central unit user plane (CU UP or CU-UP) unit.
[0047] Figure 3 is a schematic diagram illustrating the internal structure of BS 300 according to some other embodiments of the present application.
[0048] refer to Figure 3 , the CU of the BS 300 may be separated into a CU CP unit 310 and at least one CU UP 312. The CU CP unit 310 and each CU UP unit 312 may be connected to each other via an interface called E1, as specified in the 3GPP standard document. The CU CP unit 310 and the DU 33 of the BS 300 are connected via an interface called F1-C, as specified in the 3GPP document. Each CU UP unit 312 and the DU 33 are connected via an interface called F1-U, as specified in the 3GPP standard document.
[0049] In LTE, when a remote device 102 (e.g., UE) in a non-connected state wants to transmit data, it may trigger an early data transmission (EDT) procedure. The EDT procedure may include an EDT procedure for control plane (CP) cellular Internet of Things (CIoT) evolved packet system (EPS) optimization and an EDT procedure for user plane (UP) CIoT EPS optimization. In the EDT procedure for CP CIoT EPS optimization, data may be transmitted via an RRC early data request message. In the EDT procedure for UP CIoT EPS optimization, data may be transmitted via an RRC connection recovery request message.
[0050] The EDT procedure evolves into the SDT procedure in NR. In Rel-18, it was agreed to specify support for MT-SDT, i.e., downlink SDT. However, there are a number of issues to be resolved regarding MT-SDT.
[0051] For example, one question is how to support the arrival of non-SDT data during the MT-SDT procedure. In conventional technology, when downlink SDT data arrives at a RAN node (e.g., a gNB), the RAN node will initialize MT-SDT paging. The UE will perform the SDT procedure in response to receiving the MT-SDT paging. The RAN node will return the UE to RRC_INACTIVE due to the arrival of downlink non-SDT data. Then, the RAN node will send a RAN paging to the UE for the arrival of downlink non-SDT data. The UE will perform an RRC state transition to RRC_CONNECTED for the transmission of downlink non-SDT data. The RAN node will transmit the downlink non-SDT data to the UE after the UE enters RRC_CONNECTED. Therefore, in conventional technology, the transmission of non-SDT data arriving during the MT-SDT procedure has the disadvantages of large latency and high signaling overhead.
[0052] In view of the above, the embodiments of the present application provide a technical solution for data transmission, especially for solving problems related to data transmission associated with MT-SDT, such as how to support the arrival of non-SDT data during the MT-SDT procedure, how to distinguish whether the signaling is subject to SDT in the case of MT-SDT for SRB, how the CU CP and CU UP of the gNB cooperate to handle MT-SDT, and how to initialize the MT-SDT procedure in the UE in response to RAN paging for MT-SDT, etc. In this article, only downlink data, such as MT-SDT data or downlink non-SDT data, is considered.
[0053] Specifically, when the gNB receives downlink SDT data from the core network (CN), that is, there is downlink SDT data arrival in the gNB, the gNB will trigger the MT-SDT procedure (or referred to as downlink SDT procedure, SDT procedure for MT-SDT, or simply referred to as SDT procedure or the like) in response to the arrival of the downlink SDT data. The MT-SDT data may be used for user plane data or control plane signaling. For example, for a UE released to an RRC non-connected state (e.g., in RRC_INACTIVE), the gNB may receive downlink SDT control plane signaling (also referred to as MT-SDT for SRBs) from the CN, for example, for positioning, and the gNB will trigger the MT-SDT RAN paging procedure (also referred to as RAN paging procedure for MT-SDT or simply referred to as RAN paging procedure for SDT or the like). However, the gNB cannot distinguish whether the signaling from the CN (e.g., non-access stratum (NAS) PDU) is subject to SDT. According to some embodiments of the present application, an indication indicating whether the signaling is subject to SDT will be indicated by the CN to the gNB. In the event that the signaling indicates that SDT is subject, the gNB will trigger the MT-SDT procedure and transmit a RAN paging for MT-SDT (also referred to as MT-SDT RAN paging or just RAN paging for SDT or the like).
[0054] In an example, the CN (e.g., the Access and Mobility Management Function (AMF) of the CN) will indicate to the gNB whether the signaling (e.g., NAS PDU) is subject to SDT through an explicit indication (e.g., through an Information Element (IE) name). When the gNB receives the NAS PDU, the gNB will recognize that the NAS PDU is subject to SDT based on the IE name. In some embodiments of the present application, when releasing the UE to the RRC non-connected state, the gNB may indicate to the CN (e.g., AMF) that the UE is released to the RRC non-connected state, so that the AMF will provide this indication as expected.
[0055] In another example, the indication indicating whether the signaling is subject to SDT is a specific message, such as a new specific message defined for transmitting downlink SDT signaling from the CN to the gNB. When receiving this message, the gNB will know that it is for MT-SDT SRBs and will trigger the MT-SDT paging procedure. In some embodiments of the present application, the gNB receives an LTE Positioning Protocol (LPP) message, and the gNB will recognize that the LPP message is subject to SDT based on the message name. Therefore, the gNB will transmit a RAN page for MT-SDT.
[0056] In the case of CU CP and CU UP division in gNB, the MT-SDT paging procedure will be triggered by CU CP. However, the downlink data of the UE in the RRC non-connected state will first arrive at the CU UP. According to some embodiments of the present application, CU UP will inform the CU CP of the arrival of the downlink data, so that the CU CP triggers the RAN paging procedure for informing the UE to return to the RRC connected state. Considering the MT-SDT scenario, the CU CP needs to know whether the downlink data is downlink SDT data or downlink non-SDT data, so that the CU CP can trigger RAN paging for MT-SDT or RAN paging for non-SDT. RAN paging for non-SDT can be according to the traditional normal RAN paging procedure and is also called normal RAN paging procedure.
[0057] Figure 4 is a flowchart illustrating an exemplary procedure of a method for data transmission according to some embodiments of the present application, in which communication between a CU CP and a CU UP of a gNB is shown.
[0058] like Figure 4 As shown in FIG401 , for downlink data arrival, the CU UP will transmit information indicating whether the downlink data arrival is SDT data arrival or non-SDT data arrival to the CU CP in step 401, such as including such information in a DL DATANOTIFICATION message. When the information indicates SDT data arrival, the CU CP will trigger an MT-SDT paging procedure. Then, the CU CP will transmit a RAN paging for MT-SDT in step 403. When the information indicates non-SDT data arrival or does not indicate SDT data arrival or even does not exist, the CU CP will trigger a RAN paging procedure for non-SDT, such as a normal RAN paging procedure. Then, the CU CP will transmit a RAN paging for non-SDT in step 403.
[0059] In some embodiments of the present application, the information indicating whether the arrival of downlink data is the arrival of SDT data or the arrival of non-SDT data is an indication of the arrival of SDT data or an indication of the arrival of non-SDT data. For example, when receiving downlink data of an SDT RB or SDT PDU session or an SDT QoS flow from a CN (e.g., a user plane function (UPF) of the CN), the CU UP may decide whether to transmit an indication of the arrival of SDT data or an indication of the arrival of non-SDT data based on the amount of data arriving at the CU UP. When the amount of data is less than or equal to the configured threshold, the CU UP will include the indication of the arrival of SDT data in, for example, a DL DATA NOTIFICATION message. Otherwise, the CU UP will not include the indication of the arrival of SDT data or will include the indication of the arrival of non-SDT data in the DL DATA NOTIFICATION message. In some embodiments of the present application, the configured threshold is configured by the CU CP, for example, the CU CP sends the configured threshold to the CU UP.
[0060] In some other embodiments of the present application, the CU CP may implicitly indicate whether the data arrival is SDT data arrival or non-SDT arrival. The CU CP may determine whether the data arrival is SDT arrival or non-SDT arrival based on the information indicated by the CU CP.
[0061] For example, the information indicating whether the arrival of downlink data is the arrival of SDT data or the arrival of non-SDT data is the DRB ID or PDU session ID or QoS flow ID of the arrived (or received) data. The CU UP includes this DRB ID or PDU session ID or QoS flow ID of the arrived data in a message (e.g., DL DATA NOTIFICATION message). According to the included DRB ID or PDU session ID or QoS flow ID, the CU CP will know whether the arrived data is subject to MT-SDT or non-SDT. Then, the CU CP will decide to perform the MT-SDT paging procedure if the arrived data is subject to MT-SDT or to perform the non-SDT paging procedure if the arrived data is subject to non-SDT.
[0062] In another example, the information indicating whether the downlink data arrival is SDT data arrival or non-SDT data arrival is the data amount of each received SDT DRB, each PDU session or each QoS flow, or the data amount of all received SDT DRBs or all PDU sessions or all QoS flows. The CU CP will know whether the arrived data is subject to MT-SDT or non-SDT according to the indicated data amount. Then, the CU CP will decide to perform the MT-SDT paging procedure if the arrived data is subject to MT-SDT or to perform the non-SDT paging procedure if the arrived data is subject to non-SDT.
[0063] In another example, the information indicating whether the downlink data arrival is SDT data arrival or non-SDT data arrival may be a combination of the above exemplary information. For example, the CU UP may indicate to the CU CP both the DRB ID or PDU session ID or QoS flow ID of the arrived data and the data volume of the arrived data.
[0064] After receiving the RAN paging for MT-SDT, the UE will initialize the MT-SDT procedure. In Rel-17, the data volume threshold sdt-DataVolumeThreshold configured by RRC is used by the UE to determine whether to perform the uplink SDT procedure, i.e., the MO-SDT procedure. In the case where the data volume of pending uplink data across all RBs configured for SDT is less than or equal to sdt-DataVolumeThreshold, the UE will continue to perform the SDT procedure. Otherwise, the UE will consider that the conditions for initializing the SDT procedure are not met, and then perform a non-SDT procedure.
[0065] However, in the case of MT-SDT, when the UE initializes the MT-SDT procedure in response to the MT-SDT paging, there is no pending uplink data across all RBs configured for SDT. In view of this, according to some embodiments of the present application, the RRC layer in the UE (i.e., the UE RRC layer) will initialize the MT-SDT procedure upon receiving the RAN paging for MT-SDT. The UE RRC layer will indicate to the layer below the RRC layer (e.g., the MAC layer) that the upper layer initializes the MT-SDT procedure. In the case where the MT-SDT procedure is initialized by the upper layer, the MAC entity will not use the data volume threshold sdt-DataVolumeTrehsold. In other words, according to some embodiments of the present application, the data volume threshold sdt-DataVolumeTrehsold is only used for the MO-SDT procedure. The data volume threshold will not be used to determine whether to execute the MT-SDT procedure.
[0066] In some cases, regarding downlink non-SDT data, when it arrives, the gNB has not yet received the downlink SDT data. The gNB will trigger the RAN paging procedure as per tradition. In some cases, when it arrives, the gNB has received the downlink SDT data but has not yet triggered the RAN paging procedure for MT-SDT. Similarly, the gNB will trigger the RAN paging procedure for non-SDT as per tradition.
[0067] However, in some cases, non-SDT data may arrive at the gNB immediately after the SDT data, for example, during the MT-SDT procedure. As stated above, in conventional techniques, transmitting non-SDT data in such scenarios requires high signaling overhead and has a large latency. Embodiments of the present application also address this problem. For example, according to some embodiments of the present application, a method, for example, performed in a RAN node, may include: transmitting a RAN paging for MT-SDT; receiving downlink non-SDT data of the UE after transmitting the RAN paging for MT-SDT; and transmitting information on the arrival of non-SDT data for transmitting downlink non-SDT data.
[0068] In some scenarios, a UE in an RRC non-connected state may not select a new cell, and there is only one gNB serving the UE, such as an anchor gNB (hereinafter, scenario 1). In some other scenarios, a UE in an RRC non-connected state may perform cell selection or cell reselection to a new cell, and there is communication between the UE and a receiving gNB in the new cell and between the receiving gNB and the anchor gNB (hereinafter, scenario 2). The receiving gNB may also be referred to as a new serving gNB or a serving gNB, and the anchor gNB may also be referred to as a last serving gNB or an old serving gNB. In view of this, more details about some embodiments of the present application are described in view of the following two exemplary scenarios.
[0069] Figure 5 1 is a flowchart illustrating an exemplary procedure of a method for data transmission in scenario 1 according to some embodiments of the present application. Although the method is described at the system level by a RAN node, such as a gNB, and a remote device, such as a UE, it should be understood by those skilled in the art that the method implemented in the gNB and the UE may be implemented separately and / or incorporated by other devices having similar functions.
[0070] like Figure 5 As shown in , according to some embodiments of the present application, in response to the arrival of downlink SDT data, the gNB may transmit a RAN paging for MT-SDT to the UE to initialize the MT-SDT procedure in step 501. The UE is in a non-connected state (e.g., an RRC inactive state).
[0071] After transmitting the RAN paging for MT-SDT, there may be downlink non-SDT data arrival in the gNB, i.e., the gNB receives downlink non-SDT data after transmitting the RAN paging for MT-SDT. At least to reduce signaling overhead and reduce latency, in the event that downlink non-SDT data is received within a certain time during the MT-SDT procedure, the gNB may attempt to overwrite or cancel the transmitted RAN paging for MT-SDT. For example, the gNB may transmit information of the arrival of non-SDT data to the UE for transmitting downlink non-SDT data in step 503.
[0072] The information of the arrival of non-SDT data varies according to various embodiments of the present application, and may be an explicit or implicit indication.
[0073] In some embodiments of the present application, the information of non-SDT arrival may be RAN paging for non-SDT to overwrite or replace RAN paging for MT-SDT. For example, according to a predefined rule, RAN paging for non-SDT may overwrite RAN paging for MT-SDT. When the UE receives RAN paging for non-SDT and the SDT procedure has not been initialized, the UE will ignore the received RAN paging for MT-SDT and initialize the non-SDT procedure in response to the RAN paging for non-SDT according to the predefined rule. In another example, the RAN paging for non-SDT can overwrite the RAN paging for SDT by configuring the RAN paging for non-SDT to have a higher priority than the RAN paging for SDT. When the UE receives RAN paging for non-SDT with a higher paging priority for the same UE and the SDT procedure has not been initialized, the UE will initialize the non-SDT procedure in response to the RAN paging for non-SDT instead of initializing the SDT procedure in response to the RAN paging for SDT.
[0074] In some other embodiments of the present application, the information of the arrival of non-SDT may be an indication to override the RAN paging for SDT, which may be included in the RAN paging for non-SDT or other messages. When the UE receives the RAN paging for non-SDT including the indication to override the RAN paging for SDT and the SDT procedure in response to the RAN paging for SDT has not been initiated, the UE will ignore the previously received RAN paging for MT-SDT and initiate the non-SDT procedure in response to the RAN paging for non-SDT.
[0075] Information on the arrival of non-SDT data is transmitted when downlink non-SDT data arrives within the running time of a timer (hereinafter also referred to as a first timer). The timer can be configured in various ways. For example, the timer starts in response to any data of SDT data being received or in response to RAN paging for MT-SDT being transmitted. In any way, a specific time for determining whether to overwrite the RAN paging for MT-SDT in response to the arrival of non-SDT data can be determined. The gNB can configure the timer based on the ID of the UE or the default paging DRX cycle of the UE or both. For downlink non-SDT data received after the timer expires, the gNB will initialize RAN paging for non-SDT to transmit downlink non-SDT data as traditionally.
[0076] The UE may receive both the RAN paging for MT-SDT transmitted from the gNB in step 501 and the RAN paging for non-SDT transmitted from the gNB in step 505. In the case where the UE has not yet initialized the MT-SDT procedure in response to the RAN paging for MT-SDT, the RAN paging for MT-SDT will be overwritten in the UE by the RAN paging for non-SDT, for example, according to a predefined rule or priority of the RAN paging for non-SDT or an indication of overriding the RAN paging or SDT, etc. The UE will not initialize the MT-SDT procedure in response to the RAN paging for MT-SDT. Instead, the UE will initialize the RRC recovery procedure in response to the RAN paging for non-SDT. For example, in the case where the UE receives both the RAN paging for MT-SDT RAN and the RAN paging for non-SDT at the same time (e.g., in the same paging occasion), the UE will prioritize the RAN paging for non-SDT, that is, the UE will initialize the RRC recovery procedure for receiving non-SDT data in response to the RAN paging for non-SDT. In case the UE receives RAN paging for non-SDT after initiating the SDT procedure in response to the RAN paging for SDT, the UE shall ignore the RAN paging for non-SDT.
[0077] In some other embodiments of the present application, when downlink non-SDT data arrives after sending RAN paging for MT-SDT, the gNB may buffer the non-SDT data in response to RAN paging for MT-SDT and wait for a request message, such as an RRC resume request message from the UE. The gNB may transmit information that the non-SDT data has arrived to cause the UE to enter the RRC connected state upon receiving a request message (such as an RRC resume message) in response to RAN paging.
[0078] For example, Figure 61 is a flowchart illustrating an exemplary procedure of a method for data transmission in scenario 1 according to some other embodiments of the present application. Although the method is described at the system level by a RAN node, such as a gNB, and a remote device, such as a UE, it should be understood by those skilled in the art that the method implemented in the gNB and the UE may be implemented separately and / or incorporated by other devices having similar functions.
[0079] like Figure 6 As shown in FIG. 6 , in step 601, in response to the arrival of downlink SDT data, the gNB may transmit a RAN paging for MT-SDT to the UE in the non-connected state to initialize the MT-SDT procedure.
[0080] After transmitting the RAN paging for MT-SDT, there may be downlink non-SDT data arrival in the gNB, i.e., the gNB receives downlink non-SDT data after transmitting the RAN paging for MT-SDT. The gNB may buffer the received downlink non-SDT data and wait for a request message in response to the RAN paging for MT-SDT within a specific time.
[0081] Similarly, the gNB may count a specific time by setting a timer (hereinafter also referred to as a second timer). For example, the gNB may configure the second timer according to the paging DRX cycle of the receiving gNB or the ID of the UE or the default paging DRX cycle of the UE or any combination thereof. The gNB may start the second timer in response to any data of the SDT data being received or in response to the RAN paging for MT-SDT being transmitted. Although the first timer and the second timer may be configured in the same or similar manner, they should not be regarded as timers.
[0082] In step 603, the gNB may receive an RRC recovery request message from the UE. In the event that the RRC recovery request message is received within the running time of the second timer, the gNB will transmit an RRC recovery message to the UE in response to the RRC recovery request message in step 605, so that the UE can enter the RRC connected state to receive downlink non-SDT data. In the event that the RRC recovery request message is not received after the expiration of the second timer, the gNB will transmit a RAN paging for non-SDT as per the conventional method. Therefore, the signaling overhead and delay for transmitting the arrival of non-SDT data during the MT-SDT procedure can be reduced.
[0083] Figure 71 is a flowchart illustrating an exemplary procedure of a method for data transmission in scenario 2 according to some embodiments of the present application. Although the method is described at a system level through two RAN nodes, such as an anchor gNB, a receiving gNB, and a remote device, such as a UE, a person skilled in the art should understand that the method implemented in the anchor gNB, the receiving gNB, and the UE can be implemented separately and / or incorporated by other devices with similar functions.
[0084] like Figure 7 As shown in FIG. 7 , according to some embodiments of the present application, in response to the arrival of downlink SDT data of the UE, the anchor gNB may transmit a RAN paging for MT-SDT to the receiving gNB of the UE in step 701. In step 703, the receiving gNB is expected to transmit a RAN paging for MT-SDT to the UE to initialize the MT-SDT procedure.
[0085] After transmitting the RAN paging for SDT, there may be downlink non-SDT data arrival in the anchor gNB, that is, the anchor gNB receives downlink non-SDT data after transmitting the RAN paging for SDT. In some embodiments of the present application, in the case where the non-SDT arrives within a specific time that can be counted by a timer (e.g., a first timer), the anchor gNB may attempt to overwrite or cancel the transmitted RAN paging for SDT. For example, in step 705, the anchor gNB may transmit information of the non-SDT arrival to the receiving gNB to overwrite or replace the RAN paging for SDT.
[0086] In the event that downlink non-SDT data arrives within the running time of a timer (e.g., a first timer), information on the arrival of non-SDT data is transmitted. For downlink non-SDT data received after the expiration of the first timer, the anchor gNB will conventionally initiate RAN paging for non-SDT for transmitting downlink non-SDT data.
[0087] Similarly, the anchor gNB may overwrite the RAN paging for MT-SDT by indicating the arrival of non-SDT information in various ways. For example, in some embodiments of the present application, the arrival of non-SDT information is a RAN paging for non-SDT, which may overwrite the RAN paging for SDT according to a predefined rule or by configuring the RAN paging for non-SDT to have a higher priority than the RAN paging for SDT. When the receiving gNB receives the RAN paging for non-SDT and the RAN paging for MT-SDT has not been transmitted to the UE by the receiving gNB, the receiving gNB will cancel the RAN paging for MT-SDT and replace it with the RAN paging for non-SDT. That is, the receiving gNB will not transmit the RAN paging for MT-SDT to the UE in step 703, but will transmit the RAN paging for non-SDT to the UE in step 707.
[0088] In some other embodiments of the present application, the information of the arrival of non-SDT may be an indication to override the RAN paging for MT-SDT, which may be included in the RAN paging or other messages for non-SDT. When the receiving gNB receives the RAN paging message including the indication to override the RAN paging for MT-SDT and the RAN paging for MT-SDT has not been transmitted to the UE by the receiving gNB, the receiving gNB shall cancel the RAN paging for MT-SDT and replace it with the RAN paging for non-SDT.
[0089] In the case where the receiving gNB has sent RAN paging for MT-SDT to the UE, when receiving information of non-SDT arrival (e.g., RAN paging for non-SDT), the receiving gNB may ignore the information of non-SDT arrival or the receiving gNB will transmit feedback that the RAN paging for MT-SDT has been sent to the UE to the anchor gNB. In some embodiments of the present application, another timer similar to the first timer (hereinafter also referred to as the third timer) may also be configured in the receiving gNB, which may be started in response to receiving the RAN paging for MT-SDT or after transmitting the RAN paging for MT-SDT. In the case where the receiving gNB receives the RAN paging for non-SDT within the running time of the third timer, the receiving gNB will transmit the RAN paging for non-SDT to the UE. Otherwise, the receiving gNB will ignore the RAN paging for non-SDT or transmit feedback that the RAN paging for MT-SDT has been sent to the UE to the anchor gNB.
[0090] The UE may receive only RAN paging for MT-SDT or only RAN paging for non-SDT or both. When only RAN paging for MT-SDT is received, the UE will initialize the SDT procedure in response to the RAN paging for MT-SDT. When only RAN paging for non-SDT is received, the UE will initialize the non-SDT procedure in response to the RAN paging for non-SDT. In the case where the UE receives both RAN paging messages and has not yet initialized the MT-SDT procedure in response to the RAN paging for MT-SDT, the RAN paging for MT-SDT will be overwritten in the UE by the RAN paging for non-SDT. The UE will not initialize the MT-SDT procedure in response to the RAN paging for MT-SDT. Instead, the UE will initialize the RRC recovery procedure in response to the RAN paging for non-SDT. For example, in the case where the UE receives both RAN paging for MT-SDT RAN and RAN paging for non-SDT at the same time (e.g., in the same paging occasion), the UE will prioritize the RAN paging for non-SDT, i.e., the UE will initiate an RRC recovery procedure for receiving non-SDT data in response to the RAN paging for non-SDT. In the case where the UE receives RAN paging for non-SDT after initiating the SDT procedure in response to the RAN paging for SDT, the UE will ignore the RAN paging for non-SDT.
[0091] In some other embodiments of the present application, when downlink non-SDT data arrives after sending RAN paging for MT-SDT, the anchor gNB will buffer the non-SDT data and wait for a request message in response to the RAN paging for MT-SDT, such as a retrieve UE context request message from the receiving gNB. The anchor gNB may transmit information of the arrival of non-SDT data to the receiving gNB upon receiving the request message (e.g., retrieve UE context response message), so that the receiving gNB may transmit an RRC resume message to enable the UE to enter the RRC connected state for receiving non-SDT data.
[0092] Figure 8 1 is a flowchart illustrating an exemplary procedure of a method for data transmission in scenario 2 according to some other embodiments of the present application. Although the method is described at a system level through two RAN nodes, such as an anchor gNB, a receiving gNB, and a remote device, such as a UE, a person skilled in the art should understand that the method implemented in the anchor gNB, the receiving gNB, and the UE can be implemented separately and / or incorporated by other devices with similar functions.
[0093] like Figure 8As shown in FIG. 8 , according to some embodiments of the present application, in response to the arrival of downlink SDT data of the UE, the anchor gNB may transmit a RAN paging for MT-SDT to the receiving gNB of the UE in step 801. The receiving gNB will transmit a RAN paging for MT-SDT to the UE in step 803 to initialize the MT-SDT procedure.
[0094] After transmitting the RAN paging for SDT, there may be downlink non-SDT data arriving in the anchor gNB, i.e., the anchor gNB receives the downlink non-SDT data after transmitting the RAN paging for MT-SDT. The anchor gNB may buffer the received downlink non-SDT data and wait for a request message in response to the RAN paging for MT-SDT, such as a retrieve UE context request message from the receiving gNB, within a specific time. Similarly, the gNB may count the specific time by setting a timer, such as the second timer stated above.
[0095] In step 805, the intended UE transmits an RRC resume request to the receiving gNB in response to the RAN paging for MT-SDT. In step 807, in response to the received RRC resume request for SDT, the receiving gNB will transmit a retrieve UE context request message, for example with an SDT indication, to the anchor gNB. In the event that the retrieve UE context request message is received within the running time of the second timer, the anchor gNB will decide that anchor relocation is required. In step 809, the anchor gNB will transmit a retrieve UE context response message including an indication of non-SDT data arrival to the receiving gNB in response to the retrieve UE context request message. The indication of non-SDT data arrival indicates that downlink data forwarding for non-SDT RBs is requested or required. Based on the retrieve UE context response message with the indication of non-SDT data arrival, the receiving gNB will decide to resume the non-SDT RBs and move the UE to the RRC connected state. Next, the receiving gNB will send an RRC resume message in step 811 to cause the UE to enter the RRC connected state to receive downlink non-SDT data. Therefore, the signaling overhead and latency for transmitting non-SDT data can be reduced. In the event that a Retrieve UE Context Request message is received after the second timer expires, the anchor gNB will transmit a RAN paging for non-SDT as per tradition.
[0096] In addition to the method, embodiments of the present application also provide a device for data transmission. Fig. 9 is a block diagram of an apparatus for data transmission according to some embodiments of the present application.
[0097] refer to Fig. 9, the device 900 (e.g., UE or RAN node) may include at least one processor 902 and at least one transceiver 904. The transceiver 904 may include at least one separate receive circuit system 906 and transmit circuit system 908 or at least one integrated receive circuit system 906 and transmit circuit system 908. The at least one processor 902 may be a CPU, a DSP, a microprocessor, etc.
[0098] According to some embodiments of the present application, when the device 900 is a RAN node (e.g., a gNB or a last serving gNB of a UE), the processor is configured to: transmit a first RAN paging for MT-SDT via a transceiver; receive downlink non-SDT data of the UE via a transceiver after transmitting the first RAN paging; and transmit information on the arrival of non-SDT data via a transceiver for transmitting downlink non-SDT data.
[0099] According to some other embodiments of the present application, when the device 900 is a RAN node (e.g., a receiving gNB of a UE), the processor may be configured to: receive a first RAN paging for MT-SDT from a last serving BS of the UE via a transceiver; receive information of the arrival of non-SDT data from the last serving BS via a transceiver; and, if the first RAN paging has not been transmitted, transmit a message overwriting the first RAN paging to the UE via the transceiver in response to the information of the arrival of non-SDT data.
[0100] According to some other embodiments of the present application, when the device 900 is a UE, the processor may be configured to: receive, via a transceiver, a first RAN paging for MT-SDT data; receive, via a transceiver, a second RAN paging that overwrites the first RAN paging; and initialize an RRC recovery procedure in response to the second RAN paging if the MT-SDT procedure in response to the first RAN paging has not been initialized.
[0101] For example, Fig.10 A block diagram of an apparatus 800 illustrating data transmission according to some other embodiments of the present application.
[0102] like Fig.10 As shown in FIG. 1 , an apparatus 1000 may include at least one non-transitory computer-readable medium 1001, at least one receiving circuit system 1002, at least one transmitting circuit system 1004, and at least one processor 1006 coupled to the non-transitory computer-readable medium 1001, the receiving circuit system 1002, and the transmitting circuit system 1004. The apparatus 1000 may be a RAN node or a terminal device (such as a UE) or the like configured to perform the method described above.
[0103] Although in this figure, elements such as at least one processor 1006, transmit circuit system 1004, and receive circuit system 1002 are described as singular, the plural is contemplated unless limitation to the singular is explicitly stated. In some embodiments of the present application, receive circuit system 1002 and transmit circuit system 1004 may be combined into a single device, such as a transceiver. Processor 1006 may be a CPU, DSP, microprocessor, etc. In a specific embodiment of the present application, apparatus 1000 may further include an input device, a memory, and / or other components.
[0104] In some embodiments of the present application, the non-transitory computer-readable medium 1001 may store thereon computer-executable instructions to enable the processor 1006 to implement the method described above with respect to a RAN node (e.g., a gNB or a last gNB). For example, when the computer-executable instructions are executed, the processor 1006 interacts with the receiving circuit system 1002 and the transmitting circuit system 1004 to perform the steps described above with respect to the gNB or the last serving gNB of the UE.
[0105] In some embodiments of the present application, the non-transitory computer-readable medium 1001 may store thereon computer-executable instructions to enable the processor to implement the method for the terminal device as described above. For example, when the computer-executable instructions are executed, the processor 1006 interacts with the receiving circuit system 1002 and the transmitting circuit system 1004 to perform the steps of receiving the gNB of the UE as described above.
[0106] In some embodiments of the present application, the non-transitory computer-readable medium 1001 may store thereon computer-executable instructions to enable the processor to implement the method for the UE as described above. For example, when the computer-executable instructions are executed, the processor 1006 interacts with the receiving circuit system 1002 and the transmitting circuit system 1004 to perform the steps for the UE as described above.
[0107] The method according to the embodiment of the present application case can also be implemented on a programmed processor. However, the controller, flow chart and module can also be implemented on a general or special-purpose computer, a programmed microprocessor or microcontroller and peripheral integrated circuit elements, an integrated circuit, a hardware electronic or logic circuit (such as a discrete element circuit), a programmable logic device or the like. In general, any device capable of implementing the flow chart shown in the figure can be used to implement the processor function of the present application case. For example, the embodiment of the present application case provides a device including a processor and a memory. Computer programmable instructions for implementing the method are stored in a memory, and the processor is configured to execute the computer programmable instructions to implement the method. The method may be a method as described above or other methods according to the embodiment of the present application case.
[0108] Alternative embodiments preferably implement the method according to the embodiments of the present application in a non-transitory computer-readable storage medium storing computer programmable instructions. The instructions are preferably executed by a computer executable component that is preferably integrated with a network security system. The non-transitory computer-readable storage medium can be stored on any suitable computer-readable medium, such as RAM, ROM, flash memory, EEPROM, optical storage device (CD or DVD), hard drive, floppy disk drive, or any suitable device. The computer executable component is preferably a processor, but the instructions can be executed alternatively or additionally by any suitable dedicated hardware device. For example, an embodiment of the present application provides a non-transitory computer-readable storage medium having computer programmable instructions stored therein. The computer programmable instructions are configured to implement the method as described above or other methods according to the embodiments of the present application.
[0109] Although the present application has been described using its specific embodiments, it is obvious that many substitutions, modifications and changes can be understood by those skilled in the art. For example, the various components of the embodiments can be interchanged, added or replaced in other embodiments. In addition, all elements of each figure are not necessary for the operation of the disclosed embodiments. For example, it will enable a person of ordinary skill in the art of the disclosed embodiments to make and use the teachings of the present application by simply adopting the elements of the independent claims. Therefore, the embodiments of the present application as described herein are intended to be illustrative rather than restrictive. Various changes can be made without departing from the spirit and scope of the present application.
Claims
1. A radio access network RAN node, include: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: transmitting, via the transceiver, a first RAN page for a mobile terminated MT-small data transmission (SDT); receiving, via the transceiver, downlink non-SDT data for a user equipment UE after transmitting the first RAN page; and Information arriving via the transceiver transmitting non-SDT data is used to transmit the downlink non-SDT data.
2. The RAN node of claim 1, wherein the information of arrival of non-SDT data is transmitted in response to the downlink non-SDT data arriving within a running time of a timer.
3. The RAN node of claim 2, wherein the information of arrival of non-SDT data is a second RAN paging for non-SDT transmitted to the UE to overwrite the first RAN paging.
4. The RAN node according to claim 2, wherein the information of arrival of non-SDT data is a second RAN paging for non-SDT transmitted to a receiving base station BS of the UE to overwrite the first RAN paging.
5. The RAN node according to claim 2, wherein the information of arrival of non-SDT data is an indication transmitted to a receiving base station BS of the UE to overwrite the first RAN paging in a second RAN paging for non-SDT.
6. The RAN node according to claim 1, wherein the information of the arrival of non-SDT data is transmitted if a request message in response to the first RAN paging is received within the running time of a timer.
7. The RAN node according to claim 1, include: A central unit CU control plane CP and a CU user plane UP coupled to the CUCP, wherein the CU UP transmits information indicating whether the downlink data arrival is SDT data arrival or non-SDT data arrival to the CU CP in response to downlink data arrival, and the CU CP transmits the first RAN paging in response to the information indicating the SDT data arrival.
8. The RAN node according to claim 1, wherein the MT-SDT is for a signaling radio bearer (SRB) and the processor is configured to: receiving an indication indicating whether signaling for release to the UE in RRC non-connected state is subject to SDT; and The first RAN page is transmitted if the signaling is indicated as being subject to SDT.
9. A radio access network RAN node, include: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receiving, via the transceiver, a first RAN paging for mobile terminated MT-small data transmission SDT from a last serving base station BS of the user equipment UE; receiving, via the transceiver, information of arrival of non-SDT data from the last serving BS; and A message overwriting the first RAN page is transmitted to the UE via the transceiver in response to the information that non-SDT data has arrived if the first RAN page has not been transmitted.
10. The RAN node of claim 9, wherein the information of arrival of non-SDT data is a second RAN paging for non-SDT overwriting the first RAN paging, and the message is the second RAN paging.
11. The RAN node of claim 9, wherein the information of arrival of non-SDT data is an indication to overwrite the first RAN page in a second RAN page for non-SDT for overwriting the first RAN page, and the message is the second RAN page.
12. The RAN node of claim 9, wherein the processor is configured to transmit a retrieve UE context request, the information of the arrival of non-SDT data is an indication of the arrival of non-SDT data in a retrieve UE context response message in response to the retrieve UE context request, and the message is a radio resource control (RRC) resume message.
13. The RAN node of claim 9, wherein in a case where the first RAN page has been transmitted to the UE before receiving the information that non-SDT data has arrived, the processor is configured to ignore the information that non-SDT data has arrived or to transmit feedback to the last serving BS indicating that the first RAN page has been transmitted to the UE.
14. A remote device, include: Transceiver; and a processor coupled to the transceiver, wherein the processor is configured to: receiving, via the transceiver, a first radio access network RAN page for a mobile terminated MT-small data transmission (SDT); receiving, via the transceiver, a second RAN page overwriting the first RAN page; and A Radio Resource Control (RRC) recovery procedure is initialized in response to the second RAN paging if an MT-SDT procedure in response to the first RAN paging has not been initialized.
15. The remote device of claim 14, wherein the processor is configured to initialize the MT-SDT procedure by an RRC layer in response to the first RAN page before receiving the second RAN page.
