Wireless communication method and related apparatus

Abstract

Embodiments of the present application provide a wireless communication method and related apparatus. The method multiplexes a DCI scheduling a Msg2 to extend a TA in a TAC of the Msg2 transmission and adds a frequency adjustment command for a UE with GNSS unavailable or inaccurate. The UE adjusts an uplink timing according to the extended TA and adjusts an uplink carrier frequency according to the frequency adjustment command. Further, a gNB calculates a residual timing error and a residual frequency error after receiving a Msg3 and notifies the UE of the residual timing error and the residual frequency error through a Msg4. The UE adjusts an uplink time-frequency position according to the residual timing error and the residual frequency error, thereby improving the timing and frequency synchronization capability between the UE with GNSS unavailable or inaccurate and the gNB, and reducing the random access delay and failure rate of the UE.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a wireless communication method and related apparatus. Background Technology

[0002] Non-terrestrial networks (NTNs) and terrestrial cellular mobile communication networks can be integrated to effectively cover the ground, air, and sea, achieving integrated air-space-ground communication. NTN satellites orbit at altitudes of at least several hundred kilometers, covering distances of hundreds to thousands of kilometers. This results in significantly greater propagation delays for NTNs compared to terrestrial networks. Therefore, timing advance (TA) is introduced to ensure uplink / downlink frame alignment. Terminal devices need to autonomously pre-compensate for uplink timing based on their own Global Navigation Satellite System (GNSS) and ephemeris data from satellites or high-altitude platform systems (HAPS).

[0003] However, in some cases, the GNSS information from the terminal device may be inaccurate, which can lead to non-negligible errors in the GNSS-derived location, i.e., poor GNSS reliability. Poor GNSS reliability can result in inaccurate uplink timing pre-compensation.

[0004] Although in contention-based random access procedures, access network devices can use the Random Access Response (RAR) message (Msg2) to time the transmission of Msg3 by terminal devices, there is a significant time delay from the time the terminal device receives the RAR message to send Msg3, and then receives Msg4 and sends Msg4-ACK or Msg5. Furthermore, for high-speed moving satellites and terminal devices, the channel characteristics change during this process. The TA value in Msg2 may expire, or even using the maximum TA value may result in the access network device receiving Msg3 with an error exceeding the maximum tolerance limit, leading to a decrease in the decoding rate of Msg3 and potentially causing random access failure. Summary of the Invention

[0005] In view of the above, this application provides a wireless communication method and related apparatus to solve at least some of the aforementioned problems, and the disclosed technical solution is as follows:

[0006] In a first aspect, this application provides a wireless communication method executed by a terminal device. The method includes: sending a first message, the first message including GNSS status information of the terminal device, the GNSS status information indicating that the GNSS of the terminal device is unavailable or inaccurate; receiving downlink control information from a network device, the downlink control information being used to schedule the transmission of a second message, the downlink control information including a timing advance command and a frequency adjustment command; receiving a second message from the network device, the second message including a timing advance command; sending a third message based on adjusted uplink timing and adjusted uplink carrier frequency, the third message including an initial access connection request, the adjusted uplink timing being adjusted based on the timing advance command and the timing advance command, and the adjusted uplink carrier frequency being adjusted based on the frequency adjustment command; receiving a fourth message from the network device, the fourth message including residual timing error and residual frequency error obtained based on the received information of the third message; and sending uplink data based on the time-frequency resources adjusted using the residual timing error and residual frequency error.

[0007] This method reuses the DCI of the second scheduling message (Msg2) to extend the TA (Temporal Accompaniment) of UEs with unavailable or inaccurate GNSS and adds frequency adjustment commands, increasing the TA adjustment range and simultaneously achieving frequency adjustment. Further, the network device obtains residual timing errors and residual frequency errors based on the received information from the third message and notifies the UE in the fourth message (Msg4). The UE applies the residual timing errors to adjust the currently used uplink timing compensation TA and applies the residual frequency errors to adjust the uplink carrier frequency. This two-stage adjustment mechanism adjusts the time-frequency position of the UE's uplink transmission, improving the timing and frequency synchronization capability between UEs with unavailable or inaccurate GNSS and the gNB, thereby reducing random access latency and failure rate for such UEs. Moreover, this method reuses the DCI and Msg4 of the second scheduling message (Msg2) to achieve the above process without adding commands, improving signaling resource utilization and overall resource efficiency.

[0008] In one possible implementation, the reserved bits of the downlink control information are used to carry timing advance extension commands and frequency adjustment commands. This reuses the reserved bits of the DCI to extend the TA and add frequency adjustment, eliminating the need for dedicated signaling, thus improving signaling resource utilization and reducing time and frequency resource consumption.

[0009] In one possible implementation, the adjusted uplink timing is based on the timing advance extension command and the timing advance command, including: concatenating all bits of the timing advance extension command with all bits of the timing advance command into a single code; calculating the TA value corresponding to the concatenated code; and adjusting the uplink timing according to the TA value. In this way, by dividing the TA value into two parts, one part is transmitted to the UE via DCI, and the other part is transmitted to the UE via Msg2, the TA is extended without requiring additional signaling, thus improving signaling resource utilization.

[0010] In one possible implementation, the fourth message includes a MAC CE for carrying residual timing and frequency errors. This allows the Msg4 message to be used to transmit residual timing and frequency errors to the UE without requiring additional signaling transmission of these two pieces of information, thus improving signaling resource utilization.

[0011] In one possible implementation, the LCID identifier reserved in the MAC layer protocol data unit subheader of the fourth message is used to identify the MAC CE used to carry residual timing and frequency errors. This way, by using the reserved LCID identifier to identify the MAC CE carrying residual timing and frequency errors, the UE can correctly identify the MAC CE carrying these errors without needing to add additional identifier bits, thus improving signaling resource utilization.

[0012] In one possible implementation, the GNSS status information is a preamble that matches the GNSS status of the terminal device. A first preamble range is allocated to terminal devices where GNSS is unavailable or inaccurate, and a second preamble range is allocated to terminal devices where GNSS is available. The first and second preamble ranges do not overlap. By associating the preamble with the GNSS status, the network device can accurately identify the UE's GNSS status using the preamble, enhancing the network device's ability to identify GNSS-less UEs and improving signaling resource utilization.

[0013] In one possible implementation, the downlink control information is scrambled using RA-RNTI-GNSS, which is obtained by adding a GNSS state factor to RA-RNTI. The GNSS state factor is associated with the preamble corresponding to the terminal equipment where GNSS is unavailable or inaccurate. This enhances the UE's ability to identify DCIs related to its own GNSS state and improves the accuracy of TA extension and frequency adjustment for UEs with unavailable or inaccurate GNSS.

[0014] Secondly, this application also provides a wireless communication method executed by a network device. The method includes: receiving a first message from a terminal device, the first message including GNSS status information of the terminal device, the GNSS status information indicating that the GNSS of the terminal device is unavailable or inaccurate; sending downlink control information, the downlink control information used to schedule the transmission of a second message, the downlink control information including a timing advance command and a frequency adjustment command; sending a second message, the second message including a timing advance command; receiving a third message from the terminal device, the third message including an initial access connection request; sending a fourth message, the fourth message including residual timing error and residual frequency error obtained based on the received information of the third message; and receiving uplink data from the terminal device, the uplink data being transmitted based on time-frequency resources adjusted using the residual timing error and residual frequency error. This method adjusts the time-frequency position of the UE's uplink transmission through a two-level adjustment mechanism, improving the timing and frequency synchronization capability between the UE and the gNB when GNSS is unavailable or inaccurate, thereby reducing the random access latency and failure rate of such UEs. Moreover, this method reuses the DCI and Msg4 of the second scheduling message (Msg2), and can achieve the above process without adding commands, thereby improving the signaling resource utilization and overall resource utilization.

[0015] Thirdly, this application also provides a communication device including at least one processor coupled to a memory storing a program or instructions, wherein the processor executes the program or instructions to cause the device to perform the method as described in any of the first aspects.

[0016] Fourthly, this application also provides a computer-readable storage medium having a computer program or instructions stored thereon, which, when executed, cause a computer to perform the method as described in any of the first aspects.

[0017] Fifthly, this application also provides a communication system, including the communication device provided in the third aspect.

[0018] Sixthly, this application also provides a chip system including one or more processors, the one or more processors being configured to retrieve and execute instructions stored in memory, such that the method of any of the first aspects is performed. Attached Figure Description

[0019] Figure 1 A schematic diagram of an NTN communication system provided in an embodiment of this application;

[0020] Figure 2 A schematic diagram of a service link and a power supply link in an NTN communication system provided for an embodiment of this application;

[0021] Figure 3This is a schematic diagram of the structure of an access network device provided in an embodiment of this application;

[0022] Figure 4 A flowchart illustrating a wireless communication method provided in an embodiment of this application;

[0023] Figure 5 A schematic diagram of a DCI 1_0 frame structure provided for an embodiment of this application;

[0024] Figure 6 A schematic diagram of the frame structure of a MAC CE carrying residual timing error and residual frequency error provided in an embodiment of this application;

[0025] Figure 7 A flowchart illustrating another wireless communication method provided in an embodiment of this application;

[0026] Figure 8 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0027] Figure 9 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0028] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0029] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0030] In this application, "multiple" refers to two or more embodiments. It should be noted that in the description of the embodiments of this application, terms such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating or implying relative importance, nor as indicating or implying order.

[0031] First, the relevant technologies involved in the embodiments of this application will be described.

[0032] 1. NTN communication

[0033] Non-terrestrial communication boasts advantages such as wide coverage, long communication distance, high reliability, high flexibility, and high throughput. Unaffected by geographical environment, climate conditions, or natural disasters, it has been widely applied in fields such as aviation, maritime, and military communications. Introducing NTN into 5th generation (5G) mobile networks can improve the performance of communication systems. Satellite communication systems and HAPS are typical non-terrestrial communication systems. On the one hand, satellite networks can provide communication services to areas difficult for terrestrial networks to cover, such as oceans, forests, deserts, or remote areas; on the other hand, satellite networks can enhance the reliability of 5G communications, providing more stable communication services for users in high-speed moving scenarios such as trains and airplanes. Furthermore, satellite networks can provide more data transmission resources and support a larger number of connections.

[0034] Generally speaking, the higher a satellite's orbit, the larger its coverage area, but the longer the communication latency. Based on orbital altitude, satellites can be classified as:

[0035] (1) Low Earth Orbit (LEO): Orbital altitude is 160-2000 km;

[0036] (2) Medium Earth Orbit (MEO): Orbital altitude is 2000-35786 km;

[0037] (3) Geostationary Earth orbit (GEO): The orbital altitude is 35,786 km;

[0038] GEO stands for Geostationary Earth Orbit, in which satellites are stationary relative to the Earth's surface. LEO and MEO are collectively referred to as non-geostationary orbits (NGSO), in which satellites move at high speeds relative to the Earth's surface. Currently, industry research focuses on GEO and LEO satellites.

[0039] Based on how satellites process wireless signals, NTN includes two main scenarios: transparent forwarding and regenerative forwarding.

[0040] For transparent forwarding, such as Figure 1 As shown in (1), the base station can be deployed on the ground and communicate with the satellite through a ground gateway. The base station and the ground gateway can be connected to the core network equipment via wired or wireless means. The satellite forwards the cell information of the ground network equipment (such as the next generation Node-B, gNB). The role of the satellite is to filter, convert, and amplify the radio frequency. That is, the satellite mainly acts as a Layer 1 relay, regenerating the physical layer signal, and does not have other higher protocol layers.

[0041] For regeneration forwarding, such as Figure 1 As shown in (2), the base station can be deployed on the satellite, and can also be called a satellite base station. The satellite base station can be connected to the ground gateway station through the next generation (NG) interface. In this mode, the satellite has the processing function of the base station.

[0042] Figure 1 The data network (DN) in the system can transmit data with terminal devices through core network equipment and base stations, providing data communication services to terminal devices to realize their business.

[0043] The architecture of the NTN communication system described above is merely an example. The NTN communication system may also include other architectures, which are not limited in this application.

[0044] 2. TA

[0045] A key characteristic of uplink transmission is that uplink transmissions from different terminal devices within the same cell do not interfere with each other. To ensure the orthogonality of uplink transmission and avoid intra-cell interference, the base station requires that signals from different terminal devices originating from the same subframe but from different frequency domain resources (different resource blocks (RBs)) arrive at the base station at essentially the same time. As long as the base station receives the uplink data transmitted by the terminal device within the cyclic prefix (CP) range, it can correctly decode the uplink data. Therefore, uplink synchronization requires that the arrival times of signals from different terminal devices within the same subframe all fall within the cyclic prefix range.

[0046] To ensure time synchronization at the receiving end (base station), Long Term Evolution (LTE) / New Radio (NR) introduces an uplink timing advance (TA) mechanism. From the perspective of the terminal device, TA is essentially a negative offset between the start time of receiving downlink subframes and the time of transmitting uplink subframes. By appropriately controlling the offset of each terminal device, the base station can control the arrival time of uplink signals from different terminal devices. For terminal devices farther from the base station, due to the larger transmission delay, they need to send uplink data earlier than terminal devices closer to the base station.

[0047] In NTN, the propagation delay and differential delay between terminal equipment (UE) and access network equipment (gNB) are very large. Furthermore, for LEO satellites, the high-speed movement of the satellites causes the delays of both the service link and the feeder link to change rapidly and continuously. Figure 2 As shown, the link between the UE and the satellite is the serving link, and the TA used to compensate for the propagation delay of the serving link is called the serving TA. The link between the terrestrial network and the satellite is the feeder link.

[0048] 3GPP Rel-17 specifies that the UE must have GNSS capability. This allows the UE to roughly estimate the propagation delay between the UE and the satellite based on its own location and satellite ephemeris data. The residual timing error is small enough to be compensated for using methods similar to those used in terrestrial cellular mobile communication networks. At the same time, necessary enhancements were made to the protocol to compensate for the extremely long and rapidly changing propagation delay between the UE and the gNB.

[0049] However, the UE's GNSS information may be temporarily unavailable, or available but inaccurate. The current protocol considers the following two scenarios:

[0050] Scenario 1: There is no GNSS information at the UE (i.e., the UE does not have GNSS capability at the moment), and it is impossible to rely on GNSS information for timing compensation and frequency compensation on the service link.

[0051] Scenario 2: There is a previously acquired GNSS-based location, but the UE has not received GNSS information for a long time since the last acquisition of GNSS location information, that is, the GNSS accuracy is low.

[0052] In both scenario 1 and scenario 2, the UE is similar to a UE without GNSS capability, requiring compensation for at least 6.44ms of one-way latency (LEO satellite, altitude 600km). Even with differential latency compensation, at least 3.12ms (LEO satellite, altitude 600km) still needs to be compensated, far exceeding current design capabilities. Differential latency refers to the difference in propagation latency between two selected points at a specific location within the beam coverage area.

[0053] Although in a contention-based random access procedure, the gNB can perform preliminary timing adjustments on the UE's transmission of Msg3 via the TAC in Msg2 (RAR), the following two key issues exist:

[0054] (1) The TA adjustment value is inaccurate; there is a significant time delay from when the UE receives Msg2 to when it sends Msg3 (especially in case of retransmission), and then to when it receives Msg4 and sends Msg4-ACK or Msg5. For high-speed moving satellites and UEs, the channel characteristics have changed during this period, and the TA value provided in Msg2 may be outdated, or the maximum value of the TA value may not be able to compensate for the narrow range.

[0055] (2) Lack of frequency adjustment; the current RAR only includes TAC and does not have a frequency adjustment command. However, due to the very large distance error, the initial frequency error is also very large, reaching 20ppm, which will seriously affect the demodulation performance of gNB for Msg3, Msg4-ACK and Msg5.

[0056] It is evident that the unavailability or inaccuracy of GNSS can lead to unpredictable and potentially huge timing and frequency errors, exposing the limitations of the current PRACH format in NTN environments, especially in high-orbit and large-beam scenarios.

[0057] To address the aforementioned issues, this application provides a wireless communication method. Before scheduling authorization for Msg3, the downlink control information (DCI) of scheduling Msg2 is reused to transmit a TA extension command and a frequency adjustment command to a UE with unavailable or inaccurate GNSS. The UE uses the TA extension command and the TA in the TAC of Msg2 as timing compensation for transmitting Msg3. Simultaneously, it uses the frequency adjustment command to adjust the uplink carrier frequency for transmitting Msg3. After receiving Msg3, the gNB calculates the residual timing error and residual frequency error and sends Msg4 carrying the residual timing error and residual frequency error to the UE. After receiving Msg4, the UE further applies the residual timing error to adjust the currently used uplink timing compensation TA and applies the residual frequency error to adjust the uplink carrier frequency. In this way, the time and frequency position of the UE's uplink transmission is adjusted through a two-stage adjustment mechanism, improving the timing and frequency synchronization capability between the UE with unavailable or inaccurate GNSS and the gNB, thereby reducing the random access delay and failure rate of such UEs.

[0058] The technical solutions provided in this application can be applied to communication systems, which may include, but are not limited to, the following systems: second-generation (2G) communication systems, third-generation (3G) communication systems, long-term evolution (LTE) systems, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) systems or new radio (NR) systems, 5.5G systems or sixth-generation (6G) systems, and future mobile communication systems; vehicle-to-X (V2X); V2X may include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), long-term evolution-vehicle (LTE-V) communication technology, vehicle-to-everything (V2X) communication, and machine-type communication. Communication, MTC, Internet of Things (IoT), Ambient Internet of Things (AIOT), Long Term Evolution of Machine (LTE-M), Machine to Machine (M2M), etc.

[0059] The communication system can be applied to scenarios including: non-terrestrial communication, satellite communication, high-altitude communication platform communication, vehicle-to-everything (V2X) communication, integrated access and backhaul (IAB) communication, reconfigurable intelligent surface (RIS) communication, etc.

[0060] like Figure 1 As shown in (1), the NTN mainly includes: terrestrial gateway (including access network equipment), satellite, and UE. Figure 1As shown in (2), all or part of the functional modules of the access network equipment may be deployed on an airborne platform or satellite, or other forms of communication equipment deployed in the high atmosphere. Accordingly, the access network equipment may refer to an airborne platform, satellite, or other similar equipment that connects terminal equipment to the core network equipment. The airborne platform may include at least one of the following: satellite, drone, or hot air balloon.

[0061] Access network equipment is a device deployed in a radio access network to provide wireless communication functions. Access network equipment can also be called access network node, RAN (radio access network) node, RAN entity, or access node, etc. It is located on the network side of the aforementioned communication system and is used to help terminal devices achieve wireless access. It is a device with wireless transceiver capabilities, or a chip or chip system that can be installed in the device. Access network equipment includes, but is not limited to: base stations, evolved NodeBs (eNodeBs), access points (APs), transmission receiving points / transmission reception points (TRPs) or transmission points (TPs), base stations (gNodeBs or gNBs) in NR, next-generation base stations in 6G mobile communication systems, base stations in future mobile communication systems, or access nodes in Wi-Fi systems, etc.

[0062] Access network equipment can be a macro base station, micro base station, indoor station, relay node, donor node, or radio controller in a centralized radio access network (CRAN) scenario. Access network equipment can also be one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or it can be a network node constituting a gNB, TRP, TP, or transmission measurement function (TMF), such as a central unit (CU), DU, CU-control plane (CP), CU-user plane (UP), or radio unit (RU), roadside unit (RSU) with base station functionality. Optionally, access network equipment can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in V2X technology can be an RSU. All or part of the functions of the access network equipment in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The access network device in this application may also be a logical node, logical module, or software that can implement all or part of the functions of the access network device.

[0063] The CU and DU can be set up separately or included in the same network element, such as the baseband unit (BBU). The RU can be included in radio frequency equipment or radio frequency units, such as in a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0064] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0065] Figure 3This is a schematic diagram of the structure of an access network device. As an implementation example, such as... Figure 3 As shown, the access network device may include at least one CU and at least one DU. This design can be referred to as CU and DU separation. One CU can be connected to one or more DUs. CU and DU can be separated according to the protocol layer of the wireless network: for example, the functions of the PDCP layer and above (such as the RRC layer and SDAP layer, etc.) are set in the CU, and the functions of the protocol layers below the PDCP layer (such as the RLC layer, media access control (MAC) layer, and PHY layer, etc.) are set in the DU; or, for example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU, without limitation. When the CU includes CU-CP and CU-UP, CU-CP is used to implement the control plane functions of the CU, and CU-UP is used to implement the user plane functions of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, CU-CP is used to implement the RRC layer functions and the PDCP layer control plane functions, and CU-UP is used to implement the SDAP layer functions and the PDCP layer user plane functions. This application does not limit the names of CU and DU. The above division of CU and DU processing functions according to the protocol layer is just one example; other methods can also be used.

[0066] The CU can be connected to the core network. Optionally, the CU can have some of the functions of the core network.

[0067] Furthermore, some functions of the DU can be separated and configured. For example... Figure 3As shown, this functionality can be implemented by a radio unit (RU). The RU can have radio frequency (RF) capabilities. This application does not limit the name of the RU. The DU and RU can be split or separated within the PHY layer. For example, the DU can implement higher-level functions in the PHY layer, and the RU can implement lower-level functions in the PHY layer, or implement both lower-level and RF functions. Higher-level functions in the PHY layer include functions closer to the MAC layer, and lower-level functions in the PHY layer include functions closer to the RF layer. For example, higher-level functions in the PHY layer include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling, or modulation / demodulation. Lower-level functions in the PHY layer include one or more of the following: fast Fourier transform (FFT) / inverse fast Fourier transform (IFFT), beamforming, or extraction and filtering of the physical random access channel (PRACH), etc. The RU can communicate with the terminal device via the air interface using RF signals. The pre-coding function of the PHY layer code can be located in the DU or the RU. The separation between the DU and RU can be done in various ways without restriction. An interface exists between the DU and RU. For example, depending on the separation method, the interface between the DU and RU can be a Common Public Radio Interface (CPRI) interface or an Enhanced Common Public Radio Interface (eCPRI) interface.

[0068] Optionally, any one of CU, CU-CP, CU-UP, DU, and RU can be a software module, a hardware structure, or a combination of software and hardware structures, without limitation. The different entities can exist in the same or different forms. For example, CU, CU-CP, CU-UP, and DU are software modules, and RU is a hardware structure. For the sake of brevity, all possible combinations are not listed here. These modules and the methods they execute are also within the protection scope of the embodiments of this application. For example, when the method of the embodiments of this application is executed by an access network device, it can be specifically executed by at least one of CU, CU-CP, CU-UP, DU, or RU.

[0069] In this application embodiment, the form of the access network device is not limited. The device used to implement the function of the access network device can be the access network device itself; it can also be a device that supports the access network device in implementing the function, such as a chip system. The device can be installed in the access network device or used in conjunction with the access network device.

[0070] In the embodiments of this application, the terminal can be a terminal device with transceiver functions, or it can be a chip or chip system disposed in the terminal device. In the embodiments of this application, the terminal device can be of various forms, such as a mobile phone, tablet computer, computer with wireless transceiver functions, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control, vehicle-mounted terminal device, wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, wearable terminal device, etc. The terminal device of this application can also be an on-board module, on-board component, on-board chip, or on-board unit built into a vehicle as one or more components or units. The terminal device can also be other devices with terminal functions; for example, the terminal device can also be a device that performs terminal functions in D2D communication.

[0071] A terminal may also be referred to as terminal equipment, user equipment (UE), access terminal equipment, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal equipment, mobile device, UE terminal equipment, wireless communication equipment, UE agent, or UE device, etc. A terminal can also be a fixed terminal or a mobile terminal.

[0072] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal device can be the terminal device itself; it can also be a device that supports the terminal device in implementing the functions, such as a chip system. The device can be installed in the terminal device or used in conjunction with the terminal device. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete components.

[0073] A core network unit is a functional unit deployed in the core network to provide services to terminal devices. In systems employing different radio access technologies, the names of core network devices with similar wireless communication functions may differ. For example, when the communication method of this application embodiment is applied to a 5G system, the core network device may be an access and mobility management function (AMF) network element, a session management function (SMF) network element, a user plane function (UPF) network element, etc. The UPF network element processes user plane data. The AMF and SMF network elements process control plane signaling. When the precoding method of this application embodiment is applied to an LTE system, the core network device may be a mobility management entity (MME). For ease of description only, in this application embodiment, the above-mentioned devices that can provide services to terminal devices are collectively referred to as core network devices.

[0074] like Figure 1 As shown, the system also includes a data network (DN). Here, the interface for communication between the terminal equipment and the access network equipment can be an air interface. The interface for communication between the access network equipment and the ground gateway can be an NG interface. The interface for communication between the ground gateway and the core network can also be an NG interface. The core network unit can be connected to only one ground gateway; in this case, the access network equipment can connect to the core network unit through one ground gateway, as detailed below. Figure 1 As shown. A core network unit can connect to more than one terrestrial gateway. In this case, access network devices can connect to the core network unit through any of the more than one terrestrial gateways. The core network unit (such as a UPF network element) can communicate with entities or network elements in the DN through an interface (such as the N6 interface).

[0075] It should be noted that the above only lists some of the communication methods between network elements. Other network elements can also communicate through certain connection methods, which will not be described in detail here in the embodiments of this application.

[0076] Please see Figure 4 The diagram illustrates a flowchart of a wireless communication method provided in an embodiment of this application, which can be applied to... Figure 1 In the communication system shown, such as Figure 4 As shown, the method may include the following steps:

[0077] S101, the UE sends the first message (Msg1) to the network device.

[0078] The corresponding network devices receive the first message, where the network devices here mainly refer to the satellites in NTN.

[0079] The first message carries the UE's GNSS status information, which indicates that the UE's GNSS is unavailable or inaccurate.

[0080] Before transmitting Msg1, the UE calculates the initial timing advance TA_initial and the initial frequency offset FO_initial. TA_initial and FO_initial are calculated using existing methods.

[0081] For example, TA_initial can be calculated using the following formula:

[0082] (1)

[0083] TA represents the total timing advance, which is the timing adjustment amount ultimately applied to the uplink transmission of the terminal to ensure that the signal can be correctly synchronized.

[0084] Network timing advance (GNB) primarily compensates for uplink timing errors caused by UE location changes. The gNB uses Media Access Control (MAC) layer signaling to... The notification to the UE is based on a basic timing adjustment calculated according to the physical distance between the terminal and the base station; for PRACH, since the gNB does not know the UE's location, therefore... =0. For PUSCH scheduled in random access response, gNB notifies UE via RAR.

[0085] This is the network timing advance offset, used to fine-tune the timing advance of the underlying network. It can be used to compensate for specific propagation conditions or system errors. In a Frequency Division Duplex (FDD) system, this parameter is 0.

[0086] The common adjustment timing advance is the transmission delay from the satellite to the reference point, which is calculated by the network side and sent to the terminal.

[0087] The UE adjustment timing advance is the transmission delay from the terminal to the satellite, and the service link transmission delay, which is calculated by the terminal based on the terminal's location information and ephemeris information.

[0088] A timing constant is a fundamental unit of time used to quantify timing advance. In different communication systems, The specific value may vary.

[0089] It can be seen that TA consists of two parts: the first part ( , , This is provided by the network, meaning it can be calculated by the network and notified to the terminal. Part Two ( It is calculated by the terminal, for example, it can be calculated based on the terminal's GNSS position and ephemeris information.

[0090] The frequency offset FO_initial is related to the UE's elevation angle, because different elevation angles will result in different relative velocities between the satellite and the UE. It can be calculated using the following formula:

[0091] (2)

[0092] in, and represents the elevation angle of the UE when there is a positioning error and when there is no positioning error, respectively; f and v represent the operating frequency and velocity of the satellite, respectively; and c represents the speed of light.

[0093] The UE randomly selects a random access preamble and sends it to the gNB via the PRACH channel based on the calculated TA_initial and FO_initial, i.e., sends Msg1.

[0094] S102, the network device sends a DCI for scheduling Msg2. The corresponding UE receives the DCI.

[0095] This DCI carries the TA expansion command TA_expand_factor and the frequency adjustment command Fre_Offset.

[0096] In this embodiment, after receiving Msg1 from the UE, the network device calculates the TA adjustment value and the frequency adjustment value based on the time-frequency position and cyclic shift information of the received Msg1. Then, the TA adjustment value is divided into two parts: one part (the first TA) is filled into DCI 1_0 used to schedule the transmission of Msg2, and the other part (the second TA) is filled into the RAR message. The frequency adjustment value is filled into DCI 1_0 used to schedule the transmission of Msg2.

[0097] Specifically, DCI 1_0 is used to schedule the physical downlink shared channel (PDSCH) to transmit Msg2. The Cyclic Redundancy Check (CRC) in DCI 1_0 is scrambled using the Random Access-RadioNetwork Temporary Identifier (RA-RNTI) to ensure that Msg2 is only decoded by the corresponding UE.

[0098] DCI 1_0 is mainly responsible for PDSCH scheduling during access, such as services like SIB1, Msg2, and Msg4. The specific service type is distinguished according to the RNTI type of CRC scrambling.

[0099] In one possible implementation, the DCI 1_0 scrambled with RA-RNTI includes at least 14 reserved bits, such as... Figure 5 As shown, two new fields can be introduced by reusing the reserved bits in DCI 1_0: the TA extension command and the frequency adjustment command.

[0100] For example, a TA extension command can occupy 6 bits, where 1 bit (e.g., the most significant bit) represents positive or negative, and the remaining 5 bits represent TA extension, with a granularity of 0.509ns. A positive sign bit indicates that uplink data is sent earlier than the original uplink timing, while a negative sign bit indicates that uplink data is sent later than the original uplink timing.

[0101] The frequency adjustment command can occupy 8 bits, with 1 bit (e.g., the most significant bit) indicating positive or negative, and the remaining 7 bits indicating the absolute value of the frequency offset, with a granularity of 0.1 ppm. A positive sign indicates that the absolute value of the frequency offset is increased based on the original uplink carrier frequency, and a negative sign indicates that the absolute value of the frequency offset is decreased based on the original uplink carrier frequency.

[0102] The frequency domain resource indicator in DCI 1_0 is used to indicate the frequency domain resources of PDSCH, that is, the frequency domain location for transmitting Msg2; the time domain resource indicator is used to indicate the time domain resources of PDSCH, occupying 4 bits, that is, the time domain location for transmitting Msg2.

[0103] S103, the network device sends a second message (Msg2) to the UE. The corresponding UE receives Msg2. Msg2 is the Random Access Response (RAR).

[0104] Send Msg2 on the PDSCH resource scheduled by DCI 1_0. Msg2 contains a Timing Advance Command (TAC), which contains a second TA and occupies 12 bits.

[0105] Msg2 also includes uplink grant information, which mainly includes frequency hopping flags, PUSCH frequency domain resource allocation, PUSCH time domain resource allocation, modulation and coding scheme (MCS), power control commands, etc.

[0106] The first TA in DCI 1_0, which schedules Msg2 transmission, is combined with the second TA in Msg2 to obtain the TA adjustment value TA_new. The frequency adjustment command in DCI 1_0 is used to adjust the frequency of the uplink carrier.

[0107] S104, the UE adjusts the uplink timing based on the first TA and the second TA, and at the same time applies a frequency adjustment command to adjust the uplink carrier frequency.

[0108] After the UE sends Msg1, it listens for the PDCCH of DCI 1_0 in the specified search window. If the UE listens for the PDCCH of DCI 1_0, it will successfully descramble DCI 1_0 using its corresponding RA-RNTI before receiving the RAR message transmitted in the PDCCH transport block. Furthermore, the UE determines that the random access preamble index in the RAR message is the same as the preamble index it sent in Msg1, and successfully receives the RAR message, obtaining the configuration information in the RAR message, such as TAC and uplink grant information.

[0109] The UE obtains the TA adjustment value TA_new using the TA extension command in DCI 1_0 and the TAC in the RAR message. That is, TA_new = TA_expand_factor (6 bits) + TAC (12 bits). In other words, TA_new is an 18-bit code composed of the 6-bit code of TA_expand_factor and the 12-bit code of TAC. For example, the 6-bit code of TA_expand_factor is the high-order bit, and the 12-bit code of TAC is the low-order bit. In the combined 18-bit code, the highest bit is the sign bit, and the remaining 17 bits are the code corresponding to TA, with a granularity of 0.509ns. Taking a positive sign as an example, TA_new = the low 17-bit code value × 0.509ns. The UE uses TA_new to adjust the uplink timing when transmitting uplink data next time.

[0110] Meanwhile, the UE uses the frequency adjustment command in DCI 1_0 to adjust the uplink carrier frequency. The highest bit of the 8-bit code in the frequency adjustment command indicates the positive or negative sign, and the remaining 7 bits indicate the absolute value of the frequency offset with a granularity of 0.1ppm. Taking the sign as positive as an example, Fre_Offset = lower 7 bits of the code value × 0.1ppm. The UE uses Fre_Offset to adjust the uplink carrier frequency when it sends uplink data again.

[0111] S105, the UE sends a third message (Msg3) based on the adjusted uplink timing and frequency. Correspondingly, the network device receives the third message.

[0112] The UE determines the time and frequency resources for transmitting Msg3 based on TA_new, frequency offset Fre_Offset, and uplink grant information in Msg2, and then uses the determined time and frequency resources to transmit Msg3.

[0113] In one possible implementation, Msg3 is primarily used to carry the UE's initial access request message, such as an RRC connection request message (RRCSetupRequest), which contains at least a Non-Access Stratum (NAS) UE identifier (e.g., abbreviated Temporary Mobile Subscriber Identity (S-TMSI) or a random value), which is contained in the Common Control Channel Service Data Unit (CCCH SDU).

[0114] S106, the network device sends a fourth message (Msg4), which carries the residual frequency error TE_res and residual timing error FE_res obtained based on the received third message. The corresponding UE receives the fourth message.

[0115] After receiving Msg3, the gNB calculates the residual timing error TE_res based on the expected reception timing and the actual reception timing, and calculates the residual frequency error FE_res based on the expected reception frequency and the actual reception frequency, and fills TE_res and FE_res into the MAC layer control element (CE) of Msg4.

[0116] Furthermore, if the Msg3 received by the gNB contains a CCCH SDU (which contains a NAS UE identifier), then the gNB contains a MAC CE for UE contention resolution in the MAC layer Protocol Data Unit (PDU) of Msg4, and this MAC CE is the CCCH SDU contained in Msg3.

[0117] In one exemplary embodiment, such as Figure 6 As shown, in the MAC PDU subheader, a reserved LCID identifier (such as 100111) is used to identify the MAC CE dedicated to timing and frequency compensation. That is, the LCID identifier (such as 100111) indicates that the MAC CE contains TE_res and FE_res.

[0118] like Figure 6 As shown, the field used to carry TE_res occupies 8 bits, of which 1 bit (such as the most significant bit) represents the positive or negative sign, and the remaining 7 bits represent the absolute value of TE_res, with a granularity of 0.509ns. The field used to carry FE_res occupies 6 bits, of which 1 bit (such as the most significant bit) represents the positive or negative sign, and the remaining 5 bits represent the absolute value of FE_res, with a granularity of 0.1ppm.

[0119] S107, the UE transmits uplink data based on the adjusted TA and frequency using residual timing and frequency errors. The corresponding network equipment receives the uplink data.

[0120] The uplink data can be Msg4-ACK, used to confirm that Msg4 has been successfully received, or other uplink data Msg5; this application does not impose any restrictions on this.

[0121] After receiving Msg4, the UE extracts the contention resolution identifier and compares it with the identifier it sent in Msg3. If the identifiers are the same, the contention resolution is confirmed to be successful, and the TE_res and FE_res carried in Msg4 are used to adjust the currently used TA and frequency.

[0122] The adjusted TA is TA_final = TA_new + TE_res, and the adjusted frequency is FO_final = Fre_Offset + FE_res.

[0123] The UE sends uplink data, such as Msg4-ACK or Msg5, based on the final TA and frequency offset.

[0124] The wireless communication method provided in this embodiment involves the gNB calculating the TA adjustment value and frequency offset based on the received Msg1, and dividing the TA adjustment value into two parts, such as a first TA and a second TA. The first TA and the frequency offset are multiplexed and scheduled in the DCI of Msg2 and transmitted to the UE with unavailable or inaccurate GNSS. The second TA is transmitted to the corresponding UE through the TAC in Msg2. The UE uses the first and second TAs, as well as the frequency offset, to transmit Msg3. Further, after receiving Msg3, the gNB calculates the residual timing error and residual frequency error, and sends Msg4 carrying these errors to the UE. After receiving Msg4, the UE further applies the residual timing error to adjust the currently used uplink timing compensation TA, and applies the residual frequency error to adjust the uplink carrier frequency. Thus, by adjusting the time-frequency position of the UE's uplink transmission through a two-stage adjustment mechanism, the timing and frequency synchronization capability between the UE with unavailable or inaccurate GNSS and the gNB is improved, thereby reducing the random access latency and failure rate of such UEs.

[0125] Moreover, this method extends the TA of the GNSS less UE by reusing the DCI of the Msg2 scheduling and adds a frequency adjustment command. Therefore, only one TAC command needs to be sent in Msg2. At the same time, the residual timing error and residual frequency error added in Msg4 can be accurately compensated. Only one PRACH procedure needs to be executed, occupying only one PRACH opportunity, which improves resource utilization.

[0126] In another exemplary embodiment, to enhance the network's ability to identify UEs with unavailable or inaccurate GNSS (GNSS lessUE), the RA-RNTI calculation is extended by introducing a GNSS state factor into the RA-RNTI calculation formula. The GNSS state factor characterizes the UE's GNSS state, which includes whether GNSS is temporarily unavailable or inaccurate, or whether GNSS capability is normal. Figure 7 As shown, this method can be applied to Figure 1 The communication system shown may include the following steps:

[0127] S201, the network device broadcasts a first system message (such as SIB1). The corresponding UE receives the first system message.

[0128] The first system message carries the preamble index range corresponding to the UE in different GNSS states.

[0129] Static partitioning of the preamble and broadcasting of the partitioning results in SIB1: For example, preambleindex0~A: reserved for GNSS less UEs, i.e. UEs whose GNSS is temporarily unavailable or inaccurate; preambleindexAB: reserved for UEs with normal GNSS capability (or legacy UEs); preambleindexB-63: reserved for special scenarios such as Msg3 retransmission.

[0130] The partition size of the preamble is configurable, or can be dynamically adjusted based on the proportion of UE types in the network. The size of each partition is configurable, or can be dynamically adjusted based on the proportion of GNSS status types of UEs in the network.

[0131] In S202, the UE sends a first message (Msg1), which carries a preamble index that matches the UE's GNSS state. The corresponding network device receives the first message.

[0132] The GNSS less UE randomly selects a preamble index from 0 to A and sends it to the network device via Msg1. At the same time, the UE calculates its own RA-RNTI.

[0133] Preferably, a GNSS state factor is introduced into the calculation formula of RA-RNTI, and the calculation formula is as follows:

[0134] RA-RNTI-GNSS=(1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×preamble index)mod65535 (3)

[0135] Among them, RA-RNTI-GNSS represents RA-RNTI after the introduction of GNSS state factor. The newly added GNSS state-related item is 14×80×8×preamble index, and the preamble index is the preamble index selected by GNSS less UE.

[0136] s_id is the index of the first symbol in the PRACH Occasion;

[0137] t_id is the first slot index of the PRACH occasion in the system frame;

[0138] f_id is the frequency domain index of PRACH Occasion;

[0139] ul_carrier_id is the uplink carrier identifier used for random access preamble transmission. 0: indicates NUL (Normal Uplink) carrier, 1: indicates SUL (Supplementary Uplink) carrier;

[0140] mod represents the modulo operation, and mod65535 means performing a remainder operation of 65535 on the calculation result.

[0141] GNSS less UE can calculate its own RA-RNTI according to the above formula (3) based on its selected preamble index.

[0142] Both the UE and the network side use the above formula (3) to calculate RA-RNTI-GNSS, thereby ensuring that the RA-RNTI-GNSS calculated by the UE and the network side are equal. For example, the above formula (3) can be notified to the UE through pre-configuration or configuration, or the UE can also write the above calculation formula (3) into the communication code. This application does not impose any special restrictions on this.

[0143] S203, the network device sends DCI 1_0 for scheduling Msg2 transmission. The corresponding UE receives DCI 1_0.

[0144] DCI 1_0 uses RA-RNTI with GNSS state factors for scrambling and includes TA extension commands and frequency adjustment commands.

[0145] After receiving MSg1, the gNB parses the preamble index sent by the UE. If the preamble index is in a partition reserved for GNSS less UE, the RA-RNTI-GNSS corresponding to the UE is calculated according to the above formula (3). If the preamble index does not belong to a partition reserved for GNSS less UE, the RA-RNTI is calculated in the original way.

[0146] The RA-RNTI-GNSS of the GNSS less UE calculated by the gNB is used to scramble the CPC of DCI 1_0 used to schedule Msg2 transmission. Simultaneously, the reserved bits in this DCI 1_0 are reused to carry TA extension commands and frequency adjustment commands. See details... Figure 6 The frame format of DCI 1_0 is shown.

[0147] For the meaning and function of TA extended commands and frequency adjustment commands, please refer to [link to documentation]. Figure 4The relevant descriptions in S102 of the illustrated embodiment will not be repeated here.

[0148] S204, the network device sends a second message (Msg2) to the UE. The corresponding UE receives the second message.

[0149] Send Msg2 on the PDSCH resource scheduled by DCI 1_0. Msg2 contains a Timing Advance Command (TAC), which contains a second TA and occupies 12 bits.

[0150] S205, after the UE successfully descrambles DCI 1_0, it receives the second message, obtains the TA extension command and frequency adjustment command in DCI 1_0, and obtains the TAC in the second message.

[0151] After receiving DCI 1_0 scrambled with RA-RNTI-GNSS, the UE parses out the corresponding RA-RNTI-GNSS and compares it with its own RA-RNTI-GNSS. If the scrambled RA-RNTI-GNSS is the same as the UE's RA-RNTI-GNSS, the UE receives the RAR message in the PDCCH. The UE parses the RAPID in the RAR message. If the RAPID is the same as the preambleindex sent by the UE in Msg1, the UE confirms successful reception of the RAR and can obtain the configuration information in the RAR, including TAC.

[0152] If the UE resolves that the RA-RNTI-GNSS of DCI 1_0 is different from its own RA-RNTI-GNSS, then descrambling will fail and the UE will not receive subsequent transmitted RAR messages.

[0153] S206, the UE uses the TA extended command and TAC to adjust the uplink timing, and applies the frequency adjustment command to adjust the uplink carrier frequency.

[0154] S207, the UE sends a third message (Msg3) based on the adjusted uplink timing and frequency. Correspondingly, the network device receives the third message.

[0155] In step S208, the network device sends a fourth message (Msg4), which carries the residual frequency error TE_res and residual timing error FE_res obtained based on the received third message. The corresponding UE receives the fourth message.

[0156] S209, the UE transmits uplink data based on the adjusted TA and frequency using residual timing and frequency errors. The corresponding network equipment receives the uplink data.

[0157] In this embodiment, S206~S209 and Figure 4 The implementation process of S104~S107 in the illustrated embodiment is the same, and will not be repeated here.

[0158] The wireless communication method provided in this embodiment divides UEs into two categories based on GNSS status: GNSS-enabled UEs and GNSS-inaccessible or inaccurate UEs (i.e., GNSS-less UEs). Correspondingly, different preamble ranges are configured for the two types of UEs. When a GNSS-less UE performs random access, a preamble is selected from the preamble range corresponding to the GNSS-less UE and sent to the network side. The network side identifies the UE's GNSS status based on the preamble. For GNSS-less UEs, the network side applies the RA-RNTI calculation formula, which incorporates the GNSS status factor, to obtain the corresponding RA-RNTI-GNSS. The RA-RNTI-GNSS is then used to scramble the DCI 1_0 of the scheduled Msg2 transmission. Only when the corresponding UE can successfully descramble will it continue to receive subsequent RAR messages, thereby enhancing the network side's ability to identify GNSS-less UEs. This allows for TA extension and the addition of frequency adjustment commands for such UEs, shortening the random access time of GNSS-less UEs and improving their random access success rate.

[0159] It should be understood that Figures 1 to 7 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 1 to 7 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0160] The above text combined Figures 1 to 7 This document describes in detail the wireless communication method provided in the embodiments of this application. The following will combine... Figures 8 to 9 The device embodiments of this application are described in detail below. It should be understood that the communication device of this application embodiment can execute the various wireless communication methods described in the foregoing embodiments of this application. That is, the specific working processes of the various products described below can be referred to the corresponding processes in the foregoing method embodiments.

[0161] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the network device may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0162] Figure 8 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 8 As shown, the communication device may include a communication module 101. The communication module 101 can implement corresponding communication functions, which can be internal communication functions of the communication device or communication functions between the communication device and other devices. Optionally, the communication module 101 may also be referred to as a communication interface or transceiver module. Optionally, the communication device further includes a processing module 102. The processing module 102 can implement corresponding processing functions.

[0163] Optionally, the communication device further includes a storage module, which can be used to store instructions and / or data; the processing module 102 can read the instructions and / or data in the storage module so that the communication device can implement the aforementioned method embodiments.

[0164] In one possible design, the communication device may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device can be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.

[0165] For example, the communication module 101 is configured to: send a first message, the first message including GNSS status information of the terminal device, the GNSS status information indicating that the GNSS of the terminal device is unavailable or inaccurate; receive downlink control information from the network device, the downlink control information being used to schedule the transmission of a second message, the downlink control information including a timing advance extension command and a frequency adjustment command; receive a second message from the network device, the second message containing a timing advance command; send a third message based on the adjusted uplink timing and the adjusted uplink carrier frequency, the third message including an initial access connection request; receive a fourth message from the network device, the fourth message including residual timing error and residual frequency error obtained based on the received information of the third message; and send uplink data based on the time-frequency resources adjusted using the residual timing error and residual frequency error.

[0166] Processing module 102 is used to: adjust uplink timing based on timing advance extension command and timing advance command; and adjust uplink carrier frequency based on frequency adjustment command.

[0167] In one possible implementation, reserved bits for downlink control information are used to carry timing advance extension commands and frequency adjustment commands.

[0168] In one possible implementation, when the processing module 102 adjusts the uplink timing based on the timing advance extension command and the timing advance command, it specifically performs the following steps: concatenating all bits of the timing advance extension command with all bits of the timing advance command into a single code; calculating the TA value corresponding to the concatenated code; and adjusting the uplink timing according to the TA value.

[0169] In one possible implementation, the fourth message includes a MAC CE for carrying residual timing errors and residual frequency errors.

[0170] In one possible implementation, the LCID identifier reserved in the MAC layer protocol data unit subheader of the fourth message is used to identify the MAC CE used to carry residual timing error and residual frequency error.

[0171] In one possible implementation, the GNSS status information is a preamble that matches the GNSS status of the terminal device; the first preamble range is a preamble range assigned to terminal devices where GNSS is unavailable or inaccurate, and the second preamble range is a preamble range assigned to terminal devices where GNSS is available, and the first preamble range and the second preamble range do not overlap.

[0172] In one possible implementation, the downlink control information is scrambled using RA-RNTI-GNSS, which is obtained by adding a GNSS state factor to RA-RNTI. The GNSS state factor is associated with the preamble corresponding to the terminal equipment where GNSS is unavailable or inaccurate.

[0173] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0174] In one possible design, the communication device may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device can be used to perform the steps or processes executed by the network device in any of the above method embodiments.

[0175] For example, the communication module 101 is configured to: receive a first message from a terminal device, the first message including GNSS status information of the terminal device, the GNSS status information indicating that the GNSS of the terminal device is unavailable or inaccurate; send downlink control information, the downlink control information being used to schedule the transmission of a second message, the downlink control information including a timing advance extension command and a frequency adjustment command; send a second message, the second message including a timing advance command; receive a third message from the terminal device, the third message including an initial access connection request; send a fourth message, the fourth message including residual timing error and residual frequency error obtained based on the received information of the third message; and receive uplink data from the terminal device, the uplink data being transmitted based on time-frequency resources adjusted using the residual timing error and residual frequency error.

[0176] The processing module 102 is configured to: obtain the TA value and frequency adjustment value corresponding to the terminal device that sent the first message based on the relevant information of the received first message, and generate a timing advance extension command and a TAC based on the TA value; at the same time, generate a frequency adjustment command based on the frequency adjustment value; and obtain a residual timing error based on the error between the actual reception timing and the expected reception timing of the third message; and obtain a residual frequency error based on the error between the actual reception frequency and the expected reception frequency of the third message.

[0177] In one possible implementation, reserved bits for downlink control information are used to carry timing advance extension commands and frequency adjustment commands.

[0178] In one possible implementation, the fourth message includes a MAC CE for carrying residual timing errors and residual frequency errors.

[0179] In one possible implementation, the LCID identifier reserved in the MAC layer protocol data unit subheader of the fourth message is used to identify the MAC CE used to carry residual timing error and residual frequency error.

[0180] In one possible implementation, the GNSS status information is a preamble that matches the GNSS status of the terminal device; the first preamble range is a preamble range assigned to terminal devices where GNSS is unavailable or inaccurate, and the second preamble range is a preamble range assigned to terminal devices where GNSS is available, and the first preamble range and the second preamble range do not overlap.

[0181] In one possible implementation, the downlink control information is scrambled using RA-RNTI-GNSS, which is obtained by adding a GNSS state factor to RA-RNTI. The GNSS state factor is associated with the preamble corresponding to the terminal equipment where GNSS is unavailable or inaccurate.

[0182] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0183] Figure 9 This is another schematic block diagram of the communication device provided in the embodiments of this application. The communication device may be a chip, chip system, or processor, etc., in a terminal device or network device that implements the above-described methods. This communication device can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0184] like Figure 9 As shown, the communication device may include one or more processors 201, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 201 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device (e.g., base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0185] In an alternative design, the processor 201 may also store instructions and / or data that can be executed by the processor 201 to cause the communication device to perform the methods described in the above method embodiments.

[0186] In another alternative design, the communication device may include a communication interface 202 for implementing receiving and transmitting functions. For example, the communication interface 202 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0187] Optionally, the communication device may include one or more memories 203, which may store instructions that can be executed on the processor 201, causing the communication device to perform the methods described in the above method embodiments. Optionally, the memories 203 may also store data. Optionally, the processor 201 may also store instructions and / or data. The processor 201 and the memories 203 may be provided separately or integrated together.

[0188] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0189] In one implementation, the communication device may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 201 may be used to execute instructions stored in the memory 203, and when the processor 201 executes the instructions stored in the memory, the processor 201 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0190] In another implementation, the communication device may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 201 may be used to execute instructions stored in the memory 203, and when the processor 201 executes the instructions stored in the memory, the processor 201 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0191] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0192] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0193] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0194] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0195] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned network device and terminal device.

[0196] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0197] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the network device or terminal device in any of the foregoing method embodiments.

[0198] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0199] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0200] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0201] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0202] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0203] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A wireless communication method, characterized in that, The method, executed by a terminal device, includes: Send a first message, the first message including a first preamble randomly selected by the terminal device from a first preamble range, the first preamble indicating that the GNSS of the terminal device is unavailable or inaccurate, and the first preamble range is a preamble range allocated for terminal devices with unavailable or inaccurate GNSS. The downlink control information received from the network device is used to schedule the transmission of the second message. The downlink control information includes a timing advance extension command and a frequency adjustment command. The downlink control information is scrambled using RA-RNTI-GNSS, which is obtained by adding a GNSS state factor associated with the first preamble to RA-RNTI. When the RA-RNTI-GNSS calculated based on the first preamble is the same as the scrambling code RA-RNTI-GNSS of the downlink control information, the second message from the network device is received, and the second message contains a timing advance command. All bits of the timing advance extension command are concatenated with all bits of the timing advance command to form a code. The TA value is determined based on the concatenated code. The uplink carrier frequency is adjusted based on the frequency adjustment command. The TA value is used to adjust the uplink timing. A third message is sent based on the adjusted uplink timing and the adjusted uplink carrier frequency, the third message including an initial access connection request; Receive a fourth message from the network device, the fourth message including residual timing error and residual frequency error determined based on the reception information of the third message; Uplink data is transmitted based on the time-frequency resources adjusted using the residual timing error and the residual frequency error. The RA-RNTI-GNSS satisfies the following calculation formula: RA-RNTI-GNSS=(1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×preamble index)mod65535 s_id is the index of the first symbol of the random access opportunity; t_id is the index of the first slot of the random access opportunity in the system frame; f_id is the frequency domain index of the random access opportunity; ul_carrier_id is the uplink carrier identifier used for random access preamble transmission; preamble index is the preamble selected by the terminal device when GNSS is unavailable or inaccurate; mod65535 indicates that the calculation result is modulo 65535.

2. The method according to claim 1, characterized in that, The reserved bits of the downlink control information are used to carry the timing advance extension command and the frequency adjustment command.

3. The method according to claim 1 or 2, characterized in that, The timing advance extension command occupies 6 bits, one of which represents positive or negative, and the remaining bits are the TA extension field with a granularity of 0.509ns.

4. The method according to claim 1 or 2, characterized in that, The frequency adjustment command occupies 8 bits, one of which indicates positive or negative, and the remaining bits are the code corresponding to the absolute value of the frequency offset, with a granularity of 0.1ppm.

5. The method according to claim 1 or 2, characterized in that, The fourth message includes a MAC CE for carrying the residual timing error and the residual frequency error.

6. The method according to claim 5, characterized in that, The LCID identifier reserved in the MAC layer protocol data unit subheader of the fourth message is used to identify the MAC CE used to carry the residual timing error and the residual frequency error.

7. The method according to claim 5, characterized in that, The field carrying the residual timing error occupies 8 bits, one of which indicates positive or negative, and the remaining bits indicate the absolute value of the residual timing error, with a granularity of 0.509 ns.

8. The method according to claim 5, characterized in that, The field carrying the residual frequency error occupies 6 bits, one of which indicates positive or negative, and the remaining bits indicate the absolute value of the residual frequency error with a granularity of 0.1 ppm.

9. The method according to claim 1 or 2, characterized in that, The second preamble range is the preamble range allocated to GNSS-enabled terminal devices, and the first preamble range and the second preamble range do not overlap.

10. A wireless communication method, characterized in that, Performed by a network device, the method includes: Receive a first message from a terminal device, the first message including a first preamble randomly selected by the terminal device from a first preamble range, the first preamble indicating that the GNSS of the terminal device is unavailable or inaccurate, the first preamble range being a preamble range allocated for terminal devices with unavailable or inaccurate GNSS. Send downlink control information, which is used to schedule the transmission of the second message. The downlink control information includes a timing advance extension command and a frequency adjustment command. The downlink control information is scrambled using RA-RNTI-GNSS, which is obtained by adding a GNSS state factor associated with the first preamble to RA-RNTI. Send a second message, which contains a time advance command; The terminal device receives a third message, which includes an initial access connection request. This third message is sent by the terminal device after receiving the second message, on resources corresponding to the adjusted uplink timing and the adjusted uplink carrier frequency. The terminal device receives the second message when the RA-RNTI-GNSS calculated based on the first preamble is the same as the scrambling code RA-RNTI-GNSS of the downlink control information. The adjusted uplink timing is obtained by concatenating all bits of the timing advance command with all bits of the timing advance command into a single code, and adjusting the uplink timing based on the TA value corresponding to the concatenated code. The adjusted uplink carrier frequency is obtained after adjustment based on the frequency adjustment command. Send a fourth message, the fourth message including residual timing error and residual frequency error determined based on the received information of the third message; Receive uplink data from the terminal device, the uplink data being transmitted based on time-frequency resources adjusted using the residual timing error and the residual frequency error; The RA-RNTI-GNSS satisfies the following calculation formula: RA-RNTI-GNSS=(1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id+14×80×8×preamble index)mod65535 s_id is the index of the first symbol of the random access opportunity; t_id is the index of the first slot of the random access opportunity in the system frame; f_id is the frequency domain index of the random access opportunity; ul_carrier_id is the uplink carrier identifier used for random access preamble transmission; preamble index is the preamble selected by the terminal device when GNSS is unavailable or inaccurate; mod65535 indicates that the calculation result is modulo 65535.

11. The method according to claim 10, characterized in that, The reserved bits of the downlink control information are used to carry the timing advance extension command and the frequency adjustment command.

12. The method according to claim 10 or 11, characterized in that, The timing advance extension command occupies 6 bits, one of which represents positive or negative, and the remaining bits are the TA extension field with a granularity of 0.509ns.

13. The method according to claim 10 or 11, characterized in that, The frequency adjustment command occupies 8 bits, one of which indicates positive or negative, and the remaining bits are the code corresponding to the absolute value of the frequency offset, with a granularity of 0.1ppm.

14. The method according to claim 10, characterized in that, The fourth message includes a MAC CE for carrying the residual timing error and the residual frequency error.

15. The method according to claim 14, characterized in that, The LCID identifier reserved in the MAC layer protocol data unit subheader of the fourth message is used to identify the MACCE used to carry the residual timing error and the residual frequency error.

16. The method according to claim 15, characterized in that, The field carrying the residual timing error occupies 8 bits, one of which indicates positive or negative, and the remaining bits indicate the absolute value of the residual timing error, with a granularity of 0.509 ns.

17. The method according to claim 15, characterized in that, The field carrying the residual frequency error occupies 6 bits, one of which indicates positive or negative, and the remaining bits indicate the absolute value of the residual frequency error with a granularity of 0.1 ppm.

18. The method according to claim 10 or 11, characterized in that, The second preamble range is the preamble range allocated to GNSS-enabled terminal devices, and the first preamble range and the second preamble range do not overlap.

19. A communication device, characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, the processor executing the program or instructions to cause the device to perform the method as described in any one of claims 1 to 18.

20. A computer-readable storage medium having a computer program or instructions stored thereon, characterized in that, When the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 18.

Images