Data transmission method and related apparatus

Abstract

Provided are a data transmission method and a related apparatus. The method comprises: sending a first request message to a network device, the first request message being used for requesting to activate a first PUR among a plurality of PURs, the plurality of PURs being pre-configured by the network device for a terminal device, and at least two PURs among the plurality of PURs carrying different amounts of data; and, on the basis of the first PUR, sending uplink data to the network device. At least two PURs among the plurality of PURs carry different amounts of data, that is to say, at least two different data volume requirements can be met. The terminal device can, on the basis of the data volume requirement, request the network device to activate one of the plurality of PURs to transmit uplink data, widening the range of transmittable data volumes, and facilitating the improvement of the flexibility of uplink data transmission.

Description

A data transmission method and related device

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on December 20, 2023, with application number 202311770574.2 and application name “A Data Transmission Method and Related Devices”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to a data transmission method and related devices. Background Art

[0003] Traditional terrestrial communication networks have limited coverage. For example, they cannot provide terrestrial communication services in areas where base stations cannot be deployed, such as oceans, deserts, and forests. Therefore, non-terrestrial networks (NTNs) have been introduced into fifth-generation (5G) systems. NTNs offer wider coverage, and satellite base stations are less susceptible to natural disasters, which can improve the reliability of 5G systems.

[0004] In an NTN, when a terminal device transitions from a connected state to an idle state, a preconfigured uplink resource (PUR) mechanism is employed. Specifically, the network equipment configures uplink resources for the terminal device while in the connected state. When the terminal device enters the idle state, it can send uplink data using these preconfigured uplink resources without having to enter a connected state.

[0005] As the services of terminal devices become more and more diverse, the amount of data required to be transmitted for different services may be different. Therefore, when the services of terminal devices change, it is very likely that the PUR will not match the amount of data to be transmitted, which will lead to inflexible transmission of uplink data. Summary of the Invention

[0006] The present application provides a data transmission method and related devices to improve the flexibility of uplink data transmission.

[0007] In the first aspect, the present application provides a data transmission method, which can be executed by a communication device. The communication device can be a terminal device, or a component configured in the terminal device (such as a chip, chip system, etc.), or it can also be a logic module or software that can realize all or part of the terminal device functions. The present application does not limit this.

[0008] Exemplarily, the method includes: sending a first request message to the network device, the first request message being used to request activation of a first PUR among multiple PURs, the multiple PURs being pre-configured by the network device to the terminal device, and at least two of the multiple PURs carrying different amounts of data; and sending uplink data to the network device based on the above-mentioned first PUR.

[0009] In the present application, the amount of data carried by at least two of the above-mentioned multiple PURs is different, which can be understood as: the parameters configured by at least two of the above-mentioned multiple PURs are different, for example, the size and / or number of transport blocks (TB) are different, for example, the modulation and coding scheme (MCS) is different, for example, the time-frequency resources are different, etc., which is not limited in the present application.

[0010] In addition, in the present application, the first request message is used to request activation of a first PUR among multiple PURs. Alternatively, the first request message may be used to request reservation of a first PUR among multiple PURs. It is understood that in actual applications, a network device may pre-configure multiple PURs for a terminal device, but may only reserve (or activate) one of the multiple PURs.

[0011] In the above technical solution, the amount of data carried by at least two of the above multiple PURs is different, that is, at least two different data volume requirements can be met. The terminal device can request the network device to activate one of the above multiple PURs to transmit uplink data according to the data volume requirement. The range of data volume that can be transmitted is wider, which is conducive to improving the flexibility of uplink data transmission.

[0012] On the second aspect, the present application provides a data transmission method, which can be executed by a communication device. The communication device can be a network device, or a component configured in the network device (such as a chip, chip system, etc.), or it can also be a logic module or software that can realize all or part of the functions of the network device. The present application does not limit this.

[0013] Exemplarily, the method includes: receiving a first request message from a terminal device, the first request message being used to request activation of a first PUR among multiple PURs, the multiple PURs being pre-configured to the terminal device by a network device, and at least two of the multiple PURs carrying different amounts of data; and receiving uplink data from the terminal device based on the first PUR.

[0014] In the above technical solution, the network device can pre-configure multiple PURs for the terminal device, and the data amounts carried by at least two PURs among the multiple PURs are different, that is, at least two different data amount requirements can be met. The terminal device can request the network device to activate one of the above multiple PURs to transmit uplink data according to the data amount requirement. The range of data amount that can be transmitted is wider, which is conducive to improving the flexibility of uplink data transmission.

[0015] In combination with the first and second aspects, in certain possible implementations, the data volumes carried by each of the multiple PURs are different. This allows for a wider range of data volumes to be transmitted, allowing the terminal device to flexibly transmit data of varying sizes, thereby increasing the flexibility of uplink data transmission.

[0016] In conjunction with the first aspect, in some possible implementations, before sending the first request message, the method further includes: the terminal device receiving configuration information, where the configuration information is used to configure the multiple PURs. Accordingly, in conjunction with the second aspect, in some possible implementations, the network device sends the configuration information.

[0017] The network device can pre-configure the above multiple PURs for the terminal device so that the terminal device can flexibly select the first PUR to be activated from the above multiple PURs according to service requirements (or the amount of data to be transmitted), which is conducive to improving the flexibility of uplink data transmission.

[0018] In conjunction with the first aspect, in some possible implementations, before sending uplink data to the network device based on the first PUR, the method further includes: receiving a timing advance command (TAC) from the network device, where the TAC is used for uplink synchronization. Accordingly, in conjunction with the second aspect, in some possible implementations, the network device sends the TAC.

[0019] Among them, the above-mentioned TAC can be used to ensure that the uplink data sent by the terminal device on the above-mentioned first PUR can be correctly received. In more detail, the terminal device receives the TAC and can perform uplink synchronization (or adjust the time advance) based on the TAC. In this way, the uplink data sent by the terminal device on the above-mentioned first PUR can be correctly received by the network device; if the terminal device does not receive the TAC, it is possible that the terminal device and the network device are out of sync in the uplink, resulting in the uplink data sent by the terminal device on the above-mentioned first PUR cannot be correctly received by the network device.

[0020] In combination with the first aspect and the second aspect, in some possible implementations, the first PUR is periodically distributed in the time domain. When the period of the first PUR is less than the measurement duration corresponding to the global navigation satellite system (GNSS) measurement, the priority of the above-mentioned GNSS measurement is greater than the priority of the transmission of uplink data.

[0021] The transmission of signals and uplink data during the GNSS measurement process cannot be carried out at the same time. When the period of the first PUR is less than the measurement duration corresponding to the GNSS measurement, it may cause a conflict between the GNSS measurement and the transmission of uplink data. In this case, the priority of the GNSS measurement is greater than the priority of the transmission of the uplink data, that is, the GNSS measurement is performed first to ensure the synchronization of the uplink signal. The measurement duration corresponding to the GNSS measurement can be configured by the network device to the terminal device. For example, the measurement duration configured by the network device to the terminal device is 1 hour (such as 9 o'clock to 10 o'clock). In actual applications, the actual starting time of the GNSS measurement performed by the terminal device can be determined by the terminal device, as long as the GNSS measurement is completed before 10 o'clock.

[0022] In conjunction with the first aspect, in some possible implementations, the method further includes: receiving first indication information from a network device, where the first indication information indicates a duration for GNSS measurement. Accordingly, in conjunction with the second aspect, in some possible implementations, the method further includes: sending the first indication information to a terminal device.

[0023] In one possible design, the first indication information includes the number of periods of the first PUR, where the first PUR is periodically distributed in the time domain. In other words, the network device may indicate to the terminal device the number of periods of the first PUR, during which the terminal device performs GNSS measurements without transmitting uplink data.

[0024] Another possible design is that the first indication information includes a timer running duration. That is, the network device can indicate a timer running duration to the terminal device, during which the resources of the first PUR are released. That is, during the timer running duration, the terminal device performs GNSS measurement without transmitting uplink data.

[0025] In conjunction with the first aspect, in certain possible implementations, before receiving the first indication information from the network device, the method further includes: reporting to the network device the validity period of the GNSS measurement and the time required to complete the GNSS measurement. Accordingly, in conjunction with the second aspect, in certain possible implementations, before sending the first indication information to the terminal device, the method further includes: receiving the validity period of the GNSS measurement and the time required to complete the GNSS measurement from the terminal device, and determining the time required for the GNSS measurement based on the validity period of the GNSS measurement and the time required to complete the GNSS measurement.

[0026] Among them, the validity period of the GNSS measurement can be understood as the validity period of the positioning information obtained by the GNSS measurement, that is, if the validity period is exceeded, the positioning information obtained by the GNSS measurement may not be accurate. Accordingly, within the validity period, the positioning information obtained by the GNSS measurement is relatively accurate. In addition, the time required to complete the GNSS measurement can be understood as the duration required for the terminal device to perform the GNSS measurement. The time required to complete the GNSS measurement may be determined by the configuration of the terminal device, which is different from the time configured by the network device for the terminal device for GNSS measurement. For example, the network device can configure the terminal device for a time of 1 hour for GNSS measurement (such as 9 o'clock to 10 o'clock), but the time required for the terminal device to complete the GNSS measurement is 30 minutes. The terminal device can decide the starting time of the GNSS measurement by itself, as long as the GNSS measurement is completed before 10 o'clock.

[0027] In conjunction with the first aspect, in some possible implementations, the method further includes: receiving second indication information from a network device, where the second indication information is used to indicate a starting point for the GNSS measurement. Accordingly, in conjunction with the second aspect, in some possible implementations, the method further includes: sending the second indication information to a terminal device.

[0028] The network device can indicate the start time of GNSS measurement to the terminal device. From the start time, the terminal device performs GNSS measurement and does not transmit uplink data to reduce the possibility of conflict between GNSS measurement and uplink data transmission.

[0029] In conjunction with the first aspect, in some possible implementations, the method further includes: sending third indication information to the network device, where the third indication information is used to indicate a duration for GNSS measurement, where the third indication information includes the number of cycles of the first PUR. Accordingly, in conjunction with the second aspect, in some possible implementations, the method further includes: receiving the third indication information from the terminal device.

[0030] The terminal device can request the network device for the number of cycles of the first PUR for GNSS measurement. In other words, the terminal device requests to perform GNSS measurement during this period without transmitting uplink data. In this way, the network device can determine the time to perform GNSS measurement, or the time not to transmit uplink data.

[0031] In conjunction with the first aspect, in certain possible implementations, the method further includes: in the event that the amount of uplink data changes, sending a second request message to the network device, the second request message being used to request activation of a second PUR, the second PUR being one of the multiple PURs, and the second PUR carrying a different amount of data than the first PUR; and based on the second PUR, sending uplink data to the network device. Accordingly, in conjunction with the second aspect, in certain possible implementations, the method further includes: in the event that the amount of uplink data changes, receiving a second request message being used to request activation of a second PUR, the second PUR being one of the multiple PURs, and the second PUR carrying a different amount of data than the first PUR; and receiving uplink data from the terminal device based on the second PUR.

[0032] When the amount of uplink data changes, the terminal device can flexibly switch the requested activated PUR according to the data volume demand, without having to re-initiate random access to enter the connected state to transmit data, which is beneficial to reducing the power consumption overhead of the terminal device and also helps to reduce the waste of pre-configured resources.

[0033] Optionally, the effective time of the above-mentioned second PUR is predefined or indicated by the network device, and the above-mentioned sending uplink data to the network device based on the second PUR includes: when the effective time of the second PUR arrives, sending uplink data to the network device based on the second PUR.

[0034] When the effective time of the second PUR arrives, the terminal device sends uplink data to the network device based on the second PUR. That is to say, the second PUR needs to wait for a period of time to take effect. This is conducive to matching the round-trip transmission delay of messages between the network device and the terminal device.

[0035] Optionally, when the effective time of the second PUR is indicated by the network device, the effective time of the second PUR is carried in the TAC.

[0036] In combination with the first aspect and the second aspect, in some possible implementations, when the satellite switches but the network device does not switch, the multiple PURs are not released, wherein the satellite is used to forward messages between the network device and the terminal device.

[0037] The above-mentioned not releasing the multiple PURs may be understood as: the multiple PURs are still effective, or the terminal device may continue to use the multiple PURs.

[0038] When the satellite switches but the network device does not switch, the multiple PURs are not released. That is, there is no need to reconfigure the multiple PURs, which is beneficial to reducing signaling overhead.

[0039] In a third aspect, the present application provides a communications device that can implement the method described in the first aspect and any possible implementation of the first aspect, or the method described in the second aspect and any possible implementation of the second aspect. The device includes corresponding modules for executing the above methods. The modules included in the device can be implemented in software and / or hardware.

[0040] In a fourth aspect, the present application provides a communication device comprising a processor, which can be used to execute a computer program in a memory to implement the method described in the first aspect and any possible implementation of the first aspect, or to implement the method described in the second aspect and any possible implementation of the second aspect.

[0041] Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface. The communication interface is configured to receive signals from other communication devices outside the device and transmit them to the processor, or to transmit signals from the processor to other communication devices outside the device. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0042] Optionally, the apparatus further comprises a memory, the processor being coupled to the memory. The memory is configured to store program instructions and data. The memory is coupled to the processor, and when the processor executes instructions stored in the memory, the methods described in the above aspects can be implemented.

[0043] In a fifth aspect, the present application provides a communication device, comprising a processor and a communication interface, wherein the communication interface is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device, and the processor implements the method described in the first aspect and any possible implementation of the first aspect through a logic circuit or by executing code instructions, or implements the method described in the second aspect and any possible implementation of the second aspect. Exemplarily, the communication interface can be a transceiver, circuit, bus, module, pin, or other type of communication interface.

[0044] Optionally, the apparatus further includes a memory for storing instructions and data. The memory may be coupled to the processor, and when the processor executes the instructions stored in the memory, the method described in the first aspect and any possible implementation of the first aspect is implemented, or the method described in the second aspect and any possible implementation of the second aspect is implemented.

[0045] In a sixth aspect, the present application provides a communication device comprising a processor and a memory, wherein the memory is used to store instructions and data. When the processor executes the instructions stored in the memory, it can implement the method described in the first aspect and any possible implementation of the first aspect, or implement the method described in the second aspect and any possible implementation of the second aspect.

[0046] Optionally, the device further includes a communication interface, which is used for the device to communicate with other communication devices. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, pin or other types of communication interfaces.

[0047] In the seventh aspect, the present application provides a computer-readable storage medium, which stores a computer program or instructions. When the computer program or instructions are executed, it implements the method described in the first aspect and any possible implementation of the first aspect, or implements the method described in the second aspect and any possible implementation of the second aspect.

[0048] In an eighth aspect, the present application provides a computer program product comprising instructions, which, when executed, implement the method described in the first aspect and any possible implementation of the first aspect, or implement the method described in the second aspect and any possible implementation of the second aspect.

[0049] In the ninth aspect, the present application provides a chip system comprising at least one processor for supporting the implementation of the functions involved in the first aspect and any possible implementation of the first aspect, or for supporting the implementation of the functions involved in the second aspect and any possible implementation of the second aspect, for example, receiving or processing the data involved in the above method, etc.

[0050] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0051] The chip system can be composed of chips, or can include chips and other discrete devices.

[0052] In the tenth aspect, the present application provides a communication system, which includes a terminal device and a network device, wherein the terminal device is used to implement the method described in the first aspect and any possible implementation of the first aspect, and the network device is used to implement the method described in the second aspect and any possible implementation of the second aspect.

[0053] It should be understood that the third to tenth aspects of the present application correspond to the technical solutions of the first and second aspects of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] FIG1 is a schematic diagram of the architecture of a communication system applicable to the data transmission method provided in this application;

[0055] FIG2 is a schematic flow chart of a data transmission method provided in an embodiment of the present application;

[0056] FIG3 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0057] FIG4 is another schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] The technical solution in this application will be described below with reference to the accompanying drawings.

[0059] Before introducing the method provided in the embodiments of the present application, the following points are explained.

[0060] First, in this application, indications include explicit indications (also called direct indications) and implicit indications (also called indirect indications). Specifically, explicit indication information A refers to including information A; implicit indication information A refers to indicating information A through the correspondence between information A and information B and directly indicating information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured; or, it can also refer to indicating information A through information B and preset rules.

[0061] Second, in this application, information C is used to determine information D, which includes both information D being determined solely based on information C and information D being determined based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, when information D is determined based on information E, and information E is determined based on information C.

[0062] Third, in this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship, but it does not exclude the situation where the previous and next associated objects are in an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.

[0063] Fourth, in this application, prefixes such as "first" and "second" are used solely to distinguish between different items belonging to the same category and do not constrain the order, size, or quantity of the items. For example, "first request message" and "second request message" can be different request messages, and this application does not restrict their order.

[0064] Fifth, the "sending" and "receiving" in this application indicate the direction of signal transmission. For example, "sending information to a network device" can be understood as the destination end of the information being the network device, which can include direct sending through the air interface, and also includes indirect sending through the air interface by other units or modules. "Receiving information from a terminal device" can be understood as the source end of the information being the terminal device, which can include direct receiving from the terminal device through the air interface, and also includes indirect receiving from the terminal device through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.

[0065] In other words, sending and receiving can be carried out between devices, for example, between a terminal device and a network device; or it can be carried out within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, wiring or interface.

[0066] Sixth, in this application, "when", "if" and "if" all mean that the device will take corresponding actions under certain objective circumstances, which does not limit the time, nor does it require that the device must perform judgment actions when it is implemented, nor does it mean that there are other limitations.

[0067] Seventh, in this application, words such as "example," "exemplarily," "for example," or "such as" are used to indicate examples, illustrations, or explanations. Any embodiment or design described in this application as "example," "exemplarily," "for example," or "such as" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "example," "exemplarily," "for example," or "such as" is intended to present the relevant concepts in a concrete manner.

[0068] Eighth, in this application, pre-configuration can be understood as preset, predefined, definition, predefined, storage, pre-stored, pre-negotiated, prefabricated, preset or preconfigured, etc.

[0069] Traditional terrestrial communication networks have limited coverage. For example, they cannot provide terrestrial communication services in areas where base stations cannot be deployed, such as oceans, deserts, and forests. Therefore, NTN has been introduced into 5G systems. NTN provides wider coverage, and satellite base stations are less susceptible to natural disasters, which can improve the reliability of 5G systems.

[0070] In NTN, when a terminal device transitions from connected to idle state, the PUR mechanism is used. Specifically, the network device configures uplink resources for the terminal device in the connected state. After the terminal device enters the idle state, it can send uplink data using the pre-configured uplink resources without entering the connected state.

[0071] As the services of terminal devices become more and more diverse, the amount of data required to be transmitted for different services may be different. Therefore, when the services of terminal devices change, it is very likely that the PUR will not match the amount of data to be transmitted, resulting in inflexible uplink data transmission.

[0072] To solve the above problems, the present application provides a data transmission method, in which a terminal device can request a network device to activate a PUR among multiple pre-configured PURs, and based on the PUR, send uplink data to the network device, wherein the amount of data carried by at least two of the above-mentioned multiple pre-configured PURs is different. In this way, the terminal device can flexibly select a more suitable PUR according to the expected amount of data to be transmitted, which is conducive to improving the flexibility of data transmission.

[0073] Before describing in detail the data transmission method provided by the present application, the communication system to which the present application is applicable is first described in detail below.

[0074] FIG1 is a schematic diagram of the architecture of a communication system applicable to the data transmission method provided in this application.

[0075] As shown in Figure 1, the data transmission method provided in this application can be applied to an NTN communication system, which includes terminal equipment, satellites, base stations (an example of network equipment), ground stations, and a core network. In Figure 1, the base station is deployed on a satellite as an example. In actual applications, the base station can also be deployed on a high-altitude platform.

[0076] Terminal devices access the network through an air interface (which can be any type of air interface, such as a 5G air interface). Base stations, or portions of base station functionality, are deployed on high-altitude platforms or satellites and connected to the terrestrial core network via wireless links. Furthermore, when base stations are deployed on satellites, wireless links exist between them, enabling signaling and user data transmission between base stations.

[0077] In this application, satellites can be used to forward messages between base stations and terminal devices.

[0078] Base stations can be used to provide wireless access services, schedule wireless resources to terminal devices, and provide reliable wireless transmission protocols and data encryption protocols.

[0079] The core network is responsible for services such as user access control, mobility management, session management, user security authentication, and billing. The core network includes multiple functional units, which can be divided into control plane and data plane functional entities. The access and mobility management function (AMF) is responsible for user access management, security authentication, and mobility management. The user plane function (UPF) is responsible for managing user plane data transmission, traffic statistics, and other aspects.

[0080] The ground station can be used to forward signaling and service data between the base station and the core network.

[0081] In this application, the air interface refers to the wireless link between a terminal device and a base station. The Xn interface is the interface between base stations and is primarily used for signaling exchanges such as handovers. The NG interface is the interface between a base station and the core network and is primarily used for exchanging core network non-access stratum (NAS) signaling and user service data.

[0082] It should be understood that the system shown in FIG1 uses two terminal devices for illustrative purposes only and does not constitute any limitation on the present application. In actual applications, a greater number of terminal devices may be included. Furthermore, a base station is an example of a network device and does not constitute any limitation on the present application. In actual applications, the network device may also be other types of devices.

[0083] It should also be understood that the present application does not limit the types of network devices and terminal devices. In the present application, a network device can be any device with wireless transceiver functions. The network device includes, but is not limited to, an evolved node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B, or home node B, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (Wi-Fi) system, a wireless relay node, a wireless backhaul node, a transmission point (TP), or a transmission and reception point (TRP), etc. It may also be a gNB or a transmission point (TRP or TP) in a 5G (such as NR) 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 a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc. The network device may also be a wireless controller in a cloud radio access network (CRAN) scenario.

[0084] In this application, terminal devices may also be referred to as terminals, user equipment (UE), mobile stations, mobile terminals, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.

[0085] The data transmission method provided by this application will be described in detail below with reference to the accompanying drawings.

[0086] Figure 2 is a schematic flow chart of a data transmission method 200 provided in an embodiment of the present application. Figure 2 only describes the method by taking the interaction between a terminal device and a network device as an example, and should not constitute any limitation to the present application. The terminal device in Figure 2 can also be replaced by a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or a logic module or software that can implement all or part of the functions of the terminal device. The network device can be replaced by a component configured in the network device (such as a chip, a chip system, a processor, etc.), or a logic module or software that can implement all or part of the functions of the network device.

[0087] The method 200 shown in Figure 2 includes step 210 and step 220. The steps in the method 200 are described in detail below.

[0088] In step 210, the terminal device sends a first request message to the network device, where the first request message is used to request activation of a first PUR among a plurality of PURs. Accordingly, the network device receives the first request message.

[0089] The multiple PURs are pre-configured by the network device for the terminal device, and at least two of the multiple PURs carry different amounts of data. The different amounts of data carried by at least two of the multiple PURs can be understood as: at least two of the multiple PURs have different configuration parameters, such as different TB sizes and / or numbers, different MCSs, or different time-frequency resources, etc., which is not limited in this application.

[0090] It should be noted that the data volume that each PUR can carry can be the maximum data volume that the PUR can carry, that is, the maximum data volume that the PUR can carry. For example, if the data volume that PUR 1 can carry is data volume 1, and the amount of data to be transmitted by the terminal device is data volume 2, if data volume 2 is less than or equal to data volume 1, the terminal device can select PUR 1 to carry the data to be transmitted.

[0091] In addition, the first request message is used to request activation of a first PUR among multiple PURs, and can also be replaced by the first request message being used to request reservation of a first PUR among multiple PURs, wherein reserving the first PUR can be understood as: the resources of the first PUR are used for the terminal device to transmit uplink data. In actual applications, the network device can pre-configure multiple PURs for the terminal device, but can only reserve (or activate) one of the multiple PURs.

[0092] Optionally, the amount of data carried by each of the multiple PURs may be different.

[0093] For example, a network device pre-configures multiple PURs for a terminal device, including PUR 1, PUR 2, and PUR 3. The amount of data carried by each of PUR 1, PUR 2, and PUR 3 differs from one another. The terminal device sends a first request message to the network device, requesting the activation of PUR 1, where the resources of PUR 1 match the amount of data to be transmitted by the terminal device, or in other words, the amount of data that PUR 1 can carry is greater than or equal to the amount of data to be transmitted by the terminal device. Accordingly, the network device receives the first request message, thereby determining the PUR to be activated.

[0094] Optionally, before the terminal device sends the first request message to the network device, the method further includes: the terminal device receiving configuration information from the network device, the configuration information being used to configure the plurality of PURs. Accordingly, the network device sends the configuration information.

[0095] For example, while in a connected state, the terminal device may send a third request message to the network device, requesting the network device to configure a PUR. The network device then receives the third request message. Furthermore, the network device may send configuration information to the terminal device, configuring multiple PURs. The terminal device then receives the configuration information. When the terminal device enters an idle state, it may send uplink data via one of the multiple PURs.

[0096] Optionally, each of the multiple PURs includes one or more of the following parameters: time-frequency resources, period, MCS, number of repetitions, or TB size. The number of repetitions refers to the number of times uplink data needs to be repeated each time it is sent. For example, uplink data needs to be repeated three times each time to increase the probability of successful transmission. In addition, the time-frequency resources are periodic resources. In other words, the PURs are periodically distributed in the time and frequency domains.

[0097] In step 220, the terminal device sends uplink data to the network device based on the first PUR. Correspondingly, the network device receives uplink data from the terminal device based on the first PUR.

[0098] After the terminal device sends the first request message to the network device, the terminal device can send uplink data to the network device based on the above-mentioned first PUR.

[0099] It should be understood that sending uplink data based on the first PUR means sending uplink data on the first PUR. Receiving uplink data based on the first PUR means receiving uplink data on the first PUR. For the sake of brevity, descriptions of the same or similar situations are omitted below.

[0100] Optionally, before the terminal device sends uplink data to the network device based on the first PUR, the method 200 further includes: the network device sends a TAC, where the TAC is used for uplink synchronization. Correspondingly, the terminal device receives the TAC.

[0101] The above-mentioned TAC can be used to ensure that the uplink data sent by the terminal device on the above-mentioned first PUR can be correctly received. It can be understood that after the terminal device receives the above-mentioned TAC, it can perform uplink synchronization (or adjust the time advance) based on the TAC, so that the uplink data sent by the terminal device on the above-mentioned first PUR can be correctly received by the network device; if the terminal device does not receive the above-mentioned TAC, it is possible that the terminal device and the network device are out of synchronization in the uplink, resulting in the uplink data sent by the terminal device on the above-mentioned first PUR cannot be correctly received by the network device.

[0102] Exemplarily, after sending the first request message to the network device, the terminal device receives a TAC from the network device, which may carry a timing advance for uplink synchronization. Further, the terminal device sends uplink data to the network device based on the first PUR.

[0103] It can be understood that when the business of the terminal device changes, the size of the data to be transmitted may change accordingly, or in other words, the size of the data to be transmitted may exceed or be lower than the size of the resources of the first PUR. In this case, the terminal device can flexibly select a PUR (such as a second PUR) that matches the size of the data to be transmitted based on the size of the data to be transmitted, and request the network device to activate the above-mentioned second PUR.

[0104] One possible implementation is that, when the amount of uplink data changes, the terminal device sends a second request message to the network device, requesting activation of a second PUR (one of the multiple PURs) carrying a different amount of data than the first PUR. The network device then sends uplink data to the network device based on the second PUR. Accordingly, the network device receives the second request message, requesting activation of a second PUR (one of the multiple PURs) carrying a different amount of data than the first PUR. The network device then receives uplink data from the terminal device based on the second PUR.

[0105] Exemplarily, the network device pre-configures multiple PURs including PUR 1, PUR 2, and PUR 3, wherein the amount of data carried by each PUR in PUR 1, PUR 2, and PUR 3 is different. For example, the amount of data that PUR 1 can carry is recorded as data amount 1, the amount of data that PUR 2 can carry is recorded as data amount 2, and the amount of data that PUR 3 can carry is recorded as data amount 3. If the amount of data to be transmitted by the terminal device changes from data amount 1 to data amount 2, the terminal device can send a second request message to the network device to request activation of PUR 2. Accordingly, the network device receives the above-mentioned second request message.

[0106] Optionally, the effective time of the above-mentioned second PUR is predefined or indicated by the network device; and the above-mentioned sending uplink data to the network device based on the second PUR includes: when the effective time of the second PUR arrives, sending uplink data to the network device based on the above-mentioned second PUR.

[0107] In other words, the second PUR may take effect after a period of time, or in other words, the second PUR may be activated after a period of time. When the effective time of the second PUR is reached, the terminal device may send uplink data to the network device based on the second PUR.

[0108] One possible design is that the effective time of the second PUR can be predefined. Exemplarily, the effective time of the second PUR can be the starting point of the next second PUR in the time domain. For example, the second PUR is distributed in the time domain as time slot 1, time slot 3, time slot 5, time slot 7, ..., time slot 2k+1, where k is an integer greater than or equal to 0. The time slot occupied by the terminal device sending the second request message is, for example, time slot 2, and the effective time of the second PUR can be the starting point of time slot 3.

[0109] Exemplarily, the second PUR may also take effect after a predefined offset value. For example, the effective time of the second PUR is: the sending time of the second request message + the offset value.

[0110] Another possible design is that the effective time of the second PUR is indicated by the network device. For example, the network device sends a TAC to the terminal device in response to the second request message, and the effective time of the second PUR is carried in the TAC.

[0111] It can be understood that the terminal device can send uplink data based on the activated PUR in the idle state, and the GNSS measurement needs to be completed before sending the uplink data. Taking the first PUR among the above-mentioned multiple PURs as an example, in this application, the transmission of signals and uplink data during the GNSS measurement process cannot be carried out at the same time. When the period of the first PUR is less than the measurement duration corresponding to the GNSS measurement, it may cause a conflict between the GNSS measurement and the transmission of uplink data. In this case, the priority of the GNSS measurement is greater than the priority of the transmission of the uplink data. That is to say, the terminal device gives priority to the GNSS measurement and sends the uplink data after completing the GNSS measurement.

[0112] One possible implementation method for resolving the transmission conflict between GNSS measurements and uplink data is for the network device to send first indication information to the terminal device, where the first indication information indicates a duration for GNSS measurements. That is, the first indication information indicates a period of time to be used for GNSS measurements, during which the terminal device does not send uplink data. Accordingly, the terminal device receives the first indication information from the network device.

[0113] The possible designs of the first indication information will be introduced in detail below.

[0114] In a first possible design, the first indication information includes the number of first PUR cycles. The first PUR is periodically distributed in the time domain. That is, the network device can indicate the number of first PUR cycles to the terminal device, during which the terminal device performs GNSS measurements without transmitting uplink data.

[0115] A second possible design is that the first indication information includes a timer running duration. That is, the network device can indicate a timer running duration to the terminal device, during which the resources of the first PUR are released, that is, not used for uplink data transmission, but for GNSS measurement.

[0116] Optionally, before receiving the first indication information from the network device, the method further includes: the terminal device reporting to the network device the validity period of the GNSS measurement and the time required to complete the GNSS measurement. Accordingly, the network device receives the validity period of the GNSS measurement and the time required to complete the GNSS measurement from the terminal device.

[0117] Among them, the validity period of the GNSS measurement can be understood as the validity period of the positioning information obtained by the GNSS measurement, that is, if the validity period is exceeded, the positioning information obtained by the GNSS measurement may not be accurate. Accordingly, within the validity period, the positioning information obtained by the GNSS measurement is relatively accurate. In addition, the time required to complete the GNSS measurement can be understood as the duration required for the terminal device to perform the GNSS measurement. The time required to complete the GNSS measurement may be determined by the configuration of the terminal device, which is different from the time configured by the network device for the terminal device for GNSS measurement. For example, the network device can configure the terminal device for a time of 1 hour for GNSS measurement (such as 9 o'clock to 10 o'clock), but the time required for the terminal device to complete the GNSS measurement is 30 minutes. The terminal device can decide the starting time of the GNSS measurement by itself, as long as the GNSS measurement is completed before 10 o'clock.

[0118] The network device may determine the number of first PUR cycles to be skipped and / or the running duration of the timer according to the validity period of the GNSS measurement reported by the terminal device and the duration required to complete the GNSS measurement.

[0119] For example, the validity period of the GNSS measurement reported by the terminal device is 9:00, and the time required to complete the GNSS measurement is 30 minutes. The network device determines that the terminal device needs to complete the GNSS measurement before 9:00. For example, the first PUR is distributed in the time domain from 8:30 to 8:40 and from 8:50 to 9:00. In this case, the number of periods of the first PUR indicated by the network device to the terminal device may be 2. For another example, the first PUR is distributed in the time domain from 8:00 to 8:10, from 8:20 to 8:30, and from 8:40 to 8:50. In this case, the number of periods of the first PUR indicated by the network device to the terminal device may be 3.

[0120] In another example, the validity period of the GNSS measurement reported by the terminal device is 9 o'clock, and the time required to complete the GNSS measurement is 30 minutes. The network device determines that the terminal device needs to complete the GNSS measurement before 9 o'clock. The running time of the timer indicated by the network device to the terminal device can be, for example, 30 minutes, or longer, such as 1 hour.

[0121] Another possible implementation method for resolving the transmission conflict between GNSS measurement and uplink data is that the network device sends second indication information, where the second indication information is used to indicate the starting point of the GNSS measurement. Correspondingly, the terminal device receives the second indication information.

[0122] The network device can indicate the starting point of the GNSS measurement to the terminal device. After receiving the above instruction information, the terminal device starts GNSS measurement at the starting point of the GNSS measurement without sending uplink data.

[0123] Another possible implementation for resolving the transmission conflict between GNSS measurements and uplink data is for the terminal device to send a third indication message to the network device, where the third indication message indicates the duration for GNSS measurement, and the third indication message includes the number of cycles of the first PUR. In other words, the terminal device can indicate to the network device the number of cycles of the first PUR to skip in order to perform GNSS measurement.

[0124] For example, the validity period of the GNSS measurement is 9 o'clock, and the time required for the terminal device to complete the GNSS measurement is 30 minutes. Assuming that the first PUR is distributed in the time domain from 8:30 to 9 o'clock, it is 8:30 to 8:40 and 8:50 to 9 o'clock. The number of cycles of the first PUR indicated by the terminal device is 2.

[0125] It is understandable that since the satellites orbit the earth, the terminal devices are also moving relative to the satellites, which may cause the terminal devices using the network service to move from the coverage of one satellite to the coverage of another satellite. In the present application, when the satellite switches but the network device does not switch, the above-mentioned multiple PURs are not released, wherein the satellite is used to forward messages between the network device and the terminal device. For example, the base station is deployed on a high-altitude platform, and the satellite is used to forward messages between the base station and the terminal device. When satellite 1 switches to satellite 2, but the base station does not switch, the terminal device can still continue to use the above-mentioned multiple PURs, wherein the base station is an example of a network device.

[0126] The above-mentioned not releasing the multiple PURs may be understood as: the multiple PURs are still effective, or the terminal device may continue to use the multiple PURs.

[0127] For example, satellite 1 is used to forward messages between the base station and the terminal device. After a period of time, satellite 1 switches to satellite 2, and the base station does not switch. The terminal device can still transmit uplink data based on multiple PURs configured by the base station.

[0128] It should be noted that when satellites are switched, the terminal device may need to re-perform GNSS measurement, and then the terminal device needs to transmit uplink data after completing the GNSS measurement. Therefore, the above-mentioned multiple PURs may take effect after a period of time, or the terminal device may continue to use the above-mentioned multiple PURs to transmit uplink data after a period of time. The specific time period for the PURs to take effect may include the following two possible designs:

[0129] In one possible design, when a source satellite (e.g., satellite 1) is used to forward messages between a network device and a terminal device, the network device may instruct the terminal device to resume transmitting uplink data on the multiple PURs after a preset duration, where the preset duration is determined based on the duration required for the terminal device to complete a GNSS measurement. For example, if the terminal device requires 30 minutes to complete a GNSS measurement, the network device may instruct the terminal device to resume transmitting uplink data on the multiple PURs after 30 minutes.

[0130] Another possible design is that after the terminal device accesses the target satellite (such as satellite 2), the terminal device requests the network device to activate one of the multiple PURs. The specific request process is the same as the activation request process when the terminal device accesses the source satellite and is not repeated here.

[0131] Based on the above technical solution, the data volumes carried by at least two of the above multiple PURs are different, that is, at least two different data volume requirements can be met. The terminal device can request the network device to activate one of the above multiple PURs to transmit uplink data according to the data volume requirement. The range of data volume that can be transmitted is wider, which is conducive to improving the flexibility of uplink data transmission.

[0132] The data transmission method provided by the embodiment of the present application is described in detail above with reference to the accompanying drawings. Below, the device provided by the embodiment of the present application is described in detail with reference to the accompanying drawings.

[0133] It should be understood that the apparatus shown in Figures 3 and 4 can be used to implement the functions of the terminal device or network device in the above-mentioned method embodiment, and thus can also achieve the beneficial effects possessed by the above-mentioned method embodiment. In the embodiment of the present application, the apparatus can be the terminal device in the method embodiment shown in Figure 2, or it can be a component configured in the terminal device (such as a chip, a chip system, a processor, etc.), or it can be a logic module or software that can implement some or all of the functions of the terminal device; or, the apparatus can be the network device in the method embodiment shown in Figure 2, or it can be a component configured in the network device (such as a chip, a chip system, a processor, etc.), or it can be a logic module or software that can implement some or all of the functions of the network device.

[0134] FIG3 is a schematic block diagram of a communication device 300 provided in an embodiment of the present application.

[0135] As shown in Figure 3, the apparatus 300 includes a transceiver module 310 and a processing module 320. The apparatus 300 can be used to implement the functions of the terminal device or network device in the method embodiment shown in Figure 2 above.

[0136] When the device 300 is used to implement the function of the terminal device in the method embodiment shown in Figure 2, the transceiver module 310 can be used to send a first request message to the network device, and the first request message is used to request activation of a first PUR among multiple PURs. The multiple PURs are pre-configured to the device 300 by the network device, and the amount of data carried by at least two PURs among the multiple PURs is different; the processing module 320 can be used to send uplink data to the network device based on the above-mentioned first PUR.

[0137] Optionally, the transceiver module 310 is further configured to receive configuration information from a network device, where the configuration information is used to configure the multiple PURs.

[0138] Optionally, the transceiver module 310 is further configured to receive a TAC from a network device, where the TAC is used for uplink synchronization.

[0139] Optionally, the first PUR is periodically distributed in the time domain. When the period of the first PUR is less than the measurement duration corresponding to the GNSS measurement, the priority of the GNSS measurement is greater than the priority of the transmission of the uplink data.

[0140] Optionally, the transceiver module 310 is further configured to receive first indication information from a network device, where the first indication information indicates a duration for GNSS measurement.

[0141] Optionally, the first indication information includes the number of cycles of the first PUR, or the first indication information includes the running time of the timer.

[0142] Optionally, the transceiver module 310 is further configured to report the validity period of the GNSS measurement and the time required to complete the GNSS measurement to the network device.

[0143] Optionally, the transceiver module 310 is further configured to receive second indication information from a network device, where the second indication information is used to indicate a starting point of the GNSS measurement.

[0144] Optionally, the transceiver module 310 is further configured to send third indication information to the network device, where the third indication information is used to indicate a duration for GNSS measurement, and the third indication information includes the number of cycles of the first PUR.

[0145] Optionally, the transceiver module 310 is also used to send a second request message to the network device when the amount of uplink data changes. The second request message is used to request activation of a second PUR. The second PUR is one of the multiple PURs mentioned above, and the amount of data carried by the second PUR is different from that of the first PUR. The processing module 320 is also used to send uplink data to the network device based on the second PUR.

[0146] Optionally, the effective time of the second PUR is predefined or indicated by the network device; and the processing module 320 is specifically configured to send uplink data to the network device based on the second PUR when the effective time of the second PUR arrives.

[0147] Optionally, when the effective time of the second PUR is indicated by the network device, the effective time of the second PUR is carried in the TAC.

[0148] Optionally, when the satellite switches but the network device does not switch, the multiple PURs are not released, wherein the satellite is used to forward messages between the network device and the apparatus 300 .

[0149] When the device 300 is used to implement the function of the network device in the method embodiment shown in Figure 2, the transceiver module 310 can be used to receive a first request message from the terminal device, where the first request message is used to request activation of a first PUR among multiple PURs, where the multiple PURs are pre-configured to the terminal device by the device 300, and at least two of the multiple PURs carry different amounts of data; the processing module 320 can be used to receive uplink data from the terminal device based on the first PUR.

[0150] Optionally, the transceiver module 310 is further configured to send configuration information to the terminal device, where the configuration information is used to configure the multiple PURs.

[0151] Optionally, the transceiver module 310 is further configured to send a TAC to the terminal device, where the TAC is used for uplink synchronization.

[0152] Optionally, the first PUR is periodically distributed in the time domain. When the period of the first PUR is less than the measurement duration corresponding to the GNSS measurement, the priority of the GNSS measurement is greater than the priority of the transmission of the uplink data.

[0153] Optionally, the transceiver module 310 is further configured to send first indication information to the terminal device, where the first indication information indicates a duration for GNSS measurement.

[0154] Optionally, the first indication information includes the number of cycles of the first PUR, or the first indication information includes the running time of the timer.

[0155] Optionally, the transceiver module 310 is further used to receive the validity period of the GNSS measurement and the time required to complete the GNSS measurement from the terminal device; the processing module 320 is further used to determine the time used for the GNSS measurement based on the validity period of the GNSS measurement and the time required to complete the GNSS measurement.

[0156] Optionally, the transceiver module 310 is further used to send second indication information to the terminal device, where the second indication information is used to indicate a starting point of the GNSS measurement.

[0157] Optionally, the transceiver module 310 is further configured to receive third indication information from the terminal device, where the third indication information is used to indicate a duration for GNSS measurement, and the third indication information includes the number of cycles of the first PUR.

[0158] Optionally, the transceiver module 310 is also used to receive a second request message from the terminal device when the amount of uplink data changes. The second request message is used to request activation of a second PUR. The second PUR is one of the multiple PURs mentioned above, and the amount of data carried by the second PUR is different from that of the first PUR. The processing module 320 is also used to receive uplink data from the terminal device based on the second PUR.

[0159] Optionally, the effective time of the second PUR is predefined or indicated by the apparatus 300 .

[0160] Optionally, when the effective time of the second PUR is indicated by the apparatus 300 , the effective time of the second PUR is carried in the TAC.

[0161] Optionally, when the satellite switches but the network device does not switch, the multiple PURs are not released, wherein the satellite is used to forward messages between the apparatus 300 and the terminal device.

[0162] A more detailed description of each of the above modules can be directly obtained by referring to the relevant description in the method embodiment shown in Figure 2, and will not be repeated here.

[0163] It should be understood that the division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of the present application may be integrated into a single processor, or may exist physically as separate modules, or two or more modules may be integrated into a single module. The aforementioned integrated modules may be implemented in the form of hardware or software functional modules.

[0164] FIG4 is another schematic block diagram of a communication device 400 provided in an embodiment of the present application.

[0165] The device 400 may be a chip system, or may be a device configured with a chip system for implementing the method described in the above method embodiment. In the embodiment of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0166] As shown in FIG4 , the apparatus 400 may include a processor 410 , which may be configured to execute computer programs or instructions in a memory to implement the steps performed by the terminal device or the steps performed by the network device in the method embodiment shown in FIG2 .

[0167] Optionally, the apparatus 400 further includes a communication interface 420. The communication interface 420 can be used to communicate with other devices via a transmission medium, thereby enabling the apparatus 400 to communicate with other devices. The communication interface 420 can be, for example, a transceiver, an interface, a bus, a circuit, or a device capable of performing transceiver functions. The processor 410 can utilize the communication interface 420 to input and output data and implement the method described in the embodiment corresponding to FIG. 2 . Specifically, the apparatus 400 can be used to implement the functions of a terminal device or network device in the above-described method embodiment.

[0168] Optionally, the device 400 further includes at least one memory 430 for storing program instructions and / or data. The memory 430 is coupled to the processor 410. Coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 410 may operate in conjunction with the memory 430. The processor 410 may execute program instructions stored in the memory 430. At least one of the at least one memory may be included in the processor.

[0169] It should be understood that the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. The processor 410 may operate in conjunction with the memory 430. The specific connection medium between the above-mentioned processor 410, communication interface 420 and memory 430 is not limited in the embodiments of the present application. In Figure 4, the embodiment of the present application is connected by a bus 440 between the processor 410, communication interface 420 and memory 430. The bus 440 is represented by a bold line in Figure 4, and the connection method between other components is only for schematic illustration and is not limiting. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 4, but it does not mean that there is only one bus or one type of bus.

[0170] The present application also provides a computer program product, which includes: a computer program (also referred to as code, or instructions). When the computer program is executed, it can implement the steps performed by the terminal device or the steps performed by the network device in the method described in the embodiment shown in Figure 2.

[0171] The present application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed, the steps performed by the terminal device or the steps performed by the network device in the method described in the embodiment shown in FIG. 2 can be implemented.

[0172] An embodiment of the present application provides a communication system, which includes the terminal device and the network device as described above.

[0173] It should be understood that the processor in the embodiments of the present application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-mentioned method.

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

[0175] The terms "unit", "module", etc. used in this specification can be used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. The terms "unit" and "module" in the embodiments of this application have the same meaning and can be used interchangeably.

[0176] Those skilled in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. In the several embodiments provided in this application, it should be understood that the disclosed devices, equipment, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of devices or units, and can be electrical, mechanical, or other forms.

[0177] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0178] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0179] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (program) are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0180] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the technology or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0181] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A data transmission method, characterized in that: include: Sending a first request message to a network device, where the first request message is used to request activation of a first PUR among a plurality of preconfigured uplink resources PURs, where the plurality of PURs are preconfigured by the network device for a terminal device, and at least two of the plurality of PURs carry different amounts of data; Based on the first PUR, uplink data is sent to the network device.

2. The method according to claim 1, characterized in that Before sending the first request message to the network device, the method further includes: Configuration information is received from the network device, where the configuration information is used to configure the plurality of PURs.

3. The method according to claim 1 or 2, characterized in that Before sending the uplink data to the network device based on the first PUR, the method further includes: A timing advance command TAC is received from the network device, where the TAC is used for uplink synchronization.

4. The method according to any one of claims 1 to 3, characterized in that The first PUR is periodically distributed in the time domain. When the period of the first PUR is less than the measurement duration corresponding to the global satellite navigation system GNSS measurement, the priority of the GNSS measurement is greater than the priority of the transmission of the uplink data.

5. The method according to claim 4, characterized in that The method further comprises: First indication information is received from the network device, where the first indication information indicates a duration for GNSS measurement.

6. The method according to claim 5, characterized in that The first indication information includes the number of cycles of the first PUR, or the first indication information includes the running time of a timer.

7. The method according to claim 5 or 6, characterized in that Before receiving the first indication information from the network device, the method further includes: Reporting the validity period of the GNSS measurement and the time required to complete the GNSS measurement to the network device.

8. The method according to claim 4, characterized in that The method further comprises: Second indication information is received from the network device, where the second indication information is used to indicate a starting point of a GNSS measurement.

9. The method according to claim 4, characterized in that The method further comprises: Sending third indication information to the network device, where the third indication information is used to indicate a duration for GNSS measurement, and the third indication information includes the number of cycles of the first PUR.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: When the amount of uplink data changes, sending a second request message to the network device, where the second request message is used to request activation of a second PUR, where the second PUR is one of the multiple PURs, and the amount of data carried by the second PUR is different from that of the first PUR; Based on the second PUR, uplink data is sent to the network device.

11. The method according to claim 10, characterized in that The effective time of the second PUR is predefined or indicated by the network device; and the sending uplink data to the network device based on the second PUR includes: When the effective time of the second PUR arrives, uplink data is sent to the network device based on the second PUR.

12. The method according to claim 11, characterized in that When the effective time of the second PUR is indicated by the network device, the effective time of the second PUR is carried in the TAC.

13. The method according to any one of claims 1 to 12, characterized in that When the satellite switches but the network device does not switch, the multiple PURs are not released, wherein the satellite is used to forward messages between the network device and the terminal device.

14. A data transmission method, characterized in that: include: Receiving a first request message from a terminal device, where the first request message is used to request activation of a first PUR among a plurality of preconfigured uplink resources PURs, where the plurality of PURs are preconfigured for the terminal device by a network device, and at least two of the plurality of PURs carry different amounts of data; Based on the first PUR, uplink data from the terminal device is received.

15. The method according to claim 14, characterized in that Before receiving the first request message from the terminal device, the method further includes: Sending configuration information to the terminal device, where the configuration information is used to configure the multiple PURs.

16. The method according to claim 14 or 15, characterized in that Before receiving uplink data from the terminal device based on the first PUR, the method further includes: A timing advance command TAC is sent to the terminal device, where the TAC is used for uplink synchronization.

17. The method according to any one of claims 14 to 16, characterized in that The first PUR is periodically distributed in the time domain. When the period of the first PUR is less than the measurement duration corresponding to the global satellite navigation system GNSS measurement, the priority of the GNSS measurement is greater than the priority of the transmission of the uplink data.

18. The method according to claim 17, characterized in that The method further comprises: Sending first indication information to the terminal device, wherein the first indication information indicates a duration used for GNSS measurement.

19. The method according to claim 18, characterized in that The first indication information includes the number of cycles of the first PUR, or the first indication information includes the running time of a timer.

20. The method according to claim 18 or 19, characterized in that Before sending the first indication information to the terminal device, the method further includes: receiving from the terminal device the validity period of the GNSS measurement and the time required to complete the GNSS measurement; The duration for the GNSS measurement is determined according to the validity period of the GNSS measurement and the duration required to complete the GNSS measurement.

21. The method of claim 17, wherein: The method further comprises: Sending second indication information to the terminal device, where the second indication information is used to indicate a starting point of the GNSS measurement.

22. The method of claim 17, wherein: The method further comprises: Receive third indication information from the terminal device, where the third indication information is used to indicate a duration for GNSS measurement, and the third indication information includes the number of cycles of the first PUR.

23. The method according to any one of claims 14 to 22, characterized in that The method further comprises: In the case where the amount of uplink data changes, receiving a second request message from the terminal device, where the second request message is used to request activation of a second PUR, where the second PUR is one of the multiple PURs, and the amount of data carried by the second PUR is different from that of the first PUR; Based on the second PUR, uplink data from the terminal device is received.

24. The method of claim 23, wherein: The effective time of the second PUR is predefined or indicated by the network device.

25. The method of claim 24, wherein: When the effective time of the second PUR is indicated by the network device, the effective time of the second PUR is carried in the TAC.

26. The method according to any one of claims 14 to 25, characterized in that When the satellite switches but the network device does not switch, the multiple PURs are not released, wherein the satellite is used to forward messages between the network device and the terminal device.

27. A communication device, characterized in that: The method comprises a module for implementing the method according to any one of claims 1 to 13, or comprises a module for implementing the method according to any one of claims 14 to 26.

28. A communication device, characterized in that: comprising a processor and a memory, wherein: The memory is used to store computer programs; The processor is configured to call the computer program so that the apparatus implements the method according to any one of claims 1 to 13, or implements the method according to any one of claims 14 to 26.

29. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by a computer, the method according to any one of claims 1 to 13 is implemented, or the method according to any one of claims 14 to 26 is implemented.

30. A computer program product, characterized in that The computer program product comprises instructions, and when the instructions are executed by a computer, the method according to any one of claims 1 to 13 is implemented, or the method according to any one of claims 14 to 26 is implemented.

Images