Communication method and apparatus

Abstract

The present application relates to the technical field of communications, and provides a communication method and an apparatus. The method comprises: determining a first length, wherein the first length is the length of first data; on the basis of the first length, determining to transmit the first data through a first mode or a second mode; and when it is determined to transmit the first data through the first mode, transmitting the first data by means of a first message, or when it is determined to transmit the first data through the second mode, transmitting the first data by means of a second message and a third message.

Description

Communication method and apparatus

[0001] The present application claims priority from the Chinese patent application No. 202411103808.2 filed on August 9, 2024, and entitled "A communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication, and in particular to a communication method and apparatus. BACKGROUND

[0003] With the development of communication technology, the 3rd generation partnership project (3GPP) defines ambient IoT (A-IoT). A-IoT terminals communicate with the network by obtaining energy from the environment to achieve passive IoT communication. However, more scenarios of business processes will be introduced in 3GPP, such as warehouse / transportation / stocktaking, fixed asset management, etc. In these business processes, A-IoT terminals need to transmit data with the network, and the amount of data transmitted may differ due to different business processes.

[0004] Therefore, in the case of different amounts of data transmission, how to ensure the efficiency and reliability of data transmission is a problem to be studied at present. SUMMARY

[0005] To solve the above technical problems, the embodiments of the present application provide a communication method and apparatus to ensure the efficiency and reliability of data transmission in the case of different amounts of data interaction.

[0006] To achieve the above object, the present application adopts the following technical solutions:

[0007] In a first aspect, a communication method is provided. The method is applied to a first device. The method comprises: determining a first length, the first length being a length of first data. According to the first length, determining whether to transmit the first data by a first mode or a second mode; in a case of determining to transmit the first data by the first mode, transmitting the first data by a first message; or in a case of determining to transmit the first data by the second mode, transmitting the first data by a second message and a third message.

[0008] Therefore, in the case that the first length of the first data is different, or the data amount of the first data is different, the first data can be transmitted in different modes. For example, if the first length is relatively small, the first device can transmit the first data in the first mode, such as through the first message, to ensure the efficiency of data transmission. If the first length is relatively large, the first device can transmit the first data in the second mode, such as through the second message and the third message, to avoid transmission failure due to the first message being unable to transmit the first data, and thus to ensure the reliability of data transmission.

[0009] In a first possible design, determining the first length includes: receiving the first data, and determining the first length according to the first data. That is, in the case that the first device transmits the first data, the first service request can first receive the first data to directly determine the first length. Compared with the manner of obtaining the first length from other devices, the first device can avoid the overhead caused by interaction with other devices.

[0010] It should be understood that, in the first possible design, the first device can be a core network element, such as an A-IoT MF, or other network elements with A-IoT functions, and the specific name is not limited. Alternatively, the first device can also be an access network device, such as an access network device supporting a reader function, or a terminal device, such as a terminal device supporting a reader function, and thus the first device can also be regarded as a reader. Correspondingly, the second device can be a terminal device, such as an A-IoT terminal.

[0011] Optionally, receiving the first data includes: receiving the first service request. The first service request includes the first data, and the first service request is used to request writing the first data to the second device, that is, applicable to a writing scenario, to implement efficient and reliable writing of the first data to the second device.

[0012] Optionally, in the case that it is determined to transmit the first data in the first mode, transmitting the first data in the first message includes: in the case that it is determined to transmit the first data in the first mode, sending the first message to the second device, the first message including the first data. Alternatively, in the case that it is determined to transmit the first data in the second mode, transmitting the first data in the second message and the third message includes: in the case that it is determined to transmit the first data in the second mode, sending the second message and the third message to the second device, the second message including the second data, the third message including the third data, and the first data including the second data and the third data.

[0013] As can be seen, the first data can be directly carried in the first message, or can be segmented, such as obtaining the second data and the third data, and carried in the second message and the third message respectively. The specific selection can be made according to the data amount of the first data, that is, the first length, to ensure the efficiency and reliability of data transmission.

[0014] Optionally, the method of the first aspect can further comprise: determining the second data and the third data according to the first data, i.e., the first data can be segmented to be carried into the corresponding messages respectively.

[0015] Optionally, the method of the first aspect can further comprise: sending the first address to the second device, the first address indicating the storage region storing the first data, so that the second device can write the first data into the specified storage region according to the first address. Alternatively, the second address and the third address are sent to the second device, the second address indicating the region storing the second data, and the third address indicating the region storing the third data. The second address and the third address can be segmented from the first address, and specifically can be continuous addresses or non-continuous addresses, without limitation, so as to enable the second data and the third data to be written flexibly.

[0016] In the second possible design, the first length is determined by: obtaining the first length from the third device; or receiving the first address and determining the first length according to the first address. The first address indicates the region storing the first data. That is, the first device can determine the length of the first data in advance based on the obtained address or directly from other devices, so as to determine the mode of receiving the first data subsequently, such as receiving the first data by the first mode or the second mode.

[0017] It should be understood that, in the second possible design, the device types of the first device and the second device are similar to those in the first possible design described above, and can be understood with reference thereto, which will not be described herein again.

[0018] Optionally, obtaining the first length from the third device comprises: receiving a second service request and obtaining the first length from the third device according to the second service request. The second service request is used to request reading the first data from the second device. Optionally, receiving the first address comprises: receiving a second service request, the second service request including the first address, and the second service request being used to request reading the first data from the second device. That is, the first device can obtain the first address regardless of whether the second service request carries the first device. In addition, the above method can be applied to the reading scenario, so as to enable the first data to be read from the second device efficiently and reliably.

[0019] Optionally, in the case of determining to transmit the first data through the first mode, the first data is transmitted through the first message, comprising: in the case of determining to receive the first data through the first mode, receiving the first message from the second device, the first message comprising the first data. Alternatively, in the case of determining to transmit the first data through the second mode, the first data is transmitted through the second message and the third message, comprising: in the case of determining to receive the first data through the second mode, receiving the second message and the third message from the second device, the second message comprising the second data, the third message comprising the third data, and the first data comprising the second data and the third data.

[0020] Optionally, after receiving the first message of the second message and the third message, the method of the first aspect can further comprise: sending first indication information to the second device, the first indication information indicating whether the second device continues to send data, that is, whether the second device continues to send data can be indicated by the first device, so as to avoid data transmission error and ensure the reliability and stability of data transmission.

[0021] Optionally, the method of the first aspect can further comprise: determining the first data according to the second data and the third data, that is, realizing data aggregation, so that the first device can provide complete data, i.e. the first data, to other entities / network elements on the network side after receiving segmented data through data aggregation.

[0022] Optionally, the method of the first aspect can further comprise: sending the first address to the second device, so that the second device can correctly read and send the first data according to the first address, avoiding data reading error.

[0023] In some possible solutions, the first device is a core network element, and the second device is a terminal device. In the case of determining to transmit the first data through the first mode, the access network device is configured to forward the first message. The method of the first aspect further comprises: sending second indication information to the access network device, the second indication information indicating that the access network device can continue to perform operations for other terminals after forwarding the first message. Alternatively, the first device is an access network device, and the second device is a terminal device. The method of the first aspect further comprises: continuing to perform operations for other terminals after sending the first message. That is, in the case of transmitting the first data through only the first message, the access network device does not need to wait for subsequent indication from the network side, and can continue to perform operations for other terminals, such as random access of other terminals, so as to improve operation efficiency.

[0024] In some possible solutions, the first device is a core network element, and the second device is a terminal device. In a case where it is determined to transmit the first data in the second mode, the access network device is configured to forward the second message and the third message. The method of the first aspect can further include: sending third indication information to the access network device, the third indication information indicating that the access network device needs to perform an operation on other terminals according to an indication of the core network element after forwarding a first message in the second message and the third message; or the first device is an access network device, and the second device is a terminal device. The method of the first aspect can further include: after sending a first message in the second message and the third message, the first device needs to perform an operation on other terminals according to an indication of the core network. In this way, the access network device can be prevented from performing an operation on other terminals before the first data is transmitted, so that the first data transmission is not failed, and the reliability of data transmission is ensured.

[0025] In a third possible design, the first length is determined by: receiving the first address, and determining the first length according to the first address. The first address indicates a region in which the first data is stored.

[0026] It should be understood that, in the third possible design, the first device can be a terminal device, such as an A-IoT terminal. The second device can be an access network device, such as an access network device supporting a reader function, or can also be a terminal device, such as a terminal device supporting a reader function, or be considered as a reader.

[0027] Optionally, the first address is received by: receiving a command, the command including the first address, and the command indicating that the first data is read from the first device, that is, the read scenario is applied, so as to efficiently and reliably read the first data from the first device.

[0028] Optionally, in a case where it is determined to transmit the first data in the first mode, the first data is transmitted through the first message, including: in a case where it is determined to transmit the first data in the first mode, sending the first message to the second device, the first message including the first data; or in a case where it is determined to transmit the first data in the second mode, the first data is transmitted through the second message and the third message, including: in a case where it is determined to transmit the first data in the second mode, sending the second message and the third message to the second device, the second message including the second data, the third message including the third data, and the first data including the second data and the third data.

[0029] Optionally, after sending a first message in the second message and the third message to the second device, the method of the first aspect further includes: sending fourth indication information to the second device, the fourth indication information indicating whether the first device continues to send data, that is, whether the second device needs to continue to receive data can be indicated by the first device, so as to ensure the stability and reliability of data transmission.

[0030] Optionally, the method of the first aspect further comprises: determining the second data and the third data according to the first data, i.e., segmenting the first data so as to be able to be carried by different messages respectively.

[0031] Optionally, the method of the first aspect further comprises: obtaining the first data from the first area according to the first address.

[0032] Optionally, the method of the first aspect further comprises: sending the first length to the second device, so that the second device can determine whether the first data is completely received according to the first length, so as to avoid that the second device performs other operations in the case that the first data is not completely received, resulting in failure of transmission of the first data, or the second device still waits for receiving the first data in the case that the first data is completely received, resulting in increase of time delay.

[0033] In some possible design solutions, in the case that it is determined to transmit the first data by the first mode, the first message is the first message for transmitting the service data; or, in the case that it is determined to transmit the first data by the second mode, the first message or the first message in the third message is the first message for transmitting the service data, so as to further improve transmission efficiency and reduce transmission time delay.

[0034] In some possible design solutions, determining to transmit the first data by the first mode or the second mode according to the first length comprises: if the first length is less than or equal to a length threshold, determining to transmit the first data by the first mode; or, if the first length is greater than the length threshold, determining to transmit the first data by the second mode.

[0035] Optionally, the method of the first aspect can further comprise: obtaining the length threshold from a third device, i.e., obtaining a preconfigured length threshold, without dynamic determination, so as to reduce calculation power consumption; or determining the length threshold according to quality of a link used for carrying the first data, so as to match the amount of data transmitted with the quality of the link, for example, if the quality of the link is relatively poor, the length threshold is also relatively small, so as to reduce the amount of data transmitted at a time, and ensure reliability of data transmission in the case that the quality of the link is relatively poor; for another example, if the quality of the link is relatively good, the length threshold is also relatively large, so as to increase the amount of data transmitted at a time, and ensure efficiency of data transmission.

[0036] The second aspect provides a communication device. The communication device is configured to perform the communication method in any one of the implementation manners of the first aspect.

[0037] In the present application, the communication device of the second aspect can be a terminal device or a network device, or a chip (system) or other components or assemblies, or a device containing the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0038] It should be understood that the communication apparatus in the second aspect includes corresponding modules, units or means for implementing the communication method in any of the possible implementation manners of the first aspect, which can be implemented by hardware, software or by executing corresponding software by hardware. The hardware or software includes one or more modules or units for performing functions involved in the communication method.

[0039] In a third aspect, a communication apparatus is provided. The communication apparatus includes a processor, configured to perform the communication method in any of the possible implementation manners of the first aspect.

[0040] In a possible design, the communication apparatus in the third aspect can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for the communication apparatus in the third aspect to communicate with other communication apparatuses.

[0041] In a possible design, the communication apparatus in the third aspect can further include a memory. The memory can be integrated with the processor, or can be separately arranged. The memory can be used to store a computer program and / or data involved in the communication method in any of the aspects of the first aspect.

[0042] In this application, the communication apparatus in the third aspect can be a terminal device or a network device, or a chip (system) or other components or assemblies, or an apparatus containing the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0043] In a fourth aspect, a communication apparatus is provided. The communication apparatus includes a processor coupled to a memory, and the processor is configured to execute a computer program stored in the memory, so that the communication apparatus performs the communication method in any of the possible implementation manners of the first aspect.

[0044] In a possible design, the communication apparatus in the fourth aspect can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be used for the communication apparatus in the fourth aspect to communicate with other communication apparatuses.

[0045] In this application, the communication apparatus in the fourth aspect can be a terminal device or a network device, or a chip (system) or other components or assemblies, or an apparatus containing the terminal device or the network device. The chip (system) or other components or assemblies can be arranged in the terminal device or the network device.

[0046] In a fifth aspect, a communication apparatus is provided. The communication apparatus includes a processor and a memory. The memory is configured to store a computer program. When the processor executes the computer program, the communication apparatus performs the communication method in any one of the implementation manners of the first aspect.

[0047] In a possible design, the communication apparatus in the fifth aspect can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be configured to enable the communication apparatus in the fifth aspect to communicate with another communication apparatus.

[0048] In this application, the communication apparatus in the fifth aspect can be a terminal device or a network device, or a chip (system) or other component or assembly, or an apparatus including the terminal device or the network device. The chip (system) or other component or assembly can be arranged in the terminal device or the network device.

[0049] In a sixth aspect, a communication apparatus is provided. The communication apparatus includes a processor. The processor is configured to be coupled with a memory, and to read a computer program in the memory and execute the communication method in any one of the implementation manners of the first aspect according to the computer program.

[0050] In a possible design, the communication apparatus in the sixth aspect can further include a transceiver. The transceiver can be a transceiver circuit or an interface circuit. The transceiver can be configured to enable the communication apparatus in the sixth aspect to communicate with another communication apparatus.

[0051] In this application, the communication apparatus in the sixth aspect can be a terminal device or a network device, or a chip (system) or other component or assembly, or an apparatus including the terminal device or the network device. The chip (system) or other component or assembly can be arranged in the terminal device or the network device.

[0052] In a seventh aspect, a processor is provided. The processor is configured to execute the communication method in any one of the implementation manners of the first aspect.

[0053] In an eighth aspect, a communication system is provided. The communication system includes a first apparatus and a second apparatus configured to execute the method in the first aspect.

[0054] In a ninth aspect, a computer readable storage medium is provided. The computer readable storage medium includes a computer program or instructions. When the computer program or instructions are executed, the communication method in any one of the implementation manners of the first aspect is implemented.

[0055] In a tenth aspect, a computer program product is provided, including a computer program or instructions, which when executed, cause the communication method of any possible implementation of the first aspect to be implemented.

[0056] Furthermore, the technical effects of the second aspect to the eighth aspect described above can refer to the technical effects of the communication method described above in the first aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0057] FIG. 1 is a schematic diagram of an architecture of A-IoT;

[0058] FIG. 2 is a schematic diagram of a flow of A-IoT;

[0059] FIG. 3 is a schematic diagram of another flow of A-IoT;

[0060] FIG. 4 is a schematic diagram of an architecture of a communication system according to an embodiment of the present application;

[0061] FIG. 5 is a schematic diagram of another architecture of a communication system according to an embodiment of the present application;

[0062] FIG. 6 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0063] FIG. 7 is a schematic diagram of another flow of a communication method according to an embodiment of the present application;

[0064] FIG. 8 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0065] FIG. 9 is a schematic diagram of a flow of a communication method according to an embodiment of the present application;

[0066] FIG. 10 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application;

[0067] FIG. 11 is a schematic diagram of another structure of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0068] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a wireless network (Wi-Fi) system, a vehicle to everything (V2X) communication system, a device to device (D2D) communication system, a vehicle networking communication system, a 4th generation (4G) mobile communication system such as a long term evolution (LTE) system, a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) mobile communication system such as a new radio (NR) system, and a future communication system.

[0069] The technical terms and related technical solutions in the present application will be described below in conjunction with the accompanying drawings.

[0070] 1. Ambient IoT (A-IoT):

[0071] With the development of communication technology, the 3rd generation partnership project (3GPP) defines A-IoT. A-IoT is also called ambient power-enabled IoT, or passive IoT (P-IoT). A-IoT can be applied to a variety of value scenarios.

[0072] For example, warehouse / transportation / supplies: by embedding or pasting passive or semi-passive IoT tags on goods, the information of the goods in the logistics process is automatically collected by the reader, and the management personnel can quickly query the goods information in the system, reduce the risk of loss or theft, improve the goods handover speed, improve the accuracy, and prevent counterfeiting and anti-fake.

[0073] For another example, fixed asset management: some places such as libraries, art galleries and museums with large assets or valuable goods need complete management procedures or strict protection measures. When the storage information of books or valuable goods changes abnormally, the administrator will be reminded in the system in the first time, so as to handle the relevant situation.

[0074] Figure 1 is a schematic diagram of an architecture of A-IoT, as shown in Figure 1, the architecture can include: a server, an ambient IoT management function (AIoTMF), a reader, an A-IoT terminal, or a terminal supporting A-IoT.

[0075] The server can be an application function (AF), an application server (AS), or an ambient IoT / passive IoT application function (A-IoT / P-IoT AF), etc., and the specific naming is not limited.

[0076] The AIoTMF can process service requests from a service requester (AF) and perform corresponding service operations (such as instructing the reader to perform an inventory process of the A-IoT terminal), transmit instructions (such as read operations, write operations, deactivation operations, etc.). The AIoTMF can also manage IoT devices, perform security authentication processes, etc.

[0077] The A-IoT terminal can be divided into three categories: device A, device B, or device C. Device A or device 1a can be understood as a passive A-IoT terminal. The passive A-IoT terminal can be in the form of a tag, or any other terminal form, without limitation. Device B or device 1b can be understood as a semi-passive A-IoT terminal. The semi-passive A-IoT terminal can obtain energy through solar energy, radio frequency, wind energy, water energy, or tidal energy, etc., and the way of obtaining energy is not limited. These nodes do not have or rely on power supply devices such as batteries, but obtain energy from the environment to support data sensing, transmission, and distributed computing. Device C or device 1c can be understood as an active A-IoT terminal. For ease of understanding, A-IoT terminal and tag can be replaced with each other in expression. Alternatively, the A-IoT terminal can also be considered as an A-IoT device.

[0078] The reader can be a radio access network (RAN) such as a base station, a pole station, a micro base station, a macro station, etc., or the reader can also be a terminal device such as a mobile phone, an IoT device, a handheld reader, etc. The reader can perform non-contact bidirectional data communication through a wireless radio frequency, read and write the tag by using the wireless radio frequency, so as to achieve the purpose of identifying the target and exchanging data. For example, for a passive tag, when it enters the effective identification range of the reader, it can receive the radio frequency signal sent by the reader, send the information stored in the chip by means of the induced current, or for a semi-passive tag or an active tag, it can actively send a signal of a certain frequency, the reader receives the information and decodes it, and then sends it to the central information system for relevant data processing. In addition, the reader can also be called a reader-writer.

[0079] Specifically, when the server (or referred to as a service requester, for example, an application function (AF) or an application server (AS)) performs an operation on the tag, an operation instruction can be sent through a core network (CN), and the operation instruction can include but is not limited to: obtaining tag information, inventory operation (or referred to as stocktaking operation), read operation, write operation, invalidation operation, and interacting with the tag information operation. The operation instruction can include area location information, identification information of the tag, etc. The reader sends an access instruction to the tag. When the tag successfully performs random access, the reader sends an instruction to the tag, such as forwarding the above operation instruction. The tag obtains or sends corresponding information according to the instruction. For example, when the operation instruction is an inventory instruction or performs an inventory operation, the tag sends the identification information of the tag; when the operation instruction is a read instruction or performs a read operation, the tag sends the data information stored in the storage area of the tag; when the operation instruction is a write instruction or performs a write operation, the tag stores the data information to be written into the tag included in the operation instruction into the storage area of the tag. Then the reader sends (or forwards) the above information sent by the tag to the core network, and the core network sends the information to the server.

[0080] It should be understood that the manner in which the server sends the operation instruction can be through the control plane channel. For example, the AF / AS / A-IoT / P-IoT AF sends the operation instruction to the ambient IoT management function (or referred to as the ambient IoT function (AIoTF)), and the ambient IoT management function sends the operation instruction to the reader through the access and mobility management function (AMF). Alternatively, the A-IoT / P-IoT AF sends the operation instruction to the AIoTF through a network function network element, and the AIoTF sends the operation instruction to the reader, and the network function network element can include but is not limited to: a network exposure function device (NEF), a session management device (SMF), a policy control device (PCF), a user plane device (UPF), a unified data management device (UDM), a network slice and an independent non-public network (SNPN) authentication and authorization function (network slice-specific and SNPN authentication and authorization function, NSSAAF), etc. Alternatively, the manner in which the server sends the operation instruction can also be through the user plane channel. For example, the server sends the operation instruction to the reader through the UPF, and in the case of the reader being a terminal device, the server also sends the operation instruction to the RAN device through the user plane device, and the RAN device forwards the operation instruction to the reader.

[0081] The server or service requester can perform different operations on the ambient IoT device (or referred to as the ambient IoT terminal (A-IoT terminal)), such as a tag. The following lists several common service operations. The following describes the tag as a specific device form of the ambient IoT device, but the invention is not limited to the device form of the ambient IoT device.

[0082] The inventory operation, i.e. inventorying the existing tags, can also be understood as obtaining the identity of the tags. Each tag has its corresponding identity. The identity of the tag can be assigned by the enterprise (i.e. written into the tag when the enterprise prints the tag) or by the operator. In one possible implementation, the identity of the tag can be a globally unique code, such as an electronic product code (EPC), or a temporary identity or an identity that is not globally unique. In the inventory process, the server can issue an inventory instruction. Generally, the inventory instruction can include the identity range of the tag, the reader identity, the location information, etc. After receiving the inventory instruction, the reader can inventory the tag according to the inventory instruction and send the identity of the tag to the server. Alternatively, the server sends the inventory instruction, and the reader transmits the inventory instruction to the tag. The tag learns that it is an inventory operation according to the content of the inventory instruction, and sends the identity of the tag to the reader, and the reader sends the identity of the tag to the server; or the tag sends the identity of the tag to the core network through the reader, and the core network sends the identity of the tag to the server.

[0083] The read operation, i.e. reading data from the tag. The tag can have a storage function, and its storage area can store data. If the server wants to perform a read operation on the tag, it will send a read instruction, and the reader or core network will perform a read operation on the tag according to the instruction, read data from the tag storage area, and send the data to the server. The write operation, i.e. writing data to the tag. The server can send a write instruction, and the reader or core network will perform a write operation on the tag according to the instruction, and write data to the storage area of the tag.

[0084] The inactivation operation, i.e. disabling or inactivating the tag. The server can send an inactivation instruction, which can include the identity of the tag (i.e. the identity of the tag that is desired to be disabled or inactivated). The reader or core network will perform a disabling operation on the tag according to the instruction, and after the operation is completed, the tag will be disabled or inactivated and can no longer be inventoried or perform other operations.

[0085] Obtaining tag information can be understood as a high-level description of the above-mentioned various operations (e.g. a high-level description of the inventory operation and the read operation), which does not distinguish whether the server is inventorying the tag or reading the data of the tag. The operation will obtain tag information, which can be identity information of the tag or information stored in the storage area of the tag.

[0086] The message interaction with the tag can be understood as a high-level description of the various operations described above. After receiving the instruction sent by the server, the reader interacts with the tag and sends the information from the tag to the server. This operation is mainly aimed at the above-mentioned reader not viewing the content of the instruction, and only responsible for forwarding the message sent by the server to the tag and the message sent by the tag to the server. Therefore, in this scenario, the operation performed by the reader on the tag can be understood as a message interaction operation with the tag.

[0087] 2. Operation flow of A-IoT:

[0088] As shown in FIG. 2, one flow is as follows.

[0089] S200, the core network sends an inventory message to the reader.

[0090] The inventory message contains instructions, such as read / write / inventory instructions, which are not limited in detail, and the following examples are taken as read instructions for reference. In addition, the inventory message also contains inventory session, action, mask, etc.

[0091] 1) The session and the following flag bit are in a binding relationship, each flag bit corresponds to a session, and the inventory session specifies which session flag bit is set.

[0092] 2) The action specifies how to set, such as action indicating 1 or 0, and if the mask matches after the tag receives it, the session corresponding flag bit will be set, such as A(action = 1) or B(action = 0).

[0093] 3) The mask can be understood as a prefix of the tag identification. The mask is used to select which tags are selected, such as the tag storing a complete 96-bit identification, and the mask can indicate that the tag with the first 16 bits of 111…111 is selected.

[0094] The core network can send an inventory message to the reader after determining to perform an A-IoT business operation (such as a read / write / inventory operation).

[0095] S201, the reader sends a select message or a paging message.

[0096] The select message or the paging message is used to select a group of tags, and the select message or the paging message can contain the information in the above-mentioned inventory message.

[0097] The tag receives the select message, and the matched tag sets the select message and the corresponding flag position. For example, the inventory session indicates session S0, the behavior indicates 0, and if the mask matches, the tag sets the flag position of session S0 as A, which is the initial flag position. Then, the device identification (e.g., EPC) success flag position is flipped to B. In this way, A is the tag that has not transmitted the EPC, and B is the tag that has successfully transmitted the EPC. If the mask matches, the tag can further set the flag position according to the indication of the session, and further listen to the subsequent query message.

[0098] S202, the reader sends a query message or a query repetition message (queryRep).

[0099] The query message can carry a Q value, a session, or a flag position.

[0100] Suppose that the query message carries a session S0 and a flag position A, and the session and the flag position of the tag match, so that a random number of 0-2^Q-1 is randomly generated according to Q as an initial value of the counter.

[0101] The query repetition message does not need to carry content, does not have a Q value or a session, and can be sent multiple times.

[0102] If no tag sends a response, such as RN16, the reader continues to send the query repetition message. If the tag receives the query repetition message, the tag decrements the counter value, such as Counter = Counter-1.

[0103] S203, the tag sends RN16.

[0104] If the counter value generated by the tag is 0, the tag feeds back RN16, otherwise, it does not respond. RN16 is a 16-bit random number (or can be 16 bits, 8 bits), which is used for contention resolution. For example, after the tag receives the query repetition message (which can be multiple times), the counter value is decremented to 0, and the tag feeds back RN16, otherwise, it does not respond. Exemplarily, each query repetition message corresponds to the start or end of an access time slot, and the tag receives each query repetition message, which means the end of the last time slot and the start of the next time slot. The tag can randomly select an access time slot, and initiate access or send uplink data (EPC) or receive downlink data in the corresponding access time slot.

[0105] S204, the reader returns an acknowledgement message (acknowledge, ACK).

[0106] The reader receives the RN16 sent by the tag, and if there is no collision (e.g., only one tag sends the RN16), it feeds back the ACK, wherein the ACK contains the received RN16, which is used to indicate that the contention resolution is successful.

[0107] S205, the tag sends a device ID.

[0108] If the tag receives the ACK and the RN16 matches, the tag feeds back the device ID, otherwise, it does not feed back. In one possible implementation, the device ID can be carried in an uplink (UL) non-access-stratum (NAS) message, and the UL NAS message can also carry data, such as data read according to the read instruction.

[0109] S206, the reader sends a queryRep message.

[0110] If the tag sends the device ID and receives the queryRep message, it indicates that the transmission is successful, and the flag bit is flipped, i.e., flipped to B. For example, the flag bit can be used to prevent a tag that has been inventoried from being inventoried repeatedly. For example, if the flag bit carried in a subsequent paging message is A, the tag will not respond if the flag bit is flipped to B.

[0111] S207, the reader sends an N2 message to the core network.

[0112] The N2 message contains the UL NAS message described above. In addition, the execution order of S206 and S207 is not limited. In one possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced by other message types, i.e., messages corresponding to the interface between the reader and the core network, such as AIoT NGAP. The present application is not limited.

[0113] As can be seen, in the flow shown in FIG. 2, the tag only needs to report the device ID and / or data to be read through a single UL NAS message, without subsequent signaling interaction. Therefore, when the reader receives the UL NAS message from the tag, it can continue to trigger the random access procedure of other tags, such as continuing to broadcast paging messages or repeating queries, so as to avoid waiting for other instructions from the core network element.

[0114] For another example, as shown in FIG. 3, still taking the A-IoT terminal as the tag, another flow is as follows.

[0115] S300, the core network sends an inventory message to the reader.

[0116] The inventory message contains an inventory session, behavior, or mask, etc. Unlike S200 described above, the inventory message does not carry an instruction.

[0117] S301, the reader sends a selection message or a paging message.

[0118] S302, the reader sends a query message or a queryRep message.

[0119] S303, the tag sends the RN 16.

[0120] S304, the reader returns an ACK.

[0121] S305, the tag sends a device identity.

[0122] The device identity is carried in an UL NAS message.

[0123] In one possible implementation, the device identity is carried in the UL NAS message, but unlike S206 described above, the UL NAS message in S306 does not carry data.

[0124] S306, the reader sends a query repetition message.

[0125] S307, the reader sends an N2 message to the core network.

[0126] The N2 message contains the UL NAS message in S306. In one possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced by other message types, i.e., messages corresponding to the interface between the reader and the core network, such as AIoT NGAP. The present application does not make any limitation.

[0127] It can be understood that S300-S308 can refer to the related description of S200-S207 described above, and will not be repeated here.

[0128] Up to now, the tag random access is completed.

[0129] S308, the core network sends an instruction to the reader.

[0130] In one possible implementation, the core network sends a downlink (DL) NAS message to the reader.

[0131] The DL NAS message carries the instruction, such as the instruction to read.

[0132] S309, the reader sends the instruction to the tag.

[0133] The instruction can be the instruction to read.

[0134] In one possible implementation, the reader sends the DL NAS message from the core network to the tag, and the DL NAS message includes the instruction.

[0135] S310, the tag sends data to the reader.

[0136] The data is the data read according to the instruction to read. In one possible implementation, the data is carried in an UL NAS message.

[0137] S311, the reader sends an N2 message to the core network.

[0138] The N2 message in S311 contains the UL NAS message in S310. In a possible implementation, if the interface between the reader and the core network is not an NGAP interface, the N2 message can be replaced with another message type, i.e., a message corresponding to the interface between the reader and the core network, which can be AIoT NGAP for example. The present application does not make any limitation.

[0139] S312, the core network sends an inventory message to the reader.

[0140] The inventory message in S312 can carry an indication of inventory continue.

[0141] In this way, compared with the flow shown in FIG. 2, the flow shown in FIG. 3 is different in that the transmission of the device identifier (such as EPC) and the data is decoupled, and the tag reports information through multiple messages. For example, after the tag receives the ACK sent by the reader, the tag first sends the EPC, which is forwarded to the core network by the reader. Then, after the core network determines that the tag is a device that needs to perform the read operation, the core network sends a read instruction to the tag through the reader, and the tag sends the data to be read to the core network element through the reader. Since at least two interactions are required between the tag and the core network in this process, the reader cannot determine whether it can continue to inventory other tags, i.e., trigger the random access process of other tags, after receiving the first uplink message of the tag, such as the UP NAS message carrying the EPC. Therefore, in this flow, the reader needs to receive the indication information sent by the core network element to continue to perform the inventory, i.e., S312, before triggering the random access process of other tags, such as continuing to broadcast the query message or repeating the query.

[0142] It can be seen that in the A-IoT scenario, the data transmission between the A-IoT terminal and the reader / core network element can be implemented through one or more messages. In this case, how to ensure the efficiency and reliability of data transmission is a problem to be studied at present.

[0143] To solve the above technical problems, the embodiments of the present application propose the following technical solutions. The technical solutions in the present application will be described below with reference to the accompanying drawings.

[0144] The present application will present various aspects, embodiments or features around a system that can include multiple devices, components, modules, etc. It should be understood and appreciated that each system can include additional devices, components, modules, etc., and / or can not include all the devices, components, modules, etc. discussed in connection with the accompanying drawings. In addition, combinations of these solutions can also be used.

[0145] In addition, the terms "exemplary," "for example," and the like are used herein to mean serving as an instance or illustration. Any implementation described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other implementations. The terms "exemplary" and "for example" are therefore used interchangeably herein to refer to a non-limiting example.

[0146] First, in this application, "for indicating" can include for directly indicating and for indirectly indicating. When describing a certain "information" for indicating A, it can include that the information directly indicates A or indirectly indicates A, and it does not mean that A must be carried in the information.

[0147] The information indicated by one information is called to be indicated information, and in the specific implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be only indicated a part, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, a protocol stipulates), thereby reducing the indication overhead to a certain extent. Meanwhile, the common part of each information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separately indicating the same information.

[0148] In addition, the specific indication manner can also be various existing indication manners, for example, but not limited to, the above-mentioned indication manners and various combinations thereof. The specific details of various indication manners can refer to the prior art, and will not be described herein. As can be known from the above, for example, when multiple information of the same type needs to be indicated, the indication manners of different information can be different. In the specific implementation process, the required indication manner can be selected according to the specific needs, and the selected indication manner is not limited in the embodiments of the present application, so that the indication manner involved in the embodiments of the present application should be understood as covering various methods that can enable the to-be-indicated party to know the to-be-indicated information.

[0149] The to-be-indicated information can be sent as a whole or can be divided into multiple sub-information and sent separately, and the sending period and / or sending occasion of the sub-information can be the same or different. The specific sending method is not limited in the present application. The sending period and / or sending occasion of the sub-information can be predefined, for example, predefined according to a protocol, or configured by the transmitting end device to the receiving end device through sending configuration information. The configuration information can include, for example but not limited to, one or a combination of at least two of radio resource control (RRC) signaling, medium access control (MAC) layer signaling and physical layer signaling. The MAC layer signaling includes, for example, MAC control element (CE), and the physical (PHY) layer signaling includes, for example, downlink control information (DCI).

[0150] Second, in the embodiments shown below, the first, second and various numbers are only distinguished for convenience of description, and do not limit the scope of the embodiments of the present application. For example, different indication information is distinguished.

[0151] Third, “preset” or “predefined” or “preconfigured” can be realized by pre-saving corresponding codes, tables or other means for indicating related information in devices (for example, including terminal devices and network devices), and can also be pre-specified in a protocol. The specific implementation method is not limited in the present application. The “saving” can mean saving in one or more memories. The one or more memories can be separately set or integrated in the encoder or decoder, processor or communication device. The one or more memories can be partially separately set and partially integrated in the decoder, processor or communication device. The type of memory can be any form of storage medium, which is not limited in the present application.

[0152] Fourth, the “protocol” involved in the embodiments of the present application can refer to a standard protocol in the communication field, which can include, for example, the LTE protocol (such as technical specification (TS) 36, i.e. the technical specification of TS36 series) of 3GPP, the NR protocol (such as the technical specification of TS38 series) and the related protocol applied to the future communication system, which is not limited in the present application.

[0153] The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0154] The network architecture and service scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0155] To facilitate understanding of the embodiments of the present application, first, a communication system applicable to the embodiments of the present application is described in detail taking the communication system shown in FIG. 4 as an example. Exemplarily, FIG. 4 is an architecture schematic diagram of a communication system to which the method provided by the embodiments of the present application is applicable.

[0156] FIG. 4 is an architecture schematic diagram of a communication system, which mainly includes a first device and a second device.

[0157] The first device can be a network entity, and the second device can be a terminal device. Or the first device can be a terminal device, and the second device can be a network entity.

[0158] The terminal device can be a device or module with corresponding communication function for accessing the communication system. The terminal device can also be referred to as a terminal device, a user equipment (UE), a mobile station, a mobile terminal, and can be specifically virtual reality, augmented reality, industrial control, automatic driving, remote medical treatment, smart power grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc., or can also be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, a wireless communication function transport carrier, a communication module, etc.

[0159] The terminal device can be widely applied in various scenarios, such as device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), internet of things (IoT), such as A-IoT, referred to as A-IoT terminal. Embodiments of the present application do not limit the device form of the terminal. The terminal is usually provided with a communication module, circuit or chip for executing corresponding communication functions. The terminal is also configured with program instructions for executing corresponding communication functions.

[0160] The network entity can be a core network element, such as the name of the core network element can be an internet of things function, and the specific name is not limited. The internet of things function can be an ambient internet of things function (AIoTF), an ambient internet of things management function (AIoTMF), an internet of things terminal management function (IDMF), an internet of things management function (IoTMF), a tag management function (TMF), and an ambient internet of things device management function (AIDMF). The naming of the internet of things function network element is not limited in the present application, and can be other names. The present application takes AIoTMF as an example of the abbreviated name of the internet of things function network element. The AIoTMF can process service requests from service requestors (such as AF), and perform corresponding service operations (such as instructing the reader to perform the inventory process of the internet of things device), and transmit instructions (such as read operation, write operation, inactivation operation, etc.). The internet of things device is managed, the security authentication process is performed, and the data is transmitted.

[0161] Alternatively, the network entity can also be an access network device, also referred to as a radio access network (RAN) node, or a network device with logical functions of a core network. The RAN node can be for a 3GPP related cellular system, such as a 4G, 5G mobile communication system, or a future-oriented evolved system. The RAN node can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. The RAN node can also be a communication system that combines two or more of the above systems. The RAN node can also be referred to as an access network device, a RAN entity or an access node, etc., which forms part of a communication system to help terminals to realize wireless access. Multiple RAN nodes in a communication system can be nodes of the same type or nodes of different types.

[0162] In a possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a WiFi system, etc. The RAN node can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in vehicle to everything (V2X) technology can be a road side unit (RSU). All or part of the functions of the RAN node in the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform such as a cloud platform. The RAN node can also be provided with a communication module, circuit or chip for performing corresponding communication functions, and program instructions for performing corresponding communication functions. The RAN node in the present application can also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node. The device form of the RAN node can be a pole station, a micro base station, a base station, a small station, a macro station, etc., and is not specifically limited.

[0163] In another possible scenario, multiple RAN nodes cooperate to assist a terminal to implement wireless access, and different RAN nodes respectively implement part of functions of a base station. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU), etc.

[0164] In some examples, the CU is a logical node that carries radio resource control (RRC) layer, service data adaptation protocol (SDAP) layer, packet data convergence protocol (PDCP) layer, and other control functions of an access network device. The CU is connected to network nodes such as a core network through some interfaces, which can be an E2 interface or the like. Optionally, the CU can have part of the functions of the core network. The CU (for example, the PDCP layer and higher layers) is connected to the DU (for example, the RLC layer and lower layers) through some interfaces, which can be an F1 interface or the like. In some examples, these interfaces (for example, the F1 interface) can provide control plane (C-plane) and user plane (U-plane) functions (for example, interface management, system information management, UE context management, RRC message transmission, etc.). The F1AP is an application protocol of the F1 interface, which defines signaling procedures of the F1 in some examples. The F1 interface supports a control plane F1-C and a user plane F1-U.

[0165] In some examples, the CU can be split into a control unit-control plane (CU-CP) and a control unit-user plane (CU-UP), where the CU-CP is a logical node carrying an RRC layer and a PDCP control plane part (PDCP-C) layer, used to implement the control plane function of the CU. The CU-CP can interact with a network element in the core network used to implement the control plane function. The network element in the core network used to implement the control plane function can be an access and mobility function network element, such as an AMF in a 5G system. The AMF is used to be responsible for mobility management in a mobile network, such as location updating of a terminal device, registration of the terminal device to a network, handover of the terminal device, and the like. The CU-UP is a logical node carrying an SDAP layer and a PDCP user plane part (PDCP-U) layer, used to implement the user plane function of the CU. The CU-UP can interact with a network element in the core network used to implement the user plane function.

[0166] The above configuration of the CU and the DU is merely an example, and the CU and the DU can have other functions according to requirements. For example, the CU or the DU can be configured to have more protocol layer functions, or the CU or the DU can be configured to have partial processing functions of the protocol layers. For example, partial functions of the RLC layer and functions of the protocol layers above the RLC layer are arranged in the CU, and the remaining functions of the RLC layer and functions of the protocol layers below the RLC layer are arranged in the DU. For another example, the functions of the CU or the DU can be divided according to service types or other system requirements, for example, according to delay. Functions that require to meet a relatively low delay requirement in processing time are arranged in the DU, and functions that do not require to meet the delay requirement are arranged in the CU.

[0167] In some examples, the DU is a logical node carrying a radio link control (RLC) layer, a medium access control (MAC) layer, a higher physical layer (higher PHY), and other functions. In some examples, the DU can control at least one RU. The DU is connected to the RU through some interfaces, which can be a front-haul interface. In some examples, the higher physical layer includes part of the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, and the like.

[0168] In some examples, a RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). A RU is a logical node that carries lower physical layer (Lower PHY) and radio frequency (RF) processing. In some examples, a RU can be a 3GPP transmission reception point (TRP) or a remote radio head (RRH) or other similarly functioning entity. In some examples, a Lower PHY includes portions of PHY processing such as fast fourier transform (FFT), inverse fast fourier transformation (IFFT), digital beamforming, and filtering, among other processing functions. A RU communicates with one or more UEs over a wireless link.

[0169] A DU and a RU can or can not be co-located. A DU and a RU exchange control plane information and user plane information over a fronthaul link via a lower-layer split-control, user and synchronization (LLS-CUS) interface. The LLS-CUS can include a LLS-C interface and a LLS-U interface that provide control plane (C-plane) and user plane (U-plane), respectively. In some examples, a control plane (C-plane) refers to real-time control between a DU and a RU. A management plane (M-plane) refers to non-real-time management operations between a DU and a RU that have an interface of a fronthaul link to exchange management information.

[0170] A DU and a RU can cooperate to collectively implement the functionality of a PHY layer. A DU can be connected to one or more RUs. The functionality of a DU and a RU can be configured in a number of ways depending on the design. For example, a DU can be configured to implement baseband functionality and a RU can be configured to implement mid- RF functionality. As another example, a DU can be configured to implement high layer functionality in a PHY layer and a RU can be configured to implement low layer functionality in the PHY layer or to implement the low layer functionality and RF functionality. High layer functionality in a PHY layer can include a portion of the functionality of the PHY layer that is closer to a MAC layer, and low layer functionality in a PHY layer can include another portion of the functionality of the PHY layer that is closer to a mid-RF side.

[0171] The CU (or CU-CP and CU-UP), DU or RU can also have different names in different systems, but those skilled in the art can understand their meanings. For example, in the ORAN system, the CU can also be referred to as O-CU (open CU), the DU can also be referred to as O-DU, the CU-CP can also be referred to as O-CU-CP, the CU-UP can also be referred to as O-CU-UP, and the RU can also be referred to as O-RU. For the convenience of description, the CU, CU-CP, CU-UP, DU and RU are taken as examples for description in this application. Any one of the CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0172] In the ORAN system, the RAN node communicates with the core network (CN) through a backhaul link and communicates with the terminal through an air interface. The ORAN system also includes a RAN intelligent controller (RIC), which can specifically include a non-real time RAN intelligent controller (Non-RT RIC) and a near-real time RAN intelligent controller (Near-RT RIC). The Non-RT RIC is used to implement non-real-time intelligent management of RAN functions, and the Non-RT RIC is located in a service management and orchestration framework (SMO) module. The Near-RT RIC is used to implement near-real-time intelligent management of the RAN, and implements near-real-time control and optimization of modules and resources of the O-RAN through data collection and related operations on the E2 interface.

[0173] In some examples, the communication system of the embodiments of the present application can be applied to an A-IoT scenario.

[0174] As shown in (a) of FIG. 5, the A-IoT terminal directly communicates with the reader in both directions, including interactive environment Internet of Things data and / or signaling, such as the reader sending downlink data / signaling to the A-IoT terminal, and the reader receiving uplink data / signaling from the A-IoT terminal.

[0175] As shown in (b) of FIG. 5, the A-IoT terminal and the reader perform bidirectional communication through an intermediate node, which can be a repeater, an integrated access and backhaul (IAB) node, a UE, or the like, capable of implementing the environmental IoT, to transmit environmental IoT data and / or signaling between the A-IoT terminal and the reader.

[0176] As shown in (c) of FIG. 5, the A-IoT terminal receives data / signaling from the secondary node and transmits data / signaling to the reader, or receives data / signaling from the reader and transmits data / signaling to the secondary node. The secondary node can be a repeater, an IAB, a UE, or the like, capable of implementing the environmental IoT.

[0177] As shown in (d) of FIG. 5, the A-IoT terminal performs bidirectional communication with a terminal device, such as interaction of environmental IoT data and / or signaling. The terminal device can be a terminal device supporting the function of the reader, i.e., the reader can also be understood as a terminal device.

[0178] In one possible scenario, the first apparatus can be a core network element, such as an A-IoT MF, or other network elements with A-IoT functions, such as an IDMF or an AMF, which are not specifically named and are not limited, and the second apparatus can be the A-IoT terminal shown in (a) of FIG. 5 to (d) of FIG. 5. In another possible scenario, the first apparatus can be an access network device, which can be specifically a combination of one or more of the reader, the intermediate node, and the secondary node shown in (a) of FIG. 5 to (c) of FIG. 5, such as a reader, an intermediate node, a reader+intermediate node, a reader+secondary node, and the like; or the first apparatus can also be a terminal device, which can be specifically a terminal device supporting the function of the reader shown in (d) of FIG. 5. Therefore, the first apparatus can also be understood as a reader. Correspondingly, the second apparatus can still be the A-IoT terminal shown in (a) of FIG. 5 to (d) of FIG. 5. Alternatively, the device types of the first apparatus and the second apparatus can also be interchanged, such as the first apparatus being an A-IoT terminal and the second apparatus being a reader.

[0179] In the communication system, the first device and the second device can select a transmission mode of data according to different data lengths, such as direct transmission or segmented transmission. Taking the first data as an example, in the case that the first length of the first data is different, or the data amount of the first data is different, the first data can be transmitted in different modes. For example, if the first length is relatively small, the first device can transmit the first data in a first mode, such as through a first message, to ensure the efficiency of data transmission. If the first length is relatively large, the first device can transmit the first data in a second mode, such as through a second message and a third message, to avoid transmission failure due to the first message being unable to transmit the first data, and thus ensure the reliability of data transmission.

[0180] It should be understood that the communication method provided by the embodiments of the present application can be applied to the device shown in FIG. 4, and the specific implementation can refer to the method embodiments described below, which will not be described here. The scheme in the embodiments of the present application can also be applied to other communication systems, and the corresponding name can also be replaced by the name of the corresponding function in other communication systems.

[0181] It should also be understood that FIG. 4 is only a simplified schematic diagram for understanding, and other network devices and / or other terminal devices can also be included in the communication system, which are not shown in FIG. 4.

[0182] The interaction process between devices in the communication system will be specifically introduced below by combining FIGS. 6-9 and method embodiments. The communication method provided by the embodiments of the present application can be applied to the above-mentioned communication system, which will be specifically introduced below.

[0183] FIG. 6 is a flowchart of the communication method, which is applicable to the interaction between the first device and the second device, as shown in FIG. 6, the flow of the communication method is as follows:

[0184] S601, the first device determines the first length.

[0185] S602, the first device determines to transmit the first data in the first mode or the second mode according to the first length.

[0186] The S601-S602 will be introduced jointly below.

[0187] The first length can be the length of the first data.

[0188] The first length can be a quantized length value, for example, the first length can be a number of length units, or the first length can be represented by a number of length units. For example, one length unit can be one bit, i.e., the first length is a number of bits, such as 16 bits, 24 bits, 36 bits, 96 bits, 128 bits, 192 bits, 256 bits, etc.; or one length unit can be a plurality of bits, such as 16 bits as one word, and the first length is a number of 16 bits, i.e., a number of words; or one length unit can be 8 bits as one byte, and the first length is a number of 8 bits, i.e., a number of bytes; or one length unit can be other numbers of bits, such as 3 bits, 4 bits, 5 bits, etc., and the specific number is not limited. In addition, in the case where one length unit is a plurality of bits, if the number of bits contained in one length unit cannot be divided by the number of bits contained in the first data, the first length can also be represented by the number of length units + the number of bits, such as the first data contains 100 bits, and one length unit contains 8 bits, then the first length can be represented by 12 length units + 4 bits, or rounded up to 13 length units.

[0189] The first data can be data sent by the first device, or can be data received by the first device, which will be introduced below in different cases.

[0190] Case 1:

[0191] The first data is data sent by the first device, and the first device can be a core network element (such as an A-IoT MF) or an access network device (such as a RAN node), and the second device can be a terminal device, such as an A-IoT terminal, which can be referred to the related description in FIG. 4-FIG. 5. Case 1 can be applied to a write scenario, or a write operation / data write operation. For this, the first device can first receive the first data before sending the first data (such as data to be written), and determine the first length according to the first data.

[0192] The first device is taken as a core network element or an access network device as an example.

[0193] First possible implementation:

[0194] The first device is a core network element (denoted as a first core network element), and the first core network element can receive a first service request. For convenience of description, the first service request received by the first core network element is denoted as service request #1. In addition, #x mentioned in the embodiments of the present application, such as #1, #2, #a, #b, etc., is an identifier used to distinguish different messages / information, and should not be understood as a part of the message / information, and the same applies hereinafter, and will not be repeated.

[0195] The first service #1 can be used to request to write the first data to the A-IoT terminal. For example, the first service #1 can be a request sent by a service requester, such as an AF, an AS, or an A-IoT / P-IoT AF, to the first core network element. The service request #1 can include the first data, and include at least one of the following: an identity of the service requester, a service type, a device identity, a data length, or a first address. The identity of the service requester can identify the service requester, such as an AF ID, an AS ID, or an A-IoT / P-IoT AF ID, without limitation. The service type can indicate a type of the service / operation, such as a write operation. The device identity can be an identity of a device that performs the service / operation, or an identity range / identity prefix, where the A-IoT terminal is included in the A-IoT devices indicated by the identity range / identity prefix. The first address can indicate a storage area where the first data is stored, which can be a storage area of the A-IoT terminal, such as an area in a memory / cache / hard disk of the A-IoT terminal, and specifically an area storing user data. The first address can include at least one of the following: a start address of the storage area, or an end address of the storage area. The data length can indicate a number of bits included in the first data.

[0196] It should be understood that the first core network element can receive the service request #1 through another network function, such as a network exposure function (NEF) element. The message type of the service request #1 received by the first core network element from the other network function can be the same as or different from the message type of the service request received by the other network function from the service requester, that is, the other network function can pass the service request #1 to the first core network element transparently, or process (such as replace the message type) the received service request to obtain the service request #1 and then send it to the first core network element, without limitation to the processing manner.

[0197] The first core network element can obtain the first data from the service request #1, and determine the number of bits included in the first data. Alternatively, if the service request #1 includes the first address, the first core network element can also determine the number of bits included in the first data according to the first address. For example, the first core network element can determine the number of bits included in the first data according to the start address of the storage area and the end address of the storage area, such as the start address of the storage area being add1 and the end address of the storage area being add2,

[0198] |add2-add1|=X, i.e. the first data contains X bits, || denotes an absolute value operation. Alternatively, if the service request #1 contains a data length, the first core network element can also determine the number of bits contained in the first data according to the data length. On this basis, the first core network element can quantize the number of bits contained in the first data, for example, divide the number of bits contained in the first data by a length unit to obtain the first length. Of course, if a length unit contains one bit, the number of bits contained in the first data is the first length.

[0199] It should be understood that the service request #1 is an example, which can also be expressed as other names, such as command #1. The operation (such as write operation) corresponding to the command #1 can also be used as the information indicating the type of service.

[0200] After determining the first length, the first core network element can compare the first length with the length threshold.

[0201] The length threshold can refer to the maximum length of data transmission, i.e. the maximum transmission data amount / data length of a single message. If the maximum length is exceeded, multiple messages may be needed for transmission.

[0202] The length threshold can be preconfigured or protocol predefined information, such as preconfigured in the third device. For case 1, the third device can be a core network element (such as a second core network element), such as a UDM network element or a unified data repository (UDR) network element, or any other network element that can be used to store or manage data, which is not limited in particular.

[0203] In the second core network element, the length threshold can be service requestor granularity information, i.e. the length threshold corresponding to different service requestors can be different, and the length threshold corresponding to a service requestor is applicable to a terminal corresponding to the service requestor, such as a terminal executing the service of the service requestor. Alternatively, the length threshold can also be service granularity information, such as the length threshold corresponding to different types of services can be different, such as read and write can be understood as different types of services, and such as inventory and positioning can also be understood as different types of services, and the length threshold corresponding to a type of service is applicable to a terminal corresponding to the service, such as a terminal executing the service. Alternatively, the length threshold can also be terminal or device granularity information, such as A-IoT terminal, such as the length threshold corresponding to different terminals or devices can be different.

[0204] The first core network element can obtain the length threshold from the second core network element.

[0205] For example, the length threshold is service requester granularity information, the first core network element can send the identity of the service requester to the second core network element through a service interface message. The second core network element can determine the length threshold corresponding to the service requester according to the identity of the service requester, and return it to the first core network element through a service interface message. For another example, the length threshold is service granularity information, the first core network element can send the service type to the second core network element through a service interface message. The second core network element can determine the length threshold corresponding to the service type according to the service type, and return it to the first core network element through a service interface message. For another example, the length threshold is terminal or device granularity information, the first core network element can send the device identity to the second core network element through a service interface message. The second core network element can determine the length threshold corresponding to the device identity according to the device identity, and return it to the first core network element through a service interface message.

[0206] It can be understood that the length threshold is preconfigured in the second core network element, which is an example and is not limited, and can also be preconfigured locally in the first core network element, and the first core network element does not need to obtain it from other network elements.

[0207] The length threshold can also be dynamically determined information, for example, the first core network element can determine the length threshold according to the state of the link.

[0208] The link can be used to carry the first data. For example, the link can be a link between an access network device supporting a reader function and an A-IoT terminal. The state of the link can be at least one of the following: packet loss rate, packet error rate, retransmission times, bit error rate, signal-to-noise ratio, etc., or other parameters can also be used, which are not limited. If the value of the at least one is lower, the state of the link is better, otherwise, it is worse. The first core network element can obtain the state of the link from the access network device, for example, the first core network element can initiate a subscription to the link state to the access network device to periodically or under certain conditions (such as the quality of the link changes more than a quality threshold) to obtain the quality of the link, or other ways to obtain the quality of the link, which are not limited.

[0209] The first core network element can determine a length threshold matching the state of the link according to the state of the link, so that the amount of data transmitted can match the state of the link. For example, when the state of the link is relatively poor, the length threshold is relatively small, so as to reduce the amount of data transmitted at a time, and ensure the reliability of data transmission in the case of a relatively poor link state. For another example, when the state of the link is relatively good, the length threshold is relatively large, so as to increase the amount of data transmitted at a time, and ensure the efficiency of data transmission. For example, the first core network element can pre-configure or pre-define multiple intervals of the state of the link, and each interval corresponds to a length threshold. The first core network element can determine a length threshold corresponding to an interval in which the state of the link is located, i.e., a length threshold matching the state of the link. Alternatively, the access network device can determine the length threshold according to the state of the link, and the first core network element does not need to determine the length threshold, and can receive the length threshold from the access network device.

[0210] It can be understood that the state of the link can be replaced by the quality of the link, or the quality of the link, or other expressions, without limitation.

[0211] If the first length is less than or equal to the length threshold, the first core network element can determine to transmit the first data in the first mode. Alternatively, if the first length is greater than the length threshold, the first core network element can determine to transmit the first data in the second mode.

[0212] The first mode can be a mode of transmitting data (or service data) through a message. The message can be the first message used to transmit service data, or any message used to transmit service data, without limitation. In addition, the first mode can also be named in other ways, such as fast transmit mode or fast command mode. Alternatively, corresponding to a write scenario (or write operation), the first mode can also be called fast write mode, or the first mode can also be named in other ways, without limitation.

[0213] The second mode can be a mode of transmitting data (or service data) through multiple messages, or a mode of transmitting data segmented into multiple messages. The first message in the multiple messages can be the first message for transmitting service data, or can be any multiple messages for transmitting service data, and the specific limitation is not made. Similar to the first mode, the second mode can have other names, such as can be called a common transmit mode, or a common command mode, or a long command mode, or, corresponding to the write scenario (or write operation), the first mode can also be called a common write mode, a long write, or the second mode can also have other names, and the specific limitation is not made.

[0214] Therefore, the first core network element determining to transmit the first data through the first mode can mean that the first core network element determines to use one message to transmit the first data; similarly, the first core network element determining to transmit the first data through the second mode can mean that the first core network element determines to segment the first data and use multiple messages to transmit the segments respectively.

[0215] It should be understood that the above size relationship between the first length and the length threshold is only an example, and for example, if the first length is less than the length threshold, the core network element can determine to transmit the first data through the first mode, or if the first length is greater than or equal to the length threshold, the core network can determine to transmit the first data through the second mode.

[0216] The second possible implementation manner is:

[0217] The first device is an access network device, and the first access network device can receive a first service request. For convenience of description, the first service request received by the first access network device is recorded as service request #2.

[0218] The service request #2 can be the request sent by the first core network element. For example, after receiving the service request #1, the first core network element can directly forward the service request #1 to the access network device, that is, the service request #1 and the service request #2 are the same request. Or, the first core network element can also send the service request #2 to the access network device according to the service request #1, such as encapsulating the information in the service request #1 into the service request #2, and then sending the service request #2 to the access network device, in which case the message types of the service request #1 and the service request #2 can be different.

[0219] It should be understood that the service request #2 is also an exemplary naming, which can also be replaced by other names such as command #2, and the operation (such as a write operation) corresponding to the command #2 can also be used as the information indicating the service type.

[0220] The access network device can also obtain the first data from the service request #2, and determine the first length according to the first data. The specific determination principle is similar to the above-mentioned first possible implementation manner, and can be understood with reference, and will not be described here. If the first length is less than or equal to the length threshold, the access network device can determine to transmit the first data through the first mode; or if the first length is greater than the length threshold, the access network device can determine to transmit the first data through the second mode. The length threshold can also be pre-configured or protocol pre-defined information, such as being configured in the second core network element or locally in the access network device. The specific obtaining manner is similar to the above-mentioned third possible implementation manner, and can be understood with reference, and will not be described here. Alternatively, the length threshold can also be dynamically determined information, such as the access network device determining the length threshold according to the state of its own link. The specific implementation principle is similar to the above-mentioned first possible implementation manner, and can be understood with reference, and will not be described here.

[0221] In addition, the above-mentioned second possible implementation manner is only an example. For example, the access network device can not need to configure or obtain the length threshold, or the access network device can not need to determine the first length. In this case, the first core network element can determine whether to send the first data through the first mode or the second mode, and send the mode indication information to the access network device. For example, the mode indication information is 1 bit of signal element, and 0 / 1 two values respectively indicate the first mode or the second mode. In this way, the access network device can determine to send the first data through the first mode or the second mode according to the mode indication information.

[0222] Case 2:

[0223] The first data can be data received by the first device, and the first device can be a core network element or an access network device. The second device can be a terminal device, such as an A-IoT terminal. For details, please refer to the related description in FIG. 4-FIG. 5. Case 2 can be applied to a read scenario, or a read operation / data read operation. For example, the first device can determine the first length before receiving the first data (such as data to be read), to determine the mode of subsequent receiving the first data, such as receiving the first data through the first mode or the second mode.

[0224] The following will be introduced respectively taking the first device as a core network element or an access network device as an example.

[0225] Third possible implementation manner:

[0226] The first device can also be a first core network element.

[0227] For example, the first core network element can receive the first address, and determine the first length according to the first address.

[0228] Specifically, the first core network element can receive a second service request, for convenience of description, the second service request received by the first core network element is recorded as service request #3. The service request #3 can be used to request reading the first data from the A-IoT terminal. The service request #3 can include the first data, and include at least one of the following: an identifier of a service request party, a service type, a device identifier, a data length, or the first address. The service type can indicate the type of service / operation, such as a read operation / data read operation. The identifier of the service request party, the device identifier, the data length, and the first address can refer to the related description in the above service request #1, and will not be described in detail.

[0229] It should be understood that the first core network element can also receive the service request #3 through other network functions (such as the NEF network element). At this time, the message type of the service request #3 and the message type of the service request received by the other network function from the service request party can also be the same or different, that is, the other network function can also transmit the service request #3 to the first core network element, or process (such as replace the message type) the received service request to obtain the service request #3, and then send it to the first core network element, and the specific processing manner is not limited.

[0230] Therefore, the first core network element can obtain the first address from the service request #3, and determine the number of bits contained in the first data according to the first address, to further determine the first length. The specific determination principle can refer to the related description in the above first possible implementation manner, and will not be described in detail here.

[0231] It should also be understood that the service request #3 can also be replaced by other names such as command #3, and the operation (such as the read operation) corresponding to the command #3 can also be used as information indicating the service type.

[0232] For another example, the first core network element can also obtain the first length from the third device.

[0233] In case 2, the third device can also be a second core network element, such as a UDM network element or a UDR network element, or any other network element that can be used to store or manage data, and the specific implementation is not limited.

[0234] The second core network element can pre-configure or protocol pre-define at least one length of the data, which at least one length includes the first length. For example, at the second core network element, the at least one length can be service requester granularity information, i.e., different service requesters can correspond to different lengths of data respectively, and the length of data corresponding to one service requester is applicable to a terminal corresponding to the service requester. Alternatively, the at least one length can also be service granularity information, i.e., different types of services can correspond to different lengths of data respectively, and the length of data corresponding to one type of service is applicable to a terminal corresponding to the service. Alternatively, the at least one length can also be terminal or device granularity information, i.e., different terminals or devices can correspond to different lengths of data respectively.

[0235] For this purpose, if the at least one length is service requester granularity information, the first core network element can send the device identifier to the second core network element through a service interface message. The second core network element can determine the first length corresponding to the device identifier according to the device identifier, and return the first length to the first core network element through a service interface message. If the at least one length is service granularity information, the first core network element can send the service type to the second core network element through a service interface message. The second core network element can determine the first length corresponding to the service type according to the service type, and return the first length to the first core network element through a service interface message. If the at least one length is terminal or device granularity information, the first core network element can send the device identifier to the second core network element through a service interface message. The second core network element can determine the first length corresponding to the device identifier according to the device identifier, and return the first length to the first core network element through a service interface message.

[0236] It should be understood that pre-configuring the at least one length at the second core network element is an example and is not limited, e.g., the at least one length can also be pre-configured locally at the first core network element, and the first core network element does not need to obtain from other network elements.

[0237] After determining the first length, the first core network element can compare the first length with a length threshold. If the first length is less than or equal to the length threshold, the first core network element can determine to receive the first data through the first mode; or if the first length is greater than the length threshold, the first core network element can determine to receive the first data through the second mode, and the specific implementation can refer to the related description of the first possible implementation manner, which will not be described here.

[0238] It can be understood that the first core network element determining that the first data is received through the first mode / second mode does not mean that the first core network element has received the first data, and it should be understood that the first core network element knows that subsequent data of the first length needs to be received through the first mode / second mode, and the data of the first length can be named as the first data.

[0239] The fourth possible implementation manner:

[0240] The first device can be an access network device.

[0241] For example, the access network device can receive the first address, and determine the first length according to the first address. Specifically, the access network device can also receive a second service request, for convenience of description, the second service request received by the access network device is recorded as service request #4. The service request #4 can be the request sent by the first core network element as described above. For example, after receiving the service request #3, the first core network element can directly forward the service request #3 to the access network device, that is, the service request #3 and the service request #4 are the same request. Alternatively, the first core network element can also send the service request #4 to the access network device according to the service request #3, such as encapsulating the information in the service request #3 into the service request #4, and then sending the service request #4 to the access network device. In this case, the message types of the service request #3 and the service request #4 can be different.

[0242] Therefore, the access network device can also obtain the first address from the service request #4, and determine the first length according to the first address. The specific implementation principle is similar to the first possible implementation manner described above, and can be understood with reference, and will not be described here.

[0243] It should be understood that the service request #4 is also an example of naming, which can also be replaced by other names such as command #4, and the operation (such as read operation) corresponding to the command #4 can also be used as the information indicating the service type.

[0244] For another example, the access network device can obtain the first length from the second core network element, and the second core network element can also be an Internet of Things function (such as AIoT MF), a UDM network element or a UDR network element. The specific implementation principle is similar to the third possible implementation manner described above, and can be understood with reference, and will not be described here.

[0245] After obtaining the first length, the access network device can also compare the first length with the length threshold. If the first length is less than or equal to the length threshold, the access network device can determine to receive the first data through the first mode; or if the first length is greater than the length threshold, the access network device can also determine to receive the first data through the second mode. The specific implementation can be referred to the related description of the first possible implementation manner described above, and will not be described here.

[0246] It can be understood that the access network device determines that the first data received through the first mode / second mode is not that the access network device has received the first data, and it should be understood that the access network device knows that the subsequent first length of data needs to be received through the first mode / second mode, which can be named as the first data.

[0247] In addition, the above fourth possible implementation manner is only an example, for example, the access network device can not need to configure or obtain the length threshold, or the access network device also does not need to determine the first length, in this case, the first core network element can determine whether to receive the first data through the first mode or the second mode, and send mode indication information to the access network device, such as 1 bit information element, 0 / 1 two values respectively indicate the first mode or the second mode. In this way, the access network device can determine to receive the first data through the first mode or the second mode according to the mode indication information.

[0248] Case 3:

[0249] The first data can be data sent by the first device, and the first device can be a terminal device, such as an A-IoT terminal, and the second device can be an access network device, which can be referred to the related description in FIG. 4-FIG. 5. Case 3 can be applied to the read scenario, or the read operation / data read operation, for example, the A-IoT terminal can determine the first length before sending the first data (such as data to be read), in order to determine the mode of subsequent sending of the first data, such as receiving the first data through the first mode or the second mode.

[0250] For example, the A-IoT terminal can receive the first address, and determine the first length according to the first address.

[0251] Specifically, the A-IoT terminal can receive a command, such as a command from the access network device. The command can indicate reading the first data from the A-IoT terminal, and the command can include at least one of the following: service type, device identifier, data length, or first address. The service type can indicate the type of service / operation, such as the read operation / data read operation, and the device identifier, data length, and first address can be referred to the related description of the above service request #1, which will not be repeated here.

[0252] Therefore, the A-IoT terminal can also obtain the first address from the command, and determine the first length according to the first address. The specific implementation principle is similar to the above first possible implementation manner, which can be understood by reference, and will not be repeated here.

[0253] After determining the first length, the A-IoT terminal can compare the first length with the length threshold. If the first length is less than or equal to the length threshold, the A-IoT terminal can determine to transmit the first data through the first mode; or if the first length is greater than the length threshold, the A-IoT terminal can determine to transmit the first data through the second mode.

[0254] The length threshold can be pre-configured in the A-IoT terminal locally, or the A-IoT terminal can also acquire the length threshold from the third device.

[0255] In case 3, the third device can be an access network device. That is, the access network device can acquire or determine the length threshold in advance, such as can be pre-configured, or acquired from the second core network element, or determined by itself according to the state of the link, and specific details can be referred to the above-mentioned first possible implementation manner, and will not be repeated here. The access network device can send the length threshold to the A-IoT terminal, such as carried in the above-mentioned command, or carried through a separate message, and specific details are not limited.

[0256] In addition, the specific implementation of the length threshold can also refer to the introduction of the length threshold in the first possible implementation manner, and will not be repeated here.

[0257] If the first length is less than or equal to the length threshold, the A-IoT terminal can determine to transmit the first data through the first mode; or if the first length is greater than the length threshold, the A-IoT terminal can also determine to transmit the first data through the second mode, and the specific determination principle is similar to the above-mentioned first possible implementation manner, and can be understood by reference, and will not be repeated here.

[0258] S603, in the case of determining to transmit the first data through the first mode, transmitting the first data through the first message; or in the case of determining to transmit the first data through the second mode, transmitting the first data through the second message and the third message.

[0259] Continue case 1:

[0260] 1) In the case of determining to transmit the first data through the first mode, the first device can send the first message to the second device.

[0261] The first message can include the first data. The first message can be the first downlink message for transmitting service data to improve transmission efficiency, or can be any downlink message for transmitting service data, such as a NAS message, denoted as NAS message #1, or a RRC message, denoted as RRC message #1.

[0262] For example, the first apparatus is a first core network element, and the second apparatus is an A-IoT terminal. In the case that the A-IoT terminal succeeds in random access, if the first core network element determines to send the first data through the first mode, the first core network element can obtain the first data from the service request #1, and send the first data to the A-IoT terminal through the access network device, such as sending a NAS message #1 carrying the first data. Alternatively, the first apparatus is a first access network device, and the second apparatus is an A-IoT terminal. In the case that the A-IoT terminal succeeds in random access, if the access network device determines to send the first data through the first mode, the access network device can obtain the first data from the service request #2, and send the first data to the A-IoT terminal, such as sending a RRC message #1 carrying the first data, or other similar alternative messages.

[0263] Optionally, the first apparatus can further send the first address to the second apparatus, and the second apparatus can receive the first address.

[0264] For example, the first apparatus is a first core network element, and the second apparatus is an A-IoT terminal. In the case that the A-IoT terminal succeeds in random access, the first core network element can further obtain the first address from the service request #1, and send the first address to the A-IoT terminal, such as carrying in the above-mentioned NAS message #1, or carrying through a separate message, which is not limited in particular. Alternatively, the first apparatus is a first access network device, and the second apparatus is an A-IoT terminal. In the case that the A-IoT terminal succeeds in random access, the access network device can also obtain the first address from the service request #2, and send the first address to the A-IoT terminal, such as carrying in the above-mentioned RRC message #1, or also carrying through a separate message, which is also not limited in particular.

[0265] After receiving the first address, the A-IoT terminal can write the first data into a specified storage area according to the first address.

[0266] It should be understood that, if the first address is a default address of the A-IoT terminal, or the A-IoT terminal decides by itself where to write the first data, the first core network element or the access network device can not need to send the first address to the A-IoT terminal, so as to reduce the overhead.

[0267] 2) In the case that it is determined to send the first data through the second mode, the first apparatus can send a second message and a third message to the second apparatus.

[0268] The first data can include second data and third data. For example, the first apparatus can determine the second data and the third data according to the first data, that is, the first data can be segmented to obtain the second data and the third data.

[0269] The second message can comprise second data, and the third message can comprise third data. The first of the second message or the third message can be the first downlink message for transmitting the service data, so as to reduce the transmission delay, or the second message and the third message can also be any two downlink messages for transmitting the service data, and the specific implementation is not limited. The second message and the third message can be NAS messages, for example, denoted as NAS message #2 and NAS message #3 respectively, or the second message and the third message can be RRC messages, for example, denoted as RRC message #2 and RRC message #3 respectively.

[0270] For example, the first device is a first core network element, and the second device is an A-IoT terminal. In a case where the A-IoT terminal succeeds in random access, if the first core network element determines to send the first data by using the second mode, the first core network element can obtain the first data from the service request #1, and divide the first data into multiple pieces of data equally or unequally. The number of the multiple pieces of data can be determined by the first core network element itself, for example, the first length is L, the length threshold is Lmax, and the number of the multiple pieces of data is which means rounding up. For example, the first core network element can divide the first Lmax pieces of data, and the length of the Nth piece of data is L-(Lmax*(N-1)), or the first core network element can also divide the first Lmax pieces of data, and the length of the Nth piece of data is . which means rounding down. At this time, the second data and the third data can be the first two pieces of data in the N pieces of data. The first core network element can carry the second data into the NAS message #2, and send the NAS message #2 to the A-IoT terminal through the access network device. The first core network element can further carry the third data into the NAS message #3, and send the NAS message #3 to the A-IoT terminal through the access network device.

[0271] Alternatively, the first device is a first access network device, and the second device is an A-IoT terminal. In a case where the A-IoT terminal succeeds in random access, if the access network device determines to send the first data by using the second mode, the access network device can obtain the first data from the service request #2, and divide the first data into multiple pieces of data equally or unequally, and the principle of division is similar to that of the first core network element described above, and can be understood with reference, and will not be described herein again. Subsequently, the access network device can carry the second data into the RRC message #2, and send the RRC message #2 to the A-IoT terminal. The access network device further carries the third data into the RRC message #3, and sends the RRC message #3 to the A-IoT terminal.

[0272] Optionally, the first device can send the first address to the second device, and the second device can receive the first address.

[0273] For example, the first device is a first core network element, and the second device is an A-IoT terminal. In the case that the A-IoT terminal succeeds in the random access, the first core network element can further obtain the first address from the service request #1, and send the first address to the A-IoT terminal through the access network device, such as carrying in the above-mentioned NAS message #2 or NAS message #3, or carrying through a separate message, which is not limited in particular. Alternatively, the first device is a first access network device, and the second device is an A-IoT terminal. In the case that the A-IoT terminal succeeds in the random access, the access network device can also obtain the first address from the service request #2, and send the first address to the A-IoT terminal, such as carrying in the above-mentioned RRC message #2 or RRC message #3, or also carrying through a separate message, which is not limited in particular.

[0274] In this way, after receiving the first address, the A-IoT terminal can write the second data and the third data into the storage area indicated by the first address in sequence according to the first address. For example, the first address includes a start address add1 and an end address add2, |add2-add1| = X, X is 240 bits. The second data and the third data are data received by the A-IoT terminal in sequence, and both are 60 bits. Then the A-IoT terminal can write 60 bits of the second data into the area corresponding to the first 60 bits of the 240 bits, and write 60 bits of the third data into the area corresponding to the 61st to 120th bits of the 240 bits, and so on.

[0275] Alternatively, the first device can also send the second address and the third address to the second device. The second device can receive the second device and the third address.

[0276] For example, the first apparatus is a first core network element, and the second apparatus is an A-IoT terminal. In the case that the A-IoT terminal succeeds in the random access, the first core network element can further obtain the first address from the service request #1, and segment the first address according to the segmenting manner of the first data to obtain a plurality of segments of addresses, such as N segments of addresses. The N segments of addresses can be consecutive addresses or non-consecutive addresses, which are not limited, and the sum of lengths of the N segments of addresses is equal to the length of the first address, such as |add2-add1|=X. The second address and the third address can be the first two segments of addresses in the N segments of addresses, and correspond to the second data and the third data, respectively. The first core network element can send the second address and the third address to the A-IoT terminal through the access network device, such as carrying the second address in the above-mentioned NAS message #2 and carrying the third address in the above-mentioned NAS message #3, or carrying the second address and the third address through separate messages, which are not limited. Alternatively, the first apparatus is a first access network device, and the second apparatus is an A-IoT terminal. In the case that the A-IoT terminal succeeds in the random access, the access network device can also obtain the first address from the service request #2, and segment the first address according to the segmenting manner of the first data to obtain N segments of addresses. For the second address and the third address, the access network device can send the second address and the third address to the A-IoT terminal, such as carrying the second address in the above-mentioned RRC message #2 and carrying the third address in the above-mentioned RRC message #3, or carrying the second address and the third address through separate messages, which are not limited.

[0277] In this way, after receiving the first address, the A-IoT terminal can write the second data into the storage area indicated by the second address and write the third data into the storage area indicated by the third address according to the first address.

[0278] It should be understood that, if the above-mentioned address is a default address of the A-IoT terminal, or the A-IoT terminal decides to write the first data to a position by itself, the first core network element or the access network device can not need to send the above-mentioned address, such as the first address, or the second address and the third address, to the A-IoT terminal, so as to reduce the overhead.

[0279] It should also be understood that the above-mentioned is an example of the second data and the third data, and the first data can also be segmented into more data, such as fourth data, fifth data, and the like, and the principle is similar to that of the second data and the third data, which can be understood by reference, and will not be described in detail.

[0280] Continue case 2:

[0281] 1) In the case that it is determined to receive the first data through the first mode, the first apparatus receives a first message from the second apparatus, such as sending a first address to the second apparatus first to receive a first message returned by the second apparatus according to the first address.

[0282] The first message can comprise the first data, and the first message can be the first uplink message for transmitting the service data, so as to improve transmission efficiency, or can be any uplink message for transmitting the service data, such as a NAS message, denoted as NAS message#a, or a RRC message, denoted as RRC message#a.

[0283] For example, the first device is a first core network element, and the second device is an A-IoT terminal.

[0284] In a case where the first core network element determines to send the first data through the first mode, the first core network element can acquire the first address from the service request#3, and send the first address to the A-IoT terminal through the access network device. For example, the first core network element can first send an N2 message carrying the first address to the access network device, or any other possible message. The access network device then sends a message carrying the first address to the A-IoT terminal, such as a selection message / paging message, or any other possible message. The A-IoT terminal can read the first data from the storage area indicated by the first address, and determine the length of the first data, such as a first length. The A-IoT terminal is pre-configured with a length threshold, and the A-IoT terminal can determine that the first data does not need to be segmented according to that the first length is less than or equal to the length threshold. In a transmission occasion of the first data, such as when the device identifier of the A-IoT terminal needs to be reported to the network in a random access process, or after the random access is completed, the A-IoT terminal can carry the first data into the NAS message#a, and send the NAS message#a to the first core network element through the access network device. The first core network element can receive the NAS message#a to acquire the first data. The first core network element can determine the size relationship between the length of the received data, such as the first data, and the first length. In this case, the length of the first data is equal to the first length, indicating that the data transmission of the A-IoT terminal is completed, and the first core network element can send the first data to the service requester.

[0285] For example, the first device is a first core network element, and the second device is an A-IoT terminal.

[0286] In case the access network device determines to send the first data by the first mode, the access network device can obtain the first address from the service request #4, and send the first address to the A-IoT terminal, such as sending a selection message / paging message carrying the first address, or any other possible message. The A-IoT terminal can also read the first data from the storage area indicated by the first address, and determine the first length. The A-IoT terminal is pre-configured with a length threshold, and the A-IoT terminal can determine that the first data does not need to be segmented according to that the first length is less than or equal to the length threshold. In the transmission occasion of the first data, such as when the device identifier of the A-IoT terminal needs to be reported to the network in the random access process, or after the random access is completed, the A-IoT terminal can carry the first data into the RRC message #a, and then send the RRC message #a to the access network device. The access network device can receive the RRC message #a to obtain the first data. The access network device can determine the size relationship between the length of the received data, such as the first data, and the first length. In this case, the length of the first data is equal to the first length, indicating that the data transmission of the A-IoT terminal is completed, and the access network device can send the first data to the first core network element, which is forwarded to the service requester again.

[0287] Additionally, in the above S601-S602, if the access network device does not determine the first length, such as being indicated by the first core network element through the transmission mode indication information whether to adopt the first mode or the second mode, then the access network device can determine whether the data from the A-IoT terminal is received again within a preset time period after receiving the data of the A-IoT terminal. If yes, it indicates that the data transmission of the A-IoT terminal is not completed, otherwise, it indicates that the data transmission of the A-IoT terminal is completed.

[0288] 2) In case of determining to receive the second data by the first mode, the first device receives the second message and the third message from the second device, such as sending the first address to the second device to receive the second message and the third message returned by the second device according to the first address.

[0289] The first data can include the second data and the third data, such as the second device can determine the second data and the third data according to the first data, that is, the first data can be segmented to obtain the second data and the third data.

[0290] The second message can comprise second data, and the third message can comprise third data. The first of the second message or the third message can be the first uplink message for transmitting service data, so as to reduce transmission delay, or the second message and the third message can also be any two uplink messages for transmitting service data, and the specific implementation is not limited. The second message and the third message can both be NAS messages, for example, denoted as NAS message #b and NAS message #c respectively, or the second message and the third message can both be RRC messages, for example, denoted as RRC message #b and RRC message #c respectively.

[0291] For example, the first device is a first core network element, and the second device is an A-IoT terminal.

[0292] In a case where the first core network element determines to send the first data by the second mode, the first core network element can obtain the first address from the service request #3, and send the first address to the A-IoT terminal through the access network device, and the specific implementation is as described above, and will not be described herein again. The A-IoT terminal can read the first data from the storage area indicated by the first address, and determine the length of the first data, for example, the first length. The A-IoT terminal is preconfigured with a length threshold, and the A-IoT terminal can divide the first data into multiple pieces of data according to the first length being greater than the length threshold, to obtain the second data and the third data, and the specific segmentation manner is similar to that of the first core network element described above, and can be understood with reference, and will not be described herein again.

[0293] In a case where the first data needs to be reported to the network in a transmission occasion, for example, a device identifier of the A-IoT terminal needs to be reported to the network in a random access process, or after the random access is completed, the A-IoT terminal can carry the second data into the NAS message #b, and send the NAS message #b to the first core network element through the access network device. The first core network element can receive the NAS message #b to obtain the second data. The first core network element can determine the length of the received data, for example, the second data, and the size relationship with the first length. In this case, the length of the second data is less than the first length, indicating that the data transmission of the A-IoT terminal is not completed, and the first core network element can continue to receive the data of the A-IoT terminal without data aggregation.

[0294] After sending the NAS message #a, the A-IoT terminal can also carry the third data into the NAS message #c, and send the NAS message #c to the first core network element through the access network device. The first core network element can receive the NAS message #c to obtain the third data. The first core network element can determine the size relationship between the length of the received data, such as the sum of the lengths of the second data and the third data, and the first length. In this case, if the sum of the lengths of the second data and the third data is less than the first length, it indicates that the data transmission of the A-IoT terminal is not completed, and the first core network element can continue to receive the data of the A-IoT terminal without data aggregation. If the sum of the lengths of the second data and the third data is equal to the first length, it indicates that the data transmission of the A-IoT terminal is completed, and the first core network element can perform data aggregation. For example, the first core network element can determine the first data according to the second data and the third data, such as concatenating the second data, the third data or other received data in sequence to obtain the first data. Then, the first core network element can send the first data to the service requester, that is, to provide the complete data to other entities / network elements on the network side through data aggregation.

[0295] For another example, the first device is an access network device, and the second device is an A-IoT terminal.

[0296] In the case where the access network device determines to send the first data through the second mode, the access network device can obtain the first address from the service request #4, and send the first address to the A-IoT terminal through the access network device, which is specifically described above and will not be repeated here. The A-IoT terminal can read the first data from the storage area indicated by the first address, and determine the length of the first data, such as the first length. The A-IoT terminal is preconfigured with a length threshold, and the A-IoT terminal can divide the first data into multiple pieces of data to obtain the second data and the third data according to that the first length is greater than the length threshold, and the specific segmentation manner is similar to that of the access network device described above, which can be understood with reference, and will not be repeated here.

[0297] At the sending time of the first data, such as when the device identifier of the A-IoT terminal needs to be reported to the network in the random access process, or after the random access is completed, the A-IoT terminal can carry the second data into the RRC message #b (or carried in the NAS message and sent to the access network device through the RRC message #b), and send the RRC message #b to the access network device. The access network device can receive the RRC message #b to obtain the second data. The access network device can determine the size relationship between the length of the received data, such as the second data, and the first length. In this case, the length of the second data is less than the first length, indicating that the data transmission of the A-IoT terminal is not completed, and the access network device can continue to receive the data of the A-IoT terminal without data aggregation.

[0298] After sending the RRC message #a, the A-IoT terminal can also carry the third data into the RRC message #c, and send the RRC message #c to the access network device. The access network device can receive the RRC message #c to obtain the third data. The access network device can determine the size relationship between the sum of the lengths of the second data and the third data and the first length. In this case, if the sum of the lengths of the second data and the third data is less than the first length, it indicates that the data transmission of the A-IoT terminal is not completed, and the access network device can continue to receive the data of the A-IoT terminal and does not perform data aggregation. If the sum of the lengths of the second data and the third data is equal to the first length, it indicates that the data transmission of the A-IoT terminal is completed, and the access network device can perform data aggregation. For example, the access network device can determine the first data according to the second data and the third data, such as sequentially splicing the second data, the third data or other received data to obtain the first data. The access network device can send the first data to the first core network element, which is forwarded to the service requester, that is, the complete data is provided to other entities / network elements on the network side through data aggregation.

[0299] It can be understood that in the above S601-S602, if the access network device does not determine the first length, such as being indicated by the first core network element through the sending mode indication information whether to adopt the first mode or the second mode, when the access network device receives the data of the A-IoT terminal, it can determine whether the data from the A-IoT terminal is received again within a preset time period. If yes, it indicates that the data transmission of the A-IoT terminal is not completed, otherwise, it indicates that the data transmission of the A-IoT terminal is completed.

[0300] Optionally, in the above case 2, the second device (e.g., the A-IoT terminal) can send the second message and the third message in a default manner. For example, after sending the second message, the second device can continue to send the third message by default without waiting for an indication from the first device, until the first data transmission is completed. Alternatively, the second device can also wait for an indication from the first device. For example, after receiving the first message of the second message and the third message, the first device (e.g., the access network device or the first core network element) can send first indication information to the second device. The first indication information can indicate the second device to continue to send data. The first indication information can be carried in an acknowledgement message returned by the second device in response to receiving the first message, or can be carried in a separate message, without limitation. Accordingly, the second device can continue to receive the second message and the third message according to the first indication information. At this time, if the first device still needs to send other messages after the second message and the third message to carry the part of the first data that has not been sent, the same applies, and will not be repeated here, until the first data transmission is completed. That is, whether the second device needs to continue to send data can be indicated by the first device, so as to avoid data transmission errors and ensure the reliability and stability of data transmission. Alternatively, the first device can carry information indicating that the data transmission is completed in the message carrying the last data of the first data. The second device can determine that the first data transmission is completed according to the indication information, and the first device does not need to provide the first indication information in each message to reduce the indication overhead.

[0301] It should also be understood that the scheme introduced in the above case 2 is only some examples and is not limiting. For example, the first device (e.g., the access network device or the first core network element) can also determine whether to send the address after segmentation to the second device (e.g., the A-IoT terminal) according to whether the data is segmented. If the data is not segmented, the access network device or the first core network element sends the first address to the A-IoT terminal, otherwise, sends the respective addresses of the segmented data, such as the second address, the third address, etc., to the A-IoT terminal. Accordingly, the A-IoT terminal does not need to determine whether the data is segmented, and can return the data read according to the address to the access network device or the first core network element in the uplink message by default.

[0302] It can also be understood that in the above case 2, if the second device (e.g., the A-IoT terminal) sends the RRC message or the NAS message when reporting the device identifier to the network, the RRC message or the NAS message can also include the device identifier of the second device.

[0303] Optionally, in the above case 1 or case 2:

[0304] If the first device is a first core network element and the second device is an A-IoT terminal, the first core network element can further send second indication information to the access network device in a case where the first core network element determines to transmit the first data through the first mode; or the first core network element can further send third indication information to the access network device in a case where the first core network element determines to transmit the first data through the second mode.

[0305] The second indication information can be carried in an N2 message or any other possible message, and the specific implementation is not limited. The second indication information can indicate that the access network device can continue to perform operations for other terminals after forwarding the first message, or in other words, indicate that the access network device can continue to perform operations for other terminals after forwarding the first message carrying data of the A-IoT terminal. In this case, the access network device does not need to wait for subsequent indication of the core network to trigger operations for other terminals, such as a random access process or a service process, to reduce latency and improve operation efficiency.

[0306] The third indication information can be carried in an N2 message or any other possible message, and the specific implementation is not limited. The third indication information can indicate that the access network device needs to perform operations for other terminals according to the indication of the core network element after forwarding the first message of the second message and the third message, or in other words, indicate that the access network device needs to perform operations for other terminals according to the indication of the core network element after forwarding the first message carrying data of the A-IoT terminal. For example, the first core network element can indicate the access network device to continue to perform operations for other terminals, such as sending an explicit information element to the access network device to explicitly indicate the access network device to continue to perform operations for other terminals, or sending a mask to the access network device for paging other terminals to implicitly indicate the access network device to continue to perform operations for other terminals, and the specific implementation is not limited. In this way, it can be avoided that the access network device performs operations for other terminals before transmitting the first data, which causes the first data transmission to fail, to ensure the reliability of data transmission.

[0307] If the first device is an access network device and the second device is an A-IoT terminal, the access network device can continue to perform operations for other terminals after sending the first message in a case where the access network device determines to transmit the first data through the first mode, to improve operation efficiency; and the access network device needs to perform operations for other terminals according to the indication of the core network after sending the first message of the second message and the third message in a case where the access network device determines to transmit the first data through the second mode. It can be understood that if the access network device can determine whether the first data transmission is complete by itself, the access network device can also continue to perform operations for other terminals after determining that the first data transmission is complete by itself, and does not need the indication of the core network.

[0308] Continue case 3:

[0309] The first device can be an A-IoT terminal, and the second device can be an access network device.

[0310] 1) In a case where it is determined to send the second data through the first mode, the A-IoT terminal can send a first message to the access network device.

[0311] The first message can include the first data. The first message can be the first uplink message for transmitting service data to improve transmission efficiency, or can be any uplink message for transmitting service data, such as RRC message #a.

[0312] For example, when the device identifier of the A-IoT terminal needs to be reported to the network at the transmission occasion of the first data, such as in a random access procedure, or after the random access is completed, the A-IoT terminal can carry the first data into the RRC message #a and send the RRC message #a to the access network device. The access network device can receive the RRC message #a to obtain the first data. Optionally, the RRC message #a can include at least one of the following: the first length, or information for indicating that the data transmission is completed.

[0313] The access network device can determine that the data transmission of the A-IoT terminal is completed according to the first length being the same as the length of the first data received by the access network device, or according to the information for indicating that the data transmission is completed. Alternatively, if the RRC message #a does not include the first length and the information for indicating that the data transmission is completed, the access network device can determine whether data from the A-IoT terminal is received again within a preset time period after receiving the data (such as the first data) of the A-IoT terminal, and if data from the A-IoT terminal is received again within the preset time period, it indicates that the data transmission of the A-IoT terminal is not completed, otherwise, it indicates that the data transmission of the A-IoT terminal is completed. In this way, the access network device can send the first data to the first core network element, which is forwarded to the service requester.

[0314] Additionally, in a case where the access network device determines that the data transmission of the A-IoT terminal is completed, the access network device can also trigger operations for other terminals, such as a random access procedure.

[0315] 2) In a case where it is determined to send the first data through the second mode, the A-IoT terminal can send a second message and a third message to the access network device.

[0316] The first message can comprise the second data and the third data. The first message in the second message or the third message can be the first uplink message for transmitting the service data, or the second message and the third message can also be any two uplink messages for transmitting the service data, and the specific limitation is not made. The second message and the third message can be RRC messages, such as RRC message #b and RRC message #c.

[0317] For example, for the second mode, the A-IoT terminal can determine the second data and the third data according to the first data, such as segmenting the first data to obtain the second data and the third data, and the specific segmentation manner is similar to the above-mentioned first core network element, which can be understood with reference, and will not be repeated here. In the sending occasion of the first data, such as the random access process needs to report the device identifier of the A-IoT terminal to the network, or after the random access is completed, the A-IoT terminal can send multiple RRC messages to the access network device for transmitting the first data, such as RRC message #b, RRC message #c, and the specific principle is similar to the A-IoT terminal in the above case 2, which can be understood with reference, and will not be repeated here.

[0318] Optionally, any RRC message in the above-mentioned multiple RRC messages can carry the first length, and / or the last RRC message in the multiple RRC messages can carry the information for indicating the completion of data transmission.

[0319] The access network device can determine the completion of data transmission of the A-IoT terminal according to the first length being the same as the length of the data received by the access network device, or according to the information for indicating the completion of data transmission. Or, if the above-mentioned RRC message does not contain the first length and the information for indicating the completion of data transmission, the access network device can determine whether the data from the A-IoT terminal is received again within a preset time period after receiving the data of the A-IoT terminal, if yes, it indicates that the data transmission of the A-IoT terminal is not completed, otherwise, it indicates that the data transmission of the A-IoT terminal is completed. In this way, the access network device can aggregate the received data to obtain the first data, send the first data to the first core network element, and forward the first data to the service requester by the first core network element.

[0320] Optionally, in the procedure of the above case 3, the first device (such as the A-IoT terminal) can send the second message and the third message in a default manner, i.e., the first device continues to send the third message by default after sending the second message until the first data transmission is completed. Alternatively, the first device can also indicate the transmission of the messages, i.e., after sending the first message in the second message and the third message, the first device can further send fourth indication information to the second device (such as the access network device or the first core network network element). The fourth indication information can indicate that the first device continues to send data. That is, whether the second device needs to continue to wait to receive data can be indicated by the first device to ensure the stability and reliability of data transmission. At this time, if the first device still sends other messages after the second message and the third message to carry the part of the first data that has not been sent, the same reasoning applies, and details are not repeated, until the first data transmission is completed.

[0321] It should be understood that the RRC message described above is an example, and other types of messages can also be replaced, without limitation. For example, the message sent by the AIoT terminal to the reader can be referred to as a D2R message (Device to Reader, D2R), and the message sent by the reader to the AIoT terminal can be referred to as a R2D message (Reader to Device, R2D).

[0322] It should also be understood that in the above S601-S603, the access network device can also be considered as a reader, or a reader in other device forms, or the access network device can also be replaced by a terminal device, such as a terminal supporting reader functions.

[0323] In summary, in the case where the first length of the first data is different, or the data amount of the first data is different, the first data can be transmitted in different modes. For example, if the first length is relatively small, the first device can transmit the first data through the first mode, such as through the first message, to ensure the efficiency of data transmission. If the first length is relatively large, the first device can transmit the first data through the second mode, such as through the second message and the third message, to avoid transmission failure due to the first message being unable to transmit the first data, and thus the reliability of data transmission can be ensured.

[0324] The above describes the arrangement procedure of the communication method provided by the embodiments of the present application in combination with FIG. 6. The specific procedure of the communication method provided by the embodiments of the present application is described in detail in combination with FIGS. 7-8.

[0325] FIG. 7 is a flow diagram of a communication method according to an embodiment of the present application. As shown in FIG. 7, the flow involves an AF (e.g., a service requester), a NEF network element, a UDM / UDR network element (e.g., a second core network element), an A-IoTMF network element (e.g., a first core network element), a reader (e.g., an access network device or a terminal device supporting a reader function), and an A-IoT terminal.

[0326] Specifically, as shown in FIG. 7, the flow of the communication method is as follows:

[0327] S700, the UDM / UDR network element preconfigures a length threshold.

[0328] The length threshold can refer to the related description of the length threshold in FIG. 6 above, and will not be repeated here.

[0329] It should be understood that S700 is optional, and the length threshold can also be dynamically determined.

[0330] Optionally, the data length that the UDM / UDR network element can preconfigure in S700 can be at least one of the lengths (including the first length), such as information at the granularity of a service requester, a service, or a terminal / device. For details, please refer to the related description of the at least one length above, and will not be repeated here.

[0331] The data length of the A-IoT terminal can be the length of the data of the A-IoT device, such as the first length of the first data above. For details, please refer to the related description of the first length above, and will not be repeated here.

[0332] S701, the AF sends a service request to the NEF network element.

[0333] For a write scenario / write operation, the service request (e.g., service request #1 above) can include at least one of the following: first data, an identifier of a service requester, a service type (write operation), a device identifier (which can be a device identifier prefix in particular), a data length, or a first address. For details, please refer to the related description of the service request #1 above, and will not be repeated here.

[0334] For a read scenario / read operation, the service request (e.g., service request #3 above) can include at least one of the following: first data, an identifier of a service requester, a service type (read operation), a device identifier, a data length, or a first address. For details, please refer to the related description of the service request #3 above, and will not be repeated here.

[0335] S702, the NEF network element sends the service request to the A-IoTMF network element.

[0336] The service request in S702 can be the same message as the service request in S701, or can be a different message, without limitation. If the service request in S702 is a different message, the service request in S702 can also include the content of the service request in S701, i.e., the NEF network element obtains the content of the service request in S701 and carries it in the service request in S702.

[0337] In an implementation manner, the AF can also directly send a service request to the A-IoTMF (e.g., when the AF is trusted).

[0338] In S703, the A-IoTMF network element determines whether the first data needs to be transmitted in segments.

[0339] The A-IoTMF network element can determine the first length, e.g., according to the first address or the first data in the service request, or obtain the first length from the UDM / UDR network element. The A-IoTMF network element can determine whether the first data needs to be transmitted in segments according to whether the first length is greater than a length threshold, e.g., whether to send the first data in segments, or whether to receive the first data in segments, i.e., the first mode and the second mode described above. For details, refer to the related description of the first mode and the second mode, which will not be repeated here.

[0340] It can be understood that for a write scenario / write operation, if the first data does not need to be sent in segments, S704-S706 are executed, and if the first data needs to be sent in segments, S707-S710 are executed. For a read scenario / read operation, if the first data does not need to be received, S711-S713 are executed, and if the first data needs to be received in segments, S714-S718 are executed.

[0341] In S704, the A-IoTMF network element sends an N2 message to the reader.

[0342] In S704, the N2 message can include at least one of the following: the device identification prefix, the service type (write operation), or the second indication information. The second indication information can indicate that the reader can continue to perform operations for other terminals after forwarding the first message carrying the data of the A-IoT terminal. For details, refer to the related description of the second indication information, which will not be repeated here.

[0343] In S705a, the reader sends a selection message or a paging message.

[0344] The selection message or the paging message carries at least one of the following: the device identification prefix, or the service type (write operation).

[0345] In S705b, the A-IoT terminal performs random access.

[0346] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0347] In the random access procedure, the A-IoT terminal can report its complete device identity, such as an EPC or an operator-assigned identity, and the A-IoT MF network element obtains the complete device identity and determines that the A-IoT terminal successfully performs random access, and proceeds to S706.

[0348] S706, the A-IoT MF network element sends a DL NAS message to the A-IoT terminal.

[0349] In S706, the DL NAS message can include first data, i.e., no segmentation.

[0350] The A-IoT terminal can write the received first data into a storage area. Alternatively, the DL NAS message can also carry an address indicating the storage area, such as a first address, and the A-IoT terminal can write the first data into the corresponding storage area according to the received first address. For details, refer to the description of the first address above, which will not be repeated here. Alternatively, the DL NAS message can not carry the first address, and the A-IoT terminal can decide where to write the received data, or write it to a default (such as a protocol predefined or preconfigured) location. It can be understood that in the case where the A-IoT MF network element does not segment the first data, the reader can perform the operation for other terminals, such as sending a selection message or a paging message for other terminals, by default after forwarding the DL NAS message in S707 to the A-IoT terminal.

[0351] S707, the A-IoT MF network element sends an N2 message to the reader.

[0352] In S707, the N2 message can include at least one of the following: a device identity prefix, a service type (write operation), or third indication information. The third indication information can indicate that the reader needs to perform an operation for other terminals according to the indication of the core network element after forwarding the first message carrying the data of the A-IoT terminal. For details, refer to the description of the third indication information above, which will not be repeated here.

[0353] S708a, the reader sends a selection message or a paging message.

[0354] The selection message or the paging message carries at least one of the following: a device identity prefix, or a service type (write operation).

[0355] S708b, the A-IoT terminal performs random access.

[0356] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0357] In the random access procedure, the A-IoT terminal can report its complete device identity, such as EPC or operator-assigned identity, and the A-IoT MF network element obtains the complete device identity and determines that the A-IoT terminal succeeds in random access, and continues to perform S709.

[0358] S709, the A-IoT MF network element sends a DL NAS message #1 to the A-IoT terminal.

[0359] The DL NAS message #1 can include second data. The second data is a segment of the first data, i.e., segmented transmission, which can be understood with reference to the above description of the second data, and will not be repeated here.

[0360] S710, the A-IoT MF network element sends a DL NAS message #2 to the A-IoT terminal.

[0361] The DL NAS message #2 can include third data. The third data is another segment of the first data, which can be understood with reference to the above description of the third data, and will not be repeated here.

[0362] In S709-S710, the A-IoT terminal can write the received second data and third data into a storage area. Alternatively, the above DL NAS message can also carry an address indicating the storage area, such as the DL NAS message #1 carrying the first address, and the DL NAS message #1 carrying the second address, and the DL NAS message #2 carrying the third address, i.e., the address after segmentation. The A-IoT terminal can write the second data and the third data into the corresponding storage area according to the received address. For details, please refer to the above description of the first address, the second address and the third address, which will not be repeated here. Alternatively, the above DL NAS message can also not carry an address indicating the storage area, and the A-IoT terminal can decide by itself where to write the received data.

[0363] It can be understood that the segmentation of the first data can also include fourth data, fifth data, etc., and the principle is similar, which can be understood, and will not be repeated here. In addition, in the case of the A-IoT MF network element segmenting the first data, the reader needs to wait for the instruction of the network after forwarding the DL NAS message #1 in S708 to the A-IoT terminal, such as after S709-S710, the A-IoT MF network element sends the first data, and the A-IoT MF network element can instruct the reader to perform operations for other terminals.

[0364] S711, the A-IoT MF network element sends an N2 message to the reader.

[0365] In S711, the N2 message can comprise at least one of: the device identity prefix, the service type (write operation), or the second indication information, which can be referred to the related description of the second indication information above, and will not be repeated here.

[0366] S711a, the reader sends a selection message or a paging message.

[0367] The selection message or the paging message carries at least one of: the device identity prefix, or the service type (write operation).

[0368] S711b, the A-IoT terminal performs random access.

[0369] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0370] S712, the A-IoT terminal sends an UL NAS message to the A-IoT MF network element.

[0371] In S712, the UL NAS message can comprise the first data, i.e. no segmentation is performed. Alternatively, the UL NAS message can further comprise the complete device identity of the A-IoT terminal, and the UL NAS message can be sent after the A-IoT MF network element reports the EPC.

[0372] The A-IoT terminal can read the first data from a storage area. Alternatively, the A-IoT MF network element indicates the address of the storage area, such as the first address, which can be sent by the reader to the A-IoT terminal in the N2 message of S711, or sent to the A-IoT terminal through a read command, so that the A-IoT terminal reads the first data from the storage area according to the first address, which can be referred to the related description of the first address above, and will not be repeated here. Alternatively, the A-IoT MF network element can not indicate the first address, and the A-IoT terminal knows the data storage position in advance (such as protocol predefinition or preconfiguration). It can be understood that in the case that the A-IoT MF network element does not segment the first data, the reader can perform the operation for other terminals by default after forwarding the UL NAS message in S712 to the A-IoT MF network element, such as sending other terminal selection messages or paging messages.

[0373] S713, the A-IoT MF network element sends the first data to the AF.

[0374] The A-IoT MF network element can determine that the data transmission is completed, such as the sum of the lengths of the received data is the first length, i.e. the first data is received. The AF can send the first data to the AF (such as through the NEF), which can be referred to the related description of S603 above, and will not be repeated here.

[0375] S714, the A-IoTMF network element sends an N2 message to the reader.

[0376] In S714, the N2 message can include at least one of the following: the device identification prefix, the service type (write operation), or the third indication information. The third indication information can refer to the above-mentioned related description of the third indication information, and will not be repeated here.

[0377] S715a, the reader sends a selection message or a paging message.

[0378] The selection message or the paging message carries at least one of the following: the device identification prefix, or the service type (write operation).

[0379] S715b, the A-IoT terminal performs random access.

[0380] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0381] S716, the A-IoT terminal sends an UL NAS message #1 to the A-IoTMF network element.

[0382] The UL NAS message #1 can include the second data. The second data is a segment of the first data, that is, segmented transmission, which can refer to the above-mentioned related description of the second data, and will not be repeated here. Optionally, the UL NAS message #1 can also include the complete device identification of the A-IoT terminal, such as EPC, or the UL NAS message #1 can also be sent after the A-IoT terminal reports the EPC.

[0383] S717, the A-IoT terminal sends an UL NAS message #2 to the A-IoTMF network element.

[0384] The UL NAS message #2 can include the third data. The third data is another segment of the first data, which can refer to the above-mentioned related description of the third data, and will not be repeated here. The UL NAS message #2 can be sent by default by the A-IoT terminal, such as sending the UL NAS message #1 by default and then continuing to send the UL NAS message #2, or it can also be sent according to the indication of the A-IoTMF network element, such as the above-mentioned first indication information, such as the A-IoTMF network element receiving the UL NAS message #1 and instructing the A-IoT terminal to continue transmission, and the A-IoT terminal sends the UL NAS message #2 according to the indication. The above-mentioned related description of S603 can also be referred to, and will not be repeated here.

[0385] In S716-S717, the A-IoT terminal can read the second data and the third data from the storage area. Optionally, the A-IoT MF network element indicates the address of the storage area, such as the first address, or the second address and the third address, which is sent to the A-IoT terminal by the reader in the N2 message carrying S711, or is sent to the A-IoT terminal by the read command, so that the A-IoT terminal reads the second data and the third data from the storage area according to the received address. For details, refer to the above description of the first address, the second address, and the third address, which will not be repeated here. Alternatively, the A-IoT MF network element can not indicate the address, and the A-IoT terminal knows the data storage location in advance (such as protocol predefinition or preconfiguration).

[0386] It can be understood that the segmentation of the first data can also include the fourth data, the fifth data, and the like, and the principle is similar, which can be understood with reference, and will not be repeated here. In addition, in the case where the A-IoT MF network element segments and sends the first data, the reader needs to wait for the indication of the network after forwarding the UL NAS message #1 in S715 to the A-IoT MF, such as after S716-S717, such as after the A-IoT MF network element receives the first data, the A-IoT MF network element can instruct the reader to perform operations for other terminals.

[0387] S718, the A-IoT MF network element sends the first data to the AF.

[0388] The A-IoT MF network element can determine that the data transmission is complete, such as the sum of the lengths of the received segmented data is the first length, the A-IoT MF network element aggregates the received segmented data to obtain the first data, and sends the first data to the AF (such as through the NEF). For details, refer to the above description of S603, which will not be repeated here.

[0389] FIG. 8 is a flow diagram of a communication method according to an embodiment of the present application. As shown in FIG. 8, the flow involves an AF (such as a service requester), a NEF network element, a UDM / UDR network element (such as a second core network element), an A-IoT MF network element (such as a first core network element), a reader (such as an access network device or a terminal device supporting a reader function), and an A-IoT terminal.

[0390] Specifically, as shown in FIG. 8, the flow of the communication method is as follows:

[0391] S800, the UDM / UDR network element preconfigures a length threshold.

[0392] S801, the AF sends a service request to the NEF network element.

[0393] S802, the NEF network element sends a service request to the A-IoT MF network element.

[0394] S800-S802 can also refer to the above-mentioned S700-S702, and will not be repeated here.

[0395] S803, the A-IoTMF network element sends an N2 message to the reader.

[0396] In S803, the N2 message can include a service request, such as for a write scenario / write operation, the service request (such as the above-mentioned service request #2) can include at least one of the following: first data, identity of the service requestor, service type (write operation), device identity (which can be a device identity prefix in particular), data length, first address or length threshold, which can refer to the above-mentioned service request #2 for details, and will not be repeated here; for a read scenario / read operation, the service request (such as the above-mentioned service request #4) can include at least one of the following: first data, identity of the service requestor, service type (read operation), device identity, data length, first address or length threshold, which can refer to the above-mentioned service request #4 for details, and will not be repeated here.

[0397] S804, the reader determines whether the first data needs to be transmitted in segments.

[0398] The reader can determine the first length, such as according to the first address or the first data in the service request, or obtain the first length from the UDM / UDR network element. The reader can determine whether the first data needs to be transmitted in segments according to whether the first length is greater than the length threshold, such as whether to send the first data in segments or whether to receive the first data in segments, that is, the above-mentioned first mode and second mode, which can also refer to the above-mentioned first mode and second mode for details, and will not be repeated here.

[0399] Alternatively, whether the first data needs to be transmitted in segments can still be determined by the A-IoTMF network element, indicating whether the reader adopts the first mode or the second mode, such as through the N2 message of S803.

[0400] It can be understood that for a write scenario / write operation, if the first data does not need to be sent in segments, the following S804a-S805 is executed, and if the first data needs to be sent in segments, the following S806a-S808 is executed. For a read scenario / read operation, if the first data does not need to be received, the following S809a-S812 is executed, and if the first data needs to be received in segments, the following S813a-S817 is executed.

[0401] S805a, the reader sends a selection message or a paging message.

[0402] The selection message or the paging message carries at least one of the following: device identity prefix, or service type (write operation).

[0403] S805b, the A-IoT terminal performs random access.

[0404] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0405] In the random access procedure, the A-IoT terminal can report its complete device identity, such as EPC or operator-assigned identity, and the A-IoT MF network element obtains the complete device identity to determine that the A-IoT terminal successfully performs random access and continues to perform S805.

[0406] S806, the reader sends an RRC message to the A-IoT terminal.

[0407] In S805, the RRC message can include first data, i.e., no segmentation.

[0408] The A-IoT terminal can write the received first data into a storage area. Alternatively, the RRC message can also carry an address indicating the storage area, such as a first address. The A-IoT terminal can write the first data into the corresponding storage area according to the received first address. For details, refer to the above description of the first address, which is not repeated here. Alternatively, the RRC message can not carry the first address. The A-IoT terminal can decide by itself where to write the received data, or write it to a default (such as protocol predefined or preconfigured) location. It can be understood that in the case that the A-IoT MF network element does not segment the first data, the reader can perform the operation for other terminals, such as sending other terminal selection messages or paging messages, by default after forwarding the RRC message in S805 to the A-IoT terminal.

[0409] S806a, the reader sends a selection message or a paging message.

[0410] The selection message or the paging message carries at least one of the following: device identity prefix, or service type (write operation).

[0411] S806b, the A-IoT terminal performs random access.

[0412] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0413] In the random access procedure, the A-IoT terminal can report its complete device identity, such as EPC or operator-assigned identity, and the A-IoT MF network element obtains the complete device identity to determine that the A-IoT terminal successfully performs random access and continues to perform S807.

[0414] S807, the reader sends an RRC message #1 to the A-IoT terminal.

[0415] The RRC message #1 can comprise second data. The second data is one segment of the first data, i.e., segment transmission, which can be understood with reference to the above description of the second data, and thus will not be repeated here.

[0416] At S808, the reader sends an RRC message #2 to the A-IoT terminal.

[0417] The RRC message #2 can comprise third data. The third data is another segment of the first data, which can be understood with reference to the above description of the third data, and thus will not be repeated here.

[0418] In S807-S808, the A-IoT terminal can write the received second data and third data into the storage area. Alternatively, the above RRC message can also carry an address indicating the storage area, such as the first address carried by the RRC message #1, or the second address carried by the RRC message #1 and the third address carried by the RRC message #2, i.e., the address after segmentation, the A-IoT terminal can write the second data and the third data into the corresponding storage area according to the received address, which can be understood with reference to the above description of the first address, the second address and the third address, and thus will not be repeated here. Alternatively, the above RRC message can also not carry an address indicating the storage area, and the A-IoT terminal can decide by itself where to write the received data.

[0419] It can be understood that the segmentation of the first data can also include fourth data, fifth data, etc., which has a similar principle and can be understood with reference, and thus will not be repeated here. In addition, in the case where the reader segments the first data, the reader cannot continue to perform operations for other terminals after sending the RRC message #1 in S808 to the A-IoT terminal, and needs to continue to perform operations for other terminals after sending the first data, such as S807-S808.

[0420] At S809a, the reader sends a selection message or a paging message.

[0421] The selection message or the paging message carries at least one of the following: a device identification prefix, or a service type (write operation).

[0422] At S809b, the A-IoT terminal performs random access.

[0423] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0424] At S810, the A-IoT terminal sends an RRC message to the reader.

[0425] In S812, the RRC message can include the first data, i.e. no segmentation is performed. Optionally, the RRC message can also include the complete device identity of the A-IoT terminal, such as the EPC, or the RRC message can also be sent after the A-IoT terminal reports the EPC.

[0426] The A-IoT terminal can read the first data from the storage area. Optionally, the reader indicates the address of the storage area, such as the first address, which can be sent to the A-IoT terminal in a separate message, such as a read command, for the A-IoT terminal to read the first data from the storage area according to the first address. For details, refer to the description of the first address above, which will not be repeated here. Alternatively, the reader can not indicate the first address, and the A-IoT terminal knows the location of the data storage in advance (such as pre-defined or pre-configured by the protocol). It can be understood that in the case where the reader does not segment the first data, the reader can receive the S810, and by default, perform operations for other terminals, such as sending other terminal selection messages or paging messages.

[0427] S811, the reader sends the first data to the A-IoT MF network element.

[0428] S812, the A-IoT MF network element sends the first data to the AF.

[0429] The reader can determine that the data transmission is complete, such as the sum of the lengths of the received data is the first length, i.e. the first data is received, and thus sends the first data to the A-IoT MF network element. The AF can send the first data to the AF (such as through the NEF). For details, refer to the description of S603 above, which will not be repeated here.

[0430] S813a, the reader sends a selection message or a paging message.

[0431] The selection message or the paging message carries at least one of the following: a device identity prefix, or a service type (write operation).

[0432] S813b, the A-IoT terminal performs random access.

[0433] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0434] S814, the A-IoT terminal sends an RRC message #1 to the reader.

[0435] The RRC message #1 can comprise second data. The second data is one segment of the first data, i.e., segmented transmission, which can be understood with reference to the above description of the second data, and thus will not be repeated here. Optionally, the RRC message #1 can also comprise a complete device identity of the A-IoT terminal, such as an EPC, or the RRC message #1 can also be sent after the A-IoT terminal reports the EPC.

[0436] S815, the A-IoT terminal sends an RRC message #2 to the reader.

[0437] The RRC message #2 can comprise third data. The third data is another segment of the first data, which can be understood with reference to the above description of the third data, and thus will not be repeated here. The RRC message #2 can be sent by default by the A-IoT terminal, such as sending the RRC message #1 and then continuing to send the RRC message #2 by default, or can also be sent according to an indication of the reader, such as the reader receiving the RRC message #1, instructing the A-IoT terminal to continue transmission, and the A-IoT terminal sending the RRC message #2 according to the indication. Details can be understood with reference to the above description of S603, and thus will not be repeated here.

[0438] In S814-S815, the A-IoT terminal can read the second data and the third data from a storage area. Optionally, the reader can indicate the address of the storage area to the terminal, such as a first address, or a second address and a third address, which can be sent to the A-IoT terminal through a read command, so that the A-IoT terminal reads the second data and the third data from the storage area according to the received address. Details can be understood with reference to the above description of the first address, the second address, and the third address, and thus will not be repeated here. Or the reader can not indicate the address, and the A-IoT terminal knows the data storage location in advance (such as protocol predefinition or preconfiguration).

[0439] It can be understood that the segments of the first data can also comprise fourth data, fifth data, etc., the principle of which is similar and can be understood, and thus will not be repeated here. In addition, in the case of segmented reception of the first data by the reader, the reader cannot continue to perform operations for other terminals after receiving the RRC message #1 in S814 to the A-IoT terminal, and needs to continue to perform operations for other terminals after receiving the first data, such as S814-S815.

[0440] S816, the reader sends the first data to an A-IoT MF network element.

[0441] S817, the A-IoT MF network element sends the first data to an AF.

[0442] The reader can determine that the data transmission is completed, such as the sum of the lengths of the received segmented data is a first length, the reader aggregates the received segmented data to obtain first data, and then sends the first data to the A-IoTMF network element. The A-IoTMF network element can send the first data to the AF (such as through the NEF), and details can also be referred to the related description of S603, which will not be repeated here. FIG. 9 is a flowchart of a communication method provided by an embodiment of the present application. As shown in FIG. 9, the flow involves an AF (such as a service requester), a NEF network element, a UDM / UDR network element (such as a second core network element), an A-IoTMF network element (such as a first core network element), a reader (such as an access network device or a terminal device supporting a reader function), and an A-IoT terminal.

[0443] Specifically, as shown in FIG. 9, the flow of the communication method is as follows:

[0444] S900a, the UDM / UDR network element preconfigures a length threshold.

[0445] S900a can also refer to the related description of S700, which will not be repeated here.

[0446] S900b, the A-IoT terminal preconfigures a length threshold.

[0447] The length threshold can also refer to the related description of the length threshold, and S900b is optional. The A-IoT terminal can also obtain the length threshold through S904 described below.

[0448] S901, the AF sends a service request to the NEF network element.

[0449] S902, the NEF network element sends a service request to the A-IoTMF network element.

[0450] S901-S902 can also refer to the related description of S701-S702, which will not be repeated here.

[0451] S903, the A-IoTMF network element sends an N2 message to the reader.

[0452] In S903, the N2 message can include a service request, such as for a reading scenario / reading operation. The service request (such as the service request #4 described above) can include at least one of the following: first data, an identifier of the service requester, a service type (reading operation), a device identifier, a data length, a first address, or a length threshold. Details can be referred to the related description of the service request #4, which will not be repeated here.

[0453] S904a, the reader sends a selection message or a paging message.

[0454] The selection message or the paging message carries at least one of the following: a device identification prefix, or a service type (write operation), or a length threshold. The length threshold can be determined by the reader according to the state of the link, or obtained from the UDM / UDR network element / A-IoT MF network element.

[0455] S904b, the A-IoT terminal performs random access.

[0456] The A-IoT terminal can perform random access according to the selection message or the paging message.

[0457] S905, the A-IoT terminal determines whether the first data needs to be transmitted in segments.

[0458] The A-IoT terminal can receive a read command of the reader, which can be carried in a service request, delivered to the A-IoT terminal with an N2 message and a selection message or a paging message in a random access process, or also sent to the A-IoT terminal after the random access is successful. The A-IoT terminal can obtain the first data from the storage area corresponding to the first address according to the read command, and determine the first length. The A-IoT terminal can determine whether the first data needs to be transmitted in segments according to whether the first length is greater than the length threshold, such as whether to transmit the first data in segments, or whether to receive the first data in segments, that is, the first mode and the second mode described above. For details, please refer to the related introduction of the first mode and the second mode, which will not be repeated here.

[0459] If the A-IoT terminal does not need to transmit the first data in segments, it performs the following S906-S909, and if the A-IoT terminal needs to transmit the first data in segments, it performs the following S909-S908.

[0460] S906, the A-IoT terminal sends an RRC message to the reader.

[0461] In S906, the RRC message can include the first data, that is, no segmentation. Alternatively, if the read command is sent to the A-IoT terminal in the random access process, the RRC message can also include the complete device identification of the A-IoT terminal, such as EPC, that is, data fast transmission, or if the read command is sent to the A-IoT terminal after the random access is successful, the RRC message can also be sent after the A-IoT terminal reports the EPC.

[0462] S907, the reader sends the first data to the A-IoT MF network element.

[0463] S908, the A-IoT MF network element sends the first data to the AF.

[0464] The reader can determine that the data transmission is completed, such as the sum of the lengths of the received data is a first length, i.e., the first data is received, and thus sends the first data to the A-IoT MF network element. The AF can send the first data to the AF (e.g., through the NEF), and details can also be referred to the related description of S603 above, which will not be repeated here.

[0465] S909, the A-IoT terminal sends an RRC message #1 to the reader.

[0466] The RRC message #1 can include second data. The second data is a segment of the first data, i.e., segmented transmission, and details can be referred to the related description of the second data above, which will not be repeated here. Alternatively, similar to S906, the RRC message #1 can also include the complete device identifier of the A-IoT terminal, such as the EPC, or the RRC message #1 can be sent after the A-IoT terminal reports the EPC.

[0467] S910, the A-IoT terminal sends an RRC message #2 to the reader.

[0468] The RRC message #2 can include third data. The third data is another segment of the first data, and details can be referred to the related description of the third data above, which will not be repeated here. The RRC message #2 can be sent by default by the A-IoT terminal, such as sending the RRC message #1 and then continuing to send the RRC message #2 by default, or can be sent according to the indication of the reader, such as the reader receiving the RRC message #1 and instructing the A-IoT terminal to continue transmission, and the A-IoT terminal sends the RRC message #2 according to the indication. Details can also be referred to the related description of S603 above, which will not be repeated here.

[0469] Alternatively, the A-IoT terminal can send an indication to the reader after sending RRC #1, such as the fourth indication information described above, to indicate that the data transmission has not ended, and then send RRC #2, and / or the A-IoT terminal can also carry an indication in the RRC message where the last segment data is located to indicate that the data transmission is complete. Details can also be referred to the related description of S603 above, which will not be repeated here.

[0470] It can be understood that the segmentation of the first data can also include fourth data, fifth data, etc., and the principle is similar, which can be understood by reference, and will not be repeated here. In addition, the reader needs to determine the completion of the first data transmission according to the indication of the A-IoT terminal or by itself, and then continue to perform operations for other terminals.

[0471] S911, the reader sends the first data to the A-IoT MF network element.

[0472] S912, the A-IoT MF network element sends the first data to the AF.

[0473] The reader can determine that the data transmission is completed, such as the sum of the lengths of the received segmented data is a first length, the reader aggregates the received segmented data to obtain first data, and then sends the first data to the A-IoTMF network element. The A-IoTMF network element can send the first data to the AF (such as through the NEF), and details can also be referred to the related description of S603 above, which will not be described here.

[0474] FIG. 10 is a structural schematic diagram of a communication apparatus according to an embodiment of the present application. As an example, as shown in FIG. 10, the communication apparatus 1000 includes a transceiver module 1002 and a processing module 1001. For ease of illustration, FIG. 10 only shows the main components of the communication apparatus.

[0475] The communication apparatus 1000 can be applied to the communication method shown in FIGS. 6-9 above to realize the corresponding functions. For example, the transceiver module 1002 can be used to realize the transceiving function in the communication method shown in FIGS. 6-9 above, and the processing module 1001 can be used to realize the functions other than the transceiving function in the communication method shown in FIGS. 6-9 above.

[0476] Optionally, the transceiver module 1002 can include a sending module (not shown in FIG. 10) and a receiving module (not shown in FIG. 10). The sending module is used to realize the sending function of the communication apparatus 1000, and the receiving module is used to realize the receiving function of the communication apparatus 1000.

[0477] Optionally, the communication apparatus 1000 can further include a storage module (not shown in FIG. 10), which stores programs or instructions. When the processing module 1001 executes the programs or instructions, the communication apparatus 1000 can execute the functions in the method shown in FIGS. 5-8 above.

[0478] It can be understood that the communication apparatus 1000 can be a network device, a chip (system) or other components or assemblies that can be arranged in the network device, or an apparatus containing the network device, and the present application does not limit this.

[0479] In addition, the technical effects of the communication apparatus 1000 can refer to the technical effects of the communication method described above, which will not be described here.

[0480] FIG. 11 is a structural schematic diagram of a communication apparatus according to an embodiment of the present application. As an example, the communication apparatus can be a terminal, or a chip (system) or other components or assemblies that can be arranged in the terminal. As shown in FIG. 11, the communication apparatus 1100 can include a processor 1101. Optionally, the communication apparatus 1100 can further include a memory 1102 and / or a transceiver 1103. The processor 1101 is coupled with the memory 1102 and the transceiver 1103, such as can be connected through a communication bus.

[0481] The various constituent components of the communication apparatus 1100 will be described in detail below in conjunction with FIG. 11:

[0482] The processor 1101 is the control center of the communication apparatus 1100, and can be one processor or collectively refer to a plurality of processing elements. For example, the processor 1101 can be one or more central processing units (CPUs), application specific integrated circuits (ASICs), or one or more integrated circuits configured to perform the functions of the embodiments of the present application, such as one or more microprocessors (digital signal processors (DSPs)), or one or more field programmable gate arrays (FPGAs).

[0483] Optionally, the processor 1101 can perform various functions of the communication apparatus 1100 by running or executing software programs stored in the memory 1102, and calling data stored in the memory 1102, such as the communication methods shown in FIGS. 6-9 described above.

[0484] In a specific implementation, as an embodiment, the processor 1101 can include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 11.

[0485] In a specific implementation, as an embodiment, the communication apparatus 1100 can also include a plurality of processors, such as the processor 1101 and the processor 1104 shown in FIG. 11. Each of these processors can be a single-CPU or a multi-CPU. The processor here can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0486] The memory 1102 is configured to store software programs for implementing the solutions of the present application, and the processor 1101 is configured to control the execution. The specific implementation can refer to the above method embodiments, and will not be described here.

[0487] Optionally, the memory 1102 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, a magnetic disk storage or other magnetic storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this. The memory 1102 can be integrated with the processor 1101 or exist independently and be coupled to the processor 1101 through the interface circuit (not shown in FIG. 11) of the communication apparatus 1100, and the embodiments of the present application do not make a specific limitation in this regard.

[0488] The transceiver 1103 is configured to communicate with other communication apparatuses. For example, the communication apparatus 1100 is a terminal, and the transceiver 1103 can be configured to communicate with a network device or another terminal. For another example, the communication apparatus 1100 is a network device, and the transceiver 1103 can be configured to communicate with a terminal or another network device.

[0489] Optionally, the transceiver 1103 can include a receiver and a transmitter (not shown in FIG. 11). The receiver is configured to implement the receiving function, and the transmitter is configured to implement the transmitting function.

[0490] Optionally, the transceiver 1103 can be integrated with the processor 1101 or exist independently and be coupled to the processor 1101 through the interface circuit (not shown in FIG. 11) of the communication apparatus 1100, and the embodiments of the present application do not make a specific limitation in this regard.

[0491] It can be understood that the structure of the communication apparatus 1100 shown in FIG. 11 does not constitute a limitation on the communication apparatus, and the actual communication apparatus can include more or fewer components than those shown, or combine certain components, or different component arrangements.

[0492] In addition, the technical effects of the communication apparatus 1100 can refer to the technical effects of the methods described in the above method embodiments, which will not be described here again.

[0493] It should be appreciated that a processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0494] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM).

[0495] The above-described embodiments can be implemented in whole or in part by software, hardware (such as a circuit), firmware, or any combination thereof. When implemented in software, the above-described embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are wholly or partially generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center through a wired (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. containing one or more available medium collections. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium. The semiconductor medium can be a solid-state disk.

[0496] The embodiments of the present application also provide a computer-readable storage medium storing a computer program, which can make a computer execute the above-described communication method when the computer program is executed by the computer. In other words, the computer program includes instructions for implementing the above-described communication.

[0497] The embodiments of the present application also provide a computer program product, which includes computer program code, and when the computer program code is executed on a computer, the computer can execute the above-described communication method.

[0498] The embodiments of the present application also provide a communication system, which includes a first device and a second device for executing the above-described communication method.

[0499] The embodiments of the present application also provide a chip, which can include a processor for executing the above-described communication method. Optionally, the chip further includes a memory coupled to the processor, and the memory stores a program for executing the above-described communication method.

[0500] It should be understood that the term "and / or" in this document is merely used to describe associated objects, and it is possible that three relationships exist, for example, A and / or B can mean that A exists alone, A and B exist together, B exists alone, where A and B can be singular or plural. In addition, the character " / " in this document generally represents an "or" relationship between the front and rear associated objects, but it can also represent an "and / or" relationship, which can be understood according to the context before and after.

[0501] In this application, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or the like means any combination of the items, including single item or any combination of multiple items. For example, at least one of a, b, or c can mean a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be singular or plural.

[0502] It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0503] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0504] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working process of the above-described system, device and unit can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

[0505] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the shown or discussed objects can be indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other form.

[0506] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, i.e., may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

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

[0508] If the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of software products. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0509] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method is applied to a first device, and the method comprises: determining a first length, the first length being a length of first data; determining, according to the first length, that the first data is to be transmitted by a first mode or a second mode; in a case where it is determined that the first data is to be transmitted by the first mode, transmitting the first data by a first message; or in a case where it is determined that the first data is to be transmitted by the second mode, transmitting the first data by a second message and a third message.

2. The method of claim 1, wherein, The determining of the first length comprises: receiving the first data; determining, according to the first data, the first length.

3. The method of claim 2, wherein, The receiving of the first data comprises: receiving a first service request, the first service request comprising the first data, the first service request being used to request that the first data is to be written to a second device.

4. The method of claim 2 or 3, wherein in a case where it is determined that the first data is to be transmitted by the first mode, transmitting the first data by a first message comprises: in a case where it is determined that the first data is to be transmitted by the first mode, transmitting, to the second device, the first message, the first message comprising the first data.

5. The method of claim 2 or 3, wherein in a case where it is determined that the first data is to be transmitted by the second mode, transmitting the first data by a second message and a third message comprises: in a case where it is determined that the first data is to be transmitted by the second mode, transmitting, to the second device, the second message and the third message, the second message comprising second data, the third message comprising third data, the first data comprising the second data and the third data.

6. The method according to any one of claims 2-5, characterized in that, The method further comprises: determining, according to the first data, the second data and the third data.

7. The method according to any one of claims 2-6, characterized in that, The method further comprises: transmitting, to the second device, a first address, the first address indicating a storage area in which the first data is stored; or transmitting, to the second device, a second address and a third address, the second address indicating an area in which the second data is stored, the third address indicating an area in which the third data is stored.

8. The method of claim 1, wherein The determining of the first length comprises: obtaining the first length from a third device; or receiving a first address, the first address indicating an area in which the first data is stored; determining, according to the first address, the first length.

9. The method of claim 8, wherein, The obtaining of the first length from the third device comprises: receiving a second service request, the second service request being used to request that the first data is to be read from the second device; obtaining, according to the second service request, the first length from the third device.

10. The method of claim 9, wherein, The receiving of the first address comprises: receiving a second service request, the second service request comprising the first address, the second service request being used to request that the first data is to be read from the second device.

11. The method according to any one of claims 8-10, characterized in that, in a case where it is determined that the first data is to be transmitted by the first mode, transmitting the first data by a first message comprises: In a case where it is determined that the first data is received through the first mode, receiving the first message from the second device, the first message comprising the first data.

12. The method according to any one of claims 8-10, characterized in that, In a case where it is determined that the first data is transmitted through the second mode, transmitting the first data through a second message and a third message, comprising: In a case where it is determined that the first data is received through the second mode, receiving the second message and the third message from the second device, the second message comprising second data, the third message comprising third data, and the first data comprising the second data and the third data.

13. The method according to claim 11 or 12, characterized in that, After receiving a first one of the second message and the third message, the method further comprises: sending first indication information to the second device, the first indication information indicating the second device to continue sending data.

14. The method according to any one of claims 8-13, characterized in that, The method further comprises: determining the first data according to the second data and the third data.

15. The method according to any one of claims 8-14, characterized in that, The method further comprises: sending the first address to the second device.

16. The method of any of claims 2-15, wherein the first device is a core network element, and the second device is a terminal device, in a case where it is determined that the first data is transmitted through the first mode, an access network device is configured to forward the first message, and the method further comprises: sending second indication information to the access network device, the second indication information indicating that the access network device can continue to perform operations for other terminals after forwarding the first message; or the first device is the access network device, and the second device is a terminal device, and the method further comprises: continuing to perform operations for other terminals after sending the first message.

17. The method of any of claims 2-15, wherein the first device is a core network element, and the second device is a terminal device, in a case where it is determined that the first data is transmitted through the second mode, an access network device is configured to forward the second message and the third message, and the method further comprises: sending third indication information to the access network device, the third indication information indicating that the access network device needs to perform operations for other terminals according to an indication of the core network element after forwarding a first one of the second message and the third message; or the first device is the access network device, and the second device is a terminal device, and the method further comprises: needing to perform operations for other terminals according to an indication of the core network after sending the first one of the second message and the third message. The receiving the first address comprises: receiving a command, the command comprising the first address, the command indicating reading the first data from the first device.

18. The method of claim 7, wherein, In a case where it is determined that the first data is transmitted through the first mode, transmitting the first data through a first message, comprising: In a case where it is determined that the first data is transmitted through the first mode, sending the first message to the second device, the first message comprising the first data.

19. The method of claim 18, wherein, ​ ​ 20. The method of claim 19, wherein, In a case where it is determined to transmit the first data through the second mode, the first data is transmitted through a second message and a third message, comprising: In a case where it is determined to transmit the first data through the second mode, the second message and the third message are transmitted to the second device, the second message comprising second data, the third message comprising third data, the first data comprising the second data and the third data.

21. The method of claim 20, wherein, After transmitting a first message of the second message and the third message to the second device, the method further comprises: Fourth indication information is transmitted to the second device, the fourth indication information indicating the first device to continue transmitting data.

22. The method of any one of claims 18-21, wherein, The method further comprises: The second data and the third data are determined according to the first data.

23. The method of any one of claims 18-22, wherein, The method further comprises: The first data is obtained from the first area according to the first address.

24. The method of any one of claims 18-23, wherein, The method further comprises: The first length is transmitted to the second device.

25. The method of any one of claims 1-24, wherein: In a case where it is determined to transmit the first data through the first mode, the first message is a first message for transmitting service data; or In a case where it is determined to transmit the first data through the second mode, a first message of the second message or the third message is a first message for transmitting service data.

26. The method of any one of claims 1-25, wherein, The determination of the first data to be transmitted through the first mode or the second mode according to the first length comprises: If the first length is less than or equal to a length threshold, it is determined that the first data is transmitted through the first mode; or If the first length is greater than the length threshold, it is determined that the first data is transmitted through the second mode.

27. The method of claim 26, wherein, The method further comprises: The length threshold is obtained from a third device, or the length threshold is determined according to a quality of a link for carrying the first data.

28. A communications device, characterized by The communication device is configured to perform the method of any one of claims 1-27.

29. The communication apparatus of claim 26, wherein The communication device comprises a chip.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium comprises a computer program or instructions, which, when executed, cause the method of any one of claims 1-27 to be implemented.

31. A computer program product, characterised in that, The computer program product comprises a computer program or instructions, which, when executed, cause the method of any one of claims 1-27 to be implemented.

Images