Communication method, computer readable storage medium, and related apparatus

Abstract

The present application provides a communication method, a computer readable storage medium, and a related apparatus. The method comprises: a first device receiving a first message by means of a first resource; sending first information and second information, wherein the first information is used for instructing a terminal device sending the first message on the first resource to send a second message on a second resource, and the second information is used for indicating the first resource; and receiving the second message by means of the second resource. In embodiments of the present application, for the terminal device that sends the first message on the first resource, the first device can perform scheduling again by means of the first information and the second information, so that the terminal device that sends the first message on the first resource sends the second message on the second resource. In this way, the access efficiency of the terminal device can be improved, and a real-time service requirement can be quickly responded.

Description

Communication method, computer readable storage medium and related device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on April 3, 2024, with application number 202410417212.3 and application name “Communication Method, Computer-readable Storage Medium and Related Devices”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a communication method, a computer-readable storage medium, and related devices. Background Art

[0003] Radio frequency identification (RFID) technology is a contactless automatic identification technology with application scenarios including logistics, inventory management, smart shopping, smart healthcare, etc.

[0004] RFID recognition is primarily achieved through dedicated RFID readers and corresponding RFID tags, which can store relevant information, such as identification information. When a tag is within the communication range of the reader, the reader can provide energy to the tag by sending an excitation signal. The reader can also send signaling or data to the tag. The tag can then receive the signaling or data sent by the reader and respond accordingly, such as sending the electronic product code (EPC) number to the reader or storing the data sent by the reader locally. Summary of the Invention

[0005] The embodiments of the present application disclose a communication method, a computer-readable storage medium, and related devices, which can improve the access efficiency of terminal devices and the response speed of services.

[0006] In a first aspect, a communication method is disclosed. The method can be applied to a first device, a module (e.g., a processor) in the first device, or a logic module or software that implements all or part of the functions of the first device. The following description uses the application to the first device as an example. The communication method may include: receiving a first message via a first resource; sending first information and second information, the first information being used to instruct a terminal device that sent the first message on the first resource to send a second message on a second resource, the second information being used to instruct the first resource; and receiving the second message via the second resource.

[0007] In an embodiment of the present application, for a terminal device that sends an uplink message (such as a first message) on a first resource, the first device can reschedule through the first information and the second information so that the terminal device that sent the first message on the first resource sends the second message on the second resource. In this way, access efficiency can be improved and real-time business needs can be quickly responded to. For example, when a collision occurs on the first resource, the first information and the second information can trigger the terminal device that sent the uplink message on the colliding resource (the first resource) to send the corresponding uplink message again, so that access, data transmission, etc. can be achieved as soon as possible without waiting for the next round of inventory or access process, thereby improving access efficiency. For another example, assuming that the second device has completed access and data transmission through the first resource, if there is a new real-time business need (such as the need to read data stored in the second device, or the need to locate the second device in real time, or the need to write data to the memory of the second device), the first information and the second information can be used to promptly trigger the second device to access, data transmission, etc. again, so that business needs can be quickly responded to without affecting the inventory or access process of other devices in the current round.

[0008] In combination with the first aspect, in a possible implementation manner, the second information implicitly indicates the first information.

[0009] In an embodiment of the present application, the second information may implicitly indicate the first information, that is, the first device may only send one information, thereby saving transmission resources.

[0010] In combination with the first aspect, in a possible implementation, the method further includes: sending third information, where the third information is used to indicate that the second message is a random access message or uplink data.

[0011] In the embodiment of the present application, the first device can flexibly instruct the corresponding terminal device to send an uplink message through the third information, thereby reducing unnecessary interaction processes and improving overall inventory or access efficiency. For example, assuming that the second device only fails to send uplink data, in this case, the third information can be used to instruct the second device to resend the corresponding uplink data, without having to resend the random access request and then send the corresponding uplink data after receiving the random number response signaling.

[0012] In combination with the first aspect, in a possible implementation, the method further includes: sending fourth information, where the fourth information is used to indicate the second resource.

[0013] In combination with the first aspect, in a possible implementation, the first device includes multiple processes, the multiple processes include a first process, the second device is associated with the first process, and the first information is associated with the first process.

[0014] In an embodiment of the present application, for a multi-process scenario, the first information can be associated with the corresponding process (first process) to ensure that the terminal device that sends the first message on the first resource under the corresponding process can be correctly instructed to send the second message on the second resource.

[0015] In combination with the first aspect, in a possible implementation, the first information and the second information are carried in a third message, or a fourth message, or a fifth message; the third message is used to trigger random access of one or more terminal devices; the fourth message is used to trigger the terminal device to perform random access to the next time slot; the fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

[0016] In the embodiment of the present application, the first information and the second information can be flexibly carried in different downlink messages, so as to promptly trigger the terminal device that sent the first message on the first resource to send the second message on the second resource. In addition, by multiplexing related messages (signaling), signaling overhead can be reduced.

[0017] In combination with the first aspect, in a possible implementation, before receiving the first message through the first resource, the method also includes: sending fifth information, which is used to instruct the second device to send the first message on the first resource, and to instruct the third device to send a sixth message on the third resource, and the first resource is different from the third resource.

[0018] In an embodiment of the present application, the first device can directly allocate different resources to different terminal devices, thereby avoiding collisions between terminal devices when sending uplink messages, thereby improving access efficiency.

[0019] In combination with the first aspect, in a possible implementation manner, at least two of the first information, the second information, the third information, and the fourth information are included in the same message.

[0020] In an embodiment of the present application, the first device can carry at least two of the first information, the second information, the third information and the fourth information through a downlink message, which can reduce the number of times the downlink message is sent, thereby saving power consumption and reducing signaling overhead.

[0021] A second aspect discloses a communication method, which can be applied to a second device, a module (e.g., a processor) in the second device, or a logic module or software that implements all or part of the functions of the second device. The following description uses the application to the second device as an example, and the communication method may include: sending a first message via a first resource; receiving first information and second information, the first information being used to instruct a terminal device that sent the first message on the first resource to send a second message on a second resource, the second information being used to instruct the first resource; and sending the second message via the second resource.

[0022] In combination with the second aspect, in a possible implementation manner, the second information implicitly indicates the first information.

[0023] In combination with the second aspect, in a possible implementation, the method further includes: receiving third information, where the third information is used to indicate that the second message is a random access message or uplink data.

[0024] In combination with the second aspect, in a possible implementation, the method further includes: receiving fourth information, where the fourth information is used to indicate the second resource.

[0025] In combination with the second aspect, in a possible implementation, the first device includes multiple processes, the multiple processes include a first process, the second device is associated with the first process, and the first information is associated with the first process.

[0026] In combination with the second aspect, in one possible implementation, the first information and the second information are carried in a third message, or a fourth message, or a fifth message; the third message is used to trigger random access of one or more terminal devices; the fourth message is used to trigger the terminal device to perform random access to the next time slot; the fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

[0027] In combination with the second aspect, in a possible implementation, before sending the first message through the first resource, the method also includes: receiving fifth information, the fifth information being used to instruct the second device to send the first message on the first resource, and instructing the third device to send a sixth message on a third resource, the first resource being different from the third resource.

[0028] In combination with the second aspect, in a possible implementation manner, at least two of the first information, the second information, the third information, and the fourth information are included in the same message.

[0029] It should be noted that the technical solution of the second aspect of this application may correspond to the solution of the first aspect, and the relevant beneficial effects can refer to the beneficial effects of the first aspect.

[0030] A third aspect discloses a communication device, which may be a first device or a module (e.g., a processor, a communication module) in the first device. The communication device includes:

[0031] A receiving unit, configured to receive a first message through a first resource;

[0032] A sending unit, configured to send first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource;

[0033] The receiving unit is further configured to receive a second message through the second resource.

[0034] In combination with the third aspect, in a possible implementation manner, the second information implicitly indicates the first information.

[0035] In combination with the third aspect, in a possible implementation, the sending unit is further used to: send third information, where the third information is used to indicate that the second message is a random access message or uplink data.

[0036] In combination with the third aspect, in a possible implementation, the sending unit is further used to: send fourth information, where the fourth information is used to indicate the second resource.

[0037] In combination with the third aspect, in a possible implementation, the first device includes multiple processes, the multiple processes include a first process, the second device is associated with the first process, and the first information is associated with the first process.

[0038] With reference to the third aspect, in a possible implementation manner, the first information and the second information are carried in a third message, or a fourth message, or a fifth message;

[0039] The third message is used to trigger random access of one or more terminal devices;

[0040] The fourth message is used to trigger the terminal device to perform random access in the next time slot;

[0041] The fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

[0042] In combination with the third aspect, in a possible implementation, before the receiving unit receives the first message through the first resource, the sending unit is also used to: send fifth information, which is used to instruct the second device to send the first message on the first resource, and to instruct the third device to send the sixth message on the third resource, and the first resource is different from the third resource.

[0043] In combination with the third aspect, in a possible implementation manner, at least two of the first information, the second information, the third information, and the fourth information are included in the same message.

[0044] A fourth aspect discloses a communication device, which may be a second device or a module (e.g., a processor, a communication module) in the second device. The communication device includes:

[0045] A sending unit, configured to send a first message through a first resource;

[0046] A receiving unit, configured to receive first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource;

[0047] The sending unit is further configured to send a second message through the second resource.

[0048] In combination with the fourth aspect, in a possible implementation, the second information implicitly indicates the first information.

[0049] In combination with the fourth aspect, in a possible implementation, the receiving unit is further used to: receive third information, where the third information is used to indicate that the second message is a random access message or uplink data.

[0050] In combination with the fourth aspect, in a possible implementation, the receiving unit is further used to: receive fourth information, where the fourth information is used to indicate the second resource.

[0051] In combination with the fourth aspect, in a possible implementation, the first device includes multiple processes, the multiple processes include a first process, the second device is associated with the first process, and the first information is associated with the first process.

[0052] With reference to the fourth aspect, in a possible implementation manner, the first information and the second information are carried in a third message, or a fourth message, or a fifth message;

[0053] The third message is used to trigger random access of one or more terminal devices;

[0054] The fourth message is used to trigger the terminal device to perform random access in the next time slot;

[0055] The fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

[0056] In combination with the fourth aspect, in a possible implementation, before the sending unit sends the first message through the first resource, the receiving unit is also used to: receive fifth information, which is used to instruct the second device to send the first message on the first resource, and to instruct the third device to send the sixth message on the third resource, and the first resource is different from the third resource.

[0057] In combination with the fourth aspect, in a possible implementation manner, at least two of the first information, the second information, the third information, and the fourth information are included in the same message.

[0058] The fifth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instruction stored in a memory to implement the method provided in the above-mentioned first aspect and any possible implementation method of the first aspect.

[0059] The sixth aspect discloses a communication device, including a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instruction stored in a memory to implement the method provided in the above-mentioned second aspect and any possible implementation of the second aspect.

[0060] The seventh aspect discloses a communication system, characterized in that the communication system includes a first device and a second device, the first device is used to implement the method provided in the above-mentioned first aspect and any possible implementation method of the first aspect; the second device is used to implement the method provided in the above-mentioned second aspect and any possible implementation method of the second aspect.

[0061] The eighth aspect discloses a computer-readable storage medium having a computer program or computer instructions stored thereon. When the computer program or computer instructions are executed, the method provided in the above-mentioned first aspect and any possible implementation manner of the first aspect is implemented.

[0062] The ninth aspect discloses a computer-readable storage medium having a computer program or computer instructions stored thereon. When the computer program or computer instructions are executed, the method provided in the second aspect and any possible implementation of the second aspect is implemented.

[0063] The tenth aspect discloses a chip, comprising a processor for executing a program stored in a memory. When the program is executed, the chip executes the method provided in the above-mentioned first aspect and any possible implementation of the first aspect.

[0064] The eleventh aspect discloses a chip comprising a processor for executing a program stored in a memory. When the program is executed, the chip executes the method provided in the above-mentioned second aspect and any possible implementation of the second aspect.

[0065] As a possible implementation, the memory is located outside the chip.

[0066] The twelfth aspect discloses a computer program product, which includes a computer program code. When the computer program code is run, the method provided in the above-mentioned first aspect and any possible implementation of the first aspect is executed, or the method provided in the above-mentioned second aspect and any possible implementation of the second aspect is executed.

[0067] It can be understood that the communication device provided in the third aspect, the communication device provided in the fourth aspect, the communication device provided in the fifth aspect, the communication device provided in the sixth aspect, the computer-readable storage medium provided in the eighth aspect, the computer-readable storage medium provided in the ninth aspect, the chip provided in the tenth aspect, the chip provided in the eleventh aspect, and the computer program product provided in the twelfth aspect are used to execute the method provided in the first aspect of the present application and any possible embodiment of the first aspect, or the method provided in the second aspect and any possible embodiment of the second aspect. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0068] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0069] FIG1 is a schematic diagram of a network architecture disclosed in an embodiment of the present application;

[0070] FIG2 is a schematic diagram of another network architecture disclosed in an embodiment of the present application;

[0071] Figures 3A-3I are schematic diagrams of some network architectures disclosed in embodiments of the present application;

[0072] FIG4 is a schematic diagram of the architecture of an open wireless access network disclosed in an embodiment of the present application;

[0073] FIG5 is a schematic diagram of a radio frequency identification process disclosed in an embodiment of the present application;

[0074] FIG6 is a schematic diagram of a radio frequency identification scenario disclosed in an embodiment of the present application;

[0075] FIG7 is a flow chart of a communication method disclosed in an embodiment of the present application;

[0076] FIG8 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0077] FIG9 is a schematic diagram of another radio frequency identification scenario disclosed in an embodiment of the present application;

[0078] FIG10 is a schematic diagram of another radio frequency identification scenario disclosed in an embodiment of the present application;

[0079] FIG11 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0080] FIG12 is a schematic diagram of another radio frequency identification scenario disclosed in an embodiment of the present application;

[0081] FIG13 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0082] FIG14 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0083] FIG15 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0084] FIG16 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0085] FIG17 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0086] FIG18 is a flow chart of another communication method disclosed in an embodiment of the present application;

[0087] FIG19 is a schematic structural diagram of a communication device disclosed in an embodiment of the present application;

[0088] FIG20 is a schematic diagram of the hardware structure of a communication device disclosed in an embodiment of the present application. DETAILED DESCRIPTION

[0089] The embodiments of the present application disclose a communication method, a computer-readable storage medium, and related devices, which can improve the access efficiency of terminal devices and the response speed of services. The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application.

[0090] In order to better understand the embodiments of the present application, the network architecture of the embodiments of the present application is described below.

[0091] Please refer to Figure 1, which is a schematic diagram of a network architecture disclosed in an embodiment of the present application. As shown in Figure 1, the network architecture may include readers and tags. The readers may include one or more readers (one is shown in Figure 1), and the tags may include one or more tag devices (one is shown in Figure 1).

[0092] Wireless communication can be performed between the reader and the tag device. Communication between the reader and the tag device can include communication from the tag device to the reader and communication from the reader to the tag device. Accordingly, the communication link between the reader and the tag device can include a device-to-reader (DR) link, which is the communication link from the tag device to the reader, and a reader-to-device (RD) link, which is the communication link from the reader to the tag device. In some embodiments, communication from the tag device to the reader can also be referred to as uplink communication, and communication from the reader to the tag device can also be referred to as downlink communication. For example, for communication from the tag device to the reader or from the reader to the tag device, the reader can be configured with one or more antennas for transmitting and receiving data / information; the tag device can be configured with multiple antennas for transmitting and receiving data / information. It should be understood that the reader and tag device can also include multiple components related to data / information transmission and reception (e.g., a processor, modulator, multiplexer, demodulator, or demultiplexer, etc.).

[0093] The reader / writer can be a reader / writer device with radio frequency identification (RFID) capabilities. The reader / writer, also known as a reader, can read data stored in a tag device and perform some processing on the tag data (such as writing data to the tag, updating data, locking data, etc.). In some embodiments, the reader / writer can be an access network device, a terminal device, etc. In some possible implementations, the reader / writer can send an excitation signal to the tag device, and the excitation signal can provide energy to the tag. Exemplarily, the excitation signal can be a continuous wave (CW).

[0094] A tag device can be a data carrier that stores data, and its functions are usually simple and the cost is low. A tag device can also be called an electronic tag, a radio frequency tag, a transponder, etc., or simply a tag. A tag device can serve as a data carrier to store data. For example, a tag can be attached to an item and store information about the item, such as the type of item. For another example, a tag can be combined with various sensors to store data collected by the sensors. In some embodiments, the tag device can be a terminal device, an ambient IoT (A-IoT / AIoT) device, etc.

[0095] It is understandable that there are multiple ways to implement the reader / writer and tag device, two of which are introduced below.

[0096] As an example, the tag device is a terminal device, and the reader is a network device (such as a base station). Accordingly, the communication link between the reader and the tag device can be an uplink and downlink communication link. The information received by the tag device (such as the first information or the second information described below) can be downlink (DL) information / downlink signal / downlink signaling / downlink data, etc., and the information sent by the tag device can be uplink (UL) information / uplink signal / uplink signaling / uplink data, etc.

[0097] As another example, the reader and the tag device may be different terminal devices. Accordingly, the communication link between the reader and the tag device may be a sideline communication link.

[0098] Among them, the access network equipment can be a device that provides access for the terminal device, and can include a radio access network (RAN) device and an access node (AN) device. RAN equipment can include various forms of base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, access points, balloon stations, etc. In systems using different wireless access technologies, the names of radio access network equipment may be different. For example, the base transceiver station (BTS) in the global system for mobile communication (GSM) or code division multiple access (CDMA) network, the NB (NodeB) in wideband code division multiple access (WCDMA), the evolved NodeB (eNB or eNodeB) in long term evolution (LTE), the next generation NodeB (gNB) and ng-eNB (4G base station accessing the 5G core network) in the fifth generation (5G) mobile communication system. The radio access network device can also be a radio controller in a cloud radio access network (CRAN) scenario, a base station device in a future network (such as 6G, 7G, etc.), a radio access network device in a future evolved public land mobile network (PLMN) network, a wearable device, a vehicle-mounted device, a transmission and reception point (TRP), a radio network controller (RNC), a home base station (for example, home evolved NodeB, or home Node B, HNB), a base band unit (BBU), an access point (AP) in a wireless fidelity (WiFi) system, etc.

[0099] In some deployments, access network equipment (such as gNBs) may include central units (CUs) and distributed units (DUs). Access network equipment may also include radio units (RUs), as shown in Figure 2. As shown in Figure 2, access network equipment can communicate with the core network (CN) via a backhaul link and with terminal equipment (UE) via an air interface (e.g., a Uu interface). Specifically, the baseband unit (BBU) in the access network equipment can communicate with the CN via a backhaul link, and the radio unit in the access network equipment can communicate with the terminal equipment via an air interface. Furthermore, the BBU can communicate with the RU via a fronthaul link, and the BBU and RU may or may not be co-located. The BBU may include at least one centralized unit (CU) and at least one distributed unit (DU), and the CU and DU may communicate via a midhaul link. The CU may implement some of the functions of the access network equipment, and the DU may implement some of the functions of the access network equipment. Furthermore, the CU may be used to control the operations of one or more DUs. Exemplarily, the CU can implement the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers, and can also implement the functions of the service data adaptation protocol (SDAP) layer. The DU implements the functions of the radio link control (RLC) and media access control (MAC) layers, and can also implement the functions of part of the physical (PHY) layer or all of the physical layer. For a detailed description of each of the above protocol layers, please refer to the relevant technical specifications of the 3rd Generation Partnership Project (3GPP). It can be understood that in some possible implementations, the access network device can be a CU node or a DU node or a device including a CU node and a DU node.

[0100] Terminal equipment, also known as user equipment (UE), terminal, mobile station (MS), mobile terminal (MT), customer premise equipment (CPE), etc., is a device with wireless communication capabilities that can provide voice and / or data connectivity services to users. The terminal device may be a handheld terminal, a laptop computer, an RSU (road side unit), a subscriber unit, a cellular phone, a smart phone, a wireless data card, a personal digital assistant (PDA) computer, a tablet computer, a tag, a wireless modem, other processing devices connected to a wireless modem, a handheld device, a laptop computer, a cordless phone or a wireless local loop (WLL) station, a machine type communication (MTC) terminal, a wearable device (such as a smart watch, a smart bracelet, a pedometer, etc.), an in-vehicle device (such as a car, a bicycle, an electric car, an airplane, a ship, a train, a high-speed train, etc.), a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a smart home device (such as a refrigerator, a television, an air conditioner, an electric meter, etc.), an intelligent robot, a workshop device, a wireless terminal in self-driving, a remote medical device, or a similar device. Wireless terminals in smart surgery, smart grids, transportation safety, smart cities, smart homes, aerial devices (such as intelligent robots, hot air balloons, drones, airplanes), and other network-accessible devices can be fixed or mobile. Terminal devices can be deployed on land, indoors or outdoors, handheld, wearable, or in vehicles; on water (such as ships); or in the air (such as aircraft, balloons, and satellites).

[0101] Figure 1 above introduces the overall architecture for communication between the reader and the tag device. Based on the architecture of Figure 1, several specific network architectures are introduced below.

[0102] Please refer to Figure 3A, which is a schematic diagram of another network architecture disclosed in an embodiment of the present application. In the architecture shown in Figure 3A, the access network device can serve as a reader / writer, and the tag device can directly communicate with the access network device in a two-way manner. The tag device can be an ambient IoT device.

[0103] Please refer to Figure 3B again, which is another network architecture diagram disclosed in an embodiment of the present application. In the architecture shown in Figure 3B, the access network device can serve as a reader / writer, and the tag device and the access network device can communicate bidirectionally through an intermediate node. Among them, the intermediate node can be a repeater, an integrated access and backhaul (IAB) node, a UE, a repeater, etc. The tag device can be an environmental Internet of Things device.

[0104] Please refer to Figure 3C again, which is another network architecture diagram disclosed in an embodiment of the present application. In the architecture shown in Figure 3C, the access network device can act as a reader / writer, and the access network device can directly send downlink signals (data / signaling) to the tag device. For uplink communication, the tag device can be completed through an assisting node. For example, the tag device can send data / signaling to the assisting node. After receiving the data / signaling from the tag device, the assisting node can send the data / signaling to the access network device.

[0105] Please refer to Figure 3D again, which is another network architecture diagram disclosed in an embodiment of the present application. In the architecture shown in Figure 3D, the access network device can act as a reader / writer, and the tag device can directly send an uplink signal (data / signaling) to the access network device. For downlink communication, the access network device can be completed through an auxiliary node. For example, the access network device can send data / signaling to the auxiliary node, and after the auxiliary node receives the data / signaling from the access network device, it can send the data / signaling to the tag device. In some possible implementations, the auxiliary node can be a repeater, an IAB node, a UE, a repeater, etc. The tag device can be an environmental Internet of Things device.

[0106] Please refer to Figure 3E, which is another network architecture diagram disclosed in an embodiment of the present application. In the architecture shown in Figure 3E, the terminal device can act as a reader / writer, and the tag device and the terminal device can directly communicate bidirectionally. The tag device can be an environmental IoT device.

[0107] It is understood that the above examples primarily reflect the transmission of data / signaling between the reader and the tag device, and do not include an excitation source (helper). The excitation source can provide an excitation signal to the tag device. In practice, the excitation source may be configured in a variety of ways, and the present embodiment does not limit this. For example, the reader can serve as the excitation source, or the intermediate node can serve as the excitation source, or the helper node can serve as the excitation source.

[0108] Exemplarily, taking the scenario of the auxiliary node as an example, please refer to Figures 3F-3G. As shown in Figures 3F-3G, the auxiliary node can assist the tag device in online communication, the auxiliary node can provide an excitation signal for the tag device, or the access network device can provide an excitation signal for the tag device. Please refer to Figures 3H-3I again. As shown in Figures 3H-3I, the auxiliary node can assist the access network device in offline communication, the auxiliary node can provide an excitation signal for the tag device, or the access network device can provide an excitation signal for the tag device. In some possible implementations, other devices can also provide excitation signals for the tag device, or the access network device and the auxiliary node can jointly provide excitation signals for the tag device, and this embodiment of the present application does not limit this.

[0109] Please refer to Figure 4, which is a schematic diagram of the architecture of an open radio access network disclosed in an embodiment of the present application. As shown in Figure 4, the open radio access network (openRAN, O-RAN) introduces a RAN intelligent controller (RIC), which can implement intelligent management, operation and maintenance. The RIC can include near-real-time RIC (near-RT RIC) and non-real-time RIC (non-RT RIC).

[0110] Near real-time RIC refers to the near real-time part, which is mainly responsible for processing services with low latency requirements, such as services of less than 1 second (50ms-200ms), such as radio resource management, handover decision-making, connection control, load balancing, etc. For example, the near real-time RIC can obtain information (such as network side information, terminal side information, etc.) from RAN devices (such as CU, CU-CP (control plane), CU-UP (user plane), DU, RU, etc.), terminal devices, non-real-time RIC and other devices, and then train the AI ​​model based on the obtained information, or input the obtained information into the trained AI model to obtain inference results, which can be network parameters, such as RAN parameters (priority parameters, handover parameters, etc.). In this embodiment of the present application, the near real-time RIC can determine relevant RFID parameters such as Q value, number of frequency domain resources, modulus parameters, etc. based on the relevant data of RFID to reduce the probability of collision between tag devices. Optionally, the near real-time RIC can send the inference results to the RAN device and / or terminal device. Optionally, the inference results can be exchanged between the CU and DU, and between the DU and RU. For example, near real-time RIC can send the inference results to DU, and DU can send the inference results to RU in real time.

[0111] Non-real-time RIC refers to the non-real-time part, which is mainly responsible for processing services with relatively large latency requirements, such as services greater than 1 second, such as data analysis and artificial intelligence (AI) model training. For example, the non-real-time RIC can obtain information (such as network-side information, terminal-side information, etc.) from RAN devices (such as CU, CU-CP, CU-UP, DU, RU, etc.), terminal devices, near-real-time RIC, and other devices, and then perform AI model training based on the obtained information, or input the obtained information into a trained AI model to obtain inference results. The inference results can be network parameters, such as RAN parameters (priority parameters, handover parameters), etc. The non-real-time RIC can send the inference results to the RAN device and / or terminal. In an embodiment of the present application, the non-real-time RIC can determine relevant RFID parameters such as Q value, number of frequency domain resources, modulus parameters, etc. based on RFID-related data to reduce the probability of collision between tag devices. Optionally, the non-real-time RIC can send the inference results to the RAN device, terminal, near-real-time RIC, etc. Optionally, the inference results can be exchanged between the CU and DU, and between the DU and RU. For example, the non-real-time RIC can deliver the inference results to the DU, which then sends them to the RU.

[0112] In one possible implementation, the near real-time RIC and the non-real-time RIC can each be set up as a separate network element. In another possible implementation, the near real-time RIC and the non-real-time RIC can also be part of other devices. For example, the near real-time RIC can be set up in the RAN equipment (for example, in the CU, DU), and the non-real-time RIC can be set up in the OAM (operation administration and maintenance), cloud server, core network equipment, or other network equipment. For more detailed information about the open wireless access network (such as the interface), please refer to the description in the relevant standards and will not be repeated here.

[0113] It should be noted that the architectures of Figures 1 to 4 are merely exemplary and do not constitute a limitation. For example, in some possible implementations, the network architecture may further include core network devices, such as AMF (access and mobility management function).

[0114] In the embodiment of the present application, the term "wireless communication" can also be simply referred to as "communication", and the term "communication" can also be described as "data transmission", "information transmission" or "transmission".

[0115] It should be understood that the technical solutions provided in the embodiments of the present application can be applied to communication systems of various radio access technologies (RATs), such as: fifth generation (5G) systems, transition systems between LTE communication systems and 5G communication systems (the transition systems may also be referred to as 4.5G communication systems), networks integrating multiple systems, Internet of Things systems, universal mobile telecommunications systems (UMTS) systems, wireless local area networks (WLANs), etc.; and of course, future communication systems such as sixth generation (6G) or even seventh generation (7G) systems may also be used. For example, the communication between the reader and the tag device may adopt 5G new radio (NR) technology, 5G sidelink technology, or other communication technologies, which are not limited in the embodiments of the present application.

[0116] It should be noted that the system architecture, network architecture, and business scenarios (or application scenarios) described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of communication network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0117] In order to better understand the embodiments of the present application, the following briefly introduces the relevant terms or related technologies involved in the present application.

[0118] 1. Environmental Internet of Things.

[0119] With the development of communication technology and Internet of Things technology, in order to achieve larger-scale access of IoT devices, lower deployment costs, and meet more application scenarios, the 3rd Generation Partnership Project (3GPP) defined the ambient internet of things (A-IoT) technology.

[0120] The Ambient IoT can be implemented based on cellular network infrastructure (such as access network equipment and UE), and can include readers and A-IoT end devices. Readers can be network devices in the cellular network, such as base stations. A-IoT end devices can be terminals in the cellular network, such as extremely low-power, low-complexity IoT terminals.

[0121] A-IoT terminal devices can be divided into three categories, namely device A, device B and device C. Among them, device A has no energy storage capability and cannot independently generate / amplify signals, for example, for backscattering transmission. Device B has energy storage capability and cannot independently generate signals (such as for backscattering transmission), but can use stored energy to amplify reflected signals. Device C has energy storage capability and can independently generate signals, for example, it can use radio frequency components for transmission. In some embodiments, device A can also be called a passive A-IoT terminal, device B can also be called a semi-passive A-IoT terminal, and device C can also be called an active A-IoT terminal.

[0122] The main services of the Environmental Internet of Things may include inventory, positioning, sensor reporting, commands, etc. The command service may be a service that implements a write process or a lock process. Typical application scenarios of the Environmental Internet of Things may include logistics, warehousing, industrial manufacturing, identity recognition, environmental monitoring, etc. For example, the inventory service generally refers to the use of a reader / writer (such as a base station / terminal) to access the A-IoT terminal within the coverage area. The A-IoT terminal that successfully accesses the service needs to send its own identification (such as EPC in RFID) to the reader / writer. Positioning generally refers to the use of some positioning signals to locate the position of the A-IoT terminal. The sensor reporting service generally refers to the A-IoT terminal reporting sensor data to the reader / writer (such as a base station / terminal), such as temperature data, humidity data, etc. Commands generally refer to some operation instructions, such as Write and Lock. The Write process is generally that the reader sends a downlink instruction and data, instructing the A-IoT terminal to write the data into its own storage area (memory). The Lock process is generally that the reader sends a downlink instruction, instructing the A-IoT terminal to lock the data at a specified address in the storage area, making the data at the specified address unchangeable and unreadable.

[0123] It should be noted that the embodiments of the present application are mainly described using inventory as an example, but the corresponding processing flow can also be an access flow, an identification flow, or other services, such as commands, sensing, positioning, etc., which are not limited here.

[0124] 2. RFID process.

[0125] The reader can perform RFID / inventory on the tag device through signaling such as query (Query), repeated query (QueryRep), etc. The overall process of RFID is introduced below. Please refer to Figure 5, which is a schematic diagram of the process of RFID disclosed in the embodiment of this application.

[0126] As shown in FIG5 , the processing flow may include but is not limited to the following steps:

[0127] 501. The reader sends a select signaling.

[0128] Among them, the Select signaling may include indication information for filtering tags, and the indication information may be used to filter / indicate certain tags. For example, the indication information may indicate a specific identifier (ID) or indicate that a specific part is included in the tag ID (such as a tag whose first 4 bits of the EPC of the tag are 0011), and one or more tags may be selected accordingly. Exemplarily, the indication information may include parameters such as MemBank (memorybank), pointer (Pointer), length (Length) and mask (mask). MemBank and pointer may indicate the location of the memory to be compared, and length and mask may indicate specific comparison data. Among them, the ID of the tag may be the EPC in the tag, or it may be the tag identifier (TID), or it may be other information that can identify the tag, which is not limited in the embodiments of the present application. In some embodiments, the Select signaling may also be referred to as paging signaling.

[0129] Select signaling can also be used to change the status of one or more selected tags and / or the status of one or more unselected tags, such as the flag bit status corresponding to a session. When it is necessary to change the flag bit status of a tag based on Select signaling, the Select signaling can carry relevant information to instruct the corresponding tag to be modified. Exemplarily, the Select signaling may include information such as inventorySession (or target), action, etc. InventorySession can indicate the session that needs to be modified, and action can indicate how to modify it specifically. For example, inventorySession can be S0, and action can be "000". "000" indicates that the matching tag device needs to set the flag position of S0 to A, and the unmatched tag device needs to set the flag position of S0 to B.

[0130] It is understandable that the Select signaling is a public signaling, and therefore, all tags within the communication range of the reader (ie, the range within which the reader can take inventory of tags) can receive the Select signaling sent by the reader.

[0131] 502. The tag sets the flag based on Select signaling.

[0132] After receiving a Select signaling from the reader, the tag can first determine whether it meets or matches the filtering criteria indicated in the Select signaling (e.g., the first four bits of the tag's EPC are 0011). It can then proceed accordingly based on the determination result. For example, assuming the inventorySession is S0 and the action is "000," if the tag determines that it does not meet the filtering criteria (e.g., the first four bits of its EPC are 0101), the tag can set the flag bit in S0 to B. If the tag determines that it does meet the filtering criteria, the tag can set the flag bit in S0 to A. In some cases, Select signaling is optional for a round of identification / inventory processing. Therefore, there may be no Select signaling before a round of inventory processing (e.g., multiple Query-initiated inventory processes may follow a Select signaling), or there may be Select signaling before each inventory process. If there is no Select signaling before a round of inventory processing, the reader can directly send a Query signaling to begin the inventory process.

[0133] 503. The reader sends a query signaling, which includes a session, a flag bit, and a Q value.

[0134] After the reader sends the Select signaling, it can continue to send Query signaling, which can initiate a round or an inventory / identification process. Among them, a round of inventory process can be understood as the process of identifying one or more tags. A round of inventory process can start with a Query signaling, which can be followed by N repeated query (QueryRep) signaling, where N is an integer greater than or equal to 0. The end mark of a round of inventory can be the appearance of the next Query signaling, or no tag has fed back RN16 signaling after multiple QueryRep signaling, or 2 Q -1 QueryRep signaling.

[0135] Specifically, the query signaling may include indication information for filtering tags, and the indication information may be used to indicate that a certain category of tags participate in this round of inventory process. For example, the indication information may include session and flag bit, the session may be S0, and the flag bit may be A. In this case, it may indicate that tags with S0 as A participate in this round of inventory process. The query signaling may also indicate the value range of the counter (Counter), such as the query signaling may indicate a Q value, and the value range corresponding to the Q value is [0, 2 Q -1].

[0136] The Query signaling may be a public signaling, and therefore all tags within the communication range of the reader can receive the Query signaling sent by the reader.

[0137] It should be noted that the Query signaling may also include indication information for indicating transmission parameters, such as uplink transmission rate, bit rate, bandwidth, etc. Accordingly, after receiving the Query signaling, the tag may transmit according to the uplink transmission parameters indicated in the Query signaling when transmission is required.

[0138] 504. When the session and flag bits match, the tag generates a counter based on the Q value.

[0139] After the tag receives the Query signaling, it can first determine whether it meets or matches the filtering conditions indicated by the reader in the Query signaling (such as S0 is A). If the tag determines that it does not meet the filtering conditions, the tag does not need to initialize its own counter according to the Query signaling, and does not need to participate in this round of inventory process, that is, it does not need to respond to subsequent QueryRep and other signals sent by the reader. If the tag determines that it meets the filtering conditions, the tag can determine the value range of the counter according to the indication in the Query signaling, and then randomly select a value within the range to initialize its own Counter (such as if the Q value is 2, the tag can arbitrarily select a value in [0, 3] to initialize its own counter).

[0140] When the tag's counter reaches 0, the tag can send a random number (RN) response (such as RN16, RN8, etc.) signaling to the reader. The RN16 signaling can carry a 16-bit random number, which can be used as the tag's temporary ID. RN16 signaling can also be understood as random access request signaling or inventory request signaling, which can be used by the tag to request random access / inventory from the reader.

[0141] 505. When the tag's Counter is 0, the tag sends RN16 signaling to the reader.

[0142] For example, if the tag initializes its own counter to a value of 0 after receiving the Query signaling from the reader, the tag may send an RN16 signaling to the reader.

[0143] 506. The reader sends a QueryRep signaling.

[0144] It is understandable that after the reader sends a query signaling (such as Query signaling, QueryRep signaling, etc.), there are many possible situations. In one case, the counter value of multiple tags may be 0 at the same time. At this time, these multiple tags can all feedback RN16 signaling to the reader. Accordingly, the reader can receive RN16 signaling from multiple tags. If the multiple tags use the same resources, conflicts will occur between the multiple RN16 signaling, that is, conflicts (collisions) will occur between the tags, and the reader may not be able to handle them correctly, as shown in Figure 5. In the case of multiple tags colliding, the reader can generally directly perform a new query (such as sending a QueryRep signaling), skip these colliding tags, and directly proceed to the subsequent inventory process, and wait until the next round of inventory to inventory these colliding tags.

[0145] In another case, due to some reasons (for example, after the reader sends Query or QueryRep signaling, no tag counter value is 0, so no tag responds), the reader may not receive RN16 signaling from the tag after sending the query signaling. Therefore, when the reader does not receive RN16 signaling from the tag, it can directly proceed with the subsequent inventory process, such as sending QueryRep.

[0146] In another case, the reader may receive RN16 signaling (single tag response) from a single tag, and then the reader may respond to the single tag by sending an acknowledgment (ACK) signaling, as shown in steps 508-509 below. The ACK signaling may include the 16-bit random number previously fed back by the tag.

[0147] It should be understood that QueryRep signaling is also public signaling, so all tags within the communication range of the reader can receive the QueryRep signaling sent by the reader.

[0148] 507. The tag updates the Counter based on the QueryRep signaling.

[0149] After the tag receives the QueryRep signaling from the reader, it can update the Counter and reduce the current Counter by 1.

[0150] 508. When the tag's Counter is 0, the tag sends RN16 signaling to the reader.

[0151] After the tag updates the Counter, if the Counter is 0, the tag can send RN16 signaling to the reader.

[0152] 509. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the tag.

[0153] When there is no tag collision (e.g., a single tag feeds back RN16), after receiving the RN16 signaling from the tag, the reader can send an ACK signaling, which can include the 16-bit random number carried in the RN16 signaling. For example, the ACK signaling can be used to indicate successful contention resolution.

[0154] 510. The tag sends EPC signaling.

[0155] After receiving the ACK signaling, the tag can determine whether the 16-bit random number included in the ACK signaling matches. If it matches (e.g., it is the same as the 16-bit random number it sent), the tag can send EPC signaling. If it does not match, the tag may not respond and may not send EPC signaling. For example, the EPC signaling may include the tag ID, such as EPC, TID, etc.

[0156] 511. The reader sends a QueryRep signaling.

[0157] After the reader correctly receives the EPC signaling from the tag, it can send the next query signaling, such as QueryRep signaling. In some possible implementations, after the reader correctly receives the EPC signaling from the tag, it can also perform unicast communication with the tag. For example, the reader can send a random number request (request random number, Req_RN). Req_RN can be used to request the tag to give another RN16. Req_RN can also include the RN16 previously fed back by the tag. After the reader receives the new RN16 corresponding to Req_RN, the reader can send a read command (Read) to the tag based on the new RN16. The read command can indicate the content that needs to be read (such as the content of a certain storage area of ​​the tag). When the tag receives a read command from the reader, the tag can send a read response command (Read Reply) to the reader to feed back the content that the reader needs to read. For another example, the reader / writer can send a write command to the tag based on the new RN16 to write relevant data to the tag. For another example, the reader / writer can send a lock command to the tag based on the new RN16 to lock the data at the specified address of the relevant storage area, so that the data at the specified address cannot be changed or read.

[0158] After the tag sends EPC signaling to the reader, if the tag receives QueryRep signaling from the reader, the tag can determine that its data transmission (referred to as data transmission) has been successful, that is, the reader correctly receives the EPC signaling sent by itself, and the tag can change its own flag bit, such as flipping S0 from A to B. After that, the tag does not need to participate in the subsequent inventory process. In the embodiment of the present application, access can be understood as the process of the tag sending RN (such as RN16) and receiving ACK, or it can be understood as the process of the tag sending RN (such as RN16), receiving ACK and then sending uplink data (such as EPC) (based on contention access); data transmission can be understood as directly sending uplink data such as EPC (contention-free solution).

[0159] In some cases, the reader may not correctly receive EPC signaling from the tag. For example, if multiple tags use the same resource to send back EPC signaling, causing EPC signaling conflicts, the reader can send a negative acknowledgment (NAK) signaling to the tag, indicating that the data transmission failed. When the tag receives the NAK signaling from the reader, it can determine that its data transmission failed and may not change its flag bit, waiting for the next inventory. It should be understood that the inventory process shown in Figure 5 is only illustrative and does not constitute a limitation.

[0160] For example, a round of inventory process can be divided into multiple time slots (slots) / access time slots based on Query signaling and QueryRep signaling. As shown in FIG6 , the period between the Query signaling and the first QueryRep signaling can be used as the first time slot, i.e., slot 0; the period between the first QueryRep signaling and the second QueryRep signaling can be used as the second time slot, i.e., slot 1; the period between the second QueryRep signaling and the third QueryRep signaling can be used as the third time slot, i.e., slot 2; similarly, the period between the Mth QueryRep signaling and the M+1th QueryRep signaling can be used as the M+1th time slot, where M is an integer greater than or equal to 3. In other words, the above-mentioned tag initialization counter can also be understood as the tag selecting an (access) time slot.

[0161] In the above inventory process, the tag is a counter randomly initialized based on the Q value, and then access, data transmission, etc. are performed based on the counter. In the event of a collision, the colliding tag generally needs to wait for the next round of inventory process to access or transmit data again, and the access or data transmission efficiency is low. In order to solve the above problem, an embodiment of the present application proposes a communication method. Specifically, for tags that collide with a certain resource, the reader can allocate resources for the tags that access or transmit data on the resource, and instruct the tags that access or transmit data on the resource to access or transmit data again, without having to wait for the next round of inventory process to access or transmit data, so as to improve the access or data transmission efficiency. Moreover, in an embodiment of the present application, resources can be allocated to tags in a targeted manner (such as tags selecting resources based on identifier modulo), so that different tags try to use different resources for access or data transmission, thereby reducing the probability of collision or avoiding collision, and further improving the access or data transmission efficiency.

[0162] The technical solutions provided in the embodiments of the present application are described in detail below.

[0163] Based on the above system architecture, please refer to Figure 7, which is a flow chart of a communication method disclosed in an embodiment of the present application. Figure 7 is illustrated with a first device and a second device, and the first device and the second device can communicate directly or indirectly. For example, the first device can be a reader / writer, such as a base station, UE, etc., and the second device can be a tag within the coverage range corresponding to the reader / writer, or a tag within the coverage range corresponding to the intermediate node, or a tag within the coverage range corresponding to the auxiliary node, such as an environmental Internet of Things device. As shown in Figure 7, the method may include but is not limited to the following steps:

[0164] 701. The first device sends fifth information, where the fifth information is used to instruct the second device to send a first message in a first resource and to instruct the third device to send a sixth message in a third resource, where the first resource is different from the third resource.

[0165] In an embodiment of the present application, when a first device performs an inventory, different resources can be allocated to multiple terminal devices to be inventoried to avoid collisions when these multiple terminal devices send uplink messages. For example, when the first device performs an inventory, the first device can send fifth information. The fifth information can be used to instruct the second device to send a first message using a first resource and to instruct the third device to send a sixth message using a third resource, where the first resource is different from the third resource. In an embodiment of the present application, the first resource can include time domain resources, frequency domain resources, and / or code domain resources.

[0166] Among them, the time domain resource can be a time slot, or a subframe (sub-time slot), or a timing (such as an access timing or a transmission timing), or an opportunity (such as an access opportunity or a transmission opportunity), etc. Each time domain resource may not be of fixed length. For example, the time between adjacent QueyReps can be regarded as a time slot / opportunity. Adjacent means that the terminal device does not receive other QueyReps between two QueyReps received, or the reader does not send QueyReps again between two QueyReps sent. For another example, the time between adjacent SubQueyReps can be regarded as a sub-time slot / opportunity. Adjacent means that the terminal device does not receive other SubQueyReps between two SubQueyReps received, or the reader does not send SubQueyReps again between two SubQueyReps sent. Exemplarily, in an embodiment of the present application, the reader indicates that the time domain resource may be the number of the time domain resource, such as indicating the 10th time slot / opportunity. In this case, it can be indicated that the corresponding terminal device can respond after receiving the 9th QueyRep, or the terminal device can initialize the Counter to 9. It can be understood that the sub-time slot can be understood as a time slot between which multiple time slots can be divided by multiple sub-repeated query (SubQueryRep) signaling, and these multiple time slots can be sub-time slots. Exemplarily, QueryRep and SubQueryRep can also be understood as two different levels, and SubQueryRep can be the next level of QueryRep, such as QueryRep is level 1 (level 1) and SubQueryRep is level 2 (level 2). Based on this, in the time domain, under the above-mentioned sub-time slots, time slots can also be divided, that is, sub-time slots under sub-time slots, which are not limited in this embodiment of the present application. Code domain resources can be different sequences, such as preamble sequences. In the embodiment of the present application, when the fifth information indicates the first resource, it can indicate a specific sequence, or it can indicate the number or index of the sequence. The sequence or sequence number can be specified by the protocol or indicated by downlink signaling. Frequency domain resources can be different frequency shift positions, frequency positions, subcarriers, frequency point information, or transmission parameters. In an embodiment of the present application, the fifth information indicates a frequency domain resource in a variety of ways, which are introduced below. Exemplarily, the fifth information may indicate the frequency information / frequency domain position / frequency point position of the frequency domain resource corresponding to the first resource, and. Again exemplarily, the fifth information may indicate the frequency shift between the frequency domain resource corresponding to the first resource and the default frequency domain resource (or pre-configured frequency domain resource). Again exemplarily, the fifth information may include a transmission parameter corresponding to the first resource, and the frequency domain resource corresponding to the first resource may be indicated by the transmission parameter corresponding to the first resource.For example, the transmission parameters corresponding to the first resource may include one or more of a time parameter (denoted as Tpri), a code length parameter (denoted as M), and a scaling parameter (denoted as Rchip), and each transmission parameter value may correspond to a frequency domain resource. It should be noted that in the embodiment of the present application, the resources allocated by the reader to the terminal device are not specifically limited, and may include time domain resources and / or frequency domain resources and / or code domain resources. For example, the above-mentioned first resource and second resource may include time domain resources and / or frequency domain resources and / or code domain resources.

[0167] Optionally, the fifth information may implicitly indicate the resources corresponding to each terminal device, or may explicitly indicate the resources corresponding to each terminal device. For example, the fifth information may include the identifiers of multiple terminal devices and the resource indication associated with each identifier, which is equivalent to directly indicating the resources corresponding to each terminal device. For another example, the fifth information may include the identifiers of multiple terminal devices, and the identifiers of the multiple terminal devices exist in a sequence (such as a list of identifiers of a terminal device). Afterwards, the multiple terminal devices can select corresponding resources from the multiple resources in sequence. These multiple resources may be pre-configured, may be specified by the protocol, or may be configured by the first device through a downlink message (such as Paging).

[0168] It is understandable that the fifth information can be carried in a downlink message, and accordingly, all terminal devices (including the second device and the third device) within the coverage range of the first device can receive the fifth information. Exemplarily, the fifth information can be carried in paging signaling (Paging / Select), or the fifth information can be carried in a separate resource allocation signaling, which is not limited in this embodiment of the present application.

[0169] It should be noted that step 701 is optional, and the first device may also allocate resources to the terminal device in other ways. For example, the first device may indicate multiple resources, and the terminal device may randomly select a resource for sending subsequent uplink messages.

[0170] Optionally, during the inventory process, a terminal device (such as a second device) may discard downlink messages (signaling) that it is not currently listening to. Specifically, during the inventory process, with respect to downlink messages, some downlink messages may be sent by the first device to a specific terminal device for parsing (or reading), but may also be received by other terminal devices, such as ACK signaling, read commands, write commands, lock commands, downlink data, etc., wherein the parsing (or reading) refers to the need to read and process all fields carried in the downlink message, for example, for Media Access Control (MAC) signaling, the MAC layer needs to process each field carried by the MAC message (such as MAC header, MAC CE (control element), MAC SDU (service data unit)), etc.). Therefore, for a downlink message, if the downlink message is not the downlink message that the second device is currently listening to or needs to parse (or read), that is, the downlink message is not a downlink message sent to the second device, the second device may not respond to the downlink message and may discard the downlink message. For example, assuming that the time domain resource used by the second device is slot 5, then before slot 5, the second device can only listen to / respond to QueryRep signaling. For SubQueryRep signaling, ACK signaling, read commands, write commands, lock commands, downlink data, etc. in all time slots before slot 5 (slot 0-slot 4), the second device does not need to respond and can discard them. For another example, assuming that the time domain resource used by the second device is subslot (sub-time slot) 3 corresponding to slot5, then before slot5, the second device can only listen / respond to QueryRep signaling, and in slot5 and before subslot3, the second device can only listen / respond to SubQueryRep signaling. For the SubQueryRep signaling, ACK signaling, read commands, write commands, lock commands, downlink data, etc. of all time slots (slot0-slot4) before slot5, and the ACK signaling, read commands, write commands, lock commands, downlink data, etc. of all sub-time slots (subslot0-subslot3) before subslot3 in slot5, the second device does not need to respond and can discard them.

[0171] Optionally, in an embodiment of the present application, each downlink message (signaling) may include corresponding identification information to indicate the corresponding downlink message type. Exemplarily, each different downlink message (signaling) downlink message may be associated with different identification information 1 (such as a field, cell, or domain). Exemplarily, in one implementation, the identification information 1 included in the downlink message (signaling) may depend on the signaling type to indicate the corresponding downlink message type, such as LCID (logical channel ID, logical channel identifier), or signaling type identifier, or different downlink messages may be associated with different identification information. For example, the identification information corresponding to the paging signaling may be 1111, the identification information corresponding to the ACK signaling may be 1000, and the identification information corresponding to the QueryRep signaling may be 1001. When receiving a downlink message, the terminal device may determine the downlink message type based only on the identification information 1 in the downlink message. If the downlink message is not a downlink message that currently requires a response, the downlink message may be discarded (or not responded to). For another example, during the random access process, if the terminal device hears an ACK sent to other terminal devices while listening to QueryRep, it can discard the ACK message when it confirms that the LCID or identification information is not QueryRep, and there is no need to parse (or read) other fields of the message to reduce the power consumption of the terminal device.

[0172] In another implementation, the identification information 1 included in the downlink message (signaling) may include a group identifier (such as a group number) or a process identifier (such as a process number) associated with the downlink signaling, to indicate which groups or processes the terminal devices in need of responding to the corresponding downlink message. For example, during a random access process, a terminal device in group 1 receives a QueryRep or Query message carrying a group 2 identifier and can determine the group number associated with the downlink message based solely on identification information 1. If the downlink message is not associated with the group to which the terminal device belongs, the downlink message can be discarded without parsing (or reading) other fields of the message, thereby reducing power consumption of the terminal device.

[0173] Optionally, when the second device receives Paging or Query signaling, if the second device meets the response conditions of the Paging or Query signaling, the Paging or Query signaling may not be discarded even if the second device is currently listening for ACK signaling or QueryRep signaling. The response conditions may be screening conditions, such as mask information, group identifier, device identifier, session and flag bits, etc. For example, assuming that the EPC of the second device is "001101101011", and the response condition of the Paging or Query signaling is "the first 4 bits of the EPC are 0011", after receiving the Paging or Query signaling, the second device can determine that it meets the response conditions of the Paging or Query signaling and can respond.

[0174] 702. The second device sends a first message through the first resource.

[0175] In the case where the first device sends the fifth information, after the second device receives the fifth information sent by the first device, it can be determined that the first message can be sent through the first resource. Exemplarily, the first message can be RN (such as RN16, RN8, etc.) signaling, or EPC signaling, etc., or can be other uplink signaling or data, which is not limited in this embodiment of the present application. In the embodiment of the present application, there is no limit on the number of bits of the random number sent by the terminal device, which can be 8 bits (RN8), 16 bits (RN16), or other bits. RN can also be called a random access ID (identifier), or other names. RN is mainly used for contention resolution in the random access process and to distinguish identification information of different devices, which is equivalent to a temporary identification of the terminal device.

[0176] It should be understood that in other possible implementations of the present application, the second device may determine the first resource by other means and then send the first message through the first resource. For example, the first device may send a query signaling, and the query signaling may configure multiple resources (such as indicating multiple time domain resources through a Q value), where the multiple resources include the first resource. Thereafter, the second device, upon determining that the filtering condition indicated by the first device in the query signaling (such as S0 is A) is matched, may randomly select a resource (such as the first resource) from the multiple resources for sending the uplink message.

[0177] It should be noted that, in the embodiment of the present application, paging signaling (Paging) may also be referred to as selection signaling, initial (DL / RD) trigger message, initial (DL / RD) trigger indication, initial (DL / RD) trigger, trigger message, downlink trigger (message) or paging-like message. Exemplarily, Paging can be used to instruct the AIOT device to access the reader / writer. For example, when the reader / writer is a base station / access network device, Paging can be used to instruct the AIOT device to access the network. For another example, when the reader / writer is a terminal device, Paging can be used to instruct the AIOT device to access the terminal device. Optionally, the AIOT device can also access the network through the terminal device. As another example, Paging can also be used to trigger / instruct the corresponding device to send uplink data, or to trigger / instruct / request the corresponding device to perform the first service. The first service may include at least one of the following: a paging service, an inventory service, a command service (such as read, write, deactivate, lock, etc.), a positioning service, and a sensing service. For example, Paging may be triggered by a core network element, such as an AMF, an ambient IoT management function (AIoTMF), or an ambient IoT function (AIoTF).

[0178] Query signaling (Query) can also be called access round trigger / indication. Query can be used to trigger / indicate at least one access opportunity, such as directly or indirectly indicating the total number of access opportunities, or to trigger the first access opportunity.

[0179] Repeated query signaling (QueryRep) can also be called a (next) access occasion trigger / indication. QueryRep can be used to trigger / indicate the next access opportunity, or can be understood as indicating the boundary (start or end) associated with an access opportunity. Access opportunities can also be called access timings, access slots, etc. Each access opportunity allows a terminal device (such as an AIoT device) to send an access request, and / or resolve contention, and / or transmit data.

[0180] Sub-repeated query signaling (SubQueryRep) can also be called an access sub-occasion indication / trigger. Exemplarily, each access opportunity triggered / indicated by a Query or QueryRep may include one or more sub-access opportunities. SubQueryRep can be used to trigger / indicate the next sub-access opportunity, or can be understood as indicating / associated with the boundary (start or end) of a sub-access opportunity. A sub-access opportunity can also be called a sub-access opportunity, a sub-access time slot, etc. Each sub-access opportunity can allow a terminal device to send an access request, and / or perform contention resolution, and / or data transmission.

[0181] The ACK signaling (ACK) may also be called an access ID response. The ACK may be used to indicate successful contention resolution and may carry a contention resolution identifier, such as a random number sent by the terminal device.

[0182] Electronic Product Code (EPC) signaling can also be called uplink data (UL data) or device ID. EPC / uplink data / device ID is primarily service-related data. For example, it can be a device ID in an inventory service, sensor data in a sensor service, a read command can be the data in the storage area being read, and a write command can be the response to a write command. In short, in the embodiments of the present application, the names of the above-mentioned signaling / messages / data are not specifically limited, as long as they have the relevant functions.

[0183] 703. The first device sends first information and second information, where the first information is used to indicate that the terminal device that sent the first message on the first resource sends the second message on the second resource, and the second information is used to indicate the first resource.

[0184] In an embodiment of the present application, a first device may instruct a terminal device that previously sent an uplink message on a certain resource to send an uplink message again on a new resource. For example, the first device may send first information and second information, where the first information may be used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information may be used to instruct the first resource.

[0185] Among them, there are multiple situations for sending the first information and the second information. One situation is that the first information and the second information are two pieces of information, but the first information is associated with the second information. For example, the first information can be used to indicate that the terminal device that sends the first message at the resource indicated by the second information sends the second message at the second resource, and the second information can indicate the first resource. In another case, the second information implicitly indicates the first information or the first information implicitly indicates the second information. For example, a new field can be added to the QueryRep signaling, which can be a resource indication (such as the second information), and the field is used to indicate that the terminal device that sends the first message at the resource indicated by the resource indication sends the second message at the second resource. That is to say, in this case, it is equivalent to sending only one piece of information, such as the second information, or it can be understood that the first information and the second information are one piece of information.

[0186] In some possible implementations, the first device may also send a third message, and the third message may be used to indicate that the second message is a random access message or uplink data. That is, the first device may indicate which type of uplink message the terminal device corresponding to the second message sends by sending the third message, so as to flexibly meet the needs of various scenarios. Exemplarily, the third indication information may be multiple bits, and there may be multiple possible values, each value may indicate an uplink message. For example, in the case of 2 bits, it may include four cases: 00, 01, 10, and 11. 00 may indicate RN16 signaling, 01 may indicate EPC signaling, 10 may indicate sensor data associated with the terminal device, and 11 may indicate other uplink messages. For example, if a terminal device that previously reported sensor data through the first resource needs to send the current sensor data again, the first device may indicate that the second message is sensor data through the third message (10). It should be understood that the terminal device corresponding to the second information is the terminal device that sends the first message on the first resource indicated by the second information. In some embodiments, the third information may indicate whether to send uplink / DR data directly. Exemplarily, the third indication information can be 1 bit, where bit 0 represents directly sending uplink / DR data, that is, contention-free resolution, or skipping contention resolution; and bit 1 represents not directly sending uplink / DR data, that is, it is necessary to send RN signaling first for contention resolution.

[0187] In some possible implementations, the first device may further send fourth information, which may be used to indicate a second resource. The second resource may be one resource or multiple resources. Specifically, since the terminal device that sends the first message on the first resource may be one (such as in the case of a single terminal device response) or multiple (such as in the case of a multi-tag response), the number of resources indicated by the fourth information may be different for different situations. For example, if the first device can determine that the terminal device that sends the first message on the first resource is one (such as the RN16 received on the first resource is non-collision-free), the second resource indicated by the fourth information may be one resource. If the first device can determine that the terminal device that sends the first message on the first resource is multiple (such as the RN16 received on the first resource is conflicting), the second resource indicated by the fourth information may be multiple resources. If the first device cannot determine whether the terminal device that sends the first message on the first resource is one or multiple, the second resource indicated by the fourth information may be multiple resources. It should be understood that the above-mentioned example of whether the second resource is one resource or multiple resources is merely an illustrative description and does not constitute a limitation. For example, when the first device cannot determine whether the terminal device that sends the first message on the first resource is one or multiple, the second resource indicated by the fourth information may be one resource. When a collision occurs later, multiple resources may be re-indicated.

[0188] In the embodiment of the present application, the second resource indicated by the fourth information is not limited. However, it should be understood that the multiple resources indicated by the fourth information may be different from the resources already allocated through the Query signaling, that is, different from the resources used by the terminal device that has not yet sent RN16, so that collisions can be avoided.

[0189] Normally, the waiting delays between different uplink and downlink signaling between the terminal device and the reader may be different. For example, the time interval between the reader sending QueryRep and receiving the corresponding RN is T1, and the time interval between the reader receiving RN and sending ACK is T2. T2 is much larger than T1. In this case, the time between the reader receiving RN and sending ACK is sufficient to complete the sending of QueryRep and the receiving of the corresponding RN again. Therefore, in some possible implementations, in order to improve access efficiency, the first device can set multiple processes (such as process 1 and process 2), and each process can be associated with multiple terminal devices. Assume that when the first device receives RN16 sent by a terminal device associated with process 1, the first device can send QueryRep associated with process 2, and can receive RN16 returned by the corresponding terminal device. After that, process 1 can send the corresponding ACK again. In this way, the utilization of time domain resources can be improved. When multiple processes are set up, the downlink message corresponding to each process can carry the corresponding process identifier, and the terminal device that needs to be inventoried can be associated with one of the multiple processes. For example, multiple process identifiers can be indicated in the paging signaling, and the corresponding terminal device can randomly select a process identifier, and then can only respond to the downlink message corresponding to the selected process identifier.

[0190] Exemplarily, the multiple processes configured by a first device may include a first process. In this case, to instruct a terminal device associated with the first process that sends a first message on a first resource to send a second message on a second resource, first information may be associated with the first process. For example, the first information may be included in a downlink message, which may also include an identifier of the first process. A second device may be associated with the first process, where the second device may be the terminal device that sends the first message on the first resource.

[0191] In some possible implementations, at least two of the first information, the second information, the third information and the fourth information may be carried in the same message, such as carried in the third message, or the fourth message, or the fifth message. The third message may be used to trigger random access of one or more terminal devices, such as a paging message. The fourth message may be used to trigger a terminal device to perform random access to the next time slot, such as Query signaling. The fifth message may be used to trigger a terminal device to perform random access to the next sub-time slot, such as QueryRep signaling. That is, the existing downlink message may be reused to trigger a terminal device that sends a first message on the first resource to send a second message on the second resource. It should be understood that in addition to the above three downlink messages, it may also be carried in other downlink messages, which is not limited in the embodiments of the present application. For example, a new downlink message may also be set, such as query target resource signaling (QueryTargetOccasion), which may be used specifically to instruct a terminal device that sends a first message on a certain resource to send a second message on the second resource.

[0192] 704. The second device sends a second message through the second resource.

[0193] After receiving the first and second messages from the first device, the second device can determine that it has previously sent the first message using the first resource indicated by the second message. Subsequently, the second device can send the second message using the second resource. Accordingly, the first device can receive the second message using the second resource. It should be understood that some terminal devices may have previously sent the first message, but using a different resource than the first resource. In this case, these terminal devices do not need to perform corresponding processing upon receiving the first and second messages.

[0194] In some embodiments, the second device may also receive third information from the first device, where the third information may be used to indicate that the second message is a random access message or uplink data. Thereafter, the second device may send a corresponding uplink message based on the indication of the third information.

[0195] In some embodiments, the second device may also receive fourth information from the first device, where the fourth information may be used to indicate a second resource. The second device may then send a second message based on the second resource indicated by the fourth information. If the second resource indicated by the fourth information includes multiple resources, the second device sending the second message via the second resource may be sending the second message via one of the second resources. For example, the second device may randomly select a resource from the multiple resources and then send the second message via the randomly selected resource.

[0196] It should be noted that steps 701-704 can all occur within a single inventory round. That is, instructing a terminal device that sent a first message on a first resource to send a second message on a second resource can be instructing a terminal device that sent a first message on a first resource to send a second message on a second resource within the current inventory round. It should also be noted that in this embodiment of the present application, regardless of whether the second device has successfully completed an inventory, or whether the flag bit has a value of A or B, within a single inventory round, the first message and the second message can be used to trigger the second device to re-access or transmit data.

[0197] In the above processing flow, the terminal device that sent the first message on the first resource can be triggered by the first information and the second information to send the second message on the second resource. In this way, the access efficiency can be improved, and the real-time business needs can be responded to quickly. For example, in the case of a collision on a certain resource, the terminal device that sent an uplink message on the collided resource can be triggered to send the corresponding uplink message again through the above method, so that access, data transmission, etc. can be achieved as soon as possible without waiting for the next round of inventory process. In some cases, all terminal devices that match the screening conditions indicated in the Query signaling can be inventoried through a single round of inventory process. For another example, if the current inventory process requires a large number of terminal devices to be inventoried (such as 10,000), it may take a long time. In this case, for a terminal device that has already been inventoried, if there is a new real-time business demand (such as the need to read sensor data associated with the terminal device stored in the terminal device, or the need to locate the terminal device in real time, or the need to update the data stored in the terminal device), it may be necessary to wait for the subsequent tag inventory to be completed, and then re-paging and then inventory, which requires a long wait. Through the above method, the corresponding terminal device can be triggered by the first information and the second information to access and transmit data again, which can quickly respond to business needs and will not affect the current round of inventory.

[0198] The above describes the overall solution of the embodiment of the present application based on Figure 7. In order to better understand the embodiment of the present application, the following introduces several examples in specific scenarios. First, the reader instructs the terminal device that has accessed in a specific time domain resource and / or frequency domain resource and / or code domain resource to access again. The specific processing flow can be shown in Figure 8, and may include but is not limited to the following steps:

[0199] 801. The reader sends a paging signal.

[0200] It should be understood that in some possible implementations, after the reader sends the paging signaling, the terminal device located within the signal coverage of the reader can set a flag bit based on the paging signaling.

[0201] 802. The reader sends a query signaling, which includes a session, a flag bit, and a Q value.

[0202] 803. When the session and flag bits match, the terminal device generates a counter based on the Q value.

[0203] After the terminal device receives the Query signaling from the reader, it can determine whether its own session and flag bits match the session and flag bits carried by the Query signaling. If the session and flag bits match, the terminal device can initialize the counter based on the Q value, that is, select the time domain resource based on the Q value. If the session and flag bits do not match, the terminal device can do nothing.

[0204] In some possible implementations, the Query signaling may also include a frequency domain resource indication and / or a code domain resource indication, where the frequency domain resource indication may indicate multiple frequency domain resources, and the code domain resource indication may indicate multiple code domain resources. When the session and the flag bit match, the terminal device may also randomly select a frequency domain resource from the indicated multiple frequency domain resources, and / or randomly select a code domain resource from the indicated multiple code domain resources for subsequent sending of uplink signaling or data.

[0205] 804. When the Counter of the terminal device is 0, the terminal device sends RN16 signaling to the reader.

[0206] It should be understood that in some possible implementations, when the Counter of the terminal device is 0, the terminal device may also send RN8 signaling (8-bit random number) or RN16 signaling (16-bit random number) to the reader / writer. This embodiment of the present application does not limit this.

[0207] In an embodiment of the present application, when sending RN signaling, the terminal device may carry first indication information, and the first indication information may implicitly or explicitly indicate relevant communication parameters (MCS), which may be uplink and / or downlink communication parameters (such as communication parameters used for subsequent transmission of data (such as EPC)). Exemplarily, the communication parameters may include the number of repetitions (such as the number of bit repetitions, the number of level repetitions, etc.), or the desired downlink communication parameters (such as the number of cyclic redundancy check (CRC) bits, the coding rate, the preamble length, etc.), or the length (number of bits) of uplink data (such as EPC, device ID, etc.).

[0208] It should be understood that when the relevant communication parameters are explicitly indicated, the first indication information may be the corresponding communication parameters (such as the number of repetitions, the encoding code rate). In this case, the first indication information may be included in the RN signaling. The following describes a method for implicitly indicating relevant communication parameters. For example, the communication parameters listed above may be associated with the bit length of the RN signaling. For example, the RN signaling length may be divided into multiple groups, each corresponding to a communication parameter configuration, such as 8 bits corresponding to a communication parameter configuration, and 16 bits corresponding to a communication parameter configuration. In this case, the first indication information may be understood as the bit length of the RN signaling, and the corresponding communication parameter configuration is implicitly indicated by the bit length of the RN signaling. It should be understood that, in actual circumstances, the communication parameter configuration indicated by the first indication information may be the expected parameter configuration of the terminal device, and the communication parameters ultimately used may be determined by the network device (such as a base station) in combination with the expected parameter configuration and related resources (such as processing resources, transmission resources, etc.). It should also be understood that, compared with the explicit indication method, implicitly indicating the relevant communication parameters can save transmission resources.

[0209] In the above method, during the random access process, the terminal device can tell the network device (such as the base station) some parameter information in advance through RN signaling without reporting it separately, and can also let the network device reserve resources in advance (such as more resources required for uplink data bit length). The reserved resources may include frequency resources, time domain resources, etc.

[0210] Optionally, after the network device receives the first indication information, the network device can determine relevant communication parameters (such as uplink communication parameters) based on the first indication information, for example, the time unit Tpri, the encoded code length M, the scaling factor Rchip, etc. Afterwards, the network device can inform the corresponding terminal device of the determined communication parameters through downlink signaling (such as ACK, QueryRep, Query, etc.). Among them, Tpri can be an uplink or downlink or uplink and downlink transmission time unit, or a related parameter. M can be the number of Manchester coding repetitions, or a related parameter. Rchip can be the number of level repetitions, or a parameter related to the level length.

[0211] Steps 801-804 are similar to the relevant steps in FIG. 5 , and reference may be made to the relevant description in FIG. 5 .

[0212] 805. In the event of a collision, the reader sends a query target resource signaling (QueryTargetOccasion), where the query target resource signaling includes a first resource indication.

[0213] In an embodiment of the present application, when multiple terminal devices use the same resource to send RN16 signaling and a collision occurs, the reader can query the target resource signaling to instruct the terminal device that collided to access again.

[0214] Among them, the query target resource signaling may include a first resource indication, and the first resource indication may indicate a specific resource, such as indicating a resource in which a collision occurred. For example, assuming that terminal device 1 and terminal device 2 both send RN16 in slot 0 and a collision occurs, the reader / writer may send a query target resource signaling, and the first resource indication carried by the query target resource signaling may indicate slot 0. For another example, assuming that terminal device 1 and terminal device 2 both use frequency domain resource 1 to send RN16 in slot 0, and terminal device 3 uses frequency domain resource 2 to send RN16 in slot 0, and terminal device 1 and terminal device 2 collide, the reader / writer may send a query target resource signaling, and the first resource indication carried by the query target resource signaling may indicate slot 0 and frequency domain resource 1. It should be understood that each terminal device can receive the query target resource signaling sent by the reader / writer, and then check whether the resource indicated by the first resource indication in the query target resource signaling is the resource to which it previously sent uplink information. If the resource indicated by the first resource indication in the query target resource signaling is the resource to which it previously sent uplink information, the corresponding terminal device can access again based on the query target resource signaling. If the resource indicated by the first resource indication in the query target resource signaling is not the resource to which it previously sent uplink information, the corresponding terminal device does not need to perform any processing.

[0215] In some possible implementations, the query target resource signaling may not include the first resource indication. In this case, the current corresponding time domain resource, such as the current corresponding time slot, may be implicitly indicated. For example, assuming that both terminal device 1 and terminal device 2 send RN16 in slot 0 and a collision occurs, the reader / writer may then send a query target resource signaling in slot 0. In this case, the terminal device that sent the uplink message in slot 0 may be implicitly instructed to access again or send an uplink message.

[0216] The query target resource signaling may also include a second resource indication, and the second resource indication may indicate multiple resources. The terminal device corresponding to the first resource indication may randomly select a resource from the multiple resources for subsequent resending of RN16. Exemplarily, the second resource indication may indicate two sub-time slots corresponding to slot1, namely subslot0 and subslot1, from which terminal device 1 and terminal device 2 may randomly select a resource for subsequent resending of RN16. For example, terminal device 1 selects subslot0 corresponding to slot1, and terminal device 2 selects subslot1 corresponding to slot1. It should be understood that the terminal device corresponding to the first resource indication is, that is, the terminal device that sends uplink information on the resource indicated by the first resource indication.

[0217] It should be noted that the multiple resources indicated by the above-mentioned second resource indication are described by taking the multiple sub-time slots corresponding to a time slot (i.e., subslot0 and subslot1 corresponding to slot1) as an example, but in some possible implementations, the multiple resources indicated by the second resource indication may also be different frequency domain resources in the same time slot, such as the time domain resource is slot1, and the frequency domain resources include frequency domain resource 1, frequency domain resource 2, etc. The multiple resources indicated by the second resource indication may also be different frequency domain resources in the sub-time slots corresponding to a certain time slot, such as the time domain resource is subslot0 corresponding to slot1, and the frequency domain resources include frequency domain resource 1, frequency domain resource 2, etc. The multiple resources indicated by the second resource indication may also be different frequency domain resources in multiple time slots, such as the time domain resource is slot1, and the corresponding frequency domain resources include frequency domain resource 1 and frequency domain resource 2, and the time domain resource is slot2, and the corresponding frequency domain resources include frequency domain resource 3 and frequency domain resource 4. In the embodiment of the present application, there is no limitation on the multiple resources indicated by the second resource indication. It should be understood that the multiple resources indicated by the second resource indication may be different from the resources already allocated through the Query signaling, that is, they may be different from the resources used by the terminal device that has not yet sent RN16. In this way, collision can be avoided.

[0218] It is understandable that, in some possible implementations, after the terminal device corresponding to the first resource indication receives the query target resource signaling and selects a resource based on the second resource indication in the query target resource signaling, it can initialize one or more counters based on the selected resource. For example, assuming that terminal device 1 selects subslot0 corresponding to slot1, terminal device 1 can initialize two counters, one counter corresponding to the time slot and one counter corresponding to the sub-time slot. Since the current time slot is slot0, terminal device 1 can initialize the counter corresponding to the time slot to 1 and the counter corresponding to the sub-time slot to 0. Similarly, assuming that terminal device 2 selects subslot1 corresponding to slot1, terminal device 2 can initialize the counter corresponding to the time slot to 1 and the counter corresponding to the sub-time slot to 1.

[0219] In some possible implementations, the query target resource signaling may further include message indication information, and the message indication information may be used to indicate that the terminal device corresponding to the first resource indication feeds back RN16 or uplink data (such as EPC), and the feedback RN16 is taken as an example for explanation here. It should be understood that directly feeding back EPC is equivalent to omitting the random access process. For example, the message indication information may include multiple bits, and each value combination may correspond to an uplink message. Taking 1 bit as an example, 0 may indicate feedback RN16, and 1 may indicate feedback EPC. It should be understood that in some embodiments, the message indication information may indicate more uplink messages, not limited to RN16 and EPC.

[0220] The first resource indication may refer to the above-mentioned first information, the second resource indication may refer to the above-mentioned fourth information, and the message indication information may refer to the above-mentioned third information.

[0221] 806. The reader sends a QueryRep signaling.

[0222] After the reader sends the query target resource signaling, it can continue to send QueryRep signaling to perform subsequent inventory processes.

[0223] It is understandable that in the above process, the query target resource signaling may be sent after a collision occurs, and then the QueryRep signaling is sent, but the embodiment of the present application does not limit the timing of sending the query target resource signaling. For example, the reader / writer may send the QueryRep signaling first. If no terminal device responds to the QueryRep signaling, the reader / writer may send the query target resource signaling again. For another example, the reader / writer may wait for the inventory process corresponding to any subsequent QueryRep signaling to end before sending the query target resource signaling.

[0224] 807. The reader sends a SubQueryRep signaling.

[0225] For example, assuming that the reader does not receive any RN16 signaling from any terminal device within a period of time (e.g., within 5ms) after sending the QueryRep signaling, the reader may assume that there is no response from the terminal device and may continue to send query signaling. Since the resources indicated by the second resource indication sent by the reader may be subslot0 and subslot1 corresponding to slot1, when no terminal device responds to the QueryRep signaling corresponding to slot1, the reader may send SubQueryRep signaling to trigger the terminal device using the resource subslot0 corresponding to slot1 to access.

[0226] 808. Terminal device 1 sends RN16 signaling.

[0227] Assuming that the resource previously selected by the terminal device 1 is subslot0 corresponding to slot1, the terminal device 1 can send RN16 signaling after receiving the first SubQueryRep signaling corresponding to slot1 sent by the reader.

[0228] 809. The reader sends an ACK signaling, which may include a 16-bit random number fed back by terminal device 1.

[0229] After the reader receives the RN16 signaling fed back by the terminal device 1 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 1 .

[0230] 810. Terminal device 1 sends EPC signaling.

[0231] After receiving the ACK signaling, terminal device 1 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches (e.g., it is the same as the 16-bit random number sent by itself), terminal device 1 can send EPC signaling. If it does not match, terminal device 1 may not respond and may not send EPC signaling. For example, the EPC signaling may include the ID of terminal device 1, such as EPC, TID, etc.

[0232] 811. The reader sends a SubQueryRep signaling.

[0233] After receiving the EPC signaling from terminal device 1, the reader can continue to send SubQueryRep signaling to trigger the terminal device using the resource subslot1 corresponding to slot1 to access.

[0234] 812. Terminal device 2 sends RN16 signaling.

[0235] Assuming that the resource previously selected by the terminal device 2 is subslot1 corresponding to slot1, the terminal device 2 can send RN16 signaling after receiving the second SubQueryRep signaling corresponding to slot1 sent by the reader.

[0236] 813. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device 2.

[0237] After the reader receives the RN16 signaling fed back by the terminal device 2 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 2 .

[0238] 814. Terminal device 2 sends EPC signaling.

[0239] After receiving the ACK signaling, terminal device 2 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches (such as being the same as the 16-bit random number sent by itself), terminal device 2 can send EPC signaling. If it does not match, terminal device 2 may not respond and may not send EPC signaling.

[0240] 815. The reader sends a QueryRep signaling.

[0241] After receiving the EPC signaling sent by terminal device 2, the reader can continue with the subsequent inventory process, such as sending the QueryRep signaling corresponding to slot2.

[0242] It is understandable that the above steps 801-815 are merely exemplary and illustrate only a portion of the inventory process in one round of inventory.

[0243] For example, please refer to Figure 9, which is a schematic diagram of a radio frequency identification disclosed in an embodiment of the present application. As shown in Figure 9, terminal device 1 and terminal device 2 can both send RN16 in slot 0, and a collision occurs, which may cause the reader to be unable to decode correctly. In this case, the reader can send QueryTargetOccasion signaling to instruct the terminal device sending the uplink message in slot 0 to access again, that is, to instruct terminal device 1 and terminal device 2 to access again. Assume that the QueryTargetOccasion signaling includes a second resource indication, and the second resource indication indicates the two sub-time slots corresponding to slot 1, namely subslot 0 and subslot 1. Terminal device 1 selects subslot 0 corresponding to slot 1, and terminal device 2 selects subslot 1 corresponding to slot 1. Afterwards, in subslot 0 corresponding to slot 1, terminal device 1 can access again and can transmit uplink data, such as the transmission of the EPC corresponding to terminal device 1. In subslot 1 corresponding to slot 1, terminal device 2 can access again and can transmit uplink data, such as the transmission of the EPC corresponding to terminal device 2.

[0244] For another example, please refer to Figure 10, which is a schematic diagram of another radio frequency identification disclosed in an embodiment of the present application. Different from Figure 9, the resources indicated by the second resource indication included in the QueryTargetOccasion signaling in Figure 10 can be slot1 and the corresponding frequency domain resource 1 and frequency domain resource 2. Assume that terminal device 1 selects frequency domain resource 1 and terminal device 2 selects frequency domain resource 2. Afterwards, after receiving the QueryRep signaling corresponding to slot1, terminal device 1 and terminal device 2 can both feedback RN16 to the reader, but the frequency domain resource used by terminal device 1 can be frequency domain resource 1, and the frequency domain resource used by terminal device 2 can be frequency domain resource 2. Afterwards, terminal device 1 and terminal device 2 can receive the ACK signaling sent by the reader, which can carry the 16-bit random number fed back by terminal device 1 and the 16-bit random number fed back by terminal device 2. In some possible implementations, the terminal device may also separately send ACK signaling corresponding to terminal device 1 and terminal device 2 through different frequency domain resources. For example, the ACK signaling corresponding to terminal device 1 may be sent through frequency domain resource 1, where the ACK signaling includes a 16-bit random number fed back by terminal device 1, and the ACK signaling corresponding to terminal device 2 may be sent through frequency domain resource 2, where the ACK signaling includes a 16-bit random number fed back by terminal device 2. It should be understood that terminal device 1 and terminal device 2 use the same time domain resources but different frequency domain resources, which can avoid collision between terminal device 1 and terminal device 2.

[0245] The following is an example of a situation where the reader instructs the terminal device that has transmitted data in a specific time domain resource and / or frequency domain resource and / or code domain resource to transmit data again. The specific processing flow can be shown in Figure 11 and can include but is not limited to the following steps:

[0246] 1101. The reader sends a paging signal.

[0247] 1102. The reader sends a Query signaling, which includes a session, a flag bit, and a Q value.

[0248] 1103. When the session and flag bits match, the terminal device generates a Counter based on the Q value.

[0249] 1104. When the Counter of the terminal device is 0, the terminal device sends RN16 signaling to the reader.

[0250] Steps 1101-1104 are similar to steps 801-804, and reference may be made to the relevant descriptions in the above steps 801-804.

[0251] 1105. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device.

[0252] When there is no terminal device collision (such as a single terminal device feeds back RN16), the reader can send ACK signaling after receiving the RN16 signaling from the terminal device. The ACK signaling may include the 16-bit random number carried in the RN16 signaling.

[0253] 1106. The terminal device sends EPC signaling.

[0254] After the terminal device receives the ACK signaling, it can determine whether the 16-bit random number included in the ACK signaling matches. If it matches (such as being the same as the 16-bit random number sent by itself), the terminal device can send EPC signaling. If it does not match, the terminal device may not respond and may not send EPC signaling.

[0255] 1107. In the event that the EPC signaling transmission fails, the reader sends a target resource query signaling, where the target resource query signaling includes a first resource indication.

[0256] In an embodiment of the present application, when the EPC signaling sent by a terminal device fails to transmit, the reader can instruct the terminal device that failed to transmit data to transmit data again by querying the target resource signaling, or can instruct the terminal device that failed to transmit data to reconnect and then transmit data. The reasons for the failure of EPC signaling transmission may be various, for example, there may be interference in the transmission environment, or two terminal devices may feedback EPC signaling using the same resource.

[0257] The query target resource signaling may include a first resource indication, which may indicate a specific resource, such as a resource indicating a failed EPC signaling transmission. For example, assuming that terminal device 1 sends EPC signaling in slot 0, but due to interference, the EPC signaling transmission fails, the reader may then send a query target resource signaling, and the first resource indication carried by the query target resource signaling may indicate slot 0. It should be understood that each terminal device may receive the query target resource signaling sent by the reader, and then may check whether the resource indicated by the first resource indication in the query target resource signaling is the resource to which it previously sent uplink information. If the resource indicated by the first resource indication in the query target resource signaling is the resource to which it previously sent uplink information, the corresponding terminal device may perform data transmission again based on the query target resource signaling, or perform access and data transmission again based on the query target resource signaling. If the resource indicated by the first resource indication in the query target resource signaling is not the resource to which it previously sent uplink information, the corresponding terminal device may not perform any processing.

[0258] The query target resource signaling may also include a second resource indication, and since the reader is not clear about the reason for the data transmission failure, the second resource indication may indicate multiple resources. The terminal device corresponding to the first resource indication may randomly select a resource from the multiple resources for subsequent resending of EPC, or resending RN16 and EPC. Exemplarily, the second resource indication may indicate two sub-slots corresponding to slot1, namely subslot0 and subslot1. Assuming that the terminal device corresponding to the first resource indication is terminal device 1, terminal device 1 may randomly select a resource from them for subsequent resending of EPC. For example, terminal device 1 selects subslot0 corresponding to slot1.

[0259] Exemplarily, in some possible implementations, the query target resource signaling may further include message indication information, and the message indication information may be used to indicate that the terminal device corresponding to the first resource indication feeds back RN16 or uplink data (such as EPC). It should be understood that directly feeding back EPC is equivalent to omitting the random access process, that is, there is no need to send RN16 first, and then send EPC after receiving ACK. For example, the message indication information may include multiple bits, and each value combination may correspond to an uplink message. Taking 1 bit as an example, 0 may indicate feedback RN16, and 1 may indicate feedback EPC.

[0260] 1108. The reader sends a QueryRep signaling.

[0261] After the reader sends the query target resource signaling, it can continue to send QueryRep signaling to perform subsequent inventory processes.

[0262] 1109. The reader sends a SubQueryRep signaling.

[0263] For example, assuming that the reader does not receive any RN16 signaling from any terminal device within a period of time (e.g., within 5ms) after sending the QueryRep signaling, the reader may assume that there is no response from the terminal device and may continue to send query signaling. Since the resources indicated by the second resource indication sent by the reader may be subslot0 and subslot1 corresponding to slot1, when no terminal device responds to the QueryRep signaling corresponding to slot1, the reader may send SubQueryRep signaling to trigger the terminal device using the resource subslot0 corresponding to slot1 to access.

[0264] 1110. Terminal device 1 sends EPC signaling.

[0265] Assuming that the resource previously selected by terminal device 1 is subslot0 corresponding to slot1, and the message indication information in the query target resource signaling indicates direct feedback of EPC signaling, eliminating the random access process, terminal device 1 can send EPC signaling after receiving the first SubQueryRep signaling corresponding to slot1 sent by the reader.

[0266] In some possible implementations, such as when the message indication information in the query target resource signaling indicates feedback of RN16 signaling, the terminal device 1 may first send RN16 signaling after receiving the first SubQueryRep signaling corresponding to slot1 sent by the reader / writer, and subsequently may send EPC signaling after receiving the ACK signaling returned by the reader / writer and determining that the ACK signaling matches.

[0267] It can be seen that in the above process, in the case of EPC conflict, the reader does not need to feedback NAK, and does not need to wait for the next round of inventory process to reselect resources and wait for access. It can trigger the corresponding terminal device to send EPC again by querying the target resource signaling. This method can reduce signaling overhead.

[0268] 1111. The reader sends a SubQueryRep signaling.

[0269] After receiving the EPC signaling from terminal device 1, the reader can continue to send SubQueryRep signaling to trigger the terminal device using the resource subslot1 corresponding to slot1 to access.

[0270] 1112. The reader sends a QueryRep signaling.

[0271] For example, assuming that the reader does not receive any RN16 signaling, EPC signaling, etc. fed back by any terminal device within a period of time (such as within 5ms) after sending the SubQueryRep signaling, the reader can assume that there is no response from the terminal device and can continue with the subsequent inventory process, such as sending the QueryRep signaling corresponding to slot2.

[0272] It is understandable that the above steps 1101-1112 are merely exemplary and illustrate only a portion of the inventory process in one round of inventory.

[0273] For example, please refer to Figure 12, which is a schematic diagram of another radio frequency identification disclosed in an embodiment of the present application. As shown in Figure 12, the EPC transmission sent by terminal device 1 in slot0 fails, such as due to signal interference. In this case, the reader can send QueryTargetOccasion signaling to instruct the terminal device that sends the uplink message in slot0 to send EPC again, that is, to instruct terminal device 1 to send EPC again. Assume that the QueryTargetOccasion signaling includes a second resource indication, and the second resource indication indicates the two sub-time slots corresponding to slot1, namely subslot0 and subslot1, and terminal device 1 selects subslot0 corresponding to slot1. Afterwards, in subslot0 corresponding to slot1, terminal device 1 can send EPC again.

[0274] The above-mentioned Figures 8 and 11 are introduced by taking the Q value carried in the Query signaling as an example. In this case, each terminal device can select the corresponding time slot based on the Q value, and then send the uplink message in the selected time slot. In other embodiments of the present application, a sub-time slot under a time slot can be allocated to the terminal device to send an uplink message. In this case, when the reader indicates a terminal device that sends an uplink message to a certain resource through query target resource signaling to access or send uplink data again, the time domain resource indicated by the first resource indication may include the time slot and the corresponding sub-time slot. The sub-time slot scenario is introduced below in conjunction with Figure 13. As shown in Figure 13, it may include but is not limited to the following steps:

[0275] 1301. The reader sends a paging signal.

[0276] 1302. The reader sends a Query signaling, which includes a session, a flag, a Q value, and a q value.

[0277] The Q value may be used to indicate one or more time slots, and the q value may indicate one or more sub-time slots.

[0278] 1303. When the session and the flag match, the terminal device generates Counter1 based on the Q value and generates Counter2 based on the q value.

[0279] After receiving the Query signaling, if the terminal device within the coverage of the reader signal determines that its own session and flag bits match the session and flag bits carried by the Query signaling, it can generate Counter1 based on the Q value and generate Counter2 based on the q value, which is equivalent to selecting a time slot based on the Q value and selecting a sub-time slot under the time slot based on the q value. For example, assuming that the Q value is 4 and the q value is 1, in this case, the corresponding terminal device can select a time slot from slot0-slot15 and a sub-time slot from subslot0 and subslot1. For example, terminal device 1 can select slot0 and subslot0, and the corresponding Counter1 and Counter2 are both 0. Terminal device 2 can select slot0 and subslot1, and the corresponding Counter1 is 0 and Counter2 is both 1. In this case, terminal device 1 can send an uplink message in subslot0 corresponding to slot0, and terminal device 2 can send an uplink message in subslot1 corresponding to slot0.

[0280] Steps 1301-1303 are similar to steps 801-803, and reference may be made to the relevant descriptions in the above steps 801-803.

[0281] 1304. The reader sends a SubQueryRep signaling.

[0282] If the q value is 1, the reader can send two SubQueryRep signaling messages in each time slot to trigger the corresponding terminal device to access. Among them, when the terminal device's Counter1 is 0, the terminal device does not need to decrement Counter2 when receiving the first SubQueryRep. After the first SubQueryRep, Counter2 can be decremented by 1 for each SubQueryRep received.

[0283] 1305. When Counter1 and Counter2 of terminal device 1 are both 0, terminal device 1 sends RN16 signaling to the reader.

[0284] After receiving the first SubQueryRep signaling after the Query signaling, the terminal device can check whether its own Counter1 and Counter2 are both 0. If both are 0, the terminal device can send RN16 signaling to the reader. For example, terminal device 1 can determine that its own Counter1 and Counter2 are both 0 and can send RN16 signaling to the reader.

[0285] 1306. The reader sends an ACK signaling, which may include a 16-bit random number fed back by terminal device 1.

[0286] When there is no terminal device collision, after the reader receives the RN16 signaling from the terminal device 1, it can send an ACK signaling, and the ACK signaling can include the 16-bit random number carried in the RN16 signaling.

[0287] 1307. Terminal device 1 sends EPC signaling.

[0288] For example, after receiving the ACK signaling, the terminal device 1 may determine whether the 16-bit random number included in the ACK signaling matches. If so, the terminal device 1 may send the EPC signaling. If not, the terminal device 1 may not respond.

[0289] 1308. The reader sends a SubQueryRep signaling.

[0290] After receiving the EPC signaling from terminal device 1, the reader can continue to send SubQueryRep signaling to trigger the terminal device using the resource subslot1 corresponding to slot0 to access.

[0291] For example, in some possible implementations, when the terminal device sends EPC signaling and receives the next SubQueryRep signaling, it can be considered that the EPC transmission is successful, or when the terminal device sends EPC signaling and receives the next QueryRep signaling, it can be determined that the EPC transmission is successful.

[0292] 1309. When Counter1 and Counter2 of terminal device 2 are both 0, terminal device 2 sends RN16 signaling to the reader.

[0293] If Counter1 of the terminal device is 0, after receiving the second SubQueryRep signaling after the Query signaling, the terminal device can decrement its own Counter2 by 1. If Counter2 is 0 after decrement, the terminal device can send RN16 signaling to the reader. For example, after Terminal Device 2's Counter2 is decremented by 1, Terminal Device 2 can determine that both its own Counter1 and Counter2 are 0 and can send RN16 signaling to the reader.

[0294] 1310. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device 2.

[0295] When there is no terminal device collision, after the reader receives the RN16 signaling from the terminal device 2, it can send an ACK signaling, and the ACK signaling can include the 16-bit random number carried in the RN16 signaling.

[0296] In the above example, in a sub-timeslot (such as subslot0 corresponding to slot0), after the reader receives the RN signaling from the terminal device (such as terminal device 1), it can feedback the corresponding ACK. Then, after the reader receives the corresponding EPC, the reader can trigger other terminal devices (such as terminal device 2) to perform an inventory of the next sub-timeslot through SubQueryRep signaling. In addition to this method, in an embodiment of the present application, in order to improve access / inventory efficiency, after the reader receives the RN signaling from the terminal device (such as terminal device 1) in a sub-timeslot (such as subslot0 corresponding to slot0), it can trigger the inventory of the next sub-timeslot during the process of processing the RN signaling received in the sub-timeslot.

[0297] Exemplarily, the time interval between the reader sending a SubQueryRep and receiving the corresponding RN is T3, and the time interval between the reader receiving the RN signaling and sending an ACK is T4, which is much greater than T3. In this case, the time between the reader receiving the RN and sending the ACK is sufficient to complete the transmission of the SubQueryRep and the reception of the corresponding RN again. Therefore, in some possible implementations, to improve access efficiency, the reader can trigger an inventory of the next sub-timeslot while processing the RN signaling received in a certain sub-timeslot (such as subslot0 corresponding to slot0). Then, during the inventory of the next sub-timeslot (such as subslot1 corresponding to slot0), after receiving the RN signaling fed back by the terminal device (such as terminal device 2), the reader can send the ACK / NAK signaling corresponding to the previous sub-timeslot. In this case, in order to distinguish the ACK / NAK signaling corresponding to different terminal devices, the ACK / NAK signaling sent by the reader can include indication information (such as second indication information) for indicating the corresponding sub-timeslot, so as to indicate which sub-timeslot the ACK / NAK signaling corresponds to. In the above case, ACK signaling can be used to indicate that the terminal device that sent RN signaling in the corresponding sub-time slot (the sub-time slot indicated by the second indication information) has successfully completed random access, or to trigger the terminal to perform data transmission. NAK signaling can indicate that the terminal device that sent RN signaling in the corresponding sub-time slot (the sub-time slot indicated by the second indication information) has failed random access.

[0298] For example, in the above step 1305, after the reader receives the RN16 signaling from terminal device 1, step 1306 may not be executed, and the inventory of the next sub-time slot may be triggered immediately, that is, step 1308 may be executed to send the SubQueryRep signaling. Then, after the reader receives the signaling from terminal device 2, the reader has processed the RN16 signaling corresponding to terminal device 1 and can return the corresponding ACK signaling to terminal device 1. In other words, the reader can return the ACK signaling corresponding to the previous sub-time slot (subslot0 corresponding to slot0) in subslot1 corresponding to slot0. In addition to carrying the RN16 sent by terminal device 1, the ACK signaling may also carry second indication information, which may be used to indicate subslot0, or indicate subslot0 corresponding to slot0. After receiving the ACK signaling, terminal device 1 can determine that its random access is successful and can send EPC signaling. After receiving the EPC signaling returned by terminal device 1, the reader can send ACK signaling corresponding to subslot 1 corresponding to slot 0. After receiving the ACK signaling, terminal device 2 can determine that its random access is successful and can send EPC signaling. In other words, in this case, the execution steps of steps 1304-1311 can be steps 1304, 1305, 1308, 1309, 1306, 1310, and 1311. In this way, the reader can trigger terminal device 2 to perform random access while processing the RN16 signaling returned by terminal device 1.

[0299] 1311. Terminal device 2 sends EPC signaling.

[0300] For example, after receiving the ACK signaling, the terminal device 2 may determine whether the 16-bit random number included in the ACK signaling matches. If so, the terminal device 2 may send the EPC signaling. If not, the terminal device 2 may not respond.

[0301] 1312. The reader sends a query target resource signaling, where the query target resource signaling includes a first resource indication.

[0302] For example, for a terminal device that has already transmitted data (such as terminal device 1), if there is a new real-time business demand (such as the need to read sensor data associated with the terminal device stored in the terminal device), the reader can instruct the terminal device to access and transmit data again by querying the target resource signaling.

[0303] Among them, the query target resource signaling may include a first resource indication, and the first resource indication may indicate the resource of the corresponding terminal device that previously sent the uplink message, such as indicating the resource of the terminal device 1 that previously sent the uplink message, that is, subslot0 corresponding to slot0.

[0304] In the above method, the terminal device needs to determine the sub-time slot corresponding to SubQueryRep by itself, such as by counting SubQueryRep. Except for the first SubQueryRep corresponding to each time slot, counter2 is reduced by 1 each time SubQueryRep is received. In some possible implementations, the corresponding sub-time slot identifier (such as subslot number = M) can also be directly carried in SubQueryRep. In this case, after the terminal device selects the time domain resource, it can directly determine whether it is the sub-time slot selected by itself through the sub-time slot identifier carried in SubQueryRep. Accordingly, the first resource indication in the query target resource signaling can also include a sub-time slot identifier (such as subslot number = 0). In other possible implementations, the first resource indication may only indicate the time slot without indicating the sub-time slot. In this case, the first query target resource signaling (slot0) corresponding to a time slot (such as slot0) may implicitly indicate the first sub-time slot (subslot0) corresponding to the time slot, and the corresponding second query target resource signaling (slot0) may implicitly indicate the second sub-time slot (subslot1) corresponding to the time slot. Similarly, the corresponding third query target resource signaling (slot0) may implicitly indicate the third sub-time slot (subslot2) corresponding to the time slot.

[0305] In some possible implementations, the query target resource signaling may not include the first resource indication. In this case, the currently corresponding time domain resources may be implicitly indicated, such as the currently corresponding time slot and sub-time slot.

[0306] The query target resource signaling may also include a second resource indication, which may indicate new resources for the corresponding terminal device, such as indicating subslot2 corresponding to slot0 for terminal device 1.

[0307] Exemplarily, in some possible implementations, the query target resource signaling may further include message indication information, and the message indication information may be used to indicate that the terminal device corresponding to the first resource indication feeds back RN16 or uplink data (such as EPC).

[0308] 1313. The reader sends a SubQueryRep signaling.

[0309] When the reader schedules terminal device 1 to transmit uplink data again in subslot 2 corresponding to slot 0 through query target resource signaling, the reader can continue to send SubQueryRep signaling to trigger the terminal device using the resource subslot 2 corresponding to slot 0 to access.

[0310] 1314. Terminal device 1 sends RN16 signaling to the reader.

[0311] Assuming that the resource previously selected by terminal device 1 is subslot0 corresponding to slot0, and the message indication information in the query target resource signaling indicates sending RN16, and sending uplink data after receiving ACK, terminal device 1 can send RN16 signaling after receiving the third SubQueryRep signaling corresponding to slot0 sent by the reader.

[0312] 1315. The reader sends an ACK signaling, which may include a 16-bit random number fed back by terminal device 1.

[0313] When there is no terminal device collision, after the reader receives the RN16 signaling from the terminal device 1, it can send an ACK signaling, and the ACK signaling can include the 16-bit random number carried in the RN16 signaling.

[0314] 1316. Terminal device 1 sends uplink data.

[0315] For example, after receiving the ACK signaling, the terminal device 1 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, the terminal device 1 can send uplink data (such as sensor data). If it does not match, the terminal device 1 may not respond.

[0316] 1317. The reader sends a QueryRep signaling.

[0317] For example, after the reader sends the third SubQueryRep signaling corresponding to slot 0, it can continue with the subsequent inventory process, such as sending the QueryRep signaling corresponding to slot 1.

[0318] It is understandable that the above steps 1301-1317 are merely exemplary and illustrate only a portion of the inventory process in one round of inventory.

[0319] It should be noted that the above sub-timeslot scenario is merely illustrative, primarily to demonstrate that the reader can schedule a terminal device that sends an uplink message in a sub-timeslot corresponding to a time slot to re-access or transmit data. It should be understood that if a terminal device collides in a sub-timeslot, the above-described method can also be used to re-schedule the terminal device that collided in the corresponding sub-timeslot to re-access or transmit data.

[0320] The following is an illustrative description of the situation in which the reader instructs a terminal device that has accessed a specific time domain resource and / or frequency domain resource and / or code domain resource to access again in a multi-process scenario. Among them, the main difference between the processing flow in the multi-process scenario and the processing flow in Figure 8 above is that in the multi-process scenario, the downlink message sent by the reader will include the corresponding process identifier, and each terminal device within the coverage of the reader can only respond to the downlink message corresponding to the process identifier associated with itself. Accordingly, when the reader triggers the terminal device that has sent an uplink message on a specific resource to send an uplink message again by querying the target resource signaling, the query target resource signaling can be associated with a process identifier. The specific processing flow can be shown in Figure 14, and can include but is not limited to the following steps:

[0321] 1401. The reader sends a paging signal.

[0322] For example, the reader can carry multiple process identifiers in the paging signaling, such as the four process identifiers {1, 2, 3, 4}, representing process 1, process 2, process 3, and process 4, respectively. For another example, the reader can carry the maximum number of processes in the paging signaling, such as if the maximum number of processes is 4. In this case, it can be assumed that the identifiers corresponding to these four processes can be 1, 2, 3, and 4, respectively, which is equivalent to implicitly indicating multiple process identifiers. Accordingly, terminal devices within the coverage area of ​​the reader signal can receive the paging signaling and can determine multiple process identifiers based on the paging signaling. Afterwards, these terminal devices can select a process identifier from these multiple process identifiers. In the subsequent downlink messages sent by the reader, each terminal device can only respond to the downlink messages managed by the process identifier it has selected. It should be understood that the process identifier can be a process ID, a process number, or other information that can identify a process, which is not limited here.

[0323] 1402. The reader sends a query signaling, which includes a session, a flag, a Q value, and an identifier of process 1.

[0324] 1403. When the session, flag, and identifier of process 1 match, the terminal device generates a Counter based on the Q value.

[0325] It is understandable that since the Query signaling carries the identifier of Process 1, after receiving the Query signaling, terminal devices within the reader / writer signal coverage area can first determine whether they have selected Process 1. For terminal devices that have selected Process 1, they can process based on the Query signaling, such as determining whether their own session and flag bits match the session and flag bits carried in the Query signaling. If the session and flag bits match, the terminal device can initialize the counter based on the Q value, that is, select the time domain resource based on the Q value. If the session and flag bits do not match, the terminal device can perform no processing.

[0326] For example, in a multi-process scenario, the terminal device can store the process identifier of its own choice. After receiving the downlink message from the reader, it can check whether the process identifier in the downlink message is consistent with the currently stored process identifier. If they are consistent, it will respond, otherwise it will not respond.

[0327] 1404. When the Counter of the terminal device is 0, the terminal device sends RN16 signaling to the reader.

[0328] Steps 1401-1404 are similar to the relevant steps in FIG. 5 , and reference may also be made to the relevant description in FIG. 5 .

[0329] 1405. In the event of a collision, the reader sends a query target resource signaling (QueryTargetOccasion), which includes a first resource indication and an identifier of process 1.

[0330] In an embodiment of the present application, when multiple terminal devices use the same resource to send RN16 signaling and a collision occurs, the reader can query the target resource signaling to instruct the terminal device that collided to access again.

[0331] The query target resource signaling may include a first resource indication, which may indicate a specific resource, such as a resource indicating a collision. For example, assuming that both terminal device 1 and terminal device 2 send RN16 in slot 0 and a collision occurs, the reader / writer may then send a query target resource signaling, and the first resource indication carried in the query target resource signaling may indicate slot 0.

[0332] The query target resource signaling may also include a second resource indication, which may indicate multiple resources. The terminal device corresponding to the first resource indication may randomly select a resource from the multiple resources for subsequent resending of RN16. For example, the second resource indication may indicate two sub-time slots corresponding to slot1, namely subslot0 and subslot1, from which terminal device 1 and terminal device 2 may randomly select a resource for subsequent resending of RN16. For example, terminal device 1 selects subslot0 corresponding to slot1, and terminal device 2 selects subslot1 corresponding to slot1.

[0333] The query target resource signaling may further include an identifier of process 1 to indicate the process associated with the corresponding terminal device (such as terminal device 1 and terminal device 2), or to indicate the process associated with the query target resource signaling.

[0334] In some possible implementations, the query target resource signaling may further include message indication information, which may be used to instruct the terminal device corresponding to the first resource indication to feedback RN16 or uplink data (such as EPC). Feedback RN16 is used as an example for illustration. It should be understood that directly feeding back EPC is equivalent to omitting the random access process.

[0335] 1406. The reader sends a QueryRep signaling message, which includes the identifier of process 1.

[0336] After the reader sends the query target resource signaling, it can continue to send QueryRep signaling to perform the subsequent inventory process of process 1.

[0337] 1407. The reader sends a SubQueryRep signaling, which includes the identifier of process 1.

[0338] For example, assuming that the reader does not receive any RN16 signaling from any terminal device within a period of time (e.g., within 5ms) after sending the QueryRep signaling, the reader may assume that there is no response from the terminal device and may continue to send query signaling. Since the resources indicated by the second resource indication sent by the reader may be subslot0 and subslot1 corresponding to slot1, when no terminal device responds to the QueryRep signaling corresponding to slot1, the reader may send a SubQueryRep signaling to trigger process 1 to access the terminal device using the resource subslot0 corresponding to slot1.

[0339] 1408. Terminal device 1 sends RN16 signaling.

[0340] Assuming that the resource previously selected by terminal device 1 is subslot0 corresponding to slot1, after terminal device 1 receives the first SubQueryRep signaling corresponding to slot1 under process 1 sent by the reader, it can send RN16 signaling.

[0341] 1409. The reader sends an ACK signaling, which may include the 16-bit random number fed back by terminal device 1 and the identifier of process 1.

[0342] After the reader receives the RN16 signaling fed back by the terminal device 1 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 1 and the identifier of the process 1 .

[0343] 1410. Terminal device 1 sends EPC signaling.

[0344] After receiving the ACK signaling, terminal device 1 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, terminal device 1 can send EPC signaling. If it does not match, terminal device 1 may not respond and may not send EPC signaling.

[0345] 1411. The reader sends a SubQueryRep signaling message, which includes the identifier of process 1.

[0346] After receiving the EPC signaling from terminal device 1, the reader can continue to send SubQueryRep signaling to trigger the terminal device using the resource subslot1 corresponding to slot1 in process 1 to access.

[0347] 1412. Terminal device 2 sends RN16 signaling.

[0348] Assuming that the resource previously selected by terminal device 2 is subslot1 corresponding to slot1, after terminal device 2 receives the second SubQueryRep signaling corresponding to slot1 under process 1 sent by the reader, it can send RN16 signaling.

[0349] 1413. The reader sends an ACK signaling, which may include the 16-bit random number fed back by terminal device 2 and the identifier of process 1.

[0350] After the reader receives the RN16 signaling fed back by the terminal device 2 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 2 and the identifier of the process 1 .

[0351] 1414. Terminal device 2 sends EPC signaling.

[0352] After receiving the ACK signaling, terminal device 2 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, terminal device 2 can send EPC signaling. If it does not match, terminal device 2 may not respond and may not send EPC signaling.

[0353] It should be understood that the reader can also perform inventory processes corresponding to other processes, such as the inventory process corresponding to process 2, as shown in steps 1415-1419 below.

[0354] 1415. The reader sends a Query signaling, which includes a session, a flag, a Q value, and an identifier of process 2.

[0355] 1416. When the session, flag, and process 2 identifier match, the terminal device generates a Counter based on the Q value.

[0356] It is understandable that since the Query signaling carries the identifier of Process 2, after receiving the Query signaling, terminal devices within the reader / writer signal coverage area can first determine whether they have selected Process 2. For terminal devices that have selected Process 2, they can process based on the Query signaling, such as determining whether their own session and flag bits match the session and flag bits carried in the Query signaling. If the session and flag bits match, the terminal device can initialize the counter based on the Q value, that is, select the time domain resource based on the Q value. If the session and flag bits do not match, the terminal device can perform no processing.

[0357] 1417. When the Counter of the terminal device is 0, the terminal device sends RN16 signaling to the reader.

[0358] 1418. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device and the identifier of process 2.

[0359] After the reader receives the RN16 signaling fed back by the terminal device, it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device and the identifier of process 2.

[0360] 1419. The terminal device sends EPC signaling.

[0361] After receiving the ACK signaling, the terminal device can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, the terminal device can send EPC signaling. If it does not match, the terminal device may not respond and may not send EPC signaling.

[0362] It is understood that the above steps 1301-1317 are merely illustrative, illustrating only a portion of the inventory process within the next round of inventory for a portion of the processes. It should be noted that the descriptions of processes 1 and 2 are merely illustrative and do not limit the order of the steps within processes 1 and 2.

[0363] The following is an example of a multi-process scenario where the reader instructs the terminal device that has transmitted data in a specific time domain resource and / or frequency domain resource and / or code domain resource to transmit data again. In this case, the processing flow is similar to that of Figures 11 and 14 above, and reference can be made to the relevant descriptions in Figures 11 and 14 above. The specific processing flow can be shown in Figure 15 and may include but is not limited to the following steps:

[0364] 1501. The reader sends a paging signal.

[0365] 1502. The reader sends a query signaling, which includes a session, a flag, a Q value, and an identifier of process 1.

[0366] 1503. When the session, flag, and identifier of process 1 match, the terminal device generates a Counter based on the Q value.

[0367] 1504. When the Counter of the terminal device is 0, the terminal device sends RN16 signaling to the reader.

[0368] Steps 1501-1504 are similar to steps 1401-1404, and reference may be made to the relevant descriptions in the above steps 1401-1404.

[0369] 1505. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device and an identifier of process 1.

[0370] When there is no terminal device collision, the reader / writer may send an ACK signaling after receiving the RN16 signaling from the terminal device. The ACK signaling may include the 16-bit random number carried in the RN16 signaling and the identifier of process 1.

[0371] 1506. The terminal device sends EPC signaling.

[0372] After receiving the ACK signaling, the terminal device can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, the terminal device can send EPC signaling. If it does not match, the terminal device may not respond and may not send EPC signaling.

[0373] 1507. In the event that the EPC signaling transmission fails, the reader sends a target resource query signaling, which includes a first resource indication and an identifier of process 1.

[0374] In an embodiment of the present application, when the EPC signaling sent by the terminal device fails to be transmitted, the reader / writer can instruct the terminal device where the data transmission failed to be transmitted to perform data transmission again by querying the target resource signaling, or can instruct the terminal device where the data transmission failed to be transmitted to re-access and then perform data transmission.

[0375] The query target resource signaling may include a first resource indication, which may indicate a specific resource, such as a resource indicating a failure in EPC signaling transmission. For example, assuming that terminal device 1 sends EPC signaling in slot 0, but due to interference, the EPC signaling transmission fails, the reader / writer may then send a query target resource signaling, and the first resource indication carried in the query target resource signaling may indicate slot 0.

[0376] The query target resource signaling may also include a second resource indication, and since the reader is not clear about the reason for the data transmission failure, the second resource indication may indicate multiple resources. The terminal device corresponding to the first resource indication may randomly select a resource from the multiple resources for subsequent resending of EPC, or resending RN16 and EPC. Exemplarily, the second resource indication may indicate two sub-slots corresponding to slot1, namely subslot0 and subslot1. Assuming that the terminal device corresponding to the first resource indication is terminal device 1, terminal device 1 may randomly select a resource from them for subsequent resending of EPC. For example, terminal device 1 selects subslot0 corresponding to slot1.

[0377] The query target resource signaling may further include an identifier of process 1 to indicate the process associated with the corresponding terminal device (such as terminal device 1), or to indicate the process associated with the query target resource signaling.

[0378] Exemplarily, in some possible implementations, the query target resource signaling may further include message indication information, and the message indication information may be used to indicate that the terminal device corresponding to the first resource indication feeds back RN16 or uplink data (such as EPC).

[0379] 1508. The reader sends a QueryRep signaling message, which includes the identifier of process 1.

[0380] After the reader sends the query target resource signaling, it can continue to send QueryRep signaling to perform subsequent inventory processes.

[0381] 1509. The reader sends a SubQueryRep signaling, which includes the identifier of process 1.

[0382] For example, assuming that the reader does not receive any RN16 signaling from any terminal device within a period of time (e.g., within 5ms) after sending the QueryRep signaling, the reader may assume that there is no response from the terminal device and may continue to send query signaling. Since the resources indicated by the second resource indication sent by the reader may be subslot0 and subslot1 corresponding to slot1, when no terminal device responds to the QueryRep signaling corresponding to slot1, the reader may send a SubQueryRep signaling to trigger process 1 to access the terminal device using the resource subslot0 corresponding to slot1.

[0383] 1510. Terminal device 1 sends EPC signaling.

[0384] Assuming that the resource previously selected by terminal device 1 is subslot0 corresponding to slot1, and the message indication information in the query target resource signaling indicates direct feedback of EPC signaling, eliminating the random access process, terminal device 1 can send EPC signaling after receiving the first SubQueryRep signaling corresponding to slot1 sent by the reader.

[0385] 1511. The reader sends a SubQueryRep signaling, which includes the identifier of process 1.

[0386] After receiving the EPC signaling from terminal device 1, the reader can continue to send SubQueryRep signaling to trigger the terminal device using the resource subslot1 corresponding to slot1 in process 1 to access.

[0387] 1512. The reader sends a QueryRep signaling message, which includes the identifier of process 1.

[0388] For example, assuming that the reader does not receive any RN16 signaling, EPC signaling, etc. fed back by any terminal device within a period of time (such as within 5ms) after sending the SubQueryRep signaling, the reader can assume that there is no response from the terminal device and can continue with the subsequent inventory process, such as sending the QueryRep signaling corresponding to slot2.

[0389] It is understandable that the above steps 1501-1512 are merely exemplary and illustrate only a portion of the inventory process in the next round of inventory in process 1.

[0390] The above-mentioned Figures 7 to 15 introduce the situation in which, during a round of inventory, the reader / writer schedules (under a certain process) a terminal device that has sent an uplink message on a certain resource to send an uplink message again. When a collision occurs or there is a real-time business demand, this method can be used to quickly enable the colliding terminal device to access or transmit data again, and to respond to business needs in a timely manner. The following introduces several ways for terminal devices to determine resources. These resource determination methods can enable terminal devices that need to be inventoried to use different resources as much as possible to reduce the probability of collision or avoid collisions. Specifically, please refer to Figure 16, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 16, the processing flow may include but is not limited to the following steps:

[0391] 1601.AMF sends paging signaling to the reader, which includes the UE list.

[0392] Exemplarily, the AMF may receive a paging request from other network elements / devices, and the paging request may include a UE list (list), and the UE list may include the identifiers of multiple UEs. For example, the UE list may be {identifier of terminal device 1, identifier of terminal device 2, identifier of terminal device 3, identifier of terminal device 4, ...}. After receiving the paging request, the AMF may send paging signaling to the corresponding reader based on the paging request, and the paging signaling includes the UE list. For example, the AMF may first query which reader's signal coverage range the terminal device in the UE list is located, and then the AMF may send paging signaling to the corresponding reader.

[0393] It should be noted that the above-mentioned AMF can also be other network elements (such as other network elements in the core network), and this embodiment of the application does not limit this. In other words, other network elements can also be responsible for paging and access of terminal devices (such as environmental Internet of Things devices).

[0394] 1602. The reader sends a paging signaling including a UE list.

[0395] It should be understood that in some possible implementations, after the reader sends paging signaling, the terminal devices within the reader signal coverage can set a flag based on the paging signaling. For example, the terminal devices corresponding to the UE list can set a flag based on the paging signaling.

[0396] 1603. The reader sends a query signaling, which includes a session, a flag bit, and a Q value.

[0397] 1604. When the session and flag match, the terminal device generates a Counter based on the UE list.

[0398] After the terminal device receives the Query signaling from the reader, it can determine whether its own session and flag bits match the session and flag bits carried by the Query signaling. If the session and flag bits match, the terminal device (such as terminal device 1, terminal device 2, etc.) can initialize the counter based on the UE list and Q value, that is, select the time domain resources based on the UE list and Q value. If the session and flag bits do not match, the terminal device may not process it.

[0399] For example, assuming that the Q value is 4, the terminal device can determine that the selectable resources include slot0-slot15. The terminal device can select one resource from slot0-slot15 in sequence according to the order in the UE list, that is, the terminal device identifier in the UE list corresponds to slot0-slot15 in sequence. For example, when the UE list is {identifier of terminal device 1, identifier of terminal device 2, identifier of terminal device 3, identifier of terminal device 4, ...}, the resource corresponding to terminal device 1 can be slot0, the resource corresponding to terminal device 2 can be slot1, the resource corresponding to terminal device 3 can be slot2, the resource corresponding to terminal device 4 can be slot3, and so on. In this way, the terminal devices can be prevented from using the same resources to send uplink messages, thereby avoiding collisions.

[0400] In some possible implementations, the Query signaling may further include a frequency domain resource indication, which may indicate multiple frequency domain resources. When the session and the flag match, the terminal device may select a time domain resource from multiple time domain resources based on the UE list, and may select a frequency domain resource from multiple frequency domain resources for subsequent uplink signaling or data transmission. For example, when the UE list is {identifier of terminal device 1, identifier of terminal device 2, identifier of terminal device 3, identifier of terminal device 4, ...}, each time slot corresponds to two frequency domain resources, namely frequency domain resource 1 and frequency domain resource 2, the resources corresponding to terminal device 1 may be slot0 and frequency domain resource 1, the resources corresponding to terminal device 2 may be slot0 and frequency domain resource 2, the resources corresponding to terminal device 3 may be slot1 and frequency domain resource 1, the resources corresponding to terminal device 2 may be slot1 and frequency domain resource 2, and so on. In this way, terminal devices may be prevented from using the same resources to send uplink messages, thereby avoiding collisions.

[0401] In some other possible implementations, only one time slot can be configured, and the terminal device can send uplink messages through different frequency domains. For example, the frequency domain resource indication in the Query signaling can indicate multiple frequency domain resources, and the terminal device can select the frequency domain resource based on the UE list. Exemplarily, the frequency domain resource list is {frequency domain resource 1, frequency domain resource 2, frequency domain resource 3, ...}, and the UE list is {identification of terminal device 1, identification of terminal device 2, identification of terminal device 3, identification of terminal device 4, ...}. In this case, the terminal device can determine the number of frequency domain resources in the frequency domain resource list to be used by itself based on the number of its own identification in the UE list, such as the frequency domain resource corresponding to terminal device 1 is frequency domain resource 1, the frequency domain resource corresponding to terminal device 2 is frequency domain resource 2, the frequency domain resource corresponding to terminal device 3 is frequency domain resource 3, and so on.

[0402] In summary, when a reader is configured with multiple resources (time domain resources, frequency domain resources, code domain resources, etc.), a terminal device within the reader's coverage area can select a resource from these multiple resources based on the order in the UE list. Different orderings can select different resources, thus avoiding terminal device collisions. It should be noted that in addition to the aforementioned method where a terminal device determines its corresponding resource through the UE list, the reader can also directly allocate corresponding resources to each terminal device in the UE list.

[0403] The above description is based on the UE list carried in the paging signaling. In other embodiments of the present application, the paging signaling may also carry mask information. The mask information can match one or more terminal devices. For example, the mask information may include four parameters: MemBank (memorybank), pointer (Pointer), length (Length), and mask (mask).

[0404] In real-world scenarios, when inventorying, the inventory is typically performed on terminal devices of the same type, such as those used for environmental monitoring. The identifiers corresponding to these terminal devices are typically continuous. Therefore, in this case, each terminal device can take a modulo value based on its own identifier and select the corresponding resource based on the modulo value. For example, assuming there are N resources, the resource index corresponding to each terminal device can be the terminal device's identifier modulo N, where N is a positive integer. For example, there are 16 resources in total, namely slots 0 to 15, and there are 16 terminal devices to be inventoried, namely terminal devices 1 to 16. The identifiers corresponding to terminal devices 1 to 16 are 0001 to 0016, respectively. In this case, terminal device 1 can take a modulo value of 1 on its own ID and select the first resource, slot 0, from slots 0 to 15. Terminal device 2 can take a modulo value of 2 on its own ID and select the second resource, slot 1, from slots 0 to 15. Similarly, terminal device 3 can select the corresponding slot 2, terminal device 4 can select the corresponding slot 3, and so on.

[0405] It should be noted that the embodiments of the present application do not limit the configuration method of multiple uplink resources. For example, it can be configured by carrying Q values, frequency domain resource indications, etc. in the Query signaling, or it can be indicated by paging signaling, or it can be configured by other downlink messages, or it can be specified by the protocol (predefined).

[0406] 1605. Terminal device 1 sends RN16 signaling.

[0407] Assuming that the resource previously selected by terminal device 1 is slot 0, that is, the initialized Counter is 0, terminal device 1 can send RN16 signaling.

[0408] 1606. The reader sends an ACK signaling, which may include a 16-bit random number fed back by terminal device 1.

[0409] After the reader receives the RN16 signaling fed back by the terminal device 1 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 1 .

[0410] 1607. Terminal device 1 sends uplink data 1.

[0411] After receiving the ACK signaling, terminal device 1 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, terminal device 1 can send uplink data 1 (such as the EPC of terminal device 1). If it does not match, terminal device 1 may not respond.

[0412] 1608. The reader sends a QueryRep signaling.

[0413] After receiving uplink data 1 from terminal device 1, the reader can continue to send QueryRep signaling to trigger the terminal device using resource slot 1 to send the corresponding uplink data.

[0414] 1609. Terminal device 2 sends RN16 signaling.

[0415] Assume that the resource previously selected by terminal device 2 is slot 1, that is, the initialized Counter is 1. After receiving the QueryRep signaling, terminal device 2 can reduce the Counter by 1. After reduction by 1, the Counter can be 0, and terminal device 2 can send RN16 signaling.

[0416] 1610. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device 2.

[0417] After the reader receives the RN16 signaling fed back by the terminal device 2 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 2 .

[0418] 1611. Terminal device 2 sends uplink data 2.

[0419] After receiving the ACK signaling, terminal device 2 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, terminal device 2 can send uplink data 2 (such as the EPC of terminal device 2). If it does not match, terminal device 2 may not respond.

[0420] In the embodiment of the present application, since different terminal devices can use different resources to send uplink messages, in some possible implementations, the terminal device can directly send uplink data using the corresponding resources without sending RN16. For example, steps 1605 and 1606 are optional, that is, terminal device 1 can directly send uplink data 1 without sending RN16. For another example, steps 1609 and 1610 are optional, that is, terminal device 2 can directly send uplink data 2 without sending RN16.

[0421] 1612. The reader sends uplink data 1 and uplink data 2 to AMF.

[0422] After receiving uplink data 2 returned by terminal device 2, the reader / writer can send uplink data 2 and uplink data 1 previously returned by terminal device 1 to the AMF. It should be understood that the manner in which the reader / writer sends uplink data to the AMF is merely illustrative and does not constitute a limitation. For example, the reader / writer can send the corresponding uplink data to the AMF after receiving uplink data returned by each terminal device. For another example, the reader / writer can send the uplink data returned by multiple terminal devices together to the AMF after receiving uplink data returned by multiple terminal devices.

[0423] It should be understood that the reader can continue to send QueryRep signaling to perform subsequent inventory processes.

[0424] It is understandable that the above steps 1601-1612 are merely exemplary and illustrate only a portion of the inventory process in one round of inventory.

[0425] The following describes a packet access method, see Figure 17, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 17, the processing flow may include but is not limited to the following steps:

[0426] 1701.AMF sends paging signaling to the reader, which includes one or more mask information.

[0427] For example, the AMF may receive a paging request from another network element / device, where the paging request may include one or more mask information. After receiving the paging request, the AMF may send paging signaling to the corresponding reader based on the paging request, where the paging signaling includes the one or more mask information.

[0428] It should be noted that the above-mentioned AMF can also be other network elements (such as other network elements in the core network), and this embodiment of the application does not limit this. In other words, other network elements can also be responsible for paging and access of terminal devices (such as environmental Internet of Things devices).

[0429] 1702. The reader sends a paging signaling, which includes one or more mask information.

[0430] It should be understood that in some possible implementations, after the reader sends paging signaling, terminal devices within the reader's signal coverage area may set a flag based on the paging signaling. For example, terminal devices corresponding to one or more mask information in the paging signaling may set a flag based on the paging signaling.

[0431] It can be understood that one or more mask information can match multiple terminal devices. If the number of terminal devices corresponding to these one or more mask information is large, if the terminal devices corresponding to these one or more mask information are inventoried at the same time during a round of inventory, there may be a high probability of collision. Therefore, in an embodiment of the present application, the terminal devices corresponding to these one or more mask information can be grouped and then inventoried in groups.

[0432] Exemplarily, the grouping method may include various methods. For example, the terminal device corresponding to the one or more mask information may randomly select a group from multiple groups. For another example, the terminal device corresponding to the one or more mask information may select a group based on a modulo of its own identifier. For another example, each mask information may be considered a group.

[0433] The following describes the case of randomly selecting groups. For example, assuming that there are four groups, namely group 1, group 2, group 3 and group 4, any terminal device in the terminal devices corresponding to the one or more mask information can randomly select one group from the four groups. For example, terminal device 1 selects group 1, and terminal device 2 selects group 2. It should be noted that the embodiment of the present application does not limit the configuration method of the above-mentioned multiple groups. For example, it can be configured by carrying multiple group identifiers in the paging signaling (informing the terminal device which groups are included), or it can be configured through other downlink messages, or it can be specified by the protocol (predefined).

[0434] The following describes the case of selecting groups by modulo. For example, any terminal device among the terminal devices corresponding to the one or more mask information can take its own identifier modulo K, where K is an integer greater than or equal to 2. For example, assuming K is 4, the identifier of terminal device 1 is 0001, terminal device 1 can take its own ID modulo 4, with a modulus value of 1, and can select group 1. The identifier of terminal device 2 is 0002, terminal device 2 can take its own ID modulo 4, with a modulus value of 2, and can select group 2, and so on. It should be noted that the embodiment of the present application does not limit the configuration method of the above-mentioned K value. For example, the K value can be carried in the paging signaling, or the K value can be configured through other downlink messages, or it can be specified by the protocol (predefined).

[0435] It should be noted that after a terminal device selects a group, it can only access the inventory process associated with the selected group.

[0436] 1703. The reader sends a query signaling, which includes a session, a flag, a Q value, and an identifier of group 1.

[0437] In the embodiment of the present application, the Query signaling may carry a group identifier to instruct the corresponding terminal device to access. For example, the Query signaling may carry the identifier of Group 1, thereby instructing the terminal device associated with Group 1 to participate in this round of inventory process.

[0438] 1703. When the session, flag, and group identifier match, the terminal device generates a Counter based on the Q value.

[0439] After the terminal device receives the Query signaling from the reader / writer, it can determine whether its own session, flag bit and the identifier of the selected group match the session, flag bit and group identifier (such as the identifier of group 1) carried by the Query signaling. When the session, flag bit and group identifier match, the terminal device (such as terminal device 1, etc.) can initialize the counter based on the Q value, that is, select the time domain resource based on the Q value. When the session, flag bit and group identifier do not match, that is, the session and flag bit do not match or the group identifier does not match or both do not match, the terminal device can do nothing.

[0440] 1705. Terminal device 1 sends RN16 signaling.

[0441] Terminal device 1 belongs to group 1. Assuming that the resource previously selected by terminal device 1 is slot 0, that is, the initialized Counter is 0, terminal device 1 can send RN16 signaling.

[0442] 1706. The reader sends an ACK signaling, which may include a 16-bit random number fed back by terminal device 1.

[0443] After the reader receives the RN16 signaling fed back by the terminal device 1 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 1 .

[0444] 1707. Terminal device 1 sends uplink data 1.

[0445] After receiving the ACK signaling, terminal device 1 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, terminal device 1 can send uplink data 1 (such as the EPC of terminal device 1). If it does not match, terminal device 1 may not respond.

[0446] 1708. The reader sends uplink data 1 to AMF.

[0447] 1709. The reader sends a QueryRep signaling.

[0448] After the reader sends uplink data 1 to the AMF, it can trigger subsequent inventory processes, such as continuing to send QueryRep signaling to trigger the terminal device using the resource slot 1 to send the corresponding uplink data.

[0449] 1710. The reader sends a query signaling, which includes a session, a flag, a Q value, and an identifier of group 2.

[0450] After the reader / writer completes the inventory process corresponding to group 1, it can perform the inventory process corresponding to group 2. Accordingly, the Query signaling can carry the identifier of group 2 to instruct the terminal devices associated with group 2 to participate in this round of inventory process.

[0451] 1711. When the session, flag, and group identifier match, the terminal device generates a Counter based on the Q value.

[0452] After the terminal device receives the Query signaling from the reader / writer, it can determine whether its own session, flag bit and the identifier of the selected group match the session, flag bit and group identifier (such as the identifier of group 2) carried by the Query signaling. When the session, flag bit and group identifier match, the terminal device (such as terminal device 2, etc.) can initialize the counter based on the Q value, that is, select the time domain resource based on the Q value. When the session, flag bit and group identifier do not match, that is, the session and flag bit do not match or the group identifier does not match or both do not match, the terminal device can do nothing.

[0453] 1712. Terminal device 2 sends RN16 signaling.

[0454] Terminal device 2 belongs to group 2. Assuming that the resource previously selected by terminal device 2 is slot 0, that is, the initialized Counter is 0, terminal device 2 can send RN16 signaling.

[0455] 1713. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device 2.

[0456] After the reader receives the RN16 signaling fed back by the terminal device 2 , it may send an ACK signaling, which may include the 16-bit random number fed back by the terminal device 2 .

[0457] 1714. Terminal device 2 sends uplink data 2.

[0458] After receiving the ACK signaling, terminal device 2 can determine whether the 16-bit random number included in the ACK signaling matches. If it matches, terminal device 2 can send uplink data 2 (such as the EPC of terminal device 2). If it does not match, terminal device 2 may not respond.

[0459] 1715. The reader sends uplink data 2 to AMF.

[0460] 1716. The reader sends a QueryRep signaling.

[0461] After the reader sends uplink data 2 to the AMF, it can trigger subsequent inventory processes, such as continuing to send QueryRep signaling to trigger the terminal device using the resource slot 1 to send the corresponding uplink data.

[0462] It is understandable that the above steps 1701-1716 are merely exemplary and illustrate only a portion of the inventory process corresponding to group 1 and group 2.

[0463] The following describes a method for intelligently configuring resources based on RIC. See Figure 18, which is a flow chart of another communication method disclosed in an embodiment of the present application. As shown in Figure 18, the processing flow may include but is not limited to the following steps:

[0464] 1801.AMF sends paging signaling to the reader, which includes the UE list.

[0465] Exemplarily, the AMF may receive a paging request from other network elements / devices, and the paging request may include a UE list (list), and the UE list may include the identifiers of multiple UEs. For example, the UE list may be {identifier of terminal device 1, identifier of terminal device 2, identifier of terminal device 3, identifier of terminal device 4, ...}. After receiving the paging request, the AMF may send paging signaling to the corresponding reader based on the paging request, and the paging signaling includes the UE list. For example, the AMF may first query which reader's signal coverage range the terminal device in the UE list is located, and then the AMF may send paging signaling to the corresponding reader.

[0466] It should be noted that the above-mentioned AMF can also be other network elements (such as other network elements in the core network), and this embodiment of the application does not limit this. In other words, other network elements can also be responsible for paging and access of terminal devices (such as environmental Internet of Things devices).

[0467] 1802.RIC sends resource configuration information to CU.

[0468] In an embodiment of the present application, relevant resource configuration information can be determined based on RIC to reduce the probability of collision and thus improve access efficiency. For example, RIC can infer the current reasonable resource allocation based on historical data. For example, RIC can determine the Q value, the number of frequency domain resources, the number of groups, etc. based on historical data.

[0469] Exemplarily, the resource configuration information may include one or more of a Q value, the number of frequency domain resources, and the number of groups.

[0470] For example, RIC can collect historical data on access efficiency and collision rate for each resource configuration. RIC can then combine historical data with information about the current paging (such as a UE list and one or more mask information) to determine the corresponding resource configuration information. For example, for a terminal device corresponding to paging mask information 1 in the past, if the Q value is 10 and the collision rate is 10%, and if the Q value is 11, the collision rate is 1%, then if the terminal device corresponding to mask information 1 is currently being paged, RIC can determine that the Q value in the resource configuration information is 11.

[0471] In some possible implementations, after receiving the paging signaling, the CU may request the RIC for resource configuration information based on the paging signaling, which is not limited in the embodiments of the present application.

[0472] 1803. CU sends paging signaling through DU, and the paging signaling includes a UE list.

[0473] For example, the RRC layer can be in the CU and the MAC layer can be in the DU. Therefore, when the paging signaling is an RRC message, it needs to be generated by the CU and then sent to the DU, which then sends it through the air interface. The remaining downlink messages (such as Query signaling, QueryRep signaling, etc.) can be MAC messages and can be directly generated and sent by the DU.

[0474] It should be noted that the above-mentioned RIC can be a near real-time RIC or a non-real-time RIC. The near real-time RIC can be set in the access network equipment (for example, in the CU or DU), and the non-real-time RIC can be set in the OAM, the cloud server, the core network equipment, or other network equipment. The embodiments of the present application are not limited here.

[0475] 1804. The reader sends a query signaling, which includes a session, a flag bit, and a Q value.

[0476] 1805. When the session and flag match, the terminal device generates a Counter based on the UE list.

[0477] 1806. Terminal device 1 sends RN16 signaling.

[0478] 1807. The reader sends an ACK signaling, which may include a 16-bit random number fed back by terminal device 1.

[0479] 1808. Terminal device 1 sends uplink data 1.

[0480] 1809. The reader sends a QueryRep signaling.

[0481] 1810. Terminal device 2 sends RN16 signaling.

[0482] 1811. The reader sends an ACK signaling, which may include a 16-bit random number fed back by the terminal device 2.

[0483] 1812. Terminal device 2 sends uplink data 2.

[0484] 1813. The reader sends uplink data 1 and uplink data 2 to AMF.

[0485] Steps 1803-1813 are similar to the above steps 1602-1612, and reference may be made to the relevant descriptions in the above steps 1602-1612.

[0486] It is understandable that the above steps 1803-1813 are merely exemplary and illustrate only a portion of the inventory process in one round of inventory.

[0487] It should be noted that the relevant information (ie, the same information or similar information) and related descriptions in the above different embodiments can refer to each other.

[0488] It should be understood that the above-mentioned Figures 7, 8, 11, 13, 14, 15, 16, 17 and 18 mainly use the terminal device (such as the second device) and the reader / writer (such as the first device) as the execution subject of the interaction diagram as an example to illustrate the above-mentioned processing flow, but the present application does not limit the execution subject of the interaction diagram. For example, the first device in Figure 7 can also be a chip, chip system, or processor that supports the first device to implement the method, or it can be a logic module or software that can implement all or part of the functions of the first device. For another example, the second device in Figure 7 can also be a chip, chip system, or processor that supports the second device to implement the method, or it can be a logic module or software that can implement all or part of the functions of the second device.

[0489] The above mainly introduces the communication method provided in the embodiment of the present application. It can be understood that in order to realize the corresponding functions mentioned above, the above-mentioned reader / writer (such as the first device) and the terminal device (such as the second device) may include hardware structures and / or software modules corresponding to the execution of each function. In combination with the units and steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

[0490] The embodiment of the present application can divide the functional modules of the first device, the second device, etc. according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation.

[0491] FIG19 shows a possible structural diagram of a communication device 1900, in which each functional module is divided according to its function. The communication device 1900 includes a receiving unit 1901 and a sending unit 1902. In one possible design, the communication device 1900 can be the first device described above, or a chip in the first device, or a processing system in the first device, etc.

[0492] The receiving unit 1901 is configured to receive a first message through a first resource;

[0493] The sending unit 1902 is configured to send first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource;

[0494] The receiving unit 1901 is further configured to receive a second message through the second resource.

[0495] In a possible implementation, the second information implicitly indicates the first information.

[0496] In a possible implementation, the sending unit 1902 is further configured to send third information, where the third information is used to indicate that the second message is a random access message or uplink data.

[0497] In a possible implementation, the sending unit 1902 is further configured to send fourth information, where the fourth information is used to indicate the second resource.

[0498] In a possible implementation, the first device includes multiple processes, the multiple processes include a first process, the second device is associated with the first process, and the first information is associated with the first process.

[0499] In one possible implementation, the first information and the second information are carried in a third message, or a fourth message, or a fifth message; the third message is used to trigger random access of one or more terminal devices; the fourth message is used to trigger the terminal device to perform random access to the next time slot; and the fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

[0500] In one possible implementation, before the receiving unit 1901 receives the first message through the first resource, the sending unit 1902 is also used to send fifth information, which is used to instruct the second device to send the first message on the first resource, and to instruct the third device to send the sixth message on the third resource, where the first resource is different from the third resource.

[0501] In a possible implementation, at least two of the first information, the second information, the third information, and the fourth information are included in the same message.

[0502] The specific operations of each unit in the above-mentioned communication device 1900 can be found in the corresponding descriptions of the first device or reader / writer in the above-mentioned Figures 7 to 18 and their possible embodiments, and will not be repeated here.

[0503] In another possible design, the communication device 1900 may be the second device described above, or may be a chip in the second device, or may be a processing system in the second device, etc.

[0504] The sending unit 1902 is configured to send a first message through a first resource;

[0505] Receiving unit 1901 is configured to receive first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource;

[0506] The sending unit 1902 is further configured to send a second message through the second resource.

[0507] In a possible implementation, the second information implicitly indicates the first information.

[0508] In a possible implementation, the receiving unit 1901 is further configured to receive third information, where the third information is used to indicate that the second message is a random access message or uplink data.

[0509] In a possible implementation, the receiving unit 1901 is further configured to receive fourth information, where the fourth information is used to indicate the second resource.

[0510] In a possible implementation, the first device includes multiple processes, the multiple processes include a first process, the second device is associated with the first process, and the first information is associated with the first process.

[0511] In one possible implementation, the first information and the second information are carried in a third message, or a fourth message, or a fifth message; the third message is used to trigger random access of one or more terminal devices; the fourth message is used to trigger the terminal device to perform random access to the next time slot; and the fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

[0512] In one possible implementation, before the sending unit 1902 sends the first message through the first resource, the receiving unit 1901 is also used to receive fifth information, which is used to instruct the second device to send the first message through the first resource, and to instruct the third device to send the sixth message through the third resource, and the first resource is different from the third resource.

[0513] In a possible implementation, at least two of the first information, the second information, the third information, and the fourth information are included in the same message.

[0514] In one possible implementation, in the communication device 1900 shown in FIG19 , the sending unit may be a transmitter, and the receiving unit may be a receiver. The sending unit and the receiving unit may be integrated into a single device, such as a transceiver. In the embodiment of the present application, the processor and the transceiver may be coupled, etc., and the embodiment of the present application does not limit the connection method between the processor and the transceiver. For example, the communication device 1900 may also include a processing unit, which may be one or more processors / logic circuits. During the execution of the above method, the process of sending information (such as sending the first information, the second information, etc.) in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor can output the above information to the transceiver so that the transceiver can transmit it. After being output by the processor, the above information may also need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information (such as receiving the first information, the second information, etc.) in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to be processed further before being input into the processor.

[0515] In another possible implementation, in the communication device shown in Figure 19, the sending unit can be an output interface, the receiving unit can be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input-output interface, also called a communication interface, or an interface circuit, or an interface, etc.

[0516] Figure 20 shows a schematic diagram of a possible hardware structure of a communication device 2000 provided in an embodiment of the present application. The communication device 2000 may include a processor 2001 and a transceiver 2002. It should be noted that Figure 20 only shows the main components of the communication device 2000. The communication device 2000 may further include a memory 2003 and input / output devices (not shown in the figure).

[0517] The processor 2001 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. The memory 2003 is primarily used to store software programs and data. The transceiver 2002 may include a control circuit and an antenna. The control circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0518] When the communication device is powered on, processor 2001 can read the software program in memory 2003, interpret and execute the software program's instructions, and process the software program's data. When data needs to be transmitted wirelessly, processor 2001 performs baseband processing on the data to be transmitted and outputs a baseband signal to the control circuit. The control circuit then performs radio frequency processing on the baseband signal and transmits the radio frequency signal via the antenna in the form of electromagnetic waves. When data is sent to the communication device, the control circuit receives the radio frequency signal via the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to processor 2001. Processor 2001 converts the baseband signal into data and processes the data.

[0519] In one possible implementation, the control circuit and antenna may be provided independently of the processor that performs baseband processing. For example, in a distributed scenario, the control circuit and antenna may be remotely arranged independent of the communication device.

[0520] The processor 2001 , the transceiver 2002 , and the memory 2003 may be connected via a communication bus.

[0521] Exemplarily, the memory 2003 may include, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable compact disc read-only memory (CD-ROM).

[0522] Exemplarily, the processor 2001 may be a central processing unit (CPU), a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processor may 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, and the like.

[0523] In one design, the communication device 2000 can be used to perform the functions of the first device in the aforementioned embodiment. For details, please refer to the relevant descriptions in Figures 7 to 18 above, and no further details will be given here.

[0524] In another design, the communication device 2000 can be used to perform the functions of the second device in the aforementioned embodiment. For details, please refer to the relevant descriptions in Figures 7 to 18 above, and no further details will be given here.

[0525] In one possible design, the processor 2001 may store instructions, which may be computer programs. The computer programs run on the processor 2001, enabling the communication device 2000 to perform the operations performed by the first device or the operations performed by the second device in any of the above method embodiments. For details, please refer to the relevant descriptions in Figures 7-18 above, which will not be repeated here.

[0526] It should be noted that the communication device 2000 shown in FIG20 is only one implementation of an embodiment of the present application. In actual applications, the communication device 2000 may also include more or fewer components, which is not limited here.

[0527] An embodiment of the present application also discloses a communication system, which includes a first device and a second device. The first device is used to execute the operation executed by the first device in any of the above method embodiments, and the second device is used to execute the operation executed by the second device in any of the above method embodiments.

[0528] An embodiment of the present application also discloses a chip, which includes a processor, wherein the processor is used to execute a computer program or computer instructions stored in a memory, so that the chip performs the operation performed by the first device in the above method embodiment, or the chip performs the operation performed by the second device in the above method embodiment.

[0529] As a possible implementation, the memory is located outside the chip.

[0530] An embodiment of the present application further discloses a computer-readable storage medium having instructions stored thereon. When the instructions are executed, the operation performed by the first device in the above method embodiment or the operation performed by the second device in the above method embodiment is performed.

[0531] The embodiment of the present application further discloses a computer program product comprising instructions, which, when executed, performs the operations performed by the first device in the above method embodiment or the operations performed by the second device in the above method embodiment.

[0532] Obviously, the embodiments described above are only some of the embodiments of this application, and not all of them. Reference to "embodiments" herein means that the specific features, structures, or characteristics described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it refer to independent or alternative embodiments that are mutually exclusive with other embodiments. It is understood, both explicitly and implicitly, that the embodiments described herein can be combined with other embodiments. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application. In the specification, claims, and accompanying drawings of this application, the terms "first," "second," "third," and so on are used to distinguish between different objects, not to describe a specific order. Furthermore, the terms "including," "having," and any variations thereof are intended to cover non-exclusive inclusions. For example, a list of steps or elements may be included, or alternatively, steps or elements not listed may be included, or alternatively, other steps or elements inherent to the process, method, product, or device may be included. It is understandable that, in some embodiments, the equal sign of the above-mentioned conditional judgment can be taken as greater than one end or less than one end. For example, the above-mentioned conditional judgment of a threshold being greater than, less than, or equal to can also be changed to a conditional judgment of the threshold being greater than, equal to, or less than. This is not limited here. It is also understandable that, for an architecture with multiple devices or modules, if one of the devices or modules generates information and another device or module uses the information, there can be multiple ways for the other device to obtain the information. For example, the device or module that generates the information can send the information directly to the device or module that uses the information (equivalent to direct sending), or the device or module that generates the information can send the information to the device or module that uses the information through other devices or modules (equivalent to indirect sending).

[0533] It will be appreciated that only the parts relevant to the present application, not all, are shown in the accompanying drawings. It will be appreciated that some exemplary embodiments are described as processes or methods depicted as flow charts. Although the flow charts describe the various operations (or steps) as sequential processes, many of the operations therein can be implemented in parallel, concurrently, or simultaneously. In addition, the order of the various operations can be rearranged. When its operation is completed, the process can be terminated, but can also have additional steps not included in the accompanying drawings. The process can correspond to a method, function, procedure, subroutine, subprogram, etc.

[0534] As used in this specification, the terms "component," "module," "system," "unit," and the like are used to refer to computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a unit can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program, and / or distributed between two or more computers. In addition, these units can be executed from various computer-readable media having various data structures stored thereon. For example, a unit can communicate through local and / or remote processes based on signals having one or more data packets (e.g., data from a second unit interacting with another unit in a local system, a distributed system, and / or a network. For example, the Internet interacts with other systems via signals).

[0535] The specific implementation methods described above further illustrate the purpose, technical solutions and beneficial effects of this application. It should be understood that the above description is only the specific implementation methods of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions of this application should be included in the scope of protection of this application.

Claims

1. A communication method, characterized in that: Applied to a first device, the method includes: receiving a first message through a first resource; Sending first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource; A second message is received through the second resource.

2. The method according to claim 1, characterized in that The second information implicitly indicates the first information.

3. The method according to claim 1 or 2, characterized in that The method further comprises: Send third information, where the third information is used to indicate that the second message is a random access message or uplink data.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: Fourth information is sent, where the fourth information is used to indicate the second resource.

5. The method according to any one of claims 1 to 4, characterized in that The first device includes multiple processes, the multiple processes include a first process, the second device is associated with the first process, and the first information is associated with the first process.

6. The method according to any one of claims 1 to 5, characterized in that The first information and the second information are carried in a third message, or a fourth message, or a fifth message; The third message is used to trigger random access of one or more terminal devices; The fourth message is used to trigger the terminal device to perform random access in the next time slot; The fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

7. The method according to any one of claims 1 to 6, characterized in that Before receiving the first message through the first resource, the method further includes: Send fifth information, where the fifth information is used to instruct the second device to send the first message on the first resource and to instruct the third device to send a sixth message on a third resource, where the first resource is different from the third resource.

8. The method according to any one of claims 4 to 7, characterized in that: At least two of the first information, the second information, the third information, and the fourth information are included in the same message.

9. A communication method, characterized in that: Applied to the second device, the method includes: sending a first message through a first resource; receiving first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource; A second message is sent through the second resource.

10. The method according to claim 9, characterized in that The second information implicitly indicates the first information.

11. The method according to claim 9 or 10, characterized in that The method further comprises: Receive third information, where the third information is used to indicate that the second message is a random access message or uplink data.

12. The method according to any one of claims 9 to 11, characterized in that: The method further comprises: Fourth information is received, where the fourth information is used to indicate the second resource.

13. The method according to any one of claims 9 to 12, characterized in that: The first device includes a plurality of processes, the plurality of processes including a first process, the second device is associated with the first process, and the first information is associated with the first process.

14. The method according to any one of claims 9 to 13, characterized in that: The first information and the second information are carried in a third message, or a fourth message, or a fifth message; The third message is used to trigger random access of one or more terminal devices; The fourth message is used to trigger the terminal device to perform random access in the next time slot; The fifth message is used to trigger the terminal device to perform random access to the next sub-time slot.

15. The method according to any one of claims 9 to 14, characterized in that: Before sending the first message through the first resource, the method further includes: Fifth information is received, where the fifth information is used to instruct the second device to send the first message on the first resource and to instruct the third device to send a sixth message on a third resource, where the first resource is different from the third resource.

16. The method according to any one of claims 12 to 15, characterized in that: At least two of the first information, the second information, the third information, and the fourth information are included in the same message.

17. A communication device, characterized in that: include: A receiving unit, configured to receive a first message through a first resource; A sending unit, configured to send first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource; The receiving unit is further configured to receive a second message through the second resource.

18. A communication device, characterized in that: include: A sending unit, configured to send a first message through a first resource; A receiving unit, configured to receive first information and second information, wherein the first information is used to instruct the terminal device that sent the first message on the first resource to send the second message on the second resource, and the second information is used to indicate the first resource; The sending unit is further configured to send a second message through the second resource.

19. A communication device, characterized in that: It comprises a processor and a communication interface; the communication interface is used to receive and / or send data; the processor calls a computer program or computer instruction stored in a memory to implement the method according to any one of claims 1 to 8, or implements the method according to any one of claims 9 to 16.

20. A communication system, characterized in that: The method comprises a first device and a second device, wherein the first device is used to implement the method according to any one of claims 1 to 8, and the second device is used to implement the method according to any one of claims 9 to 16.

21. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program or computer instructions, and the computer program or computer instructions are executed by a processor to implement the method according to any one of claims 1 to 8, or to implement the method according to any one of claims 9 to 16.

22. A computer program product, characterized in that The computer program product includes computer program codes or computer instructions. When the computer program codes or computer instructions are executed, the method according to any one of claims 1 to 8 or the method according to any one of claims 9 to 16 is implemented.

Images