Data transmission method and device

Abstract

A data transmission method and a device. The method comprises: sending first data and first information, wherein the first data is a first part of second data, and the first information is associated with the corresponding position of the first data in the second data; receiving the first information from a second device; and sending third data, wherein the third data is a second part of the second data, and the corresponding position of the third data in the second data is determined on the basis of the first information. By means of the method, during subsequent transmission of the second data, the second device can return the first information to a first device, such that the first device can determine, on the basis of the first information, the first data transmitted last time, and thus can determine the corresponding position of the third data, that needs to be transmitted for this instance, in the first data. In this way, even if the first device loses the first information due to a power failure, etc., the transmission of the other parts of the second data can still resume on the basis of the first information of the second device, thereby improving transmission efficiency.

Description

A data transmission method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202410662232.7, filed on May 25, 2024, entitled "A Data Transmission Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a data transmission method and apparatus. Background Technology

[0004] The Internet of Things (IoT) technology has been introduced into wireless communication systems. In IoT, tags act as terminal devices, base stations act as readers, and tags can communicate with base stations. Tags are passive or semi-active devices, and typical applications include logistics, warehousing, industrial manufacturing, identification, and environmental monitoring. Before a tag can function, its capacitor needs to be charged; the capacitor must have sufficient charge for the tag to start working.

[0005] During uplink data transmission, if the data size exceeds the input limit of the media access control (MAC) layer scheduler, the data must be segmented and reassembled at the radio link control (RLC) layer. To do this, the tag needs to continuously record the serial number (SN) of the next protocol data unit (PDU) to be transmitted until data transmission is complete. This results in significant power consumption for the tag, reducing its effective operating time. If the tag's battery runs out before data transmission is complete, the tag will lose the data's serial number. This means that upon power-up, the tag cannot determine which data was not transmitted, reducing data transmission continuity and efficiency. Summary of the Invention

[0006] This application provides a data transmission method and apparatus to address the problem of improving data transmission continuity.

[0007] Firstly, this application provides a data transmission method. The execution subject of this method is a first device or a module or chip within the first device. Here, the first device is described as the execution subject, and the first device can be a terminal device or a tag. The method includes: sending first data and first information; the first data being a first part of second data, and the first information being associated with the position of the first data corresponding to the position in the second data; receiving the first information from a second device; and sending third data; the third data being a second part of the second data, and the position of the third data corresponding to the position in the second data being determined based on the first information.

[0008] Using the above method, during the subsequent transmission of the second data, the second device can return the first information to the first device. In this way, the first device can determine the first data transmitted last time based on the first information, and thus determine the position of the third data to be transmitted this time in the first data. Even if the first device loses the first information due to power failure or other reasons, it can continue to transmit other parts of the second data through the first information of the second device, thereby improving transmission efficiency and data transmission continuity.

[0009] In one possible implementation, the first information is associated with the position of the first data in the second data, including: the first information includes the index of the last byte or bit of the first data in the second data.

[0010] This method can accurately indicate the specific location of the first data within the second data, thus improving accuracy.

[0011] In one possible implementation, each M bytes or bits in the second data constitutes a data segment, where M is an integer greater than 1;

[0012] The first information is associated with the position of the first data in the second data, including: the first information includes the index of the data segment corresponding to the last byte or bit of the first data in the second data.

[0013] The overhead of the first information can be reduced by indicating the index of the data segment corresponding to the last byte or bit of the first data in the second data.

[0014] In one possible implementation, the second data includes N data segments, and the first data is a segment of the N data segments, where N is an integer greater than 1; the first information is associated with the position of the first data in the second data, including: the first information includes the index of the first data in the N data segments.

[0015] This method uses data segment granularity indicators to reduce the overhead of the first information.

[0016] In one possible implementation, the first information further indicates at least one of the following: the data size of the first data; the storage area where the second data is located; and whether the transmission of the second data has been completed.

[0017] In one possible implementation, before sending the third data, the method further includes: receiving a first identifier; and determining that the first identifier is associated with the first device.

[0018] By using the first identifier, devices not associated with the first identifier can be prevented from responding to the second device, thereby improving the accuracy of data transmission.

[0019] In one possible implementation, the size of the first data is determined based on the remaining power of the first device.

[0020] This method avoids situations where excessively large amounts of data are transmitted, leading to insufficient power to complete the data transmission and thus improving data transmission efficiency.

[0021] In one possible implementation, before receiving the first information from the second device, the method further includes: sending time information, the time information being used to determine the time for sending the third data or receiving the first information.

[0022] In one possible implementation, the method further includes: receiving first indication information from the second device, the first indication information indicating that the second data transmission is complete.

[0023] In one possible implementation, the method further includes: entering a sleep state, or temporarily not receiving or responding to downlink signaling from the second device.

[0024] In one possible implementation, the method further includes: sending second information to the second device; the second information being associated with the position of the third data within the second data.

[0025] In one possible implementation, the second information also indicates whether the second data transmission is complete.

[0026] In one possible implementation, the method further includes: sending a buffer status report to the second device, the buffer status report indicating the data size of the second data.

[0027] Secondly, this application provides a data transmission method, wherein the execution subject of the method is a second device or a module or chip in the second device. Here, the second device is used as an example for description. For example, the second device can be a network device, a terminal device, or a tag. The method includes: receiving first data and first information from a first device; the first data is a first part of the second data, and the first information is associated with the position of the first data in the second data; sending the first information to the first device; receiving third data from the first device; the third data is a second part of the second data, and the position of the third data in the second data is determined according to the first information.

[0028] In one possible implementation, the first information is associated with the position of the first data in the second data, including: the first information includes the index of the last byte or bit of the first data in the second data.

[0029] In one possible implementation, each M bytes or bits in the second data constitutes a data segment, where M is an integer greater than 1; the first information is associated with the position of the first data in the second data, including: the first information includes the index of the data segment corresponding to the last byte or bit of the first data in the second data.

[0030] In one possible implementation, the second data includes N data segments, and the first data is a segment of the N data segments, where N is an integer greater than 1; the first information is associated with the position of the first data in the second data, including: the first information includes the index of the first data in the N data segments.

[0031] In one possible implementation, the first information further indicates at least one of the following: the data size of the first data; the storage area where the second data is located; and whether the transmission of the second data has been completed.

[0032] In one possible implementation, the method further includes: sending a first identifier to the first device, the first identifier being associated with the first device.

[0033] In one possible implementation, the method further includes: the sum of the data size of the first data and the data size of the third data is greater than or equal to the data size of the second data; sending a first indication message to the first device, the first indication message indicating that the second data transmission is complete.

[0034] In one possible implementation, the method further includes: receiving a buffer status report from the first device, the buffer status report indicating the data size of the second data; or, receiving second indication information from a core network device, the second indication information indicating the data size of the second data.

[0035] In one possible implementation, the method further includes: receiving second information from a first device; the second information being associated with the position of the third data corresponding to the second data.

[0036] In one possible implementation, the second information also indicates whether the second data transmission is complete.

[0037] In one possible implementation, before sending the first information to the first device, the method further includes: receiving time information from the first device; and determining the time to send the first information based on the time information.

[0038] Thirdly, this application also provides a communication device capable of implementing any of the methods provided in any of the first to second aspects described above. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the aforementioned functions.

[0039] In one possible implementation, the communication device includes a processor configured to support the communication device in performing corresponding functions of the network device, terminal device, or core network device described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and devices such as terminal devices.

[0040] In one possible implementation, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0041] In one possible implementation, the communication device includes a processing unit and a communication unit, which can perform the corresponding functions described in the above method examples, as detailed in the descriptions of the methods provided in any of the first to second aspects, which will not be repeated here. Fourthly, a communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor implements the functional modules of the methods in any possible implementation of any of the first to second aspects through logic circuits or by executing computer programs or instructions. Optionally, the communication device further includes a memory for storing computer programs or instructions.

[0042] Fifthly, a computer-readable storage medium is provided that stores a computer program or instructions that, when executed by a processor or when the computer program or instructions are run on a computer, implement the method in any possible implementation of any of the first to second aspects described above.

[0043] In a sixth aspect, a computer program product is provided, which, when read and executed by a computer, implements the method in any possible implementation of any of the first to second aspects described above.

[0044] In a seventh aspect, a circuit is provided for performing the methods in any possible implementation of any of the first to second aspects described above. The circuit may include chip circuitry. Optionally, the circuit may also be coupled to a memory.

[0045] Eighthly, a chip is provided, comprising a processor, which, when executing a computer program or instructions, implements the methods in any possible implementation of any of the first to second aspects. Optionally, the chip may further include a memory, which may be composed of chips or may include chips and other discrete devices. The memory is used to store computer programs or instructions.

[0046] A ninth aspect provides a communication device including a processor that implements the methods in any possible implementation of any of the first to sixth aspects by means of logic circuits or by executing computer programs or instructions. Alternatively, the processor is configured to execute computer programs or instructions stored in a memory to implement the methods in any possible implementation of any of the first to sixth aspects.

[0047] In a tenth aspect, a communication apparatus is provided, comprising a unit or module for performing a method in any possible implementation of any of the first to second aspects described above.

[0048] Eleventhly, embodiments of this application also provide a communication system. The communication system includes: a first apparatus for implementing the method in the first aspect and any possible implementation thereof; and a second apparatus for implementing the method in the second aspect and any possible implementation thereof. Attached Figure Description

[0049] Figure 1A is a schematic diagram of a network device architecture provided in an embodiment of this application;

[0050] Figure 1B is a schematic diagram of a communication system applicable to an embodiment of this application;

[0051] Figure 2 is a schematic diagram of a communication system applicable to an embodiment of this application;

[0052] Figure 3 is a schematic diagram of another communication system applicable to an embodiment of this application;

[0053] Figure 4 is a schematic diagram of another communication system applicable to embodiments of this application;

[0054] Figure 5 is a schematic diagram of another communication system applicable to the embodiments of this application;

[0055] Figure 6 is a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0056] Figure 7 is a schematic diagram of the positional relationship between first data and second data provided in an embodiment of this application;

[0057] Figure 8 is a schematic diagram of the positional relationship between first data and second data provided in an embodiment of this application;

[0058] Figure 9 is a schematic flowchart of a data transmission method provided in an embodiment of this application;

[0059] Figure 10 is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0060] Figure 11 is a schematic diagram of a communication device structure provided in an embodiment of this application;

[0061] Figure 12 is a schematic diagram of a communication device structure provided in an embodiment of this application. Detailed Implementation

[0062] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. The terms "first," "second," and corresponding terminology in this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be interchanged where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or device that comprises a series of units is not necessarily limited to those units, but may include other units not explicitly listed or inherent to these processes, methods, products, or devices. The methods and apparatus provided in the embodiments of this application are based on the same or similar technical concepts. Since the principles by which the methods and apparatus solve problems are similar, the implementations of the apparatus and methods can refer to each other, and repeated details will not be repeated.

[0063] The methods provided in this application can be applied to various mobile communication systems, such as the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), fourth-generation (4G) communication systems (e.g., Long Term Evolution, LTE), fifth-generation (5G) communication systems (e.g., 5G New Radio, NR), hybrid LTE and NR architectures, and new communication systems emerging in future communication developments. The communication system can also include machine-to-machine (M2M) networks, machine-type communication (MTC), or other networks. For example, the methods and apparatus provided in this application can be applied to communication systems that support ambient IoT (AIoT) or Internet of Things (IoT) technologies.

[0064] The following section will first explain some of the terms used in the embodiments of this application so that those skilled in the art can understand them.

[0065] In this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone.

[0066] In this embodiment, the network device can be a device in a wireless network, and can also be called a network apparatus or a wireless access network device. For example, the network device can be a radio access network (RAN) node that connects a terminal device to a wireless network, and can also be called an access network device. The network device includes, but is not limited to: base station, evolved NodeB (eNodeB), transmission reception point (TRP), next-generation NodeB (gNB) in a 5th generation (5G) mobile communication system, access network device in an open radio access network (O-RAN), next-generation base station in a 6th generation (6G) mobile communication system, base station in a future mobile communication system, or access node in a wireless fidelity (WiFi) system; or it can be a module or unit that performs part of the functions of a base station, such as a central unit (CU), a distributed unit (DU), a central unit control plane (CU-CP) module, or a central unit user plane (CU-UP) module. Network equipment can be macro base stations, micro base stations, indoor stations, relay nodes, or donor nodes, etc. This application does not limit the specific technology or form of the network equipment.

[0067] In some implementations, network devices can include centralized units (CUs) and distributed units (DUs). This includes RAN devices at CU and DU nodes that separate the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed across the DUs, which are then centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP handles control plane functions, primarily including radio resource control (RRC) and the corresponding packet data convergence protocol (PDCP) (i.e., control plane part of PDCP, PDCP-C). The CU-UP handles user plane functions, primarily including the service data adaptation protocol (SDAP) and the corresponding user plane PDCP (i.e., user plane part of PDCP, PDCP-U). The CU-CP and CU-UP are connected via an E1 interface. CU-CP represents the gNB connecting to the core network via the next-generation (NG) interface and to the DU via the F1 interface control plane (i.e., F1-C). CU-UP connects to the DU via the F1 interface user plane (i.e., F1-U). Another possible implementation is that PDCP-C is also located in CU-UP.

[0068] It is understood that CU (including CU-CP or CU-UP) or DU may have different names in different systems, but those skilled in the art will understand their meaning. For example, in an open radio access network (O-RAN or ORAN) system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called O-CU-CP, and CU-UP can also be called O-CU-UP. For ease of description, this application uses CU, CU-CP, CU-UP, and DU as examples. Network devices may also include active antenna units (AAUs). CU implements some of the functions of the gNB, and DU implements some of the functions of the gNB. For example, CU is responsible for handling non-real-time protocols and services, implementing the functions of the RRC layer. DU is responsible for handling physical layer protocols and real-time services, implementing the functions of the radio link control (RLC) layer, media access control (MAC) layer, and physical (PHY) layer. In some deployments, the CU can also be divided into a centralized unit control plane (CU-CP) node and a centralized unit user plane (CU-UP) node. The CU-CP is responsible for control plane functions, while the CU-UP is responsible for user plane functions.

[0069] The terminal device involved in the embodiments of this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The terminal device can be referred to as a terminal device, or it can also be called user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), etc. The terminal device can be a device that includes wireless communication functions (providing voice / data connectivity to the user). For example, a handheld device with wireless connectivity, or an in-vehicle device, in-vehicle module, etc. Currently, examples of terminal devices include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in vehicle-to-everything (V2X) communication, wireless terminals in vehicle-to-everything (V2X) communication, intelligent vehicles, in-vehicle infotainment systems (or onboard transmitters) (T-boxes), machine-to-machine / machine-type communications (M2M / MTC) terminal devices, and the Internet of Things (IoT). IoT (Internet of Things) terminal devices, etc. For example, terminal devices can be in-vehicle equipment, vehicle equipment, in-vehicle modules, vehicles, on-board units (OBU), roadside units (RSU), T-boxes, chips or systems on chips (SOC), etc. The aforementioned chips or SOCs can be installed in vehicles, OBUs, RSUs or T-boxes.Terminal devices can also be V2X devices, such as smart cars, digital cars, unmanned cars, driverless cars, pilotless cars, autonomous cars, pure electric vehicles (EVs), hybrid electric vehicles (HEVs), range-extended electric vehicles (REEVs), plug-in hybrid electric vehicles (PHEVs), new energy vehicles, and roadside units (RSUs). Terminal devices can also be devices used in device-to-device (D2D) communication, such as electricity meters and water meters.

[0070] Furthermore, in this embodiment, the terminal device can also be an ambient internet of things (A-IoT) device. A-IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. The A-IoT terminal device can be implemented by a terminal in a cellular network, such as an extremely low-power, extremely low-complexity IoT terminal. Non-contact data communication can be performed between the network device and the A-IoT terminal device, thereby reading information from the A-IoT terminal device and / or writing information that needs to be stored into the A-IoT terminal device.

[0071] An RFID system, composed of network devices (which can be viewed as readers in radio frequency identification (RFID) technology) and passive / semi-passive / active A-IoT terminal devices, can perform tasks such as inventory management, positioning, sensing, and command execution. Typical application scenarios include logistics, warehousing, industrial manufacturing, identification, and environmental monitoring. For example, passive A-IoT terminal devices can also be referred to as passive Internet of Things (IoT) devices.

[0072] Terminal devices can include passive terminal devices, semi-passive terminal devices, and active terminal devices. Passive terminal devices require an excitation signal from the network device; some energy is used for internal processing such as encoding / decoding and modulation / demodulation. This excitation signal can also serve as a carrier wave for reflecting uplink information from the terminal device. Semi-passive terminal devices contain a battery, and internal processing such as encoding / decoding and modulation / demodulation can be performed using the battery, but they still require the network device to send an excitation signal as a reflected carrier. Active terminal devices contain a battery and perform encoding / decoding and modulation / demodulation. Active terminal devices include a radio transmitter and can actively send data to other devices.

[0073] In one implementation, terminal devices in A-IoT can be divided into three categories:

[0074] Device A, similar to a passive A-IoT terminal: has no energy storage, cannot generate signals independently, and uses backscattering to transmit signals;

[0075] Device B, similar to a semi-passive A-IoT terminal: has energy storage, but cannot generate signals independently. It uses backscatter to transmit signals, and its stored energy can amplify the reflected signals.

[0076] Device C, similar to an active A-IoT terminal, has energy storage, can generate signals independently, and has active radio frequency components for transmission.

[0077] In addition, the network devices involved in the embodiments of this application may be referred to as readers (or readers-writers), radio access network (RAN) devices, open radio access network (O-RAN) devices or any component node in O-RAN, a node B (gNB) that continues to evolve from a transmission reception point, a transmission reception point (TRP), an evolved node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a base band unit (BBU), or a wireless fidelity (Wi-Fi) access point (AP), etc.

[0078] Figure 1A illustrates an exemplary structural diagram of a network device according to an embodiment of this application. As shown in Figure 1A, the network device 100 can be a RAN device including centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN devices including both CU and DU nodes. In RAN devices including CU and DU nodes, the protocol layers of the eNB in ​​a long term evolution (LTE) system are separated. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0079] In some examples, the CU is a logical node that carries the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which can be interfaces such as E2 interfaces. Optionally, the CU may have some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the RLC layer and lower layers) through interfaces, which can be interfaces such as the F1 interface. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). F1AP is the application protocol of the F1 interface, defining the F1 signaling procedures in some examples. The F1 interface supports control plane F1-C and user plane F1-U.

[0080] In some examples, the CU can be split into CU-CP (Control Unit-Control Plane) and CU-UP (Control Unit-User Plane). CU-CP is a logical node carrying the RRC layer and PDCP-C (Control plane part of PDCP) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) elements, such as the Access and Mobility Management Function (AMF) in a 5G system. AMF elements are responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. CU-UP is a logical node carrying the SDAP layer and PDCP-U (User plane part of PDCP) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. These network elements in the core network, such as the UPF (User Plane Function) in a 5G system, are responsible for data forwarding and receiving in terminal devices. The above configuration of CU and DU is just an example; you can also configure the functions of CU and DU as needed.

[0081] In some examples, the DU is a logical node that carries the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, Higher Physical Layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one radio unit (RU). The DU connects to the RU through interfaces, which may be fronthaul interfaces.

[0082] In some examples, the RU is a logical node that carries both Lower Physical Layer (Lower PHY) and Radio Frequency (RF) processing. In other examples, the RU can be a 3GPP Transmission Reception Point (TRP), a Remote Radio Head (RRH), or other similar entities.

[0083] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through the Lower-Layer Split CUS-Plane (LLS-CUS) interface. LLS-CUS may include LLS-C and LLS-U interfaces providing the control plane (C-Plane) and user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and RU. The DU and RU exchange management information via an LLS-M interface on the fronthaul link; the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.

[0084] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.

[0085] In some examples, network devices also include RAN intelligent controllers (RICs). RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs).

[0086] Optionally, near real-time RIC and non-real-time RIC can be set up as separate network elements, or they can be part of other devices. For example, near real-time RIC can be set up in network devices, while non-real-time RIC can be set up in operation administration and maintenance (OAM) network elements, cloud servers, core network devices, or other network devices.

[0087] Optionally, the network device can be a single RAN node or include multiple RAN nodes, such as CU and DU. The CU and / or DU can also have one or more AI modules configured. In some examples, the CU can also be split into CU-CP and CU-UP. One or more AI models are configured in the CU-CP and / or CU-UP.

[0088] Figure 1B illustrates an example diagram of an O-RAN system, which may include components other than those shown in the figure. As shown, access network equipment (e.g., an eNB, gNB, or next-generation access network equipment) communicates with the core network (CN) via a backhaul link and with user equipment (UE) via an air interface.

[0089] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in Figures 2 to 5 as an example. The communication system includes at least a first device and a second device. The role of the first device can be understood as a tag, and the role of the second device can be understood as a reader, but this application does not specifically limit it in this regard.

[0090] Figures 2, 3, and 4 below illustrate a communication system applicable to the embodiments of this application, with the first device as a terminal device and the second device as a network device as examples. Figure 5 illustrates a communication system applicable to the embodiments of this application, with both the first device and the second device being terminal devices as examples.

[0091] Figure 2 illustrates a schematic diagram of a communication system 200. As shown in Figure 2, the network device can communicate bidirectionally with the terminal device. Specifically, the network device can send an excitation signal to the terminal device via a forward link to provide power to the terminal device. The terminal device receives the excitation signal sent by the network device and sends a reflected signal back to the network device via a reverse link. In this way, the network device can identify the ID of the terminal device and perform read and write operations on the terminal device. Uplink and downlink data / signaling exist between the network device and the terminal device.

[0092] Figure 3 is a schematic diagram of another communication system 300. As shown in Figure 3, the communication system 300 includes network devices, intermediate nodes, and terminal devices. Two-way information exchange is possible between the network devices and intermediate nodes, and between the intermediate nodes and terminal devices. Specifically, the network devices can send RFID-related signaling to the intermediate nodes via the fronthaul downlink. The intermediate nodes receive the RFID-related signaling and, based on it, send an excitation signal to the terminal devices via the fronthaul link. The terminal devices send a reflected signal via the reverse link. Correspondingly, the intermediate nodes can receive the reflected signal from the terminal devices via the reverse link and send it to the network devices. Furthermore, the network devices and intermediate nodes can exchange other signaling on the fronthaul uplink and fronthaul downlink, such as resource configuration signaling, which will not be detailed here.

[0093] Optionally, the intermediate node can be a repeater, an integrated access and backhaul (IAB) node, or a UE, etc., and this application does not limit this. The intermediate node transmits data and / or signaling between network devices and terminal devices.

[0094] Figure 4 is a schematic diagram of another communication system 400. As shown in Figure 4, the communication system 400 includes network devices, assisting nodes, and terminal devices. While the network devices and terminal devices engage in bidirectional information exchange, the network devices and assisting nodes, as well as the assisting nodes and terminal devices, can also engage in bidirectional information exchange. For example, the terminal device sends RFID-related signaling to the network device and also to the assisting node. The assisting node then sends the RFID-related signaling back to the network device to assist the terminal device in sending and enhance the network device's reception. The same principle applies when the network device sends RFID-related signaling to the terminal device, which will not be elaborated further. In some implementations, the assisting node and the network device can communicate via a Uu interface.

[0095] Optionally, the auxiliary node can be a repeater, IAB, UE, or other device; this application does not limit this. The terminal device sends data / signaling to the network device and receives data / signaling from the auxiliary node; or the network device sends data / signaling to the terminal device and receives data / signaling from the auxiliary node.

[0096] Optionally, the network devices in Figures 2, 3 and 4 above may be base stations or any of the network devices involved in this application described above, and the terminal devices may be A-IoT terminal devices or any of the terminal devices involved in this application described above, but this application does not limit them.

[0097] Figure 5 is a schematic diagram of another communication system 500. As shown in Figure 5, terminal device 1 and terminal device 2 can perform bidirectional information interaction. In one possible implementation, the communication between terminal device 1 and terminal device 2 adopts 5G NR technology or 5G sidelink technology.

[0098] Optionally, terminal device 1 in Figure 5 above can be a UE, and terminal device 2 can be an A-IoT terminal device. Alternatively, terminal device 2 can be a UE, and terminal device 1 can be an A-IoT terminal device. Terminal device 1 and terminal device 2 can also be any of the terminal devices involved in this application described above, but this application does not limit them.

[0099] It should be understood that the number of network devices, terminal devices, intermediate nodes, and auxiliary nodes in the above communication system example may be more or less, and this application does not limit this.

[0100] It is worth noting that the first device and the second device can be implemented in multiple ways.

[0101] As another example, the first device and the second device are different terminal devices. Accordingly, the communication link between the first device and the second device can be a communication link between terminal devices, such as a side link.

[0102] As another example, the first device can be called an (Environmental Internet of Things) device (which can be an implementation example of a terminal device), and the second device can be called a reader. Accordingly, the communication link between the first device and the second device can include a device-to-reader (DR or D2R) link and a reader-to-device (RD or R2D) link.

[0103] In NR systems, the RLC layer includes three transmission modes: Unacknowledged Mode (UM), Acknowledged Mode (AM), and Transparent Mode (TM). For UM and AM, the input size of the scheduler at the terminal device's MAC layer is limited. If the amount of data the terminal device needs to transmit exceeds the scheduler's input size, the data must be segmented and reassembled at the RLC layer. For RLC layer segmentation, the terminal device needs to buffer the data to be transmitted, save and record the sequence number of the PDU corresponding to the next data to be sent in real time until the data transmission is complete. For terminal devices such as tags, saving and recording the sequence number in real time leads to significant power consumption for the tags, reducing their effective operating time. Furthermore, if the tag's battery runs out before data transmission is complete, the tag will lose its sequence number when the battery is depleted. This means that after the tag is powered on again, it cannot determine which data was not transmitted, reducing data transmission continuity and efficiency. Therefore, this application provides a method to solve the above problems.

[0104] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0105] It is understood that this application does not specifically limit the structure of the execution subject of the method provided in the embodiments of this application. The following description takes the interaction between the first device and the second device as an example. The first device may be a terminal device or a tag, etc., and the first device may also be a chip or module in the terminal device or tag, etc.; the second device may be a network device or a terminal device or a tag, etc., and the first device may also be a chip or module in the network device or a terminal device or a tag, etc.

[0106] Figure 6 shows a schematic flowchart of a data transmission method provided in an embodiment of this application. The method includes:

[0107] Step 601: The first device sends first data and first information.

[0108] Correspondingly, the second device receives the first data and the first information from the first device.

[0109] In this system, the first data is the first part of the second data, and the first information is associated with the corresponding position of the first data in the second data. The first information can also be described as breakpoint information or data segmentation information, etc., and this application does not limit this description. After the first device sends the first information, the first device does not need to save the first information; in this case, the first information can be information temporarily saved by the first device. In another implementation, the first device can also permanently save the first information. Permanently saved information can be understood as information that the first communication device can save regardless of whether it has power or not; temporarily saved information can be understood as information that the first communication device can save when it has power (e.g., the power level is not lower than a certain threshold), but cannot save when the power level is lower than the threshold or the power is depleted.

[0110] The first device can directly send the first data and the first information to the second device, or the first device can send the first data and the first information to the second device through other devices. This application does not limit this.

[0111] The second data can be data stored in the first device, such as the tag identifier (ID) of the first device. The second data can also be data acquired by the first device, such as data collected by the first device. The second data can also be data generated by the first device; this application is not limited to this.

[0112] In another implementation, the first device may send the first information before or after sending the first data; this application is not limited to this. In this implementation, the first data and the first information may be located in different messages.

[0113] In one implementation, the first device determines that its transmission capacity is insufficient and it cannot transmit the entire transmission block size (TBS) corresponding to the second data in one transmission. For example, the first device has insufficient remaining power and the power is not enough to support the transmission of the entire TBS corresponding to the second data in one transmission. The first device can only transmit a portion of the second data.

[0114] In one implementation, the size of the first data can be determined based on the remaining power of the first device. For example, the size of the first data can be less than or equal to the maximum data size that the remaining power of the first device can support for transmission.

[0115] In one implementation, before sending the first data, the first device may send a buffer status report to the second device. The buffer status report indicates the size of the second data. The buffer status report may also be called a storage area status report, register status report, user area status report, etc.; "status report" or "buffer status report" can be replaced with "data to be transmitted" or "data size / number of bits / number of bytes".

[0116] Optionally, in another implementation, the second device receives second indication information from the core network equipment, the second indication information indicating the data size of the second data. In this application, the core network equipment may include, but is not limited to, mobility management network elements, location management network elements, tag management network elements, etc. The mobility management network element may be an access and mobility management function (AMF). The location management network element may be a location management function (LMF). The tag management network element may be a tag management function (TMF), an ambient IoT function (AIoTF), or an ambient IoT management function (AIoTMF).

[0117] The second device can send scheduling information to the first device. This scheduling information can be used to indicate resources for transmitting the second data, and the size of the data scheduled can be equal to the size of the second data. The scheduling information can also be called configuration information, indication information, etc., with no name limitation. The scheduling information can be located in access occasion trigger messages, access round trigger messages, or acknowledgement (ACK) messages, etc. Access round trigger messages can also be called query messages, access round indication messages, etc. Access occasion trigger messages can also be called queryRep messages, or access occasion indication messages, etc. The access round trigger message can be used to trigger / indicate at least one access occasion, such as directly or indirectly indicating the total number of access occasions, or triggering the first access occasion. The access occasion trigger message can be used to trigger / indicate the next access occasion, or it can be understood as indicating / associating with the boundary (start or end) of an access occasion. The ACK message can also be called a random access response message, conflict resolution message, or access ID response message, etc. The ACK message can be used to indicate whether contention resolution was successful.

[0118] In this application, an access opportunity can be understood as a time-domain unit, during which the first device can communicate with the second device. Each access opportunity allows the first device to send access (requests), and / or contention resolution, and / or data transmission, etc. The term "access opportunity" can also be replaced by descriptions such as "access timing," "access resource," "access time slot," "transmission timing," "transmission / communication resource," "transmission time slot," "scheduling resource," "time slot," or "time unit." Resources can include at least one of time resources, frequency resources, and code domain resources. This application uses time resources as an example for description; other cases can be deduced similarly and will not be elaborated further. The length of an access opportunity can be fixed or not fixed; if the length of an access opportunity is not fixed, the lengths of different access opportunities can be different. Optionally, the start time of an access opportunity can be the sending or receiving time of a query message or a query repetition (Queryrep) message, and the end time of the access opportunity can be the sending or receiving time of another query repetition message. In this application, the query repetition message can also be called an access opportunity indication message, an access opportunity trigger message, etc., and this application is not limited to these names.

[0119] In one implementation, the first device can send first data and first information via a first message. The first data may refer to the payload portion of the first message; for example, the first data may be located in the service data unit (SDU) of the first message. Optionally, the first message may also include at least one of the following: message header, padding, message prefix, message suffix, message preamble, mid-amble, and post-amble.

[0120] Optionally, the first information may be located in the message header of the first message, in the data packet of the first message, or in other fields of the first message; this application does not limit this.

[0121] In another implementation, the first information can be divided into multiple parts, and the first information can be indicated by multiple messages. The first message only includes a part of the first information, and the other parts of the first information can be indicated by other messages, such as by a 16-bit random number (RN16). For example, the first information includes 10 bits, of which 5 bits are carried by the first message, and the other 5 bits are indicated by a message carrying RN16.

[0122] In another implementation, the first data and the first information may not be in the same message. For example, the first data can be sent through the first message, and the first information can be sent through the third message.

[0123] This application does not limit the types of messages, such as the third message and the first message. For example, the first message can be an application layer message, a non-access stratum message, uplink data (UL data), etc. Optionally, the third message or the first message may be sent by the first device and received by the second device; or the third message or the first message may be sent by the first device and forwarded to the core network equipment by the second device.

[0124] Optionally, the first message can be used to carry (uplink) data sent by the first device, such as the identification information (temporary identification information or permanent identification information) of the first device, positioning information, sensor data, read data, command feedback and other information.

[0125] For example, the third message can be a random access message, such as AIoT message 1 or AIoT message 3, or a random (access) identifier (random(access) ID), random access request, etc. Optionally, the third message is used by the first device to initiate / request (random) access, or to initiate / request contention resolution.

[0126] In this application, there may be multiple ways to associate the first information with the corresponding position of the first data in the second data. Several examples are given below. Implementation Method 1: The second data includes N segments, where N is an integer greater than 1. This can be understood as the first device dividing the second data into N segments, with one segment being a subset of the second data. The first device transmits at least one segment of the N segments each time. In this implementation, the N segments can be numbered sequentially according to their positions, determining the index of each segment. The first information includes the index of the first data within the N segments. Since the index of each segment is related to its position within the N segments, the position of that segment within the N segments (i.e., the second data) can be determined by the index of a segment. Here, N can be specified by the protocol or determined by the first device and / or the second device. For example, if N is determined by the first device, then N can be carried in the first information, the first data, or the random access message.

[0127] For example, as shown in Figure 7, the second data consists of four segments. Following the order from front to back (i.e., the direction of the arrows in the figure), the indices of these four segments are 00, 01, 10, and 11, respectively. If the first data is the third segment out of the four, then the index of the first information is 10.

[0128] In the second implementation method, the first information includes the index of a reference byte or reference bit of the first data in the second data. The reference byte or reference bit can be preset or determined by the first or second device; this application does not limit this. For example, the reference byte can be the last byte of the first data, and the reference bit can be the last bit of the first data. Furthermore, byte or bit can also be replaced by byte group, bit group, or word, etc.

[0129] For example, as shown in Figure 8, the second data includes multiple bytes, and the first data includes bytes from the 0th byte to the Kth byte of the second data. In the figure, one square can represent one byte. Taking the last byte of the first data as the reference byte as an example, the index of the first information is the index of the Kth byte in the second data. In this way, the first information can indicate the position of the data that has been transmitted in the second data as the Kth byte.

[0130] In the third implementation method, each M bytes or bits in the second data constitutes a data segment, where M is an integer greater than 1. Within the second data, multiple data segments can be numbered sequentially from front to back to determine the index of each segment. The first information includes the index of the data segment corresponding to the reference byte or reference bit of the first data in the second data.

[0131] For example, M = 8, and each M bytes constitutes a data segment. The first data segment includes bytes from the 0th to the 15th byte of the second data segment. Taking the last byte of the first data segment as the reference byte as an example, and assuming that the data segments in the second data segment are numbered starting from 0, then the index of the data segment containing the reference byte is 1, and the first information segment contains index 1. Thus, the first information segment indicates the position of the data segment with index 1 that has already been transmitted in the second data segment.

[0132] The above is just an example. There may be other ways to associate the first information with the corresponding position of the first data in the second data, which will not be elaborated here.

[0133] In this application, the first information also indicates at least one of the following: the data size of the first data;

[0134] The storage area where the second data is located may include, for example, an electronic product code (EPC) storage area, a tag identifier (TID) storage area, a user storage area, etc.

[0135] Whether the second data has been completely transmitted, or whether the first data is the last part of the second data, or whether there is any data to be transmitted, or whether the second data has not been completely transmitted, or whether it is not the last part of the second data, or whether there is any data to be transmitted.

[0136] The end position of the second data; the size of the second data. For example, the end position can indicate which data segment, bit / byte / word the last bit / byte / word of the second data belongs to. Please refer to the previous descriptions for details, which will not be repeated here. The data size can indicate the number of bits or bytes, etc., and the unit of data size is not limited.

[0137] The phrase "the second data has not been fully transmitted, or is not the last part of the second data, or has continued transmission data" can refer to: data still to be transmitted, incomplete service, incomplete uplink data transmission, or incomplete segmented transmission.

[0138] The completion of the second data transmission, or the last part of the second data, or no data to be transmitted, can refer to: no data to be transmitted, service completion, completion of uplink data transmission, end of segmented transmission, etc.

[0139] For example, the first information includes information one, information two, information three, information four, information five, and information six. Information one is associated with the corresponding position of the first data in the second data; information two indicates the data size of the first data; information three indicates the storage area where the second data is located; information four indicates whether the transmission of the second data is complete; information five indicates the end position of the second data; and information six indicates the data size of the second data. Information one, information two, information three, information four, information five, and information six can also be independent information. In this case, the first device can send the first information by means of the following steps: the first device sends one or more of information one, information two, information three, information four, information five, and information six.

[0140] If the first device does not send the first information, or if the first device does not send one or more of information 1, information 2, information 3, information 4, information 5, and information 6, the second device can determine the first information based on the first data, or determine one or more of information 1, information 2, information 3, information 4, information 5, and information 6.

[0141] Optionally, information 2 can be indicated / determined by a downlink (DL) trigger message. The downlink trigger message can be a DL command message. For example, a DL command message is a non-access stratum (NAS) or application layer message, which itself indicates storage area information. For example, a DL command message can indicate whether to read the user storage area of ​​the first device or the Kth segment of data in another storage area.

[0142] At this point, the first piece of information can determine the bit / byte position in the Kth segment of data mentioned above (bit / byte can also be other indicator granularities, such as word or 16 bits, without limitation).

[0143] For example, the first piece of information could be a MAC layer field, such as a MAC control element (CE), and the second piece of information could be message content from a non-access layer or application layer, such as that carried in NAS or application layer messages.

[0144] In another implementation, the positions of the first information and the first data in the second data can have a mapping relationship. This mapping relationship can be preset or pre-configured. For example, 0000 corresponds to the second data or the first segment of the storage area storing the second data, and 0001 corresponds to the second data or the second segment of the storage area storing the second data, etc.

[0145] Optionally, after receiving the first data, the second device may send an acknowledgment message to confirm that the first data was successfully received, or that the segmented data was successfully received.

[0146] Alternatively, the confirmation message may be referred to as an access opportunity indication message, access opportunity trigger message, access round indication message, access round trigger message, etc.

[0147] Alternatively, in another implementation, the first device may not send the first information, and the second device or core network equipment may determine the first information based on the first data; or the first device may not send one or more of information one, information two, information three, information four, information five, and information six, and the second device or core network equipment may determine the first information based on the first data, or determine one or more of information one, information two, information three, information four, information five, and information six. For example, the first information may be determined based on the size of the first data. For instance, if the size of the second data is 256 bits and the size of the first data is 100 bits, then the end position of the first data can be determined as the 100th bit out of the 256 bits, and the second device or core network equipment may determine the first information based on the size of the first data.

[0148] After receiving the first data, if the second device needs to obtain the remaining part of the second data, it can also send a first message to instruct the first data to report the remaining part of the second data. For details, please refer to the following description.

[0149] Step 602: The second device sends the first information to the first device.

[0150] Correspondingly, the first device receives the first information from the second device.

[0151] The second device can send the first information via a downlink trigger message, which instructs the first device to continue reporting the remaining portion of the second data. The downlink trigger message can be a paging or contention-free random access (CFRA) trigger message, an access opportunity trigger message, or a downlink command message, etc., and this application is not limited to these. Optionally, the downlink trigger message can originate from the core network equipment or be generated by the second device.

[0152] Optionally, step 602 can be replaced by: the second device sending one or more of information 1, information 2, information 3, information 4, information 5 and information 6 to the first device; or step 602 can be replaced by: the second device sending third information to the first device.

[0153] Optionally, the downlink trigger message includes one or more of information one, information two, information three, information four, information five, and information six. Optionally, in step 602, the second device sends third information, which is determined based on the data size of the first information or the first data. For example, the third information is one or more of information one, information two, information three, information four, information five, and information six. As another example, the third information indicates at least one of the following: the start position of the third data in the second data, the data size of the third data, and the end position of the third data in the second data.

[0154] In one implementation, the second device or core network equipment can determine at least one of the following based on the first information: the starting position of the third data in the second data; the data size of the third data; and the ending position of the third data in the second data.

[0155] In one implementation, the second device or core network equipment can determine at least one of the following based on the second data and the first data: the starting position of the third data in the second data; the data size of the third data; and the ending position of the third data in the second data.

[0156] In this case, the first device may not send the first information to the second device before step 602.

[0157] In one implementation, the second device or core network equipment can determine at least one of the following based on the first information and the second data: the starting position of the third data in the second data; the data size of the third data; and the ending position of the third data in the second data.

[0158] Furthermore, the second device can carry third information via a downlink trigger message.

[0159] Optionally, the downlink trigger message may carry multiple first information and multiple first identifiers, and the downlink trigger message instructs multiple first devices to send uplink data.

[0160] Multiple first identifiers can be implemented through a group identifier, or multiple first devices can be associated through the common part of multiple first identifiers (similar to the function of a mask).

[0161] Optionally, the downlink trigger message may indicate a first resource, which is used for the transmission of third data.

[0162] The first resource can be a time-domain resource and / or a frequency-domain resource and / or a code-domain resource, and there are no restrictions on how the first resource is indicated.

[0163] Optionally, the first resource and the first information / first identifier correspond, for example, they can correspond by the order of the fields. The downlink trigger message content is: First identifier A, first information A, first resource A, first identifier B, first information B, first resource B, indicating: the first device A associated with the first identifier A sends third data A on the time domain and / or frequency domain and / or code domain resources corresponding to the first resource A, and the starting position of the third data A is associated with the first information A; the first device B associated with the first identifier B sends third data B on the time domain and / or frequency domain and / or code domain resources corresponding to the first resource B, and the starting position of the third data B is associated with the first information B.

[0164] Optionally, in this application, "downlink" can be replaced with "reader-to-device (R2D or RD)" and "uplink" can be replaced with "device-to-reader (D2R or DR)".

[0165] Optionally, the second device may send a first message if it determines that the second data has not been completely transmitted, thereby instructing the first device to send the remaining portion of the second data. In one implementation, the second device can determine that the second data has not been completely transmitted if it determines that the size of the first data is less than the size of the second data or the size of the data scheduled by the scheduling information.

[0166] In another implementation, if the second device receives the first information, or receives one or more of information 1, information 2, information 3, information 4, information 5, and information 6, it can determine that the second data transmission has not been completed.

[0167] In another implementation, if the second device receives the first information and the first information indicates that the second data has not been completely transmitted or that the first data is not the last part of the second data or that there is still data to be transmitted, then it can be determined that the second data has not been completely transmitted.

[0168] In another implementation, if the second device receives information four, and information four indicates that the second data has not been completely transmitted or that the first data is not the last part of the second data or that there is still data to be transmitted, then it can be determined that the second data has not been completely transmitted.

[0169] Optionally, the second device sends a first identifier to the first device, the first identifier being associated with the first device, and / or the first identifier being associated with first data / second data / third data. Accordingly, after receiving the first identifier, the first device determines that the first identifier is associated with the first device, and then sends the third data according to the first information. If the first device determines that the first identifier is not associated with the first device, it does not respond to the first information, that is, it does not send the third data. The first identifier may be in the same message as the first information, or it may be in a different message; this application does not limit this.

[0170] The first identifier can be preset, determined by the first device, or determined by the second device. The first identifier can be an access stratum identifier (AS ID), a local identifier, or an RN16 generated by the first device, etc. If the first identifier is determined by the first device, it can be related to the device identifier of the first device or generated by the first device, for example, the first identifier can be an RN16 generated by the first device. The first device can send the first identifier to the second device, for example, the first identifier can be sent to the second device along with the first data. For example, the first device can also send the first identifier to the second device through a message different from the first data. For example, the first device can generate an RN16, use the RN16 as the first identifier, and send the RN16 to the second device.

[0171] If the first identifier is determined by the second device, the second device may send the first identifier to the first device, for example, by sending the first identifier together with the scheduling information to the first device, or by sending the first identifier to the first device through other messages. This application does not limit this.

[0172] When this application is applied to an O-RAN architecture, if the second device is a base station or access network device in the O-RAN, the RIC in the second device can dynamically assign a first identifier to the first device. In this case, the first identifier can be an AS ID or a new identifier. For example, the first identifier can be assigned based on relevant prior information of the first device; the relevant prior information of the first device can include at least one of the following: the number of first devices; and the estimated inventory duration. In this case, the first identifier can be sent to the first device via downlink messages such as ACK messages.

[0173] Optionally, the RIC can determine the capability or power consumption of the first device and can prioritize triggering the first device with lower capability or power consumption to upload data. In this application, the first identifier can be information temporarily stored or permanently stored by the first device.

[0174] Optionally, the second device may also indicate a TBS to the first device, where the TBS is the data size of the data that the second device requests the first device to report via the first information. This TBS may be the same as or different from the TBS of the first data.

[0175] Optionally, the first device may also send time information to the second device. The time information indicates a first duration and is used to determine the time when the first device receives downlink information or sends uplink information, or the time when the first device's battery level reaches a certain energy threshold, which is at least sufficient to support the transmission of third data. For example, it can be used to determine the time when the first device sends third data or receives first information. The first duration indicated by the time information can be determined based on at least one of the remaining battery level of the first device and the charging time required for the first device. The time information can be sent together with the first data, for example, through a single message; or, the time information and the first data can be sent through different messages. The time unit of the first duration can be absolute time (e.g., milliseconds / seconds / minutes) or relative time, such as frames, subframes, time slots, sub-time slots, the number of received signaling messages, etc.

[0176] After receiving the time information, the second device can determine the time to send the first information or the time to send the third data based on the time information. For example, if the time when the second device receives the time information or the first data is T1, the second device can determine the time to send the first information T2 = T1 + X, or the second device can determine the time when the first device sends the third data T2 = T1 + X, where X is the first duration.

[0177] Optionally, the first device can also send energy information to the second device, and the network side determines the first duration. The energy information can be energy / capacity value / remaining power percentage / energy above a certain threshold, etc. The specific form of the information is not limited, and its function is to measure the amount of energy that the device can currently or subsequently have.

[0178] Optionally, the energy information may also include energy collection information, such as the power / speed of energy collection, power consumption rate (e.g., power in idle / sleep state, power per bit transmitted, or energy), and the network side can determine the minimum amount of time required for the first device based on the energy information.

[0179] Optionally, the network side (e.g., a second device or core network equipment) determines a first duration based on the energy information and sends the first duration to the first device. The first device then performs sleep / energy saving / charging based on the first duration. Optionally, it does not respond to downlink signaling during the first duration. Optionally, there is no restriction on which message carries the energy information; for example, it can be carried in a message that includes RN16 or a message that includes uplink data.

[0180] Step 603: The first device sends the third data. Correspondingly, the second device receives the third data from the first device.

[0181] The third data is the second part of the second data, and the position of the third data in the second data is determined according to the first information.

[0182] In the first implementation, the third data is the same as the second data. In this case, the third data is a retransmission of the second data.

[0183] In the second implementation method, the third data is different from the second data; in this case, the third data is the newly uploaded data.

[0184] Optionally, the second device may send a third indication message indicating whether to retransmit the second data. If the third indication message indicates retransmission of the second data, then the third data determined by the first device based on the first information is the same as the second data. The third indication message may also indicate the data size.

[0185] Optionally, if the second device does not send the third instruction information, or if the third instruction information sent by the second device indicates that the second data should not be retransmitted, then the third data determined by the first device based on the first information is different from the second data.

[0186] The following example, where the third data is different from the second data, illustrates how to determine the third data.

[0187] For example, if the first information includes the index of the first data within N data segments, then the index of the third data within N data segments can be determined based on the index included in the first information. For instance, as shown in Figure 7, the second data includes four data segments, ordered from front to back (i.e., in the direction of the arrows in the figure), with indices of 00, 01, 10, and 11 respectively. If the first data is the third data segment out of the four segments, then the index included in the first information is 10. Therefore, the index of the third data determined based on the first information is 11, meaning the third data is the segment with index 11 in the second data.

[0188] For example, the first information includes the index of a reference byte or reference bit in the second data. Then the starting byte or bit of the third data can be determined based on the reference byte or reference bit of the first data. For instance, if the reference byte is the last byte of the first data, and the index included in the first information is the index of the Kth byte in the second data, then the starting byte of the third data can be determined to be the (K+1)th byte in the second data.

[0189] For example, the first information includes the index of the data segment corresponding to the reference byte or reference bit of the first data in the second data. Then, the starting byte or bit of the third data can be determined based on the data segment corresponding to the reference byte or reference bit of the first data in the second data. For instance, each data segment in the second data consists of 8 bytes. Taking the last byte of the first data as the reference byte as an example, the data segments in the second data are indexed starting from 0. The index 1 included in the first information indicates that the first data includes bytes from the 0th to the 15th byte of the second data. Therefore, the starting byte of the third data is located in the data segment with index 2 in the second data, that is, the starting byte of the third data is the 16th byte of the second data.

[0190] Optionally, the first device sends second information to the second device; the second information is associated with the position of the third data in the second data, and the details can be found in the description of the first information, which will not be repeated here.

[0191] Optionally, the second information may also indicate at least one of the following: the size of the third data; the storage area where the second data is located; optionally, if the first information indicates a storage area, then the second information may no longer indicate a storage area, and reading / writing will be performed in a storage area by default; whether the second data has been transmitted, or whether the third data is the last part of the second data, or whether there is still data to be transmitted.

[0192] Optionally, if the second data transmission is not complete, steps 602 to 603 can be repeated until the second data transmission is complete. The specific process will not be described in detail.

[0193] In this application, the second device may indicate whether the second data transmission is complete, or the first device may indicate whether the second data transmission is complete, which will be described separately below.

[0194] In one implementation method, if the second device determines that the second data transmission is complete, it sends a first indication message to the first device. The first indication message indicates that the second data transmission is complete, or the first indication message indicates that the data transmission is complete.

[0195] For example, if the sum of the sizes of the first and third data is greater than or equal to the size of the second data, or if the sum of the sizes of the first and third data is greater than or equal to the size of the data to be scheduled by the second device, the second device may send a first instruction message to the first device. The second device can schedule data using this scheduling information, and the size of the data scheduled can be equal to the size of the second data.

[0196] For example, the second device receives a first message and a second message. The second device obtains first data from the SDU in the first message and third data from the SDU in the second message. If the size of the second data is 96 bits, and the size of the data scheduled by the scheduling information is 96 bits, and the second device obtains 48 bits of first data and 48 bits of third data, then the second device determines that the sum of the data sizes in the two SDUs is 96 bits, and can therefore determine that the data transmission is complete and there is no follow-up data for the second data.

[0197] The second device can determine the size of the second data based on the buffer status report from the first device or the second indication information from the core network device, or it can determine the size of the second data in other ways.

[0198] Optionally, after receiving the first indication information, the first device may enter a sleep state or temporarily refrain from receiving or responding to downlink signaling from the second device during the second duration to save power. During the second duration, the first device may also perform operations such as charging. The second duration of sleep / refraining from receiving or responding to downlink signaling may be determined by the first device, stipulated by a protocol, or indicated by the second device in the downlink message; this application does not impose any restrictions. The time unit of the second duration may be absolute time (e.g., milliseconds / seconds / minutes) or relative time, such as frames, subframes, time slots, sub-time slots, the number of received signaling messages, etc.

[0199] Optionally, the first device may also indicate a second duration to the second device, for example by carrying the second duration in uplink data or other uplink messages sent to the second device.

[0200] In this implementation, the first device may not need to save the end position of the second data, which can reduce power consumption and increase working time.

[0201] In the second implementation method, the first device can indicate whether there is any data to be transmitted, whether data transmission is complete, or whether it is the last segment / last part / end position of the data. For example, when the first device sends the third data, it also sends a second message, which indicates whether the second data transmission is complete or whether the third data is the last part of the second data. If the second message indicates that the second data transmission is complete, or the third data is the last part of the second data, then it means that the second data transmission is complete. As another example, if the first device sends the third data without sending the second message, it means that no data was transmitted after the third data, and the second data transmission is complete.

[0202] In this implementation, there is no need for a second device to indicate whether data transmission is complete, thus saving signaling overhead.

[0203] Optionally, after acquiring the first data and the third data, the second device can report the first data and the third data separately to the core network equipment. Alternatively, the second device can reassemble the first data and the third data into a single data segment, and then report the reassembled data segment to the core network equipment. This example uses the second data being divided into first data and third data; in reality, the second data can include multiple data segments, such as first data, third data, fourth data, etc. Other cases will not be elaborated upon.

[0204] Using the above method, during the segmented transmission of the second data, the first device transmits a portion of the second data each time, indicating the position of that portion within the second data. For example, the first information is associated with the corresponding position of the first data within the second data. The first device does not need to store the first information, thus saving power. In subsequent transmissions, the second device can return the first information to the first device. The first device can then determine the previously transmitted first data based on this information, thereby determining the position of the third data to be transmitted within the first data. Even if the first device loses the first information due to power failure or other reasons, it can still continue transmitting other parts of the second data using the information from the second device, improving transmission efficiency.

[0205] Based on the preceding description, the following is a specific example illustrating the process.

[0206] Figure 9 shows a schematic flowchart of a data transmission method provided in an embodiment of this application. The method includes:

[0207] Step 901: The core network equipment sends a service request message to the second device.

[0208] Service request messages can be inventory signaling or read signaling, etc.

[0209] The business request message is used to trigger the first device to report data, such as tag ID.

[0210] The service request message may also include second indication information, which may indicate the data size of the data reported by the first device. The service request message may also include other information, which is not limited herein.

[0211] Step 902: The second device sends a paging message to the first device.

[0212] A paging message can be used to instruct a first device to access a second device. The paging message may include information such as the identifier or group identifier of the first device; the specific content of the paging message is not limited in this application. A paging message may also be called a select message, etc. For example, when the second device is a base station / access network device, the paging message can be used to instruct the first device to access the network.

[0213] When the second device is a terminal device, the paging message can be used to instruct the first device to access the terminal device. Optionally, the first device can access the network through the terminal device.

[0214] The paging message can also be used to trigger / instruct the first device to send uplink data, or to trigger / instruct / request the first device to perform a first service, wherein the first service may include at least one of the following: paging service, inventory service, command service (such as read, write, deactivate, lock, etc.), positioning service, and sensing service.

[0215] Paging messages, also known as (initial) DL trigger messages, can be triggered by core network equipment, such as when a core network equipment sends a service request message or paging message to a second device. The service request message is used to request or trigger the first service.

[0216] Step 903: The second device sends an access round trigger message to the first device.

[0217] Access round trigger messages are also known as queries or access round indications. They are used to trigger / indicate at least one access opportunity, such as directly or indirectly indicating the total number of access opportunities, or triggering the first access opportunity.

[0218] For example, the access round trigger message may also include parameters used to trigger / indicate / configure access opportunities. For instance, the access round trigger message may include the value of parameter Q. The value of parameter Q is used to determine the total number of access opportunities; for example, parameter Q may indicate a total number of access opportunities of 2. Q For example, if Q = 4, then the total number of access opportunities is 2. 4 =16. The access round trigger message itself can be used to trigger 2. Q The first access opportunity out of a total of access opportunities. The access round trigger message can be used to trigger 2. QThe first access opportunity in a set of access opportunities can have its start time either the sending or receiving time of the access round trigger message. Since this access opportunity is used for the first device to access the second device, and / or for the first device to transmit data to the second device, the access round trigger message can also be used to trigger the first device to access the second device or to transmit data.

[0219] Optionally, in step 904: the second device sends an access opportunity trigger message to the first device.

[0220] An access opportunity trigger message is used to trigger / indicate at least one access opportunity, and / or, to trigger / indicate a first device to access a second device and / or send service data. An access opportunity trigger message can also be called a QueyRep message. The access opportunity trigger message may also include scheduling information, which can schedule the data size of the data reported by the first device. The specific content included in the access opportunity trigger message is not limited in this application.

[0221] In this application, the first device can initiate access at an access opportunity triggered by an access round trigger message, or it can initiate access at an access opportunity triggered by an access opportunity trigger message. Here, we will take the example of the first device initiating access at an access opportunity triggered by an access opportunity trigger message.

[0222] Step 905: The first device sends RN16.

[0223] RN16 can also be called a random access identifier or a random access request message. RN16 can be used to initiate random access and to distinguish different devices during random access / contention resolution. The first device can also send random numbers of other lengths, such as 8-bit random numbers.

[0224] Optionally, the first device may carry first information in the message including RN16.

[0225] Alternatively, RN16 can serve as a first identifier associated with the first device.

[0226] Optionally, the first device may also send a status buffer report, which indicates the size of the second data. The status buffer report may be in the same message as RN16 or in a different message.

[0227] Step 906: The second device sends an ACK message to the first device.

[0228] Optionally, if the access opportunity trigger message does not include scheduling information, then the ACK message may include scheduling information.

[0229] Optionally, if RN16 is not used as the first identifier associated with the first device, the ACK message may include the first identifier, which may be determined by the second device.

[0230] The ACK message indicates that the first device has successfully accessed the network, meaning the second device has successfully received the RN16 from the first device. This ACK message contains the RN16 from the first device. This ACK message may also be called a random access response message, conflict resolution message, or access ID response message, etc.

[0231] If the first device receives an ACK message including its own RN16, it determines that the random access was successful, that is, the contention was successfully resolved, and the first device can transmit data.

[0232] Step 907: The first device sends the first data.

[0233] If the first device determines that its transmission capacity is insufficient and it cannot transmit the complete TBS corresponding to the first data in one go, it sends the first part of the second data, that is, sends the first data.

[0234] The first data can be located in the first message, for example, the first data can be located in the SDU of the first message. The size of the first data can be determined based on the remaining power of the first device. The first message may also include information such as first information, which is associated with the corresponding position of the first data in the second data.

[0235] If the first device sends the first information in step 905, then the first information in step 907 shall prevail, and the first information in step 905 shall be invalid.

[0236] Optionally, the first message may also include first time information, which is used to determine the time for retransmitting the remaining portion of the second data, and / or, the first time information is used to determine the time for receiving information from the second device again.

[0237] Step 908: The second device sends the first information to the first device.

[0238] Optionally, if the second device determines that the second data has not been fully transmitted, it may send a first message to instruct the first device to send the remaining portion of the second data.

[0239] In one implementation, if the second device determines that the size of the first data is smaller than the size of the second data or the size of the data scheduled by the scheduling information, then it can be determined that the second data has not been transmitted completely.

[0240] In another implementation, if the second device receives the first information, it can determine that the second data has not been transmitted completely.

[0241] In another implementation, if the second device receives the first information and the first information indicates that the second data has not been completely transmitted or that the first data is not the last part of the second data or that there is still data to be transmitted, then it can be determined that the second data has not been completely transmitted.

[0242] The first information can be carried through a downlink trigger message, which may also include a first identifier. The downlink trigger message can be a paging message, a CFRA trigger message, or an access opportunity trigger message, etc., and this application is not limited to these.

[0243] Optionally, the time for the second device to send the first information is determined based on the first time information. For example, the second device determines the time when the first device will resend the remaining portion of the second data based on the first time information, and thus determines the time for sending the first information based on this first time. In this case, the time for the second device to send the first information is less than the first time.

[0244] For example, the second device determines the time when the first device receives information from the second device again based on the first time information as the second time, and thus determines the time to send the first information based on this second time. In this case, the time when the second device sends the first information is greater than or equal to the second time. Optionally, the second device can also indicate the TBS to the first device, where the TBS is the data size of the data that the second device requests to be reported by the first information. This TBS can be the same as or different from the TBS of the first data. This TBS can be in the same message as the first information or in a different message.

[0245] Step 909: The first device sends the third data.

[0246] The third data is the second part of the second data. The position of the third data within the second data is determined based on the first information, as detailed in the preceding description. The third data can be located within the second message, for example, within the SDU of the second message. The size of the third data can be determined based on the remaining battery power of the first device.

[0247] Optionally, if the second data has not yet been transmitted, the second device may also send second information, which is associated with the position of the third data in the second data.

[0248] Optionally, if the second data has not yet been transmitted, the second message may also include second time information, which is used to determine the time to retransmit the remaining portion of the second data, and / or, the second time information is used to determine the time to receive information from the second device again.

[0249] If the second data transmission is not completed, steps 908 to 909 can be repeated until the second data transmission is completed. The specific process will not be described in detail here.

[0250] Step 910: The second device sends the reassembled data corresponding to the first data and the third data to the core network equipment.

[0251] In another implementation, the second device can also send the first data and the third data to the core network equipment respectively.

[0252] Optionally, step 911: the second device sends a first instruction message to the first device.

[0253] If the second device determines that the second data transmission is complete, it sends a first indication message to the first device. The first indication message indicates that the second data transmission is complete, or the first indication message indicates that the data transmission is complete.

[0254] In another implementation, if the second information indicates that the second data transmission is complete or no data is being continued, then step 911 may not be executed.

[0255] Optionally, after the second data transmission is completed, after step 910 or step 911, the network side instructs the first device to report new data again, such as reporting the fourth data. If the first device cannot transmit the fourth data in one message, it can also transmit the fourth data in segments, that is, transmit the fourth data in multiple messages.

[0256] Step 912: The core network equipment sends a downlink command to the second device.

[0257] The downlink command can be a read command or a write command, etc., and this application is not limited to this. The downlink command can trigger the first device to report the fourth data.

[0258] Step 913: The second device sends a downlink command to the first device.

[0259] Step 914: The first device sends the fifth data and the fifth information.

[0260] The fifth data is the first part of the fourth data, and the fifth information is associated with the corresponding position of the fifth data in the fourth data. The fourth data can be data in the EPC storage area of ​​the first device, or data in the user storage area; this application is not limited to either.

[0261] Step 915: The second device sends the fifth message.

[0262] If the second device determines that the fourth data has not been fully transmitted, it can send a fifth message, thereby instructing the first device to send the remaining portion of the fourth data.

[0263] Step 916: The first device sends the sixth data.

[0264] The sixth data is the second part of the fourth data. Optionally, if the fourth data is not fully transmitted, the first device may also send a sixth message, which is associated with the position of the sixth data within the fourth data.

[0265] If the fourth data transmission is not completed, steps 915 to 916 can be repeated until the sixth data transmission is completed. The specific process will not be described in detail here.

[0266] Step 917: The second device sends the reassembled data corresponding to the fifth and sixth data to the core network equipment.

[0267] In another implementation, the second device can also send the fifth and sixth data to the core network equipment respectively.

[0268] Optionally, step 918: the second device sends a first instruction message to the first device.

[0269] Once the second device determines that the fourth data transmission is complete, it sends a first indication message to the first device, indicating that the data transmission is complete.

[0270] In another implementation, if the sixth information indicates that the sixth data transmission is complete or no data is being continued, then step 918 may not be executed.

[0271] The other contents of steps 913 to 918 can be referred to in the previous description, and will not be repeated here.

[0272] It is understood that, in order to achieve the functions in the above embodiments, the first or second device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0273] The following are schematic diagrams of possible communication devices provided in the embodiments of this application. These communication devices can be used to implement the functions of the first or second device in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0274] As shown in Figure 10, the communication device 1000 includes a processing unit 1010 and a communication unit 1020. The communication device 1000 is used to implement the functions of the first or second device in the various method embodiments shown above.

[0275] When the communication device 1000 is used to implement the function of the first device:

[0276] A processing unit is configured to send first data and first information via a communication unit; the first data is a first part of second data, and the first information is associated with the position of the first data in the second data;

[0277] The processing unit is configured to receive the first information from the second device via a communication unit;

[0278] The processing unit is used to send third data through the communication unit; the third data is a second part of the second data, and the position of the third data in the second data is determined according to the first information.

[0279] When the communication device 1000 is used to implement the function of the second device:

[0280] A processing unit is configured to receive first data and first information from a first device; the first data is a first part of second data, and the first information is associated with the position of the first data in the second data;

[0281] The processing unit is configured to send the first information to the first device via the communication unit;

[0282] The processing unit is configured to receive third data from the first device via a communication unit; the third data is a second part of the second data, and the position of the third data in the second data is determined according to the first information.

[0283] More detailed descriptions of the processing unit 1010 and the communication unit 1020 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0284] It should be understood that the division of units in the above device is merely a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, all units in the device can be implemented entirely through software calls from processing elements; all units can be implemented entirely in hardware; or some units can be implemented through software calls from processing elements, while others are implemented in hardware. For example, each unit can be a separate processing element, or it can be integrated into a chip within the device. Alternatively, it can be stored as a program in memory, called and executed by a processing element of the device. Moreover, these units can be fully or partially integrated together, or implemented independently. The processing element here can also be called a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, the operations or units described above can be implemented through integrated logic circuits in the processor element or through software calls from processing elements.

[0285] In one example, a unit in any of the above devices can be one or more integrated circuits configured to implement the above methods, such as one or more application-specific integrated circuits (ASICs), or one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. As another example, when a unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor capable of calling programs. Furthermore, these units can be integrated together and implemented as a system-on-a-chip (SOC). The above-described receiving unit is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the receiving unit is an interface circuit of the chip for receiving signals from other chips or devices. The above-described transmitting unit is an interface circuit of the device for transmitting signals to other devices. For example, when the device is implemented as a chip, the transmitting unit is an interface circuit of the chip for transmitting signals to other chips or devices.

[0286] As another possible product form, the first or second device in this application embodiment can be implemented using a general bus architecture. For ease of explanation, refer to FIG11, which is a schematic diagram of the structure of a communication device 1100 provided in an embodiment of this application. The communication device 1100 includes a processor 1101 and a transceiver 1102. The communication device 1100 can be a terminal device, or a chip or chip system therein; or, the communication device 1100 can be a network device, or a chip or module therein. FIG11 only shows the main components of the communication device 1100. In addition to the processor 1101 and transceiver 1102, the communication device 1100 may further include a memory 1103 and input / output devices (not shown in the figure).

[0287] Optionally, the processor 1101 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1103 is mainly used to store software programs and data. The transceiver 1102 may include radio frequency (RF) circuitry and an antenna. The RF circuitry is mainly used for converting baseband signals to RF signals and processing RF signals. The antenna is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves. Input / output devices, such as touch screens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0288] Optionally, the processor 1101, transceiver 1102, and memory 1103 can be connected via a communication bus.

[0289] When the communication device is powered on, the processor 1101 can read the software program in the memory 1103, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1101 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1101. The processor 1101 converts the baseband signal into data and processes the data.

[0290] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0291] In some embodiments, those skilled in the art will recognize that the above-described communication device 1000 can take the form of the communication device 1100 shown in FIG11 in terms of hardware implementation.

[0292] As an example, the function / implementation process of the processing unit 1010 in FIG10 can be implemented by the processor 1101 in the communication device 1100 shown in FIG11 calling the computer execution instructions stored in the memory 1103. The function / implementation process of the communication unit 1020 in FIG10 can be implemented by the transceiver 1102 in the communication device 1100 shown in FIG11.

[0293] As another possible product form, the first or second device in this application may adopt the composition structure shown in FIG12, or include the components shown in FIG12. FIG12 is a schematic diagram of the composition of a communication device 1200 provided in this application.

[0294] As shown in Figure 12, the communication device 1200 includes at least one processor 1201. Optionally, the communication device also includes a communication interface 1202. When the relevant program instructions are executed in the at least one processor 1201, the communication device 1200 can implement the methods provided in any of the foregoing embodiments and any of the possible designs therein. Alternatively, the processor 1201 can implement the methods provided in any of the foregoing embodiments and any of the possible designs therein through logic circuits or executable code instructions.

[0295] The communication interface 1202 can be used to receive program instructions and transmit them to the processor, or it can be used for communication interaction between the communication device 1200 and other communication devices, such as exchanging control signaling and / or service data. For example, the communication interface 1202 can be used to receive signals from other devices besides the communication device 1200 and transmit them to the processor 1201, or to send signals from the processor 1201 to other communication devices besides the communication device 1200.

[0296] Optionally, the communication interface 1202 can be a code and / or data read / write interface circuit, or the communication interface 1202 can be a signal transmission interface circuit between a communication processor and a transceiver, or a chip pin.

[0297] Optionally, the communication device 1200 may further include at least one memory 1203, which can be used to store the required program instructions and / or data. It should be noted that the memory 1203 may exist independently of the processor 1201 or may be integrated with the processor 1201. The memory 1203 may be located within or outside the communication device 1200, without limitation.

[0298] Optionally, the communication device 1200 may further include a power supply circuit 1204, which can be used to power the processor 1201. The power supply circuit 1204 may be located in the same chip as the processor 1201, or in a separate chip outside the chip containing the processor 1201.

[0299] Optionally, the communication device 1200 may further include a bus, through which the various parts of the communication device 1200 can be interconnected. In some embodiments, those skilled in the art will recognize that the communication device 1000 shown in FIG. 10 can take the form of the communication device 1200 shown in FIG. 12 in terms of hardware implementation.

[0300] As an example, the function / implementation process of the processing unit 1010 in FIG10 can be implemented by the processor 1201 in the communication device 1200 shown in FIG12 calling the computer execution instructions stored in the memory 1203. The function / implementation process of the communication unit 1020 in FIG10 can be implemented by the communication interface 1202 in the communication device 1200 shown in FIG12.

[0301] It should be noted that the structure shown in Figure 12 does not constitute a specific limitation on the first or second device. For example, in other embodiments of this application, the first or second device may include more or fewer components than shown in the figure, or combine some components, or split some components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0302] When the aforementioned communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules (such as radio frequency modules or antennas) in the terminal, which is information sent to the terminal by the base station; or, the terminal chip sends information to other modules (such as radio frequency modules or antennas) in the terminal, which is information sent to the base station by the terminal.

[0303] When the aforementioned communication device is a module applied to a base station, the base station module implements the functions of the base station in the above method embodiments. The base station module receives information from other modules (such as radio frequency modules or antennas) in the base station, information sent by the terminal to the base station; or, the base station module sends information to other modules (such as radio frequency modules or antennas) in the base station, information sent by the base station to the terminal. Here, the base station module can be the baseband chip of the base station, or a DU (Digital Unit) or other modules. The DU can be a DU under an Open Radio Access Network (O-RAN) architecture.

[0304] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0305] The method steps in the embodiments of this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a base station or terminal. Of course, the processor and storage medium can also exist as discrete components in the base station or terminal.

[0306] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0307] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0308] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0309] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0310] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0311] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A data transmission method, characterized by, The method is applied to a first device and comprises: sending first data and first information; the first data is a first part of second data, and the first information is associated with a corresponding position of the first data in the second data; receiving the first information from a second device; sending third data; the third data is a second part of the second data, and a corresponding position of the third data in the second data is determined according to the first information.

2. The method of claim 1, wherein, The first information is associated with the corresponding position of the first data in the second data, and the first information comprises: The first information comprises an index of a last byte or bit of the first data in the second data.

3. The method of claim 1, wherein, Every M bytes or bits in the second data are a data segment, and M is an integer greater than 1. The first information is associated with the corresponding position of the first data in the second data, and the first information comprises: The first information comprises an index of a data segment corresponding to a last byte or bit of the first data in the second data.

4. The method of claim 1, wherein, The second data comprises N data segments, and the first data is one of the N data segments, and N is an integer greater than 1. The first information is associated with the corresponding position of the first data in the second data, and the first information comprises: The first information comprises an index corresponding to the first data in the N data segments.

5. The method according to any one of claims 1 to 4, characterized in that, The first information further indicates at least one of: a data size of the first data; a storage area where the second data is located; whether the second data is transmitted completely.

6. The method according to any one of claims 1 to 5, characterized in that, Before the third data is sent, the method further comprises: receiving a first identifier; determining that the first identifier is associated with the first device.

7. The method according to any one of claims 1 to 6, characterized in that, The data size of the first data is determined according to a remaining power of the first device.

8. The method according to any one of claims 1 to 7, characterized in that, Before the first information from the second device is received, the method further comprises: sending time information, and the time information is used to determine a time of sending the third data or receiving the first information.

9. The method according to any one of claims 1 to 8, characterized in that, The method further comprises: receiving first indication information from the second device, and the first indication information indicates that the second data is transmitted completely.

10. A data transmission method, characterized by, The method is applied to a second device and comprises: receiving first data and first information from a first device; the first data is a first part of second data, and the first information is associated with a corresponding position of the first data in the second data; sending the first information to the first device; receiving third data from the first device; the third data is a second part of the second data, and a corresponding position of the third data in the second data is determined according to the first information.

11. The method of claim 10, wherein, The first information is associated with the corresponding position of the first data in the second data, and the first information comprises: The first information comprises an index of a last byte or bit of the first data in the second data.

12. The method of claim 10, wherein, Every M bytes or bits in the second data are a data segment, and M is an integer greater than 1. The first information is associated with the corresponding position of the first data in the second data, and the first information comprises: The first information comprises an index of a data segment corresponding to a last byte or bit of the first data in the second data.

13. The method of claim 10, wherein, The second data comprises N pieces of data, the first data is one piece of data in the N pieces of data, and N is an integer greater than 1; The first information is associated with a corresponding position of the first data in the second data, and comprises: The first information comprises a corresponding index of the first data in the N pieces of data.

14. The method according to any one of claims 10 to 13, characterized in that, The first information further indicates at least one of: a data size of the first data; a storage area where the second data is located; whether the second data is transmitted completely.

15. The method according to any one of claims 10 to 14, characterized in that, Before the first information is sent to the first device, the method further comprises: receiving time information from the first device; and determining a time for sending the first information according to the time information.

16. A communications device, characterized by Comprise: a processing unit configured to send first data and first information via a communication unit, the first data being a first part of second data, and the first information being associated with a corresponding position of the first data in the second data; the processing unit is configured to receive the first information from a second device via the communication unit; the processing unit is configured to send third data via the communication unit; the third data is a second part of the second data, and a corresponding position of the third data in the second data is determined according to the first information.

17. A communications device, characterized by Comprise: a processing unit configured to receive first data and first information from a first device; the first data being a first part of second data, and the first information being associated with a corresponding position of the first data in the second data; the processing unit is configured to send the first information to the first device via the communication unit; the processing unit is configured to receive third data from the first device via the communication unit; the third data is a second part of the second data, and a corresponding position of the third data in the second data is determined according to the first information.

18. A communications device, characterized by comprise a processor; the processor is configured to execute computer programs or instructions stored in a memory, so that the communication device implements the method of any one of claims 1 to 15.

19. A computer-readable storage medium, characterized in that, The computer programs or instructions are stored, and when the computer programs or instructions are run on a computer, the computer implements the method of any one of claims 1 to 15.

20. A computer program product, characterised in that, When the computer program product is read and executed by the computer, the method of any one of claims 1 to 15 is executed.

Images