Data transmission method, chip, terminal and storage medium

Abstract

The present invention provides a data transmission method, chip, terminal, and storage medium, relating to the field of communications technology. The method comprises: receiving and storing first information sent by a network; receiving second information sent by the network; determining a data transmission time based on the first and second information; and transmitting data to the network based on the data transmission time. The method provided in the present invention can effectively solve the time synchronization problem on the network side during beam switching and cross-beam transmission.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies, and in particular to a data transmission method, chip, terminal, and storage medium. Background Art

[0002] In non-terrestrial networks (NTNs), terminals send uplink data in advance based on the Timing Advance (TA) value to ensure uplink and downlink synchronization. For example, in the existing Physical Downlink Control Channel (PDCCH) scheduling the Physical Uplink Shared Channel (PUSCH), the Downlink Control Information (DCI) in the PDCCH indicates a scheduled delay value to the terminal, thereby determining the transmission resource location of the PUSCH.

[0003] However, in satellite communication networks, due to the significant propagation delay between terminals and satellites, terminals typically need to send ahead of time based on a predetermined timing advance to align uplink and downlink timing. However, the scheduling delay value indicated in the DCI is typically set too low to meet the larger timing advance requirements in satellite scenarios. In other words, based on the existing scheduling delay, terminals cannot perform timing advance transmission. This can cause problems with time synchronization between the terminal and the satellite, further reducing transmission efficiency between the terminal and the satellite. Summary of the Invention

[0004] The embodiments of the present application provide a data transmission method, chip, terminal and storage medium to provide a method for transmitting data at a fixed time.

[0005] In a first aspect, an embodiment of the present application provides a data transmission method, including:

[0006] Receiving and storing the first information sent by the network side;

[0007] receiving second information sent by the network side, and determining a data transmission time based on the first information and the second information;

[0008] Data is transmitted to the network side based on the data transmission time.

[0009] In one possible implementation manner, the first information is sent by the network side through SIB or RRC dedicated signaling.

[0010] In one possible implementation manner, the second information is sent by the network side through DCI or RAR Grant.

[0011] In one possible implementation, determining the data transmission time based on the first information and the second information includes:

[0012] Get carrier switching delay;

[0013] A data transmission time is determined based on the carrier switching delay, the first information, and the second information.

[0014] In one possible implementation, the first information includes timing offsets of multiple uplink carriers, and the second information is sent by the network side using a first beam, where the first beam corresponds to a first uplink carrier.

[0015] In one possible implementation, the second information includes index information of a second uplink carrier, and determining the data transmission time based on the first information and the second information includes:

[0016] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0017] A data transmission time is determined based on the timing offset of the second uplink carrier.

[0018] In one possible implementation, the second information includes index information of a second uplink carrier, and determining the data transmission time based on the first information and the second information includes:

[0019] Obtaining a timing offset of the first uplink carrier;

[0020] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0021] The timing offset of the first uplink carrier is compared with the timing offset of the second uplink carrier. If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the first uplink carrier. If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the second uplink carrier.

[0022] In one possible implementation, the first information includes a timing offset set of multiple uplink carriers, and the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier, wherein the timing offset set of each uplink carrier includes multiple timing offsets.

[0023] In one possible implementation, the second information includes index information of the second uplink carrier and a timing offset index identifier, and determining the data transmission time based on the first information and the second information includes:

[0024] querying the first information based on the index information of the second uplink carrier to obtain a timing offset set of the second uplink carrier;

[0025] querying the timing offset set of the second uplink carrier based on the timing offset index identifier to obtain the timing offset of the second uplink carrier corresponding to the timing offset index identifier;

[0026] A data transmission time is determined based on the timing offset of the second uplink carrier.

[0027] In one possible implementation manner, transmitting data to the network side based on the data transmission time includes:

[0028] Based on the data transmission time, data is transmitted to the network side using the second uplink carrier.

[0029] In one possible implementation, the data includes a transport block, the second information includes index information of a second uplink carrier and data segmentation information, the data segmentation information is used to characterize segmentation of the transport block to obtain a first data segment, a second data segment, and a mapping relationship between the data segment and the uplink carrier, and determining the data transmission time based on the first information and the second information includes:

[0030] Obtaining a timing offset of the first uplink carrier;

[0031] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0032] comparing a timing offset of the first uplink carrier with a timing offset of the second uplink carrier;

[0033] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first data segment based on the timing offset of the first uplink carrier, and determining the data transmission time of the second data segment based on the timing offset of the first uplink carrier and the transmission duration of the first data segment;

[0034] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time of the first data segment is determined based on the timing offset of the second uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; or the data transmission time of the first data segment is determined based on the timing offset of the first uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment;

[0035] The transmission duration of the first data segment is determined by the preset number of retransmissions of the first data segment.

[0036] In one possible implementation, the first data segment corresponds to the first uplink carrier, the second data segment corresponds to the second uplink carrier, and the transmitting data to the network side based on the data transmission time includes:

[0037] Transmitting the first data segment to the network side using the first uplink carrier based on a data transmission time of the first data segment;

[0038] Based on the data transmission time of the second data segment, the second data segment is transmitted to the network side using the second uplink carrier.

[0039] In one possible implementation, the data includes a first transport block set and a second transport block set, the first transport block set and the second transport block set respectively include one or more transport blocks, the second information includes index information of a second uplink carrier and transport block identification information, the transport block identification information is used to characterize a mapping relationship between a transport block and an uplink carrier, and determining a data transmission time based on the first information and the second information includes:

[0040] Obtaining a timing offset of the first uplink carrier;

[0041] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0042] comparing a timing offset of the first uplink carrier with a timing offset of the second uplink carrier;

[0043] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the first uplink carrier and the transmission duration of the first transport block set;

[0044] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the second uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; or determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set;

[0045] The transmission duration of the first transmission block set is determined by the accumulated transmission duration of all transmission blocks in the first transmission block set, and the transmission duration of each transmission block is determined by the preset number of retransmissions of each transmission block.

[0046] In one possible implementation, the first transmission block set corresponds to the first uplink carrier, the second transmission block set corresponds to the second uplink carrier, and transmitting data to the network side based on the data transmission time includes:

[0047] transmitting the first transport block set to the network side using the first uplink carrier based on a data transmission time instant of the first transport block set;

[0048] Based on the data transmission time of the second transmission block set, the second transmission block set is transmitted to the network side by using the second uplink carrier.

[0049] In a second aspect, an embodiment of the present application provides a chip, including:

[0050] A first receiving module, configured to receive and store first information sent by a network side;

[0051] a second receiving module, configured to receive second information sent by the network side, and determine a data transmission time based on the first information and the second information;

[0052] A transmission module is used to transmit data to the network side based on the data transmission time.

[0053] In one possible implementation manner, the first information is sent by the network side through SIB or RRC dedicated signaling.

[0054] In one possible implementation manner, the second information is sent by the network side through DCI or RAR Grant.

[0055] In one possible implementation, the second receiving module is further configured to obtain a carrier switching delay; and determine a data transmission time based on the carrier switching delay, the first information, and the second information.

[0056] In one possible implementation, the first information includes timing offsets of multiple uplink carriers, and the second information is sent by the network side using a first beam, where the first beam corresponds to a first uplink carrier.

[0057] In one possible implementation, the second information includes index information of the second uplink carrier, and the second receiving module includes:

[0058] a query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0059] A determining unit is configured to determine a data transmission time based on a timing offset of the second uplink carrier.

[0060] In one possible implementation, the second information includes index information of the second uplink carrier, and the second receiving module includes:

[0061] an acquiring unit, configured to acquire a timing offset of the first uplink carrier;

[0062] a query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0063] A determination unit is used to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier. If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the first uplink carrier; if the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the second uplink carrier.

[0064] In one possible implementation, the first information includes a timing offset set of multiple uplink carriers, and the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier, wherein the timing offset set of each uplink carrier includes multiple timing offsets.

[0065] In one possible implementation, the second information includes index information of the second uplink carrier and a timing offset index identifier, and the second receiving module includes:

[0066] A first query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset set of the second uplink carrier;

[0067] A second query unit, configured to query the timing offset set of the uplink carrier based on the timing offset index identifier, and obtain the timing offset of the second uplink carrier corresponding to the timing offset index identifier;

[0068] A determining unit is configured to determine a data transmission time based on a timing offset of the second uplink carrier.

[0069] In one possible implementation manner, the transmission module is further configured to transmit data to the network side using the second uplink carrier based on the data transmission time.

[0070] In one possible implementation, the data includes a transport block, the second information includes index information of a second uplink carrier and data segmentation information, the data segmentation information is used to characterize segmentation of the transport block to obtain a first data segment, a second data segment, and a mapping relationship between the data segment and the uplink carrier, and the second receiving module includes:

[0071] an acquiring unit, configured to acquire a timing offset of the first uplink carrier;

[0072] a query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0073] a determining unit, configured to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier;

[0074] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first data segment based on the timing offset of the first uplink carrier, and determining the data transmission time of the second data segment based on the timing offset of the first uplink carrier and the transmission duration of the first data segment;

[0075] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time of the first data segment is determined based on the timing offset of the second uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; or the data transmission time of the first data segment is determined based on the timing offset of the first uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment;

[0076] The transmission duration of the first data segment is determined by the preset number of retransmissions of the first data segment.

[0077] In one possible implementation, the first data segment corresponds to the first uplink carrier, and the second data segment corresponds to the second uplink carrier. The transmission module is further used to transmit the first data segment to the network side using the first uplink carrier based on the data transmission time of the first data segment; and transmit the second data segment to the network side using the second uplink carrier based on the data transmission time of the second data segment.

[0078] In one possible implementation, the data includes a first transport block set and a second transport block set, where the first transport block set and the second transport block set respectively include one or more transport blocks, the second information includes index information of a second uplink carrier and transport block identification information, where the transport block identification information is used to characterize a mapping relationship between a transport block and an uplink carrier, and the second receiving module includes:

[0079] an acquiring unit, configured to acquire a timing offset of the first uplink carrier;

[0080] a query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0081] a determining unit, configured to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier;

[0082] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the first uplink carrier and the transmission duration of the first transport block set;

[0083] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the second uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; or determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set;

[0084] The transmission duration of the first transmission block set is determined by the accumulated transmission duration of all transmission blocks in the first transmission block set, and the transmission duration of each transmission block is determined by the preset number of retransmissions of each transmission block.

[0085] In one possible implementation, the first transmission block set corresponds to the first uplink carrier, and the second transmission block set corresponds to the second uplink carrier. The transmission module is further used to transmit the first transmission block set to the network side using the first uplink carrier based on the data transmission time of the first transmission block set; and transmit the second transmission block set to the network side using the second uplink carrier based on the data transmission time of the second transmission block set.

[0086] In a third aspect, an embodiment of the present application provides a terminal, including:

[0087] A memory, wherein the memory is used to store computer program code, wherein the computer program code includes instructions, and when the terminal reads the instructions from the memory, the terminal executes the following steps:

[0088] Receiving and storing the first information sent by the network side;

[0089] receiving second information sent by the network side, and determining a data transmission time based on the first information and the second information;

[0090] Data is transmitted to the network side based on the data transmission time.

[0091] In one possible implementation manner, the first information is sent by the network side through SIB or RRC dedicated signaling.

[0092] In one possible implementation manner, the second information is sent by the network side through DCI or RAR Grant.

[0093] In one possible implementation, when the instruction is executed by the terminal, causing the terminal to perform the step of determining a data transmission time based on the first information and the second information includes:

[0094] Get carrier switching delay;

[0095] A data transmission time is determined based on the carrier switching delay, the first information, and the second information.

[0096] In one possible implementation, the first information includes timing offsets of multiple uplink carriers, and the second information is sent by the network side using a first beam, where the first beam corresponds to a first uplink carrier.

[0097] In one possible implementation, the second information includes index information of a second uplink carrier. When the instruction is executed by the terminal, causing the terminal to perform the step of determining a data transmission time based on the first information and the second information includes:

[0098] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0099] A data transmission time is determined based on the timing offset of the second uplink carrier.

[0100] In one possible implementation, the second information includes index information of a second uplink carrier. When the instruction is executed by the terminal, causing the terminal to perform the step of determining a data transmission time based on the first information and the second information includes:

[0101] Obtaining a timing offset of the first uplink carrier;

[0102] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0103] The timing offset of the first uplink carrier is compared with the timing offset of the second uplink carrier. If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the first uplink carrier. If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the second uplink carrier.

[0104] In one possible implementation, the first information includes a timing offset set of multiple uplink carriers, and the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier, wherein the timing offset set of each uplink carrier includes multiple timing offsets.

[0105] In one possible implementation, the second information includes index information of the second uplink carrier and a timing offset index identifier. When the instruction is executed by the terminal, causing the terminal to perform the step of determining the data transmission time based on the first information and the second information includes:

[0106] querying the first information based on the index information of the second uplink carrier to obtain a timing offset set of the second uplink carrier;

[0107] querying the timing offset set of the second uplink carrier based on the timing offset index identifier to obtain the timing offset of the second uplink carrier corresponding to the timing offset index identifier;

[0108] A data transmission time is determined based on the timing offset of the second uplink carrier.

[0109] In one possible implementation, when the instruction is executed by the terminal, causing the terminal to perform the step of transmitting data to the network side based on the data transmission time includes:

[0110] Based on the data transmission time, data is transmitted to the network side using the second uplink carrier.

[0111] In one possible implementation, the data includes a transport block, the second information includes index information of a second uplink carrier and data segmentation information, the data segmentation information is used to represent segmentation of the transport block to obtain a first data segment, a second data segment, and a mapping relationship between the data segment and the uplink carrier. When the above instruction is executed by the above terminal, causing the above terminal to perform the step of determining a data transmission time based on the first information and the second information includes:

[0112] Obtaining a timing offset of the first uplink carrier;

[0113] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0114] comparing a timing offset of the first uplink carrier with a timing offset of the second uplink carrier;

[0115] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first data segment based on the timing offset of the first uplink carrier, and determining the data transmission time of the second data segment based on the timing offset of the first uplink carrier and the transmission duration of the first data segment;

[0116] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time of the first data segment is determined based on the timing offset of the second uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; or the data transmission time of the first data segment is determined based on the timing offset of the first uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment;

[0117] The transmission duration of the first data segment is determined by the preset number of retransmissions of the first data segment.

[0118] In one possible implementation, the first data segment corresponds to the first uplink carrier, and the second data segment corresponds to the second uplink carrier. When the instruction is executed by the terminal, causing the terminal to execute the step of transmitting data to the network side based on the data transmission time includes:

[0119] Transmitting the first data segment to the network side using the first uplink carrier based on a data transmission time of the first data segment;

[0120] Based on the data transmission time of the second data segment, the second data segment is transmitted to the network side using the second uplink carrier.

[0121] In one possible implementation, the data includes a first transport block set and a second transport block set, the first transport block set and the second transport block set respectively include one or more transport blocks, the second information includes index information of a second uplink carrier and transport block identification information, the transport block identification information is used to characterize a mapping relationship between a transport block and an uplink carrier, and determining a data transmission time based on the first information and the second information includes:

[0122] Obtaining a timing offset of the first uplink carrier;

[0123] querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0124] comparing a timing offset of the first uplink carrier with a timing offset of the second uplink carrier;

[0125] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the first uplink carrier and the transmission duration of the first transport block set;

[0126] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the second uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; or determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set;

[0127] The transmission duration of the first transmission block set is determined by the accumulated transmission duration of all transmission blocks in the first transmission block set, and the transmission duration of each transmission block is determined by the preset number of retransmissions of each transmission block.

[0128] In one possible implementation, the first transmission block set corresponds to the first uplink carrier, the second transmission block set corresponds to the second uplink carrier, and transmitting data to the network side based on the data transmission time includes:

[0129] transmitting the first transport block set to the network side using the first uplink carrier based on a data transmission time instant of the first transport block set;

[0130] Based on the data transmission time of the second transmission block set, the second transmission block set is transmitted to the network side by using the second uplink carrier.

[0131] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer-readable storage medium is run on a computer, the computer executes the method described in the first aspect.

[0132] In a fifth aspect, an embodiment of the present application provides a computer program, which, when executed by a computer, is used to execute the method described in the first aspect.

[0133] In one possible design, the program in the fifth aspect may be stored in whole or in part on a storage medium packaged with the processor, or may be stored in whole or in part on a memory not packaged with the processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0134] Figure 1 Schematic diagram of application scenarios provided by embodiments of the present application;

[0135] Figure 2 A flowchart of an embodiment of the data transmission method provided by this application;

[0136] Figure 3 A schematic diagram of an embodiment of the data transmission timing provided by this application;

[0137] Figure 4 A flowchart of another embodiment of the data transmission method provided by the present application;

[0138] Figure 5 A flowchart of another embodiment of the data transmission method provided by the present application;

[0139] Figure 6 A schematic diagram of another embodiment of the data transmission timing provided by this application;

[0140] Figure 7 A schematic diagram of another embodiment of the data transmission timing provided by this application;

[0141] Figure 8 A flowchart of another embodiment of the data transmission method provided by this application;.

[0142] Figure 9 A schematic diagram of another embodiment of the data transmission timing provided by this application;

[0143] Figure 10 A schematic diagram of another embodiment of the data transmission timing provided by this application;

[0144] Figure 11 A schematic diagram of the structure of the chip provided in the embodiment of the present application;

[0145] Figure 12 A schematic diagram of the structure of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0146] The following describes the technical solutions in the embodiments of the present application in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, " / " represents "or." For example, A / B can represent A or B. "And / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone.

[0147] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0148] In an NTN, for example, a satellite communication network, a cell typically contains multiple beams. Due to the rapid movement of satellites, terminals need to frequently switch beams. When a terminal (for example, an IoT device) accesses the satellite communication network, a beam management mechanism is required to allocate communication resources. However, current physical network protocols lack a corresponding beam management mechanism.

[0149] Through research on the above problems, the inventors found that carrier management is supported in the Internet of Things, that is, the allocation of communication resources in the Internet of Things is usually based on carriers. For example, in an Internet of Things network, a single-frequency cell usually has only 180 kHz of bandwidth. In addition to the narrowband primary synchronization signal (NPSS), narrowband secondary synchronization signal (NSSS) and system information block (SIB), the remaining service channel capacity is very small. Therefore, in order to support a large number of terminals, multiple frequencies need to be used to increase network capacity. In addition to the anchor carrier that supports simultaneous carrying of NPSS, NSSS, narrowband physical broadcast channel (NPBCH), narrowband physical downlink control channel (NPDCCH) and narrowband physical downlink shared channel (NPDSCH), the cell can also include multiple non-anchor carriers that only carry NPDCCH and NPDSCH, but do not carry NPSS, NSSS and NPBCH. The spectrum bandwidth of each carrier is 180kHz, and the maximum spectrum span of all carriers in a cell does not exceed 20MHz. Terminals can transmit data on non-anchor carriers.

[0150] Therefore, a mapping relationship can be established between carriers and beams. For example, each carrier corresponds to a beam. For example, carrier 1 corresponds to beam 1, and carrier 2 corresponds to beam 2. In this way, beam switching can be achieved through carrier switching, thereby realizing beam management.

[0151] However, when the network switches between different beams, the transmission delay between the terminal and the satellite varies. Currently, the network only considers the scheduling delay, not the transmission delay between the terminal and the satellite. This can cause problems with time synchronization between the terminal and the satellite, which in turn affects the transmission efficiency between the terminal and the satellite.

[0152] Based on the above problems, an embodiment of the present application proposes a data transmission method.

[0153] Now combined Figures 1-10 The data transmission method provided in the embodiment of the present application is described. Figure 1 For the application scenarios provided in the embodiments of this application, please refer to Figure 1 The above application scenario includes a terminal 100 and a satellite 200. It is understandable that the satellite 200 is a network-side device and does not constitute a limitation on the embodiments of the present application. In some embodiments, the network-side device may also be embodied in other forms.

[0154] A terminal may also be referred to as a terminal device, user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment. A terminal may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, an Internet of Vehicles terminal, a computer, a laptop computer, a handheld communication device, a handheld computing device, a satellite wireless device, a wireless modem card, a TV set-top box (STB), customer premises equipment (CPE), and / or other devices for communicating on a wireless system, as well as next-generation communication systems, such as mobile terminals in a 5G network or mobile terminals in a future evolved Public Land Mobile Network (PLMN) network. The terminal can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design everyday wearables, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are full-featured, large in size, and can achieve full or partial functions independently of smartphones, such as smart watches or smart glasses, as well as those that focus on a specific type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring. The terminal can also be an Internet of Things device.

[0155] The embodiment of the present application does not specifically limit the specific form of the above-mentioned terminal.

[0156] Figure 2 A flowchart of an embodiment of the data transmission method provided in this application includes:

[0157] Step 101: Satellite 200 sends timing offset configuration information.

[0158] Specifically, the satellite 200 can send the timing offset configuration information by broadcasting. Exemplarily, the satellite 200 can broadcast the system broadcast message (for example, SIB) through the NPBCH, and the SIB can carry the above-mentioned timing offset configuration information. Among them, the timing offset configuration information can include multiple timing offsets, and each timing offset can correspond to an uplink carrier. It can be understood that since each uplink carrier corresponds to a beam, the timing offset of each uplink carrier can also correspond to a beam, thereby achieving different uplink carriers or beams corresponding to different timing offsets. Table 1 is a timing offset configuration information table. As shown in Table 1, the timing offset configuration information table may include a mapping relationship between uplink carriers, beams and timing offsets.

[0159] Table 1

[0160] Uplink carrier ID Beam ID Timing offset Uplink carrier 1 Beam 1 T_offset1 Uplink carrier 2 Beam 2 T_offset2 … … …

[0161] It is understood that Table 1 above only illustrates the mapping relationship between uplink carriers, beams, and timing offsets, and does not limit the embodiments of the present application. In some embodiments, the timing offset configuration information may also include a mapping relationship between uplink carriers and timing offsets or a mapping relationship between beams and timing offsets, wherein the mapping relationship between uplink carriers and beams may be pre-configured in terminal 100.

[0162] It should be noted that the timing offset of each uplink carrier may be determined by the transmission delay between the terminal 100 and the satellite 200 .

[0163] In addition, the above Table 1 only exemplarily represents the identity of the uplink carrier in an ID manner, and does not constitute a limitation on the embodiments of the present application. In some embodiments, the uplink carrier may also be identified in an index manner.

[0164] Optionally, satellite 200 may also transmit the timing offset configuration information via RRC dedicated signaling. For example, after an RRC connection is established between terminal 100 and satellite 200, satellite 200 may transmit RRC dedicated signaling to terminal 100, which may include the timing offset configuration information. For details on RRC dedicated signaling, please refer to the relevant 3GPP protocols and will not be further described here.

[0165] Step 102: The terminal 100 receives the timing offset configuration information sent by the satellite 200 and stores it.

[0166] In step 103 , the satellite 200 prepares to switch from the first beam to the second beam, and sends the ID of the second carrier to the terminal 100 via the first beam.

[0167] Specifically, due to the rapid movement of satellite 200, the beams used between satellite 200 and terminal 100 frequently switch. Therefore, satellite 200 can notify the target beam after the switch via a downlink message. In a specific implementation, the downlink message can be a DCI or a Random Access Response Grant (RAR Grant). The first beam can be any beam in the beam resources of satellite 200. The first beam can be the beam before the switch, for example, beam 1 in Table 1. The first beam corresponds to a first carrier, which can be one of the carrier resources of terminal 100. For example, the first carrier can be carrier 1 in Table 1. The second beam can be another beam in the beam resources of satellite 200. The second beam can be the target beam after the switch. For example, the second beam can be beam 2 in Table 1. The second beam corresponds to a second carrier, which can be another carrier in the carrier resources of terminal 100. For example, the second carrier can be carrier 2 in Table 1.

[0168] For example, the satellite 200 may send DCI via the PDCCH where the first beam is located, or send RAR Grant via a random access (RA) process. The specific RA process may refer to the relevant 3GPP protocol and will not be described in detail here. The DCI or RAR Grant may include the ID of the second carrier.

[0169] Optionally, the DCI or RAR Grant may also include a scheduling delay.

[0170] It can be understood that the above example only illustrates the way in which the ID of the second carrier is included in the above downlink message (for example, DCI or RAR Grant), and does not constitute a limitation on the embodiments of the present application. In some embodiments, since there is a mapping relationship between the uplink carrier and the beam, the ID of the above second carrier can also be replaced by the ID of the second beam.

[0171] In step 104 , the terminal 100 receives the ID of the second carrier sent by the satellite 200 and determines the data transmission time based on the ID of the second carrier.

[0172] Specifically, because satellite 200 transmits the DCI or RAR Grant via the first beam, terminal 100 can receive the DCI or RAR Grant via the first carrier based on the mapping relationship between the uplink carrier and the beam. Upon receiving the DCI or RAR Grant transmitted by satellite 200, terminal 100 can obtain the scheduling delay and the ID of the second carrier contained in the DCI or RAR Grant.

[0173] Then, based on the ID of the second carrier, the stored timing offset configuration information can be queried to obtain the timing offset corresponding to the second carrier (for example, T_offset2). After obtaining the timing offset of the second carrier, the data transmission time can be determined based on the above scheduling delay and the timing offset of the second carrier. Exemplarily, the data transmission time T = T_start + T0 + T_offset2, where T_start is the starting time and T0 is the above scheduling delay.

[0174] Optionally, since there is a carrier switching delay during the carrier switching process, the carrier switching delay may also be considered when calculating the data transmission time T. For example, the data transmission time T = T_start + T0 + T_offset2 + T1, where T1 is the carrier switching delay.

[0175] Now let's take DCI as an example to illustrate. Figure 3 As shown, satellite 200 transmits DCI to terminal 100 via the PDCCH containing the first beam. Based on the mapping between uplink carriers and beams, terminal 100 receives the DCI transmitted by satellite 200 via the first carrier. The time at which terminal 100 completely receives the DCI is T_start. After terminal 100 completely receives the DCI, it can obtain the scheduling delay T0 and the timing offset T_offset2 of the second carrier contained in the DCI and can transmit data at time T_start + T0 + T_offset2. For example, data can be transmitted via the PUSCH containing the second carrier at time T_start + T0 + T_offset2.

[0176] Optionally, after obtaining the timing offset T_offset2 of the second carrier, the timing offset T_offset1 of the first carrier may be further obtained. In this case, the above T_offset1 may be compared with T_offset2.

[0177] If T_offset1>=T_offset2, then the data transmission time T=T_start+T0+T_offset1;

[0178] If T_offset1<=T_offset2, then the data transmission time T=T_start+T0+T_offset2.

[0179] It is understandable that Figure 3 The DCI scenario is merely exemplified and does not limit the embodiments of the present application. In some embodiments, the data transmission time may also be determined by means of RAR Grant.

[0180] Step 105: The terminal 100 sends data to the satellite 200 based on the data transmission time.

[0181] Specifically, after the terminal 100 determines the data transmission time, it can use the PUSCH where the second carrier is located to send data to the satellite 200 at the data transmission time.

[0182] In an embodiment of the present application, the network side configures the transmission delay based on each beam. When the network side switches to the target carrier, the terminal side determines the corresponding transmission delay based on the target carrier, and determines the data transmission time based on the transmission delay. This can achieve time synchronization between the terminal side and the network side, thereby improving the transmission efficiency between the terminal side and the network side.

[0183] Figure 4 A flowchart of another embodiment of the data transmission method provided in this application includes:

[0184] Step 201: Satellite 200 sends timing offset set configuration information.

[0185] Specifically, the satellite 200 can send the timing offset set configuration information by broadcasting. Exemplarily, the satellite 200 can broadcast the system broadcast message (for example, SIB) through the NPBCH, and the SIB can carry the above-mentioned timing offset set configuration information. Among them, the timing offset set configuration information can include multiple timing offset sets, each timing offset set can correspond to an uplink carrier, and each timing offset set can include multiple timing offsets. It can be understood that since each uplink carrier corresponds to a beam, the timing offset set of each uplink carrier can also correspond to a beam, thereby achieving different uplink carriers or beams corresponding to different timing offsets. Table 2 is a timing offset set configuration information table. As shown in Table 2, the timing offset set configuration information table may include a mapping relationship between uplink carriers, beams and timing offset sets.

[0186] Table 2

[0187] Uplink carrier ID Beam ID Timing Offset Collection Uplink carrier 1 Beam 1 T_offset11, T_offset12 Uplink carrier 2 Beam 2 T_offset21, T_offset22 … … …

[0188] It is understood that Table 2 above only illustrates the number of timing offsets in a timing offset set and does not limit the embodiments of the present application. In some embodiments, each timing offset set may further include three or more timing offsets.

[0189] Optionally, the satellite 200 may also transmit the timing offset set configuration information via RRC dedicated signaling. For example, after an RRC connection is established between the terminal 100 and the satellite 200, the satellite 200 may transmit RRC dedicated signaling to the terminal 100, and the RRC dedicated signaling may carry the timing offset set configuration information.

[0190] In step 202, the terminal 100 receives the timing offset set configuration information sent by the satellite 200 and stores it.

[0191] In step 203 , the satellite 200 prepares to switch from the first beam to the second beam, and sends the ID and index of the second carrier to the terminal 100 via the first beam.

[0192] Specifically, the satellite 200 can send the ID and index identifier of the second carrier to the terminal 100, wherein the ID and index identifier of the second carrier can be carried by DCI or RAR Grant. The index identifier is used to represent the index of the timing offset in the timing offset set. In a specific implementation, the above-mentioned index identifier can be indicated by a special field in the DCI or RAR Grant. Exemplarily, if the timing offset set includes 2 timing offsets, the special field can include 1 bit (for example, the index identifier can be 0 or 1). Taking uplink carrier 1 as an example, if the index identifier is "0", it can indicate the first timing offset (for example, T_offset11); if the index identifier is "1", it can indicate the second timing offset (for example, T_offset12).

[0193] Optionally, the DCI or RAR Grant may also carry a scheduling delay.

[0194] In step 204 , the terminal 100 receives the ID and index identifier of the second carrier sent by the satellite 200 , and determines the data transmission time based on the ID and index identifier of the second carrier.

[0195] Specifically, because satellite 200 transmits the DCI or RAR Grant via the first beam, terminal 100 can receive the DCI or RAR Grant via the first carrier based on the mapping relationship between the uplink carrier and the beam. Upon receiving the DCI or RAR Grant transmitted by satellite 200, terminal 100 can obtain the scheduling delay, the ID of the second carrier, and the index identifier contained in the DCI or RAR Grant.

[0196] Then, based on the ID of the second carrier, the timing offset set configuration information can be queried to obtain the timing offset set corresponding to the second carrier. After obtaining the timing offset set of the second carrier, the timing offset in the timing offset set can be determined based on the above-mentioned index identifier (for example, the timing offset can be T_offset21 or T_offset22 in the timing offset set of the second carrier), and the data transmission time can be determined based on the scheduling delay and the determined timing offset of the second carrier. Exemplarily, if the timing offset in the timing offset set of the second carrier is determined to be T_offset21, the data transmission time T = T_start + T0 + T_offset21.

[0197] Optionally, since there is a carrier switching delay during the carrier switching process, the carrier switching delay may also be considered when calculating the data transmission time T. For example, the data transmission time T = T_start + T0 + T_offset21 + T1, where T1 is the carrier switching delay.

[0198] Step 205: The terminal 100 sends data to the satellite 200 based on the data transmission time.

[0199] Specifically, after the terminal 100 determines the data transmission time, it can use the PUSCH where the second carrier is located to send data to the satellite 200 at the data transmission time.

[0200] In an embodiment of the present application, the network side configures a transmission delay set based on each beam. When the network side switches to the target carrier, any transmission delay can be selected from the transmission delay set, and the terminal side determines the sending time based on the transmission delay indicated by the network side. This can improve the flexibility of transmission delay selection, and can achieve time synchronization between the terminal side and the network side, thereby improving the transmission efficiency of the terminal side and the network side.

[0201] The above Figure 2-Figure 4 The following uses the example of switching from the first beam to the second beam on the network side to explain Figures 5-10 Take cross-beam data transmission as an example for explanation.

[0202] Figure 5 A flowchart of another embodiment of the data transmission method provided in this application includes:

[0203] Step 301: Satellite 200 sends timing offset configuration information.

[0204] Specifically, the satellite 200 may send the timing offset configuration information by broadcasting. Exemplarily, the satellite 200 may broadcast a system broadcast message (e.g., SIB) via the NPBCH, and the SIB may carry the timing offset configuration information. The timing offset configuration information may include multiple timing offsets, each of which may correspond to an uplink carrier. It is understandable that, since each uplink carrier corresponds to a beam, the timing offset of each uplink carrier may also correspond to a beam, thereby enabling different uplink carriers or beams to correspond to different timing offsets.

[0205] Optionally, the satellite 200 may also send the timing offset configuration information via RRC dedicated signaling. For example, after an RRC connection is established between the terminal 100 and the satellite 200, the satellite 200 may send RRC dedicated signaling to the terminal 100, and the RRC dedicated signaling may carry the timing offset configuration information.

[0206] In step 302, the terminal 100 receives the timing offset configuration information sent by the satellite 200 and stores it.

[0207] In step 303, the satellite 200 sends instruction information to the terminal 100 via the first beam, instructing the terminal 100 to perform segmented transmission of a transmission block scheduled this time.

[0208] Specifically, to improve the utilization efficiency between beams, satellite 200 may segment the currently scheduled transport blocks and transmit them separately on two beams (for example, on the first beam and the second beam). In a specific implementation, satellite 200 may send indication information to terminal 100. This indication information may be carried by DCI or RAR Grant. The indication information may include the scheduling delay, the ID of the second carrier, and data segmentation information. The data segmentation information is used to indicate the segmentation of the currently scheduled transport blocks and the correspondence between the segmented transport blocks and the uplink carriers. Table 3 is an example table of data segmentation information.

[0209] Table 3

[0210]

[0211] As shown in Table 3, the data segmentation information may include a data identification field and a carrier ID field, wherein the data identification field is used to identify the segmentation method of the transport block. For example, assuming that a transport block (TB) is 1024 bytes, if the transport block is segmented, a first data segment with a length of 400 bytes (for example, the first byte is 0 and the last byte is 399) and a second data segment with a length of 624 bytes (for example, the first byte is 400 and the last byte is 1023) are obtained respectively. The first data segment corresponds to uplink carrier 1, that is, the terminal 100 can use the first carrier (for example, the first carrier can be uplink carrier 1 in Table 3, and the uplink carrier 1 corresponds to the first beam) to transmit the first data segment; and the second data segment corresponds to uplink carrier 2, that is, the terminal 100 can use the second carrier (for example, the second carrier can be uplink carrier 2 in Table 3, and the uplink carrier 2 corresponds to the second beam) to transmit the second data segment.

[0212] It can be understood that the above Table 3 only exemplifies the method of segmenting data through the above-mentioned related domains, and does not constitute a limitation on the embodiments of the present application. In some embodiments, the data segmentation information may also include more or fewer domains.

[0213] In step 304, the terminal 100 receives the indication information sent by the satellite 200 and determines the data transmission time based on the indication information.

[0214] Specifically, since satellite 200 transmits the DCI or RAR Grant via the first beam, terminal 100 can receive the DCI or RAR Grant via the first carrier based on the mapping relationship between the uplink carrier and the beam. After receiving the DCI or RAR Grant transmitted by satellite 200, terminal 100 can obtain the indication information (e.g., scheduling delay, second carrier ID, and data segmentation information) contained in the DCI or RAR Grant.

[0215] Then, based on the ID of the second carrier, the timing offset configuration information can be queried to obtain the timing offset corresponding to the second carrier (for example, T_offset2 in Table 1). After obtaining the timing offset of the second carrier, the timing offset corresponding to the first carrier (for example, T_offset1 in Table 1) can also be obtained, and the data transmission time of each data segment can be determined based on the above scheduling delay, the timing offset of the first carrier, and the timing offset of the second carrier. For example,

[0216] If T_offset1>=T_offset2, then the data transmission time of the first data segment is T_1=T_start+T0+T_offset1 (for the convenience of explanation, the "data transmission time of the first data segment" is referred to as the "first time" below), and the data transmission time of the second data segment is T_2=T_start+T0+T_offset1+T1+T2 (for the convenience of explanation, the "data transmission time of the second data segment" is referred to as the "second time" below); wherein, T_start is the starting time, T0 is the above-mentioned scheduling delay, T1 is the carrier switching delay, and T2 is the transmission duration of the first data segment. The transmission duration T2 of the first data segment may include the cumulative duration of the first transmission and the retransmission of the first data segment, wherein the number of retransmissions may be pre-configured (for example, the maximum number of uplink retransmissions may be configured to be 128 times).

[0217] If T_offset1<=T_offset2, then the first time T_1=T_start+T0+T_offset2, and the second time T_2=T_start+T0+T_offset2+T1+T2.

[0218] Now combined Figure 6 To explain, such as Figure 6 As shown, satellite 200 sends DCI to terminal 100 via the PDCCH where the first beam is located, indicating that the scheduled transport block is divided into two data segments (e.g., a first data segment and a second data segment), which are transmitted on the first carrier corresponding to the first beam and the second carrier corresponding to the second beam, respectively. After completely receiving the DCI sent by satellite 200, terminal 100 determines the starting time T_start, calculates the timing offset T_offset2 of the second carrier, and compares the timing offset T_offset2 of the second carrier with the timing offset T_offset1 of the first carrier. Assuming T_offset1>=T_offset2, terminal 100 determines the first time T_1=T_start+T0+T_offset1, where T0 is the scheduling delay indicated in the DCI. Next, assuming that the cumulative duration of transmitting (eg, including initial transmission and retransmission) the first data segment is T2, the terminal 100 may determine the second time T_2=T_start+T0+T_offset1+T1+T2, where T1 is the carrier switching delay.

[0219] Optionally, if T_offset1<=T_offset2, then the first time T_1=T_start+T0+T_offset1, and the second time T_2=T_start+T0+T_offset2+T1+T2.

[0220] Now, in combination with Figure 7 it is described as follows. As Figure 7 shown, the satellite 200 sends DCI to the terminal 100 through the PDCCH where the first beam is located, indicating that the transport block for this scheduling is divided into two data segments (for example, the first data segment and the second data segment), which are respectively transmitted on the first carrier corresponding to the first beam and the second carrier corresponding to the second beam. After the terminal 100 completely receives the DCI sent by the satellite 200, it determines the starting time T_start, calculates the timing offset T_offset2 of the second carrier, and compares the timing offset T_offset2 of the second carrier with the timing offset T_offset1 of the first carrier. Assuming T_offset1 < T_offset2, the terminal 100 determines the above-mentioned first time T_1 = T_start + T0 + T_offset1, where T0 is the scheduling delay indicated in the DCI. Then, assuming that the cumulative duration of transmitting (for example, including the first transmission and retransmission) the first data segment is T2, the terminal 100 can determine the above-mentioned second time T_2 = T_start + T0 + T_offset2 + T1 + T2, where T1 is the carrier switching delay.

[0221] Step 305, the terminal 100 sends data to the satellite 200 based on the above data transmission time.

[0222] Specifically, the terminal 100 can use the first carrier to send the first data segment to the satellite 200 based on the above-mentioned first time, and can retransmit the first data segment based on the preset number of retransmissions. Then, after the retransmission of the first data segment is completed, the terminal 100 can use the second carrier to send the second data segment to the satellite 200 based on the above-mentioned second time, and can retransmit the second data segment based on the preset number of retransmissions.

[0223] It should be noted that the above embodiments only exemplarily show the scenario where the transport block is divided into two parts, and do not constitute a limitation on the embodiments of the present application. In some embodiments, the transport block can also be divided into more blocks.

[0224] In the embodiments of the present application, the network side instructs the terminal side to divide the transport block into two parts and transmit them on two carriers respectively. When transmitting each part of the above-mentioned transport block, there are corresponding different transmission delays, thereby enabling time synchronization between the network side and the terminal side and making full use of cross-carrier applications, and further improving the data transmission efficiency.

[0225] Figure 8 It is a schematic flowchart of another embodiment of the data transmission method provided by the present application, including:

[0226] Step 401: Satellite 200 sends timing offset configuration information.

[0227] Specifically, the satellite 200 may send the timing offset configuration information by broadcasting. Exemplarily, the satellite 200 may broadcast a system broadcast message (e.g., SIB) via the NPBCH, and the SIB may carry the timing offset configuration information. The timing offset configuration information may include multiple timing offsets, each of which may correspond to an uplink carrier. It is understandable that, since each uplink carrier corresponds to a beam, the timing offset of each uplink carrier may also correspond to a beam, thereby enabling different uplink carriers or beams to correspond to different timing offsets.

[0228] Optionally, the satellite 200 may also send the timing offset configuration information via RRC dedicated signaling. For example, after an RRC connection is established between the terminal 100 and the satellite 200, the satellite 200 may send RRC dedicated signaling to the terminal 100, and the RRC dedicated signaling may carry the timing offset configuration information.

[0229] In step 402, the terminal 100 receives the timing offset configuration information sent by the satellite 200 and stores it.

[0230] In step 403, the satellite 200 sends scheduling information to the terminal 100 via the first beam, instructing the terminal 100 to transmit multiple transport blocks on two beams.

[0231] Specifically, to improve beam utilization efficiency, satellite 200 may transmit multiple transport blocks scheduled this time on two beams (e.g., on the first beam and the second beam). In a specific implementation, satellite 200 may send scheduling information to terminal 100. This scheduling information may be carried via a DCI or RAR Grant. This scheduling information may include a scheduling delay, the ID of the second carrier, and transport block identification information, which indicates the correspondence between transport blocks and uplink carriers. Table 4 is an example table of transport block identification information.

[0232] Table 4

[0233] Carrier ID Transport Block Set Uplink carrier 1 Transport block 1, transport block 3, transport block 5 Uplink carrier 2 Transport block 2, transport block 4 … …

[0234] As shown in Table 4, transport block 1, transport block 3, and transport block 5 may constitute a transport block set, which may correspond to uplink carrier 1. That is, terminal 100 may transmit transport block 1, transport block 3, and transport block 5 on uplink carrier 1. Transport block 2 and transport block 4 may constitute another transport block set, which may correspond to uplink carrier 2. That is, terminal 100 may transmit transport block 2 and transport block 4 on uplink carrier 2.

[0235] It will be appreciated that Table 4 above only illustrates a scenario with five transport blocks and does not limit the embodiments of the present application. In some embodiments, the terminal 100 may transmit more or fewer transport blocks based on the scheduling of the satellite 200. For example, each transport block set may include one or more transport blocks.

[0236] In step 404, the terminal 100 receives the scheduling information sent by the satellite 200 and determines the data transmission time based on the scheduling information.

[0237] Specifically, because satellite 200 transmits the DCI or RAR Grant via the first beam, terminal 100 can receive the DCI or RAR Grant via the first carrier based on the mapping relationship between the uplink carrier and the beam. Upon receiving the DCI or RAR Grant transmitted by satellite 200, terminal 100 can obtain the scheduling information (e.g., scheduling delay, second carrier ID, and transport block identification information) contained in the DCI or RAR Grant.

[0238] Then, based on the ID of the second carrier (for example, uplink carrier 2 in Table 4), the timing offset configuration information can be queried to obtain the timing offset corresponding to the second carrier (for example, T_offset2 in Table 1). After obtaining the timing offset of the second carrier, the timing offset corresponding to the first carrier (for example, uplink carrier 1 in Table 4) can also be obtained (for example, T_offset1 in Table 1), and the data transmission time of the first transmission block set (for example, the transmission block set including transmission block 1, transmission block 3 and transmission block 5 in Table 4) and the second transmission block set (for example, the transmission block set including transmission block 2 and transmission block 4 in Table 4) can be determined based on the above-mentioned scheduling delay, the timing offset of the first carrier and the timing offset of the second carrier. For example,

[0239] If T_offset1>=T_offset2, then the data transmission time of the first transport block set (for example, the transport block set including transport block 1, transport block 3, and transport block 5 in Table 4) is T_3=T_start+T0+T_offset1 (for convenience of explanation, the "data transmission time of the first transport block set" is referred to as the "third time" below), and the data transmission time of the second transport block set (for example, the transport block set including transport block 2 and transport block 4 in Table 4) is T_4=T_start+T0+T_offset1+T1+T2 (for convenience of explanation, the "data transmission time of the second transport block set" is referred to as the "fourth time" below); where T_start is the starting time, T0 is the above-mentioned scheduling delay, T1 is the carrier switching delay, and T2 is the transmission duration of the first transport block set. The transmission duration of the first transport block set can be determined by the cumulative transmission duration of all transport blocks in the above-mentioned first transport block set, and the transmission duration of each transport block is determined by the preset number of retransmissions of each transport block. For example, assuming that the first transmission block set includes transmission block 1, transmission block 3 and transmission block 5, if the transmission duration of transmission block 1 is T21, the transmission duration of transmission block 3 is T22, and the transmission duration of transmission block 5 is T23, then the transmission duration of the first transmission block set T2 = T21 + T22 + T23.

[0240] If T_offset1<=T_offset2, then the third time T_3=T_start+T0+T_offset2, and the fourth time T_4=T_start+T0+T_offset2+T1+T2.

[0241] Now combined Figure 9 To explain, such as Figure 9As shown, the satellite 200 sends DCI to the terminal 100 through the PDCCH where the first beam is located, indicating two transport block sets for this scheduling (for example, the first transport block set and the second transport block set mentioned above), which are respectively transmitted on the first carrier corresponding to the first beam and the second carrier corresponding to the second beam. After the terminal 100 completely receives the DCI sent by the satellite 200, it determines the starting time T_start, calculates the timing offset T_offset2 of the second carrier, and compares the timing offset T_offset2 of the second carrier with the timing offset T_offset1 of the first carrier. Assuming T_offset1 >= T_offset2, the terminal 100 determines the above-mentioned third time T_3 = T_start + T0 + T_offset1, where T0 is the scheduling delay indicated in the DCI. Then, assuming the cumulative duration of transmitting the first transport block set is T2, the terminal 100 can determine the above-mentioned fourth time T_4 = T_start + T0 + T_offset1 + T1 + T2, where T1 is the carrier switching delay.

[0242] Optionally, if T_offset1 <= T_offset2, the third time T_3 = T_start + T0 + T_offset1, and the fourth time T_4 = T_start + T0 + T_offset2 + T1 + T2.

[0243] Now in combination with Figure 10 for illustration, as Figure 10 shown, the satellite 200 sends DCI to the terminal 100 through the PDCCH where the first beam is located, indicating two transport block sets (for example, the first transport block and the second transport block) for this scheduling, which are respectively transmitted on the first carrier corresponding to the first beam and the second carrier corresponding to the second beam. After the terminal 100 completely receives the DCI sent by the satellite 200, it determines the starting time T_start, calculates the timing offset T_offset2 of the second carrier, and compares the timing offset T_offset2 of the second carrier with the timing offset T_offset1 of the first carrier. Assuming T_offset1 < T_offset2, the terminal 100 determines the above-mentioned third time T_3 = T_start + T0 + T_offset1, where T0 is the scheduling delay indicated in the DCI. Then, assuming the cumulative duration of transmitting the first transport block set is T2, the terminal 100 can determine the above-mentioned fourth time T_4 = T_start + T0 + T_offset2 + T1 + T2, where T1 is the carrier switching delay.

[0244] Step 405, the terminal 100 sends data to the satellite 200 based on the above data transmission time.

[0245] Specifically, terminal 100 may use the first carrier to send a first transport block set to satellite 200 based on the third time instant. Then, after all transport blocks in the first transport block set are transmitted, terminal 100 may use the second carrier to send a second transport block set to satellite 200 based on the fourth time instant.

[0246] In an embodiment of the present application, the network side instructs the terminal side to transmit two transmission block sets on two carriers respectively, and a different transmission delay corresponds to the transmission of each transmission block set. This can achieve time synchronization between the network side and the terminal side, and can fully utilize cross-carrier applications, thereby improving data transmission efficiency.

[0247] Figure 11 A schematic diagram of the structure of the chip provided in the embodiment of the present application is shown in FIG. Figure 11 As shown, the chip 1100 may include: a first receiving module 1110, a second receiving module 1120 and a transmission module 1130; wherein,

[0248] The first receiving module 1110 is configured to receive and store the first information sent by the network side;

[0249] A second receiving module 1120 is configured to receive second information sent by the network side, and determine a data transmission time based on the first information and the second information;

[0250] The transmission module 1130 is configured to transmit data to the network side based on the data transmission time.

[0251] In one possible implementation manner, the first information is sent by the network side through SIB or RRC dedicated signaling.

[0252] In one possible implementation manner, the second information is sent by the network side through DCI or RAR Grant.

[0253] In one possible implementation, the second receiving module 1120 is further configured to obtain a carrier switching delay; and determine a data transmission time based on the carrier switching delay, the first information, and the second information.

[0254] In one possible implementation, the first information includes timing offsets of multiple uplink carriers, and the second information is sent by the network side using a first beam, where the first beam corresponds to a first uplink carrier.

[0255] In one possible implementation, the second information includes index information of the second uplink carrier, and the second receiving module 1120 includes: a query unit 1121 and a determination unit 1122; wherein,

[0256] A query unit 1121 is configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0257] The determining unit 1122 is configured to determine a data transmission time based on the timing offset of the second uplink carrier.

[0258] In one possible implementation, the second information includes index information of the second uplink carrier, and the second receiving module 1120 includes: an acquiring unit 1123, a querying unit 1124, and a determining unit 1125; wherein,

[0259] An acquiring unit 1123 is configured to acquire a timing offset of the first uplink carrier;

[0260] A query unit 1124 is configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0261] Determination unit 1125 is used to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier. If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the first uplink carrier. If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the second uplink carrier.

[0262] In one possible implementation, the first information includes a timing offset set of multiple uplink carriers, and the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier, wherein the timing offset set of each uplink carrier includes multiple timing offsets.

[0263] In one possible implementation, the second information includes index information of the second uplink carrier and a timing offset index identifier, and the second receiving module 1120 includes: a first query unit 1126, a second query unit 1127, and a determination unit 1128; wherein,

[0264] A first query unit 1126 is configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset set of the second uplink carrier;

[0265] A second query unit 1127 is configured to query the timing offset set of the second uplink carrier based on the timing offset index identifier to obtain the timing offset of the second uplink carrier corresponding to the timing offset index identifier;

[0266] The determining unit 1128 is configured to determine a data transmission time based on the timing offset of the second uplink carrier.

[0267] In one possible implementation, the transmission module 1130 is further configured to transmit data to the network side using the second uplink carrier based on the data transmission time.

[0268] In one possible implementation, the data includes a transport block, the second information includes index information of a second uplink carrier and data segmentation information, the data segmentation information is used to characterize the segmentation of the transport block to obtain a first data segment, a second data segment, and a mapping relationship between the data segment and the uplink carrier, the second receiving module 1120 includes: an acquisition unit 1129, a query unit 112A, and a determination unit 112B; wherein,

[0269] An acquiring unit 1129 is configured to acquire a timing offset of the first uplink carrier;

[0270] A query unit 112A, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0271] a determining unit 112B, configured to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier;

[0272] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first data segment based on the timing offset of the first uplink carrier, and determining the data transmission time of the second data segment based on the timing offset of the first uplink carrier and the transmission duration of the first data segment;

[0273] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time of the first data segment is determined based on the timing offset of the second uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; or the data transmission time of the first data segment is determined based on the timing offset of the first uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment;

[0274] The transmission duration of the first data segment is determined by the preset number of retransmissions of the first data segment.

[0275] In one possible implementation, the first data segment corresponds to the first uplink carrier, and the second data segment corresponds to the second uplink carrier. The transmission module is further used to transmit the first data segment to the network side using the first uplink carrier based on the data transmission time of the first data segment; and transmit the second data segment to the network side using the second uplink carrier based on the data transmission time of the second data segment.

[0276] In one possible implementation, the data includes a first transport block set and a second transport block set, the first transport block set and the second transport block set respectively include one or more transport blocks, the second information includes index information of the second uplink carrier and transport block identification information, the transport block identification information is used to characterize the mapping relationship between the transport block and the uplink carrier, and the second receiving module 1120 includes: an acquisition unit 112C, a query unit 112D, and a determination unit 112E; wherein,

[0277] an acquiring unit 112C, configured to acquire a timing offset of the first uplink carrier;

[0278] a query unit 112D, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier;

[0279] a determining unit 112E, configured to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier;

[0280] If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the first uplink carrier and the transmission duration of the first transport block set;

[0281] If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the second uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; or determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set;

[0282] The transmission duration of the first transmission block set is determined by the accumulated transmission duration of all transmission blocks in the first transmission block set, and the transmission duration of each transmission block is determined by the preset number of retransmissions of each transmission block.

[0283] In one possible implementation, the first transmission block set corresponds to the first uplink carrier, and the second transmission block set corresponds to the second uplink carrier. The transmission module 1130 is further used to transmit the first transmission block set to the network side using the first uplink carrier based on the data transmission time of the first transmission block set; and transmit the second transmission block set to the network side using the second uplink carrier based on the data transmission time of the second transmission block set.

[0284] It should be understood that Figure 11 The division of the various modules of the chip shown is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into a single physical entity or physically separated. Furthermore, these modules can be implemented entirely as software invoked through processing elements, or entirely as hardware. Alternatively, some modules can be implemented as software invoked through processing elements, while others can be implemented as hardware. Furthermore, these modules can be fully or partially integrated or implemented independently. During implementation, each step of the above method or each of the above modules can be performed by hardware integrated logic circuits in the processor element or by software instructions.

[0285] For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs). For another example, these modules may be integrated together to implement a system-on-a-chip (SOC).

[0286] Figure 12 The schematic structural diagram of the terminal 100 is shown as an example.

[0287] The terminal 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0288] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the terminal 100. In other embodiments of the present application, the terminal 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0289] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0290] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0291] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0292] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0293] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C busses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, and the like via different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K via the I2C interface, enabling communication between the processor 110 and the touch sensor 180K via the I2C bus interface, thereby implementing the touch function of the terminal 100.

[0294] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface, enabling the function of answering calls through a Bluetooth headset.

[0295] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0296] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface, enabling the function of playing music through Bluetooth headphones.

[0297] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display 194 and the camera 193. MIPI interfaces include the camera serial interface (CSI) and the display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the camera function of the terminal 100. The processor 110 and the display 194 communicate via the DSI interface to implement the display function of the terminal 100.

[0298] The GPIO interface can be configured via software. The GPIO interface can be configured as either a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to the camera 193, display 194, wireless communication module 160, audio module 170, sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0299] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the terminal 100, or to transfer data between the terminal 100 and peripheral devices. It can also be used to connect headphones to play audio. This interface can also be used to connect other electronic devices, such as AR devices.

[0300] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative description and does not constitute a structural limitation on the terminal 100. In other embodiments of the present application, the terminal 100 may also adopt a different interface connection method from the above embodiment, or a combination of multiple interface connection methods.

[0301] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the terminal 100. While charging the battery 142, the charging management module 140 can also power the electronic device via the power management module 141.

[0302] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0303] The wireless communication function of the terminal 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0304] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0305] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied on the terminal 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0306] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0307] The wireless communication module 160 can provide wireless communication solutions applied on the terminal 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0308] In some embodiments, antenna 1 of terminal 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that terminal 100 can communicate with a network and other devices via wireless communication technologies. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0309] Terminal 100 implements display functions through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0310] Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-oLed, or a quantum dot light-emitting diode (QLED). In some embodiments, terminal 100 may include one or N display screens 194, where N is a positive integer greater than one.

[0311] The terminal 100 can realize the shooting function through the ISP, camera 193, video codec, GPU, display screen 194 and application processor.

[0312] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and transformed into a visible image. The ISP can also perform algorithmic optimization for image noise, brightness, and skin tone. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0313] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the terminal 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0314] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the terminal 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0315] Video codecs are used to compress or decompress digital video. Terminal 100 may support one or more video codecs. This allows terminal 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0316] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU enables intelligent cognitive applications in the terminal 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0317] The external memory interface 120 can be used to connect an external memory card, such as a MicroSD card, to expand the storage capacity of the terminal 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0318] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the terminal 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the terminal 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor.

[0319] The terminal 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0320] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0321] The speaker 170A, also called a "horn", is used to convert an audio electrical signal into a sound signal. The terminal 100 can listen to music or listen to a hands-free call through the speaker 170A.

[0322] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the terminal 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to hear the voice.

[0323] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The terminal 100 can be provided with at least one microphone 170C. In other embodiments, the terminal 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the terminal 100 can also be provided with three, four or more microphones 170C to realize sound signal collection, noise reduction, and identification of sound sources, and realize directional recording function, etc.

[0324] The headphone jack 170D is used to connect a wired headphone and can be a USB interface 130 or a 3.5mm open mobile terminal platform (OMTP) standard interface or a cellular telecommunications industry association of the USA (CTIA) standard interface.

[0325] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be located on display screen 194. There are many types of pressure sensors 180A, such as resistive, inductive, and capacitive. A capacitive pressure sensor can include at least two parallel plates made of conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Terminal 100 determines the intensity of the pressure based on this change in capacitance. When a touch operation is applied to display screen 194, terminal 100 detects the touch intensity based on pressure sensor 180A. Terminal 100 can also calculate the touch location based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch location but with different touch intensities can correspond to different operation instructions. For example, when a touch operation with an intensity less than a first pressure threshold is applied to a short message application icon, a command to view short messages is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to a short message application icon, a command to create a new short message is executed.

[0326] The gyroscope sensor 180B can be used to determine the motion posture of the terminal 100. In some embodiments, the angular velocity of the terminal 100 around three axes (i.e., x, y, and z axes) can be determined by the gyroscope sensor 180B. The gyroscope sensor 180B can be used for anti-shake shooting. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the terminal 100 shaking, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to offset the shaking of the terminal 100 through reverse movement to achieve anti-shake. The gyroscope sensor 180B can also be used for navigation and somatosensory game scenes.

[0327] The air pressure sensor 180C is used to measure air pressure. In some embodiments, the terminal 100 calculates the altitude using the air pressure value measured by the air pressure sensor 180C to assist in positioning and navigation.

[0328] The magnetic sensor 180D includes a Hall sensor. The terminal 100 can use the magnetic sensor 180D to detect the opening and closing of the flip case. In some embodiments, when the terminal 100 is a flip phone, the terminal 100 can detect the opening and closing of the flip cover based on the magnetic sensor 180D. Furthermore, based on the detected opening and closing status of the case or flip cover, features such as automatic unlocking of the flip cover can be configured.

[0329] Accelerometer 180E can detect the magnitude of acceleration of terminal 100 in all directions (generally three axes). When terminal 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the electronic device's posture, enabling applications such as switching between landscape and portrait modes and pedometers.

[0330] The distance sensor 180F is used to measure distance. The terminal 100 can measure distance using infrared or laser. In some embodiments, when shooting a scene, the terminal 100 can use the distance sensor 180F to measure distance to achieve fast focusing.

[0331] The proximity light sensor 180G may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal 100 emits infrared light outward through the light emitting diode. The terminal 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the terminal 100. When insufficient reflected light is detected, the terminal 100 can determine that there is no object near the terminal 100. The terminal 100 can use the proximity light sensor 180G to detect when the user holds the terminal 100 close to the ear to talk, so as to automatically turn off the screen to save power. The proximity light sensor 180G can also be used in leather case mode and pocket mode to automatically unlock and lock the screen.

[0332] Ambient light sensor 180L is used to sense ambient light brightness. Terminal 100 can adaptively adjust the brightness of display screen 194 based on the perceived ambient light brightness. Ambient light sensor 180L can also be used to automatically adjust white balance when taking photos. Ambient light sensor 180L can also work with proximity light sensor 180G to detect whether terminal 100 is in a pocket to prevent accidental touches.

[0333] The fingerprint sensor 180H is used to collect fingerprints. The terminal 100 can use the collected fingerprint characteristics to implement fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0334] Temperature sensor 180J is used to detect temperature. In some embodiments, terminal 100 uses the temperature detected by temperature sensor 180J to implement a temperature handling strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, terminal 100 reduces the performance of a processor located near temperature sensor 180J to reduce power consumption and implement thermal protection. In other embodiments, when the temperature falls below another threshold, terminal 100 heats battery 142 to prevent abnormal shutdown of terminal 100 due to low temperature. In other embodiments, when the temperature falls below yet another threshold, terminal 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.

[0335] The touch sensor 180K is also referred to as a "touch-sensitive device." The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also referred to as a "touch screen." The touch sensor 180K is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to the application processor to determine the type of touch event. Visual output related to the touch operations can be provided via the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the terminal 100, at a location different from that of the display screen 194.

[0336] The bone conduction sensor 180M can obtain vibration signals. In some embodiments, the bone conduction sensor 180M can obtain vibration signals from the vibrating bones of the human body. The bone conduction sensor 180M can also contact the human pulse to receive blood pressure pulse signals. In some embodiments, the bone conduction sensor 180M can also be set in headphones to form bone conduction headphones. The audio module 170 can parse out voice signals based on the vibration signals of the vibrating bones of the human body obtained by the bone conduction sensor 180M to implement voice functions. The application processor can parse heart rate information based on the blood pressure pulse signals obtained by the bone conduction sensor 180M to implement heart rate detection functions.

[0337] Keys 190 include a power button, a volume button, etc. Keys 190 may be mechanical keys or touch keys. Terminal 100 may receive key inputs and generate key signal inputs related to user settings and function control of terminal 100.

[0338] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0339] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0340] The SIM card interface 195 is used to connect a SIM card. A SIM card can be connected to and disconnected from the terminal 100 by inserting or removing it from the SIM card interface 195. The terminal 100 can support one or N SIM card interfaces, where N is a positive integer greater than one. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The terminal 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the terminal 100 uses an eSIM, or embedded SIM card. The eSIM card can be embedded in the terminal 100 and cannot be separated from the terminal 100.

[0341] It is understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is merely illustrative and does not constitute a structural limitation on the terminal 100. In other embodiments of the present application, the terminal 100 may also adopt different interface connection methods from the above embodiments, or a combination of multiple interface connection methods.

[0342] It is understandable that, in order to implement the above functions, the terminal 100 includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

[0343] The embodiment of the present application can divide the functional modules of the above-mentioned mobile terminal etc. according to the above-mentioned method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0344] Through the description of the above embodiments, those skilled in the art will clearly understand that for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working processes of the above-described systems, devices, and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0345] The functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0346] If the integrated unit 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 embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform 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 flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk.

[0347] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions 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: The method comprises: receiving and storing first information sent by a network side, where the first information includes timing offsets of multiple uplink carriers, where the timing offsets of the multiple uplink carriers are determined by transmission delays; receiving second information sent by the network side, and determining a data transmission time based on the first information and the second information, where the second information is sent by the network side using a first beam, where the first beam corresponds to a first uplink carrier, and the first uplink carrier is one of the multiple uplink carriers; transmitting data to the network side based on the data transmission time; The second information includes index information of a second uplink carrier, the second uplink carrier is one of the multiple uplink carriers, and the second uplink carrier is a different carrier from the first uplink carrier. The determining the data transmission time based on the first information and the second information includes: If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the first uplink carrier; if the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the second uplink carrier.

2. The method according to claim 1, characterized in that The first information is sent by the network side through SIB or RRC dedicated signaling.

3. The method according to claim 1 or 2, characterized in that The second information is sent by the network side through DCI or RAR Grant.

4. The method according to claim 1, wherein The determining of the data transmission time based on the first information and the second information includes: Get carrier switching delay; A data transmission time is determined based on the carrier switching delay, the first information, and the second information.

5. The method according to claim 1, wherein The transmitting data to the network side based on the data transmission time includes: Based on the data transmission time, data is transmitted to the network side using the second uplink carrier.

6. A data transmission method, characterized in that: The method comprises: receiving and storing first information sent by a network side, where the first information includes timing offsets of multiple uplink carriers, where the timing offsets of the multiple uplink carriers are determined by transmission delays; receiving second information sent by the network side, and determining a data transmission time based on the first information and the second information, where the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier; transmitting data to the network side based on the data transmission time; The data includes a transport block, the second information includes index information of a second uplink carrier and data segmentation information, the data segmentation information is used to represent segmentation of the transport block to obtain a first data segment, a second data segment, and a mapping relationship between the data segments and the uplink carrier, and determining the data transmission time based on the first information and the second information includes: Obtaining a timing offset of the first uplink carrier; querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier; comparing a timing offset of the first uplink carrier with a timing offset of the second uplink carrier; If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first data segment based on the timing offset of the first uplink carrier, and determining the data transmission time of the second data segment based on the timing offset of the first uplink carrier and the transmission duration of the first data segment; If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time of the first data segment is determined based on the timing offset of the second uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; or the data transmission time of the first data segment is determined based on the timing offset of the first uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; The transmission duration of the first data segment is determined by the preset number of retransmissions of the first data segment.

7. The method according to claim 6, characterized in that The first data segment corresponds to the first uplink carrier, the second data segment corresponds to the second uplink carrier, and the transmitting data to the network side based on the data transmission time includes: Transmitting the first data segment to the network side using the first uplink carrier based on a data transmission time of the first data segment; Based on the data transmission time of the second data segment, the second data segment is transmitted to the network side using the second uplink carrier.

8. A data transmission method, characterized in that: The method comprises: receiving and storing first information sent by a network side, where the first information includes timing offsets of multiple uplink carriers, where the timing offsets of the multiple uplink carriers are determined by transmission delays; receiving second information sent by the network side, and determining a data transmission time based on the first information and the second information, where the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier; transmitting data to the network side based on the data transmission time; The data includes a first transport block set and a second transport block set, the first transport block set and the second transport block set each including one or more transport blocks, the second information includes index information of a second uplink carrier and transport block identification information, the transport block identification information being used to characterize a mapping relationship between a transport block and an uplink carrier, and determining a data transmission time based on the first information and the second information includes: Obtaining a timing offset of the first uplink carrier; querying the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier; comparing a timing offset of the first uplink carrier with a timing offset of the second uplink carrier; If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the first uplink carrier and the transmission duration of the first transport block set; If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the second uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; or determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; The transmission duration of the first transmission block set is determined by the accumulated transmission duration of all transmission blocks in the first transmission block set, and the transmission duration of each transmission block is determined by the preset number of retransmissions of each transmission block.

9. The method according to claim 8, characterized in that The first transmission block set corresponds to the first uplink carrier, the second transmission block set corresponds to the second uplink carrier, and the transmitting data to the network side based on the data transmission time includes: transmitting the first transport block set to the network side using the first uplink carrier based on a data transmission time instant of the first transport block set; Based on the data transmission time of the second transmission block set, the second transmission block set is transmitted to the network side by using the second uplink carrier.

10. A chip, characterized in that: include: a first receiving module, configured to receive and store first information sent by a network side, where the first information includes timing offsets of multiple uplink carriers, where the timing offsets of the multiple uplink carriers are determined by transmission delays; a second receiving module, configured to receive second information sent by the network side, and determine a data transmission time based on the first information and the second information, wherein the second information is sent by the network side using a first beam, the first beam corresponds to a first uplink carrier, and the second information includes index information of a second uplink carrier; A transmission module, configured to transmit data to the network side based on the data transmission time; The second receiving module includes: an acquiring unit, configured to acquire a timing offset of the first uplink carrier; a query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier; A determination unit is used to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier. If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the first uplink carrier; if the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time is determined based on the timing offset of the second uplink carrier.

11. The chip according to claim 10, characterized in that The first information is sent by the network side through SIB or RRC dedicated signaling.

12. The chip according to claim 10 or 11, characterized in that The second information is sent by the network side through DCI or RAR Grant.

13. The chip according to claim 10, characterized in that The second receiving module is further configured to obtain a carrier switching delay; and determine a data transmission time based on the carrier switching delay, the first information, and the second information.

14. The chip according to claim 10, characterized in that The transmission module is further configured to transmit data to the network side using the second uplink carrier based on the data transmission time.

15. A chip, characterized in that: include: a first receiving module, configured to receive and store first information sent by a network side, where the first information includes timing offsets of multiple uplink carriers, where the timing offsets of the multiple uplink carriers are determined by transmission delays; a second receiving module, configured to receive second information sent by the network side, and determine a data transmission time based on the first information and the second information, where the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier; a transmission module, configured to transmit data to the network side based on the data transmission time, the data including a transport block, the second information including index information of a second uplink carrier and data segmentation information, the data segmentation information being used to indicate segmentation of the transport block to obtain a first data segment, a second data segment, and a mapping relationship between the data segments and the uplink carrier; The second receiving module includes: an acquiring unit, configured to acquire a timing offset of the first uplink carrier; a query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier; a determining unit, configured to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier; If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first data segment based on the timing offset of the first uplink carrier, and determining the data transmission time of the second data segment based on the timing offset of the first uplink carrier and the transmission duration of the first data segment; If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, the data transmission time of the first data segment is determined based on the timing offset of the second uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; or the data transmission time of the first data segment is determined based on the timing offset of the first uplink carrier, and the data transmission time of the second data segment is determined based on the timing offset of the second uplink carrier and the transmission duration of the first data segment; The transmission duration of the first data segment is determined by the preset number of retransmissions of the first data segment.

16. The chip according to claim 15, characterized in that The first data segment corresponds to the first uplink carrier, and the second data segment corresponds to the second uplink carrier, and the transmission module is further configured to transmit the first data segment to the network side using the first uplink carrier based on a data transmission time of the first data segment; Based on the data transmission time of the second data segment, the second data segment is transmitted to the network side using the second uplink carrier.

17. A chip, characterized in that: include: a first receiving module, configured to receive and store first information sent by a network side, where the first information includes timing offsets of multiple uplink carriers, where the timing offsets of the multiple uplink carriers are determined by transmission delays; a second receiving module, configured to receive second information sent by the network side, and determine a data transmission time based on the first information and the second information, where the second information is sent by the network side using a first beam, and the first beam corresponds to a first uplink carrier; a transmission module, configured to transmit data to the network side based on the data transmission time, the data including a first transmission block set and a second transmission block set, the first transmission block set and the second transmission block set respectively including one or more transmission blocks, the second information including index information of a second uplink carrier and transmission block identification information, the transmission block identification information being used to characterize a mapping relationship between a transmission block and an uplink carrier; The second receiving module includes: an acquiring unit, configured to acquire a timing offset of the first uplink carrier; a query unit, configured to query the first information based on the index information of the second uplink carrier to obtain a timing offset of the second uplink carrier; a determining unit, configured to compare the timing offset of the first uplink carrier with the timing offset of the second uplink carrier; If the timing offset of the first uplink carrier is greater than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the first uplink carrier and the transmission duration of the first transport block set; If the timing offset of the first uplink carrier is less than or equal to the timing offset of the second uplink carrier, determining the data transmission time of the first transport block set based on the timing offset of the second uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; or determining the data transmission time of the first transport block set based on the timing offset of the first uplink carrier, and determining the data transmission time of the second transport block set based on the timing offset of the second uplink carrier and the transmission duration of the first transport block set; The transmission duration of the first transmission block set is determined by the accumulated transmission duration of all transmission blocks in the first transmission block set, and the transmission duration of each transmission block is determined by the preset number of retransmissions of each transmission block.

18. The chip according to claim 17, characterized in that The first transport block set corresponds to the first uplink carrier, and the second transport block set corresponds to the second uplink carrier, and the transmission module is further configured to transmit the first transport block set to the network side using the first uplink carrier based on a data transmission time of the first transport block set; Based on the data transmission time of the second transmission block set, the second transmission block set is transmitted to the network side by using the second uplink carrier.

19. A terminal, characterized in that: include: A memory, wherein the memory is used to store computer program code, wherein the computer program code includes instructions, and when the terminal reads the instructions from the memory, the terminal executes the method according to any one of claims 1 to 9.

20. A computer-readable storage medium, characterized in that The method comprises computer instructions, which, when executed on a terminal, cause the terminal to execute the method according to any one of claims 1 to 9.

21. A computer program product, characterized in that When the computer program product is run on a computer, the computer is caused to perform the method according to any one of claims 1 to 9.

Images