Communication method and communication apparatus
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2026-01-16
- Publication Date
- 2026-08-13
Smart Images

Figure CN2026072984_13082026_PF_FP_ABST
Abstract
Description
Communication methods and communication devices
[0001] This application claims priority to Chinese Patent Application No. 202510144603.7, filed on February 7, 2025, entitled "Communication Method and Communication Device", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of communication technology, specifically to a communication method and a communication device. Background Technology
[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (A-IoT) technology. In A-IoT and other related technologies, the communication system can include readers and tags. Readers can be implemented by network devices (such as base stations) or user equipment (UE), while tags can be IoT terminals, such as passive / semi-passive / active tags. A-IoT technology is mainly used to achieve the following services: inventory management, positioning, sensing, and command processing. Typical application scenarios for A-IoT technology include logistics, warehousing, industrial manufacturing, identification, and environmental monitoring.
[0004] During the execution of a write command, the reader can send the message containing the write command to the A-IoT device in segments. This allows the A-IoT device to perform write operations on the data contained in the write command in segments, thereby improving the reliability and / or efficiency of transmission between the reader and the A-IoT device. However, during the process of the A-IoT device performing write operations on the data contained in the write command in segments, the A-IoT device may fail to perform write operations on only part of the data contained in the write command. Summary of the Invention
[0005] To address the aforementioned technical problems, this application provides a communication method and communication device, which, by instructing the reader and / or core network that the A-IoT device has failed to write all the data contained in the write command or has failed to write part of the data contained in the write command, triggers the reader and / or core network to retransmit all the data contained in the write command or retransmit the part of the data that failed to write to the A-IoT device, enabling the A-IoT device to re-execute the write operation on the part of the data that failed to write.
[0006] Firstly, a communication method is provided. This method can be executed by a first reader / writer, which can be replaced by components of the first reader / writer (e.g., a chip, chip system, circuit, or communication module). For ease of understanding, the following description uses execution by a first reader / writer as an example.
[0007] The method includes:
[0008] Receive a first message from a first core network element or a first access network device. The first message includes a first command, which instructs the first A-IoT device to perform a write operation on the first data.
[0009] A second message is sent to the first A-IoT device, instructing the first A-IoT device to perform a write operation on second data, which is a part of the first data;
[0010] It was determined that the first A-IoT device failed to perform a write operation on the second data.
[0011] A third message is sent to the first A-IoT device, instructing the first A-IoT device to perform a write operation on the second data.
[0012] Based on the above technical solution, the first reader sends the message containing the write command to the first A-IoT device in segments. During the process of the first A-IoT device performing the write operation on the data contained in the write command in segments, if the first reader determines that the first A-IoT device has failed to perform the write operation on part of the data contained in the write command (e.g., the second data), the first reader can instruct the first A-IoT device to perform the write operation on the failed part of the data again. This allows the first A-IoT device to re-perform the write operation on the failed data, thereby improving the success rate of the first A-IoT device performing the write operation on the data contained in the write command.
[0013] For example, if the first reader is an access network device, the first reader receives a first message from a first core network element.
[0014] For example, if the first reader / writer is a terminal device, then the first reader / writer receives a first message from the first access network device.
[0015] For example, the third message may also include a retransmission instruction.
[0016] In conjunction with the first aspect, in certain implementations of the first aspect, a third message is sent to the first A-IoT device, including:
[0017] If the first condition is met, a third message is sent to the first A-IoT device.
[0018] For example, the first condition includes one or more of the following: the number of times the first A-IoT device fails to perform write operations on part or all of the first data does not exceed a first threshold, or the number of times the first A-IoT device fails to perform write operations on the second data does not exceed a second threshold.
[0019] Based on the above technical solution, it is beneficial to avoid the signaling overhead caused by the first reader constantly sending a third message to the first A-IoT device when the first A-IoT device fails to perform write operations on part or all of the first data too many times, or when the first A-IoT device fails to perform write operations on the second data too many times.
[0020] In conjunction with the first aspect, in some implementations of the first aspect, before sending the third message to the first A-IoT device,
[0021] The method also includes:
[0022] A fourth message is sent to the first core network element or the first access network device, indicating that the first A-IoT device failed to execute the first command.
[0023] Receive a fifth message from a first core network element or a first access network device, the fifth message including the first command.
[0024] For example, when the first reader receives the fifth message, it sends a third message to the first A-IoT device based on the fifth message. In this case, the third message instructs the first A-IoT device to perform a write operation on the first data. It should be understood that since the first data includes the second data, when the third message instructs the first A-IoT device to perform a write operation on the first data, the third message also has the function of instructing the first A-IoT device to perform a write operation on the second data.
[0025] Based on the above technical solution, the first reader sends the message containing the write command to the first A-IoT device in segments. During the process of the first A-IoT device performing the write operation on the data contained in the write command in segments, if the first reader determines that the first A-IoT device has failed to perform the write operation on part of the data contained in the write command (e.g., the second data), the first reader can indicate to the first core network element that the first A-IoT device has failed to perform the write operation on the data contained in the write command (e.g., the first data), thereby triggering the first core network element to resend the data contained in the write command to the first A-IoT device through the first reader, so that the first A-IoT device can re-perform the write operation on the data that failed to be written.
[0026] In conjunction with the first aspect, in some implementations of the first aspect, before sending the third message to the first A-IoT device,
[0027] The method also includes:
[0028] Send a sixth message to the first core network element or the first access network device. The sixth message includes first information and second information. The first information includes second data. The second information indicates that the first A-IoT device failed to perform a write operation on the second data.
[0029] Receive a seventh message from a first core network element or a first access network device. The seventh message includes a first command and third information. The third information indicates one or more of the following: the start position of the write operation performed on the first data, the length of the write operation performed on the first data, and the end position of the write operation performed on the first data.
[0030] The third message also includes third information.
[0031] Based on the above technical solution, the first reader sends the message containing the write command to the first A-IoT device in segments. During the process of the first A-IoT device performing segmented write operations on the data contained in the write command (e.g., the first data), if the first reader determines that the first A-IoT device has failed to perform a write operation on part of the data contained in the write command (e.g., the second data), the first reader can send the second data to the first core network element and indicate that the first A-IoT device has failed to write the second data. This triggers the first core network element to resend the first data to the first A-IoT device through the first reader and instruct the first A-IoT device on the location where the write operation on the first data was performed. This allows the first A-IoT device to re-perform the write operation on the second data that failed to be written without having to re-perform the write operation on the successfully written data in the first data.
[0032] In conjunction with the first aspect, in some implementations of the first aspect, before sending the second message to the first A-IoT device,
[0033] The method also includes:
[0034] Send an eighth message to the first A-IoT device. The eighth message instructs the first A-IoT device to perform a write operation on the third data, which is a part of the first data and is different from the second data.
[0035] Receive the ninth message from the first A-IoT device, which indicates that the write operation on the third data was successfully performed;
[0036] The sixth message also includes the fourth message, which includes the third data.
[0037] Based on the above technical solution, if the first A-IoT device successfully performs a write operation on the third data before failing to write the second data, the first reader / writer can send the third data and the second data to the first core network element. This allows the first core network element to identify the position of the second data within the first data based on the received third and second data. In other words, it enables the first core network element to identify which part of the first data the first A-IoT device failed to write. When the first core network element can identify which part of the first data the first A-IoT device failed to write, it is beneficial for the first core network element to again notify the first A-IoT device via the first reader / writer to perform a write operation on the failed data.
[0038] For example, the sixth message also includes a fifth message indicating that the first A-IoT device has successfully performed a write operation on the third data.
[0039] In conjunction with the first aspect, in certain implementations of the first aspect, the first A-IoT device sends a third message, including:
[0040] Send a sixth message to the first core network element or the first access network device. The sixth message includes first information and second information. The first information includes second data. The second information indicates that the first A-IoT device failed to perform a write operation on the second data.
[0041] Receive the tenth message from the first core network element or the first access network device;
[0042] In response to receiving the tenth message, a third message is sent to the first A-IoT device.
[0043] Based on the above technical solution, the first reader sends the message containing the write command to the first A-IoT device in segments. During the process of the first A-IoT device performing a segmented write operation on the data contained in the write command (e.g., the first data), if the first reader determines that the first A-IoT device has failed to perform a write operation on part of the data contained in the write command (e.g., the second data), the first reader can send the second data to the first core network element and instruct the first A-IoT device that the write operation on the second data has failed. This helps to trigger the first core network element to resend the second data to the first A-IoT device through the first reader, so that the first A-IoT device can re-perform the write operation on the second data that failed to be written without re-performing the write operation on the successfully written data in the first data.
[0044] In conjunction with the first aspect, in some implementations of the first aspect,
[0045] The failure to determine if the first A-IoT device performed a write operation on the second data includes:
[0046] Receive an eleventh message from the first A-IoT device, indicating that the first A-IoT device failed to perform a write operation on the second data; or...
[0047] If no message is received from the first A-IoT device within the first time period after sending the second message, it is determined that the first A-IoT device failed to perform a write operation on the second data.
[0048] In conjunction with the first aspect, in some implementations of the first aspect,
[0049] The duration of the first time period is a predefined or pre-configured duration; or,
[0050] The method also includes:
[0051] Receive the twelfth message from the first core network element or the first access network device;
[0052] The twelfth message indicates the duration of the first time period; or,
[0053] The twelfth message includes one or more of the following: the length of the first data, the duration of the write operation on the first data, the capability or type of the first A-IoT device, and the twelfth message is used to determine the duration of the first time period.
[0054] In conjunction with the first aspect, in some implementations of the first aspect, the method further includes:
[0055] Receive a thirteenth message and / or a twelfth message, the thirteenth message indicating the cache capability or cache size of the first A-IoT device, and the twelfth message including one or more of the following: the length of the first data, the duration of the write operation on the first data, and the capability or type of the first A-IoT device;
[0056] Send a second message to the first A-IoT device, including:
[0057] Send a second message to the first A-IoT device according to the thirteenth and / or twelfth messages.
[0058] Based on the above technical solution, when the first reader sends the second message according to the thirteenth message and / or the twelfth message, it is beneficial to avoid the storage resource consumption caused by the first A-IoT device needing to cache part of the second data due to the length of the second data included in the second message being too large; or, it is beneficial to avoid the transmission resource consumption caused by the multiple interactions between the first reader and the first A-IoT device due to the length of the second data included in the second message being too small.
[0059] Secondly, a communication method is provided. This method can be executed by a first A-IoT device, which can be replaced by components of the first A-IoT device (e.g., a chip, chip system, circuit, or communication module). For ease of understanding, the following description uses the execution of the first A-IoT device as an example.
[0060] The method includes:
[0061] Receive a second message from the first reader / writer, the second message instructing the first A-IoT device to perform a write operation on second data, the second data being a part of the first data;
[0062] Send an eleventh message to the first reader / writer, indicating that the first A-IoT device failed to write the second data; or...
[0063] The fourteenth message is received from the first reader / writer, which instructs the first A-IoT device to access the network.
[0064] Based on the above technical solution, the first A-IoT device can send an eleventh message to the first reader / writer to indicate that the first A-IoT device failed to perform a write operation on the second data. Alternatively, if the link between the first A-IoT device and the first reader / writer is down, the first reader / writer can trigger the first A-IoT device to access the network, thereby enabling the first reader / writer and / or core network elements to trigger the first A-IoT device to re-perform the write operation on the second data.
[0065] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes:
[0066] A third message is received from the first reader / writer, which instructs the first A-IoT device to perform a write operation on the second data.
[0067] Based on the above technical solution, the first reader / writer can send a third message to the first A-IoT device to trigger the first A-IoT device to re-execute the write operation on the second data, thereby improving the success rate of the A-IoT device in executing the write operation on the data contained in the write command.
[0068] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes:
[0069] Send the thirteenth message to the first reader / writer. The thirteenth message indicates the cache capacity or cache size of the first A-IoT device.
[0070] Based on the above technical solution, it is beneficial for the first reader to segment the message containing the write command according to the thirteenth message, thereby avoiding the storage resource consumption caused by the first A-IoT device having to cache part of the second data due to the length of the second data included in the second message being too large; or, it is beneficial to avoid the transmission resource consumption caused by the multiple interactions between the first reader and the first A-IoT device due to the length of the second data included in the second message being too small.
[0071] In conjunction with the second aspect, in some implementations of the second aspect, the length of the second data is related to the caching capacity or cache size of the first A-IoT device.
[0072] Thirdly, a communication method is provided. This method can be executed by a first core network element, which can be replaced by its constituent components (such as a chip, chip system, circuit, or communication module). For ease of understanding, the following description uses the execution by the first core network element as an example.
[0073] The method includes:
[0074] Send a first message to the first reader or the first access network device. The first message includes a first command, which instructs the first A-IoT device to perform a write operation on the first data.
[0075] Receive a sixth message from the first reader or the first access network device. The sixth message includes first information and second information. The first information includes second data, which is a part of the first data. The second information indicates that the first A-IoT device failed to perform a write operation on the second data.
[0076] A seventh message is sent to the first reader or the first access network device. The seventh message includes a first command and third information, whereby the third information indicates one or more of the following: the start position of the write operation on the first data, the length of the write operation on the first data, and the end position of the write operation on the first data; or...
[0077] A tenth message is sent to the first reader or the first access network device. The tenth message includes a second command, which instructs the first A-IoT device to perform a write operation on the second data.
[0078] Based on the above technical solution, the first reader / writer can send the second data to the first core network element and instruct the first A-IoT device to fail to write the second data, thereby triggering the first core network element to resend the first data to the first A-IoT device through the first reader / writer and instruct the first A-IoT device on the location to perform the write operation on the first data through the first reader / writer. Alternatively, it can trigger the first core network element to resend the second data to the first A-IoT device through the first reader / writer, thereby enabling the first A-IoT device to re-perform the write operation on the second data that failed to write, without having to re-perform the write operation on the successfully written data in the first data.
[0079] In conjunction with the third aspect, in some implementations of the third aspect, the sixth message also includes a fourth message, which includes third data, which is part of the first data and is different from the second data.
[0080] Based on the above technical solution, if the first A-IoT device successfully performs a write operation on the third data before failing to write the second data, the first reader / writer can send the third data and the second data to the first core network element. This allows the first core network element to identify the position of the second data within the first data based on the received third and second data. In other words, it enables the first core network element to identify which part of the first data the first A-IoT device failed to write. When the first core network element can identify which part of the first data the first A-IoT device failed to write, it is beneficial for the first core network element to again notify the first A-IoT device via the first reader / writer to perform a write operation on the failed data.
[0081] In conjunction with the third aspect, in some implementations of the third aspect, the sixth message also includes the fifth information, which indicates that the first A-IoT device has successfully performed a write operation on the third data.
[0082] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes:
[0083] Send the twelfth message to the first reader or the first access network device;
[0084] The twelfth message indicates the duration of the first time period, which is used to determine whether the first A-IoT device failed to perform a write operation on part or all of the first data; or,
[0085] The twelfth message includes one or more of the following: the length of the first data, the duration of the write operation on the first data, and the capabilities or type of the first A-IoT device.
[0086] Based on the above technical solution, it is beneficial for the first reader to determine the appropriate duration of the first time period according to the twelfth message, thereby avoiding the first reader determining that the duration of the first time period determined by the first reader is too long, which would cause the first reader to fail to determine in time whether the first A-IoT device has failed to perform a write operation on part or all of the first data; or, it is beneficial to avoid the first reader determining that the duration of the first time period determined by the first reader is too short, which would cause the first reader to determine that the first A-IoT device has failed to perform a write operation on all or part of the first data before receiving the message indicating that the first A-IoT device has successfully performed a write operation on all or part of the first data.
[0087] In conjunction with the third aspect, in some implementations of the third aspect, the method further includes:
[0088] Receive the fifteenth message from the first A-IoT device, the fifteenth message indicating the cache capacity or cache size of the first A-IoT device;
[0089] Send a thirteenth message to the first reader or the first access network device. The thirteenth message indicates the cache capacity or cache size of the first A-IoT device.
[0090] Based on the above technical solution, it is beneficial for the first reader / writer to segment the message containing the write command according to the thirteenth message, thereby avoiding the storage resource consumption caused by the first A-IoT device having to cache part of the data in the segmented message (such as the second message) due to the excessively large length of the data included in the segmented message containing the write command; or, it is beneficial to avoid the transmission resource consumption caused by the multiple interactions between the first reader / writer and the first A-IoT device due to the excessively small length of the data included in the segmented message (such as the second message) containing the write command.
[0091] Fourthly, a communication method is provided. This method can be executed by a first reader / writer, which can be replaced by components of the first reader / writer (such as a chip, chip system, circuit, or communication module). For ease of understanding, the following description uses the execution by the first reader / writer as an example.
[0092] The method includes:
[0093] Receive the sixteenth message, which indicates the length of the data contained in the first write command.
[0094] Based on the above technical solution, it is beneficial for the first reader to segment the message containing the write command according to the sixteenth message, and / or to schedule resources for the first A-IoT device to communicate with the first reader according to the sixteenth message.
[0095] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes:
[0096] The duration for executing the first write command is determined based on the sixteenth message.
[0097] Based on the above technical solution, when the first reader determines the duration of executing the first write command, it is beneficial for the first reader to determine an appropriate first duration based on the duration of executing the first write command. This first duration is used to determine whether the first A-IoT device has failed to perform a write operation on some or all of the data contained in the first write command. When the first reader determines an appropriate first duration, it helps to avoid the first reader determining that the first time period is too long, causing the first reader to fail to determine in time whether the first A-IoT device has failed to perform a write operation on some or all of the data contained in the first write command; or, it helps to avoid the first reader determining that the first A-IoT device has failed to perform a write operation on some or all of the data contained in the first write command before receiving a message indicating that the first A-IoT device has successfully performed a write operation on some or all of the data contained in the first write command.
[0098] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the duration of executing the first write command is determined based on the sixteenth message, including:
[0099] The duration of executing the first write command is determined based on the sixteenth message and one or more of the following: the capabilities of the first A-IoT device, the type of the first A-IoT device, or distance information related to the distance between the reader / writer and the first A-IoT device, which is used to execute the first write command.
[0100] Based on the above technical solution, the first reader / writer can more accurately determine the execution time of the first write command. For example, different types or capabilities of A-IoT devices execute write commands at different speeds. Therefore, if the first reader / writer determines the execution time of the first write command based on the capability or type of the first A-IoT device, it is beneficial to determine a more accurate execution time of the first write command.
[0101] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes:
[0102] The information of the first resource is determined according to the sixteenth message. The first resource is used for communication between the first reader / writer and the first A-IoT device. The first A-IoT device is used to execute the first write command.
[0103] Based on the above technical solution, it is beneficial for the first reader / writer to allocate sufficient first resources for communication between the first A-IoT device and the first reader / writer. For example, when the first reader / writer determines the information of the first resources according to the sixteenth message, it helps to avoid insufficient time-domain resources allocated by the first reader / writer for the first A-IoT device, resulting in insufficient first resources to support communication between the first A-IoT device and the first reader / writer; or, it helps to avoid excessive time-domain resources allocated by the first reader / writer for the first A-IoT device, resulting in resource waste.
[0104] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes:
[0105] The first duration is determined according to the sixteenth message. The first duration is used to determine whether the first A-IoT device failed to execute the first write command. The first A-IoT device is used to execute the first write command.
[0106] Based on the above technical solution, it is beneficial for the first reader / writer to determine an appropriate first duration. When the first reader / writer determines an appropriate first duration, it helps to avoid the first reader / writer determining that the first A-IoT device has failed to perform the write operation on some or all of the data contained in the first write command due to an excessively long first duration; or, it helps to avoid the first reader / writer determining that the first A-IoT device has failed to perform the write operation on some or all of the data contained in the first write command before receiving the message indicating that the first A-IoT device has successfully performed the write operation on some or all of the data contained in the first write command.
[0107] Fifthly, a communication method is provided. This method can be executed by a first reader / writer, which can be replaced by components of the first reader / writer (e.g., a chip, chip system, circuit, or communication module). For ease of understanding, the following description uses the execution by the first reader / writer as an example.
[0108] The method includes:
[0109] Received the seventeenth message, which indicates the duration for executing the first command.
[0110] Based on the above technical solution, the first reader / writer can determine the second duration according to the seventeenth message, and / or schedule resources for communication between the first A-IoT device and the first reader / writer according to the seventeenth message. The second duration is used to determine whether the first A-IoT device failed to execute the first command.
[0111] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes:
[0112] The information of the second resource is determined according to message 17. The second resource is used for communication between the first reader and the first A-IoT device. The first A-IoT device is used to execute the first command.
[0113] Based on the above technical solution, it is beneficial for the first reader / writer to allocate sufficient second resources for the first A-IoT device to communicate with it. For example, when the first reader / writer determines the information of the second resources based on the seventeenth message, it helps to avoid insufficient temporal resources for the second resources allocated by the first reader / writer to the first A-IoT device, which would result in insufficient second resources to support communication between the first A-IoT device and the first reader / writer; or, it helps to avoid excessive temporal resources allocated by the first reader / writer to the first A-IoT device, which would lead to resource waste.
[0114] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the method further includes:
[0115] The second duration is determined according to message seventeen. The second duration is used to determine whether the first A-IoT device failed to execute the first command. The first A-IoT device is used to execute the first command.
[0116] Based on the above technical solution, it is beneficial for the first reader to determine an appropriate second duration. When the first reader determines an appropriate second duration, it helps to avoid the first reader determining that the second duration is too long, causing the first reader to fail to determine in time that the first A-IoT device has failed to execute the first command; or, it helps to avoid the first reader determining that the second duration is too short, causing the first reader to determine that the first A-IoT device has failed to execute the first command before receiving the message indicating that the first A-IoT device has successfully executed the first command.
[0117] Sixthly, a communication apparatus is provided. This apparatus is used to perform the methods provided in the first, fourth, or fifth aspects described above. Specifically, the communication apparatus may include units and / or modules for performing the methods provided in any of the above implementations of the first, fourth, or fifth aspects, such as processing units and transceiver units.
[0118] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.
[0119] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.
[0120] In a seventh aspect, a communication apparatus is provided. This apparatus is used to perform the method provided in the second aspect. Specifically, the communication apparatus may include units and / or modules for performing the method provided in the second aspect, such as a processing unit and a transceiver unit.
[0121] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.
[0122] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.
[0123] Eighthly, a communication apparatus is provided. This apparatus is used to perform the method provided in the third aspect. Specifically, the communication apparatus may include units and / or modules for performing the method provided in the third aspect, such as a processing unit and a transceiver unit.
[0124] In one implementation, the transceiver unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.
[0125] In another implementation, the transceiver unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip, chip system, or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.
[0126] Ninthly, this application provides a processor including a module for executing the method provided in any of the implementations of the first to fifth aspects described above.
[0127] Unless otherwise specified, or if it does not contradict its actual function or internal logic in the relevant description, the transmission and acquisition / reception operations involved in the processor can be understood as processor output and reception, input and other operations, or as transmission and reception operations performed by radio frequency circuits and antennas. This application does not limit them in this regard.
[0128] In a tenth aspect, a computer-readable storage medium is provided that stores program code for execution by a device, the program code including a method for performing any of the implementations of the first to fifth aspects described above.
[0129] Eleventhly, a computer program product containing instructions is provided, which, when run on a communication device, causes a computer to execute the method provided by any one of the implementations of the first to fifth aspects described above.
[0130] In a twelfth aspect, a chip is provided, the chip including a processor and a communication interface, wherein the processor reads instructions stored in a memory through the communication interface and executes the method provided by any one of the implementations of the first to fifth aspects.
[0131] Optionally, as one implementation, the chip also includes a memory storing computer programs or instructions, and a processor executes the computer programs or instructions stored in the memory. When the computer programs or instructions are executed, the method provided by any of the first to fifth aspects described above is executed.
[0132] In a thirteenth aspect, a communication system is provided, comprising one or more of the following: the communication device described in the sixth aspect, the communication device described in the seventh aspect, or the communication device described in the eighth aspect. Attached Figure Description
[0133] Figure 1 is a schematic diagram of a communication system applicable to an embodiment of this application.
[0134] Figure 2 is a schematic diagram of another communication system applicable to embodiments of this application.
[0135] Figure 3 is a schematic diagram of another communication system applicable to an embodiment of this application.
[0136] Figure 4 is a schematic diagram of another communication system applicable to embodiments of this application.
[0137] Figure 5 is a schematic diagram of an open radio access network (O-RAN) system applicable to embodiments of this application.
[0138] Figure 6 is a schematic diagram of another O-RAN system applicable to embodiments of this application.
[0139] Figure 7 shows a core network architecture related to the communication system shown in Figure 1.
[0140] Figure 8 shows a core network architecture related to the communication system shown in Figure 2.
[0141] Figure 9 is a schematic flowchart of a communication method provided in an embodiment of this application.
[0142] Figure 10 is a schematic flowchart of a communication method provided in an embodiment of this application.
[0143] Figure 11 is a schematic flowchart of a communication method provided in an embodiment of this application.
[0144] Figure 12 is a schematic block diagram of a communication device provided in an embodiment of this application.
[0145] Figure 13 is a schematic block diagram of another communication device provided in an embodiment of this application.
[0146] Figure 14 is a schematic block diagram of the chip system provided in an embodiment of this application. Detailed Implementation
[0147] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0148] The technical solutions provided in this application can be applied to various communication systems, such as: 5th generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area network (WLAN) systems, satellite communication systems, future communication systems, or integrated systems of multiple systems. The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.
[0149] The technical solutions provided in this application can also be applied to non-terrestrial network (NTN) systems such as inter-satellite communication and satellite communication. As an example, a satellite communication system includes a satellite base station and terminal equipment. The satellite base station provides communication services to the terminal equipment. The satellite base station can also communicate with other base stations. A satellite can act as a base station or as a terminal device. Here, "satellite" can refer to unmanned aerial vehicles (UAVs), hot air balloons, low-Earth orbit (LEO) satellites, medium-Earth orbit (MEO) satellites, high-Earth orbit (HEO) satellites, etc. "Satellite" can also refer to non-terrestrial base stations or non-terrestrial equipment, etc.
[0150] In a communication system, a device can send signals to or receive signals from another device. These signals can include information, signaling, or data. The device can also be replaced by an entity, network entity, communication device, mobile device, network element, communication module, node, communication node, communication apparatus, etc. This disclosure uses a device as an example. For instance, a communication system can include at least one terminal device and at least one network device. The network device can send downlink signals to the terminal device, and / or the terminal device can send uplink signals to the network device. It is understood that the terminal device in this disclosure can be replaced by a first communication device, and the network device can be replaced by a second communication device, both performing the corresponding communication methods described in this disclosure. Alternatively, the corresponding communication methods in this disclosure can be applied between network devices or between terminal devices, without limitation herein.
[0151] The terminal device in this application embodiment can be a device or module that accesses the aforementioned communication system and has corresponding communication functions. The terminal device can include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. The terminal device can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer, M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc. The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initiation protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multiple helicopters, four helicopters, or airplanes), ship, remote control device, smart home device, industrial equipment, transportation vehicle with wireless communication capability, communication module, or roadside unit with terminal function, all conforming to the 3rd generation partnership project (3GPP) standard. The terminal device (RSU) can be a unit or device built into the aforementioned equipment (e.g., a communication module, modem, or chip in the aforementioned equipment), or other processing devices connected to a wireless modem. For ease of description, the terminal device will be described below as a terminal or UE.
[0152] It should be understood that in certain scenarios, a UE can also be used as a base station. For example, a UE can act as a scheduling entity, providing sidelink signaling between UEs in scenarios such as V2X, D2D, or end-to-end.
[0153] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system. This device can be installed in or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. This embodiment only uses the terminal device as an example to illustrate the device for implementing the functions of the terminal device, and does not constitute a limitation on the solution of this embodiment.
[0154] The network device in this application embodiment can be a device or module with corresponding communication functions. The network device can be a device used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitter point, master station, auxiliary station, motor slide retainer (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or a combination thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.
[0155] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.
[0156] In some deployments, the network devices mentioned in the embodiments of this application may be devices including CU, DU, or CU and DU, or devices with control plane CU nodes (central unit-control plane (CU-CP)) and user plane CU nodes (central unit-user plane (CU-UP)) and DU nodes. For example, the network devices may include gNB-CU-CP, gNB-CU-UP, and gNB-DU.
[0157] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, RAN nodes can be CUs, DUs, CU-CPs, CU-UPs, or RUs. CUs and DUs can be configured separately or included in the same network element, such as a BBU. RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, AAUs, or RRHs.
[0158] In some deployments, the CU (Core Unit) is a logical node that carries the Radio Resource Control (RRC) layer, Service Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, and other control functions of the access network equipment. The CU connects to network nodes such as the core network through interfaces, which may be E2 interfaces, etc. Optionally, the CU possesses some core network functions. The CU (e.g., the PDCP layer and higher layers) connects to the DU (e.g., the Radio Link Control (RLC) layer and lower layers) through interfaces, which may be F1 interfaces, etc. In some examples, these interfaces (e.g., the F1 interface) can provide control plane (C-Plane) and user plane (U-Plane) functions (e.g., interface management, system information management, UE context management, RRC message transmission, etc.). The F1 application protocol (F1AP) is the application protocol for the F1 interface, and in some examples, it defines the F1 signaling procedures. The F1 interface supports both the control plane (F1-C) and the user plane (F1-U).
[0159] In some deployments, the CU can be split into CU-CP and CU-UP. CU-CP is a logical node carrying the RRC layer and the control plane part of PDCP (PDCP-C) layer, used to implement the CU's control plane functions. CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function network elements. CU-UP is a logical node carrying the SDAP layer and the user plane part of PDCP (PDCP-U) layer, used to implement the CU's user plane functions. CU-UP can interact with network elements in the core network used to implement user plane functions. The above CU and DU configurations are merely examples; the functions of CU and DU can be configured as needed. For example, CU or DU can be configured to have more protocol layer functions, or CU or DU can be configured to have only partial protocol layer processing functions. For example, some functions of the RLC layer and the functions of the protocol layer above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the functions of the protocol layer below the RLC layer can be placed in the DU. Another example is that the functions of the CU or DU can be divided according to service type or other system requirements. For instance, based on latency, functions that need to meet low latency requirements can be placed in the DU, while functions that do not need to meet such latency requirements can be placed in the CU.
[0160] In some deployments, the DU (Distributed Unit) is a logical node that carries the RLC (Real-Time Control) layer, the medium access control (MAC) layer, the higher physical layer (Higher PHY) layer, and other functions. In some examples, the DU can control at least one RU (Remote Root). The DU connects to the RU through interfaces, which can be fronthaul interfaces. In some examples, the Higher PHY layer includes the PHY layer processing, such as forward error correction (FEC) encoding and decoding, scrambling, modulation, and demodulation.
[0161] In some deployments, the RU is a logical node that carries both lower physical layer (PHY) and radio frequency (RF) processing. In some examples, the RU can be a TRP, RRH, or other similar entity. In some examples, the Low-PHY includes portions of the PHY processing, such as Fast Fourier Transform (FFT), Inverse Fast Fourier Transform (IFFT), digital beamforming, and filtering. The RU communicates with one or more UEs via a radio link.
[0162] The DU and RU can be co-located or not. The DU and RU exchange control plane and user plane information via a fronthaul link through a lower-layer split-control, user, and synchronization (LLS-CUS) interface. LLS-CUS may include interfaces providing control and user planes respectively. In some examples, the control plane refers to real-time control between the DU and RU. The DU and RU exchange management information via a fronthaul link interface (such as an LLS-M interface), and the management plane (M-Plane) refers to non-real-time management operations between the DU and RU.
[0163] DU and RU can cooperate to implement the functions of the PHY layer. A DU can be connected to one or more RUs. The functions of DU and RU can be configured in various ways depending on the design. For example, a DU can be configured to implement baseband functions, and an RU can be configured to implement mid-RF functions. Another example is that a DU can be configured to implement higher-level functions in the PHY layer, and an RU can be configured to implement lower-level functions in the PHY layer, or to implement both lower-level and RF functions. Higher-level functions in the physical layer can include a portion of the physical layer's functions that are closer to the MAC layer, while lower-level functions in the physical layer can include another portion of the physical layer's functions that are closer to the mid-RF side.
[0164] In one possible design, the processing unit in the BBU used to implement baseband functions is called the baseband high (BBH) unit, and the processing unit in the RRU / AAU / RRH used to implement baseband functions is called the baseband low (BBL) unit.
[0165] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, a radio access network can also be an open radio access network (O-RAN) architecture. In an O-RAN system, CU can also be called an open CU (open CU, O-CU), DU can also be called an open DU (open DU, O-DU), CU-CP can also be called an open CU-CP (O-CU-CP), CU-UP can also be called an open CU-UP (O-CU-UP), and RU can also be called an open RU (open RU, O-RU). Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.
[0166] In this embodiment, the device for implementing the functions of a network device can be a network device itself, or a device capable of supporting the network device in implementing those functions, such as a chip system, chip, circuit, or communication module (i.e., a communication module that performs communication functions). This device can be installed within the network device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. Furthermore, the device can be configured with program instructions for performing corresponding communication functions. This embodiment only uses a network device as an example to illustrate the device for implementing the functions of a network device, and does not limit the solution of this embodiment.
[0167] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located. Furthermore, terminal devices and network devices can be hardware devices, software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., a cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application does not limit the specific form of the terminal devices and network devices.
[0168] First, a brief introduction to the communication system applicable to the embodiments of this application is given below.
[0169] Figure 1 is a schematic diagram of a communication system 100 applicable to an embodiment of this application. As shown in Figure 1, the communication system includes a network device 110 and an ambient Internet of Things (A-IoT) terminal 120. The network device 110 and the A-IoT device 120 communicate bidirectionally. The communication between the network device 110 and the A-IoT device 120 includes ambient Internet of Things data and / or signaling. That is, the network device 110 sends downlink data and / or signaling to the A-IoT device 120, and the A-IoT device 120 sends uplink data and / or signaling to the network device 110. Alternatively, it can be understood that the network device 110 and the A-IoT device 120 transmit uplink and downlink data and / or signaling.
[0170] Figure 2 is a schematic diagram of a communication system 200 applicable to an embodiment of this application. As shown in Figure 2, the communication system includes a network device 210, an intermediate node 220, and an A-IoT device 230. The network device 210 and the A-IoT device 230 communicate bidirectionally with the intermediate node 220. For example, the network device 210 communicates bidirectionally with the intermediate node 220, and then the intermediate node 220 communicates bidirectionally with the A-IoT device 120. That is, the network device 210 transmits uplink and downlink data and / or signaling between itself and the intermediate node 220, and the intermediate node 220 transmits uplink and downlink data and / or signaling between itself and the A-IoT device 120. In this embodiment, the intermediate node 220 can be a repeater, an integrated access backhaul (IAB) node, a UE, etc.
[0171] Figure 3 is a schematic diagram of a communication system 300 applicable to an embodiment of this application. As shown in Figures 3(a) and (b), the communication system includes a network device 310, an auxiliary node 320, and an A-IoT device 330. In Figure 3(a), the A-IoT device 330 sends data and / or signaling to the network device 310, the network device 310 sends data and / or signaling to the auxiliary node 320 via the Uu interface, and then the A-IoT device 330 receives data and / or signaling from the auxiliary node 320. In Figure 3(b), the A-IoT device 330 receives data and / or signaling sent by the network device 310 and sends data and / or signaling to the auxiliary node 320, and then the network device 310 receives data and / or signaling from the auxiliary node 320 via the Uu interface. In this embodiment of the application, the intermediate node of the auxiliary node 320 may be a repeater, an IAB node, a UE, etc.
[0172] Figure 4 is a schematic diagram of a communication system 400 applicable to an embodiment of this application. As shown in Figure 4, the communication system includes a terminal device 410 and an A-IoT device 420. The terminal device 410 and the A-IoT device 420 communicate bidirectionally. The communication between the terminal device 410 and the A-IoT device 420 includes environmental IoT data and / or signaling. That is, the terminal device 410 sends downlink data and / or signaling to the A-IoT device 420, and the A-IoT device 420 sends uplink data and / or signaling to the terminal device 410. Alternatively, it can be understood that the terminal device 410 and the A-IoT device 420 transmit uplink and downlink data and / or signaling.
[0173] Figures 1 to 4 are merely schematic diagrams. The communication system to which the embodiments of this application are applicable may also include other devices, such as core network devices, wireless relay devices and / or wireless backhaul devices, which are not shown in Figures 1 to 4.
[0174] The embodiments of this application can also be applied to open RAN (O-RAN) system architecture.
[0175] As shown in Figure 5, an O-RAN system can include core network (CN) equipment, access network (RAN) equipment, and user equipment (UE). Access network equipment communicates with core network equipment via a backhaul link and with UE via an air interface. For example, a BBU in the access network equipment communicates with core network equipment via a backhaul link, and an RU in the access network equipment communicates with UE via an air interface. The BBU communicates with at least one RU via a fronthaul link; the BBU and RU may or may not be co-located. The BBU includes at least one CU and at least one DU, and the CU and DU can communicate via at least one midhaul link.
[0176] Figure 5 is just a schematic diagram. The wireless communication system may also include other devices, which are not shown in Figure 5.
[0177] Figure 6 is a schematic diagram of the application framework involving the RIC module under the O-RAN architecture. As shown in Figure 6, the communication system includes a RAN intelligent controller (RIC). The RIC includes near-real-time RIC (near-RT RIC) and non-real-time RIC (non-RT RIC). The non-real-time RIC mainly processes non-real-time information, such as data that is not sensitive to latency, with latency in the order of seconds. The real-time RIC mainly processes near-real-time information, such as data that is relatively sensitive to latency, with latency in the order of tens of milliseconds.
[0178] The near real-time RIC and non-real-time RIC can also be set up as separate network elements. Optionally, the near real-time RIC and non-real-time RIC can also be part of other devices. For example, the near real-time RIC can be set in the RAN node (e.g., in CU, DU), while the non-real-time RIC can be set in the OAM, cloud server, core network device, or other network device.
[0179] To facilitate a better understanding of the technical solution of this application, some related technologies involved in the technical solution of this application are introduced.
[0180] 1. A-IoT devices:
[0181] With the increasing application of MTC and IoT communication in 5G NR communication, the number of connected IoT devices is growing daily. Therefore, the industry's demand for reduced cost and power consumption of IoT devices is becoming increasingly strong. During the 4G era, 3GPP introduced Narrow-Band IoT (NB-IoT) systems. However, NB-IoT terminals still require external power (battery) and have the ability to generate local high-frequency carrier waves, thus limiting their power consumption to milliwatts. But with the evolution and development of 5G IoT, the need for lower-power terminals in 5G networks is growing. Passive Radio Frequency Identification (RFID) technology provides a good technical reference for low power consumption, supporting microwatt-level power consumption. RFID terminals (tags) use low-precision, low-power mid-to-low frequency ring oscillators or receive downlink signals without a local oscillator. When the tag is working, the energy and carrier wave for communication are supplied by the reader, and communication is based on reflected carrier waves.
[0182] Given the low power consumption advantage of RFID communication technology, 5G A-IoT has emerged. To meet ultra-low power consumption requirements, terminal devices in A-IoT also use low-precision, low-power mid-to-low frequency ring oscillators or receivers without a local oscillator to receive downlink signals. This receiving method further reduces the power consumption of downlink reception. However, for such low-power receiving methods, only amplitude detection, such as envelope detection, can be performed because a low-precision ring oscillator alone cannot guarantee accurate demodulation of signal phase information.
[0183] 2. A-IoT:
[0184] With the development of communication technology, 3GPP defined A-IoT technology. A-IoT devices in A-IoT technology include network devices and Type I terminal devices; or, in other words, A-IoT-based communication systems include network devices and Type I terminal devices. Type I terminal devices can be devices with A-IoT functionality. In this case, both readers and A-IoT devices can be implemented based on cellular network infrastructure. In other words, both readers and A-IoT devices can be devices within a cellular network. For example, the functionality of a reader can be implemented by network devices, such as base stations. A-IoT devices can be implemented by terminals within a cellular network, such as ultra-low power, ultra-low complexity IoT terminals, i.e., Type I terminals. Network devices and Type I terminals can perform contactless data communication, thereby reading information from Type I terminals and / or writing information that needs to be stored into Type I terminals. A-IoT technology can be used to implement one or more of the following services: inventory, positioning, sensing, and command. Typical application scenarios for A-IoT technology include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.
[0185] For example, inventory management involves using a reader (e.g., a base station or terminal device) to connect to A-IoT devices within the coverage area. Successfully connected devices need to send their unique identifier (which can be recognized by the network, such as the EPC in RFID) to the reader. Inventory management can also be called a count operation. It can obtain tag identification information; for example, the reader can use commands such as query and ACK to retrieve tag identification information.
[0186] Positioning is the process of using location signals to pinpoint the location of A-IoT devices.
[0187] Sensing involves A-IoT devices reporting sensor data to the base station, such as temperature data.
[0188] Commands can be operational instructions, such as read, write, disable, kill, or lock. A read command can read the EPC, tag identifier (TID), content stored in the tag's reserved area, or content stored in the user's storage area from the tag's memory. A write command can perform write operations on the tag's storage area; for example, a network device (e.g., a base station) can send a downlink command and data to instruct the A-IoT device to write data to its storage area. A disable command requests the A-IoT device to temporarily or permanently disable its radio frequency (RF) transmission capabilities. A kill command renders the tag permanently inoperable. A lock command can lock the tag's information, preventing read or write operations on that tag. Alternatively, a lock command can lock a storage area, preventing or disallowing read or write operations on that area; for example, a network device can send a downlink command to instruct the A-IoT device to lock the location at a specified address in the storage area, making the contents of that storage area immutable and / or unreadable.
[0189] A-IoT devices can be divided into three categories: device A, device B, and device C.
[0190] 1) Device A (similar to a passive tag): It has no energy storage, cannot generate independent signals, and uses backscattering to transmit signals.
[0191] 2) Device B (similar to a semi-passive tag): It stores energy but cannot generate signals independently; it uses backscattering to transmit signals. The stored energy can amplify the reflected signal.
[0192] 3) Device C (similar to an active tag): It has energy storage, can generate signals independently, and has active RF components for transmission.
[0193] The 3GPP meeting further defined the following three categories of A-IoT devices: device 1, device 2a, and device 2b.
[0194] 1) Device 1: Peak power consumption is approximately 1μW, with energy storage function, and initial sampling frequency offset (SFO) reaches 10. XAt parts per million (ppm), it cannot amplify downlink (DL) or uplink (UL) signals. It requires an external carrier signal for backscatter communication to enable uplink transmission.
[0195] 2) Device 2a: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset up to 10. X ppm can amplify DL and / or UL signals. An external carrier signal is required for backscatter communication in order to perform uplink transmission.
[0196] 3) Device 2b: Peak power consumption less than or equal to several hundred μW, with energy storage function, and initial sampling frequency offset of 10. X ppm, capable of DL and / or UL signal amplification. The device can perform uplink transmission without relying on an externally provided carrier.
[0197] Figure 7 shows a schematic diagram of the CN architecture and protocol stack applicable to the above-mentioned communication system 100.
[0198] As shown in Figure 7(a), A-IoT devices and A-IoT RAN can exchange A-IoT data and / or signaling via the A-IoT radio interface, and A-IoT RAN and A-IoT CN can exchange A-IoT data and / or signaling via the XX interface. The XX interface can be a next-generation (NG) interface.
[0199] The A-IoT RAN shown in Figure 7(a) has a common reader function and an A-IoT RAN node function. The common reader function refers to the ability to communicate with A-IoT devices via the A-IoT radio interface. The A-IoT RAN node function includes the ability to control A-IoT resources; in other words, it includes the ability to allocate time-frequency resources for communication between the UE or the A-IoT RAN and A-IoT devices. The A-IoT RAN can also be replaced by a gNB that supports A-IoT.
[0200] As shown in Figures 7(b) and (c), there are two scenarios between the A-IoT RAN and the ambient IoT function (AIoTF) (another example of A-IoT CN): direct connection and indirect connection (indirect path via access and mobile management function, AMF). As shown in Figure 7(b), in the case of a direct connection between the A-IoT RAN and AIoTF, the A-IoT RAN can directly interact with AIoTF for A-IoT data and / or signaling via the NG interface. As shown in Figure 7(c), in the case of an indirect connection between the A-IoT RAN and AIoTF, the A-IoT RAN can interact with AIoTF for A-IoT data and / or signaling via AMF.
[0201] As shown in Figure 7(d), the control plane protocol of the XX interface is the XX application protocol (XXAP). One possible implementation of XXAP is by including AIoTF information or cells in the next generation application protocol (NGAP). Another possible implementation of XXAP is by carrying a newly defined protocol layer on top of NGAP.
[0202] As shown in Figure 7(d), the A-IoT device includes an A-IoT radio protocol layer, used to transmit A-IoT service-related information between the A-IoT device and the A-IoT RAN. The A-IoT RAN includes one or more of the following protocol layers: A-IoT radio protocol layer, XXAP, Stream Control Transmission Protocol (SCTP), Internet Protocol (IP), Layer 1 (L1), or Layer 2 (L2). The A-IoT CN includes one or more of the following protocol layers: XXAP, SCTP, IP, L1, or L2. The A-IoT radio protocol layer includes the A-IoT physical layer (PHY) and the A-IoT MAC layer.
[0203] Figure 8 shows a schematic diagram of the CN architecture and protocol stack applicable to the above-mentioned communication system 200.
[0204] As shown in Figure 8(a), the A-IoT device and the A-IoT-enabled UE can exchange A-IoT data and / or signaling through the A-IoT wireless interface. The A-IoT-enabled UE can exchange A-IoT data and / or signaling with the A-IoT CN through the A-IoT-enabled gNB.
[0205] The A-IoT-enabled UE shown in Figure 8(a) has a general reader / writer function, and the A-IoT-enabled gNB has an A-IoT RAN node function. The general reader / writer function and the A-IoT RAN node function can be referred to the description in Figure 7 above.
[0206] The CN architecture shown in Figure 8(a) supports three transmission methods: RRC-based solution, NAS-based solution, or UP-based solution.
[0207] The basic idea of the RRC-based solution is as follows: After the base station (e.g., an A-IoT-enabled gNB) receives an A-IoT service-related request from the A-IoT CN via XXAP, the base station further sends the received relevant information to the A-IoT-enabled UE via an RRC message. When the base station receives A-IoT service-related data / signaling from the A-IoT-enabled UE via an RRC message, the base station transmits the relevant information to the A-IoT CN via XXAP / NGAP.
[0208] Figure 8(b) shows a schematic diagram of a protocol stack corresponding to the RRC-based solution. Here, the XX interface is the NG control plane (NG-C) interface. One possible implementation of XXAP is to include AIoTF information / cells in the NGAP; another possible implementation is to carry a newly defined protocol layer on top of the NGAP protocol.
[0209] As shown in Figure 8(b), an A-IoT device includes an A-IoT radio protocol layer. An A-IoT-enabled UE includes one or more of the following protocol layers: A-IoT radio protocol layer, RRC, PDCP, RLC, MAC, or PHY. An A-IoT-enabled gNB includes one or more of the following protocol layers: RRC, PDCP, RLC, MAC, PHY, XXAP, SCTP, IP, L1, or L2. An A-IoT CN includes one or more of the following protocol layers: XXAP, SCTP, IP, L1, or L2.
[0210] As shown in Figures 8(c) and (d), for the RRC-based scheme, there are two scenarios between the A-IoT-enabled gNB and the A-IoT CN: direct connection and indirect connection (e.g., an indirect path via AMF). A direct connection between the A-IoT-enabled gNB and the A-IoT CN can be shown in Figure 8(c), where AIoTF can be replaced by A-IoT CN, and Nx / XX are NG interfaces. An indirect connection between the A-IoT-enabled gNB and the A-IoT CN can be shown in Figure 8(d), where AIoTF can be replaced by A-IoT CN, and the A-IoT data and / or signaling transmitted between the AIoTF and the A-IoT-enabled gNB is carried on the NGAP.
[0211] The basic idea of the NAS-based solution is as follows: The base station (e.g., an A-IoT-enabled gNB) cannot see the A-IoT-related processes. The A-IoT CN and the A-IoT-enabled UE transmit A-IoT-related data / signaling through the DL / UL NAS packets of the A-IoT-enabled UE (that is, the A-IoT-enabled gNB transparently transmits A-IoT-related data / signaling sent to and from the A-IoT-enabled UE). The base station can use the DL NAS transport process and the UL NAS transport process on the NGAP to process the DL / UL NAS packets of the A-IoT-enabled UE.
[0212] Figure 8(e) illustrates a schematic diagram of a protocol stack corresponding to a NAS-based solution. As shown in Figure 8(e), an A-IoT device includes an A-IoT radio protocol layer. An A-IoT-enabled UE includes one or more of the following protocol layers: A-IoT radio protocol layer, A-IoT application protocol (AP), NAS or 5G access network (AN) protocol layer, etc. An A-IoT-enabled gNB includes one or more of the following protocol layers: 5G-AN protocol layer, NGAP, SCTP, IP, L1 or L2, etc. An AMF includes one or more of the following protocol layers: NAS, NGAP, SCTP, IP, L2, L1 or 5G internal protocol layer, etc. An AIoTF includes one or more of the following protocol layers: A-IoT AP or 5G internal protocol layer, etc.
[0213] The basic idea of the UP-based solution is as follows: The base station (e.g., an A-IoT-enabled gNB) does not see the A-IoT-related processes. The A-IoT service-related data / signaling between the A-IoT CN and the A-IoT-enabled UE is transmitted on the PDU session of the A-IoT-enabled UE (that is, the A-IoT-enabled gNB transparently transmits the A-IoT-related data / signaling sent to and from the A-IoT-enabled UE). The A-IoT-enabled gNB processes the user plane data of the A-IoT-enabled UE through the NG control plane (NG-U) interface general packet radio service (GPRS) tunneling protocol user plane (GTP-U) channel.
[0214] Figure 8(f) illustrates a schematic diagram of a protocol stack corresponding to a NAS-based solution. As shown in Figure 8(f), the A-IoT device includes an A-IoT radio protocol layer. An A-IoT-enabled UE includes one or more of the following protocol layers: A-IoT radio protocol layer, A-IoT-AP, transport / IP, PDU layer, or 5G-AN protocol layer, etc. An A-IoT-enabled gNB includes one or more of the following protocol layers: 5G-AN protocol layer, GTP-U, user datagram protocol, IP, L1, or L2, etc. The user plane function (UPF) includes one or more of the following protocol layers: PDU layer, GTP-U, UDP, IP, L2, L1, or 5G internal protocol layer, etc. The AIoTF includes one or more of the following protocol layers: transport / IP, or 5G internal protocol layer, etc.
[0215] The A-IoT CN in Figure 7 or Figure 8 above can also be replaced with a core network element that supports A-IoT. A core network element that supports A-IoT can be one of the following: access and mobile management function (AMF), TMF network element, ambient IoT management function (A-IoTMF), ambient IoT function (AIoTF), A-IoT aware CN, or other core network elements / nodes / devices that support or enable A-IoT.
[0216] The A-IoT-enabled UE in Figure 7 or Figure 8 above can be replaced with UEreader, intermediate node, or UE.
[0217] During the execution of a write command, the reader can send the message containing the write command to the A-IoT device in segments. This allows the A-IoT device to perform write operations on the data contained in the write command in segments, thereby improving the reliability and / or efficiency of transmission between the reader and the A-IoT device. However, during the process of the A-IoT device performing write operations on the data contained in the write command in segments, the A-IoT device may fail to perform write operations on only part of the data contained in the write command.
[0218] In view of this, embodiments of this application provide a communication method and apparatus, which, by instructing the reader and / or the core network that the A-IoT device has failed to write all the data contained in the write command or has failed to write part of the data contained in the write command, triggers the reader and / or the core network to retransmit all the data contained in the write command or retransmit the part of the data that failed to write to the A-IoT device, so that the A-IoT device can re-execute the write operation on the part of the data that failed to write.
[0219] Before introducing the scheme of this application, the following points should be noted.
[0220] (1) In this application, “instruction” may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.
[0221] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a relationship between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. Furthermore, the information to be instructed can be sent as a whole or divided into multiple sub-information pieces, and the sending period and / or timing of these sub-information pieces can be the same or different.
[0222] (2) In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to XX" can be understood as the destination of the information being XX, which may include direct transmission via the air interface or indirect transmission via the air interface by other units or modules. "Receive information from YY" can be understood as the source of the information being YY, which may include direct reception from YY via the air interface or indirect reception from YY via the air interface by other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface. In other words, sending and receiving can occur between devices, such as between network devices and terminal devices, or within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.
[0223] (3) In the various embodiments of this application, unless otherwise specified or logically conflicting, the terms and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.
[0224] (4) In this application, "first" and "second" are used for descriptive convenience only to distinguish objects and are not intended to limit the scope of the embodiments of this application. They are not used to describe the order or sequence of features. It should be understood that the objects described in this way can be interchanged where appropriate so as to describe solutions other than those in the embodiments of this application.
[0225] (5) In this application, “predefined” may mean a standard protocol predefined, or it may mean that the devices have agreed or negotiated in advance.
[0226] (6) In this application, the words “exemplary,” “for example,” etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as an “example” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word “example” is intended to present the concept in a concrete manner. In the embodiments of this application, “of,” “corresponding, relevant,” and “corresponding” may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinction is emphasized.
[0227] (7) In this document, "at least one" means one or more. "More than one" means two or more. "And / or" describes the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the related objects before and after are in an "or" relationship; in the formula of this application, the character " / " indicates that the related objects before and after are in a "division" relationship. "Including at least one of A, B and C" can mean: including A; including B; including C; including A and B; including A and C; including B and C; including A, B and C.
[0228] The method provided by the embodiments of this application will be described in detail below with reference to the accompanying drawings. The embodiments provided by this application can be applied to the communication systems shown in Figure 1 or Figure 2 above, and are not limited thereto.
[0229] It should be noted that the following description uses the interaction between A-IoT devices, readers, access network devices, and core network elements as examples to illustrate the methods provided in this application. Specifically, the A-IoT device can be replaced by an A-IoT device or a component of an A-IoT device (e.g., a chip, chip system, circuit, or communication module); the access network device can be replaced by an access network device or a component of an access network device (e.g., a chip, chip system, circuit, or communication module); and the core network element can be replaced by a core network element or a component of a core network element (e.g., a chip, chip system, circuit, or communication module). The reader can be replaced by an access network device or a terminal; and the terminal can be replaced by a terminal device or a component of a terminal device (e.g., a chip, chip system, circuit, or communication module).
[0230] It should also be noted that the first core network element in the embodiments below can be either an AMF or an AIoTF. For example, if the AIoTF is directly connected to the first reader / writer, the first core network element can be the AIoTF. If the AIoTF is not directly connected to the first reader / writer, the first core network element can be an AMF. If the first core network element is an AMF, then the first core network element interacts with the AIoTF to exchange information related to A-IoT services. For example, if the first core network element is an AMF, then in the embodiments below, the first core network element sends messages (such as message #1, etc.) to the first reader / writer based on messages from the AIoTF.
[0231] Furthermore, the steps described below as being performed by a single execution entity can also be divided into being performed by multiple execution entities, which may be logically and / or physically separate.
[0232] Figure 9 is a schematic diagram of a communication method 900 provided in an embodiment of this application. As shown in Figure 9, method 900 may include the following steps.
[0233] S901, Inventory procedure.
[0234] For example, the inventory process includes the following steps.
[0235] Step 1: The first core network element sends an inventory request to the first reader / writer. The inventory request includes the device ID of at least one A-IoT device.
[0236] At least one A-IoT device includes a first A-IoT device.
[0237] Optionally, the inventory request may also include a command indication, which is used to instruct the execution of command operations after the inventory process.
[0238] Optionally, if the first reader / writer is a terminal, then in step 1, the first core network element sends an inventory request #1 to the first access network device, and then the first access network device sends an inventory request #2 to the first reader / writer based on the inventory request #1. Inventory request #1 and inventory request #2 include the identifier of at least one A-IoT device.
[0239] The following description uses the inventory of the first A-IoT device as an example to illustrate the other steps in the inventory process.
[0240] Step 2: The first reader triggers the first A-IoT device to access the network via the A-IoT interface between the first reader and the first A-IoT device.
[0241] Step 3: The first A-IoT device performs inventory and sends uplink data to the first reader / writer. The uplink data includes the device ID of the first A-IoT device.
[0242] Step 4: The first reader sends an invention report message to the first core network element. The invention report message includes the device ID of the first A-IoT device.
[0243] Optionally, the inventory report message may also include an identifier assigned by the first access network device to the first A-IoT device (e.g., device NGAP ID, where NGAP stands for next generation application protocol). The identifier assigned by the first access network device to the first A-IoT device is used to identify the first A-IoT device in the first access network device and the first core network element.
[0244] It should be noted that S901 is an optional step. For example, if the command business executed by method 900 is implemented through a "command only" process, then method 900 may not include S901.
[0245] S902, the first core network element sends message #1 (an example of the first message).
[0246] Accordingly, the first reader receives message #1.
[0247] Message #1 instructs the first A-IoT device to perform a write operation on the first data via the first reader / writer.
[0248] For example, message #1 includes first data and the identifier of the first A-IoT device. For instance, the first data included in message #1 may be contained within a first command included in message #1; in other words, message #1 includes a first command that contains the first data, meaning the first command instructs the first A-IoT device to perform a write operation on the first data. For example, the first command is a write command.
[0249] For example, message #1 is an NGAP message.
[0250] For example, the name of message #1 may be a command request message or a downlink command transport message, or other names, which are not limited in this application.
[0251] For example, the first data included in message #1 is contained in a NAS container or an A-IoT NAS PDU, or the first command included in message #1 is contained in a NAS container or an A-IoT NAS PDU.
[0252] Optionally, if the first reader / writer is a terminal, then in S902, the first core network element sends message #1a (an example of a first message) to the first access network device, and then the first access network device sends message #1b (an example of a first message) to the first reader / writer based on the received message #1a. Messages #1a and #1b indicate that the first A-IoT device is notified via the first reader / writer to perform a write operation on the first data.
[0253] S903, the first reader sends message #2 (an example of the eighth message).
[0254] Accordingly, the first A-IoT device receives message #2.
[0255] Message #2 instructs the first A-IoT device to perform a write operation on the third data. The third data is a part of the first data.
[0256] For example, message #2 includes third data. Optionally, message #2 may also include the identifier of the first A-IoT device.
[0257] Optionally, message #2 also includes information about resource #1, which is used for communication between the first A-IoT device and the first reader. For example, the information about resource #1 can be referred to as device-to-reader (D2R) resource scheduling information. It should be understood that resource #1 is a resource allocated by the first access network device for the first A-IoT device.
[0258] For example, message #2 can be called a reader to device (R2D) message.
[0259] This application embodiment does not limit the triggering method for the first reader / writer to send message #2 to the first A-IoT device.
[0260] In one possible implementation, if the first reader / writer segments the received write command by default, then upon receiving message #1, the first reader / writer sends message #2, which contains partial data (i.e., third data) of the first data, to the first A-IoT device based on message #1.
[0261] In one possible implementation, if the length of the data contained in the write command received by the first reader exceeds the threshold #1, the first reader segments the received write command. In other words, if the length of the first data exceeds the threshold #1, the first reader sends message #2 containing part of the first data (i.e., the third data) to the first A-IoT device based on message #1.
[0262] For example, the length of data can be the amount of data included in the data, such as the number of bits contained in the data.
[0263] Optionally, in this implementation, method 900 further includes: the first core network element sending message #a (an example of the twelfth message) to the first reader / writer, message #a including one or more of the following: the length of the first data, the duration of the write operation on the first data, and the capability or type of the first A-IoT device.
[0264] Optionally, if the first reader / writer is a terminal, the step of the first core network element sending message #a to the first reader / writer can be replaced by the following steps: the first core network element sends message #a1 (an example of the twelfth message) to the first access network device, and then the first access network device sends message #a2 (an example of the twelfth message) to the first reader / writer based on the received message #a1. Message #a1 and message #a2 include one or more of the following: the length of the first data, the duration of the write operation on the first data, and the capability or type of the first A-IoT device.
[0265] Message #a is used to determine the length of the first data. For example, if message #a includes the length of the first data, the first reader / writer can directly obtain the length of the first data based on message #a. Alternatively, if message #a includes the duration of the write operation on the first data, the first reader / writer can determine the length of the first data based on the duration of the write operation. Or, if message #a includes the duration of the write operation on the first data and the capabilities or type of the first A-IoT device, the first reader / writer can determine the speed at which the first A-IoT device performs the write operation based on the capabilities or type of the first A-IoT device, and then determine the length of the first data based on the duration of the write operation and the speed of the write operation.
[0266] Optionally, threshold #1 can be a predefined or preconfigured threshold, or threshold #1 can be a threshold indicated by the first core network element or the first A-IoT device to the first reader / writer, or threshold #1 can be related to the buffer capability or buffer size of the first A-IoT device. For example, the buffer capability or buffer size of the first A-IoT device represents the maximum length of data corresponding to a single write operation performed by the first A-IoT device.
[0267] Optionally, if the first reader does not obtain the caching capacity or caching size of the first A-IoT device, the method 900 further includes: the first A-IoT device sending a message #b (an example of the thirteenth message) to the first reader, the message #b indicating the caching capacity or caching size of the first A-IoT device.
[0268] Optionally, if the first reader does not obtain the caching capacity or caching size of the first A-IoT device, method 900 further includes: the first core network element sending message #c (an example of the thirteenth message) to the first reader, where message #c indicates the caching capacity or caching size of the first A-IoT device. Specifically, the first core network element may send message #c to the first reader upon receiving message #d (an example of the fifteenth message) from the first A-IoT device, where message #d indicates the caching capacity or caching size of the first A-IoT device. Alternatively, the first core network element may send message #c to the first reader upon receiving message #d1 from the application function, where message #d1 indicates the caching capacity or caching size of the first A-IoT device.
[0269] Optionally, if the first reader / writer is a terminal, the step of the first core network element sending message #c to the first reader / writer can be replaced by the following steps: the first core network element sends message #c1 (an example of the thirteenth message) to the first access network device, and then the first access network device sends message #c2 (an example of the thirteenth message) to the first reader / writer based on the received message #c1. Here, message #c1 and message #c2 represent the caching capacity or cache size of the first A-IoT device.
[0270] S904, the first A-IoT device sends message #3 (an example of the ninth message).
[0271] Accordingly, the first reader receives message #3.
[0272] Message #3 indicates that the first A-IoT device has successfully written the third data. In other words, message #3 indicates that the first A-IoT device has successfully performed the write operation on the third data.
[0273] Optionally, if message #2 includes information from resource #1, then the first A-IoT device sends message #3 through resource #1.
[0274] For example, message #3 is a MAC message or a MAC control element (CE).
[0275] Optionally, S904 can be replaced with the following steps.
[0276] Step a: The first A-IoT device sends information #x1 to the first core network element through the first reader / writer. Information #x1 indicates that the first A-IoT device has successfully performed a write operation on the third data. For example, information #x1 is contained in the NAS container or A-IoT NAS PDU.
[0277] Step b: The first core network element sends information #x2 to the first reader / writer. Information #x2 indicates that the first A-IoT device has successfully performed a write operation on the third data.
[0278] It should be noted that steps S903 to S904 are optional. For example, if the first reader receives message #1 and first sends message #4 to the first A-IoT device instead of sending message #2, then method 900 does not include steps S903 to S904.
[0279] S905, the first reader sends message #4 (an example of the second message).
[0280] Correspondingly, the first A-IoT device receives message #4.
[0281] Message #4 instructs the first A-IoT device to perform a write operation on the second data. The second data is a part of the first data and is different from the third data.
[0282] For example, message #4 includes second data. Optionally, message #4 may also include the identifier of the first A-IoT device.
[0283] Optionally, message #4 also includes information about resource #2, which is used for communication between the first A-IoT device and the first reader / writer. For example, the information about resource #2 can be referred to as D2R resource scheduling information. It should be understood that resource #2 is a resource allocated by the first access network device for the first A-IoT device.
[0284] For example, message #4 can be called an R2D message.
[0285] The triggering method for the first reader to send message #4 to the first A-IoT device can be referred to the triggering method for the first reader to send message #2 to the first A-IoT device described in S903 above. For the sake of brevity, this application will not repeat it here.
[0286] S906, the first reader determines that the first A-IoT device has failed to write the second data.
[0287] The S906 can also be replaced by a first reader / writer that determines that the first A-IoT device failed to perform a write operation on the second data.
[0288] The embodiments of this application do not limit the method by which the first reader determines that the first A-IoT device has failed to write the second data.
[0289] For example, if the first reader receives message #e (an example of the eleventh message) from the first A-IoT device, and message #e indicates that the first A-IoT device failed to perform a write operation on the second data, then the first reader determines that the first A-IoT device failed to perform a write operation on the second data.
[0290] Optionally, message #e also indicates the reason why the first A-IoT device failed to perform a write operation on the second data.
[0291] For example, if the first reader receives a message #f from the first core network element, and message #f indicates that the first A-IoT device failed to perform a write operation on the second data, then the first reader determines that the first A-IoT device failed to perform a write operation on the second data.
[0292] When the first core network element receives message #f1 from the first A-IoT device through the first reader / writer, it can send message #f to the first reader / writer. Message #f1 indicates that the first A-IoT device failed to perform a write operation on the second data. Message #f1 is contained in the NAS container or A-IoT NAS PDU.
[0293] For example, if no message is received from the first A-IoT device within a first time period after the first reader sends message #4, the first reader determines that the first A-IoT device has failed to perform a write operation on the second data.
[0294] The duration of the first time period is either a predefined or pre-configured duration, or the duration of the first time period is determined by the first reader / writer based on the message received from the first core network element.
[0295] For example, method 900 further includes: the first core network element sending message #g (an example of the twelfth message) to the first reader / writer, where message #g indicates the duration of the first time period. Alternatively, method 900 further includes: the first core network element sending message #g1 (an example of the twelfth message) to the first access network device; the first access network device sending message #g2 (an example of the twelfth message) to the first reader / writer based on the received message #g1, where messages #g1 and #g2 indicate the duration of the first time period.
[0296] For example, method 900 further includes: the first core network element sending message #a to the first reader / writer. The description of message #a can be found in section S903 above. Upon receiving message #a, the first reader / writer can determine the duration of the first time period based on message #a.
[0297] S907, the first reader sends message #5 (an example of the fourth message).
[0298] Correspondingly, the first core network element receives message #5.
[0299] Message #5 indicates that the first A-IoT device failed to write the first data; in other words, message #5 indicates that the first A-IoT device failed to perform a write operation on the first data. Alternatively, message #5 indicates that the first A-IoT device failed to execute the first command.
[0300] Optionally, if the first reader / writer is a terminal, then in S907, the first reader / writer sends message #5a (an example of the fourth message) to the first access network device, and then the first access network device sends message #5b (an example of the fourth message) to the first core network element based on the received message #5a. Messages #5a and #5b indicate that the first A-IoT device failed to perform a write operation on the first data.
[0301] S908, the first core network element sends message #6 (an example of the fifth message).
[0302] Correspondingly, the first reader receives message #6.
[0303] Message #6 instructs the first A-IoT device to perform a write operation on the first data via the first reader / writer.
[0304] For example, message #6 includes first data and the identifier of the first A-IoT device. For instance, the first data included in message #6 may be contained within a first command included in message #6; in other words, message #6 includes a first command that contains the first data, meaning the first command instructs the first A-IoT device to perform a write operation on the first data. For example, the first command is a write command.
[0305] For more details on S908, please refer to the description in S901 above.
[0306] It should be noted that steps S907 and S908 are optional. For example, if the first reader / writer determines that the first A-IoT device has failed to perform a write operation on the second data, it can execute step S909 as described below, in which case method 900 may not include steps S907 and S908.
[0307] S909, the first reader sends message #7 (an example of the third message).
[0308] Accordingly, the first A-IoT device receives message #7.
[0309] Message #7 instructs the first A-IoT device to perform a write operation on the first data.
[0310] It should be understood that since the first data includes the second data mentioned above, when message #7 instructs the first A-IoT device to perform a write operation on the first data, it is equivalent to message #7 instructing the first A-IoT device to perform a write operation on the second data.
[0311] For example, message #7 includes first data. Optionally, message #7 may also include the identifier of the first A-IoT device.
[0312] Optionally, message #7 may also include information about resource #3, which is used for communication between the first A-IoT device and the first reader / writer. It should be understood that resource #3 is a resource allocated by the first access network device for the first A-IoT device.
[0313] Optionally, message #7 also includes a retransmission instruction.
[0314] Optionally, if method 800 does not execute S807 and S808 above, then in S809, the message #7 sent by the first reader / writer is the same as message #4 in S805 above. In other words, message #7 instructs the first A-IoT device to perform a write operation on the second data. For example, message #7 includes the second data. Optionally, message #7 also includes the identifier of the first A-IoT device.
[0315] In one possible implementation, the first reader sends message #7 to the first A-IoT device when the first condition is met.
[0316] The first condition includes one or more of the following: the number of times the first A-IoT device fails to perform write operations on part or all of the first data does not exceed a first threshold, or the number of times the first A-IoT device fails to perform write operations on the second data does not exceed a second threshold. The first threshold or the second threshold is a predefined or pre-configured threshold, or it may be a threshold indicated by the first core network element to the first reader / writer; this application does not limit the specific threshold in this regard.
[0317] Optionally, if the first reader does not receive a message from the first A-IoT device within a first time period after sending message #4 to the first A-IoT device, then before S909, method 900 further includes: the first reader sending message #h (an example of the fourteenth message) to the first A-IoT device, message #h indicating that the first A-IoT device accesses the network. For example, message #h could be a paging message or an inventory request. In other words, if the first reader does not receive a message from the first A-IoT device, the first reader can determine that the first A-IoT device is out of power. In this case, the first reader can send message #h to the first A-IoT device to trigger the first A-IoT device to re-access the network. If the first reader receives a message from the first A-IoT device, the first reader can determine that the first A-IoT device is powered. In this case, the first reader may not trigger the first A-IoT device to re-access the network.
[0318] In this embodiment, the reader sends a message containing a write command to the A-IoT device in segments. During the process of the A-IoT device performing a segmented write operation on the data contained in the write command, if the reader determines that the A-IoT device has failed to perform a write operation on part of the data contained in the write command, the reader can retransmit the failed part of the data to the A-IoT device. Alternatively, the reader can indicate to the first core network element that the first A-IoT device has failed to perform a write operation on the data contained in the write command, thereby triggering the core network element to resend the data contained in the write command to the A-IoT device through the reader, so that the A-IoT device can re-perform the write operation on the failed data.
[0319] Figure 10 is a schematic diagram of a communication method 1000 provided in an embodiment of this application. As shown in Figure 10, method 1000 may include the following steps.
[0320] S1001, Inventory procedure.
[0321] S1002, the first core network element sends message #1 (an example of the first message).
[0322] Accordingly, the first reader receives message #1.
[0323] S1003, the first reader sends message #2 (an example of the eighth message).
[0324] Accordingly, the first A-IoT device receives message #2.
[0325] S1004, the first A-IoT device sends message #3 (an example of the ninth message).
[0326] Accordingly, the first reader receives message #3.
[0327] S1005, the first reader sends message #4 (an example of the second message).
[0328] Correspondingly, the first A-IoT device receives message #4.
[0329] S1006, the first reader determines that the first A-IoT device failed to write the second data.
[0330] For further description of S1001 to S1006, please refer to S901 to S906 in Method 900 above.
[0331] S1007, the first reader sends message #9 (an example of the sixth message).
[0332] Correspondingly, the first core network element receives message #9.
[0333] Message #9 includes a first message and a second message. The first message includes the second data, and the second message indicates that the first A-IoT device failed to perform a write operation on the second data.
[0334] For example, the first information is contained in the NAS container or the A-IoT NAS PDU, or the first information is the NAS container or the A-IoT NAS PDU.
[0335] Optionally, if method 1000 includes S1003 and S1004 before S1005, then message #9 also includes fourth information, which includes third data.
[0336] Optionally, if message #9 includes the fourth information, message #9 may also include the fifth information, which indicates that the first A-IoT device has successfully performed a write operation on the third data.
[0337] It should be noted that the embodiments of this application take the execution of S1003 and S1004 before S1005 as an example for illustration. If, before S1005, the first reader / writer also instructs the first A-IoT device to perform a write operation on the fourth data in the first data that is different from the third data and the third data, and the first A-IoT device successfully performs the write operation on the fourth data, then message #9 also includes information #x, and information #x includes the fourth data.
[0338] Optionally, if the first reader / writer is a terminal, then in S1007, the first reader / writer sends message #9a (an example of the sixth message) to the first access network device, and then the first access network device sends message #9b (an example of the sixth message) to the first core network element based on the received message #9a. Message #9a and message #9b include first information and second information.
[0339] Furthermore, method 1000 includes S1008a and S1009a, or S1008b and S1009b.
[0340] S1008a, the first core network element sends message #10 (an example of the seventh message).
[0341] Accordingly, the first reader receives message #10.
[0342] Message #10 instructs the first A-IoT device to perform a write operation on the first data via the first reader / writer; in other words, message #10 includes a first command. Message #10 also includes information #x (an example of third information), which indicates one or more of the following: the start position of the write operation on the first data, the length of the write operation on the first data, and the end position of the write operation on the first data.
[0343] For example, message #10 includes first data and the identifier of the first A-IoT device. For instance, the first data included in message #10 may be contained within the first command included in message #10.
[0344] For example, message #10 is an NGAP message.
[0345] For example, message #10 could be a command request message or a downlink command transmission message.
[0346] For example, the first data included in message #10 is contained in a NAS container or an A-IoT NAS PDU, or the first command included in message #10 is contained in a NAS container or an A-IoT NAS PDU.
[0347] Optionally, the first core network element determines information #x based on message #9. For example, the starting position of the write operation on the first data indicated by information #x is the starting position of the second data within the first data. Another example is that the length of the write operation on the first data indicated by information #x is the length of the second data.
[0348] It should be understood that when the first core network element receives message #9 from the first reader / writer, it can determine based on message #9 that the first A-IoT device failed to perform a write operation on the second data. Then, the first core network element can carry information #x in message #10 to instruct the first A-IoT device to re-perform the write operation on the second data in the first data.
[0349] Optionally, if the first reader / writer is a terminal, then in S1008a, the first core network element sends message #10a (an example of the seventh message) to the first access network device, and then the first access network device sends message #10b (an example of the seventh message) to the first reader / writer based on the received message #10a. Messages #10a and #10b indicate that the first A-IoT device is notified via the first reader / writer to perform a write operation on the first data. Messages #10a and #10b also include information #x.
[0350] S1009a, the first reader sends message #12 (an example of the third message).
[0351] Accordingly, the first A-IoT device receives message #12 (an example of the third message).
[0352] Message #12 instructs the first A-IoT device to perform a write operation on the first data. Message #12 also includes the information #x mentioned in S1008a above.
[0353] It should be understood that when message #12 includes information #x, it is possible to instruct the first A-IoT device to perform a write operation on at least the second data included in the first data through information #x. Therefore, when message #12 instructs the first A-IoT device to perform a write operation on the first data, it is equivalent to message #12 instructing the first A-IoT device to perform a write operation on the second data.
[0354] For example, message #12 includes first data. Optionally, message #12 may also include the identifier of the first A-IoT device.
[0355] Optionally, message #12 may also include information about resource #4, which is used for communication between the first A-IoT device and the first reader / writer. It should be understood that resource #4 is a resource allocated by the first access network device for the first A-IoT device.
[0356] Optionally, message #12 may also include a retransmission instruction.
[0357] In one possible implementation, the first reader sends message #12 to the first A-IoT device when a first condition is met. The first condition can be referred to in S909 of method 900 above.
[0358] Optionally, if the first reader does not receive a message from the first A-IoT device within a first time period after sending message #4 to the first A-IoT device, then before S1009a, method 1000 further includes: the first reader sending message #h (an example of the fourteenth message) to the first A-IoT device, message #h indicating that the first A-IoT device accesses the network. For example, message #h may be a paging message or an inventory request.
[0359] In this embodiment, the reader sends a message containing a write command to the A-IoT device in segments. During the process of the A-IoT device performing a segmented write operation on the data contained in the write command (e.g., the first data), if the reader determines that the A-IoT device has failed to perform a write operation on a portion of the data contained in the write command (e.g., the second data), the reader can send the second data to the core network element and instruct the A-IoT device that the write operation on the second data has failed. This triggers the core network element to resend the first data to the A-IoT device through the first reader and instruct the A-IoT device on the location where the write operation on the first data was performed. This allows the A-IoT device to re-perform the write operation on the second data that failed to be written without having to re-perform the write operation on the successfully written data in the first data.
[0360] S1008b, the first core network element sends message #11 (example of the tenth message).
[0361] Accordingly, the first reader receives message #11.
[0362] Message #11 instructs the first A-IoT device to perform a write operation on the second data via the first reader / writer.
[0363] For example, message #11 includes second data and the identifier of the first A-IoT device. For instance, the second data included in message #11 may be contained within a second command included in message #11; in other words, message #11 includes a second command that contains the second data, meaning the second command instructs the first A-IoT device to perform a write operation on the second data. For example, the second command is a write command.
[0364] For example, message #11 is an NGAP message.
[0365] For example, message #11 could be a command request message or a downlink command transmission message.
[0366] For example, the second data included in message #11 is contained in a NAS container or an A-IoT NAS PDU, or the second write command included in message #11 is contained in a NAS container or an A-IoT NAS PDU.
[0367] It should be understood that when the first core network element receives message #9 from the first reader / writer, it can determine based on message #9 that the first A-IoT device failed to perform a write operation on the second data. Then, the first core network element can send message #11 to the first reader / writer to instruct the first A-IoT device to re-perform the write operation on the second data in the first data.
[0368] Optionally, if the first reader / writer is a terminal, then in S1008b, the first core network element sends message #11a (an example of the tenth message) to the first access network device, and then the first access network device sends message #11b (an example of the tenth message) to the first reader / writer based on the received message #11a. Messages #11a and #11b indicate that the first A-IoT device is notified via the first reader / writer to perform a write operation on the second data.
[0369] S1009b, the first reader sends message #13 (an example of the third message).
[0370] Accordingly, the first A-IoT device receives message #13 (an example of the third message).
[0371] It should be understood that when message #11 instructs the first A-IoT device to perform a write operation on the second data via the first reader, although the first reader does not perceive that message #11 contains the second data, the message #13 sent by the first reader to the first A-IoT device based on message #11 contains the second data, which is equivalent to message #13 having the function of instructing the first A-IoT device to perform a write operation on the second data.
[0372] For example, message #13 includes second data.
[0373] Optionally, message #13 may also include information about resource #5, which is used for communication between the first A-IoT device and the first reader / writer. It should be understood that resource #5 is a resource allocated by the first access network device for the first A-IoT device.
[0374] Optionally, message #13 may also include a retransmission instruction.
[0375] In one possible implementation, the first reader sends message #13 to the first A-IoT device when a first condition is met. The first condition can be referred to in S909 of method 900 above.
[0376] Optionally, if the first reader does not receive a message from the first A-IoT device within a first time period after sending message #4 to the first A-IoT device, then before S1009b, method 1000 further includes: the first reader sending message #h (an example of the fourteenth message) to the first A-IoT device, message #h indicating that the first A-IoT device accesses the network. For example, message #h may be a paging message or an inventory request.
[0377] In this embodiment, the reader sends a message containing a write command to the A-IoT device in segments. During the process of the A-IoT device performing a segmented write operation on the data contained in the write command (e.g., the first data), if the reader determines that the A-IoT device has failed to perform a write operation on a portion of the data contained in the write command (e.g., the second data), the reader can send the second data to the core network element and instruct the A-IoT device that the write operation on the second data has failed. This triggers the core network element to resend the second data to the A-IoT device through the reader, thereby enabling the A-IoT device to re-perform the write operation on the second data that failed to be written without having to re-perform the write operation on the successfully written data in the first data.
[0378] Figure 11 is a schematic diagram of a communication method 1100 provided in an embodiment of this application. As shown in Figure 11, method 1100 may include the following steps.
[0379] S1101, the first core network element sends message #14.
[0380] Accordingly, the first reader receives message #14.
[0381] Message #14 requests an inventory of at least one A-IoT device. Message #14 includes the device ID of at least one A-IoT device. At least one A-IoT device includes a first A-IoT device.
[0382] For example, message #14 is an inventory request.
[0383] Optionally, the inventory request may also include a command indication, which is used to instruct the execution of command operations after the inventory process.
[0384] Optionally, if the first core network element has pre-obtained the caching capacity or cache size of the first A-IoT device (for example, the first core network element can obtain the caching capacity or cache size of the first A-IoT device from the application function), then message #14 also indicates the caching capacity or cache size of the first A-IoT device. In the case where message #14 also indicates the caching capacity or cache size of the first A-IoT device, message #14 is an example of a thirteenth message.
[0385] Optionally, if the first reader / writer is a terminal, then in S1101, the first core network element sends message #14a to the first access network device, and then the first access network device sends message #14b to the first reader / writer based on message #14a. Messages #14a and #14b include the identifier of at least one A-IoT device, and messages #14a and #14b indicate that at least one A-IoT device should be inventoried.
[0386] The following describes the other steps of method 1100 using the inventory of the first A-IoT device as an example.
[0387] S1102, the first reader / writer sends message #15.
[0388] Accordingly, the first A-IoT device receives message #15.
[0389] Message #15 is used to trigger the first A-IoT device to access the network. For example, message #15 is an A-IoT paging message or an inventory request.
[0390] S1103, the first A-IoT device sends message #16.
[0391] Accordingly, the first reader receives message #16.
[0392] Message #16 includes the identifier of the first A-IoT device, such as the device ID of the first A-IoT device.
[0393] Optionally, message #16 may also indicate the caching capacity or cache size of the first A-IoT device. In the case where message #16 also indicates the caching capacity or cache size of the first A-IoT device, message #16 is an example of the fifteenth message.
[0394] S1104, the first reader / writer sends message #17.
[0395] Correspondingly, the first core network element receives message #17.
[0396] Message #17 includes the identifier of the first A-IoT device, such as the device ID of the first A-IoT device.
[0397] Optionally, if message #16 also indicates the caching capacity or cache size of the first A-IoT device, then message #17 also indicates the caching capacity or cache size of the first A-IoT device.
[0398] Optionally, if the first reader / writer is a terminal, then in S1104, the first reader / writer sends message #17a to the first access network device, and then the first access network device sends message #17b to the first core network element based on the received message #17a. Message #17a and message #17b include the identifier of the first A-IoT device, such as the device ID of the first A-IoT device.
[0399] S1105, the first core network element sends message #18 (an example of the sixteenth or seventeenth message).
[0400] Accordingly, the first reader receives message #18.
[0401] Message #18 instructs the first A-IoT device to execute write command #1 (an example of the first command) or command #1 (an example of the first command) via the first reader / writer. In other words, message #18 includes write command #1 or command #1. Command #1 can be a write command or a read command, etc., and this application does not limit its scope.
[0402] For example, if message #18 indicates that the first A-IoT is notified to execute write command #1 via the first reader / writer, then message #18 also indicates the length of the data contained in write command #1. In the case where message #18 also indicates the length of the data contained in write command #1, message #18 is an example of the sixteenth message.
[0403] Optionally, message #18 also indicates the duration of the write command execution.
[0404] Optionally, message #18 also indicates the capabilities or type of the first A-IoT device.
[0405] Optionally, if message #18 indicates the length of the data contained in write command #1, then method 1100 further includes: the first reader / writer determining the duration of executing write command #1 based on the length of the data contained in write command #1.
[0406] Optionally, if message #18 also indicates the capabilities or type of the first A-IoT device, or if the first reader receives message #z from the first A-IoT device, message #z indicating the capabilities or type of the first A-IoT device, then the first reader determines the duration of executing the write command #1 based on the length of the data contained in the write command #1, including: the first reader determines the duration of executing the write command #1 based on the length of the data contained in the write command #1 and one or more of the following: the capabilities of the first A-IoT device, the type of the first A-IoT device, or distance information.
[0407] The capability or type of the first A-IoT device is related to the speed at which it executes write commands. The faster the first A-IoT device executes write commands, the shorter the execution time of write command #1, as determined by the first reader / writer based on the capability or type of the first A-IoT device. For example, the order of write command execution speeds of different types of A-IoT devices from fastest to slowest is: device 2b, device 2a, device 1.
[0408] The distance information is related to the distance between the first reader and the first A-IoT device. For example, the distance information indicates the actual distance between the first reader and the first A-IoT device, or the distance information indicates the distance level (or coverage level) between the first reader and the first A-IoT device, or the distance information indicates the coverage area or coverage level of the first reader.
[0409] Optionally, if message #18 indicates the length of the data contained in write command #1, then method 1100 further includes: the first reader / writer determining information about the first resource based on the length of the data contained in write command #1.
[0410] The first resource is used for communication between the first reader / writer and the first A-IoT device. For example, the information of the first resource includes the effective duration of the first resource, or in other words, the information of the first resource includes the duration corresponding to the time-domain resource of the first resource.
[0411] Optionally, the first reader / writer determines the information of the first resource based on the length of the data contained in the write command #1, including: the first reader / writer determining the duration of executing the write command #1 based on the length of the data contained in the write command #1; and the first reader / writer determining the information of the first resource based on the duration of executing the write command #1. For example, the longer the duration of executing the write command #1, the longer the effective duration of the first resource; the shorter the duration of executing the write command #1, the shorter the effective duration of the first resource.
[0412] Optionally, if message #18 indicates the length of the data contained in write command #1, then method 1100 further includes: the first reader / writer determining a first duration based on the length of the data contained in write command #1. The first duration is used to determine whether the first A-IoT device has failed to execute write command #1.
[0413] For example, the method by which the first reader determines whether the first A-IoT device failed to execute write command #1 based on a first duration includes: if the first reader does not receive message #20 from the first A-IoT device within a first time period after sending message #19 to the first A-IoT device according to message #18, then the first reader determines that the first A-IoT device failed to execute write command #1. The duration of the first time period is related to a first duration. For example, the duration of the first time period is equal to the first duration, or the duration of the first time period is less than the first duration.
[0414] Optionally, the first reader / writer determines the first duration based on the length of the data contained in the write command #1, including: the first reader / writer determining the duration of executing the write command #1 based on the length of the data contained in the write command #1; and the first reader / writer determining the first duration based on the duration of executing the write command #1. For example, the longer the duration of executing the write command #1, the longer the first duration; the shorter the duration of executing the write command #1, the shorter the first duration.
[0415] For example, if message #18 indicates that the first A-IoT device is notified to execute command #1 via the first reader / writer, then message #18 also indicates the duration of executing command #1. In the case where message #18 also indicates the duration of executing command #1, message #18 is an example of the seventeenth message.
[0416] Optionally, message #18 also indicates the capabilities or type of the first A-IoT device.
[0417] Optionally, method 1100 further includes: the first reader determining information about the second resource based on the duration of execution of command #1.
[0418] The description of the information for the second resource can be found in the description of the information for the first resource above.
[0419] For example, the longer the execution time of command #1, the longer the effective duration of the second resource; the shorter the execution time of command #1, the shorter the effective duration of the second resource.
[0420] Optionally, method 1100 further includes: the first reader determining a second duration based on the duration of executing command #1. The second duration is used to determine whether the first A-IoT device failed to execute command #1.
[0421] For example, the way the first reader determines whether the first A-IoT device has failed to execute command #1 based on the second duration can be referred to the above method of the first reader determining whether the first A-IoT device has failed to execute write command #1 based on the first duration.
[0422] For example, the longer the execution time of command #1, the longer the second execution time will be; the shorter the execution time of command #1, the shorter the second execution time will be.
[0423] Optionally, if the first reader / writer is a terminal, then in S1105, the first core network element sends message #18a to the first access network device, and then the first access network device sends message #18b to the first reader / writer based on message #18a. Messages #18a and #18b have the same function as message #18.
[0424] S1106, the first reader / writer sends message #19.
[0425] Accordingly, the first A-IoT device receives message #19.
[0426] For example, message #19 instructs the first A-IoT device to execute a command.
[0427] For example, if message #18 instructs the first A-IoT device to execute write command #1 via the first reader / writer, then message #19 instructs the first A-IoT device to execute write command #1.
[0428] Optionally, if the first reader also determines information about the first resource, message #19 may also include information about the first resource.
[0429] For example, if message #18 instructs the first A-IoT device to execute command #1 via the first reader / writer, then message #19 instructs the first A-IoT device to execute command #1.
[0430] Optionally, if the first reader also determines information about the second resource, message #19 may also include information about the second resource.
[0431] Optionally, method 1100 also includes S1107.
[0432] S1107, the first A-IoT device sends message #20.
[0433] Accordingly, the first reader receives message #20.
[0434] Message #20 indicates command feedback.
[0435] For example, if message #19 instructs the first A-IoT device to execute write command #1, then message #20 instructs the first A-IoT device to execute write command #1 either successfully or failed.
[0436] Optionally, if message #19 also includes information about the first resource, then the first A-IoT device sends message #20 through the first resource.
[0437] For example, if message #19 instructs the first A-IoT device to execute command #1, then message #20 instructs the first A-IoT device to either fail or succeed in executing write command #1.
[0438] Optionally, if message #19 also includes information about the second resource, then the first A-IoT device sends message #20 through the second resource.
[0439] It should be understood that if the first A-IoT device fails to execute write command #1 due to power failure or command #1 fails, the first A-IoT device will be unable to send message #20 to the first reader / writer.
[0440] S1108, the first reader / writer sends message #21.
[0441] Correspondingly, the first core network element receives message #21.
[0442] Message #21 indicates command feedback.
[0443] For example, if message #18 indicates that the first A-IoT device is notified to execute write command #1 via the first reader / writer, then message #21 indicates whether the first A-IoT device failed or succeeded in executing write command #1.
[0444] Specifically, if the first reader receives message #20, and message #20 indicates that the first A-IoT device successfully executed write command #1, then message #21 indicates that the first A-IoT device successfully executed write command #1. Alternatively, if the first reader receives message #20, and message #20 indicates that the first A-IoT device failed to execute write command #1, then message #21 indicates that the first A-IoT device failed to execute write command #1. Alternatively, if the first reader does not receive a message from the first A-IoT device within a first time period after sending message #19, then message #21 indicates that the first A-IoT device failed to execute write command #1. The duration of the first time period is related to a first duration.
[0445] For example, if message #18 instructs the first A-IoT device to execute command #1, then message #21 instructs the first A-IoT device to either fail or succeed in executing command #1.
[0446] Specifically, if the first reader receives message #20, and message #20 indicates that the first A-IoT device successfully executed command #1, then message #21 indicates that the first A-IoT device successfully executed command #1. Alternatively, if the first reader receives message #20, and message #20 indicates that the first A-IoT device failed to execute command #1, then message #21 indicates that the first A-IoT device failed to execute command #1. Alternatively, if the first reader does not receive a message from the first A-IoT device within a first time period after sending message #19, then message #21 indicates that the first A-IoT device failed to execute command #1. The duration of the first time period is related to the second time period.
[0447] In this embodiment, the first core network element can indicate command-related information to the first reader, such as the duration of command execution, the length of data contained in the write command, and the capabilities or type of the A-IoT device executing the command. This enables the first reader to determine information about resources related to the command, determine whether the A-IoT device has failed to execute the command, etc., based on the command-related information. This simplifies the processing logic of the first reader and / or provides data support for the first reader to determine how to process received messages.
[0448] As mentioned above, the access network equipment involved in this implementation example can be an O-RAN architecture. The following is a brief introduction to the application of the communication methods shown in Figures 9 to 11 above under the O-RAN architecture.
[0449] Under the O-RAN architecture, the RIC can directly control both gNB-CU and gNB-DU. Therefore, the "access network device" in the communication method steps shown in Figures 9 to 11 above needs to be expanded to "CU" and "DU".
[0450] As one possible implementation, the access network device receives messages from the reader, including: the DU of the access network device receiving message #z1 from the reader (e.g., message #z1 is an RRC message); the DU of the access network device sending message #z2 to the CU of the access network device based on message #z1 (e.g., message #z2 is an F1 application protocol (F1AP) message). Furthermore, the CU of the access network device can send message #z3 to the core network element based on message #z2 (message #z3 can be an XXAP message or an NGAP message).
[0451] Message #z2 contains information #z2 that is related to information #z1 in message #z1. For example, information #z1 and information #z2 are the same, or information #z2 is obtained by the DU of the access network device processing information #z1 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information). Message #z3 contains information #z3 that is related to information #z2 in message #z2. For example, information #z3 and information #z2 are the same, or information #z3 is obtained by the CU of the access network device processing information #z2 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information).
[0452] For example, message #z1 can be message #5a, message #9a, or message #17a, etc., in the above embodiments.
[0453] In one possible implementation, the access network device receives messages from core network elements, including: the access network device's CU receiving message #z4 from the core network element (message #z4 can be an XXAP message or an NGAP message); the access network device's CU sending message #z5 to the access network device's DU based on message #z4 (for example, message #z2 is an F1AP message). Furthermore, the access network device's DU can send message #z6 to the reader based on the received message #z5.
[0454] Message #z5 contains information #z5 that is related to information #z4 in message #z4. For example, information #z4 and information #z5 are the same, or information #z5 is obtained by the CU of the access network device processing information #z4 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information). Message #z6 contains information #z6 that is related to information #z5 in message #z5. For example, information #z5 and information #z6 are the same, or information #z6 is obtained by the DU of the access network device processing information #z5 (e.g., deleting, filtering, mapping, modifying, or adding auxiliary information).
[0455] For example, message #z4 can be message #1a, message #10a, message #11a, or message #18a, etc., as described in the above embodiments.
[0456] It should be understood that the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0457] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0458] It should also be understood that in some of the above embodiments, exemplary descriptions have been provided using devices in existing network architectures (such as A-IoT devices or core network elements). It should be understood that the specific form of the device is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.
[0459] It is understood that the methods and operations implemented by devices (such as A-IoT devices, readers, or core network elements) in the above-described method embodiments can also be implemented by components (such as chips or circuits).
[0460] Those skilled in the art will recognize that, based on the units and algorithm steps described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is implemented in hardware or by computer software driving hardware 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 this application.
[0461] The communication device provided in this application is described in detail below with reference to Figures 12 to 14. It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, for details not described in detail, please refer to the method embodiments above; for brevity, some details will not be repeated.
[0462] This application embodiment can divide the transmitting or receiving device into functional modules according to the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the division of functional modules according to each function as an example.
[0463] Figure 12 is a schematic block diagram of a communication device 1200 provided in an embodiment of this application. The device 1200 includes a transceiver module 1210 and a processing module 1220. The transceiver module 1210 can implement corresponding communication functions, and the processing module 1220 is used for data processing. In other words, the transceiver module 1210 is used to perform operations related to receiving and sending, and the processing module 1220 is used to perform other operations besides receiving and sending. The transceiver module 1210 can also be referred to as a communication interface, communication unit, or transceiver unit, and the processing module 1220 can also be referred to as a processing unit.
[0464] Optionally, the device 1200 may further include a storage module 1230, which can be used to store instructions and / or data. The processing module 1220 can read the instructions and / or data from the storage module to enable the device to perform the operations of the equipment in the foregoing method embodiments. The storage module 1230 may also be referred to as a storage unit.
[0465] In one design, the device 1200 may correspond to the first reader / writer in the above method embodiments.
[0466] The device 1200 can implement the steps or processes corresponding to the first reader / writer executed in the above method embodiment. The transceiver module 1210 can be used to perform the transceiver-related operations of the first reader / writer in the above method embodiment, and the processing module 1220 can be used to perform the processing-related operations of the first reader / writer in the above method embodiment.
[0467] In one possible implementation, transceiver module 1210 is configured to receive a first message from a first core network element or a first access network device, the first message including a first command instructing a first A-IoT device to perform a write operation on first data. Transceiver module 1210 is further configured to send a second message to the first A-IoT device, the second message instructing the first A-IoT device to perform a write operation on second data, the second data being a portion of the first data. Processing module 1220 is configured to determine that the first A-IoT device's write operation on the second data has failed. Transceiver module 1210 is further configured to send a third message to the first A-IoT device, the third message instructing the first A-IoT device to perform a write operation on the second data.
[0468] In one possible implementation, transceiver module 1210 is used to receive a sixteenth message, which indicates the length of the data contained in the first write command.
[0469] In one possible implementation, the transceiver module 1210 is used to receive the seventeenth message, which indicates the duration of executing the first command.
[0470] When the device 1200 is used to execute the method in FIG9, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S902, S903, S904, S905, S907, S908 or S909. The processing module 1220 can be used to execute the processing steps in the method, such as S906.
[0471] When the device 1200 is used to execute the method in FIG10, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S1002, S1003, S1004, S1005, S1007, S1008a, S1008b, S1009a or S1009b. The processing module 1220 can be used to execute the processing steps in the method, such as S1006.
[0472] When the device 1200 is used to execute the method in FIG11, the transceiver module 1210 can be used to execute the steps of transmitting and receiving information in the method, such as one or more steps in S1101 to S1108. The processing module 1220 can be used to execute the processing steps in the method.
[0473] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.
[0474] In another design, the device 1200 may correspond to the first A-IoT device in the above method embodiments, or to a component (such as a chip) of the first A-IoT device.
[0475] The device 1200 can implement the steps or processes corresponding to those performed by the first A-IoT device in the above method embodiments. The transceiver module 1210 can be used to perform transceiver-related operations of the first A-IoT device in the above method embodiments, and the processing module 1220 can be used to perform processing-related operations of the first A-IoT device in the above method embodiments.
[0476] In one possible implementation, the transceiver module 1210 is configured to receive a second message from the first reader / writer, the second message instructing the first A-IoT device to perform a write operation on second data, the second data being a portion of the first data. The transceiver module 1210 is also configured to send an eleventh message to the first reader / writer, the eleventh message indicating that the first A-IoT device's write operation on the second data failed. Alternatively, the transceiver module 1210 is also configured to receive a fourteenth message from the first reader / writer, the fourteenth message instructing the first A-IoT device to access the network.
[0477] When the device 1200 is used to execute the method in FIG9, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S903, S904, S905 or S909. The processing module 1220 can be used to execute the processing steps in the method.
[0478] When the device 1200 is used to execute the method in FIG10, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S1003, S1004, S1005, S1009a or S1009b. The processing module 1220 can be used to execute the processing steps in the method.
[0479] When the device 1200 is used to execute the method in FIG11, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S1102, S1103, S1106 or S1107. The processing module 1220 can be used to execute the processing steps in the method.
[0480] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.
[0481] In another design, the device 1200 may correspond to the first A-IoT device in the above method embodiments, or to a component (such as a chip) of the first A-IoT device.
[0482] The device 1200 can implement the steps or processes corresponding to the first core network element in the above method embodiment. The transceiver module 1210 can be used to perform the transceiver-related operations of the first core network element in the above method embodiment, and the processing module 1220 can be used to perform the processing-related operations of the first core network element in the above method embodiment.
[0483] In one possible implementation, transceiver module 1210 is configured to send a first message to a first reader or a first access network device. The first message includes a first command, which instructs the first A-IoT device to perform a write operation on first data. Transceiver module 1210 is also configured to receive a sixth message from the first reader or the first access network device. The sixth message includes first information and second information. The first information includes second data, which is a part of the first data. The second information indicates that the first A-IoT device failed to perform a write operation on the second data. Transceiver module 1210 is also configured to send a seventh message to the first reader or the first access network device. The seventh message includes a first command and third information. The third information indicates one or more of the following: the start position of the write operation on the first data, the length of the write operation on the first data, and the end position of the write operation on the first data. Alternatively, transceiver module 1210 is also configured to send a tenth message to the first reader or the first access network device. The tenth message includes a second command, which instructs the first A-IoT device to perform a write operation on the second data.
[0484] When the device 1200 is used to execute the method in FIG9, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S902, S907 or S908. The processing module 1220 can be used to execute the processing steps in the method.
[0485] When the device 1200 is used to execute the method in FIG10, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S1002, S1007, S1008a or S1008b. The processing module 1220 can be used to execute the processing steps in the method.
[0486] When the device 1200 is used to execute the method in FIG11, the transceiver module 1210 can be used to execute the steps of sending and receiving information in the method, such as S1101, S1104, S1105 or S1108. The processing module 1220 can be used to execute the processing steps in the method.
[0487] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.
[0488] It should also be understood that the device 1200 here is embodied in the form of a functional module. The term "module" here may refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memories for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components that support the described functions.
[0489] The apparatus 1200 of each of the above-described solutions has the function of implementing the corresponding steps performed by the device (such as the first reader / writer, the first A-IoT device, or the first core network element) in the above-described methods. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver module can be replaced by a transceiver (e.g., the transmitting unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as processing modules, can be replaced by a processor, each executing the transceiver operations and related processing operations in the respective method embodiments.
[0490] In addition, the transceiver module 1210 can also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing module 1220 can be a processing circuit.
[0491] Figure 13 is a schematic diagram of another communication device 1300 provided in an embodiment of this application. The device 1300 includes a processor 1310, which executes computer programs or instructions stored in a memory 1330, or reads data / signaling stored in the memory 1330, to perform the methods in the above-described method embodiments. Optionally, there may be one or more processors 1310.
[0492] Optionally, as shown in FIG13, the device 1300 further includes a memory 1330 for storing computer programs or instructions and / or data. The memory 1330 may be integrated with the processor 1310 or may be disposed separately. Optionally, there may be one or more memories 1330.
[0493] Optionally, as shown in FIG13, the device 1300 further includes a transceiver 1320 for receiving and / or transmitting signals. For example, the processor 1310 is used to control the transceiver 1320 to receive and / or transmit signals.
[0494] As one option, the device 1300 is used to implement the operations performed by the first reader / writer in the various method embodiments described above.
[0495] As an alternative, the device 1300 is used to implement the operations performed by the first A-IoT device in the various method embodiments described above.
[0496] As an alternative, the device 1300 is used to implement the operations performed by the first core network element in the various method embodiments described above.
[0497] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.
[0498] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0499] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.
[0500] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0501] Figure 14 is a schematic diagram of a chip system 1400 provided in an embodiment of this application. The chip system 1400 (or may also be referred to as a processing system) includes logic circuitry 1410 and an input / output interface 1420.
[0502] The logic circuit 1410 can be a processing circuit in the chip system 1400. The logic circuit 1410 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 1400 to implement the methods and functions of the embodiments of this application. The input / output interface 1420 can be an input / output circuit in the chip system 1400, outputting processed information from the chip system 1400, or inputting data or signaling information to be processed into the chip system 1400 for processing.
[0503] As one approach, the chip system 1400 is used to implement the operations performed by the first reader, the first A-IoT device, or the first core network element in the various method embodiments described above.
[0504] For example, logic circuit 1410 is used to implement processing-related operations performed by the first reader, the first A-IoT device, or the first core network element in the above method embodiments; input / output interface 1420 is used to implement sending and / or receiving-related operations performed by the first reader, the first A-IoT device, or the first core network element in the above method embodiments.
[0505] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a first reader, a first A-IoT device, or a first core network element in the above-described method embodiments.
[0506] For example, when the computer program is executed by a computer, it enables the computer to implement the methods executed by the first reader, the first A-IoT device, or the first core network element in the various embodiments of the above methods.
[0507] This application also provides a computer program product containing instructions that, when executed by a computer, implement the methods executed by the first reader, the first A-IoT device, or the first core network element in the above-described method embodiments.
[0508] This application also provides a communication system, including the aforementioned first reader / writer, first A-IoT device, or first core network element.
[0509] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.
[0510] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.
[0511] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented 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 this application.
[0512] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.
[0513] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.
[0514] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0515] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0516] If the aforementioned functions are implemented as 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 solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0517] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A communication method applied to a first reader / writer or a chip in the first reader / writer, characterized in that, The method includes: Receive a first message from a first core network element or a first access network device, the first message including a first command, the first command instructing a first environment Internet of Things (A-IoT) device to perform a write operation on first data; A second message is sent to the first A-IoT device, the second message instructing the first A-IoT device to perform a write operation on second data, the second data being a part of the first data; It was determined that the first A-IoT device failed to perform a write operation on the second data; A third message is sent to the first A-IoT device, the third message instructing the first A-IoT device to perform a write operation on the second data.
2. The method according to claim 1, characterized in that, Send a third message to the first A-IoT device, including: If the first condition is met, the third message is sent to the first A-IoT device; The first condition includes one or more of the following: the number of times the first A-IoT device fails to perform write operations on part or all of the first data does not exceed a first threshold, or the number of times the first A-IoT device fails to perform write operations on the second data does not exceed a second threshold.
3. The method according to claim 1 or 2, characterized in that, The third message also includes a retransmission instruction.
4. The method according to any one of claims 1 to 3, characterized in that, Before sending the third message to the first A-IoT device, the method further includes: A fourth message is sent to the first core network element or the first access network device, the fourth message indicating that the first A-IoT device failed to execute the first command; Receive a fifth message from the first core network element or the first access network device, the fifth message including the first command.
5. The method according to any one of claims 1 to 3, characterized in that, Before sending the third message to the first A-IoT device, the method further includes: A sixth message is sent to the first core network element or the first access network device. The sixth message includes first information and second information. The first information includes the second data. The second information indicates that the first A-IoT device failed to perform a write operation on the second data. Receive a seventh message from the first core network element or the first access network device. The seventh message includes the first command and third information. The third information indicates one or more of the following: the start position of the write operation performed on the first data, the length of the write operation performed on the first data, and the end position of the write operation performed on the first data. The third message also includes the third information.
6. The method according to claim 5, characterized in that, Before sending the second message to the first A-IoT device, the method further includes: Send an eighth message to the first A-IoT device, the eighth message instructing the first A-IoT device to perform a write operation on third data, the third data being a part of the first data and different from the second data; Receive a ninth message from the first A-IoT device, the ninth message indicating that the write operation on the third data was successfully performed; The sixth message also includes a fourth message, which includes the third data.
7. The method according to claim 6, characterized in that, The sixth message also includes a fifth message, which indicates that the first A-IoT device successfully performed a write operation on the third data.
8. The method according to any one of claims 1 to 3, characterized in that, Send a third message to the first A-IoT device, including: A sixth message is sent to the first core network element or the first access network device. The sixth message includes first information and second information. The first information includes the second data. The second information indicates that the first A-IoT device failed to perform a write operation on the second data. Receive the tenth message from the first core network element or the first access network device; In response to receiving the tenth message, the third message is sent to the first A-IoT device.
9. The method according to any one of claims 1 to 8, characterized in that, The determination that the first A-IoT device failed to perform a write operation on the second data includes: Receive an eleventh message from the first A-IoT device, the eleventh message indicating that the first A-IoT device failed to perform a write operation on the second data; or... If no message is received from the first A-IoT device within a first time period after sending the second message, it is determined that the first A-IoT device failed to perform a write operation on the second data.
10. The method according to claim 9, characterized in that, The duration of the first time period is a predefined or preconfigured duration, or the method further includes: Receive the twelfth message from the first core network element or the first access network device; The twelfth message indicates the duration of the first time period; or, The twelfth message includes one or more of the following: the length of the first data, the duration of the write operation on the first data, and the capability or type of the first A-IoT device. The twelfth message is used to determine the duration of the first time period.
11. The method according to any one of claims 1 to 10, characterized in that, The method further includes: Receive a thirteenth message and / or a twelfth message, wherein the thirteenth message indicates the caching capacity or caching size of the first A-IoT device, and the twelfth message includes one or more of the following: the length of the first data, the duration of the write operation on the first data, and the capability or type of the first A-IoT device; Sending the second message to the first A-IoT device includes: The second message is sent to the first A-IoT device according to the thirteenth message and / or the twelfth message.
12. A communication method applied to a first-environment Internet of Things (A-IoT) device or a chip in the first A-IoT device, characterized in that, The method includes: Receive a second message from the first reader / writer, the second message instructing the first A-IoT device to perform a write operation on second data, the second data being a part of the first data; Send an eleventh message to the first reader / writer, the eleventh message indicating that the first A-IoT device failed to perform a write operation on the second data; or... The fourteenth message is received from the first reader / writer, the fourteenth message indicating that the first A-IoT device accesses the network.
13. The method according to claim 12, characterized in that, The method further includes: A third message is received from the first reader / writer, the third message instructing the first A-IoT device to perform a write operation on the second data.
14. The method according to claim 12 or 13, characterized in that, The method further includes: A thirteenth message is sent to the first reader / writer, the thirteenth message indicating the caching capacity or caching size of the first A-IoT device.
15. The method according to claim 14, characterized in that, The length of the second data is related to the caching capacity or cache size of the first A-IoT device.
16. A communication method applied to a first core network element, characterized in that, The method includes: Send a first message to a first reader or a first access network device, the first message including a first command, the first command instructing a first environment Internet of Things (A-IoT) device to perform a write operation on the first data; Receive a sixth message from the first reader or the first access network device. The sixth message includes first information and second information. The first information includes second data, which is a part of the first data. The second information indicates that the first A-IoT device failed to perform a write operation on the second data. A seventh message is sent to the first reader or the first access network device. The seventh message includes the first command and third information, wherein the third information indicates one or more of the following: the start position of the write operation on the first data, the length of the write operation on the first data, and the end position of the write operation on the first data; or, A tenth message is sent to the first reader or the first access network device. The tenth message includes a second command, which instructs the first A-IoT device to perform a write operation on the second data.
17. The method according to claim 16, characterized in that, The sixth message also includes fourth information, which includes third data that is a part of the first data and is different from the second data.
18. The method according to claim 17, characterized in that, The sixth message also includes a fifth message, which indicates that the first A-IoT device successfully performed a write operation on the third data.
19. The method according to any one of claims 16 to 18, characterized in that, The method further includes: Send the twelfth message to the first reader or the first access network device; The twelfth message indicates the duration of a first time period, the duration of which is used to determine whether the first A-IoT device failed to perform a write operation on part or all of the first data; or, The twelfth message includes one or more of the following: the length of the first data, the duration of the write operation on the first data, and the capability or type of the first A-IoT device.
20. The method according to any one of claims 16 to 19, characterized in that, The method further includes: Receive a fifteenth message from the first A-IoT device, the fifteenth message indicating the cache capability or cache size of the first A-IoT device; Send a thirteenth message to the first reader or the first access network device, the thirteenth message indicating the caching capacity or caching size of the first A-IoT device.
21. A communication method applied to a first reader or a chip in the first reader, characterized in that, The method includes: Receive the sixteenth message, which indicates the length of the data contained in the first write command.
22. The method according to claim 21, characterized in that, The method further includes: The duration of executing the first write command is determined based on the sixteenth message.
23. The method according to claim 22, characterized in that, The duration for executing the first write command is determined based on the sixteenth message, including: The duration of executing the first write command is determined based on the sixteenth message and one or more of the following: the capabilities of the first environmental IoT A-IoT device, the type of the first A-IoT device, or distance information related to the distance between the first reader / writer and the first A-IoT device, the first A-IoT device being used to execute the first write command.
24. The method according to any one of claims 21 to 23, characterized in that, The method further includes: The information of the first resource is determined according to the sixteenth message. The first resource is used for the first reader / writer to communicate with the first A-IoT device, and the first A-IoT device is used to execute the first write command.
25. The method according to any one of claims 21 to 24, characterized in that, The method further includes: A first duration is determined according to the sixteenth message. The first duration is used to determine whether the first A-IoT device failed to execute the first write command. The first A-IoT device is used to execute the first write command.
26. A communication method applied to a first reader or a chip in the first reader, characterized in that, The method includes: Receive the seventeenth message, which indicates the duration of executing the first command.
27. The method according to claim 26, characterized in that, The method further includes: The information of the second resource is determined according to the seventeenth message. The second resource is used for the first reader to communicate with the first environmental Internet of Things (A-IoT) device. The first A-IoT device is used to execute the first command.
28. The method according to claim 26 or 27, characterized in that, The method further includes: A second duration is determined based on the seventeenth message. The second duration is used to determine whether the first A-IoT device failed to execute the first command. The first A-IoT device is used to execute the first command.
29. A communication device, characterized in that, It includes modules for implementing the method as described in any one of claims 1 to 11, or modules for implementing the method as described in any one of claims 21 to 25, or modules for implementing the method as described in any one of claims 26 to 28.
30. The communication device according to claim 29, characterized in that, The communication device includes a reader or a chip.
31. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 12 to 15.
32. The communication device according to claim 31, characterized in that, The communication device includes an environmental Internet of Things (A-IoT) device or a chip.
33. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 16 to 20.
34. The communication device according to claim 33, characterized in that, The communication device includes core network elements or chips.
35. A computer-readable storage medium, characterized in that, The computer-readable storage medium is included in the communication device, and the computer-readable storage medium stores computer instructions that, when executed, cause the method as described in any one of claims 1 to 28 to be implemented.
36. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are run, the method as described in any one of claims 1 to 28 is implemented.