Communication method and apparatus

Abstract

Disclosed in the embodiments of the present application are a communication method and apparatus. The method comprises: receiving first information from a second device, wherein the first information does not comprise first control information, the first information is used for scheduling the transmission of first data, and the first control information is used for scheduling the length of the first data; and on the basis of the first information, sending the first data to the second device, wherein the first data comprises unsegmented data, a device identifier of a first device, or acknowledgment information of the first information. For example, in an A-IoT scenario, when scheduling first data by means of first information, a second device does not carry first control information in the first information, which reduces the number of bits occupied by the first control information. When the first information does not comprise the first control information, the first device can send unsegmented data, a device identifier of a first device, or acknowledgment information of the first information, so as to ensure that the second device can correctly parse the first data. Therefore, signaling overheads are reduced, and the communication efficiency is improved.

Description

A communication method and apparatus

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

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

[0003] With the development of communication technology, the 3rd Generation Partnership Project (3GPP) defined the Ambient Internet of Things (A-IoT) technology. A-IoT in A-IoT technology includes readers and A-IoT devices; or, in other words, A-IoT-based communication systems include readers and A-IoT devices. 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). Readers and A-IoT devices can communicate non-contactly, allowing the reader to read information from the A-IoT device and / or write information to it. A-IoT technology is used to implement one or more of the following services: inventory, location, sensing, and command. In terms of application scope, A-IoT technology can be applied to scenarios such as logistics, warehousing, industrial manufacturing, identity recognition, or environmental monitoring.

[0004] In A-IoT scenarios, downlink messages sent by readers can schedule the transmission of corresponding uplink messages, taking into account parameters such as transport block size (TBS), modulation and coding scheme (MCS), and frequency domain resources. However, this process incurs significant overhead, impacting communication efficiency. Summary of the Invention

[0005] This application provides a communication method and apparatus that can reduce signaling overhead and improve communication efficiency.

[0006] In a first aspect, embodiments of this application provide a communication method that can be applied to a terminal side, such as an A-IoT device or a communication module within an A-IoT device, or a circuit or chip responsible for communication functions within an A-IoT device (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip). Taking the application of this method to a first device as an example, the method includes:

[0007] Receive first information from the second device, the first information does not include first control information, the first information is used to schedule the transmission of first data, and the first control information is used to schedule the length of the first data; based on the first information, send the first data to the second device, the first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information.

[0008] In A-IoT scenarios, when the second device schedules the first data using the first information, it does not include the first control information in the first information, thus reducing the number of bits occupied by the first control information. Even when the first control information is not included in the first information, the first device can send unsegmented data, its device identifier, or acknowledgment information from the first information, ensuring that the second device can correctly parse the first data. This reduces signaling overhead and improves communication efficiency.

[0009] In one possible design, the business between the first device and the second device includes at least one of the following: inventory, positioning, sensing, or command.

[0010] In one possible design, the first information includes type information, which indicates the type of the first information. The type of the first information is used to determine whether the first information includes first control information. By indicating whether the first information includes first control information through the type information, the first device can determine whether the first information includes first control information based on the type information.

[0011] In one possible design, the first information includes first indication information, which indicates whether the first information includes first control information. By indicating whether the first information includes first control information through the first indication information, the first device can determine whether the first information includes first control information based on the first indication information.

[0012] In one possible design, whether the first information includes first control information is determined based on non-access stratum information or upper-layer information. The first device determines whether the first information includes first control information based on the first device's non-access stratum information or upper-layer information, and sends first data based on whether the first information includes first control information.

[0013] In one possible design, when the second device has determined the length of the first data, the first information does not include the first control information. For example, if the second device obtains the length of the first data from the CN, or if the upper-layer information of the second device indicates a non-access stratum (NAS) packet, no feedback, or feedback of a fixed length, then the first information sent by the second device does not include the first control information, thereby reducing the number of bits occupied by the first control information, reducing signaling overhead, and improving communication efficiency.

[0014] In one possible design, a second message is received from a second device, which is used to page or select a first device; wherein, when the second message indicates the length of the first data, the first message does not include the first control information. Before sending the first message, the second device uniformly indicates the length of the device identifier through the second message, so that when scheduling the first data through the first message, it is not necessary to display the indication of the device identifier's length in each piece of first information.

[0015] In one possible design, the first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

[0016] In one possible design, third information is received from a second device. This third information includes second control information, which is used to schedule the transmission of second data and to schedule the length of the second data. Based on the third information, second data is sent to the second device in response to the third information. Flexible scheduling is achieved by combining scheduling methods that include and do not include control information.

[0017] In one possible design, the second control information includes M bits, which indicate the type of the second data. Each type corresponds to a length, and M is an integer greater than or equal to 1. When the second device schedules the second data using the third information, it uses the second control information included in the third information to indicate the type of the scheduled second data. This allows the second device to send segmented data or data with varying lengths based on the second control information, ensuring that the second device can correctly parse the second data. This achieves flexible scheduling and improves communication efficiency.

[0018] In one possible design, the third information includes at least one of the following: paging message, message 2 (Msg2), and random access trigger message.

[0019] In one possible design, the second control information includes N bits, where N is an integer greater than or equal to 1, used to indicate the length range of the second data. When the second device schedules the second data via the third information, it uses the second control information included in the third information to indicate the length range of the scheduled second data, enabling the second device to send data based on the second control information and ensuring that the second device can correctly parse the second data. This achieves flexible scheduling and improves communication efficiency.

[0020] In one possible design, the third piece of information is downlink data.

[0021] In one possible design, M is less than N. That is, the number of bits used to indicate the type of the second data through the second control information is less than the number of bits used to indicate the length range of the second data through the second control information. Indicating the type of the scheduled second data through the second control information can reduce the number of bits occupied and reduce signaling overhead.

[0022] Secondly, embodiments of this application provide a communication method that can be applied to the network side, such as a network device or a communication module within a network device, or a circuit or chip within a network device responsible for communication functions. Taking the application of this method to a second device as an example, the method includes:

[0023] Send first information to the first device. The first information does not include first control information. The first information is used to schedule the transmission of first data. The first control information is used to schedule the length of the first data. Based on the first information, receive first data from the first device. The first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information.

[0024] In A-IoT scenarios, when the second device schedules the first data using the first information, it does not include the first control information in the first information, thus reducing the number of bits occupied by the first control information. Even when the first control information is not included in the first information, the first device can send unsegmented data, its device identifier, or acknowledgment information from the first information, ensuring that the second device can correctly parse the first data. This reduces signaling overhead and improves communication efficiency.

[0025] In one possible design, the business between the first device and the second device includes at least one of the following: inventory, positioning, sensing, or command.

[0026] In one possible design, the first information includes type information, which indicates the type of the first information. The type of the first information is used to determine whether the first information includes first control information. By indicating whether the first information includes first control information through the type information, the first device can determine whether the first information includes first control information based on the type information.

[0027] In one possible design, the first information includes first indication information, which indicates whether the first information includes first control information. By indicating whether the first information includes first control information through the first indication information, the first device can determine whether the first information includes first control information based on the first indication information.

[0028] In one possible design, whether the first information includes the first control information is determined based on non-access stratum information or upper-layer information. That is, the second device can determine whether the first information includes the first control information based on the second device's non-access stratum information or upper-layer information. If the upper-layer information of the second device indicates an empty NAS packet, no feedback, or feedback of a fixed length, then the first information does not include the first control information, thereby reducing the number of bits occupied by the first control information and reducing signaling overhead.

[0029] In one possible design, when the second device has determined the length of the first data, the first information does not include the first control information. For example, if the second device obtains the length of the first data from the CN, or if the upper-layer information of the second device indicates an empty NAS packet, no feedback, or feedback of a fixed length, then the first information sent by the second device does not include the first control information, thereby reducing the number of bits occupied by the first control information, reducing signaling overhead, and improving communication efficiency.

[0030] In one possible design, a second message is sent to the first device, which is used to indicate paging or selection of the first device; wherein, when the second message indicates the length of the first data, the first message does not include the first control information. Before sending the first message, the second device uniformly indicates the length of the device identifier through the second message, so that when scheduling the first data through the first message, it is not necessary to display the indication of the length of the device identifier in each first message.

[0031] In one possible design, the first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

[0032] In one possible design, a third message is sent to the first device. The third message includes second control information, which is used to schedule the transmission of second data and to schedule the length of the second data. Based on the third message, second data is received from the first device, which is used to respond to the third message.

[0033] In one possible design, the second control information includes M bits, which indicate the type of the second data. Each type corresponds to a specific length, and M is an integer greater than or equal to 1. When the second device schedules the second data using the third information, it uses the second control information included in the third information to indicate the type of the scheduled second data. This allows the second device to send data based on the second control information, ensuring that the second device can correctly parse the second data. This achieves flexible scheduling and improves communication efficiency.

[0034] In one possible design, the third information includes at least one of the following: paging message, message 2 (Msg2), and random access trigger message.

[0035] In one possible design, the second control information includes N bits, where N is an integer greater than or equal to 1, used to indicate the length range of the second data. When the second device schedules the second data via the third information, it uses the second control information included in the third information to indicate the length range of the scheduled second data. This allows the second device to send segmented data or data with varying lengths based on the second control information, ensuring that the second device can correctly parse the second data. This achieves flexible scheduling and improves communication efficiency.

[0036] In one possible design, the third piece of information is downlink data.

[0037] In one possible design, M is less than N. That is, the number of bits used to indicate the type of the second data through the second control information is less than the number of bits used to indicate the length range of the second data through the second control information. Indicating the type of the scheduled second data through the second control information can reduce the number of bits occupied and reduce signaling overhead.

[0038] Thirdly, embodiments of this application provide a communication method that can be applied to a terminal side, such as an A-IoT device or a communication module within an A-IoT device, or a circuit or chip within an A-IoT device responsible for communication functions. Taking the application of this method to a first device as an example, the method includes:

[0039] Receive first information from the second device, the first information including first indication information, the first indication information being used to indicate that the first information is a first information type, the first information type corresponding to a first service, the first service being an unfinished service between the first device and the second device; based on the first indication information, send a first response to the second device.

[0040] In multi-reader scenarios, the first indication information indicates the information type of the downlink information, enabling the first device to distinguish downlink information from different readers, avoiding the downlink information from carrying reader ID or transaction ID, thereby reducing signaling overhead and improving communication efficiency.

[0041] In one possible design, the first indication information includes a first numerical value.

[0042] In one possible design, second information is received from a third device. The second information includes second indication information, which indicates that the second information is of the second information type, which corresponds to a second service that is different from the first service. Based on the second indication information, no second response is sent to the third device.

[0043] In one possible design, the second indication information includes a second numerical value.

[0044] In one possible design, prior to receiving the first information from the second device, the method further includes:

[0045] Receive third information from the second device, the third information being used to indicate that a downlink information of the first information type is currently required to be responded to.

[0046] In one possible design, the third information includes first identification information, which corresponds to the first service.

[0047] In one possible design, a fourth message is sent to the second device when the first service is not completed; the first message is monitored while the service is in progress.

[0048] Fourthly, embodiments of this application provide a communication method that can be applied to the network side, such as a network device or a communication module within a network device, or a circuit or chip within a network device responsible for communication functions. Taking the application of this method to a second device as an example, the method includes:

[0049] Send first information to a first device, the first information including first indication information, the first indication information being used to indicate a first information type, the first information type corresponding to a first service, the first service being an unfinished service between the first device and the second device; based on the first indication information, receive a first response sent from the first device.

[0050] In a multi-reader scenario, the first indication information indicates the type of downlink information, enabling the first device to distinguish downlink information from different readers, avoiding the downlink information from carrying reader ID or transaction ID, thereby reducing signaling overhead and improving communication efficiency.

[0051] In one possible design, the first indication information includes a first numerical value.

[0052] In one possible design, before sending the first information to the first device, the method further includes sending a third information to the first device, the third information being used to indicate that downlink information of the type of the first information is currently required to respond.

[0053] In one possible design, the third information includes first identification information, which corresponds to the first service.

[0054] In one possible design, a third indication information is received from a core network device, the third indication information being used to indicate the transmission of downlink information of the first information type; based on the third indication information, the first information is transmitted to the first device.

[0055] Fifthly, embodiments of this application provide a communication device that performs the functions described in the first aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented in software, hardware, or a combination of both. The communication device may be, for example, a first device or a communication module within a first device, or a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip containing a modem core, or a system-in-package (SIP) chip) responsible for communication functions within the first device. The device includes:

[0056] A receiving module is configured to receive first information from a second device, the first information not including first control information, the first information being used to schedule the transmission of first data, and the first control information being used to schedule the length of the first data.

[0057] The sending module is used to send the first data to the second device based on the first information. The first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information. The service between the first device and the second device includes at least one of the following: inventory, positioning, sensing, or command.

[0058] In one possible design, the first information includes type information, which indicates the type of the first information, and the type of the first information is used to determine whether the first information includes the first control information.

[0059] In one possible design, the first information includes first indication information, which is used to indicate whether the first information includes the first control information.

[0060] In one possible design, whether the first information includes the first control information is determined based on non-access layer information or upper layer information.

[0061] In one possible design, when the second device has determined the length of the first data, the first information does not include the first control information.

[0062] In one possible design, a receiving module is configured to receive second information from the second device, the second information being used to page or select the first device;

[0063] Wherein, when the second information indicates the length of the first data, the first information does not include the first control information.

[0064] In one possible design, the first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

[0065] In one possible design, the receiving module is further configured to receive third information from the second device, the third information including second control information, the third information being used to schedule the transmission of second data, and the second control information being used to schedule the length of the second data;

[0066] The sending module is further configured to send the second data to the second device based on the third information, wherein the second data is used to respond to the third information.

[0067] In one possible design, the second control information includes M bits, which are used to indicate the type of the second data, with each type corresponding to a length, and M being an integer greater than or equal to 1.

[0068] In one possible design, the third information includes at least one of the following: a paging message, message 2 (Msg2), or a random access trigger message.

[0069] In one possible design, the second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1.

[0070] In one possible design, the third information is downlink data.

[0071] In one possible design, M is less than N.

[0072] The operation and beneficial effects of this communication device can be found in the method and beneficial effects described in the first aspect above, and will not be repeated here.

[0073] Sixthly, embodiments of this application provide a communication device that performs the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect. These modules, units, or means can be implemented in software, hardware, or a combination of both. The communication device may be, for example, a second device or a communication module within a second device, or a circuit or chip within a second device responsible for communication functions. The device includes:

[0074] A sending module is used to send first information to a first device. The first information does not include first control information. The first information is used to schedule the transmission of first data. The first control information is used to schedule the length of the first data.

[0075] The receiving module is configured to receive the first data from the first device based on the first information. The first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information. The service between the first device and the second device includes at least one of the following: inventory, positioning, sensing, or command.

[0076] In one possible design, the first information includes type information, which indicates the type of the first information, and the type of the first information is used to determine whether the first information includes the first control information.

[0077] In one possible design, the first information includes first indication information, which is used to indicate whether the first information includes the first control information.

[0078] In one possible design, whether the first information includes the first control information is determined based on non-access layer information or upper layer information.

[0079] In one possible design, when the second device has determined the length of the first data, the first information does not include the first control information.

[0080] In one possible design, the sending module is further configured to send second information to the first device, the second information being used to indicate paging or selection of the first device;

[0081] Wherein, when the second information indicates the length of the first data, the first information does not include the first control information.

[0082] In one possible design, the first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

[0083] In one possible design, the sending module is further configured to send third information to the first device, the third information including second control information, the third information being used to schedule the transmission of second data, and the second control information being used to schedule the length of the second data;

[0084] The receiving module is further configured to receive the second data from the first device based on the third information, wherein the second data is used to respond to the third information.

[0085] In one possible design, the second control information includes M bits, which are used to indicate the type of the second data, with each type corresponding to a length, and M being an integer greater than or equal to 1.

[0086] In one possible design, the third information includes at least one of the following: a paging message, message 2 (Msg2), or a random access trigger message.

[0087] In one possible design, the second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1.

[0088] In one possible design, the third information is downlink data.

[0089] In one possible design, M is less than N.

[0090] The operation and beneficial effects of this communication device can be found in the method and beneficial effects described in the second aspect above, and will not be repeated here.

[0091] In a seventh aspect, embodiments of this application provide a communication device, which includes one or more processors. Optionally, it also includes a memory for storing part or all of the computer programs or instructions necessary for implementing the functions involved in the first aspect above. The one or more processors can execute the computer programs or instructions, and when the computer programs or instructions are executed, cause the communication device to implement the methods in any possible design or implementation of the first aspect above.

[0092] In one possible design, the communication device may further include an interface circuit, through which the processor communicates with other devices or components.

[0093] In one possible design, the communication device may also include the memory.

[0094] The aforementioned communication device may be the first device, or the communication module in the first device, or the chip in the first device responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0095] Eighthly, embodiments of this application provide a communication device, which includes one or more processors. Optionally, it also includes a memory for storing part or all of the computer programs or instructions necessary for implementing the functions involved in the second aspect above. The one or more processors are capable of executing the computer programs or instructions, which, when executed, cause the communication device to implement the methods in any possible design or implementation of the second aspect above.

[0096] In one possible design, the communication device may further include an interface circuit, through which the processor communicates with other devices or components.

[0097] In one possible design, the communication device may also include the memory.

[0098] The aforementioned communication device may be a second device, or a communication module in a second device, or a chip in a second device that is responsible for communication functions, such as a modem chip (also known as a baseband chip) or a SoC or SIP chip containing a modem module.

[0099] Ninthly, this application provides a computer-readable storage medium for storing a computer program that, when executed, causes the method described in any one of the first to second aspects to be implemented.

[0100] In a tenth aspect, this application provides a computer program product including a computer program that, when executed, causes the method described in any one of the first to second aspects to be implemented.

[0101] Eleventhly, embodiments of this application provide a communication system, which includes a first device and a second device. The first device is used to perform the steps in the first aspect described above, and the second device is used to perform the steps in the second aspect described above.

[0102] In a twelfth aspect, a chip or chip system is provided, the chip or chip system including at least one processor and a communication interface for communicating with external or internal devices, the processor for implementing the methods of the above aspects.

[0103] In one possible design, the chip may further include a memory storing computer programs or instructions, which the processor executes, either from the stored computer programs or instructions or derived from other programs or instructions. When the computer program or instructions are executed, the processor implements the methods described above.

[0104] In one possible design, the chip can be integrated into either the first device or the second device. Attached Figure Description

[0105] Figures 1A-1E are schematic diagrams of the A-IoT network architecture;

[0106] Figure 2 is a schematic diagram of an open radio access network (O-RAN) architecture;

[0107] Figure 3 is a schematic diagram of the application framework of the RAN intelligent controller module under the O-RAN architecture;

[0108] Figure 4 is a schematic diagram of the overall A-IoT air interface / access stratum (AS) process;

[0109] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0110] Figure 6 is a schematic diagram of the structure of the first information;

[0111] Figure 7 is a schematic diagram of another type of first information structure;

[0112] Figure 8 is a schematic diagram of a communication method;

[0113] Figure 9 is a schematic diagram of another communication method;

[0114] Figure 10 is a schematic diagram of another communication method;

[0115] Figure 11 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0116] Figure 12 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0117] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

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

[0119] Figure 15 is a schematic diagram of the structure of a first device provided in an embodiment of this application;

[0120] Figure 16 is a schematic diagram of the structure of a second device provided in an embodiment of this application. Detailed Implementation

[0121] The following explains the key terms used in this application:

[0122] Ambient IoT: Based on cellular network communication infrastructure, it consists of readers and passive / semi-passive / active A-IoT devices. Its main functions include inventory, positioning, and sensor reporting. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0123] Radio Frequency Identification (RFID): RFID systems typically consist of an interrogator and electronic A-IoT devices (tags). The interrogator can interact with the electronic A-IoT devices to manage them.

[0124] The embodiments of this application can be applied to A-IoT, which includes A-IoT devices and readers. The A-IoT devices can be located within the coverage area provided by the reader. When the reader is a terminal device, the communication between the reader and the A-IoT device can be regarded as the transmission between terminals. When the reader is a network device, the communication between the reader and the A-IoT device is through the UU interface, i.e., air interface communication.

[0125] A-IoT devices, also known as RFID A-IoT devices, are a common name for RFID. Radio frequency identification technology can be divided into three types: active, passive, and semi-active. Passive A-IoT devices can also be called passive IoT devices. Therefore, A-IoT devices can also be considered a type of terminal.

[0126] A reader / writer is a handheld or fixed device that reads (and sometimes writes) information from A-IoT devices. It can also be understood as a device that communicates with A-IoT devices. This can be a terminal device, a network device, or a node that transmits signals, such as a headend, packet radio unit, or transmit / receive point (TRP), or simply a device with read / write capabilities. It can also be an integrated access and backhaul (IAB) node, a smart repeater, or a relay node.

[0127] The embodiments of this application can also be applied to various communication systems, such as Universal Mobile Telecommunications System (UMTS), Wireless Local Area Network (WLAN), Wireless Fidelity (Wi-Fi) system, 4th generation (4G) mobile communication system, such as Long Term Evolution (LTE) system, 5th generation (5G) mobile communication system, such as New Radio (NR) system, and next-generation communication systems, such as 6th generation (6G) mobile communication system, etc.

[0128] As shown in Figures 1A-1E, these figures illustrate the A-IoT network architecture. In Topology 1, A-IoT devices communicate directly and bidirectionally with network devices (e.g., base stations). Communication between the network devices and A-IoT devices includes environmental IoT data and / or signaling. This topology includes a base station (BS) sending data to and receiving data from the A-IoT devices; that is, there is uplink and downlink data / signaling between the BS and the A-IoT devices. In Topology 2, A-IoT devices communicate bidirectionally with intermediate nodes, which are located between the A-IoT devices and the base stations. In this topology, the intermediate node can be a repeater, an integrated access backhaul (IAB) node, user equipment (UE), etc., enabling environmental IoT. The intermediate node transmits A-IoT data and / or signaling between the BS and the A-IoT devices. In Topology 3, the A-IoT device sends data / signaling to the network device and receives data / signaling from the auxiliary node; or the A-IoT device receives data / signaling from the network device and sends data / signaling to the auxiliary node. In this topology, the auxiliary node can be a repeater, IAB, UE, etc., which enable the Internet of Things (IoT). In Topology 4, the A-IoT device communicates bidirectionally with the terminal device. The communication between the terminal device and the A-IoT device includes environmental IoT data and / or signaling.

[0129] Furthermore, the embodiments of this application can also be applied to open radio access network (O-RAN) architectures. Figure 2 shows a schematic diagram of an O-RAN architecture. An O-RAN system may include components other than those shown in Figure 2. Network devices are also called access network devices. Access network devices (RAN, for example, can be eNB, gNB, or next-generation access network devices) communicate with core network (CN) devices via backhaul links and with user equipment (UE) via air interfaces.

[0130] Terminal equipment, also known as user equipment, mobile station (MS), mobile terminal (MT), etc., refers to devices that provide voice and / or data connectivity to users. Examples include handheld devices with wireless connectivity and in-vehicle devices. Currently, some examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving cars, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes.

[0131] Access network equipment refers to radio access network (RAN) nodes (or devices) that connect terminals to a wireless network; it can also be called a base station. Examples of RAN nodes include: evolved Node B (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved Node B, or home Node B, HNB), base band unit (BBU), and wireless fidelity (Wi-Fi) access point (AP). Furthermore, in a network architecture, access network equipment may include centralized unit (CU) nodes, distributed unit (DU) nodes, or RAN equipment comprising both CU and DU nodes. This includes RAN equipment at CU and DU nodes that separate the protocol layer of the eNB in ​​a long term evolution (LTE) system. Some protocol layer functions are centrally controlled by the CU, while the remaining partial or complete protocol layer functions are distributed in the DU, which is centrally controlled by the CU. Access network equipment can also be reader / writer devices.

[0132] Core network equipment: A collective term for various functional entities on the network side used to manage users, data transmission, and base station configuration, including access and mobility management function (AMF) entities, user plane function (UPF) entities, session management function (SMF) entities, tag management function (TMF) entities, etc.

[0133] Specifically, the baseband unit (BBU) in the access network equipment communicates with the core network equipment via a backhaul link, while the radio unit (RU) in the access network equipment communicates with at least one 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 control unit (CU) and at least one distributed unit (DU), which can communicate via at least one midhaul link.

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

[0135] In some examples, the CU can be split into a control unit-control plane (CU-CP) and a control unit-user plane (CU-UP). The CU-CP is a logical node carrying the RRC layer and the control plane part of the Packet Data Convergence Protocol (PDCP-C) layer, used to implement the CU's control plane functions. The CU-CP can interact with network elements in the core network used to implement control plane functions. These network elements in the core network can be access and mobility function (AMF) network elements, such as the access and mobility management function (AMF) in a 5G system. The AMF network element is responsible for mobility management in the mobile network, such as terminal device location updates, terminal device registration with the network, and terminal device handover. The CU-UP is a logical node carrying the SDAP layer and the user plane part of the Packet Data Convergence Protocol (PDCP-U) layer, used to implement the CU's user plane functions. The CU-UP can interact with network elements in the core network used to implement user plane functions. In the core network, network elements used to implement user plane functions, such as the user plane function (UPF) in a 5G system, are responsible for forwarding and receiving data in terminal devices. The above configuration of CU and DU is merely an example; 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 to have only some protocol layer processing functions. For instance, some RLC layer functions and protocol layer functions above the RLC layer can be placed in the CU, while the remaining RLC layer functions and protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of CU or DU can be divided according to service type or other system requirements, such as by latency, placing functions that need to meet low latency requirements in the DU and functions that do not need to meet such latency requirements in the CU.

[0136] In some examples, a DU is a logical node that carries the radio link control (RLC) layer, medium access control (MAC) layer, higher physical layer (Higher PHY) layer, and other functions. In some examples, a DU can control at least one RU. 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.

[0137] In some examples, 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 3GPPTRP, a remote radio head (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.

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

[0139] 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.

[0140] 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, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples.

[0141] Figure 3 shows a schematic diagram of the application framework of the RAN intelligent controller (RIC) module under the O-RAN architecture. This communication system includes RICs. The RICs include near-real-time RICs (near-RT RICs) and non-real-time RICs (non-RT RICs).

[0142] The near real-time RIC is used for model training and inference. For example, it can be used to train an artificial intelligence (AI) model and then use that AI model for inference. The near real-time RIC can obtain network-side and / or terminal-side information from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU) and / or terminals. This information can be used as training data or inference data. Optionally, the near real-time RIC can deliver the inference results to the RAN nodes and / or terminals. Optionally, inference results can be exchanged between CU and DU, and / or between DU and RU. For example, the near real-time RIC delivers the inference results to the DU, and the DU sends them to the RU.

[0143] The non-real-time RIC is used for model training and inference. For example, it is used to train an AI model and then use that model for inference. The non-real-time RIC can obtain network-side and / or terminal-side information from RAN nodes (e.g., CU, CU-CP, CU-UP, DU, and / or RU) and / or terminals. This information can be used as training data or inference data, and the inference results can be delivered to RAN nodes and / or terminals. Optionally, inference results can be exchanged between CU and DU, and / or between DU and RU; for example, the non-real-time RIC delivers the inference results to the DU, which then forwards them to the RU.

[0144] 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.

[0145] In a communication system, network elements are connected via interfaces (e.g., NG, Xn) or over-the-air interfaces. These network element nodes, such as core network equipment, access network nodes (RAN nodes), terminals, or one or more devices in the OAM, are equipped with one or more AI modules (only one is shown in the figure for clarity). The access network node can be a single RAN node or can include multiple RAN nodes, for example, including CU and DU. The CU and / or DU can also be equipped with one or more AI modules. Optionally, the CU can be further divided into CU-CP and CU-UP. One or more AI models are configured in the CU-CP and / or CU-UP.

[0146] The AI ​​module is used to implement corresponding AI functions. AI modules deployed in different network elements can be the same or different. Depending on the parameter configuration, the AI ​​module can implement different functions. The AI ​​module model can be configured based on one or more of the following parameters: structural parameters (e.g., at least one of the following: number of neural network layers, neural network width, inter-layer connections, neuron weights, neuron activation function, or bias in the activation function), input parameters (e.g., type and / or dimension of input parameters), or output parameters (e.g., type and / or dimension of output parameters). The bias in the activation function can also be referred to as the neural network bias.

[0147] An AI module can have one or more models. A model can infer an output, which includes one or more parameters. The learning, training, or inference processes of different models can be deployed on different nodes or devices, or they can be deployed on the same node or device.

[0148] For the O-RAN architecture, the following interfaces can be included:

[0149] A1 Interface: The interface between Non-RT RIC and Near-RT RIC, used for intelligent and dynamic control of radio resources within the O-RAN. Non-RT RIC provides policies, rich information, and ML model updates to Near-RT RIC through the A1 interface, while Near-RT RIC provides policy feedback to Non-RT RIC through the A1 interface.

[0150] E2 Interface: The E2 interface is an open interface between two endpoints used to connect the Near-RT RIC and the RAN node. RAN nodes include, for example, CU and DU in 5G, O-RAN compatible eNB in ​​4G, O-CU (O-CU-CP and / or O-CU-UP) in O-RAN, and / or O-DU, etc. The RIC can obtain data collection and feedback from the RAN node through the E2 node, and the RAN node can obtain control feedback from the Near-RT RIC through the E2 node.

[0151] O1 Interface: The interface between the management entity in the service management and orchestration framework (SMO) and the O-RAN module. It is used for operation management and enables FCAPS management, software management, and file management.

[0152] O2 Interface: The interface between the SMO and the infrastructure management framework that supports O-RAN virtual network functionality.

[0153] The Open Fronthaul CUS-Plane interface includes the control plane (C-Plane), user plane (U-Plane), and synchronization plane (S-Plane). The control plane is used for real-time control between the O-DU and O-RU, such as transmitting beamforming weights from the O-DU to the O-RU or performing power control from the O-DU to the O-RU. The user plane is used to transmit communication data between the DU and RU for access network devices and terminals. The synchronization plane is used by the O-DU to provide clock synchronization for the O-RU.

[0154] For the O-RAN architecture, the following 3GPP interfaces may also be included:

[0155] NG interface: The interface between NR RAN equipment (such as base stations, CUs, CU-CPs, or CU-UPs) and the NR core network; among them, NG-u is the user plane NG interface, and NG-c is the control plane NG interface.

[0156] Xn interface: The interface between NR RAN devices (such as base stations, CUs, CU-CPs, or CU-UPs); where Xn-u is the user plane Xn interface and Xn-c is the control plane Xn interface.

[0157] X2 Interface: The interface between LTE RAN devices; X2-u is the user plane X2 interface, and X2-c is the control plane X2 interface. In NR, the X2 interface is mainly used in E-UTRA-NR dual connectivity (EN-DC) scenarios, where the master station is an LTE RAN device that connects to the LTE core network through the X2 interface.

[0158] E1 interface: The interface between CU-CP and CU-UP.

[0159] F1-C interface: The interface between CU-CP and DU.

[0160] F1-U interface: The interface between CU-UP and DU.

[0161] A-IoT is based on cellular network communication infrastructure and consists of readers (such as base stations) and passive, semi-passive, and active A-IoT devices (A-IoT devices are terminals in the cellular network, which can be understood as extremely low-power, extremely low-complexity IoT terminals). Its main functions include inventory management, positioning, sensing, and command processing. Typical application scenarios include logistics, warehousing, industrial manufacturing, identity recognition, and environmental monitoring.

[0162] In A-IoT, terminal devices can be divided into three categories:

[0163] 1. Device A: It may or may not be able to store energy, meaning it does not have independent signal generation / amplification capabilities when performing backscattering transmission. Device A is also known as a passive A-IoT device.

[0164] 2. Device B: This device is capable of energy storage. While it does not generate its own signal during backscattering transmission, the stored energy amplifies the reflected signal. Device B is also known as a semi-passive A-IoT device.

[0165] 3. Device C: Capable of energy storage and has independent signal generation capabilities, meaning it has active radio frequency (RF) for data transmission. Device C is also known as an active A-IoT device.

[0166] (1) Access stratum (AS) process:

[0167] Figure 4 shows a schematic diagram of the overall A-IoT air interface / AS process. It includes the following steps:

[0168] Step A: A-IoT paging.

[0169] Specifically, the reader sends an A-IoT paging message based on the service request. The A-IoT paging message is used to indicate which device needs to respond.

[0170] In this context, the A-IoT paging message can be replaced with the (initial) trigger message. For simplicity, no restrictions are imposed.

[0171] Step B: D2R Data Transmission. The triggered A-IoT device performs device ID transmission via the A-IoT random access procedure or without using the A-IoT random access procedure (e.g., contention-free resolution).

[0172] Step C: Data transmission, which may include:

[0173] Network-to-device (R2D) data transmission (e.g., for sending commands, such as read, write, lock, deactivate, and sensor commands).

[0174] Device-to-network (D2R) data transmission (e.g., responses to commands, such as data read by a read command, success / failure feedback for a write command, etc.).

[0175] The above process can then support inventory and command application scenarios in the following ways:

[0176] For an "inventory-only" scenario, steps A and B can be included.

[0177] The "inventory and command" scenario can include steps A, B, and C.

[0178] For a "command-only" scenario, steps A, B, and C can be included.

[0179] In addition, for "command-only" scenarios, this may also include: A-IoT paging. The reader sends an A-IoT paging message containing a command based on a service request, instructing the A-IoT device to process / respond to the command. The A-IoT device performs D2R data transmission (e.g., device ID or corresponding response to the command) with or without the A-IoT random access procedure.

[0180] (2) A-IoT paging:

[0181] At the access layer, the A-IoT paging function indicates which device needs to respond.

[0182] For A-IoT paging messages, an identifier may be required to identify the device / group of devices included or associated with this triggering message (e.g., a single device, a group of devices, or all devices). This includes the following scenarios:

[0183] The first scenario: A-IoT paging messages can contain a single A-IoT device ID.

[0184] The second scenario: The A-IoT paging message contains a group ID mapped to multiple A-IoT devices.

[0185] The third scenario: The A-IoT paging message does not contain any identifier, that is, it indicates that all A-IoT devices that can receive the A-IoT paging message need to respond.

[0186] The fourth scenario: The A-IoT paging message contains multiple A-IoT device identifiers.

[0187] Optionally, A-IoT paging messages can also be used to indicate resources. A-IoT devices can determine the resources (such as time-domain and / or frequency-domain resources) for D2R response messages based on A-IoT paging messages.

[0188] Optionally, the paging function of A-IoT devices can be understood as not supporting traditional paging messages, traditional paging timing, and traditional discontinuous reception (DRX) from NR. It can be assumed that A-IoT devices can receive A-IoT paging as long as they have sufficient power.

[0189] (3) A-IoT random access:

[0190] The A-IoT random access procedure is used for A-IoT devices to access the network for data transmission.

[0191] A-IoT random access is triggered by the reader, including access triggered by a single A-IoT device, a group of A-IoT devices, or all A-IoT devices under the reader's coverage.

[0192] When an A-IoT device responds to an A-IoT paging message, the A-IoT device executes the following process:

[0193] Step 1: Determine the random access type and access timing / resources.

[0194] Specifically, if the random access is contention-free access, the indicated D2R timing / resource is selected, the contention resolution in step 2 is skipped, and step 3 is executed for data transmission. If it is contention-based random access, the access timing / resource is determined / selected, for example, randomly selected, and step 2, which resolves the contention, is executed.

[0195] Step 2: Contention-based random access contention resolution, including the following two schemes:

[0196] Option 1: A-IoT Msg1 has no data.

[0197] A-IoT Msg1: When an A-IoT device recognizes the start of its access occasion, it sends a random ID generated by the A-IoT device to the reader.

[0198] There is currently no conclusion on how A-IoT devices generate random IDs; for example, they could be randomly generated or generated based on the device ID. The size of the random ID can also be unrestricted, such as a 16-bit random number.

[0199] A-IoT Msg2: The reader's response indicating a successfully received random ID.

[0200] If the A-IoT device receives A-IoT Msg2 containing a random ID, and that random ID is the same as the one previously sent in A-IoT Msg1, then the race condition is considered resolved successfully.

[0201] In this context, A-IoT Msg2 is used for contention resolution because it is assumed that the size of the random ID in A-IoT Msg1 should be sufficient for contention resolution purposes. It is highly unlikely that A-IoT devices choosing the same access timing / resources will send the same random ID value in A-IoT Msg1; therefore, the range of random ID values ​​can be considered sufficiently large.

[0202] Option 2: A-IoT Msg1 has data.

[0203] A-IoT Msg1: When an A-IoT device recognizes the start of its access period, it sends an A-IoT Msg1 containing upper-layer data, which may be the device ID and / or any other upper-layer data. Optionally, the A-IoT Msg1 may or may not include a random ID.

[0204] A-IoT Msg2: The reader can respond with the successfully received random ID and / or device ID (partial or complete) and / or acknowledgment (ACK), or it can choose not to respond. If Msg1 does not receive a signal indicating failure, reconnection, or retransmission, it considers the access successful / data transmission successful / service successful.

[0205] If an A-IoT device receives an A-IoT Msg2 containing a random ID and / or a device ID (partial or complete) and / or an ACK, and this information is a part of the previously sent information in A-IoT Msg1 or information generated based on A-IoT Msg1 (e.g., a hash function on Msg1), then the A-IoT device considers the race to be resolved successfully.

[0206] Step 3: Data transmission.

[0207] Specifically, if contention-based random access or contention-free access is used, the A-IoT device can perform upper-layer data transmission with the reader after the contention is successfully resolved. The upper-layer data can be the device ID and / or any other upper-layer data.

[0208] Step 3 can also be understood as follows: after the A-IoT device sends D2R data, subsequent R2D data does not always need to be sent. The use or existence of subsequent R2D data requires further research; for example, handling retransmission or reconnection after D2R data transmission failure could be considered.

[0209] As shown above, the reader can send R2D messages to A-IoT devices, and the A-IoT devices can send D2R messages to the reader in response to the R2D messages. The R2D messages can include control information used to schedule the transmission of D2R messages, such as parameters like TBS, MCS, and frequency domain resources. However, not all D2R transmissions require control information. For example, the data transmitted by the A-IoT device may include the device ID, or the length of the R2D command response may be known to the reader (which has already obtained it from the CN). If the reader indicates the TBS via control information in Msg2 or R2D, the control information occupies a large number of bits (e.g., 7 bits), resulting in high resource overhead and reduced communication efficiency.

[0210] To address the aforementioned technical problems, the embodiments of this application provide the following solutions.

[0211] As shown in Figure 5, Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application. The first device can be an A-IoT device, and the second device can be a reader. Alternatively, the first device can be a reader, and the second device can be an A-IoT device. The method mainly includes the following steps:

[0212] S501, the first device receives first information from the second device. The first information does not include first control information. The first information is used to schedule the transmission of first data, and the first control information is used to schedule the length of the first data.

[0213] Optionally, the services between the first and second devices include at least one of the following: inventory, positioning, sensing, or commands. Inventory involves the reader connecting to A-IoT devices within its coverage area; successfully connected A-IoT devices need to send their unique identifiers to the reader. Positioning uses location signals to pinpoint the location of the A-IoT devices. Sensing involves the A-IoT devices reporting sensor data, such as temperature data, to the reader. Commands can be operational instructions (e.g., write, lock). Specifically, the write process involves the reader sending a downlink command and data, instructing the A-IoT device to write the data into its memory; the lock process involves the reader sending a downlink command, instructing the A-IoT device to lock the specified address in the memory, making the contents of that memory area unchangeable and / or unreadable.

[0214] The term "first information" excludes "first control information," which can also be understood as: the first information excludes only the first control information but includes other control information. Alternatively, the first information includes other control information besides the first control information. Other control information may include at least one of the following: frequency domain resource, number of repetitions, training sequence, duration, or MCS.

[0215] The first control information can be TBS, meaning the first information does not include TBS. TBS can be understood as the size or length of the payload transmitted in the uplink data (D2R or physical device reader channel, PDRCH) transmission.

[0216] For example, the first information does not include TBS, but includes frequency domain resources, repetition count, duration, or MCS. The second device may not need to schedule the length of the first data sent by the first device, but can schedule the frequency domain resources, repetition count, duration, or MCS of the first data through the first information.

[0217] The first information may be at least one of the following: a paging message, a random access trigger (RA trigger) message, downlink data, or a feedback message. Optionally, the first information may also be Msg2.

[0218] The first piece of information may include R2D data (or upper-layer data, MAC service data unit (SDU)), where R2D data may include commands, such as read commands, write commands, etc.

[0219] Paging messages can be used to instruct A-IoT devices to access the reader, or to page A-IoT devices. For example, when the reader is a base station, the paging message can be used to instruct the A-IoT device to access the base station. When the reader is a terminal device, the paging message can be used to instruct the A-IoT device to access the terminal device. Optionally, A-IoT devices can also access the base station through terminal devices. In one implementation, the paging message filters or selects A-IoT devices using device identifiers (such as unique device identifiers, group identifiers, masks, etc.). Optionally, the paging message can also indicate the number of access resources.

[0220] Optionally, paging messages can also be used to trigger or instruct A-IoT devices to send uplink data, or to trigger, instruct, or request A-IoT devices to perform services, wherein the services may include at least one of the following: paging, inventory, commands (such as read, write, deactivate, lock, etc.), positioning, or sensing.

[0221] A random access trigger message, also known as an access occasion indication or trigger, is used to trigger or indicate the next (or multiple, or the next group of) access opportunities (or a set of access opportunities). Alternatively, it can be used to indicate or associate the boundary (start or end) of an access opportunity. Access occasions can also be referred to as access opportunities, access slots, access time-domain resources, etc. Each access occasion allows the first device to send access requests, resolve contention, and / or transmit data.

[0222] Downlink data can also be referred to as R2D data. Downlink data can originate from the core network, such as from ambient IoT function (A-IoTF) entities or access and mobility management function (AMF) / application function (AF) entities, without limitation to core network element entities. For example, downlink data may include commands, such as at least one of read, write, sensing, locking, deactivation, and location. This is merely an example and does not imply that downlink data can only contain these commands.

[0223] Feedback messages are used to provide feedback on uplink data or Msg3. If feedback is used as feedback on Msg3, it can be called Msg4. Optionally, feedback can be provided to multiple A-IoT devices, multiple uplink data, or multiple Msg3s. Feedback can indicate success or failure by default. Feedback can also explicitly indicate success or failure, such as by carrying indication information; if the indication information is 1, it indicates success, and if it is 0, it indicates failure. Optionally, feedback can be associated with A-IoT devices, such as by carrying the identification information of the A-IoT device, or by scrambling (descrambling) or masking (demasking) the A-IoT device's identification information using cyclic redundancy check (CRC). The identification information of the A-IoT device can be at least one of AS ID, random ID, and device ID, or a part of AS ID, random ID, and device ID, or derived from AS ID, random ID, and device ID (e.g., through hash operations). If the feedback is associated with an A-IoT device, the A-IoT device can determine whether the uplink data or Msg3 sent before receiving the feedback was successfully transmitted based on the feedback.

[0224] Msg2 is used for contention resolution (or a random ID response, used to respond with a random number or Msg1), indicating successful contention resolution, successful transmission, or successful access (Msg1 or the A-IoT device). Msg2 can carry a random ID or identification information derived from a random ID, which can be understood as contention resolution identification information. For example, if random ID#1 indicates successful access / contention resolution, Msg2 can carry random ID#1. Optionally, Msg2 can also carry an access stratum identity (AS ID). The reader assigns an AS ID to A-IoT devices that have successfully accessed or resolved contention. The AS ID can be an index of the A-IoT device's access opportunity (or time-domain and / or frequency-domain resources).

[0225] The first data in the first information scheduling can be Msg3 or uplink data. Msg3, also known as D2R data, can include at least one of a random identifier, a device ID, and upper-layer data. Uplink data can also be called D2R data. Uplink data can be sent to the core network, such as an A-IoTF entity, an AMF entity, or an AF entity. For example, uplink data can be a response to downlink data, such as a response to a command. Specifically, it can be a response to at least one of the commands: read, write, sensing, locking, deactivation, and positioning. This is only an example and does not mean that downlink data can only be these commands.

[0226] Optionally, after receiving the first information, the first device can determine whether the first information includes the first control information in the following ways.

[0227] In the first approach, the first information includes type information, which indicates the type of the first information, such as a message type. The type of the first information is used to determine whether the first information includes the first control information. After receiving the first information, the first device can determine whether the first information includes the first control information based on the type information. For example, the type information in the first information may include 2 bits, and the type of the first information may include paging message, Msg2, MAC SDU with TBS, and MAC SDU without TBS. Wherein, 00 corresponds to paging message, 01 corresponds to Msg2, 10 corresponds to MAC SDU with TBS, and 11 corresponds to MAC SDU without TBS. After receiving the first information, if the two bits of the type information are 10, the first device can determine that the information type of the first information is a MAC SDU with TBS, and the first information includes control information used to indicate the TBS scheduled by the first information. If the two bits of the type information are 11, the first device can determine that the information type of the first information is a MAC SDU without TBS, and the first information does not include control information. This reduces the need for optional fields, such as avoiding the need to indicate the presence of TBS by using an extra bit.

[0228] Figure 6 shows a schematic diagram of the structure of first information. The first information may include a medium access control (MAC) subheader and a MAC element. The MAC subheader may include type information, and the MAC element includes a MAC SDU. If the type information is type 1, the MAC element also includes control information; if the type information is type 2, the MAC element does not include control information. Optionally, the MAC subheader may also include indication information for whether to reassign an AS ID. If the indication information indicates AS ID reassignment, the MAC element also includes the AS ID. If the indication information indicates no AS ID reassignment, the MAC element does not include the AS ID.

[0229] In the second approach, the first information includes first indication information, which indicates whether the first information includes the first control information. After receiving the first information, the first device can determine whether the first information includes the first control information based on the first indication information. Optionally, the first indication information can be one or more bits. Figure 7 shows a schematic diagram of another type of first information structure. The first information may include a MAC sub-header and MAC elements, wherein the MAC sub-header may include type information and indication information (1 bit), and the MAC elements include MAC SDU. If the indication information is 0, the MAC elements also include control information, which is used to indicate the size of the data block scheduled by the first information. If the indication information is 1, the MAC elements do not include control information, that is, it is not necessary to indicate the size of the data block scheduled by the first information.

[0230] The third approach involves determining whether the first information includes first control information based on upper-layer information (e.g., non-access stratum (NAS) information, application layer data, or A-IoT layer data). Here, "upper layer" refers to layers above the access layer. For example, if the access layer only has a MAC layer, then "upper layer" refers to layers above the MAC layer. This can be understood as the first device determining whether the first information includes first control information based on its own upper-layer information. Within the first device, the MAC layer obtains upper-layer information from the upper layer to determine the presence of first control information. This upper-layer information is obtained by the first device's upper layer from the MAC SDU (e.g., NAS information, information from the core network).

[0231] For example, the upper-layer information may include indications of whether a read operation and / or write operation is required. If the indication requires a read operation and / or write operation, the first device may determine that the first information includes the first control information. If the indication does not require a read operation and / or write operation, the first device may determine that the first information does not include the first control information. Alternatively, the upper-layer information may include indications of whether a paging message requires a response. If the indication does not require a response, the first device may determine that the first information does not include the first control information. If the indication requires a response, the first device may determine that the first information includes the first control information, or the first device may discard the first control information and send back a fixed-length acknowledgment message.

[0232] For example, if the upper layer determines that it is a read command and needs to send D2R data, then the TBS is determined to be the size of the data to be transmitted. The payload size is either MAC SDU or MAC CE. Alternatively, the TBS can be the size of the data to be transmitted (NAS PDU (MAC SDU)) and the size of the MAC subheader, with the payload size being MAC subheader + MAC SDU (NAS PDU) or MAC CE. The MAC SDU is a unit encapsulating upper-layer information; its name is not limited. The MAC CE is MAC layer information; its name is also not limited.

[0233] The physical layer (PHY) can determine whether the first information includes first control information based on the indications from the MAC layer or upper layer. For example, the upper layer determines the size of the upper-layer data to be transmitted, and combines this with other information from the MAC layer to determine a TBS or payload size, then informs the physical layer of the TBS or payload size. The upper layer can also indicate the size of the upper-layer data to the MAC layer, and the MAC layer, combining this with other MAC layer information to be transmitted, determines the TBS or payload size, finally informing the physical layer of the TBS or payload size. In this case, it is not necessary to explicitly indicate the TBS; by default, the device, reader, or CN has already determined the size of the data to be transmitted (MAC layer and / or upper layer).

[0234] Optionally, when the second device sends the first information, it can determine whether the first information carries the first control information in the first information through the following methods.

[0235] In one implementation, when the second device has determined the length of the first data, the first information does not include the first control information. Specifically, this includes the following situations:

[0236] Scenario 1: If the second device obtains the length of the first data from the CN, the first information may not include the first control information when scheduling the first data through the first information. For example, as shown in Figure 8, which is a schematic diagram of a communication method, in a scenario where the reader schedules D2R data via command, before random access to A-IoT, the reader obtains the length of the D2R data from the CN. When the reader sends downlink data to the A-IoT device, the downlink data may not include the first control information.

[0237] Scenario 2: If the upper-layer information from the second device indicates an empty NAS packet, no feedback, or feedback of a fixed length (e.g., ACK / NACK), then when scheduling the first data via the first information, the first information may not include the first control information. For example, as shown in Figure 9, which is a schematic diagram of another communication method, in a scenario where the reader schedules D2R data via command, before random access to A-IoT, the reader can determine whether the first information includes the first control information based on the upper-layer information. If the upper-layer information indicates that the length of the D2R data is 0 or there is no subsequent D2R data, then when the reader sends downlink data to the A-IoT device, the downlink data may not include the first control information.

[0238] Scenario 3: If the second device obtains the length of the device identifier of the first device before the first device randomly connects, then when scheduling the first data (including the device identifier of the first device) through the first information, the first information may not include the first control information. For example, as shown in Figure 10. Figure 10 is a schematic diagram of another communication method. In the scenario where the reader schedules Msg3 through Msg2, before the A-IoT device randomly connects, the reader obtains the length of the device identifier of the A-IoT device. The length of the device identifier is fixed, and Msg3 does not support segmented data. Therefore, when the reader sends Msg2 to the A-IoT device, Msg2 may not include the first control information.

[0239] Optionally, when the second device has not determined the length of the first data, the first information includes the first control information. Further, if the second device has not obtained the length of the first data from the CN, the first information includes the first control information when scheduling the first data via the first information. Alternatively, if the upper-layer information of the second device indicates the presence of a NAS packet, or indicates feedback, or indicates data with a changed length, then the first information includes the first control information when scheduling the first data via the first information. Alternatively, if the length of the device identifier of the first device included in the first data is variable, or the first data supports segmented data, then the first information includes the first control information. For example, in a scenario where the reader schedules Msg3 via Msg2, if the length of the device identifier is variable, or Msg3 supports segmented data, then Msg2 includes the first control information, which is used to indicate the length of the device identifier of the A-IoT device.

[0240] In another implementation, before the second device sends the first information, the second device can send second information to the first device. This second information is used to indicate paging or selection of the first device. When the second information indicates the length of the first data, the first information does not include the first control information. For example, the length of the device identifier of an A-IoT device may include 100 bits, 96 bits, or 128 bits. The reader can send a paging message to the A-IoT devices, which uniformly indicates that the length of the device identifiers of multiple A-IoT devices is 100 bits. Thus, when scheduling Msg3 through Msg2, it is unnecessary to explicitly indicate the length of the device identifier for each A-IoT device in each Msg2.

[0241] S502, the first device sends the first data to the second device based on the first information.

[0242] The first data can be data that the second device can correctly parse without needing to schedule the size or length of the payload. Optionally, the first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first message.

[0243] For example, as shown in Figure 8, in a scenario where the reader schedules D2R data via a command, the reader obtains the length of the D2R data from the CN (Content Controller). The reader then sends downlink data to the A-IoT device, which does not include the first control information. After receiving the downlink data, the A-IoT device determines that the downlink data does not include the first control information and then sends D2R data to the reader. This D2R data includes unsegmented data (complete data). Optionally, the D2R data may also include a MAC header.

[0244] As shown in Figure 9, in a scenario where the reader schedules D2R data via command, the upper-layer information of the reader indicates that the length of the D2R data is 0 or there is no subsequent D2R data. The reader sends downlink data to the A-IoT device, and the downlink data does not include the first control information. After receiving the downlink data, the A-IoT device determines that the downlink data does not include the first control information, and the A-IoT device does not send D2R data to the reader. Alternatively, the A-IoT device defaults to sending an ACK, and the D2R data does not include the MAC SDU (i.e., there is no upper-layer data).

[0245] As shown in Figure 10, in the scenario where the reader schedules Msg3 via Msg2, the reader sends Msg2 to the A-IoT device. Msg2 does not include the first control information. After receiving Msg2, the A-IoT device sends Msg3 to the reader. Msg3 includes the device identifier of the A-IoT device. The length of the device identifier of the A-IoT device is fixed, and this length can be indicated by the reader through a paging message.

[0246] Optionally, the first device may use segmentation indication information to indicate to the second device that the first data is not segmented, or that the first data is complete, or that there is no other (to be transmitted) data.

[0247] It should be noted that, in the absence of first control information in the first information, the first device may send other data in addition to sending unsegmented data, the device identifier of the first device, or confirmation information of the first information.

[0248] Optionally, the second device can send third information to the first device. This third information includes second control information, which is used to schedule the transmission of second data. The second control information is used to schedule the length of the second data. The first device can send the second data to the second device based on the third information, and the second data is used to respond to the third information. Specifically, this includes the following implementation methods:

[0249] In one implementation, the second control information includes M bits, which are used to indicate the type of the second data, with each type corresponding to a length, and M being an integer greater than or equal to 1. The second data may include a device identifier. The third information includes at least one of the following: a paging message, message 2 (Msg2), or a random access trigger message. The paging message, message 2 (Msg2), and random access trigger message are as described above and will not be repeated here.

[0250] For example, the length of the device identifier is not continuously variable; device identifiers can be divided into various types, such as 96-bit, 128-bit, 256-bit, or 496-bit device identifiers, etc., for example only, and the specific values ​​are not limited. When scheduling the device identifier carried in Msg3 using Msg2, Msg2 includes second control information, which can include 2 bits. Here, 00 corresponds to a 96-bit device identifier, 01 corresponds to a 128-bit device identifier, 10 corresponds to a 256-bit device identifier, and 11 corresponds to a 496-bit device identifier. If the two bits included in the second control information are 01, it indicates that the length of the second data is 128 bits. If the two bits included in the second control information are 11, it indicates that the length of the second data is 496 bits.

[0251] In another implementation, the second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1. The second data can be uplink data, and the third information is downlink data.

[0252] For example, when scheduling uplink data via downlink data, the length of the scheduled uplink data may vary continuously. The highest bit of the uplink data can be 1000 bits. Therefore, the downlink data may include first control information (such as TBS indication) to indicate the length range of the uplink data. For example, in bytes, the length range of the uplink data can be indicated by 7 bits as 1 to 128 bytes.

[0253] Optionally, M is less than N. That is, the number of bits used to indicate the type of the second data through the second control information is less than the number of bits used to indicate the length range of the second data through the second control information.

[0254] In this embodiment of the application, in an A-IoT scenario, when the second device schedules the first data using the first information, it does not carry the first control information in the first information, thus reducing the number of bits occupied by the first control information. If the first device does not include the first control information in the first information, it can send unsegmented data, the device identifier of the first device, or confirmation information of the first information, ensuring that the second device can correctly parse the first data. This reduces signaling overhead and improves communication efficiency.

[0255] As shown in Figure 11, Figure 11 is a flowchart illustrating another communication method provided in an embodiment of this application. The first device can be an A-IoT device, and the second device can be a reader. Alternatively, the first device can be a reader, and the second device can be an A-IoT device. The method mainly includes the following steps:

[0256] S1101, the second device sends third information to the first device. The third information includes second control information. The third information is used to schedule the transmission of the second data. The second control information is used to indicate the type or length range of the second data. One type corresponds to one length.

[0257] Optionally, the services between the first device and the second device include at least one of the following: inventory, positioning, sensing, or commands.

[0258] In one implementation, the second control information includes M bits, which are used to indicate the type of the second data, with each type corresponding to a length, and M being an integer greater than or equal to 1. The third information includes at least one of the following: a paging message, Msg2, or a random access trigger message.

[0259] In another implementation, the second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1. The third information is downlink data.

[0260] The second data can be of the device ID type or the device ID length type. For example, there are four types of device IDs corresponding to four lengths: 48 bits, 96 bits, 128 bits, and 496 bits. The second control information can include 2 bits, which can indicate the four types of device IDs: 00 corresponds to a device ID with a TBS of 48 bits, 01 corresponds to a device ID with a TBS of 96 bits, 10 corresponds to a device ID with a TBS of 128 bits, and 11 corresponds to a device ID with a TBS of 496 bits.

[0261] Optionally, the second control information can be used to determine the length of the device ID. The TBS of the scheduled second data is equal to the length of the device ID indicated by the second control information plus the sum of the size of other MAC information (such as the size of the MAC header). For example, if the MAC header of Msg3 (as specified by the protocol) is 8 bits, and the device ID is determined to be 48 bits according to the second control information, then the TBS of Msg3 is: 8 + 48 = 56 bits.

[0262] Optionally, the second control information is used to determine the payload size including the MAC header, that is, the first device directly determines the TBS of the scheduled second data based on the second control information.

[0263] Optionally, M is less than N. That is, the number of bits used to indicate the type of the second data through the second control information is less than the number of bits used to indicate the length range of the second data through the second control information.

[0264] The second control information can indicate a length range of the second data, meaning data of any length within that range can be scheduled. Alternatively, the second control information can indicate a single value within the length range of the second data, meaning data of a specific value within that range can be scheduled. For example, the second indication information can indicate 16 to 24 bits, meaning data of any length between 16 and 24 bits can be scheduled. The second indication information can also indicate a value within a length range of 1 to 1024 bits (or 1 to 128 bytes) (e.g., 2 bytes or 40 bytes), requiring at least 7 bits to indicate 128 different byte lengths, corresponding to scheduling data of 2 bytes or 40 bytes.

[0265] Optionally, the second device can obtain the type and length of the second data via the CN. For example, the CN indicates the length or type of the device ID, and the second device determines the TBS of the second data, which is the sum of the device ID length (or the length of NAS or upper layer data) and the length of the message header (e.g., the MAC header). Alternatively, the CN directly indicates the size of the data including the MAC header; that is, the second device determines the TBS of the second data based on the size of the data including the MAC header indicated by the CN.

[0266] S1102, the first device sends second data to the second device based on the third information, and the second data is used to respond to the third information.

[0267] The second data can be at least one of the following: Msg3 (device ID) or D2R data (uplink data or upper layer data).

[0268] The specific implementation of this application embodiment can refer to the optional method of scheduling the second data through the third information in the previous embodiment, and will not be repeated here.

[0269] In this embodiment of the application, in an A-IoT scenario, when the second device schedules the second data through the third information, it indicates the type or length range of the scheduled second data through the second control information included in the third information. This enables the first device to send data based on the second control information, ensuring that the second device can correctly parse the second data. This achieves flexible scheduling and improves communication efficiency.

[0270] When an A-IoT device receives a paging message, if a first condition is met (e.g., the device identifier carried in the paging message matches the identification information of the A-IoT device), it responds to the paging message and enters the "ongoing" state. Then, the A-IoT device performs random access. The A-IoT device sends a first message to the reader, and remains in the "ongoing" state after sending the first message. An A-IoT device in the "ongoing" state does not respond to or ignores paging messages from other readers (e.g., those carrying different transaction IDs).

[0271] Therefore, the monitoring process is essentially an ongoing process. The response to the first monitoring message corresponds to the A-IoT device ending or terminating its ongoing state. "Ongoing" corresponds to a service, such as the first business process. The first business process could be the current paging-triggered flow (including random access and data transmission), or a first business process could correspond to a transaction ID, and a transaction ID could correspond to a specific business flow.

[0272] In multi-reader scenarios, how can multiple readers interleave to perform business operations? For example, consider two readers: Scenario 1: Reader1 initiates a paging round, then Reader2 initiates the next paging round, and then Reader1 initiates the next paging round again; Scenario 2: Reader1 initiates a paging round, and before this paging round is completed, Reader2 sends a paging and performs its corresponding paging.

[0273] The existing approach involves carrying an ID (such as a transaction ID or reader ID) in the paging message, with different readers carrying different IDs. In scenario 2, when an A-IoT device transmits services with reader 1, it receives downlink messages from reader 2, such as a Msg2 message sent by reader 2 to another A-IoT device. The A-IoT device might mistakenly identify this as its own Msg2. Therefore, it's possible to carry the reader ID or transaction ID in all downlink messages to distinguish them from different readers. However, this approach incurs significant overhead.

[0274] As shown in Figure 12, Figure 12 is a flowchart illustrating another communication method provided in an embodiment of this application. This method mainly includes the following steps:

[0275] S1201, the first device receives first information from the second device, the first information includes first indication information, the first indication information is used to indicate that the first information is a first information type, and the first information type corresponds to a first service.

[0276] The first service is an unfinished service between the first device and the second device.

[0277] The first piece of information can be Msg2, Feedback, or downlink information, etc. This first piece of information can include R2D data (or upper-layer data, MAC SDU), where R2D data can include commands, such as read commands, write commands, etc.

[0278] The first indication information includes a first numerical value. For example, the first indication information is one bit. If one bit is set to 1, it indicates the first information type; if one bit is set to 0, it indicates the second information type. Alternatively, the first indication information can also be multiple bits. Taking three bits as an example, if all three bits are set to 000, it indicates Msg2, and Msg2 is the first information type; if all three bits are set to 100, it indicates Msg2, and Msg2 is the second information type; if all three bits are set to 001, it indicates Feedback, and Feedback is the first information type; if all three bits are set to 101, it indicates Feedback, and Feedback is the second information type; if all three bits are set to 010, it indicates MAC SDU, and MAC SDU is the first information type; if all three bits are set to 110, it indicates MAC SDU, and MAC SDU is the second information type.

[0279] It should be noted that the first information type corresponds to the service between the first device and the second device, and the second information type corresponds to the service between the first device and the third device. The above only lists two information types (the first information type and the second information type). Multiple information types (three or more information types) can also be distinguished by multiple bits. For example, the third information type corresponds to the service between the first device and the third device.

[0280] Optionally, before receiving the first information from the second device, the first device may receive a third information from the second device. This third information indicates that a response to downlink information of the first information type is currently required. That is, after receiving the third information, the first device can determine the first information type based on the third information and respond only to downlink information of the first information type, without needing to respond to downlink information of the second information type.

[0281] The third piece of information can be a paging message. This third piece of information may include first identification information, which corresponds to the first service. That is, the first device determines that the first service needs to be executed based on the first identification information and only responds to the downlink information of the first service.

[0282] Optionally, the first device may send a fourth message to the second device before the first service is completed; and monitor the first message while the service is in the ongoing state. The fourth message may be Msg1 or Msg3.

[0283] When at least one of the following conditions is met, the first device that is in an ongoing state and is monitoring the response information (first information) of the fourth information considers the fourth information to have been successfully transmitted, and / or terminates the current ongoing state or monitoring.

[0284] Scenario 1: The first device can determine whether the fourth message was successfully transmitted based on a timer. After sending the fourth message, the first device starts a timer. If the timer expires, the fourth message is considered successfully transmitted. If the fifth message is received during the timer's operation, the timer is stopped, and a response to the fifth message is sent. (Optionally, re-access is not performed / skipped). The fifth message can be one or more of the following: Feedback, an R2D message sent to the first device (e.g., carrying / associating with the same AS ID stored on the device), a contention resolution success message (or access response, such as Msg2 or random ID response), or a paging message.

[0285] In scenario two, if the first device receives a paging message (carrying the same transaction ID as currently stored) after sending the fourth message, it considers the transmission to be complete / successful.

[0286] Scenario 3: After the first device sends the fourth message, it receives N R2D messages (these can be the same message or different messages, only the cumulative number of R2D messages is counted), then the transmission is considered to be complete / successful.

[0287] Scenario 4: After the first device sends the fourth message, it receives a broadcast end indication (which may not be associated with any device and is optional; it may carry a transaction ID, in which case the transaction ID stored by the device must be the same as the transaction ID currently carried), and then considers the transmission to be complete / successful.

[0288] Optionally, if the first device considers the fourth information transmission successful and / or terminates the current service or monitoring, it may choose not to perform a re-access or skip the re-access.

[0289] If at least one of the following conditions is met, the first device that is in an ongoing state and is monitoring the response information (first information) of the fourth information considers the transmission of the fourth information to have failed, and / or terminates the current ongoing state or monitoring of the service.

[0290] In scenario one, the first device can determine whether the fourth information was successfully transmitted based on a timer. After sending the fourth information, the first device starts a timer. If the timer expires, the transmission of the fourth information is considered to have failed. During the timer's operation, if it receives feedback and / or other messages sent to the device (such as R2D messages carrying / associating with the same AS ID stored on the device) or receives a contention resolution success message (or access response, such as Msg2 or random ID response), the timer will be terminated.

[0291] In scenario two, if the first device receives a paging message (carrying the same transaction ID as currently stored) after sending the fourth message, it considers the transmission to have ended or failed.

[0292] Scenario 3: After the first device sends the fourth message, it receives N R2D messages (these can be the same message or different messages, only the cumulative number of R2D messages is counted), then the transmission is considered to have ended / failed.

[0293] Scenario 4: After the first device sends the fourth message, if it receives a broadcast end indication (which may not be associated with any device and is optional; it may carry a transaction ID, in which case the transaction ID stored by the device must be the same as the transaction ID currently carried), then it considers the transmission to have ended / failed.

[0294] Optionally, the first device may re-access the device after it determines that the fourth information transmission has failed and / or after terminating the current service or monitoring.

[0295] Optionally, before sending the first information to the first device, the second device may receive third indication information from the core network device. This third indication information indicates the need to send downlink information of the first information type. Based on this third indication information, the second device sends the first information to the first device. In other words, the second device can learn from the core network device that it needs to send downlink data of the first information type, but not downlink data of the second information type.

[0296] S1202, the first device sends a first response to the second device based on the first indication information.

[0297] The first response can be Msg3 or an uplink message. The first response may include D2R data.

[0298] Optionally, a second message is received from a third device, the second message including a second indication message, the second indication message indicating that the second message is of the second message type, the second message type corresponding to a second service, the second service being different from the first service; based on the second indication message, a second response is not sent to the third device.

[0299] The second indication information includes a second numerical value. The second indication information is similar to the first indication information described above, and the indication method of the second indication information can refer to the indication method of the first indication information, which will not be repeated here.

[0300] For example, for Msg2, the message types of Msg2 include Msg type1 and Msg type2. Msg type1 and Msg type2 can be used to distinguish different readers. For example, if reader1 sends downlink messages of message type1, the device, while monitoring the downlink messages sent by reader1 (during the ongoing process), will only respond to downlink messages of message type1 and will not respond to downlink messages of message type2.

[0301] As shown in Table 1, the downlink information includes Msg2, Feedback, and MAC SDU. Msg2 includes Msg2 of the first information type and Msg2 of the second information type; Feedback includes Feedback of the first information type and Feedback of the second information type; MAC SDU includes MAC SDU of the first information type and MAC SDU of the second information type. Specifically, 000 corresponds to Msg2 of the first information type, 100 corresponds to Msg2 of the second information type, 001 corresponds to Feedback of the first information type, 101 corresponds to Feedback of the first information type, 010 corresponds to MAC SDU of the first information type, and 110 corresponds to MAC SDU of the first information type.

[0302] Specifically, during an incomplete / ongoing business process (taking a business triggered by paging as an example, such as an incomplete business with the currently saved transaction ID1), the device only responds to R2D messages with Msg type 000, 001, and 010. R2D messages with Msg type 100, 101, and 110 can be ignored (no response). Alternatively, the device only responds to R2D messages with Msg type 100, 101, and 110, and R2D messages with Msg type 000, 001, and 010 can be ignored.

[0303] Table 1

[0304] Optionally, at least two sets of information types for R2D messages are predefined. These at least two sets of information types include a first set of information types and at least one set of second information types. The first set of information types corresponds to intra-BS R2D messages and is used in intra-BS scenarios. The at least one set of second information types corresponds to inter-BS R2D messages and is used in inter-BS scenarios. For the first device, if the received first information includes first indication information indicating that the first information is of the first information type, then the first information is responded to. If the received second information includes second indication information indicating that the second information is of the second information type, then the second information is not responded to. That is, the first device only responds to intra-BS R2D messages and does not respond to (ignores) inter-BS R2D messages. For the second device, if it receives indication information from a CN or a neighboring device (e.g., a neighboring base station), this indication information can trigger the second device to send inter-BS R2D messages.

[0305] In this embodiment of the application, in a multi-reader scenario, the first indication information indicates the information type of the downlink information, enabling the first device to distinguish downlink information from different readers, avoiding the downlink information from carrying reader ID or transaction ID, thereby reducing signaling overhead and improving communication efficiency.

[0306] It should be noted that in all the above embodiments, the first device and / or the second device can perform some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application can also perform other operations or variations of various operations. Furthermore, the steps can be performed in different orders as presented in each embodiment, and it is not necessary to perform all the operations in the embodiments of this application. Moreover, the sequence number of each step 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.

[0307] Different embodiments of this application can be used in combination or separately, and this application is not limited thereto.

[0308] It is understood that, in the above-described method embodiments, the methods and operations implemented by the first device can also be implemented by components (e.g., chips or circuits) that can be used in the first device, and the methods and operations implemented by the second device can also be implemented by components (e.g., chips or circuits) that can be used in the second device.

[0309] This application embodiment can divide the first device or the second device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, 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.

[0310] The methods provided by the embodiments of this application have been described in detail above with reference to Figures 5, 11, and 12. The communication apparatus provided by the embodiments of this application will be described in detail below with reference to Figures 13 and 14. It should be understood that the descriptions of the apparatus embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail can be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0311] Please refer to Figure 13, which is a schematic diagram of a communication device provided in an embodiment of this application. This communication device can implement the steps or processes executed by the first device corresponding to those described in the method embodiments above. In one possible design, the communication device may include a receiving module 1301 and a transmitting module 1302. Optionally, the communication device may further include a storage module for storing device program code and / or data.

[0312] The communication device can be the terminal-side device in the above embodiments, such as the first device or the communication module in the first device, or the circuit or chip in the first device responsible for communication functions.

[0313] The receiving module 1301 is used to receive first information from the second device, the first information not including first control information, the first information being used to schedule the transmission of first data, and the first control information being used to schedule the length of the first data.

[0314] The sending module 1302 is used to send the first data to the second device based on the first information. The first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information. The service between the first device and the second device includes at least one of the following: inventory, positioning, sensing, or command.

[0315] Optionally, the first information includes type information, which indicates the type of the first information, and the type of the first information is used to determine whether the first information includes the first control information.

[0316] Optionally, the first information includes first indication information, which is used to indicate whether the first information includes the first control information.

[0317] Optionally, whether the first information includes the first control information is determined based on non-access layer information or upper layer information.

[0318] Optionally, when the second device has determined the length of the first data, the first information does not include the first control information.

[0319] Optionally, the receiving module 1301 is configured to receive second information from the second device, the second information being used for paging or selecting the first device;

[0320] Wherein, when the second information indicates the length of the first data, the first information does not include the first control information.

[0321] Optionally, the first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

[0322] Optionally, the receiving module 1301 is further configured to receive third information from the second device, the third information including second control information, the third information being used to schedule the transmission of second data, and the second control information being used to schedule the length of the second data;

[0323] The sending module 1302 is further configured to send the second data to the second device based on the third information, wherein the second data is used to respond to the third information.

[0324] Optionally, the second control information includes M bits, which are used to indicate the type of the second data, with each type corresponding to a length, and M being an integer greater than or equal to 1.

[0325] Optionally, the third information includes at least one of the following: paging message, message 2 (Msg2), and random access trigger message.

[0326] Optionally, the second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1.

[0327] Optionally, the third information is downlink data.

[0328] Optional, M is less than N.

[0329] In one possible design, when the communication device is a first device or a communication module within a first device, the functions of the receiving module 1301 and the transmitting module 1302 can be implemented by a transceiver circuit. Optionally, the communication device may further include a processing module, the functions of which can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core.

[0330] In one possible design, when the communication device is a circuit or chip responsible for communication functions in the first device, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the functions of the receiving module 1301 and the transmitting module 1302 can be implemented by the interface circuitry or data transceiver circuitry on the aforementioned chip. Optionally, the communication device may also include a processing module, the functions of which can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores.

[0331] It should be noted that the implementation of each module can also refer to the corresponding descriptions of the method embodiments shown in Figures 5, 11 and 12, and execute the methods and functions performed by the first device in the above embodiments.

[0332] Please refer to Figure 14, which is a schematic diagram of another communication device provided in an embodiment of this application. This communication device can implement the steps or processes executed by the second device corresponding to those described in the method embodiments above. In one possible design, the communication device may include a transmitting module 1401 and a receiving module 1402. Optionally, the communication device may further include a storage module for storing device program code and / or data.

[0333] The communication device can be a network-side device in the above embodiments, such as a second device or a communication module in the second device, or a circuit or chip in the second device that is responsible for communication functions.

[0334] The sending module 1401 is used to send first information to the first device. The first information does not include first control information. The first information is used to schedule the transmission of first data. The first control information is used to schedule the length of the first data.

[0335] The receiving module 1402 is configured to receive the first data from the first device based on the first information. The first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information. The service between the first device and the second device includes at least one of the following: inventory, positioning, sensing, or command.

[0336] Optionally, the first information includes type information, which indicates the type of the first information, and the type of the first information is used to determine whether the first information includes the first control information.

[0337] Optionally, the first information includes first indication information, which is used to indicate whether the first information includes the first control information.

[0338] Optionally, whether the first information includes the first control information is determined based on non-access layer information or upper layer information.

[0339] Optionally, when the second device has determined the length of the first data, the first information does not include the first control information.

[0340] Optionally, the sending module 1401 is further configured to send second information to the first device, the second information being used to indicate paging or selection of the first device;

[0341] Wherein, when the second information indicates the length of the first data, the first information does not include the first control information.

[0342] Optionally, the first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

[0343] Optionally, the sending module 1401 is further configured to send third information to the first device, the third information including second control information, the third information being used to schedule the transmission of second data, and the second control information being used to schedule the length of the second data;

[0344] The receiving module 1402 is further configured to receive the second data from the first device based on the third information, wherein the second data is used to respond to the third information.

[0345] Optionally, the second control information includes M bits, which are used to indicate the type of the second data, with each type corresponding to a length, and M being an integer greater than or equal to 1.

[0346] Optionally, the third information includes at least one of the following: paging message, message 2 (Msg2), and random access trigger message.

[0347] Optionally, the second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1.

[0348] Optionally, the third information is downlink data.

[0349] Optional, M is less than N.

[0350] In one possible design, when the communication device is a second device or a communication module within a second device, the functions of the transmitting module 1401 and the receiving module 1402 can be implemented by a transceiver circuit. Optionally, the device may further include a processing module, the functions of which can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core.

[0351] In one possible design, when the communication device is a circuit or chip responsible for communication functions in a second device, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the functions of the transmitting module 1401 and the receiving module 1402 can be implemented by the interface circuitry or data transceiver circuitry on the aforementioned chip. Optionally, the device may further include a processing module, the functions of which can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores.

[0352] It should be noted that the implementation of each module can also refer to the corresponding descriptions of the method embodiments shown in Figures 5, 11 and 12, and execute the methods and functions performed by the second device in the above embodiments.

[0353] Figure 15 is a schematic diagram of the structure of a first device provided in an embodiment of this application. This first device can be applied to the systems shown in Figures 1A-1E, 2, and 3 to perform the functions of the first device in the above method embodiments, or to implement the steps or processes executed by the first device in the above method embodiments.

[0354] As shown in Figure 15, the first device includes a processor 1501 and a transceiver 1502. The transceiver 1502 includes a transmitter 1521, a receiver 1522, and an antenna 1523. The receiver 1522 can be used to receive transmission control information through the antenna 1523, and the transmitter 1521 can be used to send transmission feedback information to the second device through the antenna 1523. Optionally, the first device also includes a memory 1503. The processor 1501, transceiver 1502, and memory 1503 can communicate with each other through internal connection channels to transmit control and / or data signals. The memory 1503 is used to store computer programs, and the processor 1501 is used to call and run the computer programs from the memory 1503 to control the transceiver 1502 to transmit and receive signals. Optionally, the first device may also include an antenna for transmitting uplink data or uplink control signaling output by the transceiver 1502 via wireless signals.

[0355] The processor 1501 and the memory 1503 can be integrated into a single processing device. The processor 1501 executes the program code stored in the memory 1503 to achieve the aforementioned functions. In specific implementations, the memory 1503 can be integrated into the processor 1501 or be independent of the processor 1501.

[0356] The transceiver 1502 described above can correspond to the receiving module and transmitting module in Figure 13, and can also be referred to as a transceiver unit or transceiver module. The transceiver 1502 may include a receiver (or receiver circuit) and a transmitter (or transmitter circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.

[0357] It should be understood that the first device shown in FIG15 can implement the various processes involving the first device in the method embodiments shown in FIG5, FIG11 and FIG12. The operation and / or function of each module in the first device are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0358] The processor 1501 described above can be used to execute the actions implemented internally by the first device as described in the preceding method embodiments, while the transceiver 1502 can be used to execute the actions described in the preceding method embodiments of sending data from the first device to the second device or receiving data from the second device. For details, please refer to the descriptions in the preceding method embodiments; they will not be repeated here.

[0359] The processor 1501 can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor 1501 can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc. The first device may also include a communication bus, which can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. The communication bus is used to realize the connection and communication between these components. In this embodiment, the transceiver 1502 is used for signaling or data communication with other node devices. The memory 1503 may include volatile memory, such as nonvolatile random access memory (NVRAM), phase change RAM (PRAM), magnetoresistive RAM (MRAM), etc., and may also include non-volatile memory, such as at least one disk storage device, electrically erasable programmable read-only memory (EEPROM), flash memory devices, such as NOR flash memory or NAND flash memory, semiconductor devices, such as solid-state disk (SSD), etc. Optionally, the memory 1503 may also be at least one storage device located remotely from the aforementioned processor 1501. Optionally, the memory 1503 may also store a set of computer program code or configuration information. Optionally, the processor 1501 may also execute the program stored in the memory 1503. The processor can cooperate with the memory and transceiver to execute any of the methods and functions of the first device in the above-described embodiments.

[0360] Figure 16 is a schematic diagram of a second device provided in an embodiment of this application. This second device can be applied to the systems shown in Figures 1A-1E, 2, and 3 to perform the functions of the second device in the above method embodiments, or to implement the steps or processes performed by the second device in the above method embodiments.

[0361] As shown in Figure 16, the second device includes a processor 1601 and a transceiver 1602. The transceiver 1602 includes a transmitter 1621, a receiver 1622, and an antenna 1623. The transmitter 1621 can be used to send transmission control information to the first device through the antenna 1623, and the receiver 1622 can be used to receive transmission feedback information sent by the first device through the antenna 1623. Optionally, the second device also includes a memory 1603. The processor 1601, transceiver 1602, and memory 1603 can communicate with each other through internal connection paths to transmit control and / or data signals. The memory 1603 is used to store computer programs, and the processor 1601 is used to call and run the computer programs from the memory 1603 to control the transceiver 1602 to transmit and receive signals. Optionally, the second device may also include an antenna for transmitting uplink data or uplink control signaling output by the transceiver 1602 via wireless signals.

[0362] The processor 1601 and the memory 1603 can be integrated into a single processing device. The processor 1601 executes the program code stored in the memory 1603 to achieve the aforementioned functions. In specific implementations, the memory 1603 can be integrated into the processor 1601 or be independent of the processor 1601.

[0363] The transceiver 1602 described above can correspond to the transmitting module and receiving module in Figure 14, and can also be referred to as a transceiver unit or transceiver module. The transceiver 1602 may include a receiver (or receiver circuit) and a transmitter (or transmitter circuit). The receiver is used to receive signals, and the transmitter is used to transmit signals.

[0364] It should be understood that the second device shown in Figure 16 can implement the various processes involving the second device in the method embodiments shown in Figures 5, 11, and 12. The operation and / or function of each module in the second device are respectively for implementing the corresponding processes in the above method embodiments. For details, please refer to the description in the above method embodiments; to avoid repetition, detailed descriptions are appropriately omitted here.

[0365] The processor 1601 described above can be used to execute the actions implemented internally by the second device as described in the preceding method embodiments, while the transceiver 1602 can be used to execute the actions described in the preceding method embodiments of sending data from the second device to the first device or receiving data from the first device. For details, please refer to the descriptions in the preceding method embodiments; they will not be repeated here.

[0366] The processor 1601 can be any of the processors mentioned above. The second device may also include a communication bus, which can be a PCI bus (Peripheral Component Interconnect Standard) or an EISA bus (Extended Industry Standard Architecture). The bus can be divided into an address bus, a data bus, and a control bus. The communication bus is used to enable communication between these components. In this embodiment, the transceiver 1602 is used for signaling or data communication with other devices. The memory 1603 can be any of the memory types mentioned above. Optionally, the memory 1603 can also be at least one storage device located remotely from the processor 1601. The memory 1603 stores a set of computer program code or configuration information, and the processor 1601 executes the program in the memory 1603. The processor can cooperate with the memory and the transceiver to execute any of the methods and functions of the second device in the above embodiments.

[0367] This application also provides a chip system including a processor for supporting a first device or a second device to implement the functions involved in any of the above embodiments, such as generating or processing the first information involved in the above methods.

[0368] In one possible design, the chip system may further include a memory for storing computer programs and data necessary for the second or first device. The chip system may be composed of chips or may include chips and other discrete components. The inputs and outputs of the chip system correspond to the receiving and transmitting operations of the second or first device in the method embodiments, respectively.

[0369] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: a computer program that, when run on a computer, causes the computer to perform the method of any one of the embodiments shown in FIG5, FIG11 and FIG12.

[0370] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing a computer program that, when run on a computer, causes the computer to perform the method of any one of the embodiments shown in FIG5, FIG11 and FIG12.

[0371] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0372] 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, characterized in that, The method, which involves applying a chip to a first device or a chip in a first device, includes: Receive first information from the second device, the first information not including first control information, the first information being used to schedule the transmission of first data, and the first control information being used to schedule the length of the first data; Based on the first information, the first data is sent to the second device. The first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information. The services between the first device and the second device include at least one of the following: inventory, positioning, sensing, or command.

2. The method as described in claim 1, characterized in that, The first information includes type information, which is used to indicate the type of the first information, and the type of the first information is used to determine whether the first information includes the first control information.

3. The method as described in claim 1, characterized in that, The first information includes first indication information, which is used to indicate whether the first information includes the first control information.

4. The method of claim 1, wherein, Whether the first information includes the first control information is determined based on non-access layer information or upper layer information.

5. The method according to any one of claims 1-4, characterized in that, When the second device has determined the length of the first data, the first information does not include the first control information.

6. The method according to any one of claims 1 to 5, wherein, Before receiving the first information, the process also includes: Receive second information from the second device, the second information being used to page or select the first device; Wherein, when the second information indicates the length of the first data, the first information does not include the first control information.

7. The method according to any one of claims 1-6, characterized in that, The first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: Receive third information from the second device, the third information including second control information, the third information being used to schedule the transmission of second data, the second control information being used to schedule the length of the second data; Based on the third information, the second data is sent to the second device, and the second data is used to respond to the third information.

9. The method as described in claim 8, characterized in that, The second control information includes M bits, which are used to indicate the type of the second data. Each type corresponds to a length, and M is an integer greater than or equal to 1.

10. The method as described in claim 9, characterized in that, The third information includes at least one of the following: paging message, message 2 (Msg2), and random access trigger message.

11. The method as described in claim 8, characterized in that, The second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1.

12. The method of claim 11, wherein, The third piece of information is downlink data.

13. The method according to any one of claims 9 to 12, wherein, M is less than N.

14. A communication method, comprising: The method, which applies to a second device or a chip in a second device, includes: Send first information to the first device, the first information not including first control information, the first information being used to schedule the transmission of first data, and the first control information being used to schedule the length of the first data; Based on the first information, the first data from the first device is received. The first data includes unsegmented data, the device identifier of the first device, or confirmation information of the first information. The service between the first device and the second device includes at least one of the following: inventory, positioning, sensing, or command.

15. The method as described in claim 14, characterized in that, The first information includes type information, which is used to indicate the type of the first information, and the type of the first information is used to determine whether the first information includes the first control information.

16. The method as described in claim 14, characterized in that, The first information includes first indication information, which is used to indicate whether the first information includes the first control information.

17. The method as described in claim 14, characterized in that, Whether the first information includes the first control information is determined based on non-access layer information or upper layer information.

18. The method according to any one of claims 14-17, characterized in that, When the second device has determined the length of the first data, the first information does not include the first control information.

19. The method according to any one of claims 14-18, characterized in that, Before sending the first information, the method further includes: Send a second message to the first device, the second message being used to instruct paging or selection of the first device; Wherein, when the second information indicates the length of the first data, the first information does not include the first control information.

20. The method according to any one of claims 14-19, characterized in that, The first information includes at least one of the following: paging message, random access trigger message, downlink data, and feedback message.

21. The method according to any one of claims 14-20, characterized in that, The method further includes: Send a third message to the first device, the third message including second control information, the third message being used to schedule the transmission of second data, the second control information being used to schedule the length of the second data; Based on the third information, the second data is received from the first device, and the second data is used to respond to the third information.

22. The method as described in claim 21, characterized in that, The second control information includes M bits, which are used to indicate the type of the second data. Each type corresponds to a length, and M is an integer greater than or equal to 1.

23. The method as described in claim 22, characterized in that, The third information includes at least one of the following: paging message, message 2 (Msg2), and random access trigger message.

24. The method as described in claim 21, characterized in that, The second control information includes N bits, which are used to indicate the length range of the second data, where N is an integer greater than or equal to 1.

25. The method as described in claim 24, characterized in that, The third piece of information is downlink data.

26. The method according to any one of claims 22-25, characterized in that, M is less than N.

27. A communication device, characterized in that, Includes units or modules for performing the method of any one of claims 1-13 or any one of claims 14-26.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program that, when executed by a processor, causes the method of any one of claims 1-13 or any one of claims 14-26 to be implemented.

29. A chip, characterized in that, The chip includes a processor and a communication interface, the communication interface being used to communicate with external or internal devices, and the processor being used to implement the method as claimed in any one of claims 1-13 or any one of claims 14-26.

30. A computer program product, characterized in that, When the computer program is executed, the method as claimed in any one of claims 1-13 or any one of claims 14-26 is implemented.

Images