Communication method and apparatus

Abstract

A communication method and apparatus, applied to the field of environmental Internet of Things. The method comprises: sending a first message, the first message being used for triggering a first random access occasion, and the first message indicating a first identifier; receiving a first random access request message from a first terminal device at the first random access occasion, the first terminal device being associated with the first identifier; and before responding to the first random access request message, sending a second message, the second message indicating a second identifier. By means of the method, a message in one process can be located between two messages in another process, for example, a second message in a second process is located between a first uplink message and a first response message in a first process, so that while a network device is communicating with one terminal device in one process, the network device can communicate with another terminal device in another process, thereby increasing the resource utilization rate and increasing the system capacity.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on November 29, 2023, with application number 202311614765.X and invention name "A Communication Method and Device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] Wireless communication systems have incorporated the Internet of Things (IoT) technology. Tags in the IoT can function as end devices, and base stations can function as readers. Tags can communicate with base stations. In scenarios such as tag inventory, a reader can page multiple tags using paging signaling. After receiving the paging signaling, the reader uses query signaling to indicate an inventory cycle. An inventory cycle consists of multiple time slots, and the tag selects a time slot within the inventory cycle to initiate random access.

[0005] During random access, after receiving one or more random access requests in a time slot, the reader will only send a conflict resolution message to one tag. This means that at most one tag can successfully access the same time slot. Before sending a conflict resolution message, the reader will not trigger a new random access opportunity. Therefore, tags that have not yet sent a random access request can only wait for access.

[0006] From the above description, it can be seen that according to the current random access process, the number of tags accessed per unit time is small, the random access capacity is not high, and the efficiency of the random access process is low. Summary of the Invention

[0007] The present application provides a communication method and apparatus for improving communication efficiency.

[0008] In the first aspect, the present application provides a communication method, which is applicable to scenarios such as environmental Internet of Things. The execution subject of the method is a network device or a module or chip in the network device, and the network device is used as the execution subject for description. In the method, a first message is sent; the first message is used to trigger a first random access opportunity, and the first message indicates a first identifier; a first random access request message from a first terminal device is received at the first random access opportunity; the first terminal device is associated with the first identifier; before responding to the first random access request message, a second message is sent; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with the terminal device of the second identifier.

[0009] Through the above process, a network device can trigger multiple processes in parallel, each corresponding to an identifier. Between two messages in the first process corresponding to the first identifier, a message from the second process corresponding to the second identifier can be transmitted. This allows the network device to communicate with the second terminal device associated with the second process while communicating with the first terminal device associated with the first process, maximizing the use of idle time domain resources between the two messages. This improves resource utilization, increases system capacity, and improves communication efficiency. Furthermore, because terminal devices only respond to messages with the identifier corresponding to their associated process, messages from one process will not interfere with terminal devices from another process, thereby improving system reliability.

[0010] In a possible implementation manner, the method further includes: sending a first response message corresponding to the first random access request message.

[0011] In one possible implementation, the first identifier is used to identify the first process, the second identifier is used to identify the second process, the value of the first identifier and the value of the second identifier are both less than or equal to the first value, the first value represents the number of processes, the first value is indicated by the first message or the third message, and the third message is a message located before the first message.

[0012] In the above method, the maximum number of processes is configured by the network side, so that the network side can flexibly configure the number of processes according to the number of terminal devices and message processing time, reducing the complexity of processing multi-process messages.

[0013] In one possible implementation, the maximum duration of the interval between the first random access request message and the first response message corresponding to the first random access request message is a first duration; wherein the first duration is greater than or equal to the duration required to send the second message and receive the second random access request message from the terminal device.

[0014] In the above method, by configuring the first time duration to be greater than or equal to the time duration required to send the second message and receive the second random access request message from the terminal device, there can be sufficient time to transmit the message of another process within the first time duration between the two messages, thereby avoiding message sending conflicts and improving system reliability.

[0015] In a possible implementation manner, the first response message includes the first identifier and part or all of the content of the first random access request.

[0016] In the above method, the first response message includes a first identifier, which can enable the terminal device associated with the first identifier to determine to continue processing the message, and the terminal device not associated with the first identifier to ignore the message, thereby avoiding interference with terminal devices associated with other identifiers.

[0017] In a possible implementation, the first message is a query message or a query repetition message, and the second message is a query repetition message.

[0018] In one possible implementation, the method further includes: receiving a second random access request message from a second terminal device at the second random access opportunity; the second terminal device is associated with the second identifier; and sending a second response message corresponding to the second random access request message; wherein the second message and the second random access request message are located between the first random access request message and the first response message.

[0019] In one possible implementation, the first terminal device is an environmental Internet of Things terminal device.

[0020] In one possible implementation, the first message indicates a first identifier, including: the first identifier corresponds to a first process that is a preset process, and the first message includes the first identifier; or, the first identifier corresponds to a first process that is a non-preset process, and the first message does not include the first identifier.

[0021] In one possible implementation, the method further includes: receiving a fourth message from a core network device, the fourth message including first data and the first identifier; and sending a fifth message to the first terminal device, the fifth message including the first data and the first identifier.

[0022] In a possible implementation, the method further includes: receiving an uplink message from the first terminal device, where the uplink message includes the first identifier and uplink data.

[0023] Through the above method, since the uplink message of the first terminal device also carries the first identifier, the network side can determine the identifier associated with the first terminal device based on the first identifier, thereby distinguishing devices associated with different identifiers.

[0024] On the second aspect, the present application provides a communication method, which is applicable to scenarios such as environmental Internet of Things. The execution subject of the method is a terminal device or a module or chip in the terminal device, and the terminal device is used as the execution subject for description. In the method, a first message is received; the first message is used to trigger a first random access opportunity, the first message indicates a first identifier, and the first random access opportunity is used to initiate random access with the terminal device of the first identifier; it is determined to be associated with the first identifier, and a first random access request message is sent at the first random access opportunity; a second message is received; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with the terminal device of the second identifier; it is determined that it is not associated with the second identifier, and the second message is ignored or discarded.

[0025] In one possible implementation, the first identifier is used to identify the first process, the second identifier is used to identify the second process, the value of the first identifier and the value of the second identifier are both less than or equal to the first value, the first value represents the number of processes, the first value is indicated by the first message or the third message, and the third message is a message located before the first message.

[0026] In a possible implementation, the determination of association with the first identifier includes: if the first identifier is equal to the third identifier of the process associated with the first terminal device, then association with the first identifier; wherein the third identifier is determined based on the first value.

[0027] In one possible implementation, the third identifier is determined based on the first value, including: using a value less than or equal to the first value as the third identifier; or determining the third identifier based on the device identifier of the first terminal device and the first value.

[0028] In one possible implementation, the maximum duration of the interval between the first random access request message and the first response message corresponding to the first random access request message is a first duration; wherein the first duration is greater than or equal to the duration required to send the second message, or the first duration is greater than or equal to the duration required to send the second message and receive a second random access request message from the terminal device.

[0029] In a possible implementation, the method further includes: receiving a first response message corresponding to the first random access request message from the network device, where the first response message includes the first identifier and part or all of the content of the first random access request.

[0030] In a possible implementation, the first message is a query message or a query repetition message, and the second message is a query repetition message.

[0031] In a possible implementation, the first terminal device is an environmental Internet of Things terminal device.

[0032] In a third aspect, the present application further provides a communication device capable of implementing any of the methods provided in any of the first to second aspects above. The communication device may be implemented in hardware or by executing corresponding software implementations in hardware. The hardware or software includes one or more units or modules corresponding to the above functions.

[0033] In one possible implementation, the communication device includes a processor configured to support the communication device in executing the corresponding functions of the network device or terminal device in the above-described method. The communication device may also include a memory, which may be coupled to the processor and stores program instructions and data necessary for the communication device. Optionally, the communication device also includes an interface circuit for supporting communication between the communication device and a device such as a terminal device.

[0034] In one possible implementation, the communication device includes corresponding functional modules for implementing the steps in the above method. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0035] In one possible implementation, the structure of the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples. For details, please refer to the description of the method provided in any one of the first aspect to the second aspect, which will not be repeated here.

[0036] In a fourth aspect, a communication device is provided, comprising a processor and an interface circuit, wherein the interface circuit is configured to receive signals from a communication device other than the communication device and transmit them to the processor, or to transmit signals from the processor to the communication device other than the communication device, wherein the processor implements the functional modules of the method in any possible implementation of any of the first and second aspects by means of logic circuits or by executing computer programs or instructions. Optionally, the communication device further comprises a memory configured to store the computer program or instructions.

[0037] In a fifth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed by a processor, the method in any possible implementation of any one of the first to second aspects is implemented.

[0038] In a sixth aspect, a computer program product storing instructions is provided, which, when read and executed by a computer, implements the method in any possible implementation of any one of the first to second aspects.

[0039] In a seventh aspect, a circuit is provided, which is used to execute the method in any possible implementation of any one of the first to second aspects above, and the circuit may include a chip circuit. Optionally, the circuit may also be coupled to a memory.

[0040] In an eighth aspect, a chip is provided, comprising a processor. When the processor executes a computer program or instruction, the processor is configured to implement the method of any possible implementation of any of the first and second aspects. Optionally, the chip may further include a memory. The chip may be composed of a single chip or may include a chip and other discrete devices.

[0041] In a ninth aspect, a communication device is provided, comprising a processor, which implements the method in any possible implementation of any one of the first to second aspects through a logic circuit or by executing a computer program or instruction.

[0042] In a tenth aspect, a communication device is provided, comprising a unit or module for executing the method in any possible implementation of any one of the first to second aspects above.

[0043] In an eleventh aspect, embodiments of the present application further provide a communication system. The communication system includes: a network device for implementing the method in the aforementioned first aspect and any possible implementation of the first aspect; and a terminal device for implementing the method in the aforementioned second aspect and any possible implementation of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] FIG1 is a schematic diagram of an access network device architecture provided in an embodiment of the present application;

[0045] FIG2 is a schematic diagram of an environmental Internet of Things architecture provided by an embodiment of the present application;

[0046] FIG3 is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0047] FIG4 is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0048] FIG5 is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0049] FIG6 is a schematic diagram of a network architecture provided in an embodiment of the present application;

[0050] FIG7 is a schematic diagram of an inventory process provided in an embodiment of the present application;

[0051] FIG8 is a flow chart of a communication method provided in an embodiment of the present application;

[0052] FIG9 is a flow chart of a communication method provided in an embodiment of the present application;

[0053] FIG10 is a flow chart of a communication method provided in an embodiment of the present application;

[0054] FIG11 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0055] FIG12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0056] FIG13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0057] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. The terms "first", "second" and corresponding terminology labels in this application are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, and this is merely a way of distinguishing objects of the same properties when describing the embodiments of the present application. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, so that a process, method, system, product or device that includes a series of units is not necessarily limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or devices.

[0058] The method provided in the embodiment of the present application can be applied to various types of mobile communication systems, for example, the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), the fourth generation (4G) communication system (such as long term evolution (LTE)), the fifth generation (5G) communication system (such as 5G new radio (NR)), the hybrid architecture of LTE and NR, 6G or new communication systems that will emerge in future communication developments, etc. The communication system may also include a machine to machine (M2M) network, a machine type communication (MTC) or other networks. Exemplarily, the method provided in the embodiment of the present application can be applied to a communication system that supports ambient IoT (AIoT) technology.

[0059] The methods and devices provided in the embodiments of the present application are based on the same or similar technical concepts. Since the principles of solving problems by the methods and devices are similar, the implementation of the devices and methods can refer to each other, and the repeated parts will not be repeated.

[0060] Below, some terms used in the embodiments of the present application are first explained to facilitate understanding by those skilled in the art.

[0061] The communication device involved in this application may be a device or device or chip or module that can communicate with other devices wirelessly and / or wired, including but not limited to network devices, terminal devices and other devices or equipment.

[0062] In the embodiments of the present application, a network device is a device in a wireless network. The network device may also be referred to as a network apparatus, a radio access network device, or an access network device. For example, the network device may be a radio access network (RAN) node that connects a terminal device to a wireless network, and may also be referred to as an access network device. Network equipment includes but is not limited to: base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next generation NodeBs (gNBs) in fifth generation (5G) mobile communication systems, access network equipment in open radio access networks (O-RANs), next generation base stations in sixth generation (6G) mobile communication systems, base stations in future mobile communication systems, or access nodes in wireless fidelity (WiFi) systems, etc.; or it may be a module or unit that completes part of the functions of a base station, for example, a centralized unit (CU), a distributed unit (DU), a centralized unit control plane (CU-CP) module, or a centralized unit user plane (CU-UP) module. The access network equipment may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. The specific technology and specific device form adopted by the network equipment are not limited in this application.

[0063] As shown in Figure 1, in some implementations, network equipment may include a centralized unit (CU) and a distributed unit (DU). RAN equipment, including CU and DU nodes, splits the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while some or all of the remaining protocol layer functions are distributed in the DU, which is then centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for control plane functions, primarily including radio resource control (RRC) and the control plane's corresponding packet data convergence protocol (PDCP) (i.e., PDCP-C). PDCP-C is primarily responsible for encryption, decryption, integrity protection, and data transmission of control plane data. The CU-UP is responsible for user plane functions, primarily including the service data adaptation protocol (SDAP) and the user plane's corresponding PDCP (i.e., PDCP-U). SDAP is primarily responsible for processing core network data and mapping flows to bearers. The PDCP-U is primarily responsible for data plane encryption and decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via the E1 interface. The CU-CP represents the gNB's connection to the core network via the NG interface and to the DU via the F1 interface control plane (i.e., F1-C). The CU-UP connects to the DU via the F1 interface user plane (i.e., F1-U). Alternatively, the PDCP-C may also reside in the CU-UP.

[0064] It is understandable that in different systems, CU (including CU-CP or CU-UP) or DU may have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN) system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, and CU-UP may also be called O-CU-UP. For convenience of description, this application uses CU, CU-CP, CU-UP and DU as examples. The network device may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services and implementing the functions of the RRC layer. The DU is responsible for processing physical layer protocols and real-time services and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer. In some deployments, the CU can be further divided into a Centralized Unit Control Plane (CU-CP) node and a Centralized Unit User Plane (CU-UP) node, where the CU-CP is responsible for control plane functions and the CU-UP is responsible for user plane functions.

[0065] The terminal device involved in the embodiments of the present application may be a wireless terminal device capable of receiving network device scheduling and instruction information. The terminal device may be referred to as a terminal device, and may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a device that includes wireless communication capabilities (providing voice / data connectivity to the user). For example, a handheld device with wireless connection capabilities, or an in-vehicle device, in-vehicle module, etc. Currently, some examples of terminal devices include: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in the Internet of Vehicles, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, device-to-device (D2D) communication terminal devices, vehicle-to-everything (V2X) communication terminal devices, smart vehicles, telematics boxes (T-boxes), machine-to-machine / machine-type communications (M2M / MTC) terminal devices, Internet of Things (IoT) The IoT (Internet of Things) terminal devices, etc. For example, the terminal device can be an onboard device, complete vehicle equipment, an onboard module, a vehicle, an onboard unit (OBU), a roadside unit (RSU), a T-box, a chip, or a system on chip (SOC), etc. The above chip or SOC can be installed in the vehicle, OBU, RSU, or T-box. Wireless terminals in industrial control can be cameras, robots, etc. Wireless terminals in smart homes can be TVs, air conditioners, vacuum cleaners, speakers, set-top boxes, etc.The terminal device can also be a V2X device, such as a smart car (or intelligent car), a digital car, an unmanned car (or driverless car or pilotless car or automobile), a self-driving car (or autonomous car), a pure electric vehicle (or battery EV), a hybrid electric vehicle (HEV), a range extended EV (REEV), a plug-in hybrid electric vehicle (PHEV), a new energy vehicle (new energy vehicle), or a roadside unit (RSU). The terminal device can also be a device in device-to-device (D2D) communication, such as an electricity meter, a water meter, etc. In addition, in an embodiment of the present application, the terminal device can also be a tag in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0066] Tags can also be called electronic tags, RFID tags, or tag devices. Alternatively, tags can also be called AIoT terminal devices or AIoT devices. In this application, tags can be used as a terminal device to communicate with network devices.

[0067] In one classification method, tags can be divided into passive tags, semi-passive tags, and active tags. Passive tags and semi-passive tags can use a backscatter-based communication method, while active tags use an actively generated carrier communication method.

[0068] Another classification method is to divide tags into the following three types of devices:

[0069] Device A: has no energy storage, cannot generate signals independently, and uses backscattering to transmit signals;

[0070] Device B: It has energy storage but cannot generate signals independently. It uses backscattering to transmit signals, and its stored energy can amplify the reflected signal.

[0071] Device C: has energy storage, can independently generate signals, and has active RF components for transmission.

[0072] The tag in this application can be any of the three types of devices mentioned above.

[0073] The tag uses a low-precision, low-power, medium-to-low-frequency ring oscillator or a completely local oscillator-free method to receive downlink signals. When the tag is operating, the communication energy and carrier are supplied by the reader, and communication is based on the reflected carrier. For example, as shown in Figure 2, the reader can send a carrier signal to the tag, and the tag receives the carrier signal through the antenna. The solid line in the figure is the carrier signal sent by the reader, and the dotted line represents the reflected signal transmitted by the tag based on the carrier signal. The tag can adjust the information to be transmitted in the reflected signal. In this way, the tag uses a low-precision, low-power, medium-to-low-frequency ring oscillator or a completely local oscillator-free method to receive downlink signals, which can further reduce the power consumption of the tag downlink reception.

[0074] A tag is a miniature wireless transceiver, which mainly includes a built-in tag device antenna, a coupling element and a chip. The tag chip has a storage space that can support the reader to read or write tag data. After the tag receives the radio frequency signal sent by the reader through the antenna, it can couple the radio frequency signal through the coupling element, and then provide energy to the tag chip within the coupling channel, and feed back the data stored in the chip to the reader through the antenna. A communication network based on cellular network infrastructure, consisting of readers and tags, can be called a passive Internet of Things (IoT) network, or an environmental Internet of Things, in which the tag device can also be regarded as a terminal device, which can be an active tag device, a passive tag device or a semi-active tag device.

[0075] Environmental IoT systems can be applied to passive or semi-passive IoT scenarios. For example, in logistics and warehousing scenarios, tags can be used to inventory and track goods, and to monitor the status of goods during transportation. In industrial manufacturing scenarios, tags can be used to monitor the environment and equipment status.

[0076] In an environmental IoT system, the following operations can be performed between tags and readers:

[0077] Inventory operation: An inventory operation, also known as an inventory operation, retrieves a tag's identification information. For example, a reader can use commands such as query and acknowledgement (ACK) to obtain this information. To facilitate tag inventory, tags include four session identifiers, S0-S3. Each session identifier corresponds to two inventory states: A and B. The inventory state is indicated by the sessInventoried flag. When a reader selects a tag, it sends a select command containing the session identifier, which the tag then stores. When the reader performs an inventory operation on the tag, it sends a query command containing the session identifier. The tag then flips the inventory state corresponding to the session identifier from A to B. If the reader sends a query command to perform another inventory operation, the tag will not respond because its inventory state is B, thus preventing the same tag from being inventoried multiple times during a single inventory cycle.

[0078] Read operation: The read operation can read the electronic product code (EPC) in the tag's storage area, the tag identifier (TID), the content stored in the tag's reserved area, or the content stored in the user storage area.

[0079] Write operation: The write operation can write to the storage area of ​​the tag.

[0080] Kill operation: The kill operation can make the tag unable to work forever.

[0081] Lock Operation: A lock operation can lock the tag's information, preventing read or write operations on the tag. Alternatively, a lock operation can lock a storage area, preventing or allowing read or write operations on the storage area.

[0082] The above are just examples. Other operations can be performed between the tag and the reader, which will not be explained one by one here.

[0083] The reader / writer involved in this embodiment can be a handheld or fixed device that reads or writes tag information, or can be understood as a device that communicates with tags. The reader / writer can be a terminal device, a network device, or a device with read / write functions. The reader / writer can also be an IAB node or a relay node.

[0084] In this application, predefined content generally refers to information that is defined by standards and does not require additional device configuration. It is pre-recorded / written in the hardware and / or software of the terminal device itself, or it can be understood as not being modifiable by the network device or other terminal devices. Pre-configured content generally refers to information that is pre-recorded / written in the hardware and / or software of the terminal device itself, determined by the equipment manufacturer, and can be modified through software or hardware.

[0085] (Pre) configuration can be divided into network device (pre) configuration and terminal device (pre) configuration. If it is a network device (pre) configuration, it can be (pre) configured through a system information block (SIB) or RRC signaling; if it is a terminal device (pre) configuration, it can be (pre) configured according to PC5-RRC signaling.

[0086] FIG3 shows a schematic diagram of a communication system applicable to an embodiment of the present application. As shown in FIG3 , the communication system includes a network device and a tag. The tag can be a standalone device or integrated with a terminal device, i.e., the tag is part of the terminal device. In this communication system, the network device can have the function of a reader in a radio frequency identification (RFID) system, i.e., the network device can function as a reader to communicate with the tag.

[0087] FIG4 is a schematic diagram of another communication system applicable to embodiments of the present application. As shown in FIG4 , the communication system includes a terminal device and a tag. The tag can be a standalone device or integrated with the terminal device. In this communication system, the terminal device can function as a reader / writer in an RFID system, i.e., the terminal device can function as a reader / writer to communicate with the tag.

[0088] FIG5 shows a schematic diagram of another communication system applicable to an embodiment of the present application. As shown in FIG5 , the communication system includes a network device, an integrated access and backhaul (IAB) node, and a tag. The communication system may also include other devices, such as terminal devices. In this communication system, the network device may have the function of a reader / writer in an RFID system, and the IAB node may serve as a relay node between the network device and the tag. The tag transmits information to the IAB node, and the IAB node forwards the information to the network device via the uu interface.

[0089] In the present application, the communication system including the network device, the terminal device and the tag can also be a system with a separated architecture. In this communication system, as shown in FIG6 , the network device and the terminal device can communicate directly with each other. The network device can also have the function of a reader / writer in an RFID system. There is an uplink connection between the tag and the network device, and a downlink connection between the tag and the terminal device. The terminal device can transmit information to the tag, and the tag then forwards the information to the network device. Alternatively, there is a downlink connection between the tag and the network device, and an uplink connection between the tag and the terminal device. The network device can transmit information to the tag, and the tag then forwards the information to the terminal network device. The energy required for the tag to send information can be provided by an excitation signal, and the excitation signal can come from the network device or the terminal device.

[0090] In the AIoT, before a reader can perform an inventory, the tag must connect to the reader through random access. After random access, the tag can report its identity to the reader, allowing the reader to determine the presence of tags within its coverage area. For example, Figure 7 shows a schematic diagram of an inventory process. The names of the messages in the following process are examples only; other message names may exist and are not detailed here.

[0091] Step 701: The reader sends a paging or selection signaling to select or page one or a group of tags for access.

[0092] Paging or select signaling includes mask information (mask) or group identifier. One mask information or group identifier can match multiple tags. If the mask information included in the tag matches the mask information included in the paging or select signaling, it indicates that the tag is selected, or if the group identifier included in the tag matches the group identifier included in the paging or select signaling, it indicates that the tag is selected.

[0093] Alternatively, the paging or select command may include a session identifier and / or action indication information. The session identifier may indicate the group to which the tag belongs. For example, session identifiers may include S0, S1, S2, and S3, with each session corresponding to two states. The flag bit may be used to identify the session state. The flag bit may have a value of 0 or 1, or other values, such as B or A.

[0094] If the paging or select command includes a session identifier, such as S1, it indicates that the tag including the session identifier S1 is selected. The action indication information indicates that the tag being paged or selected sets the flag bit corresponding to the indicated session identifier (if there is only one, there is no need to indicate that it is only for this session identifier) ​​to the value indicated by the action indication information. For example, if the session identifier is S1 and the value indicated by the action indication information is 0, then the tag sets the flag bit of the session identifier S1 to 0 according to the action indication information. For tags that are not selected, the flag bit corresponding to S1 is set to the opposite value, for example, to 1. Of course, tags that are not selected may not make any changes to the flag bit corresponding to S1.

[0095] Step 702: The reader sends a query signaling, which is used to initiate an inventory cycle.

[0096] The query signaling includes the value of the parameter Q, which is used to determine the total number of time slots included in the inventory cycle indicated by the reader.

[0097] For example, if Q=4, the total number of time slots included in the inventory cycle is 2 Q .

[0098] Step 703: The tag selects a time slot to send a random number.

[0099] For example, the tag may send a 16-bit random number (RN16).

[0100] Here, RN16 is taken as an example. The tag can also send random numbers of other lengths, such as 8-bit random numbers.

[0101] Specifically, the tag can calculate the access time slot range according to the Q value to be [0,2 Q-1] , the label generates a [0,2 Q-1 ] and use this random number as the initial value of the counter. For example, if Q = 4, the random number generated by the tag is one in [0, 15]. For example, if the random number generated by the tag is 10, the initial value of the counter is 10.

[0102] Each time a tag receives a QueryRep signaling, the counter value is decremented by one. When the counter value reaches 0, the tag can send an RN16, which can be used to trigger the random access process and can serve as a random access request message. The first time slot after the query signaling is time slot 0. If the random number generated by the tag is 0, it can send an RN16 immediately after receiving the query signaling.

[0103] Step 704: If the reader successfully receives the RN16, it will feedback an acknowledgement (ACK) message, which includes the RN16 from the tag.

[0104] The ACK message may also be called a random access response message or a contention resolution message.

[0105] Step 705: When the tag receives the ACK message including its own RN16, it sends uplink data to the reader.

[0106] When the tag receives an ACK message containing its own RN16, it determines that random access is successful and can then send uplink data. For example, the uplink data can be the tag's electronic product code (EPC). The tag can also flip the flag bit, such as from state A to state B.

[0107] If the ACK message received by the tag does not include its own RN16, the tag ignores the ACK message and determines that the random access has failed.

[0108] After the reader receives the uplink data from the tag, it can send a query repeat signaling to trigger the next time slot.

[0109] In the above inventory process, after receiving the tag's random number, if the reader allows a tag to access, it must wait until the tag sends uplink data before triggering the next tag to access by querying repeated signaling. This means that at most one tag can access at a time. Before sending a conflict resolution message, the reader will not trigger a new random access opportunity. Therefore, tags that have not yet sent a random access request must wait for access. This results in a small number of tags accessing per unit time, low random access capacity, and low random access efficiency.

[0110] To this end, the present application provides a method that can increase random access capacity and improve random access efficiency.

[0111] The network architecture and business 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 will know that with the evolution of 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.

[0112] When the method provided in the present application is applied to the system in Figures 3 to 6, the method executed by the terminal device in the embodiment of the present application can be implemented by the terminal device in Figures 3 to 6 or the module in the terminal device, and the method executed by the network device in the embodiment of the present application can be implemented by the network device in Figures 3 to 6 or the module in the network device.

[0113] It can be understood that the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application. The method executed by the terminal device in the present application can be applied to the terminal device or a module in the terminal device. The method executed by the network device can be applied to the network device or a module in the network device, and can also be applied to the terminal device or a module in the terminal device. As long as it is possible to communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, it can be sufficient.

[0114] The following description takes the interaction between a terminal device and a network device as an example. In practical applications, the method provided in this application can also be applied to the interaction between terminal devices and terminal devices, and the method provided in this application can also be applied to the interaction between a tag (or AIoT device) and a terminal device. Alternatively, it can be understood that in each of the following processes, the terminal device can also be replaced by a tag or device A or device B or device C or AIoT device, and the network device can also be replaced by a reader or terminal device. In this application, the message names in the following embodiments are only examples and do not represent restrictions on the individual messages.

[0115] Because it takes a certain amount of time for a network device or terminal device to process a message, there will be a period of idle time domain resources between the message sent by the terminal device and the message received by the network device. Similarly, there will be a period of idle time domain resources between the message sent by the network device and the message received by the terminal device. In this application, the network device can be configured with multiple processes, and the terminal device can independently select a process. The message sent by the network device includes the identifier of the process. For example, if a selection message or query message includes the identifier of a process, the terminal device only responds to messages including the identifier of the process it is associated with and ignores messages from other processes. The network device can thus send messages from another process between messages from one process, thereby improving communication efficiency. This is described in detail below.

[0116] In the present application, since a process is associated with at least one terminal device, and the terminal device only responds to messages including the identifier of the process with which it is associated, then multiple terminal devices within the coverage of the network device or multiple terminal devices selected by the network device can be understood as belonging to different groups, or belonging to different sessions or categories. Therefore, the process in the present application can also be expressed by other nouns, such as group or group number, session or category, etc.

[0117] FIG8 is a flow chart of a communication method provided in an embodiment of the present application, wherein the method includes:

[0118] Step 801: The network device sends a first message.

[0119] Correspondingly, the first terminal device receives the first message.

[0120] The first message indicates a first identifier, which is used to identify a first process, that is, the first message may be a message in the first process corresponding to the first identifier, and the receiver of the first message is a terminal device associated with the first process or the first identifier.

[0121] This application does not limit how the first message indicates the first identifier. For example, if the network device is configured with multiple processes, each process corresponds to an identifier. The first message may include the first identifier. Alternatively, if the first process corresponding to the first identifier is a preset process, for example, the preset process is a process with an identifier of 0, then the first message may not include the first identifier. That is, if the network device is configured with multiple processes, the message in the preset process may not include the identifier of the preset process.

[0122] In this application, there are multiple possible implementations for configuring multiple processes on a network device. For example, in implementation one, the network device may indicate a first value, where the first value represents the number of processes or the maximum value of process identifiers. The number of processes may represent the number of processes configured on the network device; the maximum value of process identifiers may represent the maximum value that can be achieved by the identifiers of all processes configured on the network device.

[0123] For example, the network device indicates the first value through the first message or the third message. The third message may be a message sent before the first message, for example, the third message is a selection message.

[0124] In this implementation, the identifier of each of the multiple processes configured by the network device may be less than or equal to the first value. For example, the maximum value of the process identifier is 5, that is, the first value is 5. Assuming that the process identifier starts at 0, the value range of the process identifier of each of the multiple processes is [0, 5]. Therefore, the terminal device can determine a value within the range of [0, 5] as the identifier of the process associated with itself.

[0125] For another example, the number of processes is 5, that is, the first value is 5. Assuming that the process identifier starts from 0, the value range of the process identifier of each process in multiple processes is [0, 4]. Then the terminal device can determine a value in the range of [0, 4] as the identifier of the process associated with itself.

[0126] In a second implementation, the network device may indicate a process ID value range. For example, the network device may indicate a process ID value range through the first message or the third message, and the terminal device may select a value within the value range as the ID of the process associated with itself. For example, the value range indicated by the network device may include a minimum process ID of 3 and a maximum process ID of 7. The terminal device may select a process ID between 3 and 7.

[0127] In the present application, the process identifiers corresponding to the processes set by different network devices or adjacent network devices have different value ranges. It can be understood that the identifiers of the processes configured by different network devices are different, or there is no intersection between the identifiers of the processes configured between network devices with overlapping coverage. In this way, even if the coverage areas of different network devices have overlapping areas, the downlink signaling is distinguished by different process identifiers, and the terminal devices under one network device will not respond to the signaling of other network devices. For example, the first network device is configured with 3 processes, and the value range of the process identifiers of these 3 processes is [0, 2]; the second network device is configured with 5 processes, and the value range of the process identifiers of these 5 processes is [3, 7]. In this way, there is no process with the same identifier among the processes configured by different network devices, and each terminal device only responds to the message with the identifier of the process associated with itself. In this way, the downlink message sent by the first network device will not affect the terminal devices in the second network device, and the downlink message sent by the second network device will not affect the terminal devices in the first network device.

[0128] This application does not limit the specific name and function of the first message (or the operation that the first message instructs the terminal device to perform). The first message can be any message sent by the network device to the terminal device. For example, the first message includes but is not limited to any of the following messages:

[0129] The first message is a select message, and the first message is used to select one or a group of terminal devices;

[0130] Alternatively, the first message is a paging message, and the first message is used to page one or a group of terminal devices;

[0131] Alternatively, the first message is a query message, and the first message is used to indicate the total number of time units included in an inventory cycle, and to trigger a time unit or random access opportunity. The time unit may include a random access opportunity, and the terminal device may initiate random access during the random access opportunity. In this case, it can be understood that the first message is used to initialize an inventory cycle, and the first message is also used to trigger the paged or selected terminal device to access the network or initiate random access. Wherein, when the first message is used to trigger a time unit or random access opportunity, the reception time of the first message by the terminal device, or the sending time of the first message by the network device, may indicate the start time of the time unit or random access opportunity triggered by the first message.

[0132] Alternatively, the first message is a read message, which is used to read the electronic product code (EPC) in the storage area of ​​the terminal device, the tag identifier (TID), the content stored in the reserved area or the content stored in the user storage area, etc.

[0133] Alternatively, the first message is a write message, and the first message is used to write data to a storage area of ​​the terminal device.

[0134] Alternatively, the first message is a query repetition (queryrep) message, and the first message is used to trigger a time unit or a random access opportunity, which may include a random access opportunity, and the terminal device may initiate random access in the random access opportunity; in this case, it can be understood that the first message is also used to trigger the paged or selected terminal device to access the network or initiate random access;

[0135] Alternatively, the first message is an ACK message, and the ACK message may also be called a contention resolution message or a random access response message.

[0136] The above are just examples, and the first message may also be other types of messages, which will not be described one by one here.

[0137] In the present application, after the first terminal device receives the first message, if the first terminal device is associated with the first process or the first identifier, the first terminal device will respond to the first message and / or perform the operation indicated by the first message. If the first terminal device is not associated with the first process or the first identifier, the first terminal device will ignore or discard the first message. Here, the association of the first terminal device with the first process or the first identifier is used as an example for description, and there may be other terminal devices associated with the first process or the first identifier. Among them, since the first identifier is used to identify the first process, the association of the first terminal device with the first process can be equivalent to the association of the first terminal device with the first identifier.

[0138] This application does not limit how the first terminal device determines to associate with the first identifier. For example, assuming that the identifier of the process associated with the first terminal device is the third identifier, the first terminal device determines that the first identifier is equal to the third identifier, then the first terminal device is associated with the first identifier.

[0139] This application does not limit how the first terminal device determines the third identifier. For example, the network device may be configured with multiple processes, such as by indicating the first value via the first message or the third message. After obtaining the first value, the first terminal device may determine the third identifier of the process associated with itself based on the first value.

[0140] There may be multiple implementations of how a terminal device specifically determines the identifier of a process associated with itself.

[0141] For example, in implementation method 1, the first terminal device uses a second value that is less than or equal to the first value as the third identifier of the process associated with itself. For example, the maximum value of the process identifier is 5. Assuming that the process identifier starts at 0, the range of the process identifier is [0, 5]. Then, the terminal device can randomly select a value within the range [0, 5] as the third identifier of the process associated with itself.

[0142] In a second implementation method, the first terminal device determines the third identifier based on the device identifier of the first terminal device and the first value. For example, the third identifier id satisfies the following form: id = DE_ID mod A. Wherein, DE_ID is the device identifier of the first terminal device, and A is the first value. The device identifier can be the serving-temporary mobile subscriber identity (s-TMSI) of the first terminal device, or EPC, or radio network temporary identity (RNTI), or a truncated device identifier, etc.

[0143] In implementation method three, the first or third message may indicate a process ID range. The terminal device may select a value within this range as the ID of the process associated with it. For example, if the minimum process ID is 3 and the maximum process ID is 7, the terminal device may select a process ID between 3 and 7 as the ID of the associated process. The specific selection method is not limited and, for example, a random ID may be selected. Different network devices or adjacent network devices may set different process ranges.

[0144] Implementation method 4: If the first terminal device uses the identifier included in the first message as the identifier of the associated process, and the first downlink message is a message that triggers the first terminal device to initiate random access at a time unit or random access opportunity, for example, the first terminal device determines to initiate random access at time unit a. When the first terminal device receives downlink message b, which triggers time unit a, the first terminal device uses the identifier included in downlink message b as the identifier of the associated process.

[0145] The above are just examples. The first terminal device can also determine the third identifier in other ways, which will not be explained one by one here.

[0146] Step 802: The first terminal device sends a first uplink message.

[0147] Correspondingly, the network device receives the first uplink message.

[0148] The first uplink message may include a first identifier. The first uplink message may be a message in response to the first message. For example, the first message is a query message, and the first uplink message may be a random access request message. The first message is an acknowledgment message, a contention resolution message, or a random access response message, and the first uplink message may include uplink data.

[0149] The first terminal device is a passive device or a semi-passive device, or the first terminal device is an environmental Internet of Things terminal device, for example, the first terminal device is a tag.

[0150] Step 803: Before responding to the first uplink message, the network device sends a second message, where the second message indicates a second identifier.

[0151] Correspondingly, the second terminal device receives the second message.

[0152] The second identifier is used to identify the second process, that is, the second message may be a message in the second process corresponding to the second identifier, and the receiving end of the second message is a terminal device associated with the second process or the second identifier.

[0153] When the second terminal device determines to associate with the second identifier, it receives the second message. How the second terminal device determines to associate with the second identifier can be referred to the description of how the second terminal device determines to associate with the first identifier in step 801, which will not be repeated here.

[0154] The network device sends a second message before responding to the first uplink message, and the following implementation methods may exist. In one implementation method, if the network device sends a response message to the first uplink message, "before" responding to the first uplink message may refer to before sending the response message to the first uplink message. In another implementation method, if the network device does not send a response message to the first uplink message, "before" responding to the first uplink message may refer to before the arrival of the moment when the interval between the first uplink message and the first uplink message is the first duration. The first duration is the maximum duration between the first uplink message and the response message corresponding to the first uplink message, and the first duration is preconfigured or preset. In order to avoid the terminal device from waiting for a long time without receiving a response message, the network device may configure a first duration. If the terminal device does not receive a response message within the first duration after sending an uplink message, it may no longer wait to receive the response message, determine that it will not receive a response message from the network device, or deem that the transmission is abnormal or the transmission has failed.

[0155] The specific name and function of the second message (or the operation that the second message instructs the terminal device to perform) are not limited. The second message can be any message sent by the network device to the terminal device. For details, please refer to the previous description of the first message and will not be repeated here.

[0156] Step 804: The second terminal device sends a second uplink message to the network device.

[0157] Correspondingly, the network device receives the second uplink message.

[0158] The second uplink message may include the second identifier. The second uplink message may be a message in response to the second message. For example, the second message is a query message, and the second uplink message may be a random access request message. The second message is an acknowledgment message, a contention resolution message, or a random access response message, and the second uplink message may include uplink data.

[0159] The second terminal device is a passive device or a semi-passive device, or the second terminal device is an environmental Internet of Things terminal device, such as device A or device B. For example, the second terminal device is a tag.

[0160] In this application, step 803 and step 804 are performed between step 802 and step 805 as an example for description. In order to ensure that step 803 and step 804 can complete the transmission, the network device can configure the first duration that meets the following conditions when configuring the first duration:

[0161] The first duration is greater than or equal to the duration required to send an uplink message to the terminal device and receive a downlink message corresponding to the uplink message.

[0162] For example, for steps 803 and 804, the first duration is greater than or equal to the duration required to send the second message and receive the second uplink message from the terminal device. If only step 803 is performed between steps 802 and 805, then the first duration is greater than or equal to the duration required to send the second message, and other situations are not further described.

[0163] Step 805: The network device sends a first response message to the first uplink message, where the first response message includes a first identifier.

[0164] Correspondingly, the first terminal device receives the first response message.

[0165] The specific content and function of the first response message are not limited. For example, the first uplink message is a random access request message, the first response message is an acknowledgment message, a contention resolution message, or a random access response message; the first uplink message is a message including uplink data, and the first response message is a query repetition message.

[0166] For another example, the core network device needs to send data to the terminal device associated with the first identifier, then the core network device can send a fourth message to the core network device, and the fourth message includes the first data and the first identifier. The network device determines that the receiving end of the first data is the terminal device associated with the first identifier based on the first identifier, so that the fifth message can be sent, and the fifth message includes the first data and the first identifier. For the first terminal device, it is associated with the first identifier. After receiving the fifth message, it determines that the fifth message includes the first identifier, so that the first data can be saved. For the second terminal device, it is associated with the second identifier. After receiving the fifth message, it determines that the fifth message includes the first identifier, so that the first data is discarded or ignored. Among them, the specific content of the first data is not limited, and it can be any data sent by the core network device. The core network device can be a device such as AMF or SMF, and this application does not limit this.

[0167] Optionally, in an implementation that does not support the flag bit, if the terminal device successfully accesses, or successfully accesses and completes data transmission, it will no longer respond to subsequent query messages (messages that trigger a new round of access). Specifically, it may not respond to such messages for a period of time, which can be predefined or configured by the network device.

[0168] The order of the above messages is only an example. In another implementation, step 803 and step 804 can also be executed between step 801 and step 802. This application does not limit this.

[0169] Through the above process, network devices can trigger multiple processes in parallel. A message in one process can be located between two messages in another process (i.e., located in the idle time domain resources between the two messages). For example, the second message in the second process is located between the first uplink message and the first response message in the first process. In this way, while the network device is communicating with one terminal device in one process, it can also communicate with another terminal device in another process, which can improve resource utilization and increase system capacity. In addition, because terminal devices only respond to messages from their associated processes, messages from one process will not interfere with terminal devices in another process, improving system reliability.

[0170] In combination with the above description, the above process is described below through a specific example.

[0171] In the process of FIG9 , the network device may send multiple query messages, each query message is associated with a process, and each terminal device only responds to messages in the process associated with itself.

[0172] FIG9 is a flow chart of a communication method provided in an embodiment of the present application, wherein the method includes:

[0173] Step 901: The network device sends a selection message, which is used to select or page one or a group of terminal devices for access.

[0174] The network device may send a selection message after receiving a first paging message from the core network. The first paging message is used to page one or a group of terminal devices. The selection message may also be called a paging message or selection signaling, etc. The specific message name is not limited.

[0175] The selection message may include a session identifier and / or action indication information. The session identifier may indicate the group to which the selected terminal device belongs. For example, session identifiers may include S0, S1, S2, and S3, with each session corresponding to two states. A flag bit may be used to identify the session state. The flag bit may take values ​​of 0 or 1, or other values ​​such as B or A. If the selection message includes a session identifier, such as S1, it indicates that the terminal device with the session identifier S1 is selected.

[0176] The action indication information instructs the terminal device selected by the selection message to set the flag bit corresponding to the indicated session identifier (if there is only one, there is no need to indicate that it is only for this session identifier) ​​to the value indicated by the action indication information. For example, if the session identifier is S1 and the value indicated by the action indication information is 0, then the terminal device will set the flag bit of the session identifier S1 to 0 according to the action indication information. The terminal device that is not selected will set the flag bit corresponding to S1 to the opposite value, for example, to 1. Of course, the terminal device that is not selected can also not make any changes to the flag bit corresponding to S1.

[0177] Optionally, if the tag has only one flag bit, then there is no need to indicate in the selection message which flag bit or which session to operate on. Only if there are multiple flag bits or multiple session identifiers may there be action indication information (indicating a certain flag bit).

[0178] The selection message also indicates a first value, which is the maximum number of processes configured for the network device or the maximum value of the process identifier. For example, if the selection message includes a maximum process identifier of 5, and assuming that the process identifier starts at 0, it means that the network device is configured with 6 processes. Alternatively, the selection message can indicate a value range for the process identifier. For example, if the network device is configured with 6 processes, the selection message indicates that the value range for the process identifier is [0,5]. After receiving the selection message, all selected terminal devices can determine an identifier as the identifier of the process associated with themselves based on the first value or the value range of the process identifier indicated in the selection message. The specific process can refer to the previous description.

[0179] The selection message may also indicate a second duration T2, which may represent the maximum time interval for the terminal device to wait for the downlink message corresponding to the uplink message after sending the uplink message. Optionally, if there are multiple processes, the second duration configured for multiple processes is greater than the second duration configured for a single process. Optionally, the second duration T2 is configured only when there are multiple processes. When there is only one process, the second duration T2 is not configured, and the second duration T2 at this time may be the value specified by the protocol. Optionally, the value of the second duration is different in the case of different coverage levels. For example, the second duration configured in the case of a high coverage level is less than the second duration configured in the case of a low coverage level.

[0180] The selection message may also include multi-process configuration information, which indicates whether the multi-process feature is used, or can be understood as indicating whether multiple processes are configured. If the selection message does not indicate the first value, there may be only one process, and the multi-process configuration information may indicate that multiple processes are not configured.

[0181] The selection message may also include other information, and this application does not limit the content of the selection message.

[0182] Optionally, if there are multiple processes, after the terminal device sends uplink data, it starts a timer to determine whether it receives downlink data from the corresponding process before the timer expires. If not, it is considered that the transmission has failed or is abnormal. The timer duration is the first duration.

[0183] Step 902: The network device sends a first query message, where the first query message is used to indicate the total number of allocated time units X, where X is an integer greater than 0.

[0184] The first query message includes a first identifier, which may be an identifier of a first process. The first query message is received by a terminal device associated with the first process or the first identifier. The X time units indicated in the first query message are allocated to the terminal device associated with the first identifier. If a terminal device is not associated with the first identifier, the first query message may be ignored or discarded.

[0185] For example, a first terminal device is associated with a first identifier. After receiving a first query message, it determines that the first query message includes the first identifier, thereby determining the total number of time units X, and selecting a time unit to initiate random access based on the total number of time units X. A second terminal device is associated with a second identifier. After receiving the first query message, it determines that the first query message includes the first identifier, thereby discarding or ignoring the first query message.

[0186] This application does not limit how the first query message indicates the total number of time units. For example, the first query message includes the value of parameter Q, which is used to determine the total number of time units allocated to the network device in an inventory cycle. For example, Q = 4, then the total number of time units is X = 2 Q =16, that is, the first query message indicates 16 time units. The first query message may also be called query signaling or the like.

[0187] In this application, a time unit may refer to a time slot, a subframe, or a frame. The lengths of different time units may be the same or different. For example, in this application, a time unit is triggered by a trigger message (e.g., a query message or a query repeat message). The length of a time unit in the time domain may be the interval between two adjacent trigger messages. The tag determines the specific number of time slots based on the number of trigger messages received or the time unit index carried in the trigger message.

[0188] The first query message may also trigger a first time unit or a first random access opportunity, where the first time unit is the first time unit of the X time units indicated by the first query message, and the first time unit includes the first random access opportunity. When the first query message is used to trigger the first time unit or the first random access opportunity, the moment when the terminal device receives the first query message, or the moment when the network device sends the first query message, may represent the starting moment of the first time unit or the first random access opportunity triggered by the first query message. The terminal device associated with the first identifier may initiate random access in the first random access opportunity.

[0189] The first query message may also include the specific value of the first flag bit; for example, if the selection message indicates that the first flag bit is set to A or 1, the first query message may include the value of the first flag bit (such as A or 1). If the selection message also indicates a session identifier, the first query message may also include the corresponding session identifier. For example, if the session identifier included in the selection message is S1, the first query message may also include S1. The session identifier and the value of the first flag bit included in the first query message are used to indicate access by a terminal device that matches the value of the first flag bit.

[0190] For example, if the value of the first flag bit is state A, it indicates that the first query message is used to select a terminal device whose first flag bit is in state A to access the network or initiate random access. If the flag bit of a terminal device is in state A and matches the first flag bit, then the terminal device can be determined to be selected. If the flag bit of the terminal device is in state B and does not match the first flag bit, then the terminal device can be determined not to be selected and the subsequent steps can be skipped.

[0191] For another example, the first query message includes a session identifier S1 and a first flag bit whose value is state A, indicating that a terminal device whose flag bit corresponding to the session identifier S1 is in state A has accessed the network or initiated random access. If the flag bit corresponding to the session identifier S1 of a terminal device is in state A and matches the first flag bit, the terminal device can be determined to be selected. If the flag bit corresponding to the session identifier S1 of a terminal device is in state B and does not match the first flag bit, the terminal device can be determined to be not selected and the subsequent steps may be skipped.

[0192] The first query message may also include other information, and this application does not limit the content of the first query message.

[0193] Step 903: The first terminal device sends a first random access request message to the network device in the first time unit or the first random access opportunity.

[0194] Correspondingly, the network device receives the first random access request message in the first time unit or the first random access opportunity, wherein the first random access opportunity is within the first time unit.

[0195] The first random access request message is used to initiate random access. The first random access request message sent by the first terminal device may include a 16-bit random number RN16, or an 8-bit random number, or a random number of multiple bits indicated in a paging message or a selection message, and may also include information such as a random access preamble. This application does not limit this. The first random access request message also includes a first identifier, so that the network device can determine the process associated with the first terminal device based on the first identifier.

[0196] In the present application, after a first terminal device receives a first query message, if the first terminal device is associated with a first identifier, the first terminal device determines whether to send a first random access request message in a first time unit or a first random access opportunity. If the first terminal device is not associated with the first identifier, the first terminal device ignores or discards the first message. This description uses the association of the first terminal device with the first identifier as an example; other terminal devices may also be associated with the first identifier.

[0197] This application does not limit how the first terminal device determines the identifier of the process associated with itself. For example, the first terminal device can determine an identifier (such as the first identifier) ​​as the identifier of the process associated with itself based on the maximum number of processes indicated by the selection message or the maximum value of the process identifier or the value range of the process identifier. The specific process can refer to the description in step 801 and will not be repeated here. Accordingly, if the first terminal device determines that the identifier selected by itself is the same as the first identifier, it determines to be associated with the first identifier and determines itself as the recipient of the first query message. The first terminal device can respond to the first query message.

[0198] One implementation method is that different network devices are configured with different process identifiers, or there is no intersection between the process identifiers configured between network devices with overlapping coverage. In this way, even if the coverage areas of different network devices overlap, the downlink signaling is distinguished by different process identifiers, and the terminal devices under one network device will not respond to the signaling of other network devices. For example, the first network device is configured with 3 processes, and the value range of the process identifiers of these 3 processes is [0, 2]; the second network device is configured with 5 processes, and the value range of the process identifiers of these 5 processes is [3, 7]. In this way, there is no process with the same identifier among the processes configured by different network devices, and each terminal device only responds to the message with the identifier of the process associated with itself. In this way, the downlink message sent by the first network device will not affect the terminal devices in the second network device, and the downlink message sent by the second network device will not affect the terminal devices in the first network device.

[0199] In another implementation method, if the network device sends a sixth message after sending a selection message, if the sixth message indicates the maximum number of processes or the maximum value of the process identifier or the value range of the process identifier, then the first terminal device can re-determine the identifier of a process associated with itself based on the sixth message. The first terminal device can determine the time unit for initiating random access based on the updated identifier. The specific process will not be repeated here.

[0200] This application describes the example of a first terminal device sending a first random access request message in a first time unit. The first terminal device may also send a first random access request message in other time units. This application does not limit in which specific time unit the first terminal device sends the first random access request message.

[0201] For example, the first terminal device may determine the time unit for sending the first random access request message in the following manner: The first query message includes Q, and the first terminal device determines that the total number of time units indicated by the first query message is 2 according to Q. Q , assuming that these time units are numbered starting from 0, then the index range of these time units is [0,2Q-1 The first terminal device generates a value in [0,2 Q-1 ], the first terminal device can determine the time unit for sending the first random access request message according to the random number, and the specific implementation methods may be as follows.

[0202] In implementation method 1, the first terminal device uses the random number as the initial value of the first counter. Each time the first terminal device receives a query repetition (QueryRep) message including the first identifier, the value of the first counter is decremented by 1. When the value of the first counter is equal to 0, the first terminal device may send a first random access request. The first time unit triggered by the first query message is time unit 0. If the random number generated by the first terminal device is 0, the first random access request message may be sent after receiving the first query message.

[0203] In implementation mode 2, the first terminal device starts counting the first counter from 0, and each time it receives a query repetition message including the first identifier, it increases the value of the first counter by 1. When the value of the first counter is equal to the random number, the first terminal device may send a first random access request message.

[0204] Implementation method three: the first query repetition message carries a time unit index. If the received time unit index matches the random number generated by the first terminal device, the first terminal device can send a first random access request message. For example, the random number generated by the terminal device is 5. If a query repetition message including a first identifier and a time unit index of 5 is received, the time unit index matches the random number, and the first terminal device can send a first random access request message. Among them, if the query repetition message includes the index of the time unit, for a process, the first query repetition message sent by the network device carries an index of 1, and the second query repetition message sent by the network device carries an index of 2, and so on for other cases.

[0205] Among them, the query repetition message can be used to trigger a time unit, or the query repetition message can be used to trigger the update of the time unit, which can be understood as the reception time of the query repetition message is the end time of the previous time unit and the start time of the next time unit. Among them, the query message can also be used to trigger time unit 0, which can be understood as: the first time unit after the query message is time unit 0, and the reception time of the query message is the start time of time unit 0. If the random number generated by the first terminal device is 0, the time unit for initiating random access is time unit 0. After receiving the query message, the first terminal device sends the first random access request message in time unit 0.

[0206] Multiple terminal devices may send random access request messages in a time unit. For example, if two terminal devices generate the same random number, the two terminal devices will send random access request messages in the same time unit or random access opportunity. This application describes an example in which a terminal device sends a first random access request message in the first time unit or the first random access opportunity, and other situations are not repeated.

[0207] Optionally, if there are multiple processes, after the first terminal device sends the first random access request message, it starts a timer to determine whether a response message corresponding to the first random access request message is received before the timer expires. If no response message is received, it is considered that the transmission has failed or the transmission is abnormal. The timer duration is the first duration.

[0208] Assuming that the number of processes configured in the selected message is greater than two, the network device may send a message related to the second process corresponding to the second identifier before responding to the first random access request message. Specifically, the process may include steps 904 and 905. In one implementation, if the network device sends a response message to the first random access request message, "before" responding to the first random access request message may refer to "before" sending the response message to the first random access request message. In another implementation, if the network device does not send a response message to the first random access request message, "before" responding to the first random access request message may refer to "before" the moment when the interval between the first random access request message and the first random access request message is equal to the first duration.

[0209] Step 904: The network device sends a second query message, where the second query message is used to indicate the total number of allocated time units Y, where Y is an integer greater than 0.

[0210] The second query message includes a second identifier, which may be an identifier of a second process. The recipient of the second query message is a terminal device associated with the second process or the second identifier. The Y time units indicated in the second query message are allocated to the terminal device associated with the second identifier. If a terminal device is not associated with the second identifier, the second query message may be ignored or discarded.

[0211] For example, a first terminal device is associated with a first identifier and, upon receiving a second query message, determines that the second query message includes the second identifier, thereby discarding or ignoring the first query message. A second terminal device is associated with a second identifier and, upon receiving a second query message, determines that the second query message includes the second identifier, thereby determining a total number of time units Y and selecting a time unit based on the total number of time units Y to initiate random access.

[0212] This application does not limit how the second query message indicates the total number of time units Y. For details, please refer to the description in step 902.

[0213] The second query message may also trigger a second time unit or a second random access opportunity, where the second time unit is the first time unit of the Y time units indicated by the second query message, and the second time unit includes the second random access opportunity. When the second query message is used to trigger the second time unit or the second random access opportunity, the moment the terminal device receives the second query message, or the moment the network device sends the second query message, may represent the starting moment of the second time unit or the second random access opportunity triggered by the second query message. The terminal device associated with the second identifier may initiate random access in the second random access opportunity.

[0214] The second query message may further include a specific value of the second flag bit and may also include a session identifier. For details, please refer to the description in step 902 and will not be repeated here.

[0215] The second query message may also include other information, and this application does not limit the content of the second query message.

[0216] Step 905: The second terminal device sends a second random access request message to the network device in a second time unit or a second random access opportunity.

[0217] Correspondingly, the network device receives the second random access request message in the second time unit or the second random access opportunity, wherein the second random access opportunity is within the second time unit.

[0218] The second random access request message is used to initiate random access. The second random access request message sent by the second terminal device may include a 16-bit random number RN16, or an 8-bit random number, or a random number of multiple bits indicated in a paging message or a selection message, and may also include information such as a random access preamble. This application does not limit this. The second random access request message also includes a second identifier, so that the network device can determine the process associated with the second terminal device based on the second identifier.

[0219] The second terminal device may determine an identifier (e.g., the second identifier) ​​as the identifier of the process associated with itself based on the maximum number of processes indicated in the selection message, the maximum value of process identifiers, or the range of process identifiers. The specific process is described in step 801 and is not further described here. Accordingly, if the second terminal device determines that its selected identifier is the same as the second identifier, it determines to associate itself with the second identifier and identifies itself as the recipient of the second query message. The second terminal device may respond to the second query message.

[0220] This application describes the example of the second terminal device sending the second random access request message in the second time unit. The second terminal device may also send the second random access request message in other time units. This application does not limit in which time unit the second terminal device sends the second random access request message. Please refer to the description in step 903 and will not repeat it here.

[0221] Step 906: The network device sends a first random access response message.

[0222] Correspondingly, the first terminal device receives the first random access response message. The random access response message may also be called a contention resolution message or a confirmation message.

[0223] Here, the network device successfully receives the first random access request message and allows the first terminal device to access the random access. If the network device does not successfully receive the first random access request message, it may not send the first random access response message.

[0224] In the present application, the first random access response message includes the first identifier and may also include part or all of the content of the first random access request message. If the first terminal device determines that the first random access response message includes the first identifier, it is determined to be the receiving end of the first random access response message. If the first terminal device determines that the first random access response message includes part or all of the content of the first random access request message, it determines that the random access is successful. For the second terminal device, it is associated with the second identifier. After receiving the first random access response message, it determines that the first random access response message includes the first identifier, thereby discarding or ignoring the first random access response message.

[0225] If the first terminal device determines that the random access is successful, it can send uplink data to the network device.

[0226] Step 907: The first terminal device sends a first uplink message to the network device.

[0227] Correspondingly, the network device receives the first uplink message.

[0228] The first uplink message may include a first identifier and first uplink data, and the first uplink data may include at least one of the following: an EPC of the first terminal device, a TID of the first terminal device, content stored in a reserved area of ​​the first terminal device, content stored in a user storage area of ​​the first terminal device, etc. The first uplink data may also include other data, which is not limited in this application.

[0229] Optionally, other uplink data or messages sent by the first terminal device may also carry an identifier of a process associated with the first terminal device, for example, the first identifier.

[0230] If the random access of the second terminal device is successful, steps 908 and 909 may also be included.

[0231] Step 908: The network device sends a second random access response message.

[0232] Correspondingly, the second terminal device receives the second random access response message. The random access response message may also be called a contention resolution message or a confirmation message.

[0233] Here, the network device successfully receives the second random access request message and allows the second terminal device to access the random access. If the network device does not successfully receive the second random access request message, it may not send the second random access response message.

[0234] In the present application, the second random access response message includes the second identifier and may also include part or all of the content of the second random access request message. If the second terminal device determines that the second random access response message includes the second identifier, it is determined to be the receiving end of the second random access response message. If the second terminal device determines that the second random access response message includes part or all of the content of the second random access request message, it determines that the random access is successful. For the first terminal device, it is associated with the first identifier. After receiving the second random access response message, it determines that the second random access response message includes the second identifier, thereby discarding or ignoring the second random access response message.

[0235] If the second terminal device determines that the random access is successful, it can send uplink data to the network device.

[0236] Optionally, if there are multiple processes, after the second terminal device sends the second random access request message, it starts a timer to determine whether a response message corresponding to the second random access request message is received before the timer expires. If no response message is received, it is considered that the transmission has failed or the transmission is abnormal. The timer duration is the first duration.

[0237] Step 909: The second terminal device sends a second uplink message to the network device.

[0238] Correspondingly, the network device receives the second uplink message.

[0239] The second uplink message may include a second identifier and second uplink data, and the second uplink data may include at least one of the following: an EPC of the second terminal device, a TID of the second terminal device, content stored in a reserved area of ​​the second terminal device, content stored in a user storage area of ​​the second terminal device, etc. The second uplink data may also include other data, which is not limited in this application.

[0240] Optionally, other uplink data or messages sent by the second terminal device may also carry an identifier of a process associated with the second terminal device, for example, the second identifier.

[0241] Step 910: The network device sends a first query repetition message, where the first query repetition message includes a first identifier.

[0242] The first query repetition message triggers a time unit or random access opportunity in the first process corresponding to the first identifier. For example, the first query repetition message at this time triggers the second time unit or random access opportunity among X time units.

[0243] The terminal device associated with the first identifier can initiate random access in the time unit triggered by the first query repetition message or the random access opportunity. The specific process will not be repeated here.

[0244] Optionally, after the first terminal device sends the first uplink message or receives the first query repetition message, the flag bit can be updated. For example, if the flag bit is in state A when the first terminal device receives the selection message, the first terminal device can update the flag bit to state B. If the selection message includes a session identifier, the first terminal device updates the flag bit corresponding to the session identifier to state B. In this way, there is no need to respond to the query repetition message including the first identifier again. If the first terminal device encounters a random access failure or collision, the flag bit of the first terminal device remains unchanged, so it can respond to the query repetition message including the first identifier again, that is, initiate random access in the time unit or random access opportunity triggered by the query repetition message including the first identifier.

[0245] Optionally, the second terminal device can update the flag bit after sending the second uplink message or receiving the second query repetition message. For example, if the flag bit is in state A when the second terminal device receives the selection message, the second terminal device can update the flag bit to state B.

[0246] Optionally, in an implementation that does not support the flag bit, if the terminal device successfully accesses, or successfully accesses and completes data transmission, it will no longer respond to subsequent query messages (messages that trigger a new round of access). Specifically, it may not respond to such messages for a period of time, which can be predefined or configured by the network device.

[0247] In the above process, two processes are taken as an example. If the number of processes is greater than two, messages of other processes may also be included between step 903 and step 906, and between step 907 and step 910, which will not be repeated here.

[0248] Taking two processes as an example, in the above process, step 904 and step 905 are executed between step 903 and step 906. To ensure that step 904 and step 905 can complete the transmission, the network device can configure the first duration to meet the following conditions when configuring the first duration:

[0249] The first duration is greater than or equal to a duration required to send the second query message and receive the second random access request message from the terminal device.

[0250] If only step 803 is performed between step 802 and step 805, then the first duration is greater than or equal to the duration required to send the second message, and other situations are not described in detail.

[0251] The order of the above messages is only an example. In another implementation, step 904 and step 905 can also be executed between step 902 and step 903, and step 908 and step 909 can also be executed between step 906 and step 907. This application does not limit this.

[0252] Through the above process, a network device can trigger multiple processes in parallel. Between two messages in the first process, messages from the second process can be transmitted. This allows the network device to communicate with a first terminal device in the first process while also communicating with a second terminal device in the second process. This improves resource utilization and increases system capacity. Furthermore, because terminal devices only respond to messages from their associated processes, messages from one process do not interfere with terminal devices in another process, improving system reliability.

[0253] In the process of FIG. 10 , when the network device is configured with multiple processes, it may only send one query message. Multiple processes are associated with the query message, but each process is associated with a different query repetition message.

[0254] FIG10 is a flow chart of a communication method provided in an embodiment of the present application, wherein the method includes:

[0255] Step 1001: The network device sends a selection message, which is used to select or page one or a group of terminal devices for access.

[0256] The network device may send a selection message after receiving a first paging message from the core network. The first paging message is used to page one or a group of terminal devices. The selection message may also be called a paging message or selection signaling, etc. The specific message name is not limited.

[0257] The specific content of the selection message can be found in the description of step 901 and will not be repeated here. Compared to the selection message in step 901, the selection message in step 1001 may not indicate the maximum number of processes configured for the network device or the maximum value of the process ID, nor may it indicate the value range of the process ID.

[0258] Step 1002: The network device sends a first query message, where the first query message is used to indicate the total number of allocated time units X, where X is an integer greater than 0.

[0259] The X time units indicated by the first query message are allocated to all processes. All selected terminal devices can select a time unit from the X time units to send an uplink message.

[0260] The first query message may indicate a first value, which is the maximum number of processes configured for the network device or the maximum value of the process identifier. For example, the first query message includes a maximum value of 5 for the process identifier. Assuming that the process identifier starts at 0, it means that the network device is configured with 6 processes. Alternatively, the first query message may indicate a value range for the process identifier. For example, if the network device is configured with 6 processes, the first query message indicates that the value range for the process identifier is [0,5]. After receiving the first query message, all selected terminal devices may determine an identifier as the identifier of the process associated with themselves based on the first value or the value range of the process identifier indicated by the first query message. The specific process can refer to the previous description.

[0261] The first query message may also trigger a first time unit or a first random access opportunity, where the first time unit is the first time unit among the X time units indicated by the first query message, and the first time unit includes a first random access opportunity.

[0262] For example, in implementation method one, the first query message may include an identifier of a process, such as a first identifier. At this time, the first time unit or the first random access opportunity triggered by the first query message is used to send a random access request message to the terminal device associated with the first identifier.

[0263] Implementation method 2: The first query message may not include the identifier of any process. In this case, the first query message is associated with a preset process, such as the preset process being the first process among all processes configured for the network device. In this implementation method, the first time unit or the first random access opportunity triggered by the first query message is used to send a random access request message to a terminal device associated with the first process (i.e., the preset process). Terminal devices associated with other processes ignore the first time unit or the first random access opportunity and may send a random access request through a random access opportunity triggered by a query repeat message or other message carrying the corresponding process identifier. The preset process may be preset or preconfigured, and this application is described by taking the first process as the preset process as an example.

[0264] Implementation method three, the first query message may not include the identifier of any process. In this case, the first query message is associated with all processes configured on the network device. At this time, the first time unit or the first random access opportunity triggered by the first query message is the first time unit or multiple random access opportunities of all processes configured on the network device, which can be used to send a random access request message to a terminal device associated with any process among all processes configured on the network device.

[0265] In another implementation, implementation method four: the first query message may not include the identifier of any process, the first query message is not associated with any process, or it can be understood that the first query message is not used to trigger the first time unit or the first random access opportunity. In this implementation, only the query repetition message or other message includes the process identifier, which is used to trigger the random access opportunity or time slot corresponding to the corresponding process. For example, after the network device sends the first query message, when it sends the query repetition message carrying the first identifier again, the query repetition message can trigger a time unit or random access opportunity for the terminal device associated with the first process corresponding to the first identifier to send a random access request message.

[0266] Another implementation manner, implementation manner five: the terminal device receives a selection message or a paging message, and the selection message or the paging message may include a value range of the process identifier, or a maximum identifier of the process.

[0267] The terminal device receives a first query message, which indicates the maximum number of time units for the terminal device to access. The maximum number of time units indicated by the first query message can be used for multiple processes, that is, the total number of time units for multiple processes is indicated by the first query message. The terminal device randomly selects a time unit to be accessed, waits for the selected time unit to arrive, and accesses in the selected time unit. The specific index of the time unit can be determined by the number of times the query repetition message is received or the information carried by the query repetition message. For example, the query repetition message can carry the identifiers of different processes, that is, the number of time units is calculated only based on the number of times the query repetition message is received or the information carried by the query repetition message, without ignoring possible process identifiers. When the selected time unit arrives, the process identifier carried in the query repetition message that triggers the time unit is used as the associated downlink process identifier or its own process identifier, and the terminal device determines that it has received the downlink message associated with its own process and ignores the downlink messages of other processes. Optionally, the uplink message sent by the terminal device can also carry the identifier of the process.

[0268] For example, the first query message includes Q, and the total number of time units indicated by the first query message is 2 Q Or Q, assuming that these time units are numbered starting from 0, then the index range of these time units is [0,2 Q-1 ] or [0,Q]. Assume that the network device is configured with 2 processes, then these 2 processes share 2 Q Or Q time units. The first terminal device generates a time interval between [0,2 Q-1 ] or a random number between [0,Q], and the first terminal device uses the random number as the initial value of the first counter.

[0269] Implementation method 1: Whenever a first terminal device receives a query repetition message, regardless of whether the process identifier carried in the query repetition message is the same as the identifier of a process associated with the first terminal device, the first counter value is decremented by 1. For example, when a query repetition message is received that includes a process identifier of 0, the first counter value is decremented by 1; and when a query repetition message is received that includes a process identifier of 1, the first counter value is also decremented by 1. When a query repetition message is received that causes the first counter value to equal 0, if the query repetition message includes a process identifier of 1, the first terminal device determines that the identifier 1 is the identifier associated with the first terminal device (i.e., identifies the identifier 1 as the identifier of the process associated with the first terminal device), and in subsequent downlink transmissions, only processes messages or data associated with the process (the process with identifier 1). If the query repetition message includes a process identifier of 0, the first terminal device determines that the identifier 0 is the identifier associated with the first terminal device (i.e., identifies the identifier 0 as the identifier of the process associated with the first terminal device), and in subsequent downlink transmissions, only processes messages or data associated with the process (the process with identifier 0).

[0270] Implementation method 2: Each query repetition message sent by the network device includes the serial number of the time unit triggered by the query repetition message. The serial number can also be called an index or other description. Whenever the first terminal device receives a query repetition message, it determines whether it is the time unit it chooses to access based on the time unit serial number carried in the query repetition message, and ignores the process identifier carried by the query repetition message. When the time unit serial number carried by the received query repetition message is the same as the time unit it chooses to access, it determines that the process identifier carried in the query repetition message is the identifier of the process associated with the first terminal device, and ignores messages carrying other process identifiers in subsequent downlink messages. For example, the network device allocates X time units through a query message, and the query message triggers the first time unit of the X time units. The first query repetition message sent by the network device triggers the second time unit of the X time units. The serial number of the time unit it carries is 1, and so on for other cases. The first terminal device generates a range between [0,2 Q-1 ] or a random number between [0,Q]. If the time unit sequence number carried in the received query repetition message is the same as the random number, the identifier of the process included in the query repetition message is used as the identifier of the process associated with the first terminal device, and only the downlink message including the identifier is processed subsequently, and the messages carrying other process identifiers are ignored.

[0271] The first query message may further include other information, for example, please refer to the description in step 902, which will not be repeated here.

[0272] Step 1003: The first terminal device sends a first random access request message to the network device in a first time unit or a first random access opportunity.

[0273] Correspondingly, the network device receives the first random access request message in the first time unit or the first random access opportunity, wherein the first random access opportunity is within the first time unit.

[0274] If the first query message is implementation method 1 in step 1002, the first query message includes a first identifier, and the first terminal device sends a first random access request message in a first time unit or a first random access opportunity when it is associated with the first identifier.

[0275] If the first query message is the second implementation method in step 1002, the first query message does not include the identifier of any process, but the first query message is associated with the preset process. When the first terminal device is associated with the preset process, the first random access request message is sent in the first time unit or the first random access opportunity.

[0276] If the first query message is implementation method three in step 1002, the first query message does not include the identifier of any process, and the first query message is associated with all processes configured by the network device, then the first terminal device can send a first random access request message in the first time unit or the first random access opportunity.

[0277] The first random access request message is used to initiate random access. The first random access request message sent by the first terminal device may include a 16-bit random number RN16, or an 8-bit random number, or a random number of multiple bits indicated in a paging message or a selection message, and may also include information such as a random access preamble. This application does not limit this. The first random access request message also includes a first identifier, so that the network device can determine the process associated with the first terminal device based on the first identifier.

[0278] Optionally, other uplink data or messages sent by the first terminal device may also carry an identifier of a process associated with the first terminal device, for example, the first identifier.

[0279] This application does not limit how the first terminal device determines the identifier of the process associated with itself. For example, the first terminal device may determine an identifier (e.g., the first identifier) ​​as the identifier of the process associated with itself based on the maximum number of processes or the maximum value of process identifiers or the value range of process identifiers indicated by the first query message. The specific process can be referred to the description in step 801 and will not be repeated here.

[0280] For another example, the first terminal device determines to initiate random access at the first time unit or the first random access opportunity. The first terminal device can use the identifier included in the message that triggers the first time unit or the first random access opportunity as the identifier of the associated process. At this time, the first terminal device uses the identifier included in the first query message as the identifier of the associated process.

[0281] This application describes the example of a first terminal device sending a first random access request message in a first time unit. The first terminal device may also send the first random access request message in other time units. This application does not limit the specific time unit in which the first terminal device sends the first random access request message. How the first terminal device determines the time unit for sending the first random access request message can be referred to the description in step 801 and will not be repeated here.

[0282] Assuming that the number of processes configured in the selected message is greater than two, the network device may send a message related to the second process corresponding to the second identifier before responding to the first random access request message. Specifically, the process may include steps 1004 and 1005. In one implementation, if the network device sends a response message to the first random access request message, "before" responding to the first random access request message may refer to "before" sending the response message to the first random access request message. In another implementation, if the network device does not send a response message to the first random access request message, "before" responding to the first random access request message may refer to "before" the moment when the interval between the first random access request message and the first random access request message is equal to the first duration.

[0283] Step 1004: The network device sends a first query repetition message, and the second query repetition message includes a second identifier.

[0284] The second query repetition message triggers a time unit or random access opportunity in the second process corresponding to the second identifier. For example, the second query repetition message at this time triggers the second time unit or random access opportunity among X time units.

[0285] The terminal device associated with the second identifier can initiate random access in the time unit triggered by the second query repetition message or the random access opportunity. The specific process will not be repeated here.

[0286] Step 1005: The second terminal device sends a second random access request message to the network device in a second time unit or a second random access opportunity.

[0287] Correspondingly, the network device receives the second random access request message in the second time unit or the second random access opportunity, wherein the second random access opportunity is within the second time unit.

[0288] The second random access request message is used to initiate random access. The content included in the second random access request message can be referred to the description in step 906 and will not be repeated here. The second random access request message also includes a second identifier, so that the network device can determine the process associated with the second terminal device based on the second identifier.

[0289] The second terminal device may determine an identifier (e.g., the second identifier) ​​as the identifier of the process associated with itself based on the maximum number of processes indicated in the selection message, the maximum value of process identifiers, or the value range of process identifiers. The specific process is described in step 801 and is not further described here. Accordingly, if the second terminal device determines that the identifier it selected is the same as the second identifier, it determines to associate with the second identifier and identifies itself as the recipient of the second query message.

[0290] This application describes the example of the second terminal device sending a second random access request message in the second time unit. The second terminal device may also send a second random access request message in other time units. This application does not limit in which time unit the second terminal device sends the second random access request message. Please refer to the description in step 1003 and will not repeat it here.

[0291] Step 1006: The network device sends a first random access response message.

[0292] Correspondingly, the first terminal device receives the first random access response message.

[0293] Here, the network device successfully receives the first random access request message and allows the first terminal device to access the random access. If the network device does not successfully receive the first random access request message, it may not send the first random access response message.

[0294] In the present application, the first random access response message includes the first identifier and may also include part or all of the content of the first random access request message. If the first terminal device determines that the first random access response message includes the first identifier, it is determined to be the receiving end of the first random access response message. If the first terminal device determines that the first random access response message includes part or all of the content of the first random access request message, it determines that the random access is successful.

[0295] If the first terminal device determines that the random access is successful, it can send uplink data to the network device.

[0296] Step 1007: The first terminal device sends a first uplink message to the network device.

[0297] Correspondingly, the network device receives the first uplink message.

[0298] The first uplink message may include a first identifier and first uplink data, and the first uplink data may include at least one of the following: an EPC of the first terminal device, a TID of the first terminal device, content stored in a reserved area of ​​the first terminal device, content stored in a user storage area of ​​the first terminal device, etc. The first uplink data may also include other data, which is not limited in this application.

[0299] If the random access of the second terminal device is successful, steps 1008 and 1009 may also be included.

[0300] Step 1008: The network device sends a second random access response message.

[0301] Correspondingly, the second terminal device receives the second random access response message. The random access response message may also be called a contention resolution message or a confirmation message.

[0302] Here, the network device successfully receives the second random access request message and allows the second terminal device to access the random access. If the network device does not successfully receive the second random access request message, it may not send the second random access response message.

[0303] In the present application, the second random access response message includes the second identifier and may also include part or all of the content of the second random access request message. If the second terminal device determines that the second random access response message includes the second identifier, it is determined to be the receiving end of the second random access response message. If the second terminal device determines that the second random access response message includes part or all of the content of the second random access request message, it determines that the random access is successful.

[0304] If the second terminal device determines that the random access is successful, it can send uplink data to the network device.

[0305] Step 1009: The second terminal device sends a second uplink message to the network device.

[0306] Correspondingly, the network device receives the second uplink message.

[0307] The second uplink message may include a second identifier and second uplink data, and the second uplink data may include at least one of the following: an EPC of the second terminal device, a TID of the second terminal device, content stored in a reserved area of ​​the second terminal device, content stored in a user storage area of ​​the second terminal device, etc. The second uplink data may also include other data, which is not limited in this application.

[0308] Optionally, other uplink data or messages sent by the second terminal device may also carry an identifier of a process associated with the second terminal device, for example, the second identifier.

[0309] Step 1010: The network device sends a second query repetition message, where the second query repetition message includes a first identifier.

[0310] The second query repetition message triggers a time unit or random access opportunity in the first process corresponding to the first identifier. For example, the second query repetition message at this time triggers the third time unit or random access opportunity among X time units.

[0311] The terminal device associated with the first identifier can initiate random access in the time unit triggered by the second query repetition message or the random access opportunity. The specific process will not be repeated here.

[0312] Optionally, after the second terminal device sends the first uplink message or receives the second query repetition message, the flag bit can be updated. For example, if the flag bit of the first terminal device is in state A when it receives the selection message, the first terminal device can update the flag bit to state B. If the selection message includes a session identifier, the first terminal device updates the flag bit corresponding to the session identifier to state B. In this way, there is no need to respond to the query repetition message including the first identifier again. If the first terminal device fails to access or collides, the flag bit of the first terminal device remains unchanged, so it can respond to the query repetition message including the first identifier again, that is, initiate random access in the time unit or random access opportunity triggered by the query repetition message including the first identifier.

[0313] Optionally, the second terminal device can update the flag bit after sending the second uplink message or receiving the second query repetition message. For example, if the flag bit is in state A when the second terminal device receives the selection message, the second terminal device can update the flag bit to state B.

[0314] Optionally, in an implementation that does not support the flag bit, if the terminal device successfully accesses, or successfully accesses and completes data transmission, it will no longer respond to subsequent query messages (messages that trigger a new round of access). Specifically, it may not respond to such messages for a period of time, which can be predefined or configured by the network device.

[0315] In the above process, two processes are taken as an example. If the number of processes is greater than two, messages of other processes may also be included between step 1003 and step 1006, and between step 1007 and step 1010, which will not be repeated here.

[0316] The order of the above messages is only an example. In another implementation, step 1004 and step 1005 can also be executed between step 1002 and step 1003, and step 1008 and step 1009 can also be executed between step 1006 and step 1007. This application does not limit this.

[0317] In the above process, when the network device is configured with multiple processes, only one query message is sent, but different processes are distinguished by querying the identifier in the repeated message. This can reduce the query message sending overhead and improve resource utilization.

[0318] In each of the above embodiments of the present application, if only one device or terminal device is operating in a process at a time, the network device can save the correspondence between the process identifier and the core network direct interface identifier. When subsequent downlink data arrives, the data can be sent to the terminal device of the process based on the saved association. In this case, the terminal device is also the sole recipient of the data.

[0319] It is understood that in order to implement the functions in the above embodiments, the terminal device or network device includes hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of each example described in the embodiments disclosed in this application, 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 hardware or in a manner driven by computer software depends on the specific application scenario and design constraints of the technical solution.

[0320] The following is a schematic diagram of the structure of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the terminal device or network device in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.

[0321] As shown in Figure 11, a communication device 1100 includes a processing unit 1110 and a communication unit 1120. The communication device 1100 is used to implement the functions of the terminal device or network device in each of the above-mentioned method embodiments.

[0322] In one implementation, the communication device 1100 is configured to implement the following functions:

[0323] A processing unit, configured to send a first message through a communication unit; the first message is used to trigger a first random access opportunity, and the first message indicates a first identifier;

[0324] The processing unit is configured to receive a first random access request message from a first terminal device at the first random access opportunity through the communication unit; the first terminal device is associated with the first identifier; and before responding to the first random access request message, send a second message; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with the terminal device of the second identifier.

[0325] In one implementation, the communication device 1100 is configured to implement the following functions:

[0326] A communication unit, configured to receive a first message; the first message is used to trigger a first random access opportunity, the first message indicates a first identifier, and the first random access opportunity is used to initiate random access with a terminal device with the first identifier;

[0327] a processing unit, configured to determine an association with the first identifier;

[0328] The communication unit is configured to send a first random access request message at the first random access opportunity; receive a second message; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with a terminal device with the second identifier;

[0329] The processing unit is configured to determine that the second message is not associated with the second identifier, and ignore or discard the second message.

[0330] A more detailed description of the processing unit 1110 and the communication unit 1120 can be directly obtained by referring to the relevant descriptions in the above-mentioned method embodiments, and will not be repeated here.

[0331] It should be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the form of a program in a memory, called by a certain processing element of the device and execute the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each operation of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or by software called through the processing element.

[0332] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital singnal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0333] The above-mentioned receiving unit is an interface circuit of the device, which is used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is the interface circuit of the chip used to receive signals from other chips or devices. The above-mentioned sending unit is an interface circuit of the device, which is used to send signals to other devices. For example, when the device is implemented as a chip, the sending unit is the interface circuit of the chip used to send signals to other chips or devices.

[0334] As another possible product form, the terminal device or network device of the embodiment of the present application can be implemented by a general bus architecture. For ease of explanation, refer to Figure 12, which is a structural diagram of a communication device 1200 provided in an embodiment of the present application, wherein the communication device 1200 includes a processor 1201 and a transceiver 1202. The communication device 1200 can be a terminal device, or a chip or chip system therein; or, the communication device 1200 can be a network device, or a chip or module therein. Figure 12 only shows the main components of the communication device 1200. In addition to the processor 1201 and the transceiver 1202, the communication device 1200 can further include a memory 1203, and an input and output device (not shown in the figure).

[0335] Optionally, the processor 1201 is primarily used to process communication protocols and communication data, as well as control the entire communication device, execute software programs, and process software program data. The memory 1203 is primarily used to store software programs and data. The transceiver 1202 may include a radio frequency circuit and an antenna. The radio frequency 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 and output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0336] Optionally, the processor 1201 , the transceiver 1202 , and the memory 1203 may be connected via a communication bus.

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

[0338] In another implementation, the RF circuit and antenna can be set independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna can be arranged remotely from the communication device.

[0339] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the above-mentioned communication device 1100 may take the form of the communication device 1200 shown in FIG. 12 .

[0340] As an example, the functions / implementation process of the processing unit 1110 in FIG11 may be implemented by the processor 1201 in the communication device 1200 shown in FIG12 calling computer-executable instructions stored in the memory 1203. The functions / implementation process of the communication unit 1120 in FIG11 may be implemented by the transceiver 1202 in the communication device 1200 shown in FIG12.

[0341] As another possible product form, the terminal device or network device in the present application may adopt the structure shown in Figure 13, or include the components shown in Figure 13. Figure 13 is a schematic diagram of the structure of a communication device 1300 provided in the present application.

[0342] As shown in FIG13 , a communication device 1300 includes at least one processor 1301. Optionally, the communication device further includes a communication interface 1302.

[0343] When the program instructions are executed in the at least one processor 1301, the communication device 1300 can implement the method provided in any of the aforementioned embodiments and any possible designs therein. Alternatively, the processor 1301 implements the method provided in any of the aforementioned embodiments and any possible designs therein through logic circuits or by executing code instructions.

[0344] The communication interface 1302 can be used to receive program instructions and transmit them to the processor. Alternatively, the communication interface 1302 can be used for the communication device 1300 to communicate with other communication devices, such as exchanging control signaling and / or service data. Exemplarily, the communication interface 1302 can be used to receive signals from devices other than the communication device 1300 and transmit them to the processor 1301, or to send signals from the processor 1301 to other communication devices other than the communication device 1300.

[0345] Optionally, the communication interface 1302 may be a code and / or data read and write interface circuit, or the communication interface 1302 may be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.

[0346] Optionally, the communication device 1300 may further include at least one memory 1303, which may be used to store required program instructions and / or data. It should be noted that the memory 1303 may exist independently of the processor 1301 or may be integrated with the processor 1301. The memory 1303 may be located within or outside the communication device 1300, without limitation.

[0347] Optionally, the communication device 1300 may further include a power supply circuit 1304, which may be used to supply power to the processor 1301. The power supply circuit 1304 may be located in the same chip as the processor 1301, or in another chip other than the chip where the processor 1301 is located.

[0348] Optionally, the communication device 1300 may further include a bus, and various parts of the communication device 1300 may be interconnected via the bus.

[0349] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the communication device 1100 shown in FIG. 11 may take the form of the communication device 1300 shown in FIG. 13 .

[0350] As an example, the functions / implementation processes of the processing unit 1110 in FIG11 may be implemented by the processor 1301 in the communication device 1300 shown in FIG13 calling computer-executable instructions stored in the memory 1303. The functions / implementation processes of the communication unit 1120 in FIG11 may be implemented by the communication interface 1302 in the communication device 1300 shown in FIG13.

[0351] It should be noted that the structure shown in FIG13 does not constitute a specific limitation on the terminal device or network device. For example, in other embodiments of the present application, the terminal device or network device may include more or fewer components than shown, or combine or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0352] When the communication device is a chip used in a terminal, the terminal chip implements the functions of the terminal in the above method embodiments. The terminal chip receives information from other modules in the terminal (such as a radio frequency module or antenna), and the information is sent by the base station to the terminal; or the terminal chip sends information to other modules in the terminal (such as a radio frequency module or antenna), and the information is sent by the terminal to the base station.

[0353] When the above-mentioned communication device is a module applied to a base station, the base station module implements the functions of the base station in the above-mentioned method embodiment. The base station module receives information from other modules in the base station (such as a radio frequency module or an antenna), and the information is sent by the terminal to the base station; or the base station module sends information to other modules in the base station (such as a radio frequency module or an antenna), and the information is sent by the base station to the terminal. The base station module here can be the baseband chip of the base station, or it can be a DU or other module. The DU here can be a DU under the open radio access network (O-RAN) architecture.

[0354] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0355] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also exist in a base station or a terminal as discrete components.

[0356] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are performed in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0357] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0358] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, optical storage, etc.) that contain computer-usable program code.

[0359] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0360] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0361] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: include: Sending a first message; The first message is used to trigger a first random access opportunity, and the first message indicates a first identifier; Receiving a first random access request message from a first terminal device at the first random access opportunity; The first terminal device is associated with the first identifier; Before responding to the first random access request message, a second message is sent; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with a terminal device with the second identifier.

2. The method according to claim 1, characterized in that The method further comprises: Send a first response message corresponding to the first random access request message.

3. The method according to claim 1 or 2, characterized in that: The first identifier is used to identify the first process, and the second identifier is used to identify the second process. The value of the first identifier and the value of the second identifier are both less than or equal to the first value. The first value represents the number of processes. The first value is indicated by the first message or the third message, and the third message is a message located before the first message.

4. The method according to any one of claims 2 to 3, characterized in that: The maximum duration between the first random access request message and a first response message corresponding to the first random access request message is a first duration; The first duration is greater than or equal to the duration required to send the second message and receive a second random access request message from the terminal device.

5. The method according to any one of claims 2 to 4, characterized in that: The first response message includes the first identifier and part or all of the content of the first random access request.

6. The method according to any one of claims 1 to 5, characterized in that: The first message is a query message or a query repetition message, and the second message is a query repetition message.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: receiving a second random access request message from a second terminal device at the second random access opportunity; the second terminal device is associated with the second identifier; and sending a second response message corresponding to the second random access request message; wherein the second message and the second random access request message are located between the first random access request message and the first response message.

8. The method according to any one of claims 1 to 7, characterized in that: The first terminal device is an environmental Internet of Things terminal device.

9. The method according to any one of claims 1 to 8, characterized in that: The method further comprises: receiving a fourth message from a core network device, where the fourth message includes first data and the first identifier; A fifth message is sent to the first terminal device, where the fifth message includes the first data and the first identifier.

10. The method according to any one of claims 1 to 9, characterized in that: The method further comprises: An uplink message is received from the first terminal device, where the uplink message includes the first identifier and uplink data.

11. A communication method, characterized in that: include: Receive a first message; the first message is used to trigger a first random access opportunity, the first message indicates a first identifier, and the first random access opportunity is used to initiate random access with a terminal device of the first identifier; Determine to associate with the first identifier, and send a first random access request message at the first random access opportunity; receiving a second message; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with a terminal device with the second identifier; Determine that it is not associated with the second identifier, and ignore or discard the second message.

12. The method according to claim 11, characterized in that The first identifier is used to identify the first process, and the second identifier is used to identify the second process. The value of the first identifier and the value of the second identifier are both less than or equal to the first value. The first value represents the number of processes. The first value is indicated by the first message or the third message, and the third message is a message located before the first message.

13. The method according to claim 12, characterized in that The determining to associate with the first identifier includes: If the first identifier is equal to the third identifier of the process associated with the first terminal device, it is associated with the first identifier; wherein the third identifier is determined according to the first value.

14. The method according to claim 13, characterized in that The third identifier is determined according to the first value, including: Taking a value less than or equal to the first value as the third identifier; Alternatively, the third identifier is determined according to the device identifier of the first terminal device and the first value.

15. The method according to any one of claims 11 to 14, characterized in that: The maximum duration between the first random access request message and a first response message corresponding to the first random access request message is a first duration; The first duration is greater than or equal to the duration required to send the second message and receive a second random access request message from the terminal device.

16. The method according to any one of claims 11 to 15, characterized in that: The method further comprises: A first response message corresponding to the first random access request message from the network device is received, where the first response message includes the first identifier and part or all of the content of the first random access request.

17. The method according to any one of claims 11 to 16, characterized in that: The first message is a query message or a query repetition message, and the second message is a query repetition message.

18. A communication device, characterized in that: include: A processing unit, configured to send a first message through a communication unit; the first message is used to trigger a first random access opportunity, and the first message indicates a first identifier; The processing unit is configured to receive, through the communication unit, a first random access request message from a first terminal device at the first random access opportunity; the first terminal device is associated with the first identifier; Before responding to the first random access request message, a second message is sent; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with a terminal device with the second identifier.

19. The device according to claim 18, characterized in that The communication unit is also used for: Send a first response message corresponding to the first random access request message.

20. The device according to claim 18 or 19, characterized in that The first identifier is used to identify the first process, and the second identifier is used to identify the second process. The value of the first identifier and the value of the second identifier are both less than or equal to the first value. The first value represents the number of processes. The first value is indicated by the first message or the third message, and the third message is a message located before the first message.

21. The device according to any one of claims 19 to 20, characterized in that The maximum duration between the first random access request message and a first response message corresponding to the first random access request message is a first duration; The first duration is greater than or equal to the duration required to send the second message and receive a second random access request message from the terminal device.

22. The device according to any one of claims 19 to 21, characterized in that The first response message includes the first identifier and part or all of the content of the first random access request.

23. The device according to any one of claims 18 to 22, characterized in that The communication unit is also used for: receiving a second random access request message from a second terminal device at the second random access opportunity; the second terminal device is associated with the second identifier; and sending a second response message corresponding to the second random access request message; wherein the second message and the second random access request message are located between the first random access request message and the first response message.

24. A communication device, characterized in that: include: A communication unit, configured to receive a first message; The first message is used to trigger a first random access opportunity, the first message indicates a first identifier, and the first random access opportunity is used to initiate random access with a terminal device of the first identifier; A processing unit, configured to determine an association with the first identifier; The communication unit is configured to send a first random access request message at the first random access opportunity; receiving a second message; the second message is used to trigger a second random access opportunity, the second message indicates a second identifier, and the second random access opportunity is used to initiate random access with a terminal device with the second identifier; The processing unit is used to determine that the second message is not associated with the second identifier, and ignore or discard the second message.

25. The device according to claim 24, characterized in that The first identifier is used to identify the first process, and the second identifier is used to identify the second process. The value of the first identifier and the value of the second identifier are both less than or equal to the first value. The first value represents the number of processes. The first value is indicated by the first message or the third message, and the third message is a message located before the first message.

26. The device according to claim 25, characterized in that The processing unit is specifically used for: If the first identifier is equal to the third identifier of the process associated with the first terminal device, it is associated with the first identifier; wherein the third identifier is determined according to the first value.

27. The device according to any one of claims 24 to 26, characterized in that The communication unit is also used for: A first response message corresponding to the first random access request message from the network device is received, where the first response message includes the first identifier and part or all of the content of the first random access request.

28. A communication system, characterized in that: include: Network equipment and terminal equipment; The network device is used to implement the method according to any one of claims 1 to 10; The terminal device is used to implement the method according to any one of claims 11 to 17.

29. A communication device, characterized in that: including a processor and a memory; The processor is configured to execute the computer program or instructions stored in the memory, so that the communication device implements the method according to any one of claims 1 to 17.

30. A computer-readable storage medium, characterized in that: A computer program or instruction is stored, and when the computer program or instruction is executed on a computer, the computer is caused to implement the method according to any one of claims 1 to 17.

31. A chip, characterized in that: The chip comprises a processor, which is coupled to a memory and is used to execute a computer program or instruction stored in the memory, so that the chip implements the method according to any one of claims 1 to 17.

32. A computer program product, characterized in that When a computer reads and executes the computer program product, the method according to any one of claims 1 to 17 is executed.

Images