Data transmission method and communication apparatus

Abstract

The present application provides a data transmission method and a communication apparatus. The method is applied to a first device. The method comprises: sending a first message to a second device, wherein the first message comprises first segment information, the first segment information is used for indicating that a data packet corresponding to the first message is a second data packet, and the second data packet is a data packet obtained by segmenting a first data packet. The method is also applied to a second device. The method comprises: receiving the first message, wherein the first message comprises the first segment information, the first segment information is used for indicating that the data packet corresponding to the first message is the second data packet, and the second data packet is the data packet obtained by segmenting the first data packet. Therefore, the present application provides a clear solution for specifically sending segmented data packets from the first device to the second device, so that the second device can reassemble the segmented data packets.

Description

Data transmission method and communication device

[0001] This application claims priority to Chinese Patent Application No. 202510380723.7, filed on March 26, 2025, entitled "Data Transmission Method and Communication Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication, and in particular to data transmission methods and communication devices. Background Technology

[0003] In wireless communication systems, such as the Ambient Internet of Things (AIoT) system, terminal devices can report data to the network. For example, the network device instructs the terminal device on the size of the data packet that can be transmitted in a single transmission, referred to as the Transport Block Size (TBS). If the data to be transmitted by the terminal device is smaller than the TBS, the terminal device can send the data. If the data to be transmitted by the terminal device is larger than the TBS, the terminal device must first segment the data before sending the segmented data.

[0004] Currently, for scenarios where terminal devices segment data to be transmitted, the terminal devices need to send segmented data to the network devices; however, there is no specific solution for how to reassemble the segments at the terminal device end. Summary of the Invention

[0005] This application provides a data transmission method and a communication device, which provides a clear scheme for the specific transmission of segmented data, thereby facilitating the reassembly of segmented data packets by network devices.

[0006] In a first aspect, this application provides a data transmission method applied to a first device. The method includes: sending a first message to a second device. The first message includes first segmentation information, which indicates that the data packet corresponding to the first message is a second data packet, and the second data packet is a data packet obtained by segmenting the first data packet.

[0007] The embodiments of this application can be applied to a communication system including a first device and a second device. The first device and the second device can communicate with each other.

[0008] The first device can be an Internet of Things (IoT) device, for example, an AIoT device. Some or all of the characteristics of AIoT devices can be found later in the descriptions in the 3GPP standard.

[0009] The first device can also be a reader, used to read data from AIoT devices. For example, this data could be inventory information of assets inventoried by AIoT devices, or instructions for reading and writing to AIoT devices. This application does not limit the specific implementation of such instructions. The reader is also used to send the data read from the AIoT devices to the core network (CN), thereby facilitating the core network devices' management of the AIoT devices. The reader can include a base station, or it can include intermediate nodes and a radio access network (RAN).

[0010] The second device can be a network-side device used to provide network communication functions. In some cases, it is also called a network device or network element. A network device can usually be a base station (including functional units of a base station, or a combination of functional units of a base station) or a core network unit. A core network unit can be a functional unit in the core network.

[0011] The first data packet mentioned above can be regarded as a complete data packet, and the second data packet can be regarded as a data packet obtained by segmenting the first data packet.

[0012] In the above method, the first device can use the first segmentation information to notify the second device that the first data packet has been segmented. This can improve the data transmission scheme of the segmented data on the first device, making it easier for the second device to reassemble the data. Furthermore, transmitting data packets in segments can avoid transmission delays caused by excessive data volume, thereby improving the efficiency of IoT service transmission.

[0013] If the first device is a reader / writer, the specific implementation of sending the first message to the second device can be found in the description of sending the first message to the CN in Embodiment 1 below; if the first device is an IoT device, the specific implementation of sending the first message to the second device can be found in the description of sending the second message to the CN in Embodiment 2 below, and will not be elaborated here.

[0014] In some implementations, the first segment information includes at least one of the following: a first segment indication, which indicates that the data packet corresponding to the first message is the second data packet; and a first segment number, which is the number of the second data packet and indicates the position of the second data packet in the first data packet.

[0015] In the above method, the first segmentation information includes a first segmentation indication and / or a first segmentation number, which can clearly notify the second device that the first data packet has been segmented, thereby facilitating the second device to reassemble the second data packet included in the first data packet.

[0016] Wherein, if the first device is a reader / writer, the specific implementation of the first segment information including the first segment indication and / or the first segment number can be found in the description of case 1 and case 2 in Embodiment 1 below; if the first device is an IoT device, the first segment information is the second segment information in Embodiment 2 below, the second segment information including the second segment indication and / or the second segment number, the specific implementation of the second segment information can be found in the description of the second segment information in Embodiment 2 below, and will not be repeated here.

[0017] In some implementations, the first message also includes N second data packets, where N is an integer greater than 1.

[0018] In the above method, N second data packets can be sent to the second device together with the first segment information, or the N second data packets can be sent to the second device separately from the first segment information. For example, the first segment information can be sent to the second device first, and then the N second data packets can be sent to the second device. This application embodiment does not limit this.

[0019] In some implementations, the first message also includes a second data packet.

[0020] In the above method, if the first device is a reader / writer, the reader / writer receives N second data packets obtained by segmenting the first data packet from the IoT device. The first device can send a first message to the first device after receiving each second data packet. Each first message sent includes first segmentation information, which includes a first segmentation indication and / or a first segmentation number. The first segmentation indication can specifically indicate that the second data packet corresponding to the first message is an incomplete first data packet. The first segmentation number is the segmentation number of the second data packet corresponding to the first message. This facilitates notifying the second device that the second data packet is obtained by segmenting the first data packet. This improves the data transmission scheme after segmentation on the first device and facilitates data reassembly on the second device.

[0021] If the first device is an IoT device, the first device generates N second data packets and sequentially sends N first messages to the second device. Each first message includes first segmentation information, which includes a first segmentation indication and / or a first segmentation number. The first segmentation indication specifically indicates that the second data packet corresponding to the first message is an incomplete first data packet, and the first segmentation number is the segmentation number of the second data packet corresponding to the first message. This facilitates notifying the second device that the second data packet is obtained by segmenting the first data packet. This improves the data transmission scheme of the segmented data on the first device and makes it easier for the second device to reassemble the data.

[0022] The case where there are N first messages can be applied to scenarios where the reader sends N second data packets to the second device in N separate transactions, or to scenarios where the IoT device sends multiple second data packets to the second device in N separate transactions. For the case where there are N first messages, please refer to the relevant description of multiple NAS messages in Embodiment 2, which will not be repeated here.

[0023] In some implementations, the first data packet is a Non-Access Layer Protocol Data Unit (NAS PDU) or an AIoT service data packet. That is, the object of segmentation processing can be an AIoT service data packet in the AIoT upper layer (the higher layer of the first device), or the object of segmentation processing can be a NAS PDU in the NAS layer (the non-access layer of the first device).

[0024] In some implementations, the second data packet is a NAS PDU or a container.

[0025] In some implementations, when the first segment number is a first value, the second data packet is the first data packet. It can be understood that if the first segment number is a specific value, the second data packet is the first data packet; for example, the first segment number might be 0 or a special value.

[0026] In some implementations, the first message also includes a service identifier and a device identifier of the first device, wherein the service identifier is used to indicate the AIoT service corresponding to the second data packet.

[0027] Among them, the device identifier of the first device can be the identifier of an Internet of Things (IoT) device.

[0028] In some implementations, when the first device is a reader / writer, the device identifier of the first device is the device identifier of the reader / writer; when the first device is an IoT device, the device identifier of the first device is the device identifier of the IoT device.

[0029] In some other implementations, when the first device is a reader / writer, the device identifier of the first device includes the device identifier of the reader / writer and the device identifier of the IoT device; when the first device is an IoT device, the device identifier of the first device is the device identifier of the IoT device.

[0030] For example, a service identifier indicates that the first data packet is the data packet corresponding to the AIoT device's storage, reading, writing, or temperature acquisition service.

[0031] In some implementations, the method further includes: receiving a third message sent by a second device, the third message including first indication information, the first indication information being used to indicate the segmentation capability of the second device.

[0032] In the above method, the first device is a reader / writer. Specifically, the first indication information is used to indicate the segmentation capability of the second device, which can be understood as whether the second device supports the first device in segmenting the first data packet of the IoT device.

[0033] The specific implementation of the first instruction information can be found in the description of the first instruction information in Embodiment 3 below, which will not be repeated here.

[0034] In some implementations, the first indication information includes at least one of the following: segmentation capability indication, which indicates that the second device supports data segmentation; and segmentation quantity indication, which indicates the number of data segments that the second device supports.

[0035] In the above method, the first device is a reader / writer. If the first indication information includes a segmentation capability indication, the first device can determine that the first data packet of the Internet of Things device can be segmented according to the segmentation capability indication. If the first indication information includes a segmentation quantity indication, the first device can determine the number of segments to be segmented for the first data packet according to the segmentation quantity indication.

[0036] The specific implementation methods of segmentation capability indication and segmentation quantity indication can be found in the description of segmentation capability indication and segmentation quantity indication in Embodiment 3 below, which will not be repeated here.

[0037] In some implementations, the third message also includes: a service identifier; the service identifier is used to indicate the first service segment allowed by the second device. The first service can be any service, for example, the first service can be a device inventory operation, or the first service can be a temperature data acquisition service.

[0038] Secondly, this application provides a data transmission method applied to a second device. The method includes: receiving a first message sent by a first device, the first message including first segmentation information, the first segmentation information indicating that the data packet corresponding to the first message is a second data packet, and the second data packet is a data packet obtained by segmenting the first data packet.

[0039] The embodiments of this application can be applied to a communication system including a first device and a second device. The first device and the second device can communicate with each other.

[0040] In the above method, corresponding to the first device, the second device can receive the first message sent by the first device and determine through the first message that the first data packet has been segmented. In this way, the scheme of the second device receiving the segmented data from the first device can be improved, which facilitates the second device to reassemble the data. Furthermore, transmitting data packets in a segmented manner can avoid transmission delays caused by excessive data volume, thereby improving the efficiency of IoT service transmission.

[0041] Wherein, if the first device is a reader / writer, the specific implementation of receiving the first message sent by the first device can be found in the relevant description of CN receiving the first message in Embodiment 1; if the first device is an IoT device, the specific implementation of receiving the first message sent by the first device can be found in the relevant description of CN receiving the second message in Embodiment 2, and will not be elaborated here.

[0042] In some implementations, the first segment information includes at least one of the following: a first segment indication, which indicates that the data packet corresponding to the first message is the second data packet; and a first segment number, which is the number of the second data packet and indicates the position of the second data packet in the first data packet.

[0043] In some implementations, the first message also includes N second data packets, where N is an integer greater than 1; the method further includes: if the first segment information includes a first segment indication, reassembling the N second data packets according to the order in which each second data packet is arranged in the first data packet; if the first segment information includes a first segment number, reassembling the N second data packets according to the position of each second data packet in the first data packet.

[0044] In the above method, the second device can determine that the second data packet needs to be reassembled by the first segmentation indication or the first segmentation number, thereby realizing the data reassembly of the second data packet, which can improve the overall scheme of sending and reassembling segmented data between the first device and the second device.

[0045] Wherein, if the first device is a reader / writer and the first segment information includes a first segment indication or a first segment number, the data reconstruction scheme of the second device can be found in the description of data reconstruction in S503 of Embodiment 1; if the first device is an IoT device and the first segment information is second segment information and the second segment information includes a second segment indication or a second segment number, the data reconstruction scheme of the second device can be found in the description of data reconstruction in S602 of Embodiment 2, and will not be described in detail here.

[0046] In some implementations, the first message also includes N second data packets, where N is an integer greater than 1.

[0047] In some implementations, the first data packet is a Non-Access Stratum Protocol Data Unit (NAS PDU) or an AIoT (Artificial Intelligence of Things) service data packet.

[0048] In some implementations, the second data packet is a NAS PDU or a container.

[0049] In some implementations, when the first segment number is the first value, the second data packet is the first data packet.

[0050] In some implementations, the first message also includes a service identifier and a device identifier of the first device, wherein the service identifier is used to indicate the AIoT service corresponding to the second data packet. In some implementations, the method further includes sending a third message to the first device, the third message including first indication information, the first indication information being used to indicate the segmentation capability of the second device.

[0051] In the above method, the first device is a reader / writer, and the second device can use the first instruction information to notify the first device of the segmentation capability of the second device, which can be understood as whether the second device supports the first device to segment the first data packet of the Internet of Things device.

[0052] The specific implementation of the first instruction information can be found in the description of the first instruction information in Embodiment 3 below, which will not be repeated here.

[0053] In some implementations, the first indication information includes at least one of the following: segmentation capability indication, which indicates that the second device supports data segmentation; and segmentation quantity indication, which indicates the number of data segments that the second device supports.

[0054] In the above method, the first device is a reader / writer, and the second device can notify the first device of its segmentation capability through a segmentation capability indicator or a segmentation quantity indicator, so that the first device can determine whether it can segment the first data packet of the Internet of Things device according to the first indicator information.

[0055] The specific implementation methods of segmentation capability indication and segmentation quantity indication can be found in the description of segmentation capability indication and segmentation quantity indication in Embodiment 3 below, which will not be repeated here.

[0056] In some implementations, before sending the third message to the first device, the method further includes: obtaining the first capability of the first device, wherein the first capability is the segmentation capability of the first device.

[0057] In the above method, the first device can be a reader or an IoT device. The first capability can include the first capability of the reader and / or the first capability of the IoT device. The first capability corresponding to the reader is used to indicate that the first device supports the ability to segment the first data packet of the IoT device, and the first capability corresponding to the IoT device is used to indicate that the IoT device has the ability to segment data.

[0058] Before the second device sends the first instruction information to the first device, the second device also needs to obtain the first capability corresponding to the reader and / or the first capability corresponding to the IoT device. If the first capability corresponding to the reader indicates that the reader supports data segmentation of the first data packet of the IoT device, the reader can schedule the IoT device to perform data segmentation; otherwise, the reader cannot schedule the IoT device to perform data segmentation. Similarly, if the second capability corresponding to the IoT device indicates that the IoT device supports data segmentation of the first data packet, the IoT device can perform data segmentation of the first data packet; otherwise, the IoT device cannot perform data segmentation of the first data packet.

[0059] The specific implementation method of the second device acquiring the first capability can be found in the following embodiment three, which describes the CN acquiring the segmentation capability of the AIoT device and / or the segmentation capability of the reader. It will not be elaborated here.

[0060] Thirdly, this application provides a communication device, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices and transmit them to the processor, or to send signals from the processor to other communication devices. The processor is used to implement the method in any possible implementation of any of the above aspects through logic circuits or execution code instructions.

[0061] Fourthly, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed by a communication device, implement the method in any possible implementation of any of the above aspects.

[0062] Fifthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0063] Sixthly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the possible implementations of the above aspects to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0064] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0065] In a seventh aspect, this application provides a communication system, comprising: a first device and a second device, wherein the first device is configured to execute any one of the technical solutions described in the first aspect, and the second device is configured to execute any one of the technical solutions described in the second aspect. Attached Figure Description

[0066] Figure 1 is a schematic diagram of the architecture of the mobile communication system used in the embodiments of this application;

[0067] Figure 2 is a structural diagram of a communication system for an environmental Internet of Things according to an embodiment of this application;

[0068] Figure 3 is a schematic diagram of the protocol stack of an environmental Internet of Things according to an embodiment of this application;

[0069] Figure 4 is a schematic diagram of the protocol stack of an environmental Internet of Things according to an embodiment of this application;

[0070] Figure 5 is a schematic diagram of the protocol stack of an environmental Internet of Things according to an embodiment of this application;

[0071] Figure 6 is a schematic diagram of the protocol stack of an environmental Internet of Things according to an embodiment of this application;

[0072] Figure 7 is a schematic diagram of the protocol stack architecture of an AIoT device according to an embodiment of this application;

[0073] Figure 8 is a schematic diagram of a MAC PDU obtained by a MAC layer according to an embodiment of this application;

[0074] Figure 9 is a schematic diagram of a reader scheduling AIoT device to perform segmentation according to an embodiment of this application;

[0075] Figure 10 is a flowchart illustrating a data transmission method according to an embodiment of this application;

[0076] Figure 11 is a flowchart illustrating a data transmission method according to an embodiment of this application;

[0077] Figure 12 is a flowchart illustrating a data transmission method according to an embodiment of this application;

[0078] Figure 13 is a schematic block diagram of a communication device provided in an embodiment of this application;

[0079] Figure 14 is a schematic block diagram of a communication device provided in an embodiment of this application;

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

[0081] Figure 1 is a schematic diagram of the architecture of the communication system 1000 used in the embodiments of this application. As shown in Figure 1, the communication system includes a radio access network (RAN) 100, wherein the RAN 100 includes at least one RAN node (110a and 110b in Figure 1, collectively referred to as 110), and may also include at least one terminal (120a-120j in Figure 1, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The terminal 120 is wirelessly connected to the RAN node 110. Terminals and RAN nodes can be interconnected via wired or wireless means. The communication system 1000 may also include a core network 200. The RAN node 110 is connected to the core network 200 via wireless or wired means. The core network equipment in the core network 200 and the RAN node 110 in the RAN 100 may be independent and different physical devices, or they may be the same physical device that integrates the logical functions of the core network equipment and the logical functions of the RAN node. The communication system 1000 may also include the Internet 300.

[0082] RAN100 can be an evolved universal terrestrial radio access (E-UTRA) system, a new radio (NR) system, or a future radio access system as defined in the 3rd generation partnership project (3GPP). RAN100 can also include two or more of the above-mentioned different radio access systems. RAN100 can also be an open RAN (O-RAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system.

[0083] RAN nodes, also known as radio access network devices, RAN entities, or access nodes, are used to help terminals access communication systems wirelessly. In one application scenario, an RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a next-generation base station in a 6G mobile communication system, or a base station in a future mobile communication system. RAN nodes can be macro base stations (as shown in Figure 1, 110a), micro base stations or indoor stations (as shown in Figure 1, 110b), and can also be relay nodes or donor nodes.

[0084] In another application scenario, multiple RAN nodes can collaborate to help terminals achieve wireless access, with different RAN nodes implementing different functions of the base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU). Here, the CU performs the functions of the base station's Radio Resource Control (RRC) and Packet Data Convergence Protocol (PDCP), and can also perform the functions of the Service Data Adaptation Protocol (SDAP). The DU performs the functions of the base station's Radio Link Control (RANC) and Medium Access Control (MAC) layers, and can also perform some or all of the physical layer functions. For specific descriptions of these protocol layers, refer to the relevant 3GPP technical specifications. The RU can be used to implement radio frequency signal transmission and reception. The CU and DU can be two independent RAN nodes or integrated into the same RAN node, such as within a baseband unit (BBU). The RU can be included in radio frequency equipment, such as in a remote radio unit (RRU) or an active antenna unit (AAU). The CU can be further divided into two types of RAN nodes: CU-control plane and CU-user plane.

[0085] In different systems, RAN nodes may have different names. For example, in an O-RAN system, a CU can be called an open CU (O-CU), a DU can be called an open DU (O-DU), and an RU can be called an open RU (O-RU). The RAN nodes in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. For example, a RAN node can be a server loaded with the corresponding software modules. The embodiments of this application do not limit the specific technology or device form used in the RAN nodes. For ease of description, a base station is used as an example of a RAN node in the following description.

[0086] A terminal is a device with wireless transceiver capabilities, capable of sending signals to or receiving signals from a base station. Terminals can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal.

[0087] Base stations and terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can be deployed on aircraft, balloons, and satellites. The embodiments of this application do not limit the application scenarios of the base stations and terminals.

[0088] The roles of base stations and terminals can be relative. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile base station. For terminals 120j that access the wireless access network 100 through 120i, terminal 120i is a base station; however, for base station 110a, 120i is a terminal, meaning that 110a and 120i communicate via a wireless air interface protocol. Of course, 110a and 120i can also communicate via a base station-to-base station interface protocol. In this case, relative to 110a, 120i is also a base station. Therefore, both base stations and terminals can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with base station functions, and 120a-120j in Figure 1 can be called communication devices with terminal functions.

[0089] Communication between base stations and terminals, between base stations, and between terminals can be conducted using licensed spectrum, unlicensed spectrum, or both simultaneously. Communication can be conducted using spectrum below 6 GHz, spectrum above 6 GHz, or both simultaneously. The embodiments of this application do not limit the spectrum resources used for wireless communication.

[0090] In the embodiments of this application, the functions of the base station can be executed by modules (such as chips) within the base station, or by a control subsystem that includes base station functions. This control subsystem, including base station functions, can be a control center in the aforementioned application scenarios such as smart grids, industrial control, intelligent transportation, and smart cities. Similarly, the functions of the terminal can be executed by modules (such as chips or modems) within the terminal, or by a device that includes terminal functions.

[0091] To facilitate understanding of the embodiments of this application, the relevant concepts involved in this application will first be explained.

[0092] 1. Environmental IoT devices

[0093] Ambient Internet of Things (AIoT) devices are IoT devices that can be powered by energy harvesting and have limited energy storage capacity. Specifically, AIoT devices do not require an external power supply or battery replacements, resulting in extremely low maintenance costs. They can be widely used in smart warehousing, smart logistics, smart agriculture, industrial wireless sensor networks, smart transportation, smart healthcare, and other fields. AIoT devices can include various sensors, smart meters, and more.

[0094] 2. Environmental IoT Services

[0095] Ambient IoT services (AIoT service) support the functions and processes of environmental IoT application scenarios. AIoT is one possible abbreviation for Ambient IoT, but other English abbreviations, such as A-IoT, may also be used; this application does not limit the specific abbreviation used.

[0096] 3. AIoT service data packets

[0097] AIoT service data packets are service data generated by AIoT devices or AIoT servers that need to be transmitted via wireless networks, such as 5G networks. Specifically, AIoT service data packets can also be service data packets that have been encapsulated at protocol layers, such as application layer, transport layer, and data link layer.

[0098] The rise of IoT technology has presented new challenges to communication systems. Use cases for IoT devices can include logistics, warehousing, factory automation, and animal husbandry. IoT devices and network devices can engage in intermittent, simple communication or coarse location tracking. Even the simplest IoT devices, such as NB-IoT terminal devices used for measuring electricity in coal mines, require batteries for power.

[0099] As a result, AIoT devices have emerged. AIoT devices are Internet of Things devices that can be powered by energy harvesting and have limited energy storage capacity.

[0100] AIoT devices require no external power supply or battery replacements, resulting in extremely low maintenance costs. They can be widely used in fields such as smart warehousing, smart logistics, smart agriculture, industrial wireless sensor networks, smart transportation, and smart healthcare. AIoT devices can include various sensors and smart meters.

[0101] Among them, AIoT-related applications can include: (1) Identification-based connectivity (asset identification), with typical scenarios including the management of goods or assets in the manufacturing and logistics industries. (2) Micro-sensor-based connectivity (sensor data acquisition), with typical scenarios including wireless sensor networks in the energy, power, animal husbandry, and industrial sectors. (3) Low-power downlink connectivity (data downlink push), with typical scenarios including electronic shelf labels (ESL) applications in industrial, supermarket retail, and office applications.

[0102] Compared to existing narrowband internet of things (NB-IoT) devices, AIoT devices, combined with cellular networks, have lower or even zero power consumption, making passive cellular networks suitable for more IoT scenarios.

[0103] The network structure of the AIoT communication system mainly includes the two topological network structures shown in Figure 2. The two topological structures will be explained in detail below.

[0104] Figure 2(a) shows a structural diagram of a communication system for an environmental Internet of Things (AIoT) according to an embodiment of this application. As shown in Figure 2(a), the communication system includes a base station and AIoT devices.

[0105] AIoT devices can be used to receive excitation signals or backscattered signals.

[0106] Base stations can provide data transmission services to AIoT devices through wireless interfaces. That is, base stations and AIoT devices can transmit data wirelessly. For example, base stations can send data or instructions to AIoT devices through wireless communication, and AIoT devices can report data through wireless communication, such as data packets, data packet size, energy information, etc.

[0107] Please refer to Figure 2(b), which shows a schematic diagram of the architecture of another Internet of Things (IoT) network communication system provided in an embodiment of this application. As shown in Figure 2(b), the communication system may include a base station, intermediate nodes (or auxiliary nodes), and AIoT devices.

[0108] In this architecture, AIoT devices communicate wirelessly with base stations through intermediate nodes.

[0109] The intermediate node can be a relay, user equipment (UE), integrated access and backhaul (IAB) node, repeater, or other device with relay capabilities. In this embodiment, the intermediate node can be considered as part of the base station.

[0110] In the embodiment shown in Figure 2(b), an intermediate node can provide data transmission services to AIoT devices via a wireless interface, i.e., the intermediate node provides relay functionality for the AIoT devices. For example, during uplink, the AIoT device can send uplink data to the base station through the intermediate node, or the AIoT device can send uplink data directly to the base station. During downlink, the base station can send downlink data to the AIoT device through the intermediate node, or the base station can send downlink data directly to the AIoT device. In other words, the intermediate node can assist the base station and the AIoT device in achieving wireless communication during uplink and / or downlink processes.

[0111] In this context, the base stations and intermediate nodes that provide wireless interface transmission for AIoT devices can be collectively referred to as readers. During data transmission, the process of an AIoT device sending data to a reader can be called D2R transmission, and the specific content transmitted can be called a D2R message. Conversely, the process of a reader sending data to an AIoT device can be called R2D transmission, and the specific content transmitted can be called an R2D message.

[0112] It should be noted that, in addition to the architectures of the AIoT system shown in Figure 2(a) and Figure 2(b), the architecture of the AIoT system can include various other architectures, which are not specifically limited in this application. For example, the transmitting and receiving of the AIoT device may be handled by different base stations or nodes.

[0113] It should also be noted that the base station described above can be referred to the RAN description shown in Figure 1, and is not specifically limited here. The AIoT device described above can communicate with the core network via the reader shown in Figure 2(a) and Figure 2(b). The AIoT device can be referred to the terminal device description shown in Figure 1, and is not specifically limited here.

[0114] Furthermore, for topology 1 in Figure 2(a) above, 3GPP has two possible protocol stack structures as shown in Figure 3 and Figure 4. Figure 3 shows an example of a protocol stack for topology 1 between AIoT devices and AIoT function (AIOTF) (direct path), and Figure 4 shows an example of a protocol stack for topology 1 between AIoT devices and AIOTF (indirect path via AMF).

[0115] As shown in Figure 3, if an AIoT device needs to send data to an application function (AF), it can do so through the AIoT RAN, AIOTF, or network exposure function (NEF). Similarly, if an AF needs to send data to an AIoT device, it can do so through the NEF, AIOTF, or AIoT RAN. The AF can be a data analytics platform, remote control software, etc. This application does not limit the specific type of AF. For a detailed description of the functions and processes of each layer of the protocol stack, please refer to 3GPP TS23.369.

[0116] The following explanation, using Figure 3 as an example, illustrates how an AIoT device sends data (e.g., AIoT data collected by a sensor) to the AF. The AIoT device acquires AIoT data and sends it to the AIoT Non-Access Stratum (AIoT NAS). The AIoT NAS then transmits the data to the AIoT RAN via the AIoT Access Stratum (AIoT AS), also known as the AIoT AS Layers. The data is then transmitted to the corresponding AIOTF, which in turn transmits it to the NEF. Finally, the NEF transmits the data to the AF via the AIOTF's API interface.

[0117] As shown in Figure 4, if an AIoT device needs to send data to the AF (Access and Mobility Management), the AIoT device can send data to the AF through the AIoT RAN (Access and Mobility Management RAN), the AIOTF (Access and Mobility Management Function), and the NEF (Network Provider Interface). Similarly, if the AF needs to send data to an AIoT device, the AF can send data to the AIoT device through the NEF, AIOTF, AMF, and AIoT RAN. The AF can be a data analytics platform, remote control software, etc. This application does not limit the specific type of AF. It should be noted that the various functional entities through which AIoT data transmission passes in this application are not mandatory; different functional entities can be selected according to different data transmission requirements. For example, data transmission between the AIOTF and the AF may not pass through the NEF.

[0118] The following explanation, using Figure 4 as an example, illustrates how an AIoT device sends data (e.g., AIoT data collected by a sensor) to the AF. The AIoT device acquires AIoT data and sends it to the AIoT NAS. The AIoT NAS then sends the data to the AIoT RAN via the AIoT AS Layers. The AIoT RAN sends the data to the AMF, which in turn transmits it to the AIOTF. The AIOTF then transmits the data to the NEF, and the NEF finally transmits it to the AF via the AIOTF's API interface.

[0119] Furthermore, for topology 2 in Figure 2(b) above, 3GPP has two possible protocol stack structures as shown in Figure 5 and Figure 6. Figure 5 shows a protocol stack example of one transmission mode of topology 2, and Figure 6 shows a protocol stack example of another transmission mode.

[0120] As shown in Figure 5, AIoT devices can communicate with the AIoT RAN through intermediate nodes (such as UEreader). The intermediate nodes and the AIoT RAN can be collectively referred to as readers.

[0121] Taking the UE Reader as an intermediate node as an example, if an AIoT device needs to send data to the AF, the AIoT device can send data to the AF through the UE Reader, NG-RAN, User Plane Function (UPF), AIOTF, or NEF. Similarly, if the AF needs to send data to an AIoT device, the AF can send data to the AIoT device through NEF, AIOTF, UPF, NG-RAN, or UE Reader. The AF can be a data analysis platform, remote control software, etc. This application does not limit the specific type of AF.

[0122] The UPF is located between the NG-RAN (5G access network) and AIOTF (Internet of Things Functions), serving as a data relay hub.

[0123] As shown in Figure 6, AIoT devices can communicate with the AIoT RAN through intermediate nodes (such as UE Readers). The intermediate nodes and the AIoT RAN can be collectively referred to as readers.

[0124] Taking the UE Reader as an intermediate node as an example, if an AIoT device needs to send data to the AF, the AIoT device can send data to the AF through the UE Reader, NG-RAN, AMF, AIOTF, or NEF. Similarly, if the AF needs to send data to an AIoT device, the AF can send data to the AIoT device through NEF, AIOTF, AMF, NG-RAN, or UE Reader. The AF can be a data analysis platform, remote control software, etc. This application does not limit the specific type of AF.

[0125] In Figure 6, the RRC layer can be used to control the connection status of the terminal device (e.g., triggering sleep mode to save power). The RLC / PDCP layer is used for data segmentation, header compression, and encryption. The PHY / MAC layer is used by the terminal device to transmit wireless signals through the physical layer, and for channel resource allocation, etc.

[0126] Figure 7 shows the protocol stack architecture of an AIoT device. It should be noted that the names and functions of each protocol layer in an AIoT device are not fully defined. This application does not specifically limit the names and functions of the relevant protocol layers. The following explanation uses an AIoT device including the AIoT upper layer, NAS layer, and MAC layer as an example.

[0127] The AIoT upper layer refers to the higher layer of AIoT devices, which can generate AIoT data (such as temperature data collected by temperature sensors), also known as AIoT service data packets or AIoT application data packets. AIoT service data packets can be stored in the first cache of the AIoT device, such as the AIoT device's non-volatile memory (NVM).

[0128] The NAS layer, also known as AIoT NAS, can be called the non-access layer. The NAS layer can encapsulate AIoT service data packets according to NAS rules, and optionally perform encryption and decryption operations. The resulting data packets can be called NAS protocol data units (PDUs).

[0129] The MAC layer is also a part of the AIoT AS Layer. The MAC layer can encapsulate data based on the obtained MAC Media Access Control Service Data Unit (SDU). The data packet obtained by the MAC layer can be called a MAC PDU. The output data packet of the NAS layer is called a NAS PDU, and the NAS PDU input into the MAC layer is called a MAC SDU.

[0130] The MAC layer can receive scheduling information from the reader. The MAC layer can send all or part of the scheduling information to the AIoT upper layer or NAS layer, so that the AIoT upper layer or NAS layer can perform data segmentation. See Figure 9 for details, which will not be described in detail here.

[0131] Currently, there is no clear solution regarding which protocol layer (AIoT upper layer or NAS layer) should perform data segmentation. In other words, data segmentation can be performed in either the AIoT upper layer or the NAS layer. When data segmentation is performed in the AIoT upper layer, the object of segmentation is the AIoT service data packet within the AIoT upper layer (e.g., command feedback in Figure 8, which can be service data or service data encapsulated by a portion of the lower-layer protocol stack (e.g., the transport layer)). When data segmentation is performed in the NAS layer, the object of segmentation can be either the AIoT service data packet or the NAS PDU within the NAS layer (e.g., the data packet composed of NAS layer information and command feedback in Figure 8). In practice, the AIoT upper layer's segmentation also involves storing the AIoT service data packet in a first buffer. The specific segmentation method can be retrieving data packets of different sizes from the buffer and submitting the retrieved data packets to the NAS layer.

[0132] Figure 8 shows the specific form of the MAC PDU obtained by the MAC layer. MAC layer information contains MAC layer related information, which may include MAC layer header information and other information that the MAC layer needs to add. NAS layer information contains NAS layer related information, which may include address information and data indication information encapsulated by the NAS protocol. NAS layer information and AIoT service data packets (command feedback) together constitute the NAS layer NAS PDU. Command feedback refers to the AIoT service data packets in the AIoT upper layer.

[0133] When the segmentation object is an AIoT service data packet: if segmentation is not performed, the command feedback is the complete service data packet; if data segmentation is performed, the command feedback is a data packet resulting from the segmentation of the complete data packet. When the segmentation object is a NAS PDU: if segmentation is not performed, the complete NAS PDU, containing the complete service data packet, is submitted to the MAC layer; if data segmentation is performed, the NAS layer submits a segmented data packet to the MAC layer, and the NAS PDU contains a segmented data. When the segmentation object is an AIoT service data packet, data segmentation can be performed by either the AIoT upper layer or the NAS layer. When the segmentation object is a NAS PDU, data segmentation can be performed by either the NAS layer or the MAC layer. Whether the AIoT upper layer or the NAS layer needs to perform data segmentation is detailed in Figure 9, and will not be elaborated upon here.

[0134] Based on the topology in Figure 2 and the protocol stacks in Figures 3 to 6, the specific data packet transmission process can be shown in Figure 9.

[0135] S401, the reader sends an R2D message to the AIoT device.

[0136] The R2D message includes D2R scheduling information, which indicates the amount of data the AIoT device sends to the reader in the D2R message, i.e., the transport block size (TBS). The scheduling information can directly indicate the TBS or implicitly indicate it. Implicitly, the TBS is calculated based on the available transmission resources for the AIoT device, such as time-domain resources, frequency-domain resources, or repetition methods. The AIoT device can calculate the TBS based on time-domain or frequency-domain resources.

[0137] S402, the AIoT device sends a D2R message to the reader based on the R2D message.

[0138] D2R messages can include either fragmented data packets or complete data packets.

[0139] It should be noted that if TBS is smaller than the data size of the D2R message to be sent by the AIoT device, the AIoT device needs to segment the data packets to be sent, sending only a portion of the data packets each time, and waiting for the reader to schedule again. That is, S401 and S402 are executed in a loop until the AIoT device has sent all the data packets to be sent.

[0140] In other words, if the TBS is smaller than the data size of the D2R message to be sent by the AIoT device, data segmentation is required, and the D2R message includes the segmented data packets. If the TBS is greater than or equal to the data size of the D2R message to be sent by the AIoT device, segmentation is not required, and the D2R message includes the complete data packets.

[0141] However, the environmental IoT communication protocol has not yet provided a specific solution on how to reassemble segmented data packets at the AIoT device or reader end.

[0142] To address the aforementioned issues, this application provides a data transmission method, a communication device, and a computer-readable storage medium. When an AIoT device or reader sends a data packet to a CN, it can simultaneously send the segmentation status of the data packet. The segmentation status indicates whether the data packet is segmented, thereby improving the data segmentation scheme between the AIoT device or reader and the CN and enhancing the transmission efficiency of AIoT services.

[0143] Based on the above description, the data transmission method provided by the embodiments of this application will be described in detail below with reference to Embodiment 1 in Figure 10, Embodiment 2 in Figure 11, and Embodiment 3 in Figure 12. This method can be applied to the Internet of Things in the environment.

[0144] Example 1: The reader sends data to the CN.

[0145] The reader can include the RAN (AIoT RAN), or the RAN and intermediate nodes. The case where the reader includes the RAN is applicable to the protocol stack architectures shown in Figures 3 and 4. The case where the reader includes the RAN and intermediate nodes is applicable to the protocol stack architectures shown in Figures 5 and 6.

[0146] CN can include at least one of AMF, AIOTF, NEF, and UPF.

[0147] Referring to the description in Figure 9, the reader can receive data packets from the AIoT device. If the AIoT device does not perform segmentation processing, the reader receives a complete data packet from the AIoT device at once, which can be referred to as the first data packet in this embodiment. If the AIoT device performs segmentation processing, the reader will receive multiple data packets from the AIoT device in multiple sessions. In this embodiment, these multiple data packets can be referred to as multiple second data packets, and the complete data packet composed of the multiple second data packets is the aforementioned first data packet.

[0148] As can be seen from the description in Figure 7, the object of segmentation processing can be AIoT service data packets in the AIoT upper layer, or it can be a NAS PDU in the NAS layer. Therefore, the first data packet may be an AIoT service data packet or a NAS PDU. This application does not specifically limit the type of the first data packet.

[0149] If the reader receives the first data packet from the AIoT device, it can send the complete data packet to the CN. If the reader receives multiple second data packets from the AIoT device, it can send all of them to the CN at once or send them in multiple installments. Figure 10 below illustrates this in detail using the example of the reader sending the first data packet to the CN at once.

[0150] Please refer to Figure 10, which shows a schematic flowchart of a data transmission method provided in an embodiment of this application.

[0151] As shown in Figure 10, the method illustrated in Figure 10 may include steps S501 to S503. The various steps of this method are described in detail below with reference to Figure 10. The method includes:

[0152] S501, the reader sends a first message to the CN, the first message including first segment information.

[0153] The first message can be encapsulated using NGAP signaling. The first segmentation information includes the segmentation status of the first data packet, indicating whether the first message contains a first data packet or a second data packet. The first segmentation information can be at least one of the following: a first segmentation indication, a first segmentation number, or N second data packets (N greater than 1), specifically, it can include at least one of the following: Case 1, Case 2, and Case 3. That is, the first segmentation information can include Case 1, Case 2, Case 3, Case 1+Case 2, Case 1+Case 2+Case 3, Case 1+Case 3, and Case 3+Case 2; this application does not limit the specific nature of the first segmentation information.

[0154] Case 1: The first segment information includes a first segmentation indication. The first segmentation indication is used to indicate that the data packet corresponding to the first message is either the second data packet or the first data packet. The second data packet is a data packet obtained by segmenting the first data packet.

[0155] For example, the first segmentation indication includes a segmentation identifier. If the segmentation identifier is 1, it means that the data packet corresponding to the first message is the second data packet, that is, the first data packet has been segmented. If the segmentation identifier is 0, it means that the data packet corresponding to the first message is the first data packet, that is, the first data packet has not been segmented.

[0156] For case 1, the first message also includes N second data packets, where N is 1 or an integer greater than 1. If the first segmentation indicator is used to indicate that the first data packet has been segmented, the first message also includes multiple second data packets. If the first segmentation indicator is used to indicate that the first data packet has not been segmented, the first message includes 1 second data packet, which is the same as the first data packet and corresponds to the complete data.

[0157] For example, the first message includes a first data packet and a first segmentation indication. The first segmentation indication is a segmentation identifier, and the segmentation identifier is 1. The first data packet includes three second data packets, namely Segment1, Segment2, and Segment3.

[0158] Case 2: The first segment information includes the first segment number, which is used to indicate the position of the second data packet in the first data packet.

[0159] For example, the first data packet includes three second data packets, with the first segment numbers being sequence number 1, sequence number 2, and sequence number 3, respectively.

[0160] For scenario 2, the first message may also include N second data packets, which can be reassembled into a first data packet, where N is 1 or an integer greater than 1. If the number of first segment numbers is 1, then the first data packet includes 1 second data packet, which is either the first data packet or a segment of the first data packet. Optionally, if the first segment number is 0 or a special value, then the second data packet is the first data packet; otherwise, the second data packet is a segment of the first data packet.

[0161] For example, the first segment information included in the first message is the first segment number. Taking the first data packet as an example, which includes three second data packets, namely data packet A, data packet B, and data packet C, the corresponding first segment numbers can be sequence number 1, sequence number 2, and sequence number 3.

[0162] When Case 2 is combined with Case 1, the first segment information includes the first segment indicator and the first segment number.

[0163] Optionally, in cases 1 and 2, the first message may include N second data packets or only one second data packet. For example, when only one second data packet is included, the CN can reassemble the data packets from multiple first messages. For instance, if each first message includes one second data packet, and the first segment indication is a segment, or the first segment number is a valid value, then the CN reassembles the data packet based on the first segment information to obtain the first data packet.

[0164] Case 3: The first segment information includes N second data packets.

[0165] In this context, each of the N second data packets represents a segment. If the value of N is 1, it means that the first data packet is not segmented and corresponds to complete data. If the value of N is greater than 1, it means that the first data packet has been segmented.

[0166] For example, if the value of N is 3, it means that the first data packet includes 3 second data packets.

[0167] In cases where Case 3 and Case 2 are combined with Case 1, the first segment information includes N second data packets, a first segment indication, and a first segment number. In cases where Case 3 is combined with Case 1, the first segment information includes N second data packets and a first segment indication. In cases where Case 3 is combined with Case 2, the first segment information includes N second data packets and a first segment number.

[0168] In addition, the first message may also include at least one of the following: a service identifier, an AIoT device identifier, a CN identifier, and a reader identifier. The service identifier may include a transaction ID and / or a correlation ID.

[0169] The service identifier is used to indicate the service corresponding to the first data packet; for example, the service identifier indicates that the first data packet is the data packet corresponding to the AIoT device performing disk storage, reading, writing or temperature acquisition services.

[0170] The device identifier of the AIoT device is used to uniquely identify the AIoT device. The CN identifier is used to uniquely identify the destination CN of the reader sending the first message. The reader identifier is used to uniquely identify the reader that sent the first message.

[0171] The following explanation uses NAS PDU as the second data packet, RAN as the reader, and AIoTF as the CN as the example. The first message can be represented by NAS-PDU List or NAS-PDU Segment List to show the first segment information and the list of the second data packet. Figure 1 illustrates this using NAS-PDU Segment List. The first message can also include message type, AIoTF ID (AIoTF UE NGAP ID), RAN ID (RAN UE NGAP ID), and user location information.

[0172] Table 1 shows the information sent by the RAN to the AIoTF in the first segment.

[0173] In Table 1, "M" in the existence section indicates that the field must appear in the first segment information.

[0174] Taking the case where the first data packet includes two second data packets, i.e., there are 2 NAS-PDUs, the NAS-PDU Segment List can be represented as follows:

[0175] Method 1 corresponds to Case 3. The first segment information in the first message includes N second data packets, that is, it includes 2 second data packets. In other words, the NAS-PDU Segment List includes: NAS-PDU1 and NAS-PDU2.

[0176] Method 2, corresponding to Case 2 + Case 3, the first message includes the first segment information and the second data packet. The first segment information is the first segment number. There are 2 second data packets, and both second data packets have the first segment number. That is, the NAS-PDU Segment List includes: sequence number 1 (first segment number) NAS-PDU1 and sequence number 2 NAS-PDU2.

[0177] Method 3 corresponds to Case 1 + Case 3. The first message includes the first segment information and the second data packet. The first segment information is the first segment indicator. The second data packet has two parts. The NAS-PDU Segment List includes: Seg Indicator (first segment indicator), NAS-PDU1, and NAS-PDU2.

[0178] It should be noted that each second data packet in the first message corresponds to a first segment information, or one first segment information in the first message can correspond to multiple second data packets.

[0179] Furthermore, as illustrated in Table 2, the second data packet can be a NAS PDU as shown below. When the first data packet is a NAS PDU, the reader can also encapsulate the segmented NAS PDU into containers, with each container being a second data packet.

[0180] Table 2. A NAS PDU

[0181] It should be noted that the first message may include multiple first data packets. Each first data packet may be segmented or not segmented. Therefore, the first data packet may be in the form of a data packet list. Each item in the data packet list may include the second data packet corresponding to each first data packet and the first segment information.

[0182] For example, each item in the data list may include: first segmentation indication, NAS-PDU segment / NAS-PDU Segment List. For example, the NAS-PDU segment / NAS-PDU Segment List may include: NAS-PDU1, NAS-PDU2.

[0183] It should be noted that in this embodiment, the second data packet is a NAS-PDU, which is applicable to scenarios where the segmentation object is an AIoT upper layer data packet. If the segmentation object is a NAS PDU, each second data packet included in the NAS-PDU segment / list in this embodiment may be other forms of data, such as a container-type data packet.

[0184] In addition, the second data packet included in the first message in this application is all segments of the first data packet. Optionally, the second data packet in the first message may also be a partial segment of the first data packet.

[0185] S502 and CN send the first response message to the reader.

[0186] The first response message indicates that CN has received the first message sent by the reader.

[0187] S503 and CN perform data reorganization.

[0188] Based on the description in S501, the first segment information received by the CN may be at least one of Case 1, Case 2, and Case 3.

[0189] If the first segment information in the first message received by the CN is Case 1, that is, the first segment information includes a first segmentation indication, and the first segmentation indication indicates that the first message contains a second data packet, meaning the first data packet has been segmented, then the CN needs to reassemble multiple second data packets to obtain the first data packet. During data reassembly, the multiple second data packets can be reassembled according to their order of arrangement in the first data packet; if the first segmentation indication indicates that no segmentation has been performed, the CN does not need to perform data reassembly.

[0190] For example, the first segmentation indicator is segmentation identifier 1, and the first data packet includes three second data packets, namely Segment1, Segment2, and Segment3. CN reassembles the data according to the order of Segment1, Segment2, and Segment3 in the first data packet.

[0191] If the first segment information in the first message received by the CN is Case 2, that is, the first segment information includes the first segment number, and if there are multiple first segment numbers or a valid segment number, it means that segmentation processing has been performed, and the CN needs to reassemble the multiple second data packets in the first data packet according to the first segment number; if there is only one first segment number or an invalid segment number, it means that segmentation processing has not been performed, and the CN does not need to perform data reassembly operation.

[0192] For example, the first message includes three second data packets, namely Segment1, Segment2, and Segment3. The first segment numbers of the three second data packets are sequence number 1, sequence number 2, and sequence number 3, respectively. The CN can reassemble the data of Segment1, Segment2, and Segment3 in the order of sequence number 1, sequence number 2, and sequence number 3.

[0193] For example, if a first message includes one second data packet, designated Segment 1, and the data number is a valid number (i.e., the value indicating the segment), the CN can reassemble the second data packets from multiple received first messages sequentially according to the number. The specific determination method can be one or more of the following: identical service numbers, identical device identifiers, or complete sequence numbers.

[0194] If the first segment information in the first message received by CN is case 3, that is, the first segment information includes N second data packets, and the value of N is greater than 1, CN needs to reassemble multiple second data packets. During data reassembly, the data can be reassembled according to the order in which the multiple second data packets are arranged in the first message; alternatively, when the value of N is equal to 1, CN does not need to perform data reassembly operation.

[0195] For example, the first data packet includes three second data packets, namely Segment1, Segment2, and Segment3. CN reassembles the data according to the order of Segment1, Segment2, and Segment3.

[0196] Similarly, if the first segment information in the first message is Case 1 + Case 2, Case 1 + Case 2 + Case 3, Case 1 + Case 3, or Case 2 + Case 3, CN can refer to the above process to perform the reorganization operation according to the actual situation, or not perform the reorganization operation. This application will not elaborate on this in detail here.

[0197] It should be noted that if the reader includes intermediate nodes and the RAN, in the second method, the intermediate nodes need to send an RRC message to the RAN, and the RRC message also needs to include the first segment information mentioned above.

[0198] Furthermore, in Embodiment 1, the example of the reader sending the first data packet to the CN in one go is used for specific illustration. If the first data packet received by the reader from the AIoT device includes multiple second data packets, the reader can also send multiple second data packets in the first data packet to the CN in multiple installments (receive once from the AIoT device and send once to the CN). If the reader sends multiple second data packets included in the first data packet to the CN in multiple installments, the method shown in Embodiment 2 below can be adopted, that is, send multiple second data packets in the first data packet to the CN in sequence. Each installment needs to include the first segment information, which will not be described in detail here.

[0199] In this embodiment, the reader can notify the CN of the segmentation status of the first data packet through at least one of the first segmentation indication, the first segmentation number, and multiple second data packets. This enables the CN to reassemble the received second data packets, which can improve the segmentation solution for AIoT service data packets. Furthermore, transmitting data packets through segmentation and reassembly can avoid transmission delays caused by excessive data volume, thereby improving the efficiency of AIoT service transmission.

[0200] It should be noted that the segmentation information can be added on either the reader side or the AIoT device side. If added on the reader side, the AIoT device can send the complete first data packet or multiple second data packets obtained from the segmentation to the reader. The reader then adds the first segmentation information and sends it to the CN. For details, please refer to the scheme in Embodiment 1. If added on the AIoT device side, the AIoT device can directly add the second segmentation information and then send the multiple second data packets obtained from the segmentation or the complete first data packet to the reader. The reader then sends it to the CN. For details, please refer to the scheme in Embodiment 2. In Embodiment 2, it is simplified to say that the AIoT device can directly add the second segmentation information and then send the multiple second data packets obtained from the segmentation or the complete first data packet to the CN.

[0201] Example 2: The AIoT device sends data to the CN.

[0202] CN can include at least one of AMF, AIOTF, NEF, and UPF.

[0203] Referring to the description in Figure 9, the AIoT device may or may not segment the data packets. If the AIoT device does not segment the data packets, it can directly send the complete data packet to the CN, which can be called the first data packet. If the AIoT device segments the first data packet to obtain multiple second data packets, it can send the second data packets to the CN in multiple sessions.

[0204] As can be seen from the description in Figure 7, the object performing segmentation processing in the AIoT device may be an AIoT service data packet in the AIoT upper layer or a NAS PDU in the NAS layer. Therefore, the first data packet may be an AIoT service data packet or a NAS PDU. This application does not specifically limit the type of the first data packet.

[0205] Please refer to Figure 11, which shows a schematic flowchart of a data transmission method provided in an embodiment of this application.

[0206] As shown in Figure 11, the method illustrated in Figure 11 may include steps S601 to S602. The various steps of this method are described in detail below with reference to Figure 11. The method includes:

[0207] S601, the AIoT device sends a second message to the CN, which includes second segment information.

[0208] The second message can be a NAS message, and the number of second messages is related to the number of segments in the first data packet.

[0209] The following example illustrates how a complete first data packet includes three second data packets, namely data packet A, data packet B, and data packet C, and correspondingly, multiple second messages are three NAS messages. The three NAS messages are the first NAS message, the second NAS message, and the third NAS message, and data packets A, B, and C correspond one-to-one with the first NAS message, the second NAS message, and the third NAS message, respectively.

[0210] S6011, the AIoT device sends the first NAS message to the CN.

[0211] The first NAS message includes second segment information, which may include at least one of Case 1 and Case 2 below. That is, the second segment information may include Case 1, Case 2, or Case 1 + Case 2; this application does not limit the specific circumstances of the second segment information.

[0212] Case 1: The second segmentation information includes a second segmentation indication, which indicates that data packet A is segmented data, or that data packet A is an incomplete first data packet, or that data packet A is a second data packet.

[0213] For example, if the second segmentation indication includes a segmentation identifier, and the segmentation identifier is 1, it indicates that data packet A is segmented data, or data packet A is an incomplete first data packet.

[0214] For case 1, the first NAS message also includes data packet A.

[0215] Case 2: The second segment information includes the second segment number, which is used to indicate the position of data packet A in the first data packet.

[0216] For case 2, the first NAS message also includes data packet A.

[0217] For example, the second segment number of data packet A can be sequence number 1.

[0218] S6012, the AIoT device sends a second NAS message to the CN.

[0219] S6013, the AIoT device sends a third NAS message to the CN.

[0220] S6012 and S6013 are implemented similarly to S6011, and will not be described in detail here. During implementation, when the reader receives the first NAS message, the second NAS message, and the third NAS message, the reader can send them to the CN separately, or aggregate them and send them to the CN; there is no restriction on this.

[0221] S602, CN receives the second message, and CN reassembles the data based on the second message.

[0222] Based on the above description, the AIoT device can send multiple second messages to the CN in sequence. If the second segment information in each second message includes a second segment indication, the CN can reassemble the data in the order of receiving the second data packets in each second message when performing data reassembly. If the second segment information in each second message includes a second segment number, the CN can reassemble the data in the order of receiving the second data packets in each second message when performing data reassembly.

[0223] For example, the first data packet includes three second data packets, namely Segment1, Segment2, and Segment3. Each second data packet in each second message has a segment number, namely SN1 Segment1, SN2 Segment2, and SN3 Segment3. Then, CN can reassemble the data of Segment1, Segment2, and Segment3 according to the number SN1, SN2, and SN3.

[0224] Furthermore, if the AIoT device does not segment the first data packet, the AIoT device sends a second message to the CN. The second message includes the complete first data packet, or the second message includes second indication information. The second segmentation indication and / or the second segmentation number in the second indication information indicate the unsegmented state of the first data packet. This method is similar to the segmentation method of the first data packet described above, and will not be described in detail here. If the second message includes the complete first data packet, the CN does not need to perform a reassembly operation.

[0225] It should be noted that the AIoT device can also send its permanent or temporary device identifier to the CN. Optionally, the AIoT device also needs to send encryption and decryption related parameters to the CN so that the CN can parse the segmented information. The interaction information between the AIoT device and the CN may also include other information, which is not specifically limited in this application.

[0226] In this embodiment, the AIoT device can sequentially send multiple second messages to the CN. Each second message may contain a segmentation indication or a segmentation number, thereby indicating the segmentation status of the first data packet to the CN. This enables the CN to reassemble the received second data packet, thus improving the segmentation solution for AIoT application layer data packets. Furthermore, transmitting data packets through segmentation and reassembly can avoid transmission delays caused by excessive data volume, thereby improving the efficiency of AIoT service transmission.

[0227] Example 3: CN indicates to the reader the CN's segmentation capability or the situation where the reader is allowed to segment.

[0228] Based on the descriptions of Embodiment 1 in Figure 10 and Embodiment 2 in Figure 11, it can be seen that the CN can reassemble segmented data packets. Therefore, the CN usually also has the ability to segment, which can also be called the reassembly capability.

[0229] Please refer to Figure 12, which shows a schematic flowchart of a data transmission method provided in an embodiment of this application.

[0230] As shown in Figure 12, the method illustrated in Figure 12 may include steps S701 to S702. The various steps of this method are described in detail below with reference to Figure 12. The method includes:

[0231] S701 and CN send a third message to the reader, which includes segmentation indication information.

[0232] The segmentation indication information is used to indicate that the CN has segmentation capability and / or the number of segments that the CN can support.

[0233] The CN can send a third message to the reader at any time, depending on the specific implementation of the CN. This application does not specify the time when the CN sends a third message to the reader.

[0234] The segmentation indication information may include first indication information, which may include at least one of the following: segmentation capability indication and segmentation quantity indication. This application does not specifically limit the specific circumstances of the first indication information.

[0235] The first indication information includes a segmentation capability indication, which indicates that the CN supports data segmentation (which can be understood as the CN supporting data reassembly), or that the CN supports segmentation of the first service, or that the CN supports the reader to perform segmentation.

[0236] It should be understood that when a CN performs data reassembly, it needs to consume certain storage resources to store the second data packet that needs to be reassembled. If the current storage space of the CN's memory is greater than or equal to the storage threshold, the CN can support data reassembly and can send a segmentation capability indication to the reader. If the current storage space of the CN's memory is less than the storage threshold, the CN will not support data reassembly and may not send a segmentation capability indication to the reader.

[0237] The first service is the currently ongoing AIoT service, specifically the AIoT service indicated by the CN when sending the third message, i.e., the third message contains the service identifier. The first service can be any service, and this application does not limit the specific type of the first service. For example, the first service can be a device inventory operation, or it can be a temperature data acquisition service. Exemplarily, when the CN receives a temperature acquisition request from the AF end, if the current storage space of the CN's memory is greater than or equal to the storage threshold, the CN can support data reassembly. The CN can send a segmentation capability indication to the reader, indicating that the CN supports segmenting the response data packet of the temperature acquisition request.

[0238] The first indication information includes a segmentation number indication, which indicates the number of segments that the CN allows the reader to segment the target data packet into.

[0239] S702, the reader sends a second response message to CN.

[0240] The second response message indicates that the reader has received the third message sent by the CN.

[0241] Optionally, the CN may have the ability to send an expected feedback size to the reader. If the CN sends an expected feedback size to the reader, it implicitly instructs the CN not to allow the reader to segment the feedback. The CN can send the expected feedback size to the reader at any time, depending on the specific implementation of the CN. This application does not impose a specific limitation on the timing of the CN sending the expected feedback size to the reader.

[0242] For example, if the expected feedback size is 100 bits, the reader can schedule resources that allow the device to send data packets exceeding 100 bits. In this case, the reader does not need to segment the feedback.

[0243] Furthermore, before the CN sends a third message to the reader, it may also include: the CN acquiring the segmentation capability of the AIoT device and / or the segmentation capability of the reader. Typically, the AIoT device performs data segmentation, and the reader's segmentation capability can be understood as the ability to assist the device in segmentation, such as: indicating the amount of segmented data received, supporting segmented retransmission, and / or the ability to indicate segmentation to the CN, etc.

[0244] If the reader has segmentation capability, the CN can send segmentation indication information to the reader; if the reader does not have segmentation capability, the CN will not send segmentation indication information to the reader. If the AIoT device has segmentation capability, the CN can send segmentation indication information to the reader; if the reader does not have segmentation capability, the CN will not send segmentation indication information to the reader.

[0245] In this embodiment, CN sends a segmentation indication capability or a segmentation number indication to the reader to indicate whether the reader can perform the segmentation function, thereby assisting the reader in efficiently scheduling AIoT devices and avoiding unnecessary segmentation behavior.

[0246] It should be noted that when the segmentation function is executed at the NAS layer: the NAS layer can segment the received AIoT upper layer packet and then encapsulate it into a NAS PDU before submitting it to the lower layer; or the NAS upper layer can encapsulate the AIoT upper layer packets into a NAS PDU before segmenting them and then submitting them to the lower layer.

[0247] Furthermore, the embodiments of this application can also be applied to non-AIoT scenarios, such as 6G or subsequent evolved communication technologies.

[0248] The method embodiments of this application have been described in detail above with reference to Figures 1 to 12. The apparatus embodiments of this application will be described below with reference to Figures 13 to 15. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0249] Figure 13 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 13, the communication device 1300 includes a receiving module 1301 and a transmitting module 1302.

[0250] In one possible implementation, the device 1300 can be used to perform the steps described above by the first device.

[0251] The sending module 1302 is used to: send a first message, the first message including first segmentation information, the first segmentation information being used to indicate that the data packet corresponding to the first message is a second data packet, and the second data packet is a data packet obtained by segmenting the first data packet.

[0252] In some implementations, the first segment information includes at least one of the following: a first segment indication, which indicates that the data packet corresponding to the first message is the second data packet; and a first segment number, which is the number of the second data packet and indicates the position of the second data packet in the first data packet.

[0253] In some implementations, the first message also includes N second data packets, where N is an integer greater than 1.

[0254] In some implementations, the first message also includes a second data packet.

[0255] In some implementations, the first data packet is a Non-Access Stratum Protocol Data Unit (NAS PDU) or an AIoT (Artificial Intelligence of Things) service data packet.

[0256] In some implementations, the second data packet is a NAS PDU or a container.

[0257] In some implementations, when the first segment number is the first value, the second data packet is the first data packet.

[0258] In some implementations, the first message also includes a service identifier and a device identifier of the first device, wherein the service identifier is used to indicate the AIoT service corresponding to the second data packet.

[0259] In some implementations, the receiving module 1301 is further configured to: receive a third message, the third message including first indication information, the first indication information being used to indicate the segmentation capability of the second device.

[0260] In some implementations, the first indication information includes at least one of the following: segmentation capability indication, which indicates that the second device supports data segmentation; and segmentation quantity indication, which indicates the number of data segments that the second device supports.

[0261] In some implementations, the third message also includes: a service identifier; the service identifier is used to indicate the service segments allowed by the second device.

[0262] Figure 14 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 14, the communication device 1400 includes a receiving module 1401 and a transmitting module 1402.

[0263] In one possible implementation, the device 1400 can be used to perform the steps described above by the second device.

[0264] The receiving module 1401 is used to: receive a first message, the first message including first segmentation information, the first segmentation information being used to indicate that the data packet corresponding to the first message is a second data packet, and the second data packet is a data packet obtained by segmenting the first data packet.

[0265] In some implementations, the first segment information includes at least one of the following: a first segment indication, which indicates that the data packet corresponding to the first message is the second data packet; and a first segment number, which is the number of the second data packet and indicates the position of the second data packet in the first data packet.

[0266] In some implementations, the communication device 1400 further includes a reassembly module 1403, and the first message further includes N second data packets, where N is an integer greater than 1; the reassembly module 1403 is used to: if the first segmentation information includes a first segmentation indication, reassemble the N second data packets according to the order in which each second data packet is arranged in the first data packet; if the first segmentation information includes a first segmentation number, reassemble the N second data packets according to the position of each second data packet in the first data packet.

[0267] In some implementations, the first message also includes N second data packets, where N is an integer greater than 1.

[0268] In some implementations, the first data packet is a NAS PDU or an AIoT service data packet.

[0269] In some implementations, the second data packet is a NAS PDU or a container.

[0270] In some implementations, when the first segment number is the first value, the second data packet is the first data packet.

[0271] In some implementations, the first message also includes a service identifier and a device identifier of the first device, wherein the service identifier is used to indicate the AIoT service corresponding to the second data packet.

[0272] In some implementations, the sending module 1402 is used to: send a third message, the third message including first indication information, the first indication information being used to indicate the segmentation capability of the second device.

[0273] In some implementations, the first indication information includes at least one of the following: segmentation capability indication, which indicates that the second device supports data segmentation; and segmentation quantity indication, which indicates the number of data segments that the second device supports.

[0274] In some implementations, the communication device 1400 further includes an acquisition module 1404. Before sending the first instruction information, the acquisition module 1404 is used to: acquire the first capability of the first device, wherein the first capability is the segmentation capability of the first device.

[0275] It should be understood that devices 1300 and 1400 are embodied in the form of functional modules. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors, etc.) and memories for executing one or more software or firmware programs, integrated logic circuits, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that device 1300 may be specifically the first device in the above embodiments, and device 1300 may be used to perform the various processes and / or steps corresponding to the first device in the above method embodiments. Device 1400 may be specifically the second device in the above embodiments, and device 1400 may be used to perform the various processes and / or steps corresponding to the second device in the above method embodiments. To avoid repetition, further details are omitted here.

[0276] The aforementioned device 1300 has the function of implementing the corresponding steps performed by the first device in the aforementioned method, and the device 1400 has the function of implementing the corresponding steps performed by the Internet of Things (IoT) device in the aforementioned method. These functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions.

[0277] In embodiments of this application, devices 1300 and 1400 may also be chips, such as a system-on-a-chip (SOC) or a modem. Correspondingly, the receiving module and the transmitting module may be the transceiver circuits of the chip, and are not limited herein.

[0278] Figure 15 is a schematic structural diagram of a communication device provided in an embodiment of this application. This device 1500 can be used to implement the methods described in the above method embodiments. The device 1500 can be a first device, an Internet of Things (IoT) device, or a core network. As shown in Figure 15, the communication device 1500 includes a processor 1501 and an interface circuit 1502. The processor 1501 and the interface circuit 1502 are coupled to each other. It is understood that the interface circuit 1502 can be a transceiver or an input / output interface. Optionally, the communication device 1500 may also include a memory 1503 for storing instructions executed by the processor 1501, or storing input data required by the processor 1501 to execute instructions, or storing data generated after the processor 1501 executes instructions.

[0279] When the communication device 1500 is used to implement the above method, the processor 1501 is used to implement the functions of the above-mentioned reassembly module and acquisition module, and the interface circuit 1502 is used to implement the functions of the above-mentioned sending module and / or receiving module.

[0280] When the aforementioned communication device is a chip applied to the first device, the chip implements the functions of the first device in the above method embodiments. The chip receiving information from the second device can be understood as the information being first received by other modules (such as an RF module or antenna) in the first device, and then sent to the chip by these modules. The chip sending information to the second device can be understood as the information being first sent to other modules (such as an RF module or antenna) in the first device, and then sent to the second device by these modules.

[0281] When the aforementioned communication device is a chip applied to the second device, the chip implements the functions of the second device in the above method embodiments. The chip receives information from the first device, which can be understood as the information being first received by other modules (such as an RF module or antenna) in the second device, and then sent to the chip by these modules. The chip sends information to the first device, which can be understood as the information being sent down to other modules (such as an RF module or antenna) in the second device, and then sent back to the first device by these modules.

[0282] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a first or second device provided in this application, and the program causes a computer to perform the methods executed by the first or second device in various embodiments of this application.

[0283] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the first device or the second device provided in the embodiments of this application, and the program causes a computer to perform the methods executed by the first device or the second device in various embodiments of this application.

[0284] This application also provides a computer program. This computer program can be applied to the first or second device provided in this application, and causes the computer to perform the methods executed by the first or second device in various embodiments of this application.

[0285] This application also provides a communication system, which may include a first device or a second device.

[0286] It should be understood that in the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0287] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0288] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0289] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be RAN nodes or terminals, or modules within RAN nodes or terminals. Information transmission and reception can be between RAN nodes and terminals, such as between a base station and a terminal; between two RAN nodes, such as between a CU and a DU; or between different modules within a single device, such as between a terminal chip and other modules of the terminal, or between a base station chip and other modules of the base station.

[0290] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0292] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0293] 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 instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0294] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A data transmission method, characterized in that, The method is applied to a first device, and the method includes: Send a first message, the first message including first segmentation information, the first segmentation information being used to indicate that the data packet corresponding to the first message is a second data packet, the second data packet being a data packet obtained by segmenting the first data packet.

2. The method according to claim 1, characterized in that, The first segmentation information includes at least one of the following: The first segmentation indication is used to indicate that the data packet corresponding to the first message is the second data packet; The first segment number is the number of the second data packet, and the first segment number is used to indicate the position of the second data packet in the first data packet.

3. The method according to claim 1 or 2, characterized in that, The first message also includes N second data packets, where N is an integer greater than 1.

4. The method according to claim 2, characterized in that, The first message also includes one second data packet.

5. The method according to any one of claims 1 to 4, characterized in that, The first data packet is a Non-Access Layer Protocol Data Unit (NAS PDU) or an AIoT (Artificial Intelligence of Things) service data packet.

6. The method according to any one of claims 1 to 5, characterized in that, The second data packet is a NAS PDU or a container.

7. The method according to claim 4, characterized in that, When the first segment number is a first value, the second data packet is the first data packet.

8. The method according to any one of claims 1 to 7, characterized in that, The first message also includes a service identifier and a device identifier of the first device, wherein the service identifier is used to indicate the AIoT service corresponding to the second data packet.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: A third message is received, the third message including first indication information, the first indication information being used to indicate the segmentation capability of the second device.

10. The method according to claim 9, characterized in that, The first indication information includes at least one of the following: Segmentation capability indication, wherein the segmentation capability indication is used to indicate that the second device supports data segmentation; Segment Count Indicator, which indicates the number of data segments the second device supports.

11. The method according to claim 9 or 10, characterized in that, The third message also includes: Service identifier; the service identifier is used to indicate the service segments allowed by the second device.

12. A data transmission method, characterized in that, The method is applied to a second device, and the method includes: A first message is received, the first message including first segmentation information, the first segmentation information being used to indicate that the data packet corresponding to the first message is a second data packet, the second data packet being a data packet obtained by segmenting the first data packet.

13. The method according to claim 12, characterized in that, The first segmentation information includes at least one of the following: The first segmentation indication is used to indicate that the data packet corresponding to the first message is the second data packet; The first segment number is the number of the second data packet, and the first segment number is used to indicate the position of the second data packet in the first data packet.

14. The method according to claim 13, characterized in that, The first message also includes N second data packets, where N is an integer greater than 1; the method further includes: If the first segmentation information includes the first segmentation indication, the N second data packets are reassembled according to the arrangement order of each second data packet in the first data packet; If the first segmentation information includes the first segmentation number, the N second data packets are reassembled according to the position of each second data packet in the first data packet.

15. The method according to claim 13, characterized in that, The first message also includes N second data packets, where N is an integer greater than 1.

16. The method according to any one of claims 12 to 15, characterized in that, The first data packet is a NAS PDU or an AIoT service data packet.

17. The method according to any one of claims 12 to 16, characterized in that, The second data packet is a NAS PDU or a container.

18. The method according to claim 13, characterized in that, When the first segment number is a first value, the second data packet is the first data packet.

19. The method according to any one of claims 12 to 18, characterized in that, The first message also includes a service identifier and a device identifier of the first device, wherein the service identifier is used to indicate the AIoT service corresponding to the second data packet.

20. The method according to any one of claims 12 to 19, characterized in that, The method further includes: A third message is sent, which includes first indication information, which is used to indicate the segmentation capability of the second device.

21. The method according to claim 20, characterized in that, The first indication information includes at least one of the following: Segmentation capability indication, wherein the segmentation capability indication is used to indicate that the second device supports data segmentation; Segment Count Indicator, which indicates the number of data segments the second device supports.

22. The method according to claim 20 or 21, characterized in that, Before sending the third message, the method further includes: Obtain the first capability of the first device, wherein the first capability is the segmentation capability of the first device.

23. A communication device, characterized in that, The device includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices and transmit them to the processor or to send signals from the processor to other communication devices, and the processor is used to implement the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 22, through logic circuits or execution code instructions.

24. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 22.

Images