Communication transmission method, device, chip, storage medium, and program product

Abstract

Embodiments of the present application provide a communication method. The method comprises: a first device receives a first paging message sent by a second device, wherein the first paging message is used for determining whether to re-perform random access, the first paging message and a second paging message are associated with the same service, and the second paging message has triggered an access procedure for the first device to access the second device.

Description

A communication transmission method and device, chip, storage medium, and program product Technical Field

[0001] This application relates to the field of communication technology, specifically to a wireless communication method and device, chip, storage medium, and program product. Background Technology

[0002] Ambient IoT (A-IoT) communication employs energy harvesting and backscatter communication technologies. An A-IoT device is an IoT device that uses various forms of environmental energy, such as radio frequency energy, light energy, solar energy, thermal energy, and mechanical energy, to power itself. Such devices may have no energy storage capacity or very limited energy storage capacity (e.g., using capacitors with a capacitance of tens of microfarads (µF)).

[0003] A-IoT supports many industrial applications, such as automated warehousing, smart homes, smart agriculture, and finding personal items. Summary of the Invention

[0004] This application provides a communication method and device, a chip, a storage medium, and a program product.

[0005] This application provides a communication method, the method comprising:

[0006] The first device receives a first paging message sent by the second device, the first paging message being used to determine whether to re-execute random access;

[0007] The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

[0008] This application provides a communication method, the method comprising:

[0009] The second device sends a first paging message to the first device, the first paging message being used to determine whether to re-execute random access;

[0010] The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

[0011] This application provides a first device, including:

[0012] The first communication unit is configured to receive a first paging message sent by the second device, wherein the first paging message is used to determine whether to re-execute random access;

[0013] The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

[0014] This application provides a second device, including:

[0015] The second communication unit is configured to send a first paging message to the first device, wherein the first paging message is used to determine whether to re-execute random access;

[0016] The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

[0017] The communication device provided in this application embodiment can be either the first device or the second device in the above-described scheme. The communication device includes a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to execute the aforementioned wireless communication method.

[0018] The chip provided in this application embodiment is used to implement the above-described wireless communication method.

[0019] Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the aforementioned wireless communication method.

[0020] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the above-described wireless communication method.

[0021] The computer program product provided in this application includes computer program instructions that cause a computer to execute the above-described wireless communication method.

[0022] The computer program provided in this application embodiment, when run on a computer, causes the computer to execute the above-described wireless communication method.

[0023] Through the above technical solution, when the first device has already performed the access process to the second device based on the second paging message, it receives a first paging message with the same service associated with the second paging message. Based on the first paging message, it determines whether to re-execute random access. This avoids the situation where the first device ignores the first paging message and communication between the first device and the second device cannot be guaranteed if the second device attempts to trigger the first device to re-access through the first paging message. Attached Figure Description

[0024] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0025] Figure 1 is a schematic diagram of a communication architecture provided in an embodiment of this application;

[0026] Figure 2 is a flowchart illustrating the wireless communication method provided in an embodiment of this application;

[0027] Figure 3 is a flowchart illustrating the wireless communication method provided in an embodiment of this application;

[0028] Figure 4 is a flowchart illustrating the wireless communication method provided in an embodiment of this application.

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

[0030] Figure 6 is a flowchart illustrating the wireless communication method provided in an embodiment of this application;

[0031] Figure 7 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0032] Figure 8 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0033] Figure 9 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0034] Figure 10 is a flowchart illustrating the communication method provided in an embodiment of this application;

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

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

[0037] Figure 13 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0038] Figure 14 is a flowchart illustrating the communication method provided in an embodiment of this application;

[0039] Figure 15 is a schematic diagram of the structural composition of the first device provided in an embodiment of this application;

[0040] Figure 16 is a schematic diagram of the structural composition of the second device provided in an embodiment of this application;

[0041] Figure 17 is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0042] Figure 18 is a schematic structural diagram of a chip according to an embodiment of this application;

[0043] Figure 19 is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0045] Figure 1 is a schematic diagram of an application scenario according to an embodiment of this application. As shown in Figure 1, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0046] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Internet of Things (IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), 6G communication system, or future communication systems, etc.

[0047] In the communication system 100 shown in Figure 1, network device 120 may be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 (e.g., UE) located within that coverage area.

[0048] Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a base station in a 6G system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, access point, vehicle-mounted equipment, wearable device, hub, switch, bridge, router, or network equipment in a future evolved Public Land Mobile Network (PLMN), etc.

[0049] Terminal device 110 can be any terminal device, including but not limited to terminal devices that are connected to network device 120 or other terminal devices via wired or wireless connections.

[0050] For example, the terminal device 110 can refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, terminal device in a 6G network, or terminal device in a future evolved network, etc.

[0051] Terminal device 110 can be used for device-to-device (D2D) communication.

[0052] The communication system 100 may also include a core network device 130 that communicates with the network device 120. The core network device 130 may be a 5G core network (5G Core, 5GC) device. For example, the 5GC device may include Access and Mobility Management Function (AMF) network elements, Location Management Function (LMF) network elements, Unified Data Management (UDM) network elements, Network Exposure Function (NEF) network elements, Application Function (AF) network elements, Network Function (NF) network elements, Home Gateway Mobile Location Center (H-GMLC) network elements, Visited Gateway Mobile Location Center (V-GMLC) network elements, Location Services Client (LCS Client), etc.

[0053] It should be noted that core network device 130 can also be an Evolved Packet Core (EPC) device for LTE networks, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C.

[0054] It should also be noted that during network evolution, the aforementioned core network equipment may be called by other names, or new network entities may be formed by dividing the functions of the core network. This application does not impose any restrictions on this.

[0055] Figure 1 exemplarily illustrates a network device, a core network device, and two terminal devices. Optionally, the communication system 100 may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0056] It should be noted that Figure 1 is merely an example illustrating the system to which this application applies. Of course, the method shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0057] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0058] Ambient power enabled IoT, or A-IoT for short, is a new type of wireless communication technology that achieves significant self-sufficiency by utilizing energy sources in the environment (such as radio frequency energy, light energy, solar energy, thermal energy, and mechanical energy) and relies on cellular networks for connectivity.

[0059] The Internet of Things (IoT) is built on early cellular IoT standards such as NB-IoT (Narrowband IoT) and LTE-M. While these standards have achieved low power consumption and wide-area connectivity, they still require regular battery replacements. The goal of A-IoT is to reduce battery dependence and minimize large-scale environmental impact and costs.

[0060] A-IoT focuses on the following technologies:

[0061] Environmental energy harvesting: The equipment operates on microwatt-level energy harvested from the environment;

[0062] Minimalist hardware design: Reduce costs by simplifying hardware (target is devices under $1);

[0063] Ultra-dense deployment: Supports large-scale, dense deployment of millions of devices per square kilometer;

[0064] Cellular network convergence: compatible with existing 5G networks;

[0065] Backscatter communication: Devices transmit data by reflecting or modifying ambient radio frequency (RF) signals (such as TV towers, WIFI, and cellular base stations), avoiding high-performance wireless transmission.

[0066] Wake-up Receiver: An ultra-low-power receiver that wakes up the device only when necessary, minimizing power consumption;

[0067] Sparse bursty data: used for optimization of low-frequency, small-volume data transmission (e.g., temperature readings, location updates).

[0068] Use cases for A-IoT may include:

[0069] Smart logistics: Tracking of pallets, parcels, and containers without battery limitations;

[0070] Agriculture: Remote monitoring of farmland soil / weather;

[0071] Smart cities: Monitoring of infrastructure (bridges / pipelines, etc.) using maintenance-free sensors;

[0072] Retail: Low-cost, product-level tracking within stores.

[0073] Introduction to Backscatter Communication in A-IoT

[0074] Backscatter communication is a fundamental technology in 3GPP A-IoT for enabling battery-free, self-powered devices. Backscatter devices transmit data without generating their own radio waves by utilizing existing radio frequency signals in the environment (such as signals from TV towers, Wi-Fi routers, or cellular networks). Instead, they reflect and modulate existing signals, significantly reducing power consumption and enabling operation through energy harvesting.

[0075] The process of backscattering:

[0076] Environmental RF source: A nearby transmitter is emitting RF signals;

[0077] Modulation: Backscattering devices encode data by changing the antenna impedance, thereby altering the reflected environmental signals;

[0078] Receive: The reflected signal after decoding and modulation by a dedicated gateway or cellular base station.

[0079] This process avoids the need for high-power radios, allowing devices to operate on microwatt-level energy harvested from light, heat, or RF waves.

[0080] Energy efficiency of backscattering:

[0081] Non-active transmission: The energy consumed by the device is used only for impedance switching (nanowatt-level energy consumption);

[0082] No frequency generation required: Eliminating the need for oscillators and complex circuitry reduces equipment cost and complexity.

[0083] A-IoT can include the following four topologies:

[0084] Topology 1: Base Station (BS) - A - IoT Equipment

[0085] The base station communicates directly with the A-IoT device in two directions. The A-IoT device can also be used as a reader for backscattered signals.

[0086] Topology 2: BS - intermediate node - A - IoT device

[0087] A-IoT devices connect to the BS through intermediate UE nodes, which handle reader functions, thereby achieving wider coverage and flexibility.

[0088] Topology 3: BS - Assisting Node - A - IoT Device

[0089] A-IoT devices transmit data to the base station (BS) but receive commands or power from auxiliary nodes (such as user equipment (UE) or relay nodes). This approach allows for asymmetric communication, where uplink / downlink roles are defined between the base station and auxiliary nodes.

[0090] Topology 4: UE to A-IoT device

[0091] A-IoT devices communicate directly with UEs (e.g., smartphones) acting as both exciters (power sources) and readers. This topology supports distributed applications, such as asset tracking in retail or logistics, without the involvement of a base station (BS). The UE will send D2R messages directly to the APP server outside the 3GPP network range.

[0092] It should be noted that in the above topology, the base station in topology 1, the intermediate node in topology 2, and the base station and auxiliary node in topology 3 can all be understood as readers. A-IoT devices can be understood as devices or tags. The transmission from the reader to the device is called reader to device (R2D) transmission, and the transmission from the device to the reader is called device to reader (D2R) transmission.

[0093] RFID transmission resource allocation method

[0094] The time-domain-based resource allocation aims to avoid conflicts when multiple tags respond simultaneously. The method includes: the Reader divides time into time slots and broadcasts the number of time slots (frame size); the tag randomly selects a time slot to transmit its ID; wherein the frame size can be dynamically adjusted based on the number of tags.

[0095] The transmission resource allocation process is as follows:

[0096] 1. Query command (beginning of frame)

[0097] The reader initiates a frame by sending a query command carrying the following parameters: Q: frame size (N=2 Q ); Session: Specifies the session (S0–S3) in which the label participates.

[0098] The tags receive a query command, generate a random timeslot number (0 to N-1), and reset their timeslot counters to that value.

[0099] 2. Use QueryRep for time-slot advancement

[0100] The reader sends a query response command (not a restart frame) in each subsequent time slot; the tag decrements its time slot counter by 1 upon receiving the QueryRep; the tag only responds when the time slot counter reaches 0.

[0101] For example, if a tag selects time slot 3, its counter starts at 3. After each QueryRep, the counter decrements: 3 → 2 → 1 → 0. In time slot 0 (after the fourth QueryRep), the tag transmits its ID.

[0102] 3. Time Slot Results

[0103] Empty slot: No tag response, the reader sends a QueryRep to advance to the next slot.

[0104] Success Slot: A tag responder sends a positive acknowledgment (ACK) and remains silent.

[0105] Conflict Slot: Multiple tags respond to the reader, record the conflict, and continue.

[0106] 4. Adjust frame size (query adjustment)

[0107] If collisions are frequent, the reader can use the QueryAdjust command to dynamically adjust the Q (frame size) within a frame.

[0108] 5. End of frame

[0109] After all N time slots have been processed, the reader sends a new query command to start a new frame for the unresolved tags.

[0110] In the event of a transmission failure, how to trigger reconnection to the reader? Currently, the RAN2 protocol agrees that the reader can send an optional ACK / NACK for received D2R messages, which can trigger the A-IoT device to reconnect to the network later. For D2R messages (at least for msg3), a NACK-based mechanism is supported for determining reconnection. Whether a timer or explicit message is needed, and when the reader should send feedback, requires further discussion.

[0111] The relevant technologies include the following two solutions:

[0112] The first approach is to use an explicit NACK message for receiving D2R messages, as shown in Figure 2:

[0113] S201, the A-IOT device sends a D2R message (e.g., Msg3) to the reader.

[0114] S202. If the reader does not receive a D2R message, it returns a NACK to the A-IOT device.

[0115] The S203 and A-IoT devices have decided to perform a re-access later.

[0116] S204. The reader sends a subsequent paging message to the A-IoT device.

[0117] S205 and A-IOT devices perform reconnection.

[0118] S206, A-IOT devices send D2R messages (e.g., Msg3) to the reader.

[0119] Here, if the A-IOT device successfully reconnects to the reader, it sends a D2R message.

[0120] If the A-IoT device does not receive a NACK, it means that the A-IoT device has not received any messages sent to it within a certain period of time, and therefore considers the D2R transmission to be successful. (See Figure 3.)

[0121] S301, A-IOT devices send D2R messages (e.g., Msg3) to the reader.

[0122] After a period of time, the S302 and A-IOT devices consider the D2R message transmission to be successful.

[0123] S303, the reader sends a follow-up paging message to the A-IOT device.

[0124] S304 and A-IOT devices do not perform reconnection.

[0125] However, if the Reader sends a NACK, but the A-IoT device does not receive the NACK, the A-IoT device will incorrectly determine that the D2R message transmission was successful, and therefore will not reconnect to the network, as shown in Figure 4.

[0126] S401, A-IOT device failed to send D2R message (e.g., Msg3) to reader;

[0127] S402, the reader failed to send a NACK to the A-IOT device;

[0128] Here, it can be assumed that the A-IoT device successfully sent a D2R message (e.g., Msg3) to the reader, but the reader failed to send a NACK to the A-IoT device.

[0129] If an S403 or A-IOT device does not receive a NACK within a certain period of time, it is considered that the D2R message transmission was successful.

[0130] S404, the reader sends a follow-up paging message to the A-IOT device.

[0131] S405 and A-IOT devices do not perform reconnection.

[0132] Another timer-based scheme is shown in Figures 5 and 6. Figure 5 shows the flow when the reader successfully receives the D2R message, i.e., the D2R message transmission is successful. Figure 6 shows the flow when the reader fails to receive the D2R message, i.e., the D2R message transmission is unsuccessful.

[0133] As shown in Figure 5, it includes:

[0134] S501, A-IOT devices send D2R messages (e.g., Msg3) to the reader.

[0135] If the S502 reader successfully receives the D2R message, it returns an ACK to the A-IOT device.

[0136] The S503 and A-IOT devices determine that the D2R message transmission was successful based on the received ACK.

[0137] S504, the reader sends a follow-up paging message to the A-IOT device.

[0138] S505 and A-IOT devices do not perform reconnection.

[0139] As shown in Figure 6, it includes:

[0140] S601, the A-IOT device sends a D2R message (e.g., Msg3) to the reader, but the reader fails to receive the D2R message.

[0141] S602. If the A-IOT device does not receive an ACK during the timer's operation, the D2R message transmission is considered to have failed.

[0142] S603, the reader sends a follow-up paging message to the A-IOT device.

[0143] S604 and A-IOT devices perform reconnection.

[0144] The S605 and A-IoT devices send D2R messages (e.g., Msg3) to the reader. By default, the reader needs to send an ACK to the A-IoT device. If the A-IoT device does not receive an ACK within a limited time after sending the D2R message, it considers the D2R message unsuccessful and decides to reconnect to the reader when it receives a subsequent paging message.

[0145] An abnormal situation occurs when the A-IoT device does not receive an ACK from the reader. It will assume the previous D2R transmission failed and decide to retransmit the D2R message upon receiving a subsequent paging message. This is not a serious problem, as the device is simply repeating the D2R message transmission. However, this solution requires the reader to constantly send an ACK to the A-IoT device to prevent it from reconnecting. Considering that good channel conditions are common, this method incurs more signaling overhead than the previous method.

[0146] For methods based on explicit NACK messages, when a NACK sent by the reader is not received by the A-IoT device, an inconsistency arises between the reader and the A-IoT device regarding the success of the previous D2R message transmission. If this inconsistency cannot be resolved, the A-IoT device will not reconnect to the reader, even if the reader subsequently sends multiple subsequent A-IoT paging messages with the same transaction ID as the previous (initial) A-IoT paging message in an attempt to trigger reconnection. However, these messages are meaningless to the A-IoT device.

[0147] In view of this, in the communication method provided in the embodiments of this application, when the first device has already performed the access process to access the second device based on the second paging message, it receives a first paging message with the same service associated with the second paging message, and determines whether to re-execute random access based on the first paging message, so as to avoid the situation where the communication between the first device and the second device cannot be guaranteed due to the first device ignoring the first paging message when the second device attempts to trigger the first device to re-access through the first paging message.

[0148] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0149] This application provides a wireless communication method applied to a first device, as shown in FIG7. The method may include the following steps:

[0150] S701, the first device receives a first paging message sent by the second device, the first paging message being used to determine whether to re-execute random access; wherein, the first paging message and the second paging message are associated with the same service; the second paging message has triggered an access process for the first device to access the second device.

[0151] This application provides a wireless communication method applied to a second device, as shown in FIG8. The method may include the following steps:

[0152] S801, the second device sends a first paging message to the first device, the first paging message being used to determine whether to re-execute random access; wherein, the first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

[0153] The wireless communication method shown in Figure 7 or Figure 8 will now be described.

[0154] Both the first device and the second device can be nodes in the environmental Internet of Things (IoT).

[0155] The first device is a terminal device or an A-IoT terminal. The first device can connect to the network device through an intermediate device or a relay terminal.

[0156] In some embodiments, the first device may be understood as a tag or a terminal having a tag.

[0157] The second device is an intermediate device, relay device, or network device.

[0158] In some embodiments, the second device can be understood as a reader or interrogator or an intermediate UE with a reader, i.e., an intermediate node, a relay terminal, or a network device.

[0159] The first paging message is a paging message sent by the second device after the second paging message.

[0160] The first paging message and the second paging message are associated with the same service.

[0161] In some embodiments, the first paging message can be understood as a paging message triggered when the first device fails to access the second device based on the second paging message, or when the first device has successfully accessed the second device based on the second paging message but has not successfully received data about the service sent by the first device. In this case, the terminal device believes that it has successfully accessed the second device (accessed the network), but in reality, the second device has not successfully accessed the second device.

[0162] In some embodiments, the first paging message can be understood as a subsequent paging message or a subsequent A-IOT paging message, and the second paging message can be understood as a previous A-IOT paging message or an initial A-IOT paging message.

[0163] In some embodiments, the second paging message may be used to page the first device, to page a group of devices including the first device, or may not be configured to page any device (i.e., for any device that can successfully receive the second paging message).

[0164] In some embodiments, the first paging message may be used to page a first device, to page a group of devices including the first device, or may not specify a paging device (i.e., for any device that can successfully receive the first paging message).

[0165] The first device receives a first paging message and determines whether to re-execute random access based on the received first paging message. If it is determined that random access should be re-executed, the random access procedure is executed; if it is not determined that random access should be re-executed or that random access should not be re-executed, the random access procedure is not executed.

[0166] In some embodiments, the terminal device performing a random access procedure includes: the terminal device performing a re-access.

[0167] In some embodiments, the first device may receive one or more first paging messages and determine whether to re-execute random access based on all or part of one or more of the messages.

[0168] The second paging message triggering the access process for the first device to access the second device can be understood as the first device, upon receiving the second paging message, executing a random access process to access the second device based on the triggering of the second paging message. The execution result of this random access process can include: the first device failing to access the second device or the first device successfully accessing the second device. One scenario where the first device fails to access the second device is that the second device believes the first device has failed to access, but the first device believes it has successfully accessed.

[0169] If the first device has already performed the access process to access the second device based on the second paging message, and receives a first paging message with the same service associated with the second paging message, it determines whether to re-perform random access based on the first paging message. This is to prevent the first device from ignoring the first paging message in the event that the second device attempts to trigger the first device to re-access, thus ensuring communication between the first and second devices.

[0170] In some embodiments, the first paging message and the second paging message include the same first identifier, which indicates a first service, the first service being the service associated with the first paging message and the second paging message.

[0171] If the first device receives a paging message that includes the same first identifier as the second paging message, the first device considers the second paging message to be associated with the first service, and the paging message is also associated with the first service, determines that the paging message is the first paging message, and determines whether to re-execute random access based on the paging message.

[0172] In some embodiments, the first identifier includes a transaction ID associated with the first service.

[0173] In this embodiment of the application, the first identifier may be any identifier other than the transaction identifier. This embodiment of the application does not limit the first identifier that indicates the first service.

[0174] In some embodiments, one or more of the following are used to determine the re-execution of random access:

[0175] Rule 1: The number of times the first paging message is received is greater than the first threshold.

[0176] Rule 2: The first paging message includes first information, which is used to indicate reconnection;

[0177] Rule 3: The first paging message is received if the first timer times out;

[0178] Rule 4: The first paging message includes the second identifier.

[0179] The first device may determine to re-execute random access if the received first paging message satisfies one or more of rules one to four.

[0180] In one example, the first device may determine to re-execute random access if the number of times the first paging message is received is greater than a first threshold, and determine not to re-execute random access if the number of times the first paging message is received is less than or equal to the first threshold.

[0181] In one example, the first device may determine to re-perform random access if the first paging message contains a second identifier, and determine not to re-perform random access if the first paging message does not contain a second identifier.

[0182] In one example, the first device may determine to re-execute random access if the number of times the first paging message is received is greater than a first threshold and the first paging message includes first information, and determine not to re-execute random access if the number of times the first paging message is received is less than or equal to the first threshold, or the first paging message does not contain first information.

[0183] In one example, the first device may determine to re-execute random access if it receives a first paging message after the first timer expires and the number of times the first paging message is received is greater than a first threshold; or determine not to re-execute random access if it receives a first paging message before the first timer expires or the number of times the first paging message is received is less than or equal to the first threshold.

[0184] In one example, the first device may determine to re-execute random access if it receives a first paging message after the first timer expires and the received first paging message contains a second identifier, or determine not to re-execute random access if it receives a first paging message before the first timer expires or the first paging message does not contain a second identifier.

[0185] In this embodiment of the application, the rule used to determine whether to re-execute random access can be one of rule one to rule two or a combination of multiple rules from rule one to rule four, without limitation. In the case of multiple rules from rule one to rule four, the combination method of multiple rules from rule one to rule four is not limited.

[0186] In this embodiment of the application, the rule used to determine whether to re-execute random access may include one or more of the rules one to four mentioned above, and other rules may also be included. This embodiment of the application does not impose any limitations on this.

[0187] For rule one, a first threshold can be set, and the number of times the first paging message is received can be counted to determine the number of times the first paging message is received.

[0188] In some embodiments, the first threshold is predefined or configured by the second device.

[0189] When the first threshold is configured for the second device, the first threshold can be carried in the R2D message sent by the second device.

[0190] In some embodiments, receiving the first paging message more than the first threshold is used to determine to re-execute random access; receiving the first paging message is used to trigger the start or restart of the second timer.

[0191] The first paging message is associated with the second timer. Understandably, the listening for the first paging message is controlled by the second timer.

[0192] If the rule used to determine whether to re-execute random access includes rule one, a second timer can be set to listen for the first paging message.

[0193] Understandably, during the second timer's operation, the first paging message is listened for, and after the second timer expires, the first paging message is no longer listened for.

[0194] Here, the second timer can be used to determine whether the second device will send the first paging message. If the first paging message is not received when the second timer expires, it can be assumed that the second device will no longer send the first paging message, and the first device will no longer listen for the first paging message.

[0195] In some embodiments, receiving a first paging message is used to trigger the start or restart of a second timer.

[0196] Understandably, receiving the first paging message triggers the start of the second timer. Receiving the Nth paging message triggers the restart of the second timer, where N is greater than 1.

[0197] In this embodiment of the application, a first counter may be set, which is used to count the first paging messages.

[0198] In some embodiments, if the first paging message is not received before the second timer times out, the second timer stops running and the first counter is reset to zero; and / or,

[0199] If the first paging message is received before the second timer expires, the second timer restarts, and the value of the first counter is incremented by 1.

[0200] In this embodiment, upon receiving a first paging message, a second timer starts and the value of a first counter is incremented by 1. During the operation of the second timer, the system listens for first paging messages to determine if a new first paging message has been received. If another first paging message is received during the second timer's operation, the second timer restarts and the value of the first counter is incremented again. If no first paging message is received during the second timer's operation, the second timer stops running and the value of the first counter is reset to zero. If the second timer restarts, the system continues to check for new first paging messages during its operation until the first counter is reset to zero or its value exceeds a first threshold. If the first counter is reset to zero, the listening for first paging messages ends, and it is assumed that the number of first paging message receptions has not exceeded the first threshold. If the value of the first counter exceeds the first threshold, the first timer can be stopped and the first counter reset to zero, ending the listening for first paging messages.

[0201] In this embodiment of the application, the listening of the first paging message can be controlled by a second timer, and the number of times the first paging message is received can be counted by a first counter. Thus, the number of times the first paging message is received can be accurately counted by the cooperation of the second timer and the first paging message, and invalid listening of the first paging message can be avoided.

[0202] In some embodiments, the duration of the second timer is predefined, or the duration of the second timer is configured by the second device.

[0203] In some embodiments, the duration of the second timer may be greater than or equal to the sending period of the first paging message.

[0204] For Rule 2, the first information can be understood as an instruction or flag used to instruct the second device to re-perform random access.

[0205] If the first paging message received contains the first information, the first device may decide to perform a re-access or combine it with other rules to decide to perform a re-access.

[0206] In some embodiments, the first information triggers the first device to reconnect to the second device.

[0207] Understandably, the first information is used to indicate whether the first device should re-perform random access if it believes it has successfully accessed the second device.

[0208] The first information may have different values ​​and / or whether the first information is included in the first paging message indicates whether to re-execute random access.

[0209] In one example, if the first paging message includes the first information, it can be considered an instruction to re-execute random access. If the first paging message does not include the first information, it can be considered that no instruction to re-execute random access has been given.

[0210] In one example, if the first information included in the first paging message has a first value, it can be considered an instruction to re-execute random access. If the first information included in the first paging message has a second value, it can be considered that no instruction to re-execute random access has been given. The first value and the second value are different values. In one example, the first value is 1 and the second value is 0.

[0211] Whether the first paging message includes first information to determine whether to re-execute random access, thereby quickly determining whether to re-execute random access through the first information explicitly carried in the first paging message.

[0212] For rule three, there is a second timer, which is associated with the acknowledgment message. The second timer can be stopped when the acknowledgment message is received.

[0213] The second timer is used to listen for confirmation messages. During the operation of the second timer, if the first device anticipates that it may receive a confirmation message from the second device, the first device will listen for confirmation messages. After the second timer expires, if the first device anticipates that it will not receive a confirmation message from the second device, the first device will stop listening for confirmation messages.

[0214] Understandably, the first device may consider the first paging message received during the second timer operation as an invalid first paging message (at which time an acknowledgment message may be received), and thus ignore the first paging message. The first device may consider the first paging message received after the first timer expires as (at which time no acknowledgment message will be received), and thus determine whether to re-execute random access based on the first paging message.

[0215] In one example, if the first paging message is received after the first timer expires, it is determined that random access will be re-executed.

[0216] In some embodiments, the second timer is associated with NACK.

[0217] In one example, if the first paging message is received after the first timer expires, it is determined that random access will be re-executed.

[0218] In one example, if the first paging message is not received after the first timer expires, it is determined that random access will not be re-executed.

[0219] In some embodiments, the first timer start time is a first time, which is the time when the first device sends the first D2R message.

[0220] When the first device sends a first D2R message to the second device, it starts a first timer. During the first timer period, if an acknowledgment message is received, the first timer stops running. The acknowledgment message is a response message to the first D2R message.

[0221] In some embodiments, the acknowledgment message includes ACK and / or NACK.

[0222] If the first device receives an acknowledgment message during the first timer's operation, it can confirm whether the first message transmission was successful or failed. If the first device does not receive an acknowledgment message during the first timer's operation, it cannot confirm whether the first message transmission was successful or failed. In this case, it can determine whether to re-execute random access based on the first paging message received after the timer expires.

[0223] In this embodiment of the application, the start time of the first timer can be any time other than the first time, and this embodiment of the application does not impose any restrictions on this.

[0224] In some embodiments, the duration of the first timer is predefined, or the duration of the first timer is configured by the second device.

[0225] In some embodiments, the duration of the first timer is related to the acknowledgment message.

[0226] In some embodiments, the duration of the first timer is greater than the duration of the second timer.

[0227] In this embodiment, a second timer is introduced to limit the first device's behavior regarding whether to perform a re-access. Specifically, the decision to re-execute random access is determined by the first paging message received after the first timer expires, avoiding errors in determining whether to re-execute random access based on a first paging message received before the acknowledgment message.

[0228] For rule four, the first device determines whether to re-execute random access based on the first paging message containing the second identifier.

[0229] The first paging message includes a second identifier, indicating that the second device believes the first device needs to re-execute random access. The first paging message does not include the second identifier, indicating that the second device does not believe the first device needs to re-execute random access.

[0230] In some embodiments, the second identifier is an identifier associated with the first device.

[0231] Here, the first paging message does not include any second identifier corresponding to the first device, which can be understood as the second device believing that no device needs to re-perform random access. If the second device believes that a device needs to re-perform random access, it will carry the second identifier corresponding to that device in the first paging message.

[0232] The second identifier corresponding to the first device can identify the first device.

[0233] In one example, if the first device receives a first paging message that includes a second identifier corresponding to the first device, it considers the device to be a device that the second device deems necessary to re-perform random access, and can determine whether to re-perform random access based on the first paging message. If the first device receives a first paging message that does not include the second identifier corresponding to the first device, it considers the device not to be a device that the second device deems necessary to re-perform random access, and then determines whether not to re-perform random access based on the first paging message.

[0234] In one example, if the first device receives a first paging message that includes the second identifier corresponding to the first device, then the first device considers it to be a device that the second device believes needs to re-perform random access, and it can be determined to re-perform random access; if the first device receives a first paging message that does not include the second identifier corresponding to the first device, then the first device considers it not to be a device that the second device believes needs to re-perform random access, and it can be determined not to re-perform random access.

[0235] In this embodiment of the application, the device to be accessed is indicated by the second identifier in the first paging message.

[0236] Understandably, if the first paging message may include a second identifier corresponding to each of the one or more devices, it instructs the one or more second devices to re-perform random access.

[0237] In some embodiments, the second identifier includes one or more of the following: an access layer identifier; a device identifier of the first device; and a temporary identifier for encryption.

[0238] In some embodiments, the access stratum identifier may include: Access Stratum (AS) ID.

[0239] In some embodiments, the device identifier of the first device may include: the device ID of the first device.

[0240] In some embodiments, the temporary identifier used for encryption may include: a temporary ID used for encryption.

[0241] In this embodiment of the application, a second identifier is used to indicate the device that needs to re-perform random access, so that when multiple devices receive the first paging message, it is possible to clearly and effectively identify whether they need to re-perform random access.

[0242] In some embodiments, for the first device, the method further includes:

[0243] The first device sends a first D2R message to the second device;

[0244] In this case, the first device did not receive an acknowledgment message in response to the first D2R message.

[0245] In some embodiments, for the second device, the method further includes:

[0246] The second device did not receive the first D2R message sent by the first device.

[0247] In some embodiments, for the second device, the method further includes:

[0248] The first device sends a first D2R message to the second device;

[0249] The first device did not receive an acknowledgment message in response to the first D2R message.

[0250] As shown in Figure 9, the first device sends a first D2R message to the second device. The second device does not receive the first D2R message, meaning the transmission of the first D2R message fails. In this case, the second device sends a first paging message to the first device, and the first device determines whether to re-execute random access based on the received first paging message.

[0251] In this scenario, the first device sends a first D2R message to the second device. The second device does not receive the first D2R message. At this point, the first device and the second device have different perceptions of the sending of the first D2R message. If the second device does not receive the first D2R message within the first time period, it may send a first paging message to the first device. The first device determines whether to re-execute random access based on the received first paging message, so that the first device and the second device reach a consensus in their perception.

[0252] Here, as shown in Figure 10, the second device receives the first D2R message sent by the first device. The second device sends an acknowledgment message to the first device in response to the first D2R message, but the first device does not receive the acknowledgment message and is unsure whether it has successfully received the first D2R message, that is, the transmission of the first D2R message fails. When the first terminal device receives the first paging message, it determines whether to re-execute random access based on the received first paging message, so that the first device and the second device reach a consensus in their understanding.

[0253] Here, when the first device and the second device have different understandings of the transmission of the first D2R message, the second device instructs the first device to re-execute random access based on the first paging message, and the first device determines whether to re-execute random access based on the received first paging message, so that the first device and the second device reach a consensus in their understanding and improve communication reliability.

[0254] In some embodiments, the first D2R message includes one or more of the following:

[0255] Message 3;

[0256] The first message is a D2R message transmitted after message 3. The first device repeatedly transmits the first message to the second device.

[0257] In this embodiment of the application, if the first D2R message is not successfully transmitted, it can be assumed that the first device has successfully accessed the second device based on the random access procedure when executing the random procedure. However, in reality, the first device has successfully accessed the second device based on the random access procedure.

[0258] In this embodiment of the application, when the first D2R message is the first message, the first device sends the first message after successfully connecting to the second device. The second device determines that the first device has not successfully connected to the second device based on the sending of the first message, but the first device still believes that it has successfully connected to the second device.

[0259] In some embodiments, the first message is used for data transmission of the first device.

[0260] In some embodiments, rules one through three apply to scenarios where the transmission of message 3 and the first message fails.

[0261] In some embodiments, rule four applies to scenarios where the transmission of the first message fails.

[0262] The communication method provided in the embodiments of this application will be described in detail below with reference to specific application scenarios.

[0263] In this embodiment, this problem is solved by utilizing subsequent A-IoT paging messages received. In particular, if the A-IoT paging message is sent multiple times, or if the A-IoT device-related ID is included in subsequent A-IoT paging messages, it is likely that the reader is attempting to trigger the A-IoT device to reconnect to the network.

[0264] In this embodiment of the application, if the reader sends subsequent A-IOT paging messages multiple times, the A-IOT device should interpret this as possibly having missed the NACK message.

[0265] The wireless communication method provided in this application can be implemented as including, but not limited to, the following embodiments one to four.

[0266] Example 1

[0267] The reader can configure a threshold, i.e., the first threshold, in the R2D message sent to the A-IOT device, corresponding to the number of subsequent A-IOT paging messages, or the threshold can be defined in the specification.

[0268] As shown in Figure 11, it includes:

[0269] S1101, the reader configures thresholds for the A-IOT device.

[0270] Here, the threshold configured for the reader is 2.

[0271] S1102, the A-IOT device sends a D2R message (e.g., Msg3) to the reader.

[0272] There is a situation where the reader fails to receive the D2R message, in which case the D2R message is not transmitted successfully.

[0273] S1103, the reader returns an acknowledgment message to the A-IOT device.

[0274] If the reader receives a D2R message, it returns an ACK to the A-IoT device; if the reader does not receive a D2R message, it returns a NACK to the A-IoT device.

[0275] Here, there are cases where the A-IOT device fails to receive the NACK message.

[0276] S1104 and A-IOT devices consider the D2R message transmission to be successful.

[0277] If an A-IoT device fails to receive a NACK message during the timer's operation, it considers the D2R message transmission to be successful.

[0278] S1105, the reader sends a follow-up paging message to the A-IOT device.

[0279] S1106 and A-IOT devices do not perform reconnection.

[0280] If an A-IoT device receives a subsequent paging message once, and the number of subsequent paging messages received does not exceed the threshold of 2, then it will not perform a reconnection.

[0281] S1107, the reader sends a follow-up paging message to the A-IOT device.

[0282] S1108 and A-IOT devices do not perform reconnection.

[0283] If an A-IoT device receives two subsequent paging messages, and the number of subsequent paging messages received does not exceed the threshold of 2, then it will not perform a reconnection.

[0284] S1109, the reader sends a follow-up paging message to the A-IOT device.

[0285] The S1110 and A-IOT devices are determined to reconnect.

[0286] If an A-IoT device receives three subsequent paging messages, and the number of subsequent paging messages received exceeds a threshold of 2, then it will determine to perform a reconnection.

[0287] It should be noted that S1101 can be omitted in Figure 11 when the threshold is predefined.

[0288] Initially, if the A-IoT device receives a new follow-up paging message, the relevant counter, i.e., the first counter, will increment by 1. Simultaneously, a timer will be triggered. If no follow-up paging message is received before the timer expires, the A-IoT device will stop the timer and set the counter to zero. If a follow-up paging message is received before the timer expires, the A-IoT device will increment the counter by 1. Simultaneously, the timer will be reinitialized. If the counter exceeds a certain threshold, the A-IoT device will decide to perform a reconnection.

[0289] After an A-IoT device successfully connects, if the number of subsequent A-IoT paging messages with the same transaction ID as the previous paging message received by the A-IoT device exceeds the threshold (configured threshold or defined in the specification), the A-IoT device that has not received a NACK message from the reader must perform a reconnection process.

[0290] In this embodiment of the application, based on whether the number of subsequent paging messages received exceeds a threshold to determine whether to perform re-access, as shown in Figure 11, a timer (i.e., a second timer) can be introduced.

[0291] Example 2

[0292] An A-IoT paging message with the same transaction ID as the initial paging message may contain a flag, which is the first piece of information. When this flag is received, the A-IoT device can decide to reconnect to the reader.

[0293] As shown in Figure 12, it includes:

[0294] S1201, A-IOT devices send D2R messages (e.g., Msg3) to the reader.

[0295] There is a situation where the reader fails to receive the D2R message, in which case the D2R message is not transmitted successfully.

[0296] S1202, the reader returns an acknowledgment message to the A-IOT device.

[0297] If the reader receives a D2R message, it returns an ACK to the A-IoT device; if the reader does not receive a D2R message, it returns a NACK to the A-IoT device.

[0298] The S1203 and A-IOT devices consider the D2R message transmission to be successful.

[0299] If an A-IoT device fails to receive a NACK message during the timer's operation, it considers the D2R message transmission to be successful.

[0300] S1204, the reader sends a follow-up paging message to the A-IoT device. This follow-up paging message does not carry any flags.

[0301] S1205 and A-IOT devices do not perform reconnection.

[0302] S1206, the reader sends a follow-up paging message to the A-IOT device, and the value of the flag carried in the follow-up paging message is 0.

[0303] S1207 and A-IOT devices do not perform reconnection.

[0304] S1208, the reader sends a follow-up paging message to the A-IOT device, and the value of the flag carried in the follow-up paging message is 1.

[0305] S1209, A-IOT devices are determined to perform reconnection.

[0306] The function of the flag is to trigger A-IOT devices that believe they have successfully completed the access task (but may have missed NACK) to perform a re-access.

[0307] Example 3

[0308] A timer (second timer) is introduced to limit the A-IoT device's behavior regarding whether it should perform a re-access operation. If the timer expires, but the reader still sends a subsequent paging message with the same transaction ID as the previous paging message, then the A-IoT device should perform a re-access operation to the network.

[0309] In some embodiments, the introduced timer can be considered as a timer that takes NACK into account.

[0310] As shown in Figure 13, it includes:

[0311] S1301, the reader configures the timer duration for the A-IOT device.

[0312] S1302, the A-IOT device sends a D2R message (e.g., Msg3) to the reader.

[0313] There is a situation where the reader fails to receive the D2R message, in which case the D2R message is not transmitted successfully.

[0314] The sending of a D2R message triggers the start of a timer.

[0315] S1303, the reader returns an acknowledgment message to the A-IOT device.

[0316] If the reader receives a D2R message, it returns an ACK to the A-IoT device; if the reader does not receive a D2R message, it returns a NACK to the A-IoT device.

[0317] Here, there are cases where the A-IOT device fails to receive the NACK message.

[0318] S1304 and A-IOT devices consider D2R message transmission to be successful.

[0319] If an A-IoT device fails to receive a NACK message during the timer's operation, it considers the D2R message transmission to be successful.

[0320] S1305, the reader sends a follow-up paging message to the A-IOT device.

[0321] S1306 and A-IOT devices do not perform reconnection.

[0322] If an A-IoT device receives a subsequent paging message during the timer's operation, it will not reconnect.

[0323] S1307, the reader sends a follow-up paging message to the A-IOT device.

[0324] S1308 and A-IOT devices do not perform reconnection.

[0325] If an A-IoT device receives a subsequent paging message during the timer's operation, it will not reconnect.

[0326] S1309, the reader sends a follow-up paging message to the A-IOT device.

[0327] The subsequent paging message was received after the timer expired.

[0328] The S1310 and A-IOT devices are determined to reconnect.

[0329] If an A-IoT device receives a subsequent paging message after the timer expires, it will determine to reconnect.

[0330] The runtime of this timer should be set by the reader or defined in the specification. Furthermore, the start time of this timer should be the time when the A-IoT device sends a D2R message.

[0331] It should be noted that S1301 can be omitted in Figure 13 if the timer duration is predefined.

[0332] Example 4

[0333] In cases where subsequent D2R message transmissions (excluding msg3) fail, the reader already knows the A-IoT device's associated ID (AS ID, A-IoT device ID, or a temporary ID for security reasons). In this situation, the reader can include the A-IoT device's associated ID in a subsequent paging message with the same transaction ID as the previous paging message. In this case, the A-IoT device has already heard the paging message and should reconnect to the reader.

[0334] As shown in Figure 14, it includes:

[0335] S1401, the A-IOT device sends a D2R message to the reader (e.g., a D2R message after Msg3).

[0336] There is a situation where the reader fails to receive the D2R message, in which case the D2R message is not transmitted successfully.

[0337] S1402, the reader returns an acknowledgment message to the A-IOT device.

[0338] If the reader receives a D2R message, it returns an ACK to the A-IoT device; if the reader does not receive a D2R message, it returns a NACK to the A-IoT device.

[0339] The S1403 and A-IOT devices consider the D2R message transmission to be successful.

[0340] If an A-IoT device fails to receive a NACK message during the timer's operation, it considers the D2R message transmission to be successful.

[0341] S1404, the reader sends a follow-up paging message to the A-IoT device, which carries the A-IoT device ID.

[0342] S1405, A-IOT device determines to perform reconnection.

[0343] It should be noted that Examples 1 to 3 can be applied to cases where MSG3 and subsequent D2R transmissions fail, while Example 4 is only applicable to cases where subsequent D2R transmissions fail.

[0344] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0345] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0346] Based on the foregoing embodiments, this application provides corresponding communication devices.

[0347] Figure 15 is a schematic diagram of the structure of the first device provided in an embodiment of this application. As shown in Figure 15, the first device 1500 includes:

[0348] The first communication unit 1501 is configured to receive a first paging message sent by the second device, the first paging message being used to determine whether to re-execute random access;

[0349] The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

[0350] In some embodiments, the first paging message and the second paging message include the same first identifier, which indicates a first service, the first service being the service associated with the first paging message and the second paging message.

[0351] In some embodiments, the first identifier is the transaction identifier associated with the first service.

[0352] In some embodiments, one or more of the following are used to determine the re-execution of random access:

[0353] The number of times the first paging message has been received is greater than the first threshold;

[0354] The first paging message includes first information, which is used to indicate reconnection;

[0355] The first paging message is received if the first timer times out;

[0356] The first paging message includes a second identifier.

[0357] In some embodiments, the first threshold is predefined, or the first threshold is configured by the second device.

[0358] In some embodiments, the number of times the first paging message is received exceeds the first threshold to determine whether to re-execute random access;

[0359] The receipt of the first paging message is used to trigger the start or restart of the second timer.

[0360] In some embodiments, if the first paging message is not received before the second timer times out, the second timer stops running and the first counter is reset to zero; and / or,

[0361] If the first paging message is received before the second timer expires, the second timer restarts, and the value of the first counter is incremented by 1.

[0362] In some embodiments, the duration of the second timer is predefined, or the duration of the second timer is configured by the second device.

[0363] In some embodiments, the first information triggers the first device to reconnect to the second device.

[0364] In some embodiments, the start time of the first timer is a first time, which is the time when the first device sends the first D2R message.

[0365] In some embodiments, the duration of the first timer is predefined, or the duration of the first timer is configured by the second device.

[0366] In some embodiments, the second identifier is an identifier associated with the first device.

[0367] In some embodiments, the second identifier includes one or more of the following:

[0368] Access layer identifier;

[0369] The device identifier of the first device;

[0370] Temporary identifiers used for encryption.

[0371] In some embodiments, the first communication unit 1501 is further configured to send a first D2R message to the second device;

[0372] The first device did not receive an acknowledgment message in response to the first D2R message.

[0373] In some embodiments, the first D2R message includes one or more of the following:

[0374] Message 3;

[0375] The first message is a D2R message transmitted after message 3.

[0376] The first communication unit in the first device can be implemented by the transceiver in the first device.

[0377] Figure 16 is a schematic diagram of the structure of the second device provided in an embodiment of this application. As shown in Figure 16, the second device 1600 includes:

[0378] The second communication unit 1601 is configured to send a first paging message to the first device, the first paging message being used to determine whether to re-execute random access;

[0379] The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

[0380] In some embodiments, the first paging message and the second paging message include the same first identifier, which indicates a first service, the first service being the service associated with the first paging message and the second paging message.

[0381] In some embodiments, the first identifier is the transaction identifier associated with the first service.

[0382] In some embodiments, one or more of the following are used to determine the re-execution of random access:

[0383] The number of times the first paging message has been received is greater than the first threshold;

[0384] The first paging message includes first information, which is used to indicate reconnection;

[0385] The first paging message is received if the first timer times out;

[0386] The first paging message includes a second identifier.

[0387] In some embodiments, the first threshold is predefined, or the first threshold is configured by the second device.

[0388] In some embodiments, the number of times the first paging message is received exceeds the first threshold to determine whether to re-execute random access;

[0389] The receipt of the first paging message is used to trigger the start or restart of the second timer.

[0390] In some embodiments, if the first paging message is not received before the second timer times out, the second timer stops running and the first counter is reset to zero; and / or,

[0391] If the first paging message is received before the second timer expires, the second timer restarts, and the value of the first counter is incremented by 1.

[0392] In some embodiments, the duration of the second timer is predefined, or the duration of the second timer is configured by the second device.

[0393] In some embodiments, the first information triggers the first device to reconnect to the second device.

[0394] In some embodiments, the start time of the first timer is a first time, which is the time when the first device sends the first D2R message.

[0395] In some embodiments, the duration of the first timer is predefined, or the duration of the first timer is configured by the second device.

[0396] In some embodiments, the second identifier is an identifier associated with the first device.

[0397] In some embodiments, the second identifier includes one or more of the following:

[0398] Access layer identifier;

[0399] The device identifier of the first device;

[0400] Temporary identifiers used for encryption.

[0401] In some embodiments, the second communication unit 1601 is further configured to not receive the first D2R message sent by the first device.

[0402] In some embodiments, the second communication unit 1601 is further configured to receive a first D2R message sent by the first device;

[0403] The second communication unit 1601 is further configured to send an acknowledgment message to the first device in response to the first D2R message.

[0404] In some embodiments, the first D2R message includes one or more of the following:

[0405] Message 3;

[0406] The first message is a D2R message transmitted after message 3. The first device repeatedly transmits the first message to the second device.

[0407] The second communication unit in the second device can be implemented by the transceiver in the second device.

[0408] Those skilled in the art should understand that the description of the communication device in the embodiments of this application can be understood with reference to the description of the communication method in the embodiments of this application.

[0409] Figure 17 is a schematic structural diagram of a communication device provided in an embodiment of this application. The communication device can be a first device or a second device. The communication device 1700 shown in Figure 17 includes a processor 1710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0410] Optionally, as shown in FIG17, the communication device 1700 may further include a memory 1720. The processor 1710 may retrieve and run computer programs from the memory 1720 to implement the methods described in the embodiments of this application.

[0411] The memory 1720 can be a separate device independent of the processor 1710, or it can be integrated into the processor 1710.

[0412] Optionally, as shown in FIG17, the communication device 1700 may further include a transceiver 1730, and the processor 1710 may control the transceiver 1730 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0413] The transceiver 1730 may include a transmitter and a receiver. The transceiver 1730 may further include an antenna, and the number of antennas may be one or more.

[0414] Optionally, the communication device 1700 may specifically be the first device in the embodiments of this application, and the communication device 1700 may implement the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0415] Optionally, the communication device 1700 may specifically be the second device in the embodiments of this application, and the communication device 1700 may implement the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0416] Figure 18 is a schematic structural diagram of a chip according to an embodiment of this application. The chip 1800 shown in Figure 18 includes a processor 1810, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0417] Optionally, as shown in FIG18, chip 1800 may further include memory 1820. Processor 1810 can call and run computer programs from memory 1820 to implement the methods in the embodiments of this application.

[0418] The memory 1820 can be a separate device independent of the processor 1810, or it can be integrated into the processor 1810.

[0419] Optionally, the chip 1800 may also include an input interface 1830. The processor 1810 can control the input interface 1830 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0420] Optionally, the chip 1800 may also include an output interface 1840. The processor 1810 can control the output interface 1840 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0421] Optionally, the chip can be applied to the first device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0422] Optionally, the chip can be applied to the second device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0423] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0424] This application also provides a computer storage medium that stores one or more programs, which can be executed by one or more processors to implement the methods in this application.

[0425] Figure 19 is a schematic block diagram of a communication system provided in an embodiment of this application. As shown in Figure 19, the communication system 1900 includes a first device 1910 and a second device 1920.

[0426] The first device 1910 can be used to implement the corresponding functions implemented by the first device in the above method, and the second node 1920 can be used to implement the corresponding functions implemented by the second device in the above method. For the sake of brevity, it will not be described in detail here.

[0427] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0428] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0429] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0430] This application also provides a computer-readable storage medium for storing computer programs.

[0431] Optionally, the computer-readable storage medium can be applied to the first device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0432] Optionally, the computer-readable storage medium can be applied to the second device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0433] This application also provides a computer program product, including computer program instructions.

[0434] Optionally, the computer program product can be applied to the first device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0435] Optionally, the computer program product can be applied to the second device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0436] This application also provides a computer program.

[0437] Optionally, the computer program can be applied to the first device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the first device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0438] Optionally, the computer program can be applied to the second device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the second device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0439] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0440] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0441] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0442] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0443] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0444] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0445] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A wireless communication method, the method comprising: The first device receives a first paging message sent by the second device, the first paging message being used to determine whether to re-execute random access; The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

2. The method according to claim 1, wherein, The first paging message and the second paging message include the same first identifier, which is used to indicate a first service, and the first service is the service associated with the first paging message and the second paging message.

3. The method according to claim 2, wherein, The first identifier is the transaction identifier associated with the first service.

4. The method according to any one of claims 1 to 3, wherein, One or more of the following are used to determine whether to re-execute random access: The number of times the first paging message has been received is greater than the first threshold; The first paging message includes first information, which is used to indicate reconnection; The first paging message is received if the first timer times out; The first paging message includes a second identifier.

5. The method according to claim 4, wherein, The first threshold is predefined, or the first threshold is configured by the second device.

6. The method according to claim 4 or 5, wherein, If the number of times the first paging message is received exceeds the first threshold, it is used to determine whether to re-execute random access; The receipt of the first paging message is used to trigger the start or restart of the second timer.

7. The method according to claim 6, wherein, If the first paging message is not received before the second timer expires, the second timer stops running and the first counter is reset to zero; and / or, If the first paging message is received before the second timer expires, the second timer restarts, and the value of the first counter is incremented by 1.

8. The method according to claim 6 or 7, wherein, The duration of the second timer is predefined, or the duration of the second timer is configured by the second device.

9. The method according to any one of claims 4 to 8, wherein, The first information triggers the first device to reconnect to the second device.

10. The method according to any one of claims 4 to 9, wherein, The start time of the first timer is the first time, which is the time when the first device sends the first D2R message.

11. The method according to any one of claims 4 to 10, wherein, The duration of the first timer is predefined, or the duration of the first timer is configured by the second device.

12. The method according to any one of claims 4 to 11, wherein, The second identifier is an identifier related to the first device.

13. The method according to claim 12, wherein, The second identifier includes one or more of the following: Access layer identifier; The device identifier of the first device; Temporary identifiers used for encryption.

14. The method according to any one of claims 1 to 13, wherein, The method further includes: The first device sends a first D2R message to the second device; The first device did not receive an acknowledgment message in response to the first D2R message.

15. The method according to claim 14, wherein, The first D2R message includes one or more of the following: Message 3; The first message is a D2R message transmitted after message 3.

16. A wireless communication method, the method comprising: The second device sends a first paging message to the first device, the first paging message being used to determine whether to re-execute random access; The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

17. The method according to claim 16, wherein, The first paging message and the second paging message include the same first identifier, which is used to indicate a first service, and the first service is the service associated with the first paging message and the second paging message.

18. The method according to claim 17, wherein, The first identifier is the transaction identifier associated with the first service.

19. The method according to any one of claims 16 to 18, wherein, One or more of the following are used to determine whether to re-execute random access: The number of times the first paging message has been received is greater than the first threshold; The first paging message includes first information, which is used to indicate reconnection; The first paging message is received if the first timer times out; The first paging message includes a second identifier.

20. The method according to claim 19, wherein, The first threshold is predefined, or the first threshold is configured by the second device.

21. The method according to claim 19 or 20, wherein, If the number of times the first paging message is received exceeds the first threshold, it is used to determine whether to re-execute random access; The receipt of the first paging message is used to trigger the start or restart of the second timer.

22. The method according to claim 21, wherein, If the first paging message is not received before the second timer expires, the second timer stops running, and the first counter is reset to zero; and / or, If the first paging message is received before the second timer expires, the second timer restarts, and the value of the first counter is incremented by 1.

23. The method according to claim 21 or 22, wherein, The duration of the second timer is predefined, or the duration of the second timer is configured by the second device.

24. The method according to any one of claims 19 to 23, wherein, The first information triggers the first device to reconnect to the second device.

25. The method according to any one of claims 19 to 24, wherein, The start time of the first timer is the first time, which is the time when the first device sends the first D2R message.

26. The method according to any one of claims 19 to 25, wherein, The duration of the first timer is predefined, or the duration of the first timer is configured by the second device.

27. The method according to any one of claims 19 to 26, wherein, The second identifier is an identifier related to the first device.

28. The method according to claim 27, wherein, The second identifier includes one or more of the following: Access layer identifier; The device identifier of the first device; Temporary identifiers used for encryption.

29. The method according to any one of claims 16 to 28, wherein, The method further includes: The second device did not receive the first D2R message sent by the first device.

30. The method according to any one of claims 16 to 28, wherein, The method further includes: The second device receives the first D2R message sent by the first device; The second device sends an acknowledgment message to the first device in response to the first D2R message.

31. The method according to claim 29 or 30, wherein, The first D2R message includes one or more of the following: Message 3; The first message is a D2R message transmitted after message 3. The first device repeatedly transmits the first message to the second device.

32. A first device, the first device comprising: The first communication unit is configured to receive a first paging message sent by the second device (reader), the first paging message being used to determine whether to re-execute random access; The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

33. A second device, the second device comprising: The second communication unit is configured to send a first paging message to the first device, wherein the first paging message is used to determine whether to re-execute random access; The first paging message and the second paging message are associated with the same service; the second paging message has triggered the access process for the first device to access the second device.

34. A communication device, the communication device comprising: Memory, used to store computer programs; A processor, connected to the memory, is configured to invoke and run a computer program stored in the memory to perform the method as described in any one of claims 1 to 15, or to perform the method as described in any one of claims 16 to 31.

35. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as claimed in any one of claims 1 to 15, or the method as claimed in any one of claims 16 to 31.

36. A computer-readable storage medium for storing a computer program, the execution of which causes a computer to perform the method as claimed in any one of claims 1 to 15, or the method as claimed in any one of claims 16 to 31.

37. A computer program product comprising computer program instructions, the execution of which causes a computer to perform the method as claimed in any one of claims 1 to 15, or to perform the method as claimed in any one of claims 16 to 31.

38. A computer program, the execution of which causes a computer to perform the method as claimed in any one of claims 1 to 15, or the method as claimed in any one of claims 16 to 31.

Images