Method, apparatus and device for transmitting GNSS validity period and storage medium

Abstract

The application discloses a GNSS validity period transmission method and device, equipment and a storage medium, and relates to the field of communication. The method comprises the following steps: a first media access control (MAC) control element (CE) is sent, and the first MAC CE carries a GNSS validity period. Therefore, the terminal device and the network device can share the accurate GNSS validity period in time.

Description

Technical Field

[0001] This application relates to the field of communications, and in particular to a method, apparatus, device, and storage medium for transmitting GNSS data during its validity period. Background Technology

[0002] The Global Navigation Satellite System (GNSS) position fix obtained by terminal devices has an expiration date. After the expiration date, the GNSS position fix times out, and the terminal device needs to reacquire the GNSS position fix. Furthermore, some Internet of Things (IoT) terminal devices do not support simultaneous GNSS reception and Long Term Evolution (LTE) transmission and reception, leading to issues with sharing the GNSS position fix validity period between terminal devices and network devices.

[0003] To enable terminal devices and network devices to share accurate GNSS validity periods, related technologies have considered the design of terminal devices reporting GNSS validity periods, but there is no clear solution on how to specifically report GNSS validity periods. Summary of the Invention

[0004] This application provides a method, apparatus, device, and storage medium for transmitting GNSS data during its validity period. The technical solution is as follows:

[0005] According to one aspect of this application, a method for transmitting GNSS data during its validity period is provided, the method being performed by a terminal device, the method comprising:

[0006] Send a first Medium Access Control (MAC) control element (CE), the first MAC CE carrying the GNSS validity period.

[0007] According to one aspect of this application, a method for transmitting GNSS validity period is provided, the method being performed by a network device, the method comprising:

[0008] Receive the first MAC CE, which carries the GNSS validity period.

[0009] According to one aspect of this application, a GNSS-valid transmission device is provided, the device comprising:

[0010] The first transmitting module is used to transmit a first MAC CE, which carries the GNSS validity period.

[0011] According to one aspect of this application, a GNSS-valid transmission device is provided, the device comprising:

[0012] The second receiving module is used to receive the first MAC CE, which carries the GNSS validity period.

[0013] According to one aspect of this application, a terminal device is provided, the terminal device comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the GNSS validity transmission method as described above.

[0014] According to one aspect of this application, a network device is provided, the network device comprising: a processor; a transceiver connected to the processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the GNSS validity transmission method as described above.

[0015] According to one aspect of this application, a computer-readable storage medium is provided that stores executable instructions, which are loaded and executed by a processor to implement the GNSS validity transmission method as described above.

[0016] According to one aspect of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, a processor of a computer device reading the computer instructions from the computer-readable storage medium, the processor executing the computer instructions, causing the computer device to perform a transmission method for GNSS validity as described above.

[0017] According to one aspect of this application, a chip is provided, the chip including programmable logic circuitry and / or program instructions, which, when the chip is running, are used to implement the GNSS validity transmission method as described above.

[0018] According to one aspect of this application, a computer program is provided, the computer program including computer instructions, wherein a processor of a computer device executes the computer instructions, causing the computer device to perform the GNSS validity transmission method as described above.

[0019] The technical solutions provided in this application have at least the following beneficial effects:

[0020] By sending the GNSS validity period in the MAC CE, the terminal device and network device can share the accurate GNSS validity period in a timely manner, which helps to improve the accuracy and effectiveness of positioning methods based on GNSS technology. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 The present application provides a schematic diagram of an NTN communication system according to some illustrative embodiments.

[0023] Figure 2 The present application provides a schematic diagram of an NTN communication system according to some illustrative embodiments.

[0024] Figure 3 The present application provides a schematic diagram of an NTN communication system according to some illustrative embodiments.

[0025] Figure 4 The present application provides a schematic diagram of an NTN communication system according to some illustrative embodiments.

[0026] Figure 5 The present application provides a schematic diagram of an NTN communication system according to some illustrative embodiments.

[0027] Figure 6 The illustration shows a flowchart of a GNSS validity period transmission method provided by some illustrative embodiments of this application;

[0028] Figure 7 The illustration shows a flowchart of a GNSS validity period transmission method provided by some illustrative embodiments of this application;

[0029] Figure 8 The illustration shows a flowchart of a GNSS validity period transmission method provided by some illustrative embodiments of this application;

[0030] Figure 9 The illustration shows a flowchart of a GNSS validity period transmission method provided by some illustrative embodiments of this application;

[0031] Figure 10 The illustration shows a flowchart of a GNSS validity period transmission method provided by some illustrative embodiments of this application;

[0032] Figure 11 The diagram illustrates a structural block diagram of a GNSS transmission device according to some illustrative embodiments of this application;

[0033] Figure 12 The diagram illustrates a structural block diagram of a GNSS transmission device according to some illustrative embodiments of this application;

[0034] Figure 13 The diagram shows a structural schematic of a communication device provided by some illustrative embodiments of this application. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0036] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The singular forms “a,” “the,” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

[0037] It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0038] First, the relevant technologies involved in the embodiments of this application will be introduced:

[0039] (1) Communication Scenarios

[0040] Communication system scenarios include terrestrial networks (TN) and non-terrestrial networks (NTN). NTN typically provides communication services to terrestrial users via satellite. Current NTN systems include New Radio (NR)-NTN and Internet of Things (IoT)-NTN systems. This application primarily concerns NTN, which, simply put, provides wireless resources to terminal devices via satellite or Unmanned Aerial System (UAS) rather than through terrestrial base stations. This application uses satellite-based wireless resource provision to terminal devices as an example for illustration.

[0041] Communication satellites are classified according to their orbital altitude into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites, Highly Elliptical Orbit (HEO) satellites, and so on. Currently, research primarily focuses on LEO and GEO.

[0042] 1. LEO

[0043] Low Earth orbit (LEO) satellites range in altitude from 500km to 1500km, with corresponding orbital periods of approximately 1.5 to 2 hours. The signal propagation delay for single-hop communication between users is generally less than 20ms. The maximum satellite visibility time is 20 minutes. The short signal propagation distance and low link loss mean that the requirements for the transmission power of user terminal equipment are not high.

[0044] 2. GEO

[0045] A geostationary orbit satellite, with an orbital altitude of 35,786 km, orbits the Earth every 24 hours. The signal propagation delay for single-hop communication between users is typically 250 ms.

[0046] To ensure satellite coverage and improve the overall capacity of the satellite communication system, satellites use multi-beam coverage to cover the ground. A single satellite can generate dozens or even hundreds of beams to cover the ground; a single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0047] Table 1 shows the satellite altitude, orbit, and coverage area of ​​a typical NTN network:

[0048] Table 1. Satellite altitude, orbit, and coverage area of ​​the NTN network.

[0049]

[0050]

[0051] For example, Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Figure 1 As shown, this communication system includes terminal device 101 and satellite 102, which can communicate wirelessly. The network formed between terminal device 101 and satellite 102 can also be called an NTN. Figure 1 In the architecture of the communication system shown, satellite 102 can function as a base station, and terminal device 101 and satellite 102 can communicate directly. In this communication system architecture, satellite 102 can be referred to as a network device. In some cases, the communication system may include multiple network devices (i.e., satellite 102), and each network device may include a number of other terminal devices within its coverage area; this application does not limit this.

[0052] For example, Figure 2 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application. For example... Figure 2 As shown, the communication system includes terminal device 201, satellite 202, and base station 203. Terminal device 201 and satellite 202 can communicate wirelessly, and satellite 202 can communicate with base station 203. The network formed by terminal device 201, satellite 202, and base station 203 can also be called an NTN. Figure 2 In the architecture of the communication system shown, satellite 202 may not function as a base station, and communication between terminal device 201 and base station 203 requires relay through satellite 202. In this communication system architecture, base station 203 can be referred to as a network device. In some embodiments, the communication system may include multiple network devices (i.e., base stations 203), and the coverage area of ​​each network device may include other numbers of terminal devices; this application does not limit this.

[0053] For example, Figure 3This is a schematic diagram of an NTN communication scenario provided in an embodiment of this application. The transmission link between the terminal device 301 and the serving satellite 302 is a service link, and the transmission link between the serving satellite 302 and the gateway 303 is a feeder link. Both the service link and the feeder link may change over time. The data network 304 can be a private network, such as a local area network; it can also be an external network not controlled by the operator, such as the Internet; or it can be a proprietary network jointly deployed by the operator, such as an IP Multimedia Core Network Subsystem (IMS). The gateway 303 can access the data network 304.

[0054] (2) Global Navigation Satellite System (GNSS)

[0055] GNSS refers to all systems that achieve positioning through satellite signals, including global systems, regional systems, and augmented systems. Simply put, GNSS can provide users with all-weather three-dimensional coordinates, velocity, and time information from any location on the Earth's surface or in near-Earth space. GNSS can use observations such as pseudorange, ephemeris, and satellite launch time from a set of satellites, as well as user clock bias, to locate the user's terminal equipment.

[0056] When a terminal device is positioned using GNSS, the GNSS location fix obtained by the terminal device has a validity period. After the validity period expires, the GNSS location fix times out, and the terminal device needs to re-obtain the GNSS location fix.

[0057] Furthermore, some Internet of Things (IoT) terminal devices do not support simultaneous GNSS reception and Long Term Evolution (LTE) transmission and reception, which leads to problems in the sharing and synchronization of GNSS validity between terminal devices and network devices, thereby affecting the accuracy and effectiveness of GNSS positioning.

[0058] IoT terminal devices include at least one of the following: Bandwidth Reduction and Low Complexity UE (BL UE), Coverage Enhancement Mode UE (CE Mode), and Narrow Band Internet of Things UE (NB-IoT UE).

[0059] The relevant technologies have considered the design of terminal devices reporting GNSS validity period, but there is no clear solution on how to report the specific GNSS validity period.

[0060] This application proposes a method for transmitting GNSS validity period, which supports terminal devices in reporting GNSS validity period, enabling network devices and terminal devices to share accurate GNSS validity period duration.

[0061] Figure 4 A schematic diagram of an NTN communication system provided by an exemplary embodiment of this application is shown. The communication satellites in this NTN system are transparent payload satellites. Figure 4 As shown, the NTN system includes: terminal equipment 10, satellite 20, NTN gateway 30, access network equipment 40, and core network equipment 50.

[0062] Terminal device 10 and access network device 40 can communicate via an air interface (such as a Uu interface). Figure 4 In the illustrated architecture, the access network device 40 can be deployed on the ground. Uplink and downlink communication between the terminal device 10 and the access network device 40 can be relayed via satellite 20 and NTN gateway 30 (usually located on the ground). Taking uplink transmission as an example, the terminal device 10 sends the uplink signal to satellite 20, satellite 20 forwards the uplink signal to NTN gateway 30, and then NTN gateway 30 forwards the uplink signal to access network device 40. Subsequently, access network device 40 sends the uplink signal to core network device 50. Taking downlink transmission as an example, the downlink signal from core network device 50 is sent to access network device 40, access network device 40 sends the downlink signal to NTN gateway 30, NTN gateway 30 forwards the downlink signal to satellite 20, and then satellite 20 forwards the downlink signal to terminal device 10.

[0063] In this NTN system, satellite 20 has the function of frequency conversion and signal amplification. Satellite 20 does not demodulate the signal of access network equipment 40. Satellite 20 is similar to a repeater.

[0064] Figure 5 A schematic diagram of another NTN system provided by an exemplary embodiment of this application is shown, in which the communication satellite is a regenerative payload satellite. Figure 5 As shown, the NTN system includes: terminal equipment 10, satellite 20, NTN gateway 30, and core network equipment 50.

[0065] exist Figure 5 In this architecture, the functions of the access network device 40 are integrated into the satellite 20, meaning that the satellite 20 possesses the functions of the access network device 40. The terminal device 10 and the satellite 20 can communicate via an air interface (such as a Uu interface). The satellite 20 and the NTN gateway 30 (usually located on the ground) can communicate via a satellite radio interface (SRI). In this NTN system, the satellite receives signals, demodulates and decodes them, then re-encodes and modulates them, and transmits the regenerated signals via the satellite frequency band.

[0066] exist Figure 5 In the illustrated architecture, taking uplink transmission as an example, terminal device 10 sends uplink signals to satellite 20, satellite 20 forwards the uplink signals to NTN gateway 30, and then NTN gateway 30 forwards the uplink signals to core network device 50. Taking downlink transmission as an example, downlink signals from core network device 50 are sent to NTN gateway 30, NTN gateway 30 forwards the downlink signals to satellite 20, and then satellite 20 forwards the downlink signals to terminal device 10.

[0067] In the above Figure 4 and Figure 5 In the network architecture shown, access network device 40 is a device used to provide wireless communication services to terminal device 10. Access network device 40 and terminal device 10 can establish a connection to communicate, including signaling and data exchange. There can be multiple access network devices 40, and two access network devices 40 can communicate with each other via wired or wireless means. Terminal device 10 can switch between different access network devices 40, that is, establish connections with different access network devices 40.

[0068] Access network equipment 40 includes, but is not limited to: Evolved Node B (eNB), Radio Network Controller (RNC), Node B (NB), Base Station Controller (BSC), Base Transceiver Station (BTS), Home Base Station (e.g., Home Evolved Node B, or Home Node B, HNB), Baseband Unit (BBU), Access Point (AP) in a Wireless Fidelity (Wi-Fi) system, Wireless Relay Node, Wireless Backhaul Node, Network Equipment, Transmission Point (TP), or Transmission and Reception Point (TRP), etc. It can also be a Next Generation Node B (gNB) or Transmission Point (TRP or TP) in a 5G system, or one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or Transmission Point, such as a Baseband Unit (BBU) or Distributed Unit (DMU). This includes devices such as Units (DUs), base stations in 6G communication systems, Radio Access Network (RAN) equipment, and network slices. A base station is a device deployed in an access network to provide wireless communication functionality to the terminal device 10. Base stations can include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the names of devices with base station functionality may differ; for example, in a 5G NR system, they are called gNodeB or gNB. As communication technologies evolve, the name "base station" may change. For ease of description, in this embodiment, the devices providing wireless communication functionality to the terminal device 10 are collectively referred to as base stations or access network equipment.

[0069] In addition, the terminal device 10 involved in the embodiments of this disclosure may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, as well as various forms of user equipment (UE), mobile station (MS), terminal device, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, and user device. The terminal device 10 includes, but is not limited to: handheld devices, wearable devices, in-vehicle devices, and Internet of Things (IoT) devices, such as: mobile phones, tablets, e-readers, laptops, desktop computers, televisions, game consoles, mobile internet devices (MID), augmented reality (AR) terminals, virtual reality (VR) terminals, mixed reality (MR) terminals, wearable devices, controllers, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wireless terminals in remote medical surgery, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, and wireless local loops. Local loop (WLL) stations, personal digital assistants (PDAs), set-top boxes (STBs), customer premises equipment (CPEs), etc. For ease of description, in this embodiment of the disclosure, the devices mentioned above are collectively referred to as terminal devices. In some instances of this embodiment of the disclosure, "UE" is used to represent "terminal device". In this embodiment of the disclosure, "network device" can be access network equipment (such as a base station) or a satellite.

[0070] Furthermore, taking a 5G NTN system as an example, an NTN system can include multiple satellites 20. One satellite 20 can cover a certain area of ​​the ground, providing wireless communication services to terminal devices 10 in that area. In addition, satellites 20 can orbit the Earth, and by deploying multiple satellites 20, communication coverage of different areas on the Earth's surface can be achieved.

[0071] The technical solutions provided in the embodiments of this application can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Advanced Long Term Evolution (LTE-A) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) system, 5th Generation (5G) mobile communication system, New Radio (NR) system, evolution systems of NR systems, and LTE-based access to unlicensed spectrum. This application can be applied to unlicensed spectrum (LTE-U) systems, NR (NR-based access to unlicensed spectrum) systems, terrestrial networks (TN) systems, non-terrestrial networks (NTN) systems, wireless local area networks (WLAN), wireless Fidelity (Wi-Fi), cellular IoT systems, and cellular passive IoT systems. It can also be applied to subsequent evolutions of 5G NR systems, as well as 6G and subsequent evolutions. In some embodiments of this application, "NR" can also be referred to as a 5G NR system or a 5G system. The 5G mobile communication system can include non-standalone (NSA) and / or standalone (SA) networks.

[0072] The technical solutions provided in the embodiments of this application can also be applied to Machine Type Communication (MTC), Long Term Evolution-Machine (LTE-M) technology, Device to Device (D2D) networks, Machine to Machine (M2M) networks, Internet of Things (IoT) networks, or other networks. IoT networks, for example, can include vehicle-to-everything (V2X) networks. The communication methods in V2X systems are collectively referred to as Vehicle to X (V2X), where X can represent anything. For example, V2X can include Vehicle to Vehicle (V2V) communication, Vehicle to Infrastructure (V2I) communication, Vehicle to Pedestrian (V2P) communication, or Vehicle to Network (V2N) communication, etc.

[0073] The NTN communication system provided in this embodiment can be applied to, but is not limited to, at least one of the following positioning methods: Downlink Time Difference of Arrival (DL-TDOA) positioning method, Uplink Time Difference of Arrival (UL-TDOA) positioning method, and Multi-Round Trip Time (Multi-RTT) positioning method.

[0074] In addition, the terms "network" and "system" are often used interchangeably in this disclosure, but their meanings will be understood by those skilled in the art.

[0075] Figure 6 The illustration shows a flowchart of a GNSS validity transmission method provided by some exemplary embodiments of this application. Taking the method being executed by a terminal device as an example, the method includes at least some of the following steps:

[0076] Step 620: Send the first Medium Access Control (MAC) Control Element (CE), which carries the GNSS validity period.

[0077] GNSS validity period refers to the valid time of GNSS positioning, which can be understood as information related to the valid time of GNSS positioning.

[0078] The first MAC CE is sent from the terminal device to the network device, which includes access network equipment and / or satellite.

[0079] The MAC layer is used to multiplex (or map) multiple logical channels onto the same transport channel and pass the transport block (TB) of the mapped transport channel to the physical layer (PHY).

[0080] The MAC layer includes multiplexing / demultiplexing entities and Logical Channel Prioritization (LCP) entities. These entities are responsible for composing and decomposing MAC Protocol Data Units (PDUs) and performing multiplexing / demultiplexing of data from several logical channels to / from a single transport channel. Simply put, multiplexing refers to the process of mapping multiple logical channels to one transport channel, while demultiplexing refers to the process of mapping one transport channel to multiple logical channels. A MAC PDU can also be understood as a MAC packet data unit or a MAC data packet unit.

[0081] Logical channel priority refers to the logical channel priority allocation process, that is, allocating resources to logical channels according to their logical channel priorities. For example, resources are allocated to logical channels in descending order of logical channel priority. When allocating radio resources for new transmissions, the logical channel priority entity can instruct the multiplexing / demultiplexing entity to generate a MAC PDU from the MAC Service Data Unit (SDU). For the physical layer, a MAC PDU is a transport block, and one transport block includes one MAC PDU.

[0082] A MAC PDU includes a MAC CE, and at least one of the following: a MAC header, a MAC SDU, and padding. The MAC header includes one or more MAC sub-headers. Each MAC sub-header corresponds to a MAC PDU, a MAC CE, or a padding portion. That is, each MAC PDU, each MAC CE, and each padding portion has a one-to-one corresponding MAC sub-header. The lengths of the MAC header, MAC sub-headers, and MAC SDU are variable.

[0083] In summary, the method provided in this embodiment carries the GNSS validity period in the MAC CE for transmission, enabling the terminal device and network device to share the accurate GNSS validity period in a timely manner, which is beneficial to improving the accuracy and effectiveness of positioning methods based on GNSS technology.

[0084] Figure 7 The illustration shows a flowchart of a GNSS validity transmission method provided by some exemplary embodiments of this application. Taking the method being executed by a terminal device as an example, the method includes at least some of the following steps:

[0085] Step 720: Generate the first MAC CE;

[0086] When at least one MAC CE carrying a GNSS validity period is triggered, the terminal equipment generates at least one MAC CE carrying a GNSS validity period through a multiplexing and assembly process.

[0087] A MAC CE carrying the GNSS validity period can also be understood as a MAC CE used to transmit the GNSS validity period, for example, named GNSS validity duration MAC CE. This application does not limit the name.

[0088] The terminal device generates a MAC PDU based on the logical channel priority result. This MAC PDU contains only one MAC CE carrying the GNSS validity period. This MAC CE included in the MAC PDU is the first MAC CE.

[0089] The first MAC CE is any one of at least one MAC CE carrying a GNSS validity period, or one selected according to specific rules (such as priority rules).

[0090] GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period. The start time of the remaining GNSS validity period is the transmission time of the first MAC CE. The start time of the total GNSS validity period is the time when the terminal device acquires GNSS location information. The GNSS expiration period refers to the time during which GNSS location information has expired; its start time is the time when the terminal device acquires GNSS location information, and its end time is the transmission time of the first MAC CE.

[0091] Step 740: Send the first MAC CE;

[0092] If at least one MAC CE carrying the GNSS validity period is triggered, a MAC PDU carrying the first MAC CE is sent.

[0093] In some embodiments, when a terminal device receives GNSS location information, at least one MAC CE carrying the GNSS validity period is triggered.

[0094] In some embodiments, at least one MAC CE carrying the GNSS validity period is triggered, which can be understood as the terminal device being in a state that needs to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state that is preparing to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state that is about to send a MAC CE carrying the GNSS validity period.

[0095] The first MAC CE is sent from the terminal device to the network device, which includes access network equipment and / or satellite.

[0096] If a first uplink resource exists, the first MAC CE is transmitted on that first uplink resource. The first uplink resource is an uplink resource allocated to the terminal device that is idle, unoccupied, or unused, and the data size corresponding to the first MAC CE is less than or equal to the data size corresponding to the first uplink resource. Alternatively, the first uplink resource can be understood as an uplink resource that the terminal device can use to transmit the first MAC CE. Or, it can be understood as an uplink resource allocated to the terminal device that is idle, unoccupied, or unused, and capable of accommodating the first MAC CE. The terminal device directly uses the first uplink resource to transmit a MAC PDU carrying the first MAC CE.

[0097] In some embodiments, the amount of data corresponding to the first MAC CE is less than or equal to the amount of data corresponding to the first uplink resource. This can be understood as the first uplink resource being able to accommodate the first MAC CE, or the first uplink resource being able to accommodate the first MAC CE and its corresponding MAC subheader. It can also be understood as the amount of data corresponding to the first MAC CE being less than or equal to the amount of data that the first uplink resource can carry or the maximum amount of data.

[0098] In some embodiments, the terminal device determines whether a first uplink resource exists based on a logical channel priority result. If the logical channel priority result indicates the existence of a first uplink resource, the terminal device transmits a first MAC CE on the first uplink resource.

[0099] Step 760: Cancel the second MAC CE.

[0100] The second MAC CE is at least one of the MAC CEs carrying a GNSS validity period, other than the first MAC CE.

[0101] In some embodiments, when the first MAC CE is carried in the MAC PDU for transmission, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and ready for transmission, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and about to be transmitted, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is being transmitted, the terminal device cancels all triggered second MAC CEs.

[0102] In some embodiments, when the first MAC CE is carried in the MAC PDU for transmission, the terminal device cancels all triggered MAC CEs (including the first MAC CE and the second MAC CE); or, when the first MAC CE is carried in the MAC PDU and is ready for transmission, the terminal device cancels all triggered MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is about to be transmitted, the terminal device cancels all triggered MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is being transmitted, the terminal device cancels all triggered MAC CEs.

[0103] In some embodiments, the cancellation of MAC CE triggering can be understood as the terminal device being in a state where it does not need to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state where it is not prepared to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state where it is not about to send a MAC CE carrying the GNSS validity period.

[0104] In some embodiments, triggering a MAC CE can be achieved by setting a flag. Cancelling the trigger can be achieved by deleting the flag, meaning that the MAC CE will not be sent again; otherwise, if the flag is not deleted, the MAC CE will be sent again later.

[0105] In summary, the method provided in this embodiment, when there is a first uplink resource available for sending the first MACCE, carries the GNSS validity period in the first MACCE and directly uses the first uplink resource for transmission, thereby improving the utilization efficiency of uplink resources and enabling the terminal device and network device to share the accurate GNSS validity period in a timely manner.

[0106] Figure 8 The illustration shows a flowchart of a GNSS validity transmission method provided by some exemplary embodiments of this application. Taking the method being executed by a terminal device as an example, the method includes at least some of the following steps:

[0107] Step 810: Generate the first MAC CE;

[0108] When at least one MAC CE carrying a GNSS validity period is triggered, the terminal equipment generates at least one MAC CE carrying a GNSS validity period through a multiplexing and assembly process. Multiplexing involves multiplexing multiple logical channels and MAC CEs into a single MAC PDU, while assembly involves loading MAC CEs and logical channel data according to priority.

[0109] The terminal device generates a MAC PDU based on the logical channel priority result. This MAC PDU contains only one MAC CE carrying the GNSS validity period. This MAC CE included in the MAC PDU is the first MAC CE.

[0110] The first MAC CE is any one of at least one MAC CE carrying a GNSS validity period, or one selected according to specific rules (such as priority rules).

[0111] GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period. The start time of the remaining GNSS validity period is the transmission time of the first MAC CE. The start time of the total GNSS validity period is the time when the terminal device acquires GNSS location information. The GNSS expiration period refers to the time during which GNSS location information has expired; its start time is the time when the terminal device acquires GNSS location information, and its end time is the transmission time of the first MAC CE.

[0112] Step 830: Send the first scheduling request;

[0113] The first scheduling request is sent by the terminal device to the network device. The first scheduling request is used to request the network device to configure a second uplink resource for the terminal device. The second uplink resource is the uplink resource that the terminal device requests the network device to configure for sending the first MAC CE.

[0114] In the absence of a first uplink resource, the terminal device sends a first scheduling request to the network device.

[0115] In some embodiments, the terminal device determines whether a first uplink resource exists based on a logical channel priority result. If the logical channel priority result indicates that the first uplink resource does not exist, the terminal device sends a first scheduling request, which requests the network device to configure a second uplink resource.

[0116] The first uplink resource is the uplink resource that is idle, unoccupied, or unused among the uplink resources allocated to the terminal device, and the data volume corresponding to the first MAC CE is less than or equal to the data volume corresponding to the first uplink resource.

[0117] In some embodiments, the amount of data corresponding to the first MAC CE is less than or equal to the amount of data corresponding to the first uplink resource. This can be understood as the first uplink resource being able to accommodate the first MAC CE, or the first uplink resource being able to accommodate the first MAC CE and its corresponding MAC subheader. It can also be understood as the amount of data corresponding to the first MAC CE being less than or equal to the amount of data that the first uplink resource can carry or the maximum amount of data.

[0118] The second uplink resource refers to the uplink resource configured by the network device for sending the first MAC CE, which is requested by the terminal device, and the data volume corresponding to the first MAC CE is less than or equal to the data volume corresponding to the second uplink resource.

[0119] In some embodiments, the amount of data corresponding to the first MAC CE is less than or equal to the amount of data corresponding to the second uplink resource. This can be understood as the second uplink resource being able to accommodate the first MAC CE, or the second uplink resource being able to accommodate the first MAC CE and its corresponding MAC subheader. It can also be understood as the amount of data corresponding to the first MAC CE being less than or equal to the amount of data that the second uplink resource can carry or the maximum amount of data.

[0120] In some embodiments, before sending the first scheduling request, the terminal device also receives a first configuration sent by the network device, the first configuration being used to allow the terminal device to send the first scheduling request.

[0121] In some embodiments, the first configuration is sent by the network device when establishing a connection with the terminal device, or periodically, semi-periodically, or non-periodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0122] In some embodiments, the terminal device sends a first scheduling request based on a second configuration. The second configuration is used to configure common scheduling request resources, i.e., general scheduling request sending resources.

[0123] In some embodiments, before sending the first scheduling request, the terminal device may also receive a second configuration sent by the network device.

[0124] In some embodiments, the second configuration is sent periodically, semi-periodically, or aperiodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0125] In some embodiments, the terminal device sends a first scheduling request based on a third configuration. The third configuration is used to configure dedicated scheduling request resources, which are uplink resources specifically used for sending the first scheduling request.

[0126] In some embodiments, before sending the first scheduling request, the terminal device may also receive a third configuration sent by the network device.

[0127] In some embodiments, the third configuration is sent periodically, semi-periodically, or aperiodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0128] In some embodiments, the terminal device receives a configuration sent by the network device, wherein the configuration includes at least one of the following:

[0129] The first configuration indicates that the terminal device is allowed to send a first scheduling request;

[0130] The second configuration is used to configure common scheduling request resources;

[0131] The third configuration is used to configure dedicated scheduling request resources, which are dedicated to the transmission of the first scheduling request.

[0132] In some embodiments, if a dedicated scheduling request resource has been configured for the terminal device, the terminal device uses this dedicated scheduling request resource to send a first scheduling request. That is, if the terminal device has already received a third configuration sent by the network device, the terminal device sends a first scheduling request based on the third configuration.

[0133] Otherwise, the terminal device uses the common scheduling request resource to send the first scheduling request. In other words, if no dedicated scheduling request resource is configured for the terminal device, the terminal device uses the common scheduling request resource to send the first scheduling request. This can also be understood as the terminal device sending the first scheduling request based on the second configuration if it has not received the third configuration from the network device.

[0134] Step 850: Receive the configuration of the second uplink resource;

[0135] The terminal device receives the configuration of the second uplink resource from the network device.

[0136] Step 870: Send the first MAC CE;

[0137] If at least one MAC CE carrying the GNSS validity period is triggered, a MAC PDU carrying the first MAC CE is sent.

[0138] The first MAC CE is sent from the terminal device to the network device, which includes access network equipment and / or satellite.

[0139] If the first uplink resource is unavailable, the terminal device sends a first MAC CE on the second uplink resource. Alternatively, if the terminal device receives configuration of the second uplink resource, it sends a first MAC CE on the second uplink resource.

[0140] In some embodiments, the terminal device determines whether a first uplink resource exists based on a logical channel priority result. If the logical channel priority result indicates that a first uplink resource does not exist, the terminal device transmits a first MAC CE on a second uplink resource.

[0141] Step 890: Cancel the second MAC CE.

[0142] The second MAC CE is at least one of the MAC CEs carrying a GNSS validity period, other than the first MAC CE.

[0143] In some embodiments, when the first MAC CE is carried in the MAC PDU for transmission, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and ready for transmission, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and about to be transmitted, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is being transmitted, the terminal device cancels all triggered second MAC CEs.

[0144] In some embodiments, when the first MAC CE is carried in the MAC PDU for transmission, the terminal device cancels all triggered MAC CEs (including the first MAC CE and the second MAC CE); or, when the first MAC CE is carried in the MAC PDU and is ready for transmission, the terminal device cancels all triggered MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is about to be transmitted, the terminal device cancels all triggered MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is being transmitted, the terminal device cancels all triggered MAC CEs.

[0145] In some embodiments, the cancellation of MAC CE triggering can be understood as the terminal device being in a state where it does not need to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state where it is not prepared to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state where it is not about to send a MAC CE carrying the GNSS validity period.

[0146] In summary, the method provided in this embodiment sends a first scheduling request to the network device when there is no first uplink resource available to send the first MACCE, and uses the second uplink resource configured by the network device to send the first MACCE carrying the GNSS validity period. This enables the terminal device and the network device to share the accurate GNSS validity period in a timely manner, avoiding the problem that the terminal device and the network device cannot share the accurate GNSS validity period in a timely manner due to resource shortage.

[0147] Figure 9 The illustration shows a flowchart of a GNSS validity period transmission method provided by some exemplary embodiments of this application. Taking the method being executed by a network device as an example, the method includes at least some of the following steps:

[0148] Step 910: Send the first configuration to the terminal device;

[0149] The first configuration is used to allow the terminal device to send a first scheduling request. The first scheduling request is used to request the network device to configure a second uplink resource for the terminal device, which is the uplink resource that the terminal device requests the network device to configure for sending the first MAC CE.

[0150] In some embodiments, the first configuration is sent by the network device when establishing a connection with the terminal device, or periodically, semi-periodically, or non-periodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0151] In some embodiments, the network device sends a configuration to the terminal device, wherein the configuration includes at least one of the following:

[0152] The first configuration indicates that the terminal device is allowed to send a first scheduling request;

[0153] The second configuration is used to configure common scheduling request resources;

[0154] The third configuration is used to configure dedicated scheduling request resources, which are dedicated to the transmission of the first scheduling request.

[0155] Step 930: Receive the first scheduling request sent by the terminal device;

[0156] In some embodiments, the first scheduling request is sent based on a second configuration. The second configuration is used to configure common scheduling request resources, i.e., general scheduling request sending resources.

[0157] In some embodiments, the network device also sends a second configuration to the terminal device.

[0158] In some embodiments, the second configuration is sent periodically, semi-periodically, or aperiodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0159] In some embodiments, the first scheduling request is sent based on a third configuration. The third configuration is used to configure dedicated scheduling request resources, that is, resources specifically used for sending the first scheduling request.

[0160] In some embodiments, the network device also sends a third configuration to the terminal device.

[0161] In some embodiments, the third configuration is sent periodically, semi-periodically, or aperiodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0162] Step 950: Configure the second uplink resource for the terminal device;

[0163] In some embodiments, the second uplink resource refers to the uplink resource configured by the network device for sending the first MAC CE, which is requested by the terminal device, and the data volume corresponding to the first MAC CE is less than or equal to the data volume corresponding to the second uplink resource.

[0164] Step 970: Receive the first MAC CE sent by the terminal device.

[0165] The first MAC CE carries the GNSS validity period. The GNSS validity period refers to the valid time for GNSS positioning.

[0166] In some embodiments, the first MAC CE is carried in the MAC PDU. The MAC PDU includes only one MAC CE carrying the GNSS validity period, and this MAC CE included in the MAC PDU is the first MAC CE.

[0167] GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period. The start time of the remaining GNSS validity period is the transmission time of the first MAC CE. The start time of the total GNSS validity period is the time when the terminal device acquires GNSS location information. The GNSS expiration period refers to the time during which GNSS location information has expired; its start time is the time when the terminal device acquires GNSS location information, and its end time is the transmission time of the first MAC CE.

[0168] In some embodiments, the first MAC CE is transmitted via a first uplink resource or via a second uplink resource. The first uplink resource refers to the uplink resources allocated to the terminal device that are idle or unoccupied and capable of accommodating the first MAC CE and its corresponding MAC subheader.

[0169] In summary, the method provided in this embodiment configures uplink resources for the terminal device to send a first scheduling request and / or a first MAC CE, and receives a first MAC CE carrying the GNSS validity period, so that the terminal device and the network device can share the accurate GNSS validity period in a timely manner, avoiding the problem that the terminal device and the network device cannot share the accurate GNSS validity period in a timely manner due to resource shortage.

[0170] Figure 10 The illustration shows a flowchart of a GNSS validity transmission method provided by some exemplary embodiments of this application. Taking the method being executed by a network device and a terminal device as an example, the method includes at least some of the following steps:

[0171] Step 1010: The network device sends the first configuration to the terminal device;

[0172] The first configuration is used to allow the terminal device to send a first scheduling request. The first scheduling request is used to request the network device to configure a second uplink resource for the terminal device, which is the uplink resource that the terminal device requests the network device to configure for sending the first MAC CE.

[0173] In some embodiments, the first configuration is sent by the network device when establishing a connection with the terminal device, or periodically, semi-periodically, or non-periodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0174] Step 1020: The terminal device generates the first MAC CE;

[0175] When at least one MAC CE carrying a GNSS validity period is triggered, the terminal equipment generates at least one MAC CE carrying a GNSS validity period through a multiplexing and assembly process. Multiplexing involves multiplexing multiple logical channels and MAC CEs into a single MAC PDU, while assembly involves loading MAC CEs and logical channel data according to priority.

[0176] The terminal device generates a MAC PDU based on the logical channel priority result. This MAC PDU contains only one MAC CE carrying the GNSS validity period. This MAC CE included in the MAC PDU is the first MAC CE.

[0177] The first MAC CE is any one of at least one MAC CE carrying a GNSS validity period, or one selected according to specific rules (such as priority rules).

[0178] GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period. The start time of the remaining GNSS validity period is the transmission time of the first MAC CE. The start time of the total GNSS validity period is the time when the terminal device acquires GNSS location information. The GNSS expiration period refers to the time during which GNSS location information has expired; its start time is the time when the terminal device acquires GNSS location information, and its end time is the transmission time of the first MAC CE.

[0179] Step 1030: The terminal device sends the first scheduling request;

[0180] The first scheduling request is sent by the terminal device to the network device. The first scheduling request is used to request the network device to configure a second uplink resource for the terminal device. The second uplink resource is the uplink resource that the terminal device requests the network device to configure for sending the first MAC CE.

[0181] In the absence of a first uplink resource, the terminal device sends a first scheduling request to the network device.

[0182] In some embodiments, the terminal device determines whether a first uplink resource exists based on a logical channel priority result. If the logical channel priority result indicates that the first uplink resource does not exist, the terminal device sends a first scheduling request, which requests the network device to configure a second uplink resource.

[0183] The first uplink resource refers to the uplink resource that is idle, unoccupied, or unused among the uplink resources allocated to the terminal device, and the data volume corresponding to the first MAC CE is less than or equal to the data volume corresponding to the first uplink resource.

[0184] In some embodiments, the amount of data corresponding to the first MAC CE is less than or equal to the amount of data corresponding to the first uplink resource. This can be understood as the first uplink resource being able to accommodate the first MAC CE, or the first uplink resource being able to accommodate the first MAC CE and its corresponding MAC subheader. It can also be understood as the amount of data corresponding to the first MAC CE being less than or equal to the amount of data that the first uplink resource can carry or the maximum amount of data.

[0185] The second uplink resource refers to the uplink resource configured by the network device for sending the first MAC CE, which is requested by the terminal device, and the data volume corresponding to the first MAC CE is less than or equal to the data volume corresponding to the second uplink resource.

[0186] In some embodiments, the amount of data corresponding to the first MAC CE is less than or equal to the amount of data corresponding to the second uplink resource. This can be understood as the second uplink resource being able to accommodate the first MAC CE, or the second uplink resource being able to accommodate the first MAC CE and its corresponding MAC subheader. It can also be understood as the amount of data corresponding to the first MAC CE being less than or equal to the amount of data that the second uplink resource can carry or the maximum amount of data.

[0187] In some embodiments, before sending the first scheduling request, the terminal device also receives a first configuration sent by the network device, the first configuration being used to allow the terminal device to send the first scheduling request.

[0188] In some embodiments, the first configuration is sent by the network device when establishing a connection with the terminal device, or periodically, semi-periodically, or non-periodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0189] In some embodiments, the terminal device sends a first scheduling request based on a second configuration. The second configuration is used to configure common scheduling request resources, i.e., general scheduling request sending resources.

[0190] In some embodiments, before sending the first scheduling request, the terminal device also receives a second configuration sent by the network device.

[0191] In some embodiments, the second configuration is sent periodically, semi-periodically, or aperiodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0192] In some embodiments, the terminal device sends a first scheduling request based on a third configuration. The third configuration is used to configure dedicated scheduling request resources, which are uplink resources specifically used for sending the first scheduling request.

[0193] In some embodiments, before sending the first scheduling request, the terminal device also receives a third configuration sent by the network device.

[0194] In some embodiments, the third configuration is sent periodically, semi-periodically, or aperiodically by the network device. The period value is predefined by the communication protocol, determined by the network device, or determined by the terminal device.

[0195] In some embodiments, if a dedicated scheduling request resource has been configured for the terminal device, the terminal device uses this dedicated scheduling request resource to send a first scheduling request. That is, if the terminal device has already received a third configuration sent by the network device, the terminal device sends a first scheduling request based on the third configuration.

[0196] Otherwise, the terminal device uses the common scheduling request resource to send the first scheduling request. In other words, if no dedicated scheduling request resource is configured for the terminal device, the terminal device uses the common scheduling request resource to send the first scheduling request. This can also be understood as the terminal device sending the first scheduling request based on the second configuration if it has not received the third configuration from the network device.

[0197] Step 1040: The network device configures a second uplink resource for the terminal device;

[0198] In some embodiments, the second uplink resource refers to the uplink resource configured by the network device for sending the first MAC CE, which the terminal device requests, and which is capable of accommodating the first MAC CE and its corresponding MAC subheader.

[0199] Step 1050: The terminal device sends the first MAC CE;

[0200] When at least one MAC CE carrying the GNSS validity period is triggered, the terminal device sends a MAC PDU carrying the first MAC CE.

[0201] The first MAC CE is sent from the terminal device to the network device, which includes access network equipment and / or satellite.

[0202] If a first uplink resource exists, the first MAC CE is transmitted on that first uplink resource. The first uplink resource refers to the uplink resource allocated to the terminal device that is idle or unoccupied and can accommodate the first MAC CE and its corresponding MAC subheader. The terminal device directly uses the first uplink resource to transmit a MAC PDU carrying the first MAC CE.

[0203] In some embodiments, the terminal device determines whether a first uplink resource exists based on a logical channel priority result. If the logical channel priority result indicates the existence of a first uplink resource, the terminal device transmits a first MAC CE on the first uplink resource.

[0204] If the first uplink resource is unavailable, the terminal device sends a first MAC CE on the second uplink resource. Alternatively, if the terminal device receives configuration of the second uplink resource, it sends a first MAC CE on the second uplink resource.

[0205] In some embodiments, the terminal device determines whether a first uplink resource exists based on a logical channel priority result. If the logical channel priority result indicates that a first uplink resource does not exist, the terminal device transmits a first MAC CE on a second uplink resource.

[0206] Step 1060: Cancel the second MAC CE.

[0207] The second MAC CE is at least one of the MAC CEs carrying a GNSS validity period, other than the first MAC CE.

[0208] In some embodiments, when the first MAC CE is carried in the MAC PDU for transmission, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and ready for transmission, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and about to be transmitted, the terminal device cancels all triggered second MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is being transmitted, the terminal device cancels all triggered second MAC CEs.

[0209] In some embodiments, when the first MAC CE is carried in the MAC PDU for transmission, the terminal device cancels all triggered MAC CEs (including the first MAC CE and the second MAC CE); or, when the first MAC CE is carried in the MAC PDU and is ready for transmission, the terminal device cancels all triggered MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is about to be transmitted, the terminal device cancels all triggered MAC CEs; or, when the first MAC CE is carried in the MAC PDU and is being transmitted, the terminal device cancels all triggered MAC CEs.

[0210] In some embodiments, the cancellation of MAC CE triggering can be understood as the terminal device being in a state where it does not need to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state where it is not prepared to send a MAC CE carrying the GNSS validity period, or the terminal device being in a state where it is not about to send a MAC CE carrying the GNSS validity period.

[0211] In summary, the method provided in this embodiment configures uplink resources for the terminal device to send a first MAC CE carrying the GNSS validity period, and the terminal device determines whether to use the first uplink resources or the second uplink resources to send the first MAC CE. This enables the terminal device and the network device to share the accurate GNSS validity period in a timely manner, avoiding the problem that the terminal device and the network device cannot share the accurate GNSS validity period in a timely manner due to resource shortages.

[0212] It should be understood that the order of the above steps can be adjusted in practical applications, and this application does not limit this. For example, the network device first sends the first configuration to the terminal device, and then sends the second configuration and / or the third configuration to the terminal device; or, the network device first sends the first configuration to the terminal device, then sends the second configuration to the terminal device, and then sends the third configuration to the terminal device; or, the network device sends the first configuration and the second configuration to the terminal device simultaneously; or, the network device sends the first configuration and the third configuration to the terminal device simultaneously.

[0213] Figure 11 The diagram illustrates a structural block diagram of a GNSS transmission apparatus according to some exemplary embodiments of this application. The apparatus includes at least some of the following modules: a first transmitting module 1120, a first processing module 1140, and a first receiving module 1160.

[0214] The first transmitting module 1120 is used to transmit a first MAC CE, the first MAC CE carrying the GNSS validity period.

[0215] In some embodiments, the first sending module 1120 is further configured to send the first MAC CE on the first uplink resource when the first uplink resource exists;

[0216] The first uplink resource refers to the uplink resource that is in an idle state and can accommodate the first MAC CE.

[0217] In some embodiments, the first sending module 1120 is further configured to send a first scheduling request in the absence of a first uplink resource;

[0218] Wherein, the first scheduling request is used to request the network device to schedule the second uplink resource, the second uplink resource is used to send the first MAC CE, and the first uplink resource refers to the uplink resource that is in an idle state and can accommodate the first MAC CE.

[0219] In some embodiments, the apparatus further includes:

[0220] The first receiving module 1160 is configured to receive a first configuration sent by the network device, the first configuration being configured to allow the device to send the first scheduling request.

[0221] In some embodiments, the first sending module 1120 is further configured to send the first scheduling request based on a second configuration, wherein the second configuration is configured to configure a common scheduling request resource.

[0222] In some embodiments, the first receiving module 1160 is configured to receive the second configuration sent by the network device.

[0223] In some embodiments, the first sending module 1120 is further configured to send the first scheduling request based on a third configuration, wherein the third configuration is configured to configure a dedicated scheduling request resource, which is dedicated to the transmission of the first scheduling request.

[0224] In some embodiments, the first receiving module 1160 is configured to receive the third configuration sent by the network device.

[0225] In some embodiments, the first transmitting module 1120 is further configured to transmit a MAC protocol data unit (PDU) carrying the first MAC CE when at least one MAC CE carrying a GNSS validity period is triggered;

[0226] The first MAC CE is one of the at least one MAC CE carrying the GNSS validity period.

[0227] In some embodiments, the apparatus further includes:

[0228] The first processing module 1140 is used to cancel the second MAC CE, which is the MAC CE other than the first MAC CE among the at least one MAC CE carrying the GNSS validity period.

[0229] In some embodiments, the GNSS validity period includes the remaining GNSS validity period and / or the total GNSS validity period.

[0230] In some embodiments, the start time of the remaining GNSS validity period is the transmission time of the first MAC CE;

[0231] The start time of the total GNSS validity period is the time when the GNSS location is obtained.

[0232] In summary, the device provided in this embodiment carries the GNSS validity period in the first MAC CE for transmission, enabling the device and network equipment to share the accurate GNSS validity period in a timely manner. Furthermore, it considers how to transmit the first MAC CE in the presence and absence of first uplink resources, thus avoiding the problem of being unable to transmit the GNSS validity period due to resource shortages.

[0233] Figure 12 The diagram illustrates a structural block diagram of a GNSS transmission apparatus provided in some exemplary embodiments of this application. The apparatus includes at least a portion of the following modules: a second receiving module 1220 and a second transmitting module 1240.

[0234] The second receiving module 1220 is used to receive the first MAC CE, which carries the GNSS validity period.

[0235] In some embodiments, the first MAC CE is sent by the terminal device on the first uplink resource;

[0236] The first uplink resource refers to the uplink resource that is in an idle state and can accommodate the first MAC CE.

[0237] In some embodiments, the second receiving module 1220 is further configured to receive a first scheduling request sent by the terminal device;

[0238] Wherein, the first scheduling request is used to request the device to schedule a second uplink resource, the second uplink resource is used to send the first MAC CE, and the first uplink resource refers to an uplink resource that is in an idle state and can accommodate the first MAC CE.

[0239] In some embodiments, the apparatus further includes:

[0240] The second sending module 1240 is used to send a first configuration, which allows the terminal device to send the first scheduling request.

[0241] In some embodiments, the second sending module 1240 is used to send a second configuration, which is used to configure a common scheduling request resource.

[0242] In some embodiments, the second sending module 1240 is configured to send a third configuration, the third configuration being configured to configure a dedicated scheduling request resource, the dedicated scheduling request resource being dedicated to the transmission of the first scheduling request.

[0243] In some embodiments, the second receiving module 1220 is further configured to receive a MAC PDU, the MAC PDU carrying the first MAC CE;

[0244] The first MAC CE is one of at least one MAC CE carrying a GNSS validity period.

[0245] In some embodiments, the GNSS validity period includes the remaining GNSS validity period and / or the total GNSS validity period.

[0246] In some embodiments, the start time of the remaining GNSS validity period is the transmission time of the first MAC CE;

[0247] The start time of the total GNSS validity period is the time when the GNSS location is obtained.

[0248] In summary, the apparatus provided in this embodiment supports configuring uplink resources for a terminal device to send a first scheduling request and / or a first MAC CE, and receiving a first MAC CE carrying the GNSS validity period, so that the terminal device and the apparatus can share the accurate GNSS validity period in a timely manner, avoiding the problem that the terminal device and the apparatus cannot share the accurate GNSS validity period in a timely manner due to resource shortage.

[0249] It should be noted that the device provided in the above embodiments is only an example of the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0250] Regarding the apparatus in this embodiment, the specific manner in which each module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0251] Figure 13 The present application shows a schematic diagram of the structure of a communication device (terminal device or network device) provided in some exemplary embodiments. The communication device 1300 includes: a processor 1301, a receiver 1302, a transmitter 1303, a memory 1304, and a bus 1305.

[0252] The processor 1301 includes one or more processing cores. The processor 1301 executes various functional applications and information processing by running software programs and modules. In some embodiments, the processor 1301 can be used to implement the functions and steps of the first processing module 1140 described above.

[0253] Receiver 1302 and transmitter 1303 can be implemented as a communication component, which can be a communication chip. In some embodiments, receiver 1302 can be used to implement the functions and steps of the first receiving module 1160 and / or the second receiving module 1220 as described above. In some embodiments, transmitter 1303 can be used to implement the functions and steps of the first transmitting module 1120 and / or the second transmitting module 1240 as described above.

[0254] The memory 1304 is connected to the processor 1301 via a bus 1305. The memory 1304 can be used to store at least one instruction, which the processor 1301 uses to execute to implement the various steps in the above method embodiments.

[0255] Furthermore, the memory 1304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), static random-access memory (SRAM), read-only memory (ROM), magnetic storage, flash memory, and programmable read-only memory (PROM).

[0256] In some embodiments, the receiver 1302 independently receives signals / data, or the processor 1301 controls the receiver 1302 to receive signals / data, or the processor 1301 requests the receiver 1302 to receive signals / data, or the processor 1301 cooperates with the receiver 1302 to receive signals / data.

[0257] In some embodiments, the transmitter 1303 independently transmits signals / data, or the processor 1301 controls the transmitter 1303 to transmit signals / data, or the processor 1301 requests the transmitter 1303 to transmit signals / data, or the processor 1301 cooperates with the transmitter 1303 to transmit signals / data.

[0258] In one exemplary embodiment of this application, a computer-readable storage medium is also provided, wherein at least one program is stored in the computer-readable storage medium, the at least one program being loaded and executed by a processor, the computer-readable storage medium being used to implement the GNSS validity period transmission method or GNSS validity period reception method provided in the above-described method embodiments.

[0259] In one exemplary embodiment of this application, a chip is also provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is run on a communication device, is used to implement the GNSS validity period transmission method or GNSS validity period reception method provided in the above-described method embodiments.

[0260] In one exemplary embodiment of this application, a computer program product is also provided, which, when run on the processor of a computer device, causes the computer device to perform the above-described method for transmitting or receiving GNSS validity period.

[0261] In one exemplary embodiment of this application, a computer program is also provided, the computer program including computer instructions, wherein a processor of a computer device executes the computer instructions, causing the computer device to perform the above-described method for transmitting or receiving GNSS validity period.

[0262] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0263] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for transmitting data during the validity period of a Global Navigation Satellite System (GNSS), characterized in that, The method is executed by a user equipment (UE), and the method includes: Send a first GNSS validity duration Media Access Control (MAC) control element (CE), wherein the first GNSS validity duration MAC CE is one of at least one MAC CE used to report the GNSS validity duration; When the first GNSS validity duration MAC CE is included in the MAC protocol data unit (PDU) for transmission, all triggered GNSS validity duration MAC CEs are cancelled. The GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period.

2. The method according to claim 1, characterized in that, Each MAC subheader corresponds to a MAC PDU, or a MACCE, or a padding portion.

3. The method according to claim 1, characterized in that, The method further includes: Based on the GNSS location obtained by the UE, at least one GNSS validity duration MAC CE is triggered.

4. The method according to claim 1, characterized in that, The cancellation of the triggered GNSS validity duration MAC CE includes at least one of the following situations: the UE is in a state where it does not need to send GNSS validity duration MAC CE, or the UE is in a state where it is not ready to send GNSS validity duration MAC CE, or the UE is in a state where it is not about to send GNSS validity duration MAC CE.

5. The method according to claim 1, characterized in that, The transmission of the first GNSS validity duration MAC CE includes: If a first uplink resource exists, transmit the first GNSS validityduration MAC CE on the first uplink resource; Wherein, the first uplink resource is an unused uplink resource that has been allocated to the UE, and the amount of data corresponding to the first GNSSvalidity duration MAC CE is less than or equal to the amount of data corresponding to the first uplink resource.

6. The method according to claim 1, characterized in that, The method further includes: If no first uplink resource is available, send the first scheduling request; Wherein, the first scheduling request is used to request the network device to configure the second uplink resource, the second uplink resource is used for the UE to send the first GNSS validity duration MAC CE, and the data volume corresponding to the first GNSS validity duration MAC CE is less than or equal to the data volume corresponding to the second uplink resource.

7. The method according to claim 6, characterized in that, Before sending the first scheduling request, the method further includes: Receive configuration sent by the network device, wherein the configuration includes at least one of the following: A first configuration, wherein the first configuration indicates that the UE is allowed to send the first scheduling request; The second configuration is used to configure the common scheduling request resource; The third configuration is used to configure a dedicated scheduling request resource, which is dedicated to the transmission of the first scheduling request.

8. The method according to claim 7, characterized in that, The first scheduling request is sent based on the second configuration of the network device.

9. The method according to claim 7, characterized in that, The first scheduling request is sent based on the third configuration of the network device.

10. The method according to any one of claims 1 to 9, characterized in that, The transmission of the first GNSS validity duration MAC CE includes: When at least one MAC CE for reporting GNSS validity duration is triggered, the MAC PDU containing the first GNSS validity duration MAC CE is sent.

11. The method according to claim 10, characterized in that, The method further includes: Cancel the second GNSS validity duration MAC CE; Alternatively, cancel the first GNSS validity duration MAC CE and the second GNSS validity duration MAC CE; Wherein, the second GNSS validity duration MAC CE is the GNSS validity duration MAC CE other than the first GNSS validity duration MAC CE among the at least one MAC CE used to report GNSS validity period.

12. The method according to any one of claims 1 to 9, characterized in that, The start time of the remaining GNSS validity period is the transmission time of the first GNSS validity duration MAC CE; The start time of the total GNSS validity period is the time when the GNSS location is obtained; The start time of the GNSS validity period is the time when the GNSS location is acquired, and the end time of the GNSS validity period is the time when the first GNSS validity duration MAC CE is transmitted.

13. A method for transmitting data during the validity period of a Global Navigation Satellite System (GNSS), characterized in that, The method is performed by a network device, and the method includes: Receive a first GNSS validity duration MAC control element (CE), wherein the first GNSS validity duration MAC CE is one of at least one MAC CE used to report the GNSS validity duration; When the first GNSS validity duration MAC CE is included in the MAC protocol data unit (PDU) for transmission, all triggered GNSS validity duration MAC CEs are cancelled. The GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period.

14. The method according to claim 13, characterized in that, Each MAC PDU subheader corresponds to a MAC PDU, or a MAC CE, or a padding portion.

15. The method according to claim 13, characterized in that, At least one GNSS validity duration MACCE is triggered based on the GNSS location obtained by the user equipment (UE).

16. The method according to claim 13, characterized in that, The cancellation of the triggered GNSS validity duration MAC CE includes at least one of the following situations: the user equipment (UE) is in a state where it is not required to send a GNSS validity duration MAC CE, or the UE is in a state where it is not prepared to send a GNSS validity duration MAC CE, or the UE is in a state where it is not about to send a GNSS validity duration MAC CE.

17. The method according to claim 13, characterized in that, The first GNSS validity duration MAC CE is transmitted by the user equipment (UE) on the first uplink resource; Wherein, the first uplink resource is an unused uplink resource that has been allocated to the UE, and the amount of data corresponding to the first GNSSvalidity duration MAC CE is less than or equal to the amount of data corresponding to the first uplink resource.

18. The method according to claim 13, characterized in that, The method further includes: Receive the first scheduling request sent by the user equipment (UE); Wherein, the first scheduling request is used to request the network device to configure the second uplink resource, the second uplink resource is used for the UE to send the first GNSS validity duration MAC CE, and the data volume corresponding to the first GNSS validity duration MAC CE is less than or equal to the data volume corresponding to the second uplink resource.

19. The method according to claim 18, characterized in that, Before receiving the first scheduling request sent by the UE, the method further includes: Send a configuration to the UE, wherein the configuration includes at least one of the following: A first configuration, wherein the first configuration indicates that the UE is allowed to send the first scheduling request; The second configuration is used to configure the common scheduling request resource; The third configuration is used to configure a dedicated scheduling request resource, which is dedicated to the transmission of the first scheduling request.

20. The method according to any one of claims 13 to 19, characterized in that, The receiving of the first GNSS validity duration MAC CE includes: Receive the MAC PDU, which contains the first GNSS validity duration MAC CE.

21. The method according to any one of claims 13 to 19, characterized in that, The start time of the remaining GNSS validity period is the transmission time of the first GNSS validity duration MAC CE; The start time of the total GNSS validity period is the time when the GNSS location is obtained; The start time of the GNSS validity period is the time when the GNSS location is acquired, and the end time of the GNSS validity period is the time when the first GNSS validity duration MAC CE is transmitted.

22. A transmission device for the validity period of a Global Navigation Satellite System (GNSS), characterized in that, Configured to execute: Send a first GNSS validity duration Media Access Control (MAC) control element (CE), wherein the first GNSS validity duration MAC CE is one of at least one MAC CE used to report the GNSS validity duration; When the first GNSS validity duration MAC CE is included in the MAC protocol data unit (PDU) for transmission, all triggered GNSS validity duration MAC CEs are cancelled. The GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period.

23. A transmission device for the validity period of a Global Navigation Satellite System (GNSS), characterized in that, Configured to execute: Receive a first GNSS validity duration MAC control element (CE), wherein the first GNSS validity duration MAC CE is one of at least one MAC CE used to report the GNSS validity duration; When the first GNSS validity duration MAC CE is included in the MAC protocol data unit (PDU) for transmission, all triggered GNSS validity duration MAC CEs are cancelled. The GNSS validity period includes at least one of the following: remaining GNSS validity period, total GNSS validity period, and GNSS expiration period.

24. A user equipment (UE), characterized in that, The UE includes: processor; A transceiver connected to the processor; Memory used to store executable instructions; The processor is configured to execute the executable instructions to enable the UE to implement the method as described in any one of claims 1 to 12.

25. A network device, characterized in that, The network device includes: processor; A transceiver connected to the processor; Memory used to store executable instructions; The processor is configured to execute the executable instructions to enable the network device to implement the method as described in any one of claims 13 to 21.

26. A computer-readable storage medium, characterized in that, The readable storage medium stores executable instructions that are executed by a processor of the communication device to enable the communication device to perform the method as claimed in any one of claims 1 to 12 or 13 to 21.

27. A chip, characterized in that, The chip includes programmable logic circuitry or a program, and the chip is used to enable a communication device to implement the method as claimed in any one of claims 1 to 12 or 13 to 21.

28. A computer program product, characterized in that, The device stores a computer program that, when executed by a processor of the communication device, causes the communication device to perform the method as claimed in any one of claims 1 to 12 or 13 to 21.

Images