Methods and apparatus related to advance time management
By configuring offset threshold information based on DL BWP SCS in NTN and ATG networks, the problem of inconsistent timing advance management caused by different SCSs is solved, and more reliable timing alignment and communication stability are achieved.
Patent Information
- Application Number
- CN202580026493.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-03-21
- Filing Date
- 2025-05-07
- Publication Date
- 2026-11-10
AI Technical Summary
In non-terrestrial network (NTN) and air-to-ground (ATG) communications, timing advance management between terminals and base stations suffers from timing alignment inconsistencies and misinterpretations due to different subcarrier spacings (SCS), which are particularly severe under high frequency and high SCS conditions.
In a wireless communication system, offset threshold information is configured between the terminal and the base station based on the subcarrier spacing (SCS) of the active downlink (DL) bandwidth portion (BWP) to enable the management of advance timing (TA) reporting, including the interaction of radio resource control (RRC) messages and media access control (MAC) control unit (CE) between the base station and the terminal.
This ensures consistent interpretation of timing advance values, improves the reliability of uplink timing alignment, prevents misinterpretation, and enhances the stability and connection quality of the communication system.
Smart Images

Figure CN123077221A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the operation of terminals and base stations in wireless communication systems. In particular, this disclosure relates to methods and apparatus for providing timing advance management. For example, certain examples of this disclosure provide one or more techniques for timing advance management in non-terrestrial networks (NTN) and / or air-to-ground (ATG) networks with different subcarrier spacings (SCS) in 3GPP 5G New Radio (NR) networks. Background Technology
[0002] To meet the growing demand for wireless data communication services since the deployment of fourth-generation (4G) communication systems, efforts are underway to develop improved fifth-generation (5G) or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems".
[0003] Fifth-generation (5G) mobile communication technology defines a wide frequency band capable of enabling high transmission rates and new services, and it can be implemented not only in the "sub-6GHz" band, such as 3.5GHz, but also in the "above 6GHz" band, including 28GHz and 39GHz, known as millimeter waves. Furthermore, sixth-generation (6G) mobile communication technology (called "super 5G systems") has been considered for implementation in terahertz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates 50 times faster than 5G and ultra-low latency one-tenth that of 5G.
[0004] In the early stages of 5G mobile communication technology development, to support services and meet performance requirements for enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine-type communication (mMTC), the following technologies have been standardized: beamforming and massive multiple-input multiple-output (MIMO) for reducing radio wave path loss and increasing radio wave transmission distance in millimeter waves; support parameters for dynamic operation (e.g., operating multiple subcarrier spacings) for efficient utilization of millimeter wave resources and time slot formats; initial access technologies to support multi-beam transmission and wideband; definition and operation of bandwidth portions (BWP); new channel coding methods such as low-density parity-check (LDPC) codes for large data transmissions and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing for providing dedicated networks for specific services.
[0005] Regarding the services supported by 5G mobile communication technology, the industry is continuously discussing improvements and performance enhancements to the initial 5G mobile communication technology, and physical layer standardization has been completed for technologies such as: Vehicle-to-Everything (V2X) for assisting driving decisions and improving user convenience based on information sent by the vehicle about its location and status; New Radio Unlicensed Bands (NR-U) designed to comply with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Networks (NTNs) for direct satellite communication between UEs to ensure coverage in areas where communication with terrestrial networks is not possible; and positioning.
[0006] Furthermore, standardization of air interface architectures / protocols for technologies such as: Industrial Internet of Things (IIoT) for supporting new services through interoperability and integration with other industries; Integrated Access and Backhaul (IAB) for providing nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including conditional handover and Dual Active Protocol Stack (DAPS) handover; and two-step random access (RACH for NR) for simplifying the random access process. Simultaneously, standardization of system architectures / services for technologies such as: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Virtual Network Functions (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC) for receiving services based on UE location.
[0007] With the commercialization of 5G mobile communication systems, an exponential increase in connected devices will be added to communication networks, thus necessitating enhanced functionality and performance of 5G mobile communication systems and the integrated operation of connected devices. To this end, new research is underway on the following technologies: Extended Reality (XR) for efficient support of Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), etc.; 5G performance improvements and complexity reductions through the utilization of Artificial Intelligence (AI) and Machine Learning (ML); AI service support; Metaverse service support; and drone communication.
[0008] This development of 5G mobile communication systems will not only lay the foundation for the development of technologies such as: new waveforms for providing coverage in the terahertz band of 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive MIMO; metamaterial-based lenses and antennas for improving coverage of terahertz band signals; high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM); and reconfigurable smart surfaces (RIS), but will also lay the foundation for the development of technologies such as: full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies for system optimization from the design stage by leveraging satellites and artificial intelligence (AI) and internalizing end-to-end AI support capabilities; and next-generation distributed computing technologies for providing services at complexity levels that exceed the operational limits of UEs by utilizing ultra-high-performance communication and computing resources.
[0009] Non-terrestrial networks (NTN) and air-to-ground (ATG) communications are technologies that provide wireless connectivity between the ground and non-terrestrial platforms such as satellites or aircraft. In such environments, due to the vast variations in transmission distance, timing alignment, or timing advance (TA), is required between the terminal and the base station to maintain synchronized communication and ensure reliable uplink transmission. Summary of the Invention
[0010] Technical issues
[0011] This disclosure relates to the operation of terminals and base stations in wireless communication systems. In particular, this disclosure relates to methods and apparatus for providing timing advance management.
[0012] Therefore, one aspect of this disclosure is to provide a method and apparatus for managing timing advance (TA) on an NTN / ATG network with different subcarrier spacings (SCS).
[0013] Other aspects will be set forth in part in the description which follows, and in part will be apparent from the description or may be learned by practice of the presented embodiments.
[0014] The aspects of this disclosure at least address the aforementioned problems and / or disadvantages, and at least provide the advantages described below.
[0015] Solution to the problem
[0016] According to one aspect of this disclosure, a method is provided performed by a terminal supporting an air-to-ground (ATG) network in a wireless communication system. The method includes: receiving from a base station supporting the ATG network a Radio Resource Control (RRC) message including a configuration for Timing Advance (TA) reporting, wherein the configuration includes offset threshold information for TA reporting; determining, based on the offset threshold information, whether to trigger a TA report, wherein the offset threshold information is configured in symbols and based on the subcarrier spacing (SCS) of the active downlink (DL) bandwidth portion (BWP); and, if a TA report is triggered, sending to the base station a Media Access Control (MAC) Control Unit (CE) including information about the estimated TA.
[0017] According to one aspect of this disclosure, a method is provided performed by a base station supporting an air-to-ground (ATG) network in a wireless communication system. The method includes: generating offset threshold information for timing advance (TA) reporting, wherein the offset threshold information is configured in symbols and based on the subcarrier spacing (SCS) of the active downlink (DL) bandwidth portion (BWP); sending a radio resource control (RRC) message including a configuration for TA reporting to a terminal supporting the ATG network, wherein the configuration includes the offset threshold information; and receiving from the terminal a media access control (MAC) control unit (CE) including information about the TA, wherein the TA reporting is triggered based on the offset threshold information.
[0018] According to one aspect of this disclosure, a terminal supporting an air-to-ground (ATG) network in a wireless communication system is provided. The terminal includes: a transceiver; and a processor connected to the transceiver and configured to: receive from a base station supporting the ATG network a Radio Resource Control (RRC) message containing a configuration for Timing Advance (TA) reporting, wherein the configuration includes offset threshold information for TA reporting; determine, based on the offset threshold information, whether to trigger a TA report, wherein the offset threshold information is in symbol units and configured based on the subcarrier spacing (SCS) of the active downlink (DL) bandwidth portion (BWP); and, if a TA report is triggered, send to the base station a Media Access Control (MAC) Control Unit (CE) including information about the estimated TA.
[0019] According to one aspect of this disclosure, a base station supporting an air-to-ground (ATG) network is provided in a wireless communication system. The base station includes: a transceiver; and a processor connected to the transceiver and configured to: generate offset threshold information for advance timing (TA) reporting, wherein the offset threshold information is symbol-based and configured based on the subcarrier spacing (SCS) of the active downlink (DL) bandwidth portion (BWP); send a radio resource control (RRC) message including a configuration for TA reporting to a terminal supporting the ATG network, wherein the configuration includes the offset threshold information; and receive a media access control (MAC) control unit (CE) from the terminal including information about the TA, wherein the TA reporting is triggered based on the offset threshold information.
[0020] Beneficial effects
[0021] According to embodiments of this disclosure, by applying a timing advance offset threshold for the SCS based on the associated active DL / UL BWP, the terminal can ensure a consistent interpretation of the timing advance (TA) value, regardless of changes in the subcarrier spacing (SCS) between the bandwidth portions (BWPs).
[0022] Furthermore, according to embodiments of this disclosure, UEs and base stations in an NTN / ATG network can prevent misinterpretations of reported errors, thereby improving the reliability of uplink timing alignment.
[0023] The effects that can be obtained in this disclosure are not limited to those described above, and other effects not mentioned herein will be clearly understood by those skilled in the art from the following description. Attached Figure Description
[0024] The above and other aspects, features, and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which: Figure 1 An exemplary air-to-ground network is shown; Figure 2 The NTN version 17 architecture and the NTN version 19 regenerated architecture are shown; Figure 3 An exemplary timing advance MAC CE is shown; Figure 4 The issues associated with the report TAR MAC CE are shown; Figure 5 The scenario of switching BWP is shown; Figure 6 A method of a first network entity according to an example of this disclosure is shown; Figure 7 A method of a second network entity according to an example of this disclosure is shown; Figure 8 A method of a first network entity according to an example of this disclosure is shown; Figure 9 A method of a second network entity according to an example of this disclosure is shown; and Figure 10 A block diagram of an exemplary network entity that may be used in some examples of this disclosure is shown. Detailed Implementation
[0025] The following description, with reference to the accompanying drawings, is provided to aid in a full understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. It includes various specific details to aid understanding, but these are merely exemplary. Those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.
[0026] To achieve the objectives, technical solutions, and advantages of the embodiments of this disclosure, the technical solutions of the embodiments of this disclosure will be clearly and completely described in conjunction with the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. Other embodiments obtained by those skilled in the art based on the described embodiments of this disclosure without creative effort are all within the protection scope of this disclosure.
[0027] The terms and words used in the following description and claims are not limited to their dictionary meanings, but are used solely by the inventors to achieve a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description, which provides various embodiments of this disclosure, is for illustrative purposes only and is not intended to limit the disclosure as defined by the appended claims and their equivalents.
[0028] It should be understood that the singular forms “a,” “an,” and “the” include plural indicators unless the context clearly specifies otherwise. Thus, for example, referring to “the surface of a component” includes referring to one or more such surfaces.
[0029] Before proceeding with the following detailed description, it may be advantageous to define certain words and phrases used throughout this patent document. The term “connection” and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives include both direct and indirect communication. The terms “include” and “comprise,” and their derivatives imply non-restrictive inclusion. The term “or” is inclusive, meaning and / or. The phrase “associated with,” and its derivatives mean including, being included, interconnected with or connected to, containing, being included, coupled to or coupled to, connected to or connected to, communicating with, cooperating with, intertwined, juxtaposed, close to, bound to or bound to, having, possessing the properties of, having a relationship with, or having a relationship to, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware, or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, local or remote. The phrase "at least one," when used with a list of items, means that different combinations of one or more of the listed items can be used, and only one item from the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A; B; C; A and B; A and C; B and C; and A and B and C. Similarly, "at least one of A, B, or C" includes any of the following combinations: A; B; C; A and B; A and C; B and C; and A and B and C.
[0030] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and later rewrite it, such as rewritable optical discs or erasable storage devices.
[0031] The terminology used herein to describe embodiments of this application is not intended to limit and / or restrict the scope of this application. For example, unless otherwise defined, technical or scientific terms used in this disclosure should have the common meaning understood by one of ordinary skill in the art to which this application pertains.
[0032] It should be understood that the terms “first,” “second,” and similar terms used in this disclosure do not indicate any order, quantity, or importance, but are used only to distinguish different components. Unless otherwise clearly indicated in the context, similar terms such as “a,” “an,” “the,” etc., in the singular form do not indicate a limitation of quantity, but rather indicate the presence of at least one.
[0033] As used herein, any reference to “an example” or “example,” “an embodiment” or “an embodiment” means that a particular element, feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. The phrases “in one embodiment” or “in one instance” appearing in different places in the specification do not necessarily refer to the same embodiment.
[0034] As used in this article, “part of” means “at least some” of that thing, and therefore can mean smaller than or equal to the whole. Thus, “part of” includes the whole as a special case, that is, an example where the whole is a part of the thing.
[0035] To be further understood, words such as "including" or "contains" mean that the elements or objects preceding the word encompass the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Words such as "connected" or "interconnected" are not limited to physical or mechanical connections but can include direct or indirect electrical connections. "Up," "down," "left," and "right" are used only to indicate relative positional relationships. Therefore, when the absolute position of the described objects changes, the relative positional relationship may also change.
[0036] The various embodiments discussed below, used to describe the principles of this disclosure in this patent document, are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged wireless communication system. For example, although the following detailed description of embodiments of this disclosure focuses on LTE and 5G communication systems, those skilled in the art will understand that the main points of this disclosure can also be applied to other communication systems with similar technical backgrounds and channel configurations with minor modifications and without substantially departing from the scope of this disclosure. The solutions of the embodiments of this application can be applied to various communication systems.
[0037] For example, communication systems may include Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Universal Mobile Telecommunications System (UMTS), Global Microwave Access Interoperability (WiMAX), fifth-generation (5G) systems, or New Radio (NR) systems, etc. Furthermore, the solutions of the embodiments of this application can be applied to future-oriented communication technologies.
[0038] For example, a base station may be at least one of a gNode B, an eNode B (eNB), a Node B, a radio access unit, a base station controller, and a node on a network. A terminal may include a user equipment (UE), a mobile station (MS), a mobile phone, a smartphone, a computer capable of performing communication functions, or a multimedia system. In some embodiments of this disclosure, a downlink (DL) is a wireless transmission path through which signals are transmitted from the base station to the terminal, and an uplink (UL) is a wireless transmission path through which signals are transmitted from the terminal to the base station.
[0039] Accordingly, the various embodiments discussed below for describing the principles of this disclosure are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged wireless communication system. Although the detailed description of embodiments of this disclosure below is directed to 5G, those skilled in the art will understand that the main points of this disclosure can also be applied to other communication systems with similar technical backgrounds and channel configurations (e.g., Beyond 5G (B5G) or 6G) with minor modifications and without departing from the scope of this disclosure.
[0040] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that the same reference numerals in different drawings may be used to denote the same elements already described.
[0041] The following description, with reference to the accompanying drawings, is provided to aid in a full understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. This description includes various specific details to aid understanding, but should be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of the invention. Furthermore, for clarity and brevity, descriptions of well-known functions and structures may be omitted.
[0042] The terms and phrases used in the following description and claims are not limited to their dictionary meanings, but are used by the inventors only to achieve a clear and consistent understanding of this disclosure. Therefore, it will be clear to those skilled in the art that the following description, which provides various embodiments of this disclosure, is for illustrative purposes only and is not intended to limit the disclosure as defined by the appended claims and their equivalents.
[0043] It should be understood that the singular forms “a,” “an,” and “the” include plural indicators unless otherwise clearly indicated in the context. Thus, for example, referring to “the surface of a component” includes referring to one or more such surfaces.
[0044] The terms “comprising” or “may include” mean the presence of a corresponding disclosed function, operation, or component that can be used in various embodiments of this disclosure, and do not limit the presence of one or more additional functions, operations, or components. The terms “comprising” and / or “having” may be interpreted as indicating certain features, quantities, steps, operations, constituent elements, components, or combinations thereof, but are not to be interpreted as excluding the possibility of the presence of one or more other features, quantities, steps, operations, constituent elements, components, or combinations thereof.
[0045] The term "or" as used in the various embodiments of this disclosure includes any one of the listed terms or all combinations thereof. For example, "A or B" may include A, may include B, or may include both A and B.
[0046] Unless otherwise defined, all terms used in this disclosure (including technical or scientific terms) have the same meaning as understood by one of those skilled in the art, as set forth in this disclosure. Public terms as defined in dictionaries should be interpreted as having a meaning consistent with the context in the relevant technical field and should not be interpreted ideally or excessively unless expressly defined in this disclosure.
[0047] Certain examples of this disclosure provide one or more techniques for advance timing management. For example, certain examples of this disclosure provide one or more techniques for advance timing management of NTN and / or ATG with different SCS in 3GPP 5G NR networks. However, those skilled in the art will understand that this disclosure is not limited to these examples and can be applied to any suitable system or standard, such as one or more existing and / or future generation wireless communication systems or standards, including any existing or future versions of the same standard specification, such as 3GPP 5G, 5G Advanced, or 6th generation (6G).
[0048] The functions of the various network entities and other features disclosed herein can be applied to corresponding or equivalent entities or features in the same or any other suitable communication system or standard. Corresponding or equivalent entities or features can be considered as entities or features performing the same or similar roles, functions, or purposes within the network.
[0049] For example, the functions of base stations, etc. (e.g., eNB, gNB, NB, RAN node, access point, radio point, transmit / receive point, central unit, distributed unit, radio unit, remote radio unit, etc.) in the following examples can be applied to any other suitable type of entity performing RAN functions, and the functions of UEs, etc. (e.g., electronic devices, user equipment, mobile station, subscriber station, user terminal equipment, terminal, remote terminal, radio terminal, vehicle terminal, etc.) in the following examples can be applied to any other suitable type of device.
[0050] A specific network entity can be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, and / or a virtualization function exemplified on a suitable platform (e.g., on cloud infrastructure).
[0051] Those skilled in the art will understand that this disclosure is not limited to the specific examples disclosed herein. For example: The technologies disclosed in this article are not limited to 3GPP 5G.
[0052] One or more entities in the examples disclosed herein can be replaced by one or more alternative entities that perform equivalent or corresponding functions, procedures, or operations.
[0053] One or more messages in the examples disclosed herein may be replaced by one or more alternative messages, signals, or other types of information carriers that convey equivalent or corresponding information.
[0054] One or more other elements or entities may be added to the examples disclosed herein.
[0055] In some examples, one or more non-essential elements or entities may be omitted.
[0056] In one example, the functionality, process, or operation of a particular entity can be divided among two or more separate entities in an alternative example.
[0057] In one example, the functionality, process, or operation of two or more separate entities can be performed by a single entity in an alternative example.
[0058] In one example, the information carried by a particular message can be carried by two or more separate messages in an alternative example.
[0059] In one example, information carried by two or more separate messages can be carried by a single message as in an alternative example.
[0060] In alternative examples, the order of operations performed and / or the order of messages sent can be modified, if possible.
[0061] Some examples of this disclosure may be provided in the form of an apparatus / device / network entity configured to perform one or more defined network functions, and / or methods thereof. Some examples of this disclosure may also be provided in the form of a system (e.g., a network or wireless communication system) including one or more such apparatus / device / network entities, and / or methods thereof.
[0062] The accompanying drawings and various embodiments used to illustrate the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.
[0063] Overview of air-to-ground networks
[0064] Air-to-ground (ATG or A2G) networks are cellular networks that provide connectivity in the air via ground-based base stations (see [link]). Figure 1 It differs from non-terrestrial networks because the access link is from the ground to the user equipment (UE) in the sky, while in NTN, the access link is from space / sky to the ground, such as... Figure 2 As shown.
[0065] A primary use case for ATG networks is providing backhaul connectivity to access points in aircraft.
[0066] A research project was initiated in RAN4 version 18 [RP-221369] to define the requirements for coexistence between ATG and International Mobile Telecommunications (IMT) terrestrial networks, and also to further define the Radio Resource Management (RRM) performance requirements for ATG UEs, the demodulation performance requirements for ATG base stations (BS) / UEs, and the test procedures for ATG BS conformance testing.
[0067] Air-to-ground networks are similar to non-terrestrial networks in that cells can be very large, synchronization will have to be different, and network elements can move very quickly.
[0068] [RP-221369] describes some characteristics of ATG networks from a radio frequency (RF) perspective: 1. Extremely large distances between sites and wide coverage area 2. Utilizing non-separated frequencies to deploy both ATG and terrestrial networks. 3. Much more powerful airborne ATG terminal capacity
[0069] Non-terrestrial network overview
[0070] NR NTN (NR_NTN_solutions-Core) [RP-211557] is a 3GPP working project in 3GPP Release 17, used to define solutions that can support New Radio (NR) and NG-RAN for non-terrestrial networks. It proposes a transparent payload solution for both geostationary and non-geostationary network scenarios, where the UE has Global Navigation Satellite System (GNSS) capability and the satellite beam can be either geostationary or geomobile.
[0071] The Internet of Things (IoT) NTN is a 3GPP research and work item in Release 17, designed to provide non-terrestrial network access for IoT devices (NB-IoT and LTE Machine-Type Communications (LTE-M) / Enhanced Machine-Type Communications (eMTC)) on the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) [RP-202689]. NR NTN is also a work item in Release 17, specifying applicability to allow NR to function on NTN [RP-211557]. Non-terrestrial network access can be provided via satellites in Low Earth Orbit (LEO), Medium Earth Orbit (MEO), and Geostationary Orbit (GEO), as well as via High Altitude Platform Systems (HAPS).
[0072] Following the work item in version 17, there are work items in version 18 for enhanced NR NTN [RP-220953] and IoTNTN [RP-220979].
[0073] NR NTN Phase 3 [RP-234078] is a 3GPP work item in 3GPP Release 19, designed to enhance the scope of NR NTN enhancements. - Downlink coverage enhancement - Enhanced uplink capacity and throughput through the use of orthogonal overlay codes - Broadcasting multicast and broadcast services (MBS) via NTN -Introducing regenerative payload - Redcap and NTN enhancements -Ground E-UTRAN to NR NTN Mobility
[0074] Frequency band overview for NR NTN
[0075] For version 17, RAN4 introduced basic support for NTN in lower frequency bands. These are bands n254, n255, and n256 with the following characteristics: Frequency band n254 in Frequency Division Duplex (FDD) mode: Uplink (UL) operating frequency band: 1610-1626.5MHz Downlink (DL) operating frequency band: 2483.5-2500MHz Frequency band n255 in FDD mode: UL operating frequency band: 1626.5-1660.5MHz DL operating frequency band: 1525-1559MHz Frequency band n256 in FDD mode: UL operating frequency band 1980-2010MHz DL operating frequency band 2170-2200MHz For version 18, RAN4 has introduced support for higher frequency NTNs. RAN4 defines the frequency range 1 (FR2)-NTN as the frequency between 17.3 GHz and 30 GHz [38.101-5, V18.5.0], while the frequency range 1 (FR1)-NTN remains in the lower frequency band of 410 MHz to 7.125 GHz.
[0076] RAN4 introduces the following set of frequency bands for FR2-NTN [38.101-5, V18.5.0]: Frequency band n510 in FDD mode: UL operating frequency band: 27500-30000MHz DL operating frequency band: 17300-20200MHz Frequency band n511 in FDD mode: UL operating frequency band: 28350-30000MHz DL operating frequency band: 17300-20200MHz Frequency band n512 in FDD mode: UL operating frequency band: 27500-28350MHz DL operating frequency band: 17300-20200MHz For these frequency bands, SCSs at 60kHz and 120kHz are introduced [3GPP TS 38.101-5, V18.5.0]:
[0077] NR Parameter Set Overview
[0078] Because NR is designed to support a wide range of frequencies, the subcarrier spacing can be different. This differs from LTE, where the subcarrier spacing is designed to be 15 kHz. The supported subcarrier spacings are numbered from 0 to 6 with values of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, and 960 kHz.
[0079] Overview of Timing Advance (TA) in NR and LTE
[0080] In LTE, the complete timing advance of the UE T TA Defined as:
[0081] The components are: =Basic time unit 1 / (15000 × 2048) = 1 / 30720000 It is specific to NTN. In NR, T TA It is the complete and absolute timing advance of the UE, which is defined as:
[0082] The components are: The basic time unit for NR is 1 / (480 × 10). 3 (× 4096) = 1 / 1966080000 The timing advance is notified via MAC signal, and it is calculated as follows: ○ This is when received in the random access response How to calculate the timing advance ○ When received in the advance media access control (MAC) control unit (CE) It is calculated in time.
[0083] μ is the subcarrier spacing configuration, which can take values [0, 1, 2, 3, 4, 5, 6] kHz corresponding to subcarrier spacing [15, 30, 60, 120, 240, 480, 960]. Generally, the higher the frequency, the higher the subcarrier spacing.
[0084] It is specific to NTN.
[0085] As can be seen from the above, in NR, The granularity of the value changes with the subcarrier spacing. For example, for SCS=15kHz, the value that the timing advance change for the UE application is [value]. =[...-4096, -3072, -2048, -1024, 0, 1024, 2048, ...]. For SCS = 60kHz, the UE applied value =[...,-1024,-768,-512,-256,0,256,512,768,1024,...].
[0086] The difference between LTE and NR is that in LTE, the SCS is always the same, and the basic time unit is much smaller in LTE.
[0087] Overview of Timely Advance Reporting
[0088] In NR Release 15 and LTE, timing advance is signaled by the network in a Timing Advance Command (TAC). Once received, the UE applies the TA; therefore, timing is always entirely under the control of the network.
[0089] Timing advance reporting is a feature introduced for NR NTN in version 17. This is because in NR NTN, the UE primarily performs self-pre-compensation for timing advance. In other words, the UE autonomously estimates and applies timing advance. Therefore, to inform the network what timing advance the UE has applied, the UE can be configured to report its timing advance under specific conditions.
[0090] These conditions are: - Once an instruction is received from the upper layer, a report is triggered. This can occur after a set of Radio Resource Control (RRC) procedures, such as RRC establishment, handover (with synchronized RRC reconfiguration), RRC reconstruction, and RRC connection restoration.
[0091] - If the change between the current advance timer value and the last reported advance timer (TA) is greater than the configured threshold (offsetThresholdTA). This will also be triggered when offsetThresholdTA is configured and no advance timer report has been sent yet.
[0092] TA is reported via the Timely Advance Reporting (TAR) Media Access Control (MAC) Control Unit (CE), which can... Figure 3 As can be seen from this, the timing advance field in NR NTN is the number of time slots and can span the entire value range, i.e., all 14 bits. The timing advance field in ATG is the number of symbols and has a value range of 1 to 56.
[0093] In 3GPP Release 18, support for timed advance MAC CE was also agreed upon for ATG.
[0094] Bandwidth adaptation overview
[0095] Bandwidth adaptation is a feature that allows for flexible bandwidth usage for a specific UE. This feature allows the UE's receive and transmit bandwidth to be less than the cell's full bandwidth and to be dynamically adjusted. This allows for power savings for the UE because the bandwidth can be reduced based on service profiles. This feature is particularly important in cells with large bandwidth.
[0096] To address this, a Bandwidth Part (BWP) is introduced, allowing the network and UE to switch over for different events. BWPs are defined for both uplink and downlink. The initial BWP is the broadcast bandwidth portion used by the UE for initial access and always contains the most basic broadcast signaling. When the UE is in an RRC connection (RRC_CONNECTED), a non-initial BWP is specifically configured for the UE.
[0097] BWP handover is performed by both the network and the UE. The network can switch from the initial BWP to a non-initial BWP, and also switch between non-initial BWPs. This is accomplished via downlink control information (DCI) or RRC signaling. The UE can switch between BWPs based on certain conditions, such as the expiration of an inactivity timer or the initiation of random access. The initiation of random access is typically triggered by a set of various faults.
[0098] The above information is presented as background information only to aid in understanding this disclosure. There is no determination or assertion as to whether any of the above content can be used as prior art with respect to this disclosure.
[0099] Timely advance reporting is a key feature in ATG and NTN.
[0100] In 3GPP Release 17, the only subcarrier spacing agreed upon for introduction is 15kHz; therefore, all features are considered only for the 15kHz SCS. An example of this is as follows:
[0101] When NTN is extended to higher frequencies or other use cases, problems will arise because the subcarrier spacing will similarly need to increase with the higher frequency. In these cases, it may be necessary to redesign the signaling and conditions to accommodate the different subcarrier spacing.
[0102] In ATG, the "Timing Advance" field in the Timing Advance Report (TAR) MAC CE is defined as the number of symbols. However, the symbol duration depends on the SCS in which the symbols are defined. Therefore, it is stipulated that the number of symbols transmitted is based on the SCS configured for the UE.
[0103] However, as a key enhancement to NR in Release 15, a bandwidth portion was introduced. The bandwidth portion allows the UE to be configured with a subset of cell frequencies that can be dynamically switched based on service. Bandwidth portions can have different bandwidths and different physical layer configurations, and can also have different subcarrier spacings. This means that an NR UE can be configured with multiple potentially different subcarrier spacings depending on the bandwidth portion the UE is currently in. Therefore, if the subcarrier spacing on which the UE report is based is unclear, there can be confusion regarding how to report TAR MAC CE. As a result, the UE might report a value that, using the current method, indicates an actual timing advance of two or half times, which can confuse the network and trigger network actions that, at best, are detrimental and at worst, could lead to connection loss. This can be... Figure 4 This can be seen from the data. For example, if a larger subcarrier spacing is introduced to support higher frequency operation, there may be even greater problems.
[0104] Due to the assumption of a 15kHz SCS, this type of problem exists more frequently in timing advance management of ATG and NTN. These problems become more severe with higher frequencies and higher subcarrier spacing, and in version 18, a higher frequency band for NR NTN operation, called FR2-NTN, was introduced.
[0105] Certain examples of this disclosure provide a UE, a base station (e.g., eNB, gNB), and / or other network entities (e.g., Access and Mobility Management Function (AMF), SMF) configured to perform methods according to any example, aspect, embodiment, and / or claim disclosed herein.
[0106] Certain examples of this disclosure provide a network (or wireless communication system) including a UE, a base station (e.g., eNB, gNB), and / or other network entities (e.g., AMF, SMF) according to any example, aspect, embodiment, and / or claim disclosed herein.
[0107] Some examples of this disclosure provide computer programs that include instructions that, when executed by a computer or processor, cause the computer or processor to perform a method according to any of the examples, aspects, embodiments, and / or claims disclosed herein.
[0108] Certain examples of this disclosure provide a computer or processor-readable data carrier on which a computer program pursuant to any example, aspect, embodiment, and / or claim disclosed herein is stored.
[0109] Various examples of this disclosure can now be described in more detail.
[0110] Some examples of this disclosure provide one or more techniques for managing timing advance based on different and varying subcarrier spacings in air-to-ground and / or non-terrestrial networks.
[0111] This disclosure refers to gNB (5G NR), but those skilled in the art will understand that the technology described herein can also be used with eNB, NG-RAN (5G NR), and / or 6G RAN. This technology can also be applied to eMTC / LTE-M UE, 5G NR UE, and / or E-UTRAN UE.
[0112] In this disclosure, references to a BWP can include BWPs of PCell, PSCell, SpCell, and / or SCell, depending on the configuration, such as if dual connectivity or carrier aggregation is used. Similarly, references to an SCS of a BWP can include the SCS of a BWP of PCell, PSCell, SpCell, or SCell, depending on the configuration.
[0113] Report TAR MAC CE
[0114] Maintaining timing in non-terrestrial or air-to-ground networks is an important aspect of the UE reporting its estimated timing advance. In both cases, subcarrier spacing is used, and assumptions are made about the subcarrier spacing. For example, the UE calculates the reported timing advance value based on the SCS, and the triggering of TAR MAC CE is based on the estimated timing advance, where the threshold is based on a time slot assuming a certain SCS.
[0115] TAR MAC CE content
[0116] In some examples, when the UE reports the timing advance field, the timing advance field is based on the SCS of the initial BWP. This could be, for example, the initial DL or UL BWP. This could be for the PCell or SpCell (in a dual-connectivity setup) or SCell. This approach is advantageous because the reporting of TAR MAC CE content remains the same regardless of the SCS, and the SCS can be switched when the network switches BWPs. For example, if a fault occurs and TAR MAC CE is triggered, the network can explicitly use the SCS for reporting the timing advance field. This can be seen in Example 1a of the specification below.
[0117] This means that for NTN, the number of slots can be based on the SCS of the initial DL or UL BWP, and for ATG, the number of symbols can be based on the SCS of the initial DL or UL BWP.
[0118] In some examples, when the UE reports a timing advance field, the timing advance field is based on the SCS of the active DL or UL BWP. This can similarly be the DL or UL BWP of the PCell or SpCell (in a dual connectivity setup) or SCell (in a carrier aggregation setup). An example of this can be seen in Example 1b of the specification below.
[0119] For this method, the UE may need to report based on the SCS of the BWP that triggered the TAR MAC CE. This could mean that if a TAR MAC CE is triggered on a BWP where SCS = X, and then a BWP handover occurs where SCS = Y, the UE can continue reporting based on SCS = X. Alternatively, the UE can report the timing advance field based on the current SCS of the BWP. This could mean that if a TAR MAC CE is triggered in a BWP with SCS = X, and then a BWP handover occurs where SCS = Y, the UE can report the TAR MAC CE with SCS = Y.
[0120] In some examples, the UE reports timing advance based on the minimum SCS configured for the UE in the cell. In other words, the UE uses the minimum SCS among the configured BWPs.
[0121] In some examples, when a UE reports a timing advance field, the timing advance field is based on the SCS of the minimum SCS configured in the cell. This means that the UE uses the minimum SCS among all the SCSs configured for it.
[0122] For ATG, the UE can report based on a subcarrier spacing of 15 kHz, even though the configured SCS is 30 kHz or higher.
[0123] In some examples, the above depends on the frequency range of the UE, i.e., FR1, FR2, FR2-1, or FR-2. This may also include fixed SCS values for different frequency ranges.
[0124] Here is an example: - For FR2, the UE reports the timing advance field based on the SCS of the initial BWP, while for FR1, the UE reports the timing advance field based on the 15kHz subcarrier spacing.
[0125] - For FR2, the UE reports the timing advance field based on an SCS of 120kHz, while for FR1, the UE reports the timing advance field based on an SCS of 15kHz. 60kHz is the minimum SCS for FR2 frequencies, but any other value can be applied.
[0126] In some examples, the above method is applied if the SCS is greater than a specific threshold. For example, if the SCS is greater than 30 kHz.
[0127] Here is an example: - For SCS of a cell or BWP greater than 30kHz, the UE reports the timing advance field based on the initial BWP SCS, while if the SCS is less than or equal to 30kHz, the UE reports the timing advance field based on the 15kHz subcarrier spacing.
[0128] In some examples, the MAC CE timed advance report includes a field indicating the SCS that the UE is applying.
[0129] The above can be applied to one or both of ATG and NTN. For example, it can be advantageously applied to NTN above 10 GHz. It can also be applied differently to ATG or NTN.
[0130] In some examples, a new MAC CE is introduced to report timing advance for a higher SCS, or a new MAC CE is introduced to report timing advance for an even higher frequency. For example, if the SCS is larger for a higher SCS or for a higher frequency. This new MAC CE may be called an extended timing advance MAC CE (or any other suitable name), and it may contain a larger field for the timing advance field. Whether this MAC CE is used can be configurable, or it may be used only for higher frequencies, such as FR2-NTN. It is also possible that the number of slots or symbols reported by the UE is configurable.
[0131] The extended timing advance MAC CE can similarly make its timing advance field dependent on the SCS based on the options mentioned above.
[0132] Trigger TAR MAC CE
[0133] In some examples, the timing advance threshold (or the configured timing advance offset threshold) is interpreted as being based on the initial DL or UL BWP. This can be defined, for example, as the initial DL or UL BWP of the PCell, or the initial DL or UL BWP of the SpCell, or the initial DL or UL BWP of the SCell. This could mean, for example, that the UE operates on a specific BWP of a certain SCS, but the TAR MAC CE is triggered based on the SCS with the initial BWP.
[0134] In some examples, the timing advance threshold (or the configured timing advance offset threshold) is interpreted as based on the DL or UL active BWP. This could be the initial DL or UL BWP of the PCell, SpCell, or SCell. This may mean that the absolute timing advance threshold changes with BWP switching if the SCS of the BWP is different.
[0135] The advantage of a fixed SCS (Self-Controlled Class Components) approach, which does not consider the specific SCS of a particular BWP, is that other methods might encounter problems when the BWP is switched. Figure 5 This issue can be observed. This is because if the SCS changes with BWP handover, the threshold or threshold offset, which is actually expressed as absolute timing advance, may change as the time slot becomes shorter in absolute time. This is because the absolutely estimated timing advance is constant, depending on the distance between the UE and the satellite, and therefore may not change with the changing SCS. This leads to unexpected and unnecessary TAR MAC CE reports.
[0136] In some examples, the timing advance threshold (or the configured timing advance offset threshold) is interpreted as the minimum configured SCS of the UE in the cell.
[0137] In some examples, the timing advance threshold or timing advance threshold offset is based on when the configuration is received. For example, if the configuration is received when the UE is configured with a specific SCS on a specific BWP, the UE can always maintain the threshold based on that specific SCS.
[0138] In some examples, the timing advance threshold or timing advance threshold offset is interpreted based on the cell frequency using fixed values (e.g., 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, 480 kHz, 960 kHz). This can be the same value in all cases, or it can depend on the frequency range. For example: - For FR1, the threshold is interpreted as using a 15kHz SCS. - For FR2, the threshold is interpreted as using an SCS of 120kHz. - For FR2-1, the threshold is interpreted as using an SCS of 120 kHz. - For FR2-1, the threshold is interpreted as using an SCS of 240kHz. In another example, the technique used to interpret the SCS may differ for different frequency ranges, such as a mixture of the aforementioned techniques depending on the frequency range. Some examples may be as follows: - For FR1, the threshold is interpreted as using a 15kHz SCS, while for FR2, the initial DL or UL BWP SCS is used.
[0139] - For FR1, the threshold is interpreted as using the initial BWP, while for FR2, the threshold is interpreted as using the 60kHz SCS.
[0140] Depending on whether the UE is in FR1 / FR2 or whether the SCS is above a certain value, an extended timed advance MAC CE can be triggered (as described above under the heading "Content of TAR MAC CE"). For example, for FR1, a (non-extended) TAR MAC CE is reported, while in FR2, an extended TAR MAC CE is reported. Similarly, whether the UE reports an extended TAR MAC CE can be configured. This could, for example, be a flag indicating whether the UE should report using an extended TAR MAC CE.
[0141] In some examples, a separate threshold for FR2 is introduced. For instance, this threshold may have one or more of the following characteristics: - Whether the threshold is expressed in absolute time (i.e., in seconds, milliseconds, or microseconds), or whether the threshold is defined as a time slot or symbol, is configurable.
[0142] In some examples, the TAR configuration is configured based on the BWP, and it is assumed that the triggered SCS uses the SCS of a specific bandwidth portion. This means that there may be multiple TAR configurations, each for the BWP of each configuration. This allows the threshold to vary depending on the SCS of each BWP.
[0143] Other examples
[0144] In some examples, restrictions on the SCS can be introduced. In some examples, the SCS of different BWPs in an ATG or NTN cell may need to be the same. This means that all SCS configured for different BWPs are required to be exactly the same. This can be, for example, specific to an ATG or NTN cell, specific to an FR1 ATG or FR1 NTN cell, or specific to an FR2 ATG or FR2 NTN cell. An example of this can be seen in Example 3 of the specification below. For example, this restriction may be imposed on FR1, while this restriction may not exist for FR2, possibly because a more complex technique was used in the previous sections.
[0145] In practice, this may mean that the network must ensure that the SCS configured for all BWPs is identical, and that the SCS is consistent with the SCS signaled in the Master Information Block (MIB). The SCS of any non-initial (DL or UL) BWP configuration may need to be the same as the initial (DL or UL) BWP. The SCS for any Synchronization Signal Block (SSB) of the cell may also need to be identical.
[0146] These restrictions can be applied to a single serving cell or a group of cells.
[0147] In some examples, certain fields in NTN or ATG that depend on SCS can be configured based on BWP: - Timing advance reporting can be configured based on the BWP. This addresses the question of which SCS to utilize when the UE can use an SCS associated with a specific BWP. This also allows for flexibility when the network can configure different offsetThresholds for different BWPs (which could result in the same absolute timing threshold or different absolute timing threshold offsets depending on configuration and usage).
[0148] - Configure the Koffset based on the BWP. This allows for greater flexibility, similar to configuring a timed advance reporting configuration. This can be signaled in, for example, the BWP configuration, and / or as a list of BWPs in the System Information Block (SIB). In some examples, the Koffset signaled in SIB19 (for NR NTN) or SIB22 (for ATG) can only be used for the initial BWP, while the Koffset is configured for non-initial BWPs.
[0149] The following are examples of how standards can be modified to incorporate one or more of the technologies described in this article.
[0150] Standard Example
[0151] Example 1a
[0152] 3GPP TS 38.321 V18.1.0 Example
[0153] 6.1.3.56 Scheduled advance report to MAC CE
[0154] The MAC CE (Advance Message Certificate) is identified by the MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of two octets, defined as follows (…). Figure 6 .1.3.56-1): -R: Reserved bit, set to 0; - Timing Advance: In FR1, except for ATG, the timing advance field indicates the minimum integer number of time slots that are greater than or equal to the timing advance value when using a subcarrier spacing of 15 kHz (see TS 38.211 [8], Section 4.3.1).
[0155] For ATG in FR1, the timing advance field represents the minimum integer number of symbols greater than or equal to the timing advance value (see TS 38.211 [8], Section 4.3.1). The symbol duration is based on the current configuration assigned to the UE. Initial BWP Subcarrier spacing. In this version of the specification, only 15 kHz and 30 kHz SCS are used, and only values between 1 and 56 are used.
[0156] The length of this field is 14 bits.
[0157] 3GPP TS 38.321 V18.1.0 Example
[0158] Example 1b
[0159] 3GPP TS 38.321 V18.1.0 Example
[0160] 6.1.3.56 Scheduled advance report to MAC CE
[0161] The MAC CE (Advance Message Certificate) is identified by the MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of two octets, defined as follows (…). Figure 6 .1.3.56-1): -R: Reserved bit, set to 0; - Timing Advance: In FR1, except for ATG, the timing advance field indicates the minimum integer number of time slots that are greater than or equal to the timing advance value when using a subcarrier spacing of 15 kHz (see TS 38.211 [8], Section 4.3.1).
[0162] For ATG in FR1, the timing advance field represents the minimum integer number of symbols greater than or equal to the timing advance value (see TS 38.211 [8], Section 4.3.1). The symbol duration is based on the current configuration assigned to the UE. DL activity BWP Subcarrier spacing. In this version of the specification, only 15 kHz and 30 kHz SCS are used, and only values between 1 and 56 are used.
[0163] The length of this field is 14 bits.
[0164] 3GPP TS 38.321 V18.1.0 Example
[0165] Example 1c
[0166] 3GPP TS 38.321 V18.1.0 Example
[0167] 6.1.3.56 Scheduled advance report to MAC CE
[0168] The MAC CE (Advance Message Certificate) is identified by the MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of two octets, defined as follows (…). Figure 6 .1.3.56-1): -R: Reserved bit, set to 0; - Timing Advance: In FR1, except for ATG, the Timing Advance field indicates the use of 15 kHz. Initial BWP When the subcarrier spacing is greater than or equal to the minimum integer number of time slots (see TS 38.211 [8], Section 4.3.1).
[0169] For the ATG in FR1, the timing advance field represents the minimum integer number of symbols greater than or equal to the timing advance value (see TS 38.211 [8], Section 4.3.1). The symbol duration is based on the subcarrier spacing currently configured for the UE. In this version of the specification, only 15 kHz and 30 kHz SCSs are used, and only values between 1 and 56 are used.
[0170] The length of this field is 14 bits.
[0171] 3GPP TS 38.321 V18.1.0 Example
[0172] Example 1d
[0173] 3GPP TS 38.321 V18.1.0 Example
[0174] 6.1.3.56 Scheduled advance report to MAC CE
[0175] The MAC CE (Advance Message Certificate) is identified by the MAC subheader with LCID as specified in Table 6.2.1-2. It has a fixed size and consists of two octets, defined as follows (…). Figure 6 .1.3.56-1): -R: Reserved bit, set to 0; - Timing Advance: In FR1, except for ATG, the timing advance field indicates the minimum integer number of time slots that are greater than or equal to the timing advance value when using a subcarrier spacing of 15 kHz (see TS 38.211 [8], Section 4.3.1).
[0176] In FR2 for NTN, the timing advance field indicates that when using the subcarrier spacing of the initial BWP, it is greater than or equal to... The minimum integer number of time slots for timing advance values (see TS 38.211 [8], Section 4.3.1).
[0177] For the ATG in FR1, the timing advance field represents the minimum integer number of symbols greater than or equal to the timing advance value (see TS 38.211 [8], Section 4.3.1). The symbol duration is based on the subcarrier spacing currently configured for the UE. In this version of the specification, only 15 kHz and 30 kHz SCSs are used, and only values between 1 and 56 are used.
[0178] The length of this field is 14 bits.
[0179] 3GPP TS 38.321 V18.1.0 Example
[0180] Example 2
[0181] 3GPP TS 38.331 V18.1.0 Example
[0182] - TAR-Config
[0183] IE TAR-Config Used to configure timed advance reporting in non-terrestrial networks and ATG networks.
[0184] TAR-Config Information elements
[0185] 3GPP TS 38.331 V18.1.0 Example
[0186] Example 3
[0187] 3GPP TS 38.331 V18.1.0 Example
[0188] -BWP
[0189] The IE BWP is used to configure general parameters for the bandwidth portion, as defined in Section 4.5 of TS 38.211
[16] and Section 12 of TS38.213
[13] .
[0190] For each serving cell, the network configures at least one initial downlink bandwidth portion, and one (if the serving cell has an uplink) or two (if a supplementary uplink (SUL)) initial uplink bandwidth portions. Additionally, the network may configure additional uplink and downlink bandwidth portions for the serving cell.
[0191] The uplink and downlink bandwidth configurations are divided into common parameters and dedicated parameters.
[0192] BWP Information Elements
[0193] 3GPP TS 38.331 V18.1.0 Example
[0194] Figure 6 A method for a first network entity (e.g., a base station) according to an example of this disclosure is illustrated. In step 602, the method includes sending a timing advance reporting configuration to a second network entity (e.g., a UE), the timing advance reporting configuration including information indicating a timing advance offset threshold for triggering a timing advance report. The timing advance offset threshold may be based on an active downlink bandwidth portion.
[0195] Figure 7 A method for a second network entity (e.g., a UE) according to an example of this disclosure is illustrated. In step 702, the method includes receiving a timing advance reporting configuration from a first network entity (e.g., a base station), the timing advance reporting configuration including information indicating a timing advance offset threshold for triggering a timing advance report. The timing advance offset threshold may be based on an active downlink bandwidth portion.
[0196] Figure 8 A method for a first network entity (e.g., a base station) according to an example of this disclosure is illustrated. In step 802, the method includes receiving a timing advance report from a second network entity (e.g., a UE), the timing advance report including information indicating timing advance. The timing advance may be based on an active downlink bandwidth portion.
[0197] Figure 9A method for a second network entity (e.g., a UE) according to an example of this disclosure is illustrated. In step 902, the method includes sending a timing advance report to a first network entity (e.g., a base station), the timing advance report including information indicating timing advance. The timing advance may be based on an active downlink bandwidth portion.
[0198] Figure 10 This is a block diagram of exemplary network entities that can be used in the examples of this disclosure. For example, Figures 1-9 The examples of UEs, base stations (e.g., eNB, gNB) and / or other network entities (e.g., AMF, SMF, NWDAF) may include Figure 10 The entity. Those skilled in the art will understand that a network entity can be implemented as, for example, a network element on dedicated hardware, a software instance running on dedicated hardware, and / or a virtualization function exemplified on a suitable platform (e.g., on cloud infrastructure).
[0199] Entity 1000 includes a processor (or controller) 1001, a transmitter 1003, and a receiver 1005. Receiver 1005 is configured to receive one or more messages from one or more other network entities, as described above. Transmitter 1003 is configured to transmit one or more messages to one or more other network entities, as described above. Processor 1001 is configured to perform one or more operations, for example, according to the operations described above.
[0200] The techniques described herein can be implemented using any suitably configured apparatus and / or system. Such apparatus and / or system can be configured to perform methods according to any aspect, embodiment, example, or claim disclosed herein. Such apparatus may include one or more elements, such as receivers, transmitters, transceivers, processors, controllers, modules, units, etc., each element configured to perform one or more corresponding process, operational, and / or method steps for implementing the techniques described herein. For example, operation / function of X can be performed by a module (or X module) configured to perform X. One or more elements can be implemented in hardware, software, or any combination of hardware and software.
[0201] It is understood that the examples of this disclosure can be implemented in the form of hardware, software, or any combination of hardware and software. Any such software can be stored in the form of volatile or non-volatile memory, such as a storage device like ROM, whether erasable or rewritable; or in the form of memory, such as, for example, RAM, memory chips, devices, or integrated circuits; or stored on optical or magnetically readable media, such as, for example, CDs, DVDs, disks, or magnetic tapes.
[0202] It is understood that storage devices and storage media are embodiments of machine-readable storage media adapted to store one or more programs including instructions that, when executed, implement one example of this disclosure. Thus, some examples provide a program comprising code for implementing a method, apparatus, or system according to any example, embodiment, aspect, and / or claim disclosed herein, and / or a machine-readable storage medium for storing such a program. Furthermore, such a program can be electrically transmitted via any medium, such as communication signals carried over a wired or wireless connection.
[0203] Although this disclosure has been shown and described with reference to certain examples, those skilled in the art will understand that various changes in form and detail may be made therein without departing from the scope of this disclosure as defined by the appended claims.
[0204] In a first example, a method is provided for a first network entity (e.g., a base station) in a network, the method comprising: sending a timing advance report configuration to a second network entity (e.g., a UE), the timing advance report configuration including information indicating a timing advance offset threshold for triggering a timing advance report; wherein the timing advance offset threshold is based on an active downlink bandwidth portion.
[0205] In the second example, the method of the first example is provided, wherein the active downlink bandwidth portion is the active downlink bandwidth portion when the second network entity receives the timed advance report configuration.
[0206] In the third example, the method of the first or second example is provided, wherein the timing advance offset threshold is based on the subcarrier spacing of the active downlink bandwidth portion.
[0207] In the fourth example, the method of the third example is provided, where the timing advance offset threshold is based on the symbol duration of the subcarrier interval of the active downlink bandwidth portion.
[0208] In the fifth example, the method of the third or fourth example is provided, wherein the subcarrier spacing is the subcarrier spacing of the downlink bandwidth portion of the activity when the second network entity receives the timing advance report configuration.
[0209] In the sixth example, a method according to any one of the first to fifth examples is provided, wherein if the downlink bandwidth portion of the activity changes, the timing advance offset threshold does not change.
[0210] In the seventh example, a method according to any one of the first to sixth examples is provided, further comprising: receiving a timing advance report from a second network entity, the timing advance report including information indicating timing advance; wherein the timing advance is based on the downlink bandwidth portion of the activity.
[0211] In the eighth example, a method is provided for a second network entity (e.g., a UE) in a network, the method comprising: receiving a timing advance reporting configuration from a first network entity (e.g., a base station), the timing advance reporting configuration including information indicating a timing advance offset threshold for triggering a timing advance report; wherein the timing advance offset threshold is based on an active downlink bandwidth portion.
[0212] In the ninth example, the method of the eighth example is provided, wherein the active downlink bandwidth portion is the active downlink bandwidth portion when the second network entity receives the timed advance report configuration.
[0213] In the tenth example, the method of the eighth or ninth example is provided, wherein the timing advance offset threshold is based on the subcarrier spacing of the active downlink bandwidth portion.
[0214] In the eleventh example, the method of the tenth example is provided, wherein the timing advance offset threshold is based on the symbol duration of the subcarrier interval of the active downlink bandwidth portion.
[0215] In the twelfth example, the method of the tenth or eleventh example is provided, wherein the subcarrier spacing is the subcarrier spacing of the downlink bandwidth portion of the activity when the second network entity receives the timing advance report configuration.
[0216] In the thirteenth example, a method according to any one of the eighth to twelfth examples is provided, wherein, in response to a partial change in the downlink bandwidth of the activity, the second network entity is configured to maintain a timing advance offset threshold received from the first network entity.
[0217] In the fourteenth example, a method according to any one of the eighth to thirteenth examples is provided, further comprising: sending a timing advance report to a first network entity, the timing advance report including information indicating timing advance; wherein the timing advance is based on the downlink bandwidth portion of the activity.
[0218] In the fifteenth example, a method is provided for a first network entity (e.g., a base station) in a network, the method comprising: receiving a timing advance report from a second network entity (e.g., a UE), the timing advance report including information indicating timing advance; wherein the timing advance is based on an active downlink bandwidth portion.
[0219] In the sixteenth example, a method is provided for a second network entity (e.g., a UE) in a network, the method comprising: sending a timing advance report to a first network entity (e.g., a base station), the timing advance report including information indicating timing advance; wherein the timing advance is based on an active downlink bandwidth portion.
[0220] In the seventeenth example, a method is provided in any one of the seventh example or the fourteenth to sixteenth examples, wherein the timing is advanced based on the subcarrier spacing of the active downlink bandwidth portion.
[0221] In the eighteenth example, a method is provided in any one of the seventh or fourteenth to seventeenth examples, wherein the information indicating timing advance indicates the number of symbols, and wherein the symbol duration is based on the subcarrier spacing of the active downlink bandwidth portion.
[0222] In the nineteenth example, a method is provided in any one of the seventh or fourteenth to eighteenth examples, wherein the information indicating timing advance is a timing advance field.
[0223] In the twentieth example, a method is provided in any one of the seventh or fourteenth to nineteenth examples, wherein the timed advance reporting is a timed advance reporting media access control control unit (TAR MAC CE).
[0224] In the twenty-first example, a method according to any one of the first to twentieth examples is provided, wherein the network is either an air-to-ground network or a non-terrestrial network.
[0225] In the twenty-second example, a first network entity (e.g., a base station) is provided, which is configured to operate according to any one of the first to seventh examples, the fifteenth example, or the seventeenth to twenty-first examples.
[0226] In the twenty-third example, a second network entity (e.g., a UE) is provided, which is configured to operate according to any one of the methods in the eighth to fourteenth examples, or the sixteenth to twenty-first examples.
[0227] In the twenty-fourth example, a network or wireless communication system is provided, which includes a first network entity according to the twenty-second example and a second network entity according to the twenty-third example.
[0228] In the twenty-fifth example, a computer program including instructions is provided that, when executed by a computer or processor, causes the computer or processor to perform a method according to any one of the first to twenty-first examples.
[0229] In the twenty-sixth example, a computer or processor-readable data carrier on which a computer program according to the twenty-fifth example is stored is provided.
[0230] Those skilled in the art will understand that the illustrative embodiments described herein are not intended to limit the scope of the descriptions above. It should be understood that any two or more embodiments disclosed herein can be combined in any combination. Furthermore, other embodiments can be utilized and other changes can be made without departing from the spirit and scope of the subject matter set forth herein. It will be readily understood that various aspects of the invention disclosed herein, as generally described herein and shown in the accompanying drawings, can be arranged, substituted, combined, separated, and designed in a variety of different configurations, all of which are contemplated herein.
[0231] Those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and steps described herein can be implemented as hardware, software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are generally described above in the form of their functional sets. Whether such a functional set is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art may implement the described functional sets in different ways for each specific application, but such design decisions should not be construed as departing from the scope of this application.
[0232] The various illustrative logic blocks, modules, and circuits described in this application may be implemented in a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.
[0233] The steps of the methods or techniques described in this application may be embodied directly in hardware, in a software module executed by a processor, or in a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, or any other form of storage medium known in the art. An exemplary storage medium is connected to the processor so that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in the UE. Alternatively, the processor and storage medium may reside in the UE as discrete components.
[0234] The above description is merely an exemplary embodiment of this disclosure and is not intended to limit the scope of protection of this disclosure as defined by the appended claims.
[0235] Abbreviations / Definitions
[0236] The following abbreviations / definitions may be used in this disclosure.
[0237]
Claims
1. A method performed by a terminal supporting an air-to-ground ATG network in a wireless communication system, the method comprising: Receive a Radio Resource Control (RRC) message from a base station supporting the ATG network, including a configuration for timed advance TA reporting, wherein the configuration includes offset threshold information for the TA reporting; Based on the offset threshold information, it is determined whether to trigger the TA report, wherein the offset threshold information is in symbol units and configured based on the subcarrier spacing (SCS) of the active downlink DL bandwidth portion (BWP); and Upon triggering the TA report, a Media Access Control (MAC) Control Unit (CE) including information about the estimated TA is sent to the base station.
2. The method according to claim 1, in, The configured offset threshold information is not changed autonomously by the terminal during BWP handover.
3. The method according to claim 1, in, The offset threshold information is configured for the primary cell group (MCG), and The serving cell associated with the activity DL BWP is the primary cell PCell of the MCG.
4. The method according to claim 1, in, Information about the estimated TA indicates the sign of the smallest integer number greater than or equal to the estimated TA, and The symbol duration for the minimum number of symbols is determined based on the SCS of the activity DL BWP.
5. The method according to claim 1, in, The TA report is triggered when the terminal has not previously reported a TA associated with the serving cell when the offset threshold information is configured, or when the change between the estimated TA and the last reported TA is equal to or greater than the offset threshold information.
6. A method performed by a base station supporting an air-to-ground ATG network in a wireless communication system, the method comprising: Generate offset threshold information for timed advance TA reporting, wherein the offset threshold information is in symbol units and is configured based on the subcarrier spacing SCS of the active downlink DL bandwidth portion BWP; Send a Radio Resource Control (RRC) message to terminals supporting the ATG network, including configurations for the TA report, wherein the configurations include offset threshold information; and The Media Access Control (MAC) control unit CE receives information about the TA from the terminal. The TA report is triggered based on the offset threshold information.
7. The method according to claim 6, in, The configured offset threshold information is not changed autonomously by the terminal during BWP handover.
8. The method according to claim 6, in, The offset threshold information is configured for the primary cell group (MCG), and The serving cell associated with the activity DL BWP is the primary cell PCell of the MCG.
9. The method according to claim 6, in, Information about the TA indicates signs that are greater than or equal to the minimum number of integers in the TA, and The symbol duration for the minimum number of symbols is determined based on the SCS of the activity DL BWP.
10. The method according to claim 6, in, The TA report is triggered when the terminal has not previously reported a TA associated with the serving cell when the offset threshold information is configured, or when the change between the TA and the last reported TA is equal to or greater than the offset threshold information.
11. A terminal supporting an air-to-ground ATG network in a wireless communication system, the terminal comprising: transceiver; as well as The processor, connected to the transceiver, is configured to: Receive a Radio Resource Control (RRC) message from a base station supporting the ATG network, including a configuration for timed advance TA reporting, wherein the configuration includes offset threshold information for the TA reporting; Based on the offset threshold information, it is determined whether to trigger the TA report, wherein the offset threshold information is in symbol units and configured based on the subcarrier spacing (SCS) of the active downlink DL bandwidth portion (BWP); and Upon triggering the TA report, a Media Access Control (MAC) Control Unit (CE) including information about the estimated TA is sent to the base station.
12. The terminal according to claim 11, in, The configured offset threshold information is not changed autonomously by the terminal during BWP handover. The offset threshold information is configured for the primary cell group (MCG), and The serving cell associated with the activity DL BWP is the primary cell PCell of the MCG.
13. The terminal according to claim 11, in, Information about the estimated TA indicates the sign of the smallest integer number greater than or equal to the estimated TA. Wherein, the symbol duration for the minimum integer number of symbols is determined based on the SCS of the activity DL BWP, and Specifically, the TA report is triggered when the terminal has not previously reported a TA associated with the serving cell when the offset threshold information is configured, or when the change between the estimated TA and the last reported TA is equal to or greater than the offset threshold information.
14. A base station supporting an air-to-ground ATG network in a wireless communication system, the base station comprising: transceiver; as well as The processor, connected to the transceiver, is configured to: Generate offset threshold information for timed advance TA reporting, wherein the offset threshold information is in symbol units and is configured based on the subcarrier spacing SCS of the active downlink DL bandwidth portion BWP; Send a Radio Resource Control (RRC) message to terminals supporting the ATG network, including configurations for the TA report, wherein the configurations include offset threshold information; and The Media Access Control (MAC) control unit CE receives information about the TA from the terminal. The TA report is triggered based on the offset threshold information.
15. The base station according to claim 14, in, The configured offset threshold information is not changed autonomously by the terminal during BWP handover. The offset threshold information is configured for the primary cell group (MCG), and The serving cell associated with the activity DL BWP is the primary cell PCell of the MCG. The information about TA indicates the sign of a minimum number of integers greater than or equal to TA. The symbol duration for the minimum integer number of symbols is determined based on the SCS of the activity DL BWP. Specifically, the TA report is triggered when the terminal has not previously reported a TA associated with the serving cell when the offset threshold information is configured, or when the change between the TA and the last reported TA is equal to or greater than the offset threshold information.
