Data transmission method and related device

Abstract

Provided are a data transmission method and a related device, the method comprising: sending a first request message to a network device, the first request message being used for requesting to activate a first PUR in a plurality of PURs, the plurality of PURs being pre-configured to a terminal device by the network device, the data volumes borne by at least two PURs in the plurality of PURs being different; and sending uplink data to the network device based on the first PUR. At least two PURs in the plurality of PURs bear different data volumes, that is to say, at least two different data volume requirements can be met, the terminal equipment can request the network equipment to activate one of the plurality of PURs to transmit uplink data according to the data volume requirements, the range of the data volume capable of being transmitted is wider, and the user experience is improved. And the flexibility of uplink data transmission is improved.

Description

Technical Field

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

[0002] The coverage of traditional terrestrial communication networks is limited. For example, terrestrial communication services cannot be provided in places such as the sea, desert, and forest where base stations cannot be deployed. Therefore, non-terrestrial networks (NTNs) are introduced into the 5th generation (5G) system. NTNs can provide a wider coverage, and satellite base stations are less affected by natural disasters, which can improve the reliability of the 5G system.

[0003] In NTN, when a terminal device transitions from the connected state to the idle state, a preconfigured uplink resources (PUR) mechanism is adopted. 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 through the above-mentioned preconfigured uplink resources without entering the connected state.

[0004] As the services of terminal devices become more and more diverse, the amount of data required for different services may be different. Therefore, when the services of the terminal device change, it is very likely that the problem of mismatch between PUR and the amount of data to be transmitted occurs, which in turn leads to inflexible transmission of uplink data. Summary of the Invention

[0005] This application provides a data transmission method and related devices, aiming to improve the flexibility of uplink data transmission.

[0006] In a first aspect, this application provides a data transmission method. This method can be executed by a communication device, which can be a terminal device, or a component (such as a chip, chip system, etc.) configured in the terminal device, or, it can also be a logical module or software that can implement all or part of the functions of the terminal device. This application does not make any limitations in this regard.

[0007] Exemplarily, the method includes: sending a first request message to a network device, where the first request message is used to request activation of a first PUR among multiple PURs. The multiple PURs are preconfigured by the network device for the terminal device, and at least two PURs among the multiple PURs carry different amounts of data; sending uplink data to the network device based on the above-mentioned first PUR.

[0008] In this application, the data volumes carried by at least two of the multiple PURs are different. It can be understood that: the parameters configured for at least two of the multiple PURs are different. For example, the size and / or quantity of the transport block (TB) are different, or for another example, the modulation and coding scheme (MCS) is different, or for yet another example, the time-frequency resources are different, etc. This application does not make any limitations in this regard.

[0009] In addition, in this application, the first request message is used to request the activation of the first PUR among the multiple PURs, or it can be replaced with that the first request message is used to request the reservation of the first PUR among the multiple PURs. It can be understood that in practical applications, the network device can pre-configure multiple PURs for the terminal device, but only one of the multiple PURs can be reserved (or activated).

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

[0011] In a second aspect, this application provides a data transmission method. This method can be executed by a communication device. The communication device can be a network device, or a component (such as a chip, a chip system, etc.) configured in the network device, or it can also be a logical module or software that can implement all or part of the functions of the network device. This application does not make any limitations in this regard.

[0012] Exemplarily, the method includes: receiving a first request message from a terminal device, where the first request message is used to request the activation of the first PUR among the multiple PURs, the multiple PURs are pre-configured by the network device for the terminal device, and the data volumes carried by at least two of the multiple PURs are different; receiving uplink data from the terminal device based on the first PUR.

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

[0014] Combining the first aspect and the second aspect, in some possible implementation manners, the data volume sizes carried by each of the multiple PURs are different from each other. In this way, the range of data volume that can be transmitted is wider, and the terminal device can flexibly transmit data with different data volume sizes, which is beneficial to improving the flexibility of uplink data transmission.

[0015] Combining the first aspect, in some possible implementation manners, before sending the first request message, the above method further includes: the terminal device receives configuration information, and the configuration information is used to configure the multiple PURs. Correspondingly, combining the second aspect, in some possible implementation manners, the network device sends the above configuration information.

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

[0017] Combining the first aspect, in some possible implementation manners, before sending uplink data to the network device based on the first PUR, the above method further includes: receiving a timing advance command (TAC) from the network device, and the TAC is used for uplink synchronization. Correspondingly, combining the second aspect, in some possible implementation manners, the network device sends the above TAC.

[0018] Among them, the above TAC can be used to ensure that the uplink data sent by the terminal device on the first PUR can be correctly received. More specifically, when the terminal device receives the TAC, it can perform uplink synchronization (or adjust the timing advance) based on the TAC. In this way, the uplink data sent by the terminal device on the 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 uplink synchronization, resulting in the uplink data sent by the terminal device on the first PUR not being correctly received by the network device.

[0019] Combining the first aspect and the second aspect, in some possible implementation manners, 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 GNSS measurement is greater than the priority of the uplink data transmission.

[0020] The transmission of signals and uplink data during GNSS measurement cannot be carried out simultaneously. When the period of the first PUR is less than the measurement duration corresponding to GNSS measurement, it may cause conflicts between GNSS measurement and uplink data transmission. In this case, the priority of GNSS measurement is higher than that of uplink data transmission, that is, GNSS measurement is carried out first to ensure the synchronization of uplink signals. Among them, the measurement duration corresponding to GNSS measurement can be configured by the network device for the terminal device. For example, the measurement duration configured by the network device for the terminal device is 1 hour (such as from 9 o'clock to 10 o'clock). In practical applications, the actual start time of GNSS measurement by the terminal device can be determined by the terminal device, as long as the GNSS measurement is completed before 10 o'clock.

[0021] Combined with the first aspect, in some possible implementation manners, the above method further includes: receiving first indication information from the network device, where the first indication information indicates the duration for GNSS measurement. Correspondingly, combined with the second aspect, in some possible implementation manners, the above method further includes: sending the above first indication information to the terminal device.

[0022] A possible design is that the above first indication information includes the number of periods of the first PUR, where the first PUR is periodically distributed in the time domain. That is to say, the network device can indicate the number of periods of the first PUR to the terminal device. During this period, the terminal device performs GNSS measurement without transmitting uplink data.

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

[0024] Combined with the first aspect, in some possible implementation manners, before receiving the first indication information from the network device, the above method further includes: reporting the validity period of GNSS measurement and the duration required to complete GNSS measurement to the network device. Correspondingly, combined with the second aspect, in some possible implementation manners, before sending the first indication information to the terminal device, the above method further includes: receiving the validity period of GNSS measurement and the duration required to complete GNSS measurement from the terminal device, and determining the duration for GNSS measurement according to the validity period of GNSS measurement and the duration required to complete GNSS measurement.

[0025] Among them, the validity period of GNSS measurement can be understood as the validity period of the positioning information obtained by GNSS measurement. That is to say, in the case of exceeding the validity period, the positioning information obtained by GNSS measurement may not be highly accurate. Correspondingly, within the validity period, the positioning information obtained by GNSS measurement is relatively accurate. In addition, the duration required to complete the GNSS measurement can be understood as the duration required for the terminal device to perform GNSS measurement. This duration required to complete the GNSS measurement may be determined by the configuration of the terminal device and is different from the duration for GNSS measurement configured by the network device for the terminal device. For example, the network device can configure the duration for GNSS measurement for the terminal device to be 1 hour (such as from 9 o'clock to 10 o'clock), but the duration required for the terminal device to complete the GNSS measurement is 30 minutes. The terminal device can independently determine the start time of GNSS measurement as long as the GNSS measurement is completed before 10 o'clock.

[0026] Combined with the first aspect, in some possible implementation manners, the above method further includes: receiving second indication information from the network device, where the second indication information is used to indicate the starting point of GNSS measurement. Correspondingly, combined with the second aspect, in some possible implementation manners, the above method further includes: sending the above second indication information to the terminal device.

[0027] The network device can indicate the starting time of GNSS measurement to the terminal device. Starting from this starting time, the terminal device performs GNSS measurement and does not transmit uplink data, so as to reduce the possibility of conflict between GNSS measurement and uplink data transmission.

[0028] Combined with the first aspect, in some possible implementation manners, the above method further includes: sending third indication information to the network device, where the third indication information is used to indicate the duration for GNSS measurement, and the third indication information includes the number of cycles of the first PUR. Correspondingly, combined with the second aspect, in some possible implementation manners, the above method further includes: receiving the above third indication information from the terminal device.

[0029] 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 for GNSS measurement, or rather, the time without transmitting uplink data.

[0030] In combination with the first aspect, in some possible implementation manners, the above method further includes: when the uplink data volume changes, sending a second request message to a network device, where the second request message is used to request to activate a second PUR, the second PUR is one of the above-mentioned multiple PURs, and the data volume carried by the second PUR is different from that carried by the first PUR; based on the second PUR, sending uplink data to the network device. Correspondingly, in combination with the second aspect, in some possible implementation manners, the above method further includes: when the uplink data volume changes, receiving a second request message, where the second request message is used to request to activate a second PUR, the second PUR is one of the above-mentioned multiple PURs, and the data volume carried by the second PUR is different from that carried by the first PUR; based on the second PUR, receiving uplink data from a terminal device.

[0031] When the uplink data volume changes, the terminal device can flexibly switch the PUR whose activation is requested according to the data volume requirement, 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 beneficial to reducing the waste of pre-configured resources.

[0032] 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.

[0033] 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 become effective. In this way, it is beneficial to match the round-trip transmission delay of messages between the network device and the terminal device.

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

[0035] In combination with the first aspect and the second aspect, in some possible implementation manners, when the satellite switches but the network device does not switch, the above-mentioned multiple PURs are not released, where the above-mentioned satellite is used to forward messages between the network device and the terminal device.

[0036] Among them, the above-mentioned not releasing the multiple PURs can be understood as: the above-mentioned multiple PURs are still effective, or, the terminal device can continue to use the above-mentioned multiple PURs.

[0037] When the satellite switches but the network device does not switch, the above-mentioned multiple PURs are not released, that is to say, there is no need to re-configure the multiple PURs, which is beneficial to reducing the signaling overhead.

[0038] In a third aspect, the present application provides a communication device that can implement the methods described in the first aspect and any possible implementation manner of the first aspect, or implement the methods described in the second aspect and any possible implementation manner 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 manners.

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

[0040] Optionally, the device further includes a communication interface, and the processor is coupled to the communication interface. The communication interface is used to receive signals from other communication devices outside the device and transmit them to the processor, or send signals from the processor to other communication devices outside the device. Exemplarily, the communication interface can be a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces.

[0041] Optionally, the device further includes a memory, and the processor is coupled to the memory. The memory is used to store program instructions and data. When the processor executes the instructions stored in the memory, the methods described in the above aspects can be implemented.

[0042] In a fifth aspect, the present application provides a communication device, including a processor and a communication interface. The communication interface is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or send signals from the processor to other communication devices outside the communication device. The processor uses logic circuits or executes code instructions to implement the methods described in the first aspect and any possible implementation manner of the first aspect, or implement the methods described in the second aspect and any possible implementation manner of the second aspect. Exemplarily, the communication interface can be a transceiver, a circuit, a bus, a module, a pin, or other types of communication interfaces.

[0043] Optionally, the device further includes a memory for storing instructions and data. The memory can be coupled to the processor. When the processor executes the instructions stored in the memory, the methods described in the first aspect and any possible implementation manner of the first aspect, or the methods described in the second aspect and any possible implementation manner of the second aspect are implemented.

[0044] In a sixth aspect, the present application provides a communication device, including a processor and a memory. 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 manner of the first aspect, or implement the method described in the second aspect and any possible implementation manner of the second aspect.

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

[0046] In a seventh aspect, the present application provides a computer-readable storage medium, in which a computer program or instructions are stored. When the computer program or instructions are executed, they can implement the method described in the first aspect and any possible implementation manner of the first aspect, or implement the method described in the second aspect and any possible implementation manner of the second aspect.

[0047] In an eighth aspect, the present application provides a computer program product, which includes instructions. When the instructions are run, they can implement the method described in the first aspect and any possible implementation manner of the first aspect, or implement the method described in the second aspect and any possible implementation manner of the second aspect.

[0048] In a ninth aspect, the present application provides a chip system, which includes at least one processor, and is used to support the implementation of the functions involved in the first aspect and any possible implementation manner of the first aspect, or is used to support the implementation of the functions involved in the second aspect and any possible implementation manner of the second aspect. For example, it is used to receive or process the data involved in the above method, etc.

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

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

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

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

[0053] Figure 1 is a schematic structural diagram of a communication system applicable to the data transmission method provided by the present application;

[0054] Figure 2 is a schematic flowchart of the data transmission method provided by an embodiment of the present application;

[0055] Figure 3 is a schematic block diagram of a communication device provided by an embodiment of the present application;

[0056] Figure 4 is another schematic block diagram of a communication device provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0057] The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0058] Before introducing the method provided by the embodiment of the present application, the following points are explained first.

[0059] First, in the present application, an indication includes an explicit indication (also referred to as a direct indication) and an implicit indication (also referred to as an indirect indication). Among them, explicitly indicating information A means including the information A; implicitly indicating information A means 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 mean indicating information A through information B and a preset rule.

[0060] Second, in the present application, information C is used for the determination of information D, which includes both the case where information D is determined only based on information C and the case where it is determined based on information C and other information. In addition, the situation where information C is used for the determination of information D can also be an indirect determination, for example, the case where information D is determined based on information E, and information E is determined based on information C.

[0061] Third, in this application, "at least one" means one or more, and "a plurality of" means two or more than two. "And / or" describes the relationship between associated objects and indicates that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship, but it does not exclude the case where the associated objects before and after are in a "and" relationship. The specific meaning can be understood in combination with the context. "At least one of the following" or similar expressions refer 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, b, and c. Where a, b, and c can be single or multiple.

[0062] Fourth, in this application, the use of prefix words such as "first" and "second" is only for the convenience of distinguishing and describing different things belonging to the same name category, and does not restrict the order, size, or quantity of things. For example, "the first request message" and "the second request message" can be different request messages, and this application does not limit their order.

[0063] Fifth, "send" and "receive" in this application represent the direction of signal transmission. For example, "sending information to a network device" can be understood as the destination of the information being the network device, which can include directly sending through the air interface or indirectly sending through other units or modules via the air interface. "Receiving information from a terminal device" can be understood as the source of the information being the terminal device, which can include directly receiving from the terminal device through the air interface or indirectly receiving from the terminal device through other units or modules via the air interface. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

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

[0065] Sixth, in this application, "when", "if", and "in case" all refer to the device making corresponding processing under a certain objective situation, not limited to time, and do not require the device to have a judgment action when implemented, nor does it mean there are other limitations.

[0066] Seventh, in this application, words such as "example", "exemplarily", "for example", or "such as" are used to give examples, illustrations, or explanations. Any embodiment or design solution described as "example", "exemplarily", "for example", or "such as" in this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "example", "exemplarily", "for example", or "such as" is intended to present relevant concepts in a specific manner.

[0067] Eighth, in this application, pre-configuration can be understood as pre-setting, pre-defining, defining, pre-defining, storing, pre-storing, pre-negotiating, prefabricating, pre-setting, or pre-configuring, etc.

[0068] The coverage of traditional terrestrial communication networks is limited. For example, in places such as the sea, desert, and forest where base stations cannot be deployed, terrestrial communication services cannot be provided. Therefore, NTN is introduced into the 5G system. NTN can provide a wider coverage, and satellite base stations are less affected by natural disasters, which can improve the reliability of the 5G system.

[0069] In NTN, when the terminal device transitions from the connected state to the idle state, the PUR mechanism is adopted. 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 through the above pre-configured uplink resources without entering the connected state.

[0070] As the services of terminal devices become more and more diverse, the amount of data required for different services may be different. Therefore, when the services of terminal devices change, it is very likely that there will be a problem of mismatch between PUR and the amount of data to be transmitted, which may lead to inflexible uplink data transmission.

[0071] To solve the above problems, this application provides a data transmission method. The terminal device can request the network device to activate a certain PUR among multiple pre-configured PURs, and based on this PUR, send uplink data to the network device. Among them, the amount of data carried by at least two PURs among the above pre-configured multiple 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 beneficial to improving the flexibility of data transmission.

[0072] Before introducing in detail the data transmission method provided by this application, the communication system applicable to this application will be described in detail below.

[0073] Figure 1 is a schematic diagram of the architecture of the communication system applicable to the data transmission method provided by this application.

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

[0075] The terminal device can access the network through an air interface (the air interface can be various types of air interfaces, such as a 5G air interface). The base station or some base station functions are deployed on a high-altitude platform or a satellite and are connected to the core network on the ground through a wireless link. In addition, when the base station is deployed on the satellite, there is a wireless link between the satellites to complete the signaling interaction and user data transmission between the base stations.

[0076] In this application, the satellite can be used to forward messages between the base station and the terminal device.

[0077] The base station can be used to provide wireless access services, schedule wireless resources for the terminal device, and can also be used to provide reliable wireless transmission protocols and data encryption protocols, etc.

[0078] The core network can be used for services such as user access control, mobility management, session management, user security authentication, and charging. The core network can include multiple functional units and can be divided into functional entities of the control plane and the data plane. Among them, 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 the transmission of user plane data, traffic statistics, etc.

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

[0080] In addition, in this application, the air interface refers to the wireless link between the terminal device and the base station. The Xn interface is the interface between the base stations and is mainly used for signaling interaction such as handover. The NG interface is the interface between the base station and the core network and is mainly used for interacting with the non-access stratum (NAS) signaling of the core network and the service data of the user.

[0081] It should be understood that Figure 1 the system shown is only an example with two terminal devices and should not impose any limitations on this application. In actual applications, there can be a greater number of terminal devices. In addition, the base station is an example of a network device and should not impose any limitations on this application. In actual applications, the network device can also be other types of devices.

[0082] It should also be understood that the types of network devices and terminal devices are not limited in this application. In this application, a network device can be any device with wireless transceiver functions. Network devices include, but are 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, transmission point (TP), or transmission and reception point (TRP), etc. It can 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 it can also be 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 can also be a wireless controller in a cloud radio access network (CRAN) scenario.

[0083] In this application, a terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, for example, 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, remote medical treatment, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, etc. The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver functions, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a robotic arm, a smart home device, etc.

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

[0085] Figure 2 It is a schematic flowchart of the data transmission method 200 provided by an embodiment of the present application. Figure 2 This method is only described 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. Figure 2 The terminal device in it can also be replaced by components configured in the terminal device (such as chips, chip systems, processors, etc.), or, logical modules or software that can implement all or part of the functions of the terminal device. The network device can be replaced by components configured in the network device (such as chips, chip systems, processors, etc.), or, logical modules or software that can implement all or part of the functions of the network device.

[0086] Figure 2 The method 200 shown includes step 210 and step 220. Each step in the method 200 will be described in detail below.

[0087] In step 210, the terminal device sends a first request message to the network device, and this first request message is used to request to activate the first PUR among multiple PURs. Correspondingly, the network device receives the above first request message.

[0088] The above multiple PURs are pre-configured by the network device for the terminal device, and at least two of the above multiple PURs carry different amounts of data. Among them, at least two of the above multiple PURs carry different amounts of data, which can be understood as: at least two of the above multiple PURs are configured with different parameters. For example, the TB size and / or quantity are different, or, the MCS is different, or, the time-frequency resources are different, etc. The present application does not make any limitation thereto.

[0089] It should be noted that the size of 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, the size of the data volume that PUR 1 can carry is data volume 1, and the data volume to be transmitted by the terminal device is data volume 2. In the case where 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.

[0090] In addition, the above first request message for requesting to activate the first PUR among multiple PURs can also be replaced by that the first request message is used to request to reserve the first PUR among multiple PURs. Among them, 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 practical applications, the network device can pre-configure multiple PURs for the terminal device, but only one of the above multiple PURs can be reserved (or activated).

[0091] Optionally, the data volume carried by each of the multiple PURs described above may be different from each other.

[0092] Exemplarily, the multiple PURs pre-configured by the network device for the terminal device include PUR 1, PUR 2, and PUR 3. Among them, the data volume carried by each of PUR 1, PUR 2, and PUR 3 is different from each other. The terminal device sends a first request message to the network device, and this first request message is used to request the activation of PUR 1. The resources of this PUR 1 match the data volume to be transmitted by the terminal device, or rather, the data volume that this PUR 1 can carry is greater than or equal to the data volume to be transmitted by the terminal device. Correspondingly, the network device receives the above first request message. In this way, the network device can determine the PUR to be activated.

[0093] Optionally, before the terminal device sends the first request message to the network device, the above method further includes: the terminal device receives configuration information from the network device, and this configuration information is used to configure the above multiple PURs. Correspondingly, the network device sends the above configuration information.

[0094] Exemplarily, the terminal device can send a third request message to the network device in the connected state, and this third request message is used to request the network device to configure the PUR. Correspondingly, the network device receives this third request message. Further, the network device sends configuration information to the terminal device, and this configuration information is used to configure multiple PURs. Correspondingly, the terminal device receives the above configuration information. When the terminal device enters the idle state, it can send uplink data through a certain PUR among the above multiple PURs.

[0095] Optionally, each of the above multiple PURs includes one or more of the following parameters: time-frequency resources, period, MCS, number of repetitions, or TB size. Among them, the number of repetitions refers to the number of times that the uplink data needs to be repeatedly sent each time. For example, the uplink data needs to be repeatedly sent 3 times each time to increase the probability of successful transmission. In addition, the above time-frequency resources are periodic resources. In other words, the PUR is periodically distributed in the time domain and the frequency domain.

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

[0097] 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 first PUR.

[0098] 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. In the following text, for the sake of brevity, the description of the same or similar situations is omitted.

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

[0100] 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 timing 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 above-mentioned TAC, it is possible that the terminal device and the network device are out of uplink synchronization, resulting in the uplink data sent by the terminal device on the above-mentioned first PUR not being correctly received by the network device.

[0101] Exemplarily, after the terminal device sends a first request message to the network device, it receives a TAC from the network device. The TAC may carry a timing advance for uplink synchronization. Further, the terminal device sends uplink data to the network device based on the above-mentioned first PUR.

[0102] It can be understood that when the service of the terminal device changes, the size of the data volume to be transmitted may change accordingly. Or rather, the size of the data volume 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 the second PUR) that matches the size of the data volume according to the size of the data volume to be transmitted, and request the network device to activate the above-mentioned second PUR.

[0103] A possible implementation is that in the case of a change in the uplink data volume, the terminal device sends a second request message to the network device. The second request message is used to request the activation of the second PUR. The second PUR is one of the above-mentioned multiple PURs, and the second PUR has a different data volume size from that carried by the first PUR; and based on the second PUR, the terminal device sends uplink data to the network device. Correspondingly, the network device receives the second request message. The second request message is used to request the activation of the second PUR. The second PUR is one of the above-mentioned multiple PURs, and the second PUR has a different data volume size from that carried by the first PUR; and based on the second PUR, the network device receives uplink data from the terminal device.

[0104] Exemplarily, multiple pre-configured PURs in the network device include PUR 1, PUR 2, and PUR 3. Among them, the data volume carried by each PUR in PUR1, PUR 2, and PUR 3 is different. For example, the data volume that PUR 1 can carry is denoted as data volume 1, the data volume that PUR 2 can carry is denoted as data volume 2, and the data volume that PUR 3 can carry is denoted as data volume 3. If the data volume to be transmitted by the terminal device changes from data volume 1 to data volume 2, the terminal device can send a second request message to the network device to request the activation of PUR 2. Correspondingly, the network device receives the above second request message.

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

[0106] In other words, the second PUR can become effective after a period of time, or rather, the second PUR can be activated after a period of time. When the effective time of the second PUR arrives, the terminal device can send uplink data to the network device based on the above second PUR.

[0107] A possible design is that the effective time of the above second PUR can be predefined. Exemplarily, the effective time of the above second PUR can be the starting point in the time domain of the next second PUR. For example, the distribution of the second PUR in the time domain is 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. If the time slot occupied by the terminal device to send the second request message is, for example, time slot 2, then the effective time of the second PUR can be the starting point of time slot 3.

[0108] Exemplarily, the above second PUR can also become effective after a predefined offset value. For example, the effective time of the above second PUR is: the sending time of the second request message + the offset value.

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

[0110] It can be understood that in the idle state, the terminal device can send uplink data based on the activated PUR, and GNSS measurement needs to be completed before sending the uplink data. Taking the first PUR as an example among the multiple PURs above, in this application, the signal during the GNSS measurement process and the transmission of uplink data cannot be carried out simultaneously. 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 higher than that of the transmission of uplink data. That is to say, the terminal device gives priority to performing the GNSS measurement and then sends the uplink data after completing the GNSS measurement.

[0111] A possible implementation to solve the conflict between the GNSS measurement and the transmission of uplink data is that the network device sends the first indication information to the terminal device, and the first indication information indicates the duration for GNSS measurement, that is, the first indication information indicates which period of time is used for GNSS measurement, and the terminal device does not send uplink data during this period. Correspondingly, the terminal device receives the first indication information from the network device.

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

[0113] The first possible design is that the above first indication information includes the number of periods of the first PUR. Among them, the first PUR is periodically distributed in the time domain. That is to say, the network device can indicate the number of periods of the first PUR to the terminal device, and during this period, the terminal device performs GNSS measurement without transmitting uplink data.

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

[0115] Optionally, before receiving the first indication information from the network device, the above method further includes: the terminal device reports the validity period of the GNSS measurement and the duration required to complete the GNSS measurement to the network device. Correspondingly, the network device receives the validity period of the GNSS measurement and the duration required to complete the GNSS measurement from the terminal device.

[0116] Among them, the validity period of GNSS measurement can be understood as the validity period of the positioning information obtained by GNSS measurement. That is to say, in the case of exceeding the validity period, the positioning information obtained by GNSS measurement may not be highly accurate. Correspondingly, within the validity period, the positioning information obtained by GNSS measurement is relatively accurate. In addition, the duration required to complete GNSS measurement mentioned above can be understood as the duration required for the terminal device to perform GNSS measurement. This duration required to complete GNSS measurement may be determined by the configuration of the terminal device and is different from the duration configured by the network device for the terminal device to perform GNSS measurement. For example, the network device can configure the duration for the terminal device to perform GNSS measurement as 1 hour (such as from 9 o'clock to 10 o'clock), but the duration required for the terminal device to complete GNSS measurement is 30 minutes. The terminal device can independently determine the start time of GNSS measurement as long as it completes GNSS measurement before 10 o'clock.

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

[0118] In one example, if the validity period of GNSS measurement reported by the terminal device is 9 o'clock and the duration required to complete GNSS measurement is 30 minutes, then the network device determines that the terminal device needs to complete GNSS measurement before 9 o'clock. For example, if the distribution of the first PUR in the time domain is from 8:30 to 9 o'clock, which is from 8:30 to 8:40 and from 8:50 to 9 o'clock, then the number of cycles of the first PUR indicated by the network device to the terminal device can be 2. Another example, if the distribution of the first PUR in the time domain is from 8 o'clock to 9 o'clock, which is from 8 o'clock to 8:10, from 8:20 to 8:30, and from 8:40 to 8:50, then the number of cycles of the first PUR indicated by the network device to the terminal device can be 3.

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

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

[0121] The network device can indicate the starting point of GNSS measurement to the terminal device. After receiving the above indication information, the terminal device starts GNSS measurement at the starting point of GNSS measurement and does not send uplink data.

[0122] Another possible implementation to solve the transmission conflict between GNSS measurement and uplink data is that the terminal device sends a third indication information to the network device. The third indication information is used to indicate the duration for GNSS measurement, and the third indication information includes the number of cycles of the first PUR. That is to say, the terminal device can indicate the number of cycles of the skipped first PUR to the network device for GNSS measurement.

[0123] Exemplarily, the validity period of GNSS measurement is 9 o'clock, and the duration required for the terminal device to complete GNSS measurement is 30 minutes. Assuming that the distribution of the first PUR in the time domain is from 8:30 to 9:00, and it is from 8:30 to 8:40 and from 8:50 to 9:00, then the number of cycles of the first PUR indicated by the terminal device is 2.

[0124] It can be understood that since the satellite orbits the earth and the terminal device is also moving relative to the satellite, this may cause the terminal device using the network service to move from the coverage area of one satellite to the coverage area of another satellite. In this application, when the satellite switches but the network device does not switch, the above-mentioned multiple PURs are not released, where 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, where the base station is an example of the network device.

[0125] Among them, the non-release of the multiple PURs can be understood as: the above-mentioned multiple PURs are still in effect, or the terminal device can continue to use the above-mentioned multiple PURs.

[0126] Exemplarily, 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, then the terminal device can still perform uplink data transmission based on the multiple PURs configured by the base station.

[0127] It should be noted that when the satellite switches, the terminal device may need to re-perform GNSS measurement. Furthermore, the terminal device needs to transmit uplink data after completing GNSS measurement. Therefore, the above-mentioned multiple PURs can take effect after a period of time, or rather, the terminal device can continue to use the above-mentioned multiple PURs to transmit uplink data after a period of time. Specifically, how long it takes to take effect can include the following two possible designs:

[0128] In a possible design, when the source satellite (such as satellite 1) is used to forward messages between the network device and the terminal device, the network device may instruct the terminal device to continue transmitting uplink data on the above-mentioned multiple PURs after a preset duration, where the preset duration is determined based on the duration required for the terminal device to complete GNSS measurement. For example, if the duration required for the terminal device to complete GNSS measurement is 30 minutes, the network device may instruct the terminal device that it can continue transmitting uplink data on the above-mentioned multiple PURs after 30 minutes.

[0129] In another possible design, after the terminal device accesses the target satellite (such as satellite 2), the terminal device requests to activate one of the above-mentioned multiple PURs from the network device. The specific request process is the same as the process of requesting activation when the terminal device accesses the source satellite, and will not be elaborated here.

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

[0131] Above, the data transmission method provided by the embodiments of the present application has been described in detail with reference to the accompanying drawings. Below, the device provided by the embodiments of the present application will be described in detail with reference to the accompanying drawings.

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

[0133] Figure 3 is a schematic block diagram of a communication device 300 provided by the embodiments of the present application.

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

[0135] When the apparatus 300 is used to implement Figure 2 the functions of the terminal device in the method embodiments shown, the transceiver module 310 may be used to send 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, the plurality of PURs being pre-configured by the network device for the apparatus 300, and at least two of the plurality of PURs having different data volume sizes; the processing module 320 may be used to send uplink data to the network device based on the above-mentioned first PUR.

[0136] Optionally, the transceiver module 310 is further used to receive configuration information from the network device, where the configuration information is used to configure the above-mentioned plurality of PURs.

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

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

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

[0140] Optionally, the first indication information includes the number of periods of the first PUR, or the first indication information includes the running duration of a timer.

[0141] Optionally, the transceiver module 310 is further used to report to the network device the validity period of GNSS measurement and the duration required to complete GNSS measurement.

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

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

[0144] Optionally, the transceiver module 310 is further configured to send a second request message to the network device when the uplink data volume changes. 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 data volume carried by the second PUR is different from that carried by the first PUR; the processing module 320 is further configured to send uplink data to the network device based on the second PUR.

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

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

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

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

[0149] 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.

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

[0151] 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 higher than the priority of the uplink data transmission.

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

[0153] Optionally, the first indication information includes the number of periods of the first PUR, or the first indication information includes the running duration of a timer.

[0154] Optionally, the transceiver module 310 is further configured to receive the validity period of the GNSS measurement from the terminal device and the duration required to complete the GNSS measurement; the processing module 320 is further configured to determine the duration for the GNSS measurement according to the validity period of the GNSS measurement and the duration required to complete the GNSS measurement.

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

[0156] 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 the duration for the GNSS measurement, and the third indication information includes the number of cycles of the first PUR.

[0157] Optionally, when the uplink data volume changes, the transceiver module 310 is further configured to receive a second request message from the terminal device, where the second request message is used to request to activate a second PUR, the second PUR is one of the multiple PURs, and the data volume carried by the second PUR is different from that of the first PUR; the processing module 320 is further configured to receive uplink data from the terminal device based on the second PUR.

[0158] Optionally, the activation time of the second PUR is predefined or indicated by the device 300.

[0159] Optionally, when the activation time of the second PUR is indicated by the device 300, the activation time of the second PUR is carried in the TAC.

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

[0161] For a more detailed description of each of the above modules, reference can be directly made to Figure 2 the relevant descriptions in the method embodiments shown, which will not be elaborated here.

[0162] It should be understood that the division of modules in the embodiments of the present application is illustrative, merely a logical function division, and there may be other division methods in actual implementation. In addition, in each embodiment of the present application, each functional module may be integrated in one processor, may also exist separately physically, or two or more modules may be integrated in one module. The above integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0163] Figure 4 is another schematic block diagram of the communication device 400 provided by the embodiments of the present application.

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

[0165] As Figure 4 shown, the device 400 may include a processor 410, which may be used to execute computer programs or instructions in a memory to implement Figure 2 the steps executed by the terminal device or the steps executed by the network device in the method embodiments shown.

[0166] Optionally, the device 400 further includes a communication interface 420. Among them, the communication interface 420 may be used to communicate with other devices through a transmission medium, so that the device 400 can communicate with other devices. The communication interface 420 may be, for example, a transceiver, an interface, a bus, a circuit, or a device capable of implementing a transceiver function. The processor 410 may use the communication interface 420 to input and output data, and is used to implement Figure 2 the method described in the corresponding embodiment. Specifically, the device 400 may be used to implement the functions of the terminal device or the network device in the above method embodiments.

[0167] 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. The coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be electrical, mechanical, or other forms, for information interaction between devices, units, or modules. The processor 410 may cooperate with the memory 430. The processor 410 may execute the program instructions stored in the memory 430. At least one of the at least one memory may be included in the processor.

[0168] 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 may be electrical, mechanical, or other forms, for information interaction between devices, units, or modules. The processor 410 may cooperate with the memory 430. In the embodiments of the present application, 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 Figure 4 it is connected by a bus 440 between the processor 410, communication interface 420, and memory 430. The bus 440 is in Figure 4The connection among other components is only schematically illustrated by thick lines and is not limited thereto. The bus may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 4 it is only represented by a thick line in the figure, but it does not mean that there is only one bus or one type of bus.

[0169] This application also provides a computer program product, which includes: a computer program (which may also be referred to as code or instruction). When the computer program is run, it can implement Figure 2 the steps executed by the terminal device or the steps executed by the network device in the method described in the foregoing embodiments.

[0170] This application also provides a computer-readable storage medium, which stores a computer program (which may also be referred to as code or instruction). When the computer program is run, it can implement Figure 2 the steps executed by the terminal device or the steps executed by the network device in the method described in the foregoing embodiments.

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

[0172] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiments may be completed by the integrated logic circuit in the hardware of the processor or instructions in the form of software. The above-mentioned processor may 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, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed by the hardware decoding processor, or executed by a combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0173] 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 ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (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 but 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), synchlink DRAM (SLDRAM), and direct rambus 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.

[0174] The terms "unit", "module", etc. used in this specification may be used to represent computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. The units and modules in the embodiments of the present application have the same meaning and can be used interchangeably.

[0175] Those of ordinary skill in the art will realize that the various illustrative logical blocks and steps described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. A professional technician can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application. In 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. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling, direct coupling, or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical, or other forms.

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

[0177] In addition, in each embodiment of this application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit.

[0178] 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 (programs) are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.). 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 integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0179] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the technology, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs that can store program codes.

[0180] As described above, the above are only the specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed in the present application can easily think of changes or substitutions, which should all be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A data transmission method, characterized in that, including: sending a first request message to a network device, where the first request message is used to request activation of a first PUR among multiple pre-configured uplink resources PURs, the multiple PURs are pre-configured by the network device for a terminal device, and at least two PURs among the multiple PURs carry different amounts of data; sending uplink data to the network device based on the first PUR.

2. The method according to claim 1, characterized in that, Before sending the first request message to the network device, the method further includes: receiving configuration information from the network device, where the configuration information is used to configure the multiple 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: receiving a timing advance command TAC 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 global navigation satellite system GNSS measurement, the priority of the GNSS measurement is higher than the priority of uplink data transmission.

5. The method according to claim 4, characterized in that, The method further includes: receiving first indication information from the network device, where the first indication information indicates the duration for GNSS measurement.

6. The method according to claim 5, characterized in that, The first indication information includes the number of periods of the first PUR, or the first indication information includes the running duration 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 duration required to complete the GNSS measurement to the network device.

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

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

10. The method according to any one of claims 1 to 9, characterized in that, The method further includes: in the case where the uplink data volume changes, sending a second request message to the network device, where the second request message is used to request activation of a second PUR, the second PUR is one of the multiple PURs, and the second PUR carries a different amount of data from the first PUR; sending uplink data to the network device based on the second PUR.

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, sending the 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.

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, where the satellite is used to forward messages between the network device and the terminal device.

14. A data transmission method, characterized in that, including: Receive a first request message from a terminal device, where the first request message is used to request activation of a first PUR among multiple pre-configured uplink resources PUR, the multiple PURs are pre-configured by a network device for the terminal device, and at least two PURs among the multiple PURs carry different amounts of data; Receive uplink data from the terminal device based on the first PUR.

15. The method according to claim 14, wherein, Before receiving the first request message from the terminal device, the method further includes: Send 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, wherein, Before receiving the uplink data from the terminal device based on the first PUR, the method further includes: Send a timing advance command TAC to the terminal device, where the TAC is used for uplink synchronization.

17. The method according to any one of claims 14 to 16, wherein, 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 global navigation satellite system GNSS measurement, the priority of the GNSS measurement is higher than the priority of the uplink data transmission.

18. The method according to claim 17, wherein, The method further includes: Send first indication information to the terminal device, where the first indication information indicates the duration for GNSS measurement.

19. The method according to claim 18, wherein, The first indication information includes the number of periods of the first PUR, or, the first indication information includes the running duration of a timer.

20. The method according to claim 18 or 19, wherein, Before sending the first indication information to the terminal device, the method further includes: Receive the validity period of the GNSS measurement from the terminal device and the duration required to complete the GNSS measurement; Determine the duration for GNSS measurement according to the validity period of the GNSS measurement and the duration required to complete the GNSS measurement.

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

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

23. The method according to any one of claims 14 to 22, wherein, The method further includes: In the case where the uplink data volume changes, receive a second request message from the terminal device, where the second request message is used to request activation of a second PUR, the second PUR is one of the multiple PURs, and the second PUR carries a different amount of data from the first PUR; Receive uplink data from the terminal device based on the second PUR.

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

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

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

27. A communication device, wherein, Include a module for implementing the method according to any one of claims 1 to 13, or, include a module for implementing the method according to any one of claims 14 to 26.

28. A communication device, wherein, including a processor and a memory, wherein, the memory is used for storing a computer program; the processor is used for calling the computer program to enable the device to implement the method according to any one of claims 1 to 13, or to implement the method according to any one of claims 14 to 26.

29. A computer-readable storage medium, characterized in that, A computer program or instruction is stored in the storage medium, and 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 includes instructions, and when the instructions are run 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