Early data transmission

Abstract

Various aspects of the present disclosure relate to early data transmission. In one aspect, a UE receives a configuration for an early data transmission operation. The configuration includes at least one uplink resource or at least one downlink resource for the early data transmission operation. The UE then performs the EDT operation based on the configuration. In this way, early data transmission (e.g., in non-terrestrial networks) can be enhanced, thereby improving communication performance in early data transmission.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more particularly to user equipment (UE), base stations, and methods for enhanced early data transmission (EDT). Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices (which may also be referred to as UE, or other suitable terms). The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access technology, fifth-generation (5G) wireless access technology, and other suitable wireless access technologies beyond 5G (e.g., sixth-generation (6G)).

[0003] The wireless communication system may include one or more satellites, which can relay signals or act as base stations, such as in a non-terrestrial network (NTN). Satellites in an NTN can be geostationary orbit (GEO) satellites with a fixed position on Earth, or low Earth orbit (LEO) satellites orbiting the Earth. In an NTN, considering the need to support a large capacity in terms of the number and type of UEs, it is necessary to optimize uplink and downlink transmissions between satellites and UEs. Summary of the Invention

[0004] This disclosure relates to a UE, a base station, and a method for a solution for EDT. Using this UE, base station, and method, uplink and downlink signaling for EDT can be reduced, thereby enhancing EDT in NTN, for example.

[0005] In a first aspect, some embodiments of the UE described herein may include a processor; and a transceiver coupled to the processor, wherein the processor is configured to: receive, via the transceiver and from a base station, a configuration for Early Data Transmission (EDT) operations, wherein the configuration includes at least one uplink (UL) resource or at least one downlink (DL) resource for EDT operations; and to perform EDT operations based on the configuration.

[0006] In some implementations, the processor is configured to perform EDT operations by sending message 3 (Msg3) without requiring the transmission of Msg1 and the reception of Msg2.

[0007] In some implementations, at least one uplink (UL) resource includes at least one of the following: at least one UL resource shared by multiple UEs in a group; at least one UL resource shared by UEs in a cell; or at least one UL resource dedicated to that UE.

[0008] In some implementations, the configuration also includes an identifier associated with a UL resource, and the identifier includes at least one of the following: a first group identifier indicating a group of UEs that are permitted to use at least one UL resource for EDT operation; a first UE identifier indicating a specific UE in the group that is permitted to use at least one UL resource for EDT operation; or a second UE identifier indicating a specific UE in the cell that is permitted to use at least one UL resource for EDT operation.

[0009] In some implementations, the processor is configured to perform EDT operations based on the following: determining a UL resource in at least one UL resource based on one or more of the following: a first set of identifiers, a first UE identifier, or a second UE identifier; and transmitting Msg3 using the determined UL resource without requiring the transmission of Msg1 and the reception of Msg2.

[0010] In some implementations, Msg3 includes one or more of the following: a first set of identifiers, a first UE identifier, or a second UE identifier.

[0011] In some implementations, the processor is configured to determine UL resources by: determining UL resources shared by UEs in a group based on a first UE identifier; determining UL resources shared by UEs in a cell based on a second UE identifier; or randomly determining UL resources shared by UEs in a group or a cell.

[0012] In some implementations, the sequence number of the shared UL resource is determined based on the UE identifier and the resource size of the shared UL resource.

[0013] In some implementations, the processor is configured to send Msg3 by: using UL resources shared by the UEs in the group if one or both of the first group identifier and the first UE identifier are configured; or using UL resources shared by the UEs in the cell if the second UE identifier is configured.

[0014] In some implementations, the processor is configured to perform EDT operations based on the following configuration: sending Msg3 to the base station using UL resources dedicated to the UE.

[0015] In some implementations, the configuration includes thresholds configured for EDT operations, and the configured thresholds include at least one of the following: a signal strength threshold for EDT operations; a signal quality threshold for EDT operations; a delay threshold for EDT operations; a distance threshold for EDT operations; or a time point for EDT operations.

[0016] In some implementations, the processor is configured to perform EDT operations based on the following configuration: initiating an EDT operation when the UE's Non-Access Stratum (NAS) requests a Mobility Initiated Early Data Transmission (MO-EDT) and the uplink data size is below a data size threshold and at least one predetermined condition is met.

[0017] In some implementations, the at least one predetermined condition includes at least one of the following: the configured threshold is a signal strength threshold, and the signal strength received by the UE is equal to or higher than the configured threshold; the configured threshold is a signal quality threshold, and the signal quality received by the UE is equal to or higher than the configured threshold; the configured threshold is a latency threshold, and the timing advance or round-trip time of the UE is equal to or lower than the configured threshold; the configured threshold is a distance threshold, and the distance from the UE to a reference point of the base station or antenna element or serving cell is equal to or lower than the configured threshold; the configured threshold is a time point, and the current time when the MO-EDT is requested is before the time point; or the configured cell stop service time or feeder link handover time is obtained, and the current time when the MO-EDT is requested is before the cell stop service time or feeder link handover time.

[0018] In some implementations, the processor is also configured to calculate the timing advance to be pre-compensated for UL synchronization of the UE to the cell provided by the base station before performing the EDT operation.

[0019] In some implementations, the timing advance is calculated based on valid information including the ephemeris of the serving cell and the location of the UE.

[0020] In some implementations, the processor is also configured to delay the execution of the EDT operation to obtain valid information if valid information is not obtained.

[0021] In some implementations, when valid information is not available, the timing is calculated in advance based on the current information of the ephemeris of the serving cell and the location of the UE.

[0022] In some implementations, the processor is also configured to determine that the EDT operation was unsuccessful in the event that the timed advance calculation fails.

[0023] In some implementations, the processor is also configured to perform a rollback operation if the EDT operation is determined to be unsuccessful.

[0024] In some implementations, the fallback operation includes at least one of the following: suspending the EDT operation for a duration upon receiving a contention indication from the base station or upon the expiration of a timer used by the UE for contention resolution; performing an EDT operation configured with a random access preamble or random access response upon receiving a contention indication or fallback indication from the base station or upon the expiration of a timer used by the UE for contention resolution; or performing connection establishment to transition to a connected state upon receiving a contention indication or fallback indication from the base station or upon the expiration of a timer used by the UE for contention resolution.

[0025] In some implementations, the timer used for contention resolution is separate from the timer used for contention resolution of an EDT configured with a random access preamble or random access response.

[0026] In some implementations, the timer used for contention resolution is a timer specifically designed for non-terrestrial networks, and the start of the timer is offset by the round-trip time from the UE to the base station.

[0027] In some implementations, at least one DL resource includes at least one of the following: at least one DL resource shared by multiple UEs in a group; at least one DL resource shared by UEs in a cell; or at least one DL resource dedicated to that UE.

[0028] In some implementations, the configuration also includes an identifier associated with the reception of message 4 (Msg4), and the identifier includes at least one of the following: a second group identifier indicating a group of UEs that are allowed to receive Msg4 associated with the group; a third UE identifier indicating a specific UE in the group that is allowed to receive Msg4 associated with the group; or a fourth UE identifier indicating a specific UE in the cell that is allowed to receive Msg4 associated with the cell.

[0029] In some implementations, Msg4 includes at least one of the following as a common part: zero information or data from the NAS layer; empty information or data from the NAS layer; common waiting time for delay-tolerant services; common cell reselection configuration including frequency priority; common redirection information; common cause indication or value for connection release; common chain count for next hop; common robust header compression (EOHC) configuration for data radio bearer (DRB); flag indication indicating successful reception of uplink EDT data; or at least one identifier indicating successful or unreceived uplink EDT data from the indicated UE.

[0030] In some implementations, the common portion is received via multicast or broadcast using at least one DL resource shared by multiple UEs in a group or by UEs in a cell.

[0031] In some implementations, Msg4 includes at least one of the following as a dedicated component: non-zero information or data from the NAS layer; UE-specific waiting time for delay-tolerant services; UE-specific cell reselection configuration including frequency priority; UE-specific redirection information; UE-specific identifier for connection recovery; UE-specific downlink data; a flag indicating successful reception of uplink EDT data; a physical layer acknowledgment; or a media access control (MAC) layer acknowledgment.

[0032] In some implementations, the dedicated portion is received via unicast using at least one DL resource dedicated to the UE.

[0033] In some implementations, the processor is also configured to receive Msg4 from the base station and based on at least one of the following: a second set of identifiers, a third UE identifier, and a fourth UE identifier.

[0034] In some implementations, the processor is also configured to delay Global Navigation Satellite System (GNSS) positioning or ephemeris acquisition prior to the reception of Msg4 and if the remaining effective duration of at least one of the serving cell's ephemeris or the UE's location is less than a threshold.

[0035] In some implementations, the unavailable duration or expected duration of reception for Msg4 is indicated in Msg3.

[0036] In some implementations, the remaining valid duration of the information used for UL synchronization is indicated in Msg3.

[0037] In some implementations, the processor is configured to receive Msg4 from the base station in another cell of another cell that has been reselected and synchronized to, prior to the reception of Msg4, if the remaining effective duration of at least one of the cell outage service time or the power supply link handover time is less than a threshold.

[0038] In some implementations, the processor is configured to receive Msg4 by: receiving Msg4 from another base station in another cell synchronized to another base station if, prior to receiving Msg4, the remaining effective duration of at least one of the cell outage service time or the power supply link handover time is less than a threshold.

[0039] In some implementations, the UE and the base station are in a non-terrestrial network (NTN).

[0040] In a second aspect, some implementations of the base station described herein may include a processor; and a transceiver coupled to the processor, wherein the processor is configured to transmit via the transceiver and to a user equipment (UE) configuration for early data transmission (EDT) operations, wherein the configuration includes at least one uplink (UL) resource or at least one downlink (DL) resource for EDT operations.

[0041] In some implementations, at least one UL resource includes at least one of the following: at least one UL resource shared by multiple UEs in a group; at least one UL resource shared by UEs in a cell; or at least one UL resource dedicated to a UE.

[0042] In some implementations, the configuration also includes an identifier associated with a UL resource, and the identifier includes at least one of the following: a first group identifier indicating a group of UEs that are permitted to use at least one UL resource for EDT operation; a first UE identifier indicating a specific UE in the group that is permitted to use at least one UL resource for EDT operation; or a second UE identifier indicating a specific UE in the cell that is permitted to use at least one UL resource for EDT operation.

[0043] In some implementations, the processor is also configured to identify EDT operations based on one of the following: a first set of identifiers; a first UE identifier; a second UE identifier; or UL resources dedicated to the UE.

[0044] In some implementations, the processor is also configured to receive Msg3 sent from the UE based on EDT operations.

[0045] In some implementations, Msg3 includes one or more of the following: a first set of identifiers, a first UE identifier, and a second UE identifier.

[0046] In some implementations, the configuration includes thresholds configured for EDT operation, and the thresholds of the configuration include at least one of the following: a signal strength threshold for EDT operation; a signal quality threshold for EDT operation; a delay threshold for EDT operation; a distance threshold for EDT operation; or a time point for EDT operation.

[0047] In some implementations, the processor is also configured to send, via a transceiver and to the UE, one of the following: a contention indication for EDT operation; a backoff indication for instructing the UE to back off to execute an EDT configured with a random access preamble or a random access response; or a backoff indication for instructing the UE to back off to execute a connection establishment to transition to a connected state.

[0048] In some implementations, at least one DL resource includes at least one of the following: at least one DL resource shared by multiple UEs in a group; at least one DL resource shared by UEs in a cell; or at least one DL resource dedicated to that UE.

[0049] In some implementations, the configuration also includes an identifier associated with the reception of message 4 (Msg4), and the identifier includes at least one of the following: a second set of identifiers indicating a group of UEs that are allowed to receive Msg4 associated with the group; a third UE identifier indicating a specific UE in the group that is allowed to receive Msg4 associated with the group; or a fourth UE identifier indicating a specific UE in the cell that is allowed to receive Msg4 associated with the cell.

[0050] In some implementations, Msg4 includes at least one of the following as a common part: zero information or data from the NAS layer; empty information or data from the NAS layer; common waiting time for delay-tolerant services; common cell reselection configuration including frequency priority; common redirection information; common cause indication or value for connection release; common chain count for next hop; common robust header compression (EOHC) configuration for data radio bearer (DRB); flag indication indicating successful reception of uplink EDT data; or at least one identifier indicating successful or unreceived uplink EDT data from the indicated UE.

[0051] In some implementations, the common portion is transmitted via multicast or broadcast using at least one DL resource shared by multiple UEs in a group or by UEs in a cell.

[0052] In some implementations, Msg4 includes at least one of the following as a dedicated component: non-zero information or data from the NAS layer; UE-specific waiting time for delay-tolerant services; UE-specific cell reselection configuration including frequency priority; UE-specific redirection information; UE-specific identifier for connection recovery; UE-specific downlink data; a flag indicating successful reception of uplink EDT data; a physical layer acknowledgment; or a media access control (MAC) layer acknowledgment.

[0053] In some implementations, the dedicated portion uses at least one DL resource dedicated to the UE and is transmitted via unicast.

[0054] In some implementations, the processor is also configured to send Msg4 to the UE.

[0055] In some implementations, the processor is also configured to send Msg3 received from the UE to another base station before the transmission of Msg4, and when at least one of the cell outage time or power supply link handover time is about to arrive.

[0056] In some implementations, the processor is also configured to send Msg4, generated based on the reception of Msg3 received from the UE, to another base station before the transmission of Msg4 and when at least one of the cell service outage time or power supply link handover time is about to arrive.

[0057] In a third aspect, some implementations of the methods described herein may include: receiving, via a transceiver and from a base station, a configuration for Early Data Transmission (EDT) operations, wherein the configuration includes at least one uplink (UL) resource or at least one downlink (DL) resource for EDT operations; and performing EDT operations based on the configuration.

[0058] In the fourth aspect, some embodiments of the processor described herein may include at least one memory and a controller coupled to the at least one memory and configured such that the controller: receives via a transceiver and from a base station a configuration for early data transmission (EDT) operations, wherein the configuration includes at least one uplink (UL) resource or at least one downlink (DL) resource for EDT operations; and performs EDT operations based on the configuration.

[0059] In the fifth aspect, some implementations of the methods described herein may include: transmitting via a transceiver and to a user equipment (UE) a configuration for early data transmission (EDT) operation, wherein the configuration includes at least one uplink (UL) resource or at least one downlink (DL) resource for EDT operation.

[0060] It should be understood that the summary section is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to be used to limit the scope of this disclosure. Other features of this disclosure will become apparent from the following description. Attached Figure Description

[0061] Figure 1 An example of a wireless communication system for an enhanced EDT according to aspects of this disclosure is shown.

[0062] Figure 2 A signaling diagram of an example procedure for an enhanced EDT is shown, according to some aspects of this disclosure.

[0063] Figure 3 A signaling diagram of an example procedure for an enhanced EDT is shown, according to some aspects of this disclosure.

[0064] Figure 4A A signaling diagram is shown as a portion of an example procedure for an enhanced EDT according to aspects of this disclosure.

[0065] Figure 4B Aspects according to this disclosure are shown Figure 4A The signaling diagram for another part of the example process.

[0066] Figure 5 An example of a device for an enhanced EDT is shown, according to some aspects of this disclosure.

[0067] Figure 6 An example of a processor for an enhanced EDT according to aspects of this disclosure is shown.

[0068] Figure 7 A flowchart of a method for an enhanced EDT according to aspects of this disclosure is shown.

[0069] Figure 8 A flowchart of a method for an enhanced EDT according to aspects of this disclosure is shown. Detailed Implementation

[0070] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0071] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0072] The references to "an embodiment," "an example embodiment," "an embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments(s) described may include a particular feature, structure, or characteristic, but not every embodiment includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it should be understood that, whether explicitly described or not, in conjunction with other embodiments, affecting such feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0073] It should be understood that although terms such as "first" and "second" may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may also be referred to as a second element, and similarly, a second element may also be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate that a number of functions used are selected for the chosen option, and that such selection is not necessarily better, smaller, higher, or more preferred than other options.

[0074] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that, when used herein, the terms “comprising,” “including,” “having,” “constituting,” and / or “forming” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and variations thereof should be understood as open-ended terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “an embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can refer to “A only,” “B only,” or “both A and B.” Other explicit or implicit definitions may be included below.

[0075] Aspects of this disclosure are described in the context of wireless communication systems.

[0076] Figure 1An example of a wireless communication system 100 for enhanced EDT according to aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more terminal devices or UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various wireless access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other embodiments, the wireless communication system 100 may be a 5G network, such as an NR network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable wireless access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support wireless access technologies beyond 5G. Additionally, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0077] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. One or more network entities 102 described herein may be, include, or may be referred to as network nodes, base stations (BS), network elements, radio access network (RAN) nodes, base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0078] In the NTN scenario, network entity 102 can be implemented as a satellite. Network entity 102, in satellite form, can communicate directly with UE 104 using the LTE / NR Uu interface. This satellite can be a transparent satellite or a regenerated satellite. For NTN utilizing a transparent satellite, a base station on Earth can communicate with the UE via the satellite. For example, communication links 110 between the satellite and UE 104, between the satellite and a base station on Earth, and between the base station on Earth and the core network 106 can be used for NTN transparent mode. For NTN utilizing a regenerated satellite, a base station can be mounted and communicate directly with the UE. For example, communication links 110 between the satellite and UE 104 and between the satellite (carrying all or part of an eNB / gNB) and the core network 106 can be used for NTN regenerated mode.

[0079] Network entity 102 can provide a geographic coverage area 112, for which network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within that geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) according to one or more radio access technologies. In some embodiments, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some embodiments, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0080] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable terminology. In some embodiments, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some embodiments, UE 104 may be stationary within the wireless communication system 100A. In some other embodiments, UE 104 may be mobile within the wireless communication system 100A.

[0081] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 As shown in A. Figure 1 As shown in A, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Additionally or alternatively, UE 104 can support communication with other network entities 102 or UE 104, which can act as relays in the wireless communication system 100.

[0082] UE 104 may also support direct wireless communication with other UE 104 via communication link 114. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a sidelink. For example, UE 104 may support direct wireless communication with another UE 104 via a PC5 interface.

[0083] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0084] In some implementations, network entity 102 may be configured in a de-aggregation architecture that utilizes a protocol stack physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-Real-Time RIC, a Non-Real-Time RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0085] An RU can also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a de-converging RAN architecture, one or more components of network entity 102 can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a de-converging RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0086] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can carry higher-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can be connected to one or more DUs or RUs, which can carry lower-layer protocol layers, such as Layer 1 (L1) (e.g., Physical Layer (PHY)) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer) functions and signaling, and each can be at least partially controlled by the CU.

[0087] Additionally or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU may be within the protocol layer (e.g., some functions for the protocol layer may be performed by one of CU, DU, or RU, while other functions of the protocol layer may be performed by a different one of CU, DU, or RU).

[0088] The CU can be further functionally divided into CU control plane (CU-CP) and CU UP (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1c, F1-u), while the DUs can be connected to one or more RUs via front-end communication links (e.g., open front-end (FH) interfaces). In some implementations, the mid-range or front-end communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack supported by corresponding network entities 102 communicating via these communication links.

[0089] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core network (5GC), which may include control plane entities (e.g., Mobility Management Entity (MME), Access and Mobility Management Functions (AMF)) that manage access and mobility, and user plane entities (e.g., Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Functions (UPF)) that route or interconnect packets to external networks. In some implementations, control plane entities may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106.

[0090] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. PDU session can serve as an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0091] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some embodiments, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other embodiments, such as in 5G and other suitable wireless access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multi-frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more sets of parameters.

[0092] One or more parameter sets can be supported in the wireless communication system 100, and the parameter sets may include subcarrier spacing and cyclic prefix. The first parameter set (e.g.) =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and the normal cyclic prefix. In some implementations, the first parameter set associated with the first subcarrier spacing (e.g., 15 kHz) is... =0) allows each subframe to utilize one time slot. The second parameter set (e.g., =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and the normal cyclic prefix. The third parameter set (e.g., =2) can be associated with the third subcarrier spacing (e.g., 60 kHz) and the normal or extended cyclic prefix. The fourth parameter set (e.g., =3) can be associated with the fourth subcarrier spacing (e.g., 120 kHz) and the normal cyclic prefix. The fifth parameter set (e.g., =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0093] The time intervals of resources (e.g., communication resources) can be organized according to frames (also known as radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0094] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth parameter sets (i.e., ...) associated with the corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. =0、 =1、 = 2. =3、 =4) Each subframe may utilize a single time slot, two time slots per subframe, four time slots per subframe, eight time slots per subframe, or 16 time slots per subframe. Each time slot may include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots used for a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier spacing), a time slot may include 12 symbols. The relationship between the number of symbols per time slot for normal and extended cyclic prefixes, the number of time slots per subframe, and the number of time slots per frame may depend on the parameter set. It should be understood that the first parameter set (e.g., 15 kHz) associated with the first parameter set (e.g., =0) can be used interchangeably between subframes and time slots.

[0095] In wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. By way of example, wireless communication system 100 can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410 MHz – 7.125 GHz), FR2 (24.25 GHz – 52.6 GHz), FR3 (7.125 GHz – 24.25 GHz), FR4 (52.6 GHz – 114.25 GHz), FR4a or FR4-1 (52.6 GHz – 71 GHz), and FR5 (114.25 GHz – 300 GHz). In some embodiments, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some embodiments, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.

[0096] FR1 can be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 can be associated with the first parameter set (e.g., =0) is associated with, including a 15 kHz subcarrier spacing; the second parameter set (e.g., =1), including a 30kHz subcarrier spacing; and a third parameter set (e.g., =2), including a 60 kHz subcarrier spacing. FR2 can be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 can be associated with a third parameter set (e.g., =2) associated with, including a 60 kHz subcarrier spacing; and a fourth parameter set (e.g., =3), including a 120 kHz subcarrier spacing.

[0097] NTN refers to a network or network segment that uses radio frequency (RF) resources carried on satellites. The 3GPP Rel-17 specification already provides basic support for NTN features, and Rel-18 provides further optimizations. EDT is a feature supported in the LTE protocol that allows the UE to transmit and receive data without entering a CONNECTED state, thereby reducing UE power consumption. EDT can be divided into Mobile-Initiated Early Data Transmission (MO-EDT) and Mobile-Terminated Early Data Transmission (MT-EDT).

[0098] MO-EDT allows an uplink data transmission during a random access procedure to be optionally followed by a downlink data transmission; and it is triggered when a data request radio resource control (RRC) connection has been established or resumed for a mobile-initiated data request at an upper layer and the uplink data size is less than or equal to the size threshold indicated in the system information.

[0099] MT-EDT is intended for single downlink data transmission during a random access procedure; and if both the UE and the network support MT-EDT and there is a single DL data transmission for that UE, it is initiated by the Mobility Management Entity (MME).

[0100] Typically, the EDT scheme includes Msg1 (preamble) transmission, Msg2 (RAR) reception, Msg3 transmission, and Msg4 reception throughout the random access process. Specifically, the aforementioned EDT only supports unicast transmission with random access and message 4 (Msg4). For Rel-19 NTN enhancements, considering the large-scale capacity requirements in terms of the number and types of supported UEs, an identification mechanism to reduce the required uplink and downlink signaling is desirable. Satellite operators and vendors have proposed optimizing the EDT / pre-configured uplink resource (PUR) mechanism.

[0101] In view of the foregoing, some embodiments of this disclosure focus on enhancing uplink and downlink signaling required to complete an EDT transaction (i.e., transmission of message 3 (Msg3)) without requiring the transmission / reception of message 1 (Msg1) / message 2 (Msg2, Random Access Response (RAR)) or the efficient delivery (reduced overhead) of Msg4 / RRCEarlyDataComplete. Specifically, some embodiments of this disclosure provide a mechanism for implementing or supporting enhancements to EDT in Rel-17 and Rel-18 IoT / NRNTN. In other words, this disclosure enables the formulation of signaling and procedures to optimize EDT operations in NTN deployments, with particular focus on the two enhancements mentioned above for Rel-19 IoT NTN.

[0102] More specifically, regarding enhancing Msg3 transmission without the need for Msg1 and Msg2, embodiments of this disclosure may be provided based on the following considerations.

[0103] In the EDT scheme, the UE relies on the transmission of the EDT-specific preamble to request EDT, and the eNB can identify the request for EDT based on the use of the EDT-specific preamble. If the Msg1 (preamble) transmission for EDT is omitted, a new scheme is needed for the UE to request EDT operation and for the eNB to identify the request for that EDT operation.

[0104] In the EDT scheme, no resources are pre-configured for the UE; therefore, the UE relies on the reception of Msg2 (RAR) to obtain UL resources for subsequent Msg3 transmission. If Msg2 (RAR) is omitted for EDT, then how to configure the UE to have the corresponding resources for Msg3 transmission needs to be specified.

[0105] In the EDT scheme, EDT initiation only considers a single metric: data size, while channel quality (e.g., signal strength) can be guaranteed through random access mechanisms (e.g., power ramp-up). Even if Msg1 (preamble) is omitted for the EDT, ensuring sufficient channel quality for transmitting Msg3 remains a reasonable expectation. Furthermore, for NTNs deployed with LEO satellites, the timing of cell changes (e.g., cell outage time or feeder link handover time) should also be considered.

[0106] In Rel-17 and Rel-18 NTN, the UE needs to pre-compensate the time advance between the UE and the network reference point for UL synchronization before initiating random access. For EDT operations in such deployments, the UE also needs to calculate the pre-compensated timing advance, and the process of obtaining ephemeris or UE location may interrupt the initiation of EDT.

[0107] In the EDT scheme, if the EDT operation fails, the UE falls back to RRC connection establishment. If Msg3 transmission without Msg1 (preamble) / Msg2 (RAR) is supported but unsuccessful, subsequent operations, including possible backoff or fallback, need to be specified.

[0108] In this article, reference will be made to Figure 2 Figure 4 illustrates how to enable or configure EDT operations without Msg1 (preamble) / Msg2 (RAR), i.e., the configuration and execution of EDT operations without Msg1 (preamble) / Msg2 (RAR).

[0109] Figure 2 A signaling diagram of an example procedure 200 for an enhanced EDT according to aspects of this disclosure is shown. Figure 4A A signaling diagram is shown as a portion of an example procedure 400 for an enhanced EDT according to aspects of this disclosure. Figure 4B A signaling diagram of another part of example procedure 400 is shown. For the purposes of discussion, procedures 200 and 400 may relate to UE 104 and BS (e.g., eNB) 102. Procedures 200 and 400 may be applied to reference... Figure 1 The wireless communication system 100 is described above. It should be understood that processes 200 and 400 can also be applied to other communication scenarios, which will not be described in detail hereafter.

[0110] like Figure 2 As shown, UE 104 receives 210 a configuration for EDT operation from BS 102. This configuration includes at least one UL resource for EDT operation. UE 104 performs 220 EDT operation based on this configuration, for example, by sending Msg3 without the transmission of Msg1 and the reception of Msg2. In other words, eNB 102 configures preamble(s) for UE 104 for EDT operation without the need for Msg1 (preamble) / Msg2 (RAR). In one embodiment #1, as... Figure 4A As shown, eNB 102 configures 410 UL resource preambles for UE 104 in IDLE for EDT operation without Msg1 (preamble) / Msg2 (RAR), and UE 104 initiates EDT operation without Msg1 / Msg2 using the configured UL resources.

[0111] In implementation A1, the at least one UL resource may include at least one UL resource shared by multiple UEs in the group. The configuration may also include an identifier associated with the UL resource. The identifier may include one or both of a group identifier and a UE identifier. The group identifier indicates a group of UEs permitted to use at least one UL resource for EDT operation, while the UE identifier indicates a specific UE within that group permitted to use at least one UL resource for EDT operation.

[0112] For example, in a multicast / group configuration shared by a group of UEs 104, a group identifier (e.g., EDT-group-ID) is associated with each group of UEs 104 and the corresponding resources(s). In other words, the UL resources(s) are shared by UEs in the same group indicated by the group identifier associated with that resource. A UE identifier (e.g., EDT-RNTI) for the UEs in the group may be needed to distinguish UEs 104 using the same resources(s). UE 104 can select resources (e.g., shared resources with a sequence number) based on the UE identifier (e.g., the EDT-RNTI for the UEs in the group). The sequence number of the shared UL resource can be determined by the UEs in the group based on the UE identifier and the resource size of the shared UL resource, for example, by taking the modulo of the resource size with respect to the UE identifier. Alternatively, UE 104 can randomly determine the UL resources shared by the UEs in the group. In other words, UE 104 can determine a UL resource in at least one UL resource based on one or both of the group identifier and the UE identifier used to identify the UEs in the group. Then, UE 104 can send Msg3 using the determined UL resources (e.g., UL resources shared by UEs in the group) without the transmission of Msg1 and the reception of Msg2. Msg3 may include one or both of the group identifier and the UE identifier for UE 104 in the group. On the other side of the communication, eNB 102 can receive Msg3 and identify EDT operations that do not require Msg1 (preamble) / Msg2 (RAR) based on at least one of the UL resources(s), group identifier, or UE identifier used.

[0113] In another implementation, A2, at least one UL resource may include at least one UL resource shared by UE 104 in the cell. The configuration may also include an identifier associated with the UL resource. This identifier may include another UE identifier indicating a specific UE 104 in the cell that is permitted to use at least one UL resource for EDT operations.

[0114] For example, in a broadcast manner shared by all UEs 104 in the cell, the (multiple) UL resources are shared by all UEs 104 in the cell. A UE identifier (e.g., EDT-RNTI) for the UEs in the cell may be needed to distinguish UEs 104 using the same resources. UE 104 can select a resource (e.g., a shared UL resource with a sequence number) based on this UE identifier (e.g., the EDT-RNTI for the UEs in the cell). The sequence number of the shared UL resource can be determined by the UEs in the cell based on the UE identifier and the resource size of the shared UL resource, for example, by taking the modulo of the resource size with respect to the UE identifier. Alternatively, UE 104 can also randomly determine the UL resources shared by the UEs in the cell. In other words, UE 104 can determine a UL resource from at least one UL resource based on the UE identifier used to identify the UEs in the cell. Then, without the need for the transmission of Msg1 or the reception of Msg2, UE 104 can send Msg3 using the determined UL resource (e.g., a UL resource shared by the UEs in the cell). Msg3 may include the UE identifier for UE 104 in the cell. On the other side of the communication, eNB 102 may receive Msg3 and, based on the UL resources used and / or the UE identifier, identify that no EDT operation of Msg1 (preamble) / Msg2 (RAR) is required.

[0115] In another implementation, A3, the at least one UL resource may include at least one UL resource dedicated to UE 104. For example, in a unicast manner dedicated to the UE, (multiple) UL resources are dedicated to UE 104. UE 102 may use the UL resource dedicated to that UE to send Msg3. On the other side of the communication, eNB 102 may use the UL resource identifier used without the need for EDT operations of Msg1 (preamble) / Msg2 (RAR).

[0116] It should be understood that the above embodiments can be modified by combining with each other or with other embodiments.

[0117] In the above embodiments A1-A3, eNB 102 can identify an EDT operation requested by UE 104 without Msg1 (preamble) / Msg2 (RAR) via one of the following options. In option B1 (corresponding to A1, A2, and A3), if UE 104 uses dedicated resources to perform an EDT operation without Msg1 (preamble) / Msg2 (RAR), eNB 102 can identify the dedicated resource. In option B2 (corresponding to A1 and A2), if UE 104 can use a UE identifier to perform an EDT operation without Msg1 (preamble) / Msg2 (RAR), eNB 102 can identify the UE identifier. In option B3 (corresponding to A1), if UE 104 can use a group identifier to perform an EDT operation without Msg1 (preamble) / Msg2 (RAR), eNB 102 can identify the group identifier. In option B4, UE 104 explicitly indicates that EDT transmission of Msg1 (preamble) / Msg2 (RAR) is not required.

[0118] As described above, when the configuration for EDT without Msg1 and Msg2 is configured, UE 104 can skip the transmission of 420Msg1 and the reception of Msg2. Figure 4A As shown, the UE can determine that 430 initiates an EDT without Msg1 and Msg2. In some implementations, the configuration may include a threshold configured for EDT operation regarding how to ensure sufficient channel quality for transmitting Msg3.

[0119] Specifically, in addition to data size metrics, other metrics (such as RSRP / distance / TA thresholds) can be introduced for initiating EDT operations that do not require Msg1 (preamble) / Msg2 (RAR). For example, in an embodiment #2 (as shown in the example #2), other metrics can be introduced for initiating EDT operations that do not require Msg1 (preamble) / Msg2 (RAR). Figure 4A As shown in the diagram, eNB 102 can configure thresholds other than the data size threshold for EDT operations that do not require Msg1 (preamble) / Msg2 (RAR). If the UE's Non-Access Stratum (NAS) requests a Mobile-Initiated Early Data Transmission (MO-EDT) and the uplink data size is below the data size threshold, and at least one of the following conditions is met, then UE 104 can initiate the EDT operation.

[0120] Condition 1: The configured threshold is a signal strength threshold, and the signal strength received by the UE is equal to or higher than the configured threshold.

[0121] Condition 2: The configured threshold is a signal quality threshold, and the signal quality received by the UE is equal to or higher than the configured threshold.

[0122] Condition 3: The configured threshold is a latency threshold, and the UE's timing advance or round-trip time is equal to or lower than the configured threshold.

[0123] Condition 4: The configured threshold is a distance threshold, and the distance from the UE to the base station, antenna unit, or reference point of the serving cell is equal to or lower than the configured threshold.

[0124] Condition 5: The configured threshold is a time point, and the current time when MO-EDT is requested is before that time point.

[0125] Condition 6: The cell outage time or feeder link handover time in the configuration is obtained, and the current time when MO-EDT is requested is before the cell outage time or feeder link handover time, or before the remaining time before the cell outage time or feeder link handover time.

[0126] In some implementations, UL synchronization is required to ensure the aforementioned EDT operation without Msg1 (preamble) / Msg2 (RAR). The initiation of an EDT operation without Msg1 (preamble) / Msg2 (RAR) can trigger UE calculations for pre-compensation of timing advance, for example, using newly acquired or stored GNSS location or ephemeris data. For example, before performing the EDT operation, UE104 can calculate the timing advance to be pre-compensated for UL synchronization between the UE and the cell provided by the base station. In one implementation #3, as... Figure 4A As shown, when UE 104 decides to initiate an EDT operation without Msg1 (preamble) / Msg2 (RAR), UE 104 can trigger and execute 440 for calculating the timing advance for pre-compensation of UL synchronization with the NTN cell. This timing advance can be calculated based on valid information, including the ephemeris of the serving cell and the location of UE 104.

[0127] In one implementation, if UE 104 lacks the necessary valid information (including the serving cell's ephemeris and UE location) for calculating the timing advance, i.e., if the valid information is not obtained, UE 104 may delay performing an EDT operation to obtain the valid information, or postpone the initiation of the EDT operation and obtain the necessary valid information. For example, when UE 104 is acquiring GNSS location or ephemeris (SIB31), the initiation of an EDT operation that does not require Msg1 (preamble) / Msg2 (RAR) is delayed. Alternatively, when an EDT operation that does not require Msg1 (preamble) / Msg2 (RAR) is triggered, acquiring GNSS location or ephemeris is suspended (without UL synchronization loss after the validity period).

[0128] In another implementation, if valid information is not obtained, the timing advance is calculated based on the current information of the ephemeris for the serving cell and the UE's location. In other words, UE 104 can use the current information to calculate the timing advance without triggering UL synchronization loss or pausing the acquisition of necessary valid information.

[0129] In another implementation, if the timing advance calculation fails, UE 104 can determine that the EDT operation is unsuccessful. In other words, if UE 104 fails to calculate the timing advance to be pre-compensated, UE 104 can consider the EDT operation unsuccessful.

[0130] In some implementations, if the EDT operation is determined to be unsuccessful, UE 104 can perform a rollback operation. For example, in one embodiment #4 (e.g.) Figure 4B As shown in the figure, when UE 104 can consider the above EDT operation as unsuccessful, the fallback mechanism for EDT operations that do not require Msg1 (preamble) / Msg2 (RAR) can be executed (450), as follows.

[0131] In implementation C1, if a contention indication is received from the base station, or if the timer used by the UE for contention resolution expires, the UE 104 can perform a backoff operation by pausing the EDT operation for a duration. In other words, the UE 104 can pause the EDT operation without Msg1 (preamble) / Msg2 (RAR) and wait for the next attempt, for example, when the UE 104 receives a contention indication from the eNB 102, or when the timer used by the UE 104 for contention resolution (Msg4 received) expires. The UE 104 can back off for the duration to use the next available resource.

[0132] In another implementation C2, if a conflict indication or backoff indication comes from base station 102, or if the timer used by UE 104 for contention resolution expires, UE 104 can perform a backoff operation by executing an EDT operation configured with a random access preamble or random access response.

[0133] In other words, UE 104 can fall back (460) to EDT (with random access, or Msg1 (preamble) / Msg2 (RAR)), for example, when UE 104 receives a contention or fallback indication from eNB 102, or when UE 104 has a timer for contention resolution (Msg4 received) expire. For example, if UE 104 receives a contention or fallback indication from eNB 102, or when UE 104 has a timer for contention resolution (Msg4 received) expire, UE 104 can fall back to connection establishment in order to transition to the CONNECTED state.

[0134] When UE 104 decides to fall back (460) to EDT (with random access, or Msg1 (preamble) / Msg2 (RAR)), UE 104 can determine 461 to initiate a normal EDT with Msg1 and Msg2. Then, UE 104 can send 462 Msg1 (random access preamble) to eNB 102, and eNB 102 can send 463 Msg2 (random access response) to UE 104. Next, UE 104 can use the UL resources (multiple) scheduled in Msg2 to send 464 Msg3 (RAR). RRCEarlyDataRequest or RRCConnectionResumeRequest Msg3 includes RRCEarlyDataRequest (For example (5G-)s-TMSI, establishmentCause,dedicatedInfoNAS (etc.) and RRCConnectionResumeRequest (For example resumeID, resumeCause, UL data wait).

[0135] In another implementation C3, if a contention indication or fallback indication is received from base station 102, or if a timer used by the UE for contention resolution expires, the UE 104 may perform connection establishment to transition to a connected state.

[0136] In other words, UE 104 can directly fall back to connection establishment to transition to the CONNECTED state, for example, when UE 104 receives a contention or fallback indication from eNB 102, or when UE 104 has a timer for contention resolution (Msg4 reception) expire. This contention resolution timer can be separate from the timer used for contention resolution of EDTs configured with random access preambles or random access responses. Alternatively, the contention resolution timer can be a timer dedicated to non-terrestrial networks, and the start of this timer is offset by UE 104 to the round-trip time (RTT) of base station 102. In other words, the timer for contention resolution (Msg4 reception) of EDT operations without Msg1 / Msg2 can be separate from the timer used for contention resolution of EDT operations with Msg1 / Msg2 (e.g., ...). contentionResolutionTimerEDT Different timers. The timer used for contention resolution (Msg4 reception) of EDT operations that do not require Msg1 / Msg2 can be a timer dedicated to NTN, and its start is offset from UE 104 to BS RTT.

[0137] Regarding the enhancement of efficient transmission of Msg4 as described above, some embodiments of this disclosure may be provided based on the following considerations.

[0138] In EDT (with random access, or Msg1 (preamble) / Msg2 (RAR)), Msg4 ( RRCEarlyDataCompleteThe transmission of ) is unicast via dedicated signaling, and all of its included fields ( dedicatedInfoNAS, extendedWaitTime, idleModeMobilityControlInfo, redirectedCarrierInfo All of these are optional.

[0139] The content of Msg4 is not entirely UE-specific. For example, at least the fields... extendedWaitTime , idleModeMobilityControlInfo and redirectedCarrierInfo These fields may be common to multiple or even all UEs in the cell. It is unnecessary to always unicast these fields with repetitive signaling overhead. When there is no corresponding DL data from the NAS, Msg4 can be simplified (e.g., to a flag indication or lower-level indication) to reduce signaling overhead.

[0140] As described in the Msg3 description above, due to the need for UL synchronization or satellite movement, Msg4 ( RRCEarlyDataComplete ) reception may also be interrupted by GNSS positioning or ephemeris acquisition, or by approaching service outage time (and possible cell changes). In these cases, how can we ensure Msg4 ( RRCEarlyDataComplete The method for receiving or handling unsuccessful operations also needs to be specified.

[0141] How to implement Msg4 ( RRCEarlyDataComplete Efficient transmission of ), namely, enhanced Msg4 transmission for EDT operations, will refer to Figure 3 As described in Figure 4. Figure 3 A signaling diagram of an example procedure 300 for enhanced EDT according to aspects of this disclosure is shown. For discussion purposes, procedure 300 may relate to UE 104 and BS (e.g., eNB) 102 in procedures 200 and 400. Procedure 300 may be applied to reference Figure 1 The wireless communication system 100. It should be understood that process 300 can also be applied to other communication scenarios, which will not be described in detail hereafter.

[0142] like Figure 3 As shown, UE 104 receives configuration from base station 102 310 for EDT operation. This configuration includes at least one DL resource for EDT operation. The at least one DL resource may include at least one DL resource shared by multiple UEs in a group. Alternatively or additionally, the at least one DL resource may include at least one DL resource shared by UEs in a cell. Alternatively or additionally, the at least one DL resource may include at least one DL resource dedicated to a UE.

[0143] In some implementations, the configuration may further include an identifier associated with the reception of Msg4. This identifier may include a group identifier indicating a group of UEs permitted to receive Msg4 associated with that group. Additionally or alternatively, the identifier may include a UE identifier indicating a specific UE within the group permitted to receive Msg4 associated with that group. Additionally or alternatively, the identifier may include another UE identifier indicating a specific UE within the cell permitted to receive Msg4 associated with that cell.

[0144] Regarding enhancements to the Msg4 content or format, in implementation D1, Msg4 can be divided into a common part and a private (UE-specific) part.

[0145] In one example, for CP-EDT RRCEarlyDataComplete The public portion may include at least one of the following: zero information or data from the NAS layer (e.g., zero...). dedicatedInfoNAS ); empty information or data from the NAS layer (e.g., empty dedicatedInfoNAS ); for public wait times for delay-tolerant services (e.g., public... extendedWaitTime ); including public cell reselection configurations based on frequency priority (e.g., idleModeMobilityControlInfo ); public redirect information (e.g., redirectedCarrierInfo ); a flag indicating successful reception of uplink EDT data; at least one UE identifier indicating whether uplink EDT data from the indicated UE has been successfully received or not received.

[0146] For use with UP-EDT RRCConnectionRelease The common part may include at least one of the following: a common cause indication or value for connection release (e.g., releaseCause ); a common chain count used for the next hop (e.g., NextHopChainingCount ); Common Robust Header Compression (EOHC) configuration for Data Radio Bearer (DRB) (e.g. drb-ContinueROHC ); a flag indicating successful reception of uplink EDT data; or at least one flag indicating successful or unsuccessful reception of uplink EDT data from the indicated UE.

[0147] The common portion can be transmitted via broadcast or multicast. That is, the common portion can be sent from base station 102 and received by UE 104 via multicast or broadcast using at least one DL resource shared by multiple UEs in the group or by UEs in the cell. As an example, for the multicast mode, a group identifier is introduced and can be the same as the group-based configuration used for EDT operation without Msg1 (preamble) / Msg2 (RAR), i.e., the EDT-group-ID in implementation A1.

[0148] In addition, such as Figure 4B As shown, in embodiment #5, eNB 102 may respond to Msg3 (RRCEarlyDataRequest for CP-EDT or RRCConnectionResumeRequest for UP-EDT) by sending at least a portion of Msg4 (RRCEarlyDataComplete for CP-EDT or RRCConnectionRelease for UP-EDT) to the UE using multicast or broadcast.

[0149] In one example, for RRCEarlyDataComplete for CP-EDT, the dedicated portion may include at least one of the following: non-zero information or data from the NAS layer (e.g., non-zero dedicatedInfoNAS); UE-specific waiting time for delay-tolerant services (e.g., UE-specific extendedWaitTime); UE-specific cell reselection configuration including frequency priority (e.g., idleModeMobilityControlInfo); UE-specific redirection information (e.g., redirectedCarrierInfo); or a flag indication indicating successful reception of uplink EDT data.

[0150] For RRCConnectionRelease for UP-EDT, the dedicated portion may include at least one of the following: a UE-specific identifier (e.g., resumeID) for connection recovery; UE-specific downlink data; a flag indicating successful reception of uplink EDT data; a physical layer acknowledgment; or a media access control (MAC) layer acknowledgment.

[0151] The dedicated portion (if present) can be transmitted as an incremental configuration via unicast. A timing advance command (TAC) can also be included to adjust the UE's TA. Specifically, the dedicated portion can be transmitted from base station 102 and received from UE 104 via unicast (dedicated signaling) using at least one DL resource dedicated to that UE. The UE can then derive the complete Msg4 based on a portion of the Msg4 received via multicast or broadcast and another portion of the Msg4 received via unicast.

[0152] In implementation D2, Msg4 is a non-RRC message used as an ACK for Msg3, such as a Layer 1 ACK (optionally containing a time advance adjustment) or a MAC CE ACK (optionally containing a time advance command).

[0153] Next, UE 104 performs 320 EDT operation based on this configuration. For example, UE 104 may receive Msg4 sent from base station 102, and based on at least one of the following: group identifier, UE identifier for UEs in the group, and UE identifier for UEs in the cell.

[0154] In some implementations, UL synchronization for the reception of Msg4 needs to be performed or ensured. For example, the reception of Msg4 may be interrupted by Global Navigation Satellite System (GNSS) positioning or ephemeris acquisition. In implementation E1, for possible reception interruption caused by GNSS positioning or ephemeris acquisition, UE 104 may indicate the duration or expected duration of the unavailability of the reception of Msg4. That is, the duration or expected duration of the unavailability of the reception of Msg4 is indicated in Msg3.

[0155] Alternatively, for example in embodiment #6, UE 104 may decide to send Msg3 for EDT operation and expect to receive Msg4 in response, while at least one of the necessary information for UL synchronization (including the ephemeris of the serving cell and the UE location) before the end of its effective duration. In this case, in response to a possible reception interruption caused by GNSS positioning or ephemeris acquisition, UE 104 may indicate the remaining effective duration of the necessary information for UL synchronization (e.g., GNSS / ephemeris) in Msg3. That is, the remaining effective duration of the information for UL synchronization is indicated in Msg3.

[0156] In implementation E2, for potential reception interruptions caused by GNSS positioning or ephemeris acquisition, GNSS positioning or ephemeris acquisition can be delayed without triggering UL synchronization loss after Msg3 transmission. For example, UE 104 can delay GNSS positioning or ephemeris acquisition before Msg4 is received, and if the remaining valid duration of at least one of the serving cell's ephemeris or the UE's location is less than a threshold.

[0157] In some implementations, reception of Msg4 may be interrupted due to approaching cell outage time or power supply link handover time. For example, in one embodiment #7, UE 104 may decide to send Msg3 for EDT operation and expect to receive Msg4 as its response, while at least one of the cell outage time or power supply link handover time is approaching.

[0158] In these implementations, Msg4 reception may be interrupted whether the cell changes or not. In the case of a cell change, if UE 104 can guarantee UL synchronization in the next cell or the reselected cell, UE 104 can maintain the continuity of Msg4 reception and continue receiving Msg4 in the next cell after cell reselection. The network can ensure delivery via X2 / S1 interface signaling between eNBs. For example, if the remaining effective duration of at least one of the cell outage time or feeder link handover time is less than a threshold before Msg4 reception, UE 104 can receive Msg4 from base station 102 in another cell of another cell that has been reselected and synchronized.

[0159] If UE 104 can guarantee UL synchronization in the cell after handover, provided the cell remains unchanged, UE 104 can maintain continuity of Msg4 reception and continue receiving Msg4 in the next cell after satellite handover with resynchronization. For example, if the remaining effective duration of at least one of the cell downtime or feeder link handover time is less than a threshold before receiving Msg4, UE 104 can receive Msg4 from another base station 102 in another cell synchronized to that other base station.

[0160] Figure 5 An example of an apparatus 500 for enhanced early data transmission according to aspects of this disclosure is shown. Apparatus 500 may be an example of network entity 102 or UE 104 as described herein. Apparatus 500 may support wireless communication with one or more network entities 102, UE 104, or any combination thereof. Apparatus 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 502, memory 504, transceiver 506, and optional I / O controller 508. These components may be electronically or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0161] Processor 502, memory 504, transceiver 506, or various combinations thereof or various components thereof may be examples of various components for performing the operations described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof or components thereof may support methods for performing one or more of the operations described herein.

[0162] In some embodiments, processor 502, memory 504, transceiver 506, or various combinations thereof, or various components thereof, may be implemented in hardware (e.g., as a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described herein. In some embodiments, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more of the functions described herein (e.g., processor 502 executing instructions stored in memory 504).

[0163] For example, processor 502 can support wireless communication at device 500 according to examples disclosed herein. Processor 502 can be configured or operable to support: components for receiving a configuration for an early data transmission operation, wherein the configuration includes at least one uplink resource or at least one downlink resource for the early data transmission operation; and components for performing the early data transmission operation based on the configuration. Additionally, processor 502 can be configured or operable to support performing the combinations described above. Figure 1 The components for various other operations of the UE as shown in Figure 4.

[0164] Alternatively, in some embodiments, processor 502 may be configured or operable to support: components for transmitting a configuration for an early data transmission operation, wherein the configuration includes at least one uplink resource or at least one downlink resource for the early data transmission operation. Additionally, processor 502 may be configured or operable to support performing the combination described above. Figure 1 The various other operating components of the base station shown in Figure 4.

[0165] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some embodiments, processor 502 may be configured to use a memory controller to operate a memory array. In some other embodiments, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.

[0166] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some embodiments, the code may not be directly executable by processor 502, but may cause a computer (e.g., at compile and execution time) to perform the functions described herein. In some embodiments, memory 504 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0167] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripherals not integrated into device M02. In some embodiments, I / O controller 508 can represent a physical connection or port to an external peripheral. In some embodiments, I / O controller 508 can utilize an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some embodiments, I / O controller 508 can be implemented as part of a processor (such as processor 506). In some embodiments, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0168] In some embodiments, device 500 may include a single antenna 510. However, in other embodiments, device 500 may have more than one antenna 510 (i.e., multiple antennas), including multiple antenna panels or antenna arrays that may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 506 may communicate bidirectionally via one or more antennas 510, wired or wireless links, as described herein. For example, transceiver 506 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets to provide modulated packets to one or more antennas 510 for transmission, and for demodulating packets received from one or more antennas 510. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0169] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes, such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 510 for transmitting the amplified signal over the air or wireless medium.

[0170] The receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 510 for receiving signals over the air or a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding / processing the demodulated signal to receive the transmitted data.

[0171] Figure 6 An example of a processor 600 for an enhanced EDT according to aspects of this disclosure is shown. Processor 600 may be an example of a processor configured to perform various operations as described herein. Processor 600 may include a controller 602 configured to perform various operations as described herein. Processor 600 may optionally include at least one memory 604, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be electronically or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0172] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to examples as described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to or included in the processor chipset (e.g., processor 600)), or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0173] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations according to the examples described herein. For example, controller 602 can operate as a control unit of processor 600 to generate control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating the timing of operations.

[0174] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, such that processor 600 supports various operations according to the examples described herein. Controller 602 may be configured to track the memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operations to be performed and their operands. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 500, such that processor 600 supports various operations according to the examples described herein. Additionally or alternatively, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0175] Memory 604 may include one or more caches (e.g., memory native to processor 600 or included in processor 600) or other memory, such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some embodiments, memory 604 may be located inside or on the processor chipset (e.g., native to processor 600). In some other embodiments, memory 604 may be located outside the processor chipset (e.g., remote from processor 600).

[0176] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions. For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.

[0177] One or more ALUs 606 may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALUs 606 may be located inside or on a processor chipset (e.g., processor 600). In some other embodiments, one or more ALUs 606 may be located outside the processor chipset (e.g., processor 600). One or more ALUs 606 may perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 606 may receive input operands and an opcode, the opcode determining the operation to be performed. One or more ALUs 606 may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs 606 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALUs 606 to handle conditional operations, comparisons, and bitwise operations.

[0178] Processor 600 can support wireless communication according to examples disclosed herein. Processor 600 can be configured or operable to support: components for receiving a configuration for an early data transmission operation, wherein the configuration includes at least one uplink resource or at least one downlink resource for the early data transmission operation; and components for performing the early data transmission operation based on the configuration. Additionally, processor 600 can be configured or operable to support performing the combinations described above. Figure 1 The components for various other operations of the UE as shown in Figure 4.

[0179] Alternatively, in some embodiments, processor 600 may be configured or operable to support: components for transmitting a configuration for an early data transmission operation, wherein the configuration includes at least one uplink resource or at least one downlink resource for the early data transmission operation. Additionally, processor 600 may be configured or operable to support performing the combinations described above. Figure 1 The various other operating components of the base station shown in Figure 4.

[0180] Figure 7 A flowchart of a method 700 for an enhanced EDT according to aspects of this disclosure is shown. Operation of method 700 can be implemented by a device or components thereof as described herein. For example, operation of method 700 can be performed by a UE 104 as described herein. In some embodiments, the device can execute a set of instructions to control functional elements of the device to perform the function. Additionally or alternatively, the device can use dedicated hardware to perform aspects of the function.

[0181] At 710, the method may include receiving configuration for EDT operation, wherein the configuration includes at least one UL resource or at least one DL resource for the EDT operation. Operation of 710 may be performed according to examples as described herein. In some embodiments, aspects of operation of 710 may be provided by reference to [reference needed]. Figure 1 The aforementioned device is used to perform this action.

[0182] At 720, the method may include performing an EDT operation based on the configuration. The operation at 720 can be performed according to examples as described herein. In some implementations, aspects of the operation at 720 may be derived from references... Figure 1 The aforementioned device is used to perform this action.

[0183] Figure 8A flowchart of a method 800 for an enhanced EDT according to aspects of this disclosure is shown. Operation of method 800 can be implemented by a device or components thereof as described herein. For example, operation of method 800 can be performed by a base station 102 as described herein. In some embodiments, the device can execute a set of instructions to control functional elements of the device to perform the function. Additionally or alternatively, the device can use dedicated hardware to perform aspects of the function.

[0184] At 810, the method may include sending a configuration for EDT operation, wherein the configuration includes at least one UL resource or at least one DL resource for the EDT operation. The operation of 810 may be performed according to examples as described herein. In some embodiments, aspects of the operation of 810 may be provided by reference to [reference needed]. Figure 1 The aforementioned device is used to perform this action.

[0185] It should be noted that reference has been made. Figure 1 The embodiments of this disclosure described up to Figure 4 are also applicable to device 500, processor 600, and methods 700 and 800.

[0186] It should be noted that the methods described herein are possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, two or more aspects of the method can be combined.

[0187] The various exemplary blocks and components described herein in conjunction with this disclosure can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which are designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0188] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented by software executed by a processor, these functions can be stored on a computer-readable medium or sent to a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the function are implemented at different physical locations.

[0189] Computer-readable media include both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store required program code components in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.

[0190] As used herein, including in the claims, the article “a” preceding an element is not limited and is understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” as used in a list of items (e.g., a list of items beginning with phrases such as “at least one,” “one or more,” or “one or two”) indicates an inclusive list, such as a list that makes at least one of A, B, or C refer to A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.

[0191] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be applied within the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: The transceiver receives, via the transceiver and from the base station, a configuration for Early Data Transmission (EDT) operation, wherein the configuration includes at least one uplink (UL) resource or at least one downlink (DL) resource for the EDT operation; and The EDT operation is performed based on the configuration.

2. The UE of claim 1, wherein the processor is configured to perform the EDT operation by: Send message 3 (Msg3) without needing to transmit Msg1 or receive Msg2.

3. The UE of claim 1, wherein the at least one uplink (UL) resource comprises at least one of the following: At least one UL resource shared by multiple UEs in the group; At least one UL resource shared by UEs in the cell; or At least one UL resource dedicated to the UE.

4. The UE of claim 3, wherein the configuration further includes an identifier associated with the UL resource, and the identifier includes at least one of the following: A first set of identifiers indicates a group of UEs that are permitted to use the at least one UL resource for the EDT operation; A first UE identifier indicates a specific UE in a group that is permitted to use the at least one UL resource for the EDT operation; or A second UE identifier, which indicates a specific UE in a cell that is permitted to use the at least one UL resource for the EDT operation.

5. The UE of claim 4, wherein the processor is configured to perform the EDT operation based on the following: The UL resource is determined from the at least one UL resource based on one or more of the following: the first set of identifiers, the first UE identifier, or the second UE identifier; and Without requiring the transmission of Msg1 and the reception of Msg2, Msg3 is transmitted using the determined UL resources. The Msg3 includes one or more of the following: the first group identifier, the first UE identifier, or the second UE identifier.

6. The UE of claim 1, wherein the configuration includes a threshold configured for the EDT operation, and the configured threshold includes at least one of the following: The signal strength threshold for the EDT operation; The signal quality threshold for the EDT operation; The latency threshold for the EDT operation; The distance threshold for the EDT operation; or The timing of the EDT operation.

7. The UE of claim 6, wherein the processor is configured to perform the EDT operation based on the following: The EDT operation is initiated when the UE's Non-Access Stratum (NAS) Request for Mobility Initiated Early Data Transmission (MO-EDT) occurs, the uplink data size is below a data size threshold, and at least one predetermined condition is met. The at least one predetermined condition includes at least one of the following: The configured threshold is the signal strength threshold, and the signal strength received by the UE is equal to or higher than the configured threshold; The configured threshold is the signal quality threshold, and the signal quality received by the UE is equal to or higher than the configured threshold; The configured threshold is the latency threshold, and the UE's timing advance or round-trip time is equal to or lower than the configured threshold; The configured threshold is the distance threshold, and the distance from the UE to the reference point of the base station, antenna unit, or serving cell is equal to or lower than the configured threshold; The configured threshold is the time point, and the current time when the MO-EDT is requested is before the time point; or The cell outage time or power supply link handover time in the configuration is obtained, and the current time when the MO-EDT is requested is before the cell outage time or the power supply link handover time.

8. The UE of claim 1, wherein the processor is further configured to: Before performing the EDT operation, the timing advance to be pre-compensated is calculated for the UE to synchronize with the UL of the cell provided by the base station; and If the calculation for the timing advance fails, it is determined that the EDT operation is unsuccessful.

9. The UE of claim 8, wherein the processor is further configured to: If the EDT operation is determined to be unsuccessful, a rollback operation is performed. The rollback operation mentioned above includes at least one of the following: If a contention indication is received from the base station or if the timer used by the UE for contention resolution expires, the EDT operation is suspended for the duration. Upon receiving a contention indication or backoff indication from the base station, or upon the expiration of the timer used by the UE for contention resolution, an EDT operation configured with a random access preamble or random access response is performed. or Upon receiving the contention indication or backoff indication from the base station, or upon the expiration of the timer used by the UE for contention resolution, a connection establishment is performed to transition to a connected state.

10. The UE of claim 9, wherein the timer for contention resolution is a timer specifically for non-terrestrial networks, and the start of the timer is offset by the UE to the round-trip time of the base station.

11. The UE according to any one of claims 1 to 10, wherein the at least one DL resource comprises at least one of the following: At least one DL resource shared by multiple UEs in the group; At least one DL resource shared by UEs in the cell; or At least one DL resource dedicated to the UE.

12. The UE of claim 11, wherein the configuration further includes an identifier associated with the reception of message 4 (Msg4), and the identifier includes at least one of the following: The second group of identifiers indicates a group of UEs that are allowed to receive Msg4 associated with the group; A third UE identifier indicates a specific UE in the group that is allowed to receive Msg4 associated with the group; or The fourth UE identifier indicates a specific UE in the cell that is allowed to receive Msg4 associated with the cell.

13. The UE of claim 12, wherein the Msg4 comprises at least one of the following as a common part: Zero information or data from the NAS layer; Empty information or data from the NAS layer; Public waiting time for delay-tolerant services; This includes public cell reselection configuration based on frequency priority; Public redirect information; A common reason indicator or value used for connection release; A common chained counter used for the next hop; Common Robust Header Compression (EOHC) configuration for Data Radio Bearer (DRB); A flag indicating successful reception of uplink EDT data; or At least one identifier indicating whether uplink EDT data from the indicated UE was successfully received or not received.

14. A base station, comprising: processor; as well as The transceiver coupled to the processor, The processor is configured as follows: The transceiver transmits a configuration for Early Data Transmission (EDT) operation to the user equipment (UE), wherein the configuration includes at least one uplink (UL) resource or at least one downlink (DL) resource for the EDT operation.

15. The base station of claim 14, wherein the at least one UL resource comprises at least one of the following: At least one UL resource shared by multiple UEs in the group; At least one UL resource shared by UEs in the cell; or At least one UL resource dedicated to the UE.

16. The base station of claim 15, wherein the configuration further includes an identifier associated with the UL resource, and the identifier includes at least one of the following: A first set of identifiers indicates a group of UEs that are permitted to use the at least one UL resource for the EDT operation; A first UE identifier indicates a specific UE in a group that is permitted to use the at least one UL resource for the EDT operation; or A second UE identifier, which indicates a specific UE in a cell that is permitted to use the at least one UL resource for the EDT operation.

17. The base station of claim 14, wherein the configuration includes a threshold configured for the EDT operation, and the configured threshold includes at least one of the following: The signal strength threshold for the EDT operation; The signal quality threshold for the EDT operation; The latency threshold for the EDT operation; The distance threshold for the EDT operation; or The timing of the EDT operation.

18. The base station according to any one of claims 14 to 17, wherein the at least one DL resource comprises at least one of the following: At least one DL resource shared by multiple UEs in the group; At least one DL resource shared by UEs in the cell; or At least one DL resource dedicated to the UE.

19. The base station of claim 18, wherein the configuration further includes an identifier associated with the reception of message 4 (Msg4), and the identifier includes at least one of the following: The second group of identifiers indicates a group of UEs that are allowed to receive Msg4 associated with the group; A third UE identifier indicates a specific UE in the group that is allowed to receive Msg4 associated with the group; or The fourth UE identifier indicates a specific UE in the cell that is allowed to receive Msg4 associated with the cell.

20. The base station of claim 19, wherein the Msg4 comprises at least one of the following as a common part: Zero information or data from the NAS layer; Empty information or data from the NAS layer; Public waiting time for delay-tolerant services; This includes public cell reselection configuration based on frequency priority; Public redirect information; A common reason indicator or value used for connection release; A common chained counter used for the next hop; Common Robust Header Compression (EOHC) configuration for Data Radio Bearer (DRB); A flag indicating successful reception of uplink EDT data; or At least one identifier indicating whether uplink EDT data from the indicated UE was successfully received or not received.

Images