Communication method, device and system

Abstract

The embodiment of the invention provides a communication method, device and system, and relates to the technical field of communication. According to the method, a repeated paging mechanism between the card reading equipment and the AIoT equipment can be provided, so that the AIoT equipment can try to carry out random access with the card reading equipment again through repeated paging. The solution may include sending a first message for a second device to initiate a random access to the first device. And sending a second message, wherein the second message is used by the second device to initiate random access to the first device. The first message and the second message are associated with a first request, and the first request indicates the first device to perform environmental Internet of Things AIoT communication with the second device.

Description

Technical Field

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

[0002] Currently, in the communication process based on the Environmental Internet of Things (AIoT), card readers can page one or more AIoT devices using paging messages. Correspondingly, AIoT devices can attempt random access to the card reader based on the paging message in order to establish an AIoT communication connection between the devices.

[0003] In some cases, AIoT devices may experience random connection failures. This can prevent the AIoT device from transmitting data normally with the card reader. Summary of the Invention

[0004] This application provides a communication method, device, and system, which provides a repeated paging mechanism between a card reader and an AIoT device, so that the AIoT device can attempt to randomly access the card reader again through repeated paging.

[0005] To achieve the above technical objectives, this application adopts the following technical solution:

[0006] In a first aspect, a communication method is provided, applied to a first device, the method comprising: sending a first message for a second device to initiate random access to the first device; sending a second message for the second device to initiate random access to the first device; and associating the first message and the second message with a first request, the first request instructing the first device to perform AIoT (Artificial Intelligence of Things) communication with the second device.

[0007] For example, the first message may include a paging message or an initial message. The second message may be a repaging message. The first device may be a card reader. For example, the card reader may be a user equipment (UE) or a base station.

[0008] In some implementations of this example, the first message and / or the second message can be the message that triggers random access. In other implementations, the first message and / or the second message itself can have content different from directly triggering random access. Correspondingly, the second device can determine whether to trigger random access based on the first message and / or the second message.

[0009] For example, the second device can determine whether to initiate random access based on the first message and / or the device identification information of the second device (such as the card reader device ID indicating the first device carried in the first message and / or the second message), or the process identification information (such as the process ID) carried in the first message and / or the second message.

[0010] Based on this scheme, the first device can instruct a second device (such as an AIoT device) to initiate random access via a first message. Correspondingly, some second devices can successfully establish an AIoT communication connection with the first device through this random access based on the first message. Other second devices may not access the device during the paging process corresponding to the first message (e.g., not receiving the first message) or may not have completed access (e.g., receiving the first message and attempting random access, but failing). In this case, the first device can instruct itself to initiate random access again via a second message. Thus, second devices that did not establish an AIoT connection with the card reader during the paging process can re-initiate random access to the first device based on the second message. In this way, through the configuration of the second devices, opportunities are provided for second devices that did not access the device or did not complete access during the paging process to re-initiate random access, thereby increasing the likelihood of the second device successfully establishing an AIoT communication connection with the first device.

[0011] In some possible designs, the method further includes receiving a first request carrying a first process ID. Exemplarily, the first request may be a CN request from a core network device. In some embodiments, the first request may include inventory instructions and / or downlink commands (DL commands). The first process ID may be the CNrequest ID of the CN request.

[0012] In some possible designs, the first message and / or the second message includes at least one of the following: shared resource and / or dedicated resource information, resource allocation type, downlink command indication information, second process ID, information indicating whether to receive or ignore a paging message, identification information of the first device, information indicating that a device with failed access will receive a paging message, type information of the second device, and information indicating whether a duplicate message exists. The second process ID corresponds to the first request.

[0013] In this application, the second process ID sent by the second device can be the same as the first process ID. Alternatively, the second process ID can be mapped to the first process ID, thereby allowing the identification of different Paging (or Repaging) messages associated with the same CN request through the second process ID.

[0014] In a specific implementation of this application, "not connected" may include having received the first message but not initiating access in the corresponding process (such as the Paging process) due to reasons such as battery power. For example, if the first message includes information indicating the existence of duplicate messages, the second device, upon receiving the first message and with sufficient battery power, can wait for the second message instead of entering sleep mode. This allows the second device to perform Repaging based on the second message. Alternatively, if the second device's battery is low, it can actively or passively charge, or enter sleep mode and wake up before the second message arrives, so as to receive the second message and perform Repaging.

[0015] In some possible designs, the first message and / or the second message are configured with a first flag bit, which is used to indicate whether the message carrying the first flag bit is an initial message or a repeat message.

[0016] In this application, the initial message may include the first message corresponding to the first request sent by the first device after receiving the first request message (such as a CN request). For example, the initial message may include a Paging message.

[0017] Correspondingly, a duplicate message may include a message corresponding to the first request sent a second time or a subsequent time after the first device receives the first request message (such as a CN request). For example, the duplicate message may include a Repaging message.

[0018] In some possible designs, the first flag bit of the first message indicates that the first message is the initial message. The first flag bit of the second message indicates that the second message is a duplicate message.

[0019] For example, the first flag bit of the first message is configured to a first value, which indicates that the first message is an initial message. The first flag bit of the second message is configured to a second value, which indicates that the second message is a duplicate message.

[0020] In some other possible designs, the first message can also be a repeating message.

[0021] Therefore, by setting a flag, it is possible to distinguish between initial messages and duplicate messages.

[0022] In some possible designs, the first message is of type one, and the second message is of type two. The first type corresponds to the initial message, and the second type corresponds to the repeating message.

[0023] Therefore, by configuring the initial message and the repeating message as different types, the initial message and the repeating message can be distinguished.

[0024] In some possible designs, both the first message and the second message are configured with identification information, wherein the identification information of the first message indicates that the first message is of the first type, and the identification information of the second message indicates that the second message is of the second type.

[0025] Therefore, by configuring the corresponding information in the identification information, the indication of initial messages and repeating messages can be achieved.

[0026] In some possible designs, the first message's data packet header or control information includes the second process ID, the first flag bit of the first message, or the identification information of the first message. And / or, the second message's data packet header or control information includes the second process ID, the first flag bit of the second message, or the identification information of the second message.

[0027] In this way, by configuring the second process ID and / or identification information and / or flag bits in the subheader or control information, the second device can know whether the currently received message is an initial message or a duplicate message without parsing the data part, and can also know whether the process ID corresponding to the message has been received.

[0028] Understandably, if the second process ID has been received, and the identification information and flags indicate that the message is a duplicate, then the second device can determine whether to respond to the duplicate message. If the second process ID has not been received, or the identification information and flags indicate that the message is an initial message, then the second device can respond directly to the message without additional judgment. Through this mechanism, the first device can configure the second process ID, identification information, and flags according to actual needs, thereby controlling the second device to respond accordingly.

[0029] The following are examples of the content of several different second messages.

[0030] In some possible designs, the second message includes a device ID or group ID corresponding to at least one device that has not accessed or has not completed access; alternatively, the second message includes resource information indicating unaccessed or uncompleted access, which indicates conflicting resource information and / or resource information where a response failed to be received and / or resource information for which no response was received. This resource information includes at least one of the following: round information, time-domain information, frequency-domain information, and Q-value.

[0031] Among these, round information indicates the round in which a response is initiated. Time-domain information indicates the time slot in which the response is initiated. Frequency-domain information indicates the frequency, frequency point, channel, etc., in which the response is initiated. The Q value can be used to determine the time-domain information, frequency-domain information, and / or round information.

[0032] In some possible designs, the second message includes a device ID or group ID corresponding to at least one device that has completed access; alternatively, the second message includes resource information indicating that access has been completed, which indicates that a response resource information has been received. This resource information includes at least one of the following: round information, time-domain information, frequency-domain information, and Q-value.

[0033] Based on this example, the first device can control the second device to determine whether to respond to a duplicate message based on the device ID or group ID via the second message. Alternatively, the first device can control the second device to determine whether to respond to a duplicate message based on resource information.

[0034] In some possible designs, after sending the first message, the method further includes: sending the second message within a first duration; or sending the second message after the first duration. The first duration is a preset duration, and / or the first duration is the duration from the start to the end of the first time slot. For example, the first duration can be the length of a time slot. This allows the first device to initiate a repaging process between time slots. In some implementations, the second device can begin charging after receiving the first message. The charging duration of the second device is related to the timing of the first device sending the second message. For example, if the first device sends the second message within the first duration, the charging duration of the second device is less than the first duration. Alternatively, if the first device sends the second message after the first duration, the charging duration of the second device can be greater than or equal to the first duration.

[0035] In some possible designs, after sending the first message, the method further includes sending a first time slot start message, which is used to indicate the start of the first time slot.

[0036] In some possible designs, after sending the first message, the method further includes sending a second time slot start message, which is used to indicate the end of the first time slot.

[0037] In some possible designs, this first message is used to indicate the start of a new round. In this example, the first device may not need to send a separate round start message; it can indicate the start of a new round via a first message (such as a paging message).

[0038] In some possible designs, after sending the first message, the method further includes sending a third message to indicate the start of a new round. This third message may include the first message, or it may include the second message. In this example, the first device can indicate the start of a new round by sending the third message. In different implementations, the third message may be the paging message corresponding to the first message. That is, within the same CN request process, the first device can send multiple paging messages to indicate the start of a new round for the second device. Alternatively, the third message may be the repaging message corresponding to the second message. When the third message is a repaging message, the first device can trigger the repaging process within a paging process, at the end of a round and / or the start of a new round.

[0039] In some possible designs, after sending the first message, the method further includes sending a first round start message to indicate the start of a first round. In this example, the first device can indicate the start of a new round by sending a round start message.

[0040] In some possible designs, sending the second message includes sending the second message after all rounds and / or time slots corresponding to the first message have ended. In this implementation, sending the second message after all rounds corresponds to sending the second message after the Paging process ends, causing the second device to perform repeated paging. Sending the second message after all time slots corresponds to sending the second message after a round has ended, or after a Paging process in an interaction mode without a round start message, causing the second device to perform repeated paging.

[0041] In some possible designs, the method further includes: receiving Msg1, which includes at least one of the following: upper-layer data, a second process ID, and a first random ID. And / or, receiving Msg3, which includes at least one of the following: upper-layer data and a process ID. The upper-layer data includes the device ID of the second device, the second process ID corresponds to the first request, and the first random ID corresponds to the second device. Here, Msg1 can be Msg1 in a random access process.

[0042] The random access procedure can differ across implementations. Examples are provided below.

[0043] In some possible designs, the first message and / or the second message includes a resource allocation type. When the resource allocation type is type 1, it instructs the second device to access the first device via a non-contention-based random access procedure (CFRA). When the resource allocation type is type 2, it instructs the second device to access the first device via a two-step contention-based random access procedure (2-step CBRA). When the resource allocation type is type 3, it instructs the second device to access the first device via a three-step contention-based random access procedure (3-step CBRA).

[0044] In some possible designs, the second message includes the resource allocation type, which indicates the first type. After sending the second message, the method further includes receiving the CFRA's Msg1, which includes at least one of the following: the upper-layer data, the second process ID. Thus, in the CFRA, the first device can send Msg1 with data to the second device.

[0045] In some possible designs, the method may also include sending Msg2 of the CFRA, which includes either an ACK message or a NACK message.

[0046] In some implementations of CFRA, the first device may not need to send Msg2 after receiving Msg1. That is, the second device can be considered to have completed the access (successfully) after sending Msg1.

[0047] In some implementations of CFRA, after receiving Msg1, the first device can send Msg2. That is, if the second device sends Msg1 and receives Msg2 carrying an ACK message, the access is considered complete (successful). Conversely, if the second device sends Msg1 but does not receive Msg2, the access is considered incomplete. If the second device sends Msg1 and receives Msg2 carrying a NACK message, the access is considered to have failed.

[0048] In some possible designs, the second message includes the resource allocation type, which indicates the second type. After sending the second message, the method further includes: receiving the Msg1 of the 2-step CBRA, the Msg1 of the 2-step CBRA including at least one of the following: the upper-layer data, the second process ID.

[0049] In some possible designs, the method further includes sending Msg2 of the 2-step CBRA, wherein Msg2 of the 2-step CBRA includes an ACK message or a NACK message.

[0050] In some possible designs, the first device determines whether the second device's contention was successful based on the second device's device ID. If the second device's contention is successful, it sends Msg2 with a 2-step CBRA acknowledgment message. If the second device's contention fails, it sends Msg2 with a 2-step CBRA acknowledgment message.

[0051] In some possible designs, the second message includes the resource allocation type, which indicates the third type. After sending the second message, the method further includes: receiving the 3-step CBRA's Msg1, the 3-step CBRA's Msg1 including at least one of the following: the first random ID, the second process ID; and sending the 3-step CBRA's Msg2, the 3-step CBRA's Msg2 including the second random ID.

[0052] In some possible designs, if the second random ID is the same as the first random ID, it indicates that the second device has successfully competed for the data. If the second random ID is different from the first random ID, it indicates that the second device has failed to compete for the data.

[0053] In some possible designs, where the second random ID is the same as the first random ID, the method further includes receiving the Msg3 of the 3-step CBRA, wherein the Msg3 of the 3-step CBRA includes the device ID of the second device.

[0054] In some possible designs, the method further includes sending Msg4 of the 3-step CBRA, which includes either an ACK message or a NACK message. Similar to the CFRA process, Msg4 is optional in this 3-step CBRA procedure. The function of Msg4 is similar to that of Msg2 in the CFRA.

[0055] In some possible designs, the method further includes configuring resource information to the second device via an initial message, and / or a repeat message, and / or a round start message, and / or a time slot start message, the resource information including at least one of the following: round information, time domain information, frequency domain information, and Q value.

[0056] In some possible designs, where the second device is configured with resource information multiple times, the updated resource information is used for the second device to randomly access the first device.

[0057] Therefore, a specific scheme for configuring resource information to a second device is provided. In this application, the first device can configure resources to the second device through one or more of the following: Paging message, Repaging message, round start message, and time slot start message.

[0058] In some possible designs, the method further includes configuring first resource information and second resource information to the second device. The configuration of the second resource information occurs later than the configuration of the first resource information. When both the first and second resource information include configurations corresponding to a first resource type, the first resource set is used for random access from the second device to the first device. The first resource set includes the second resource information and resource configurations in the first resource information that differ from the first resource type. When the resource types configured in the first and second resource information are different, the second resource set is used for random access from the second device to the first device. The second resource set includes the first resource information and the second resource information. The first resource type includes one or more of the following: round information, time-domain information, frequency-domain information, and Q-value.

[0059] In some possible designs, configuring the first resource information to the second device includes configuring the first resource information to the second device via the first message, and / or a round start message, and / or a time slot start message. Configuring the second resource information to the second device includes configuring the second resource information to the second device via a round start message, and / or a time slot start message, and / or the second message.

[0060] This clarifies the specific implementation of the first device configuring resources to the second device.

[0061] For example, when the first device configures resource information to the second device multiple times, if the configured resource information includes duplicate types (such as round information, time domain information, frequency domain information, Q value, etc.), then the resource configured later (i.e., after the update) takes effect. If the configured resource information does not include duplicate types, then joint configuration can be achieved, meaning that all configured resource information takes effect.

[0062] Secondly, a communication method is provided, applied to a second device. The method includes: receiving a second message instructing the second device to initiate random access to a first device to establish AIoT (Artificial Intelligence of Things) communication with the first device; and sending a fourth message for initiating random access to the second device. Exemplarily, the second device may be an AIoT device. In some embodiments, the second message may instruct the second device to repeatedly (or again) initiate random access to the first device. In this example, the second device may have attempted one or more random access attempts before receiving the second message, all of which were unsuccessful or incomplete. For example, the second message may include a Repaging message.

[0063] Based on this scheme, the second device can perform random access to the first device according to the received second message. It is understandable that during communication, the second device may be unable to complete the access in a timely manner for some reason. Thus, by receiving the second message, the second device can attempt to access the device again under the instruction of the first device (such as a card reader).

[0064] In one possible design, before receiving the second message, the method further includes: receiving a first message, the first message being used by the second device to initiate random access to the first device. The first message and the second message are associated with a first request, the first request instructing the first device to perform AIoT communication with the second device. A first random access message is sent, the first random access message being used to initiate random access to the first device.

[0065] In this example, the second device can receive the first message before receiving the second message. The first and second messages can be associated with the first request, allowing the second device to know that they correspond to the same first request message (e.g., a CN request). In this example, assuming the second device receives the first message, it can attempt random access based on the first message. If random access fails, the second device can attempt access again based on the received second message.

[0066] In one possible design, the first message and / or the second message includes at least one of the following: shared resource and / or dedicated resource information, resource allocation type, downlink command indication information, second process ID, information indicating whether to receive or ignore a paging message, identification information of the first device, information indicating whether a device with failed access receives a paging message, information indicating whether a duplicate message exists, and type information of the second device. The second process ID corresponds to the first request. In some implementations, the first request may include the first process ID. The second process ID may be the same as or correspond to the first process ID.

[0067] In one possible design, the first message and / or the second message are configured with a first flag bit, which is used to indicate whether the message carrying the first flag bit is an initial message or a repeat message.

[0068] In one possible design, the first flag bit of the first message indicates that the first message is the initial message. The first flag bit of the second message indicates that the second message is a duplicate message.

[0069] Therefore, by configuring the flag bits, the second device can accurately determine whether the received message is an initial message or a repeat message. An initial message can be the first message sent by the card reader after receiving the CN request, such as the first Paging message. A repeat message can be the second or subsequent message sent by the card reader after receiving the CN request, such as a Repaging message.

[0070] In one possible design, the first message is of type 1, and the second message is of type 2. The first type corresponds to the initial message, and the second type corresponds to the repeating message.

[0071] In one possible design, both the first message and the second message are configured with identification information, wherein the identification information of the first message indicates that the first message is of the first type, and the identification information of the second message indicates that the second message is of the second type.

[0072] This solution provides yet another way to distinguish between initial and repeating messages. For example, it differentiates between initial and repeating messages by using different types.

[0073] In one possible design, the header or control information of the first message includes the second process ID, the first flag bit of the first message, or the identification information of the first message. And / or, the header or control information of the second message includes the second process ID, the first flag bit of the second message, or the identification information of the second message. In this way, after receiving a message (such as the first message, the second message, etc.), the second device can parse the header or control information to determine if a response is needed before parsing the subsequent data portion. This saves power consumption for the second device.

[0074] In one possible design, after receiving the second message, the method further includes: determining, based on the second message, to respond to the second message. Sending the fourth message includes: sending the fourth message if a response to the second message is determined.

[0075] In one possible design, if the second process ID included in the second message has not been received before, and / or the second message is an initial message, a response to the second message is determined. Alternatively, if the second process ID included in the second message has not been received before, and / or the second message is a duplicate message, a response to the second message is determined according to a preset rule.

[0076] In one possible design, the preset rule includes: determining whether random access to the first device has not been accessed or has not been completed.

[0077] In this example, the response to the message may include, based on the message, making a random access to the first device.

[0078] In this way, the second device can respond to all initial messages. For example, the second device can respond to a Paging message. Alternatively, if the second device receives a Repaging message without having received a Paging message before, it can directly respond to the Repaging message because the second process ID of that Repaging message has not been received before.

[0079] If the second device has already received the second process ID, and can determine whether to respond accordingly by combining flag bits, identification information, etc., it can decide whether to respond according to preset rules.

[0080] For example, if the second message (such as a Repaging message) does not contain information indicating whether a response is required or not (such as ID, group ID, resources, etc.), the second device can determine whether to respond to the second message based on whether the connection has been successfully established. The second device can respond to the second message even if the connection has not been established or has not been completed. This solution can be applied to scenarios where the second device can determine whether the connection has been successful.

[0081] For example, if the second message includes instructions on whether to respond or not, the second device can determine whether to respond based on preset rules and the content carried in the second message. This solution can be applied in scenarios where the second device has the ability to determine whether the connection was successful, or in scenarios where the second device does not have this ability.

[0082] In one possible design, before receiving the second message, the method further includes: sending Msg1, which includes at least one of the following: upper-layer data, a second process ID, and a first random ID. And / or, sending Msg3, which includes at least one of the following: upper-layer data and a process ID. The upper-layer data includes the device ID of the second device, the second process ID corresponds to the first request, and the first random ID corresponds to the second device. Msg1 can be Msg1 in a random access process (such as the first message). Msg3 can be Msg3 in a random access process (such as the third message). In different random access processes, the content of Msg1 and / or Msg3 can be the same or different.

[0083] In one possible design, the first message and / or the second message includes a resource allocation type. This resource allocation type instructs the second device to access the first device via a non-contention-based random access procedure (CFRA). Alternatively, the resource allocation type instructs the second device to access the first device via a two-step contention-based random access procedure (2-step CBRA). Alternatively, the resource allocation type instructs the second device to access the first device via a three-step contention-based random access procedure (3-step CBRA).

[0084] In one possible design, the first message includes the resource allocation type, which instructs the second device to access the first device via CFRA. Alternatively, the resource allocation type instructs the second device to access the first device via 2-step CBRA. After receiving the first message, the method further includes sending Msg1, which includes at least one of the following: the upper-layer data, the second process ID.

[0085] In one possible design, random access to the first device fails or is not completed, including: failure to send Msg1, failure to send Msg1, or failure to receive the first message.

[0086] In this example, the second device can determine that access has not been granted or has not been completed if Msg1 is not sent correctly during random access via CFRA or 2-step CBRA. This allows the second device to respond to a second message (such as a Repaging message), for example, by sending a fourth message. This fourth message may include one or more messages from the random access process (such as Msg1, Msg3, etc.).

[0087] In one possible design, the first message includes the resource allocation type, which instructs the second device to access the first device via CFRA. Alternatively, the resource allocation type instructs the second device to access the first device via 2-step CBRA. After sending Msg1, the method further includes receiving Msg2, which includes an ACK message or a NACK message.

[0088] In one possible design, random access to the first device fails or is not completed, including: failure to receive Msg2, or failure to receive Msg2, or receipt of Msg2 including an unacknowledged message.

[0089] In this example, the second device can determine whether it has not been connected or has not completed the connection, based on the relevant procedures of Msg2, in the case of random access via CFRA or 2-step CBRA.

[0090] In one possible design, the first message includes the resource allocation type, which instructs the second device to access the first device via 3-step CBRA. After receiving the first message, the method further includes: sending Msg1, which includes a first random ID corresponding to the second device; receiving Msg2, which includes a second random ID; and, if the first random ID and the second random ID are the same, sending Msg3, which includes the device ID of the second device.

[0091] In one possible design, random access to the first device fails or is incomplete, including: failure to send Msg1 and / or Msg3, or failure to send Msg1 and / or Msg3, or failure to receive the first message; and / or failure to receive Msg2, or failure to receive Msg2.

[0092] In one possible design, after sending Msg3, the method further includes receiving Msg4, which includes an ACK message or a NACK message.

[0093] In one possible design, random access to the first device is not accessed or is not completed, including: failure to receive the Msg4, or not receiving the Msg4, or receiving the Msg4 including an unacknowledged message.

[0094] In this example, the second device can determine whether access has not been completed or has not been completed based on the failure to send or receive messages or the indication of failure in the process when random access is performed via 3-step CBRA.

[0095] In the example above, the second device determines that it needs to respond to the second message because the random access procedure performed before receiving the second message failed.

[0096] In other embodiments, the second device may also determine whether to respond to the second message based on the content carried in the second message.

[0097] In one possible design, the second message includes a device ID corresponding to at least one device that has not accessed or has not completed access, and the random access to the first device has not been accessed or has not been completed, including: the device ID of the second device is included in the second message. Alternatively, the second message includes a device ID corresponding to at least one device that has completed access, and the random access to the first device has not been accessed or has not been completed, including: the device ID of the second device is not included in the second message.

[0098] In one possible design, the second message includes a first set of IDs corresponding to at least one device that has not accessed or has not completed access. This first set of IDs corresponds to at least one device ID, and among the at least one device ID corresponding to this first set of IDs, at least one device ID corresponds to a device that has not accessed or has not completed access. Random access to the first device failing to connect or completing access includes: the device ID of the second device being included in the at least one device ID corresponding to the first set of IDs. Alternatively, the second message includes at least one second set of IDs, which includes the device ID of at least one device that has completed access. Random access to the first device failing to connect or completing access includes: the device ID of the second device not being included in the device IDs corresponding to the second set of IDs.

[0099] In one possible design, the second message includes resource information indicating no access or incomplete access. This resource information includes at least one of the following: round information, time-domain information, frequency-domain information, and Q-value. Random access to the first device failing or failing to complete includes: the resource information used by the second device when it last accessed the first device is included in the second message. Alternatively, the second message includes resource information indicating completed access. Random access to the first device failing or failing to complete includes: the resource information used by the second device when it last accessed the first device is not included in the second message.

[0100] In different implementations of this application, the timing of sending duplicate messages may also differ. These will be explained separately below.

[0101] In one possible design, after receiving the first message, the method further includes: receiving the second message within a first duration. The first duration is a preset duration, and / or the first duration is the duration from the start of the first time slot to the end of the first time slot.

[0102] In one possible design, after receiving the first message, the method further includes: receiving a first time slot start message, which is used to indicate the start of the first time slot.

[0103] In one possible design, after receiving the first message, the method further includes: receiving a second time slot start message, which is used to indicate the end of the first time slot.

[0104] In one possible design, the first message is used to indicate the start of a new round.

[0105] In one possible design, after receiving the first message, the method further includes receiving a third message indicating the start of a new round. The third message includes the first message, or the third message includes the second message.

[0106] In one possible design, after receiving the first message, the method further includes: receiving a first round start message, which indicates the start of the first round.

[0107] In one possible design, receiving the second message includes receiving the second message after all rounds and / or time slots corresponding to the first message have ended.

[0108] In different implementations of this application, the resource information used by the second device when performing AIoT communication can be obtained from the first device through different logics.

[0109] In one possible design, the method further includes configuring resource information to the second device via an initial message, and / or a repeat message, and / or a round start message, and / or a time slot start message, the resource information including at least one of the following: round information, time domain information, frequency domain information, and Q value.

[0110] In one possible design, if the second device is configured with resource information multiple times, the updated resource information is used for the second device to randomly access the first device.

[0111] In one possible design, the method further includes configuring first resource information and second resource information to the second device. The configuration of the second resource information occurs later than the configuration of the first resource information. When both the first and second resource information include configurations corresponding to a first resource type, a first resource set is used for random access from the second device to the first device. The first resource set includes the second resource information and resource configurations in the first resource information that differ from the first resource type. When the resource types configured in the first and second resource information are different, the second resource set is used for random access from the second device to the first device. The second resource set includes the first resource information and the second resource information. The first resource type includes one or more of the following: round information, time-domain information, frequency-domain information, and Q-value.

[0112] In one possible design, configuring the first resource information to the second device includes configuring the first resource information to the second device via the first message, and / or a round start message, and / or a time slot start message. Configuring the second resource information to the second device includes configuring the second resource information to the second device via a round start message, and / or a time slot start message, and / or the second message.

[0113] Thirdly, a communication device is provided. This communication device can be used to execute the schemes provided in the first aspect and any of its possible designs. For example, the communication device can be a card reader. For instance, a base station in topology 1; or a UE in topology 2.

[0114] Fourthly, a communication device is provided. This communication device can be used to execute the schemes provided in the first aspect and any of its possible designs. For example, the communication device can be an AIoT device.

[0115] Fifthly, a communication system is provided, which includes the communication devices provided in the third and fourth aspects.

[0116] In a sixth aspect, a chip system is provided, which is applied to a first device. The chip system may include one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines. The interface circuits are used to receive signals from the memory of the first device and to send the signals to the processors, the signals including computer instructions stored in the memory. When the processor executes the aforementioned computer instructions, the first device performs the methods provided in the first aspect and any of its possible designs.

[0117] A seventh aspect provides a chip system applied to a second device. The chip system may include one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines. The interface circuits are used to receive signals from the memory of the second device and send the signals to the processors, the signals including computer instructions stored in the memory. When the processor executes the aforementioned computer instructions, the second device performs the methods provided in the second aspect and any of its possible designs.

[0118] Eighthly, this application also provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause a first device or a second device to perform the technical solutions provided in the first to second aspects and any possible implementation thereof.

[0119] Ninthly, this application also provides a computer program product that, when run on a computer (such as a first device or a second device), causes the computer to execute the technical solutions provided in the first to second aspects and any possible implementation thereof.

[0120] It is understood that the solutions provided in the third to ninth aspects of this application can be respectively associated with the first aspect and any of its possible designs, and therefore the beneficial effects achieved are similar, which will not be elaborated here. Attached Figure Description

[0121] Figure 1 A schematic diagram illustrating a communication scenario provided in an embodiment of this application;

[0122] Figure 2 A schematic diagram illustrating a communication scenario provided in an embodiment of this application;

[0123] Figure 3 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0124] Figure 4 This is a schematic diagram of the interaction process of a random access method provided in an embodiment of this application;

[0125] Figure 5 This is a schematic diagram of the interaction process of a random access method provided in an embodiment of this application;

[0126] Figure 6 This is a schematic diagram of the interaction process of a random access method provided in an embodiment of this application;

[0127] Figure 7 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0128] Figure 8A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0129] Figure 9 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0130] Figure 10 A schematic diagram illustrating a communication scenario provided in an embodiment of this application;

[0131] Figure 11 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0132] Figure 12 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0133] Figure 13 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0134] Figure 14 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0135] Figure 15 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0136] Figure 16 A schematic diagram of the interaction flow of a communication method provided in an embodiment of this application;

[0137] Figure 17 This is a schematic diagram of the composition of a chip system provided in an embodiment of this application. Detailed Implementation

[0138] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "a plurality of" means two or more.

[0139] The relevant concepts involved in the embodiments of this application will be explained below.

[0140] 1. Ambient Internet of Things (AIoT).

[0141] AIoT aims to provide a low-power, low-complexity, and low-cost Internet of Things (IoT) solution. Within the 3GPP standards framework, it represents a lower-capability standard than Narrowband Internet of Things (NB-IoT). In non-3GPP frameworks, its market target is radio frequency identification (RFID), offering comparable and more advantageous technological solutions.

[0142] The demand for AIoT stems from its aim to address scenarios not covered by current 3GPP technologies, such as the following three scenarios:

[0143] 1) Extreme environmental conditions, such as high pressure, extremely high / low temperature, and humid environments;

[0144] 2) There is a strong demand for one or more of the following: ultra-low complexity, very small device size / shape factor (e.g., thickness in millimeters), maintenance-free (e.g., conventional batteries that do not require device replacement), and longer life cycle.

[0145] 3) Device scenarios where traditional battery-powered devices are not applicable.

[0146] AIoT is also a type of Internet of Things (IoT) service that aims to provide AIoT devices with features such as low power consumption and low complexity, very small size, and longer lifespan. AIoT devices are powered by energy harvesting and can operate without batteries or with limited energy storage capacity (i.e., using capacitors). They can communicate with other devices without a traditional power source and / or avoid human intervention for charging or replacement.

[0147] Typically, ambient-powered IoT devices do not use traditional batteries. The devices themselves use energy derived from radio waves or any other form of energy that may be available for a particular use case. For example, in some scenarios, AIoT devices can draw power from radio waves, which may originate from 5G NR network entities or end devices. In other scenarios, ambient-powered IoT devices can draw power from solar energy, light, motion / vibration, heat, pressure, or any other source of energy.

[0148] AIoT devices can be categorized into the following types:

[0149] Type 1: This type of AIoT device has no energy storage capacity, no independent signal generation / amplification, and can use backscatter transmission;

[0150] Type 2: This type of AIoT device has energy storage capabilities, does not generate independent signals, and can participate in backscatter transmission. The stored energy can be used to amplify the backscatter signal.

[0151] Type 3: This type of AIoT device has energy storage capabilities and independent signal generation;

[0152] Type 4: The device's uplink transmission needs to be triggered based on the downlink transmission (The device originated traffic is triggered by the device terminated traffic or signalling). This type can also be called Device-originated-device-terminated triggered (DO-DTT) type.

[0153] Type 5: Only downlink transmission exists, and the device does not perform uplink transmission (The traffic is terminated at the AIoT device). This type can also be called Device-terminated (DT) type.

[0154] Type 6: Devices can actively perform uplink transmission (Device-originated–autonomous, DO-A).

[0155] 2. Inventory.

[0156] Inventory taking refers to the process by which a reader identifies a device and obtains its identity (ID). This process can be applied in various scenarios, such as logistics management or warehouse management, especially for scenarios with a large number of terminal devices, where it can save a significant amount of manpower and resources and achieve quick and accurate inventory counting.

[0157] 3. RFID technology.

[0158] RFID (Radio Frequency Identification) is a communication technology that allows network devices and terminal devices to communicate non-contactly and bi-directionally via radio frequency. Network devices (such as readers) can use radio frequency to identify devices (such as tags) and read and write related data.

[0159] For example, application scenarios for AIoT technology may include product inventory and indoor command communication.

[0160] Take product inventory as an example. Product inventory can also be called indoor inventory. In this scenario, the communication system, based on AIoT technology, can perform inventory processing on products within a limited area, thereby obtaining product information. This product information may include at least one of the following: product quantity, product type, product identifier, product location, etc.

[0161] 4. Initial Message and Repeat Message. The initial message can be the first message sent after the start of a process (such as a paging process). For example, the initial message may include a paging message. The repeat message can be the Nth message sent after the start of a process (such as a paging process), where N is an integer greater than 1. For example, the repeat message may include a repaging message. In this application, the initial message includes a paging message and the repeat message includes a repaging message as an example, where the repeat message may include information about the number of times the paging message has been sent. In other implementations, the initial message and / or repeat message may also include other messages, and / or, the initial message may be a message different from the paging message, and / or, the repeat message may be a message different from the paging message.

[0162] refer to Figure 1 This is a logical diagram of an AIoT communication method.

[0163] In this example, the devices involved in AIoT communication may include core network devices, access network devices, card readers, and AIoT devices.

[0164] Core network equipment can also be called AIoT controller (AIoT CN, abbreviated as CN). This core network equipment can be an Access and Mobility Management Function (AMF) or a User Plane Function (UPF).

[0165] The access network device can be a base station. This access network device can be a base station specifically configured for AIoT communication, or it can reuse base stations used in 4G, 5G, 6G, or other cellular communications. For example, if the access network device reuses a base station used in 5G communication, it can be simply referred to as a gNB.

[0166] A card reader can be a device that communicates directly with AIoT devices. For example, it can be a mobile phone, a tag reader, or a mobile phone. Taking a mobile phone as an example, a card reader can also be referred to as a UE (user equipment).

[0167] AIoT devices can be simply referred to as devices. In some embodiments, AIoT devices may be configured with an RFID chip. AIoT devices can communicate with card readers via the RFID chip.

[0168] Figure 1 The document also provides a schematic diagram of the device-to-device communication process for AIoT communication.

[0169] like Figure 1 As shown, in Topology 2 scenario, this process may include:

[0170] S101, The core network equipment sends message 101 to the access network equipment.

[0171] In this example, AIoT communication can be initiated by the CN. In other embodiments, AIoT communication can also be initiated by other devices connected to the CN (such as AF). In still other embodiments, AIoT communication can also be initiated directly by the access network device or the card reader.

[0172] In such Figure 1 In the example, message 101 may include an inventory command and / or a DL command.

[0173] In some embodiments, message 101 may also be referred to as a CN request.

[0174] S102, The access network device sends message 102 to the card reader device.

[0175] For example, the base station can send a corresponding message 102 to the reader based on the received message 101. In this scenario, the reader can be a user equipment (UE), and the message 102 can include information representing the inventory command and / or downlink command in message 101. For instance, the access network device can send the CN request carried in message 101 to the card reader device.

[0176] In some embodiments, the base station can establish a communication connection with the Reader through a Radio Resource Control (RRC) communication link.

[0177] Therefore, the base station can send message 102 to the Reader via the RRC communication link.

[0178] S103, The card reader sends a message to the AIoT device.

[0179] For example, message 103 can be an initial message. Message 103 may include paging messages for one or more devices.

[0180] The Paging message may include at least one of the following:

[0181] Shared and / or dedicated resources configured for AIoT communication; Resource Allocation Type (RA type); Downlink Command Indication (DL command) information; Paging Procedure ID; Device ID indicating whether paging is required or ignored; Card Reader ID; Failed Device Paging Indication; Information indicating whether duplicate messages exist; AIoT device type information.

[0182] The AIoT device type can be any of types one through six mentioned above. Based on this AIoT device type information, the AIoT device can determine whether its device type matches the type indicated by the Paging message. If the device types are the same, the AIoT device can respond to the Paging message. Alternatively, if the device types are the same, the AIoT device can reconnect based on subsequent received duplicate messages if it failed to connect or complete the connection process corresponding to the initial message. Or, if the device types are the same, the AIoT device can determine whether to respond to duplicate messages based on whether other conditions are met (such as whether preset rules are met, which will be detailed later) if it failed to connect or complete the connection process corresponding to the initial message. Alternatively, if its device type is different from the type indicated by the Paging message, it will not respond to duplicate messages. Or, if its device type is different from the type indicated by the Paging message, it will determine whether to respond to duplicate messages based on whether preset rules are met.

[0183] The information indicating whether duplicate messages exist is used to indicate whether duplicate messages are present after the initial message. Taking the presence of duplicate messages after the initial message as an example, this information allows the AIoT device to remain awake after receiving the initial message (or if it hasn't connected or completed the connection process corresponding to the initial message), so it can receive subsequent duplicate messages (such as Repaging messages) for reconnection; alternatively, the AIoT device can charge after receiving the initial message (or if it hasn't connected or completed the connection process corresponding to the initial message), and it can also wake up before receiving duplicate messages, so it can receive subsequent duplicate messages (such as Repaging messages) for reconnection.

[0184] Shared and / or dedicated resources configured for AIoT communication may include time-domain and / or frequency-domain resources configured for AIoT communication.

[0185] RA type can include one or more. For example, consider three RA types (e.g., type0, type1, type2). Different RA types can be used to indicate different resource configuration types. For different resource configuration types, the Device can use different random access methods to establish an AIoT communication connection with the Reader.

[0186] For example, if the RA type is the first value, the Device can use a contention-free random access (CFRA) procedure to attempt to establish an AIoT communication connection with the Reader. For example, the first value can be 0, or binary 00.

[0187] For example, if the RA type is the second value, the Device can use a 2-step contention-based random access (2-step CBRA) procedure to attempt to establish an AIoT communication connection with the Reader. For instance, the second value can be 1, or binary 01.

[0188] For example, if the RA type is a third value, the Device can use a 3-step contention-based random access (3-step CBRA) process to attempt to establish an AIoT communication connection with the Reader. For instance, the third value can be 2 or binary 10.

[0189] Downlink command indication (DL command) information can be used to indicate whether the Paging message is used to establish AIoT communication for DL ​​command transmission.

[0190] When the Device ID field indicates that paging is required, the Device corresponding to the Device ID carried in the paging message can receive the paging message and respond accordingly. Conversely, when the Device ID field indicates that paging is required, the Device corresponding to the Device ID carried in the paging message can choose not to receive the paging message, or receive the paging message but not respond to it or parse it.

[0191] The paging process ID can correspond to a paging message. For example, based on different CN requests, the paging process IDs corresponding to the generated paging messages will be different. When a Reader generates multiple paging messages (such as paging messages and repaging messages) after receiving a single CN request, the paging process IDs corresponding to each paging message can be the same or different.

[0192] In some implementations, the paging procedure ID can be the same as the CN request ID. In other implementations, the paging procedure ID can have a one-to-one mapping relationship with the CN request ID. In this way, the Reader can determine the corresponding paging procedure ID based on the CN request ID.

[0193] In the following example, the paging process ID can be represented as the paging ID.

[0194] If a failed device receives a paging indication and is configured, the corresponding indication has been randomly accessed by the failed device and the device will respond to the current paging message according to the configuration.

[0195] In this application, the paging message sent by the Reader can be used to trigger inventory or command sending.

[0196] In some embodiments, a paging message may include a device ID of a single A-IoT device.

[0197] In this example, upon receiving a paging message, the Device can compare the device ID carried in the paging message with its own device ID. If the device ID in the paging message matches the device's own device ID, the Device can attempt to establish an AIoT communication connection with the Reader.

[0198] In other embodiments, the paging message may include a message containing a group ID that maps to multiple A-IoT devices.

[0199] In this example, upon receiving a paging message, the Device can determine whether the group ID of the multiple Devices mapped to the paging message includes the current Device. If the Device is included among the multiple Devices corresponding to that group ID, the Device can attempt to establish an AIoT communication connection with the Reader.

[0200] In other embodiments, the paging message may not contain a device ID. For example, all devices that receive the paging message may attempt to establish an AIoT communication connection with the Reader.

[0201] The above Figure 1 In this example, we'll take the separation of the access network device and the card reader as an example. In other scenarios, the access network device and the card reader can be the same device. In this case, the access network device can communicate directly with AIoT devices.

[0202] For example, refer to Figure 2 The scenario in Topology 1 provides an illustration of yet another communication scenario.

[0203] In this example, the core network device can send message 201 to the access network device via S201. Message 201 may include a CN request.

[0204] Access network devices can communicate directly with AIoT devices via message 202, which is sent in S202. For example, message 202 may include a Paging message.

[0205] Taking the Device receiving a Paging message and establishing an AIoT communication connection with the Reader as an example, this corresponds to... Figure 1 In the scenario shown, the Device can establish an AIoT communication connection with the UE based on the Paging message. And corresponding to... Figure 2 In the scenario shown, the Device can establish an AIoT communication connection with access network devices (such as base stations) based on Paging messages.

[0206] refer to Figure 3 In an AIoT communication scenario, after the card reader sends a Paging message to the AIoT device, AIoT communication between the card reader and the AIoT device can be achieved through steps A, B, and C.

[0207] like Figure 3 As shown, in step A, the card reader can send an AIoT paging message to the AIoT device. This AIoT paging message can correspond to the aforementioned... Figure 1 or Figure 2 The paging message in the middle.

[0208] like Figure 3 As shown in step B, the AIoT device can attempt to establish an AIoT communication connection with the card reader device through the AIoT random access process based on the received AIoT paging message.

[0209] Once an AIoT communication connection is successfully established, the AIoT device can send its data to the card reader (such as performing D2R data transmission) through this established AIoT communication connection.

[0210] In this application, random access failure is the opposite of random access success. For example, random access is successful if all message exchanges during the random access process are completed, and / or if a message indicates successful random access (such as ACK). Conversely, random access fails if one or more message exchanges during the random access process are not completed in the Paging process, or if a message indicates random access failure (such as NACK).

[0211] In some implementations, AIoT communication may further include step C after step B. In step C, the card reader can further send instructions for additional data reporting to the AIoT device via an R2D data transmission instruction. Correspondingly, the AIoT device can perform D2R data transmission to the card reader through the established AIoT communication connection.

[0212] In different implementations of this application, such as Figure 3 In step B, the methods by which the AIoT device and the card reader establish an AIoT communication connection can differ. For example... Figure 1 The communication scenario shown is an example.

[0213] In some embodiments, after receiving a Paging message (such as message 103), the AIoT device may attempt to establish an AIoT communication connection with the card reader through a contention-free random access (CFRA) procedure.

[0214] For example, refer to Figure 4 This is a schematic diagram of a CFRA access process.

[0215] like Figure 4 As shown, the solution may include:

[0216] S301, The card reader sends message 103 to the AIoT device.

[0217] For example, the execution of S301 can be referred to the foregoing. Figure 1 S103 in the context of this message. This message 103 may include a Paging message sent by the card reader to the AIoT device.

[0218] Taking the example of an AIoT device determining to perform random access to a card reader based on Paging messages, if the random access is successful, the AIoT device can establish an AIoT communication connection with the card reader.

[0219] Based on the example above, in some implementations of this example, the Paging message sent by the card reader to the AIoT device may carry information indicating that the RA type is type0.

[0220] Therefore, the AIoT device can execute CFRA based on RA type being type0, attempting to establish an AIoT communication connection with the card reader. The CFRA process can specifically include the following steps S302 or S302-S303.

[0221] S302, The AIoT device sends message 301 to the card reader.

[0222] For example, message 301 may include CFRA message 1 (Msg1).

[0223] In some embodiments, Msg1 may carry upper layer data. This upper layer data may include the device ID of the AIoT device and / or other upper layer data.

[0224] In some other embodiments, the Paging ID is carried in the Paging message as an example. The Paging ID can also be carried in Msg1 corresponding to message 301.

[0225] In some implementations, the S302 enables AIoT devices to access card readers via CFRA.

[0226] In some implementations, after executing S302, the CFRA-based access procedure may also include S303:

[0227] S303, The card reader sends a message to the AIoT device 302.

[0228] For example, in this implementation, the card reader can send message 302 to the AIoT device upon receiving Msg1. This message 302 can also be referred to as CFRA message 3 (Msg2).

[0229] In some embodiments, message 302 may include acknowledgment (ACK) information. Thus, the card reader can indicate that the AIoT device has successfully accessed the network by sending message 302 carrying ACK information. Correspondingly, the AIoT device can determine that it has successfully accessed the card reader based on the received message 302.

[0230] In other embodiments, message 302 may include a non-acknowledgment (NACK) message. Thus, the card reader can indicate that the AIoT device's random access has failed by sending message 302 carrying the NACK message. Correspondingly, the AIoT device can determine that its random access to the card reader has failed based on the received message 302.

[0231] Therefore, through the above S302 or S302-S303, the AIoT device can attempt to establish an AIoT communication connection with the card reader via CFRA upon receiving the Paging message.

[0232] In other embodiments, after receiving a Paging message, the AIoT device may attempt to establish an AIoT communication connection with the card reader through a 2-step non-contention random access procedure (CBRA).

[0233] For example, refer to Figure 5 This is a schematic diagram of a 2-step CBRA access process.

[0234] like Figure 5 As shown, the solution may include:

[0235] S401, The card reader sends message 103 to the AIoT device.

[0236] For example, the execution of S401 can be referred to the foregoing. Figure 1 S103 in the context of this message. This message 103 may include a Paging message sent by the card reader to the AIoT device.

[0237] Taking the example of an AIoT device determining to perform random access to a card reader based on Paging messages, if the random access is successful, the AIoT device can establish an AIoT communication connection with the card reader.

[0238] Based on the example above, in some implementations of this example, the Paging message sent by the card reader to the AIoT device may carry information indicating that the RA type is type1.

[0239] Therefore, the AIoT device can perform a 2-step CBRA based on the RA type being type1, attempting to establish an AIoT communication connection with the card reader. This 2-step CBRA process can specifically include the following steps S402 or S402-S403.

[0240] S402, The AIoT device sends message 401 to the card reader.

[0241] For example, message 401 may include message 1 (Msg1) of 2-step CBRA.

[0242] In some embodiments, Msg1 may carry upper layer data. This upper layer data may include the device ID of the AIoT device and / or other upper layer data.

[0243] In some other embodiments, the Paging ID is carried in the Paging message as an example. The Paging ID can also be carried in Msg1 corresponding to message 201.

[0244] In some implementations, the S402 enables AIoT devices to connect to card readers via a 2-step CBRA.

[0245] In some implementations, after executing S402, the 2-step CBRA-based access procedure may also include S403:

[0246] S403, The card reader sends a message 402 to the AIoT device.

[0247] For example, in this implementation, the card reader can send message 402 to the AIoT device upon receiving Msg1. Message 402 can also be referred to as message 2 (Msg2) of the 2-step CBRA.

[0248] In some embodiments, message 402 may include acknowledgment (ACK) information. Thus, the card reader can indicate that the AIoT device has successfully accessed the network by sending message 402 carrying ACK information. Correspondingly, the AIoT device can determine that it has successfully accessed the card reader based on the received message 402.

[0249] In some embodiments, message 402 may include a non-acknowledgment (NACK) message. Thus, the card reader can indicate that the AIoT device's random access has failed by sending message 402 carrying the NACK message. Correspondingly, the AIoT device can determine that its random access to the card reader has failed based on the received message 402.

[0250] Therefore, through the above S402 or S402-S403, the AIoT device can attempt to establish an AIoT communication connection with the card reader via 2-step CBRA upon receiving the Paging message.

[0251] In other embodiments, after receiving a Paging message, the AIoT device may attempt to establish an AIoT communication connection with the card reader through a 3-step non-contention random access procedure (CBRA).

[0252] For example, refer to Figure 6 This is a schematic diagram of a 3-step CBRA access process.

[0253] like Figure 6 As shown, the solution may include:

[0254] S501, The card reader sends message 103 to the AIoT device.

[0255] For example, the execution of S501 can be referred to the foregoing. Figure 1 S103 in the context of this message. This message 103 may include a Paging message sent by the card reader to the AIoT device.

[0256] Taking the example of an AIoT device determining to perform random access to a card reader based on Paging messages, if the random access is successful, the AIoT device can establish an AIoT communication connection with the card reader.

[0257] Based on the example above, in some implementations of this example, the Paging message sent by the card reader to the AIoT device may carry information indicating that the RA type is type2.

[0258] Therefore, the AIoT device can perform a 3-step CBRA based on the RA type being type2, attempting to establish an AIoT communication connection with the card reader. This 3-step CBRA process can specifically include the following steps: S502-S503 or S502-S504.

[0259] S502, The AIoT device sends message 501 to the card reader.

[0260] For example, message 501 may include message 1 (Msg1) of 3-step CBRA.

[0261] In some embodiments, Msg1 may include a random ID. This random ID may be a random ID generated by the AIoT device to the card reader (A-IoT Msg1 including one random ID generated by the A-IoT device to the card reader), and may be determined based on the number of time slots obtained.

[0262] S503, The card reader sends message 502 to the AIoT device.

[0263] For example, in this implementation, the card reader can send message 502 to the AIoT device upon receiving Msg1. Message 502 can also be referred to as message 2 (Msg2) of the 3-step CBRA.

[0264] In this example, message 502 may include a random ID. For example, message 502 may include a random ID received via message 501.

[0265] Correspondingly, AIoT devices can receive this message 502.

[0266] In some implementations, the AIoT device can execute S504 upon receiving message 502, provided that the random ID carried in message 502 is the same as the random ID sent by the AIoT device in message 501. It is understood that if the random ID carried in message 502 is the same as the random ID sent by the AIoT device in message 501, the AIoT device can confirm that the contention was successful. In this way, the AIoT device can perform subsequent operations with the card reader, such as executing S504.

[0267] In some implementations, an AIoT device can determine that the race has failed based on whether it has not received message 502, or whether it has received message 502 but the random ID carried in message 502 is different from the random ID sent by the AIoT device in message 501. This will cause it to exit the 3-step CBRA process.

[0268] Take, for example, an AIoT device determining that it has successfully competed based on a received message 502.

[0269] S504, The AIoT device sends message 503 to the card reader.

[0270] For example, message 503 may correspond to Msg3 of 3-step CBRA.

[0271] The device ID of the AIoT device can be included in this 503 message.

[0272] Therefore, upon receiving a Paging message, an AIoT device can attempt to establish an AIoT communication connection with the card reader via a 3-step CBRA.

[0273] In some embodiments, the 3-step CBRA has been completed via the above steps S502-S504.

[0274] In other embodiments, after S504, the card reader may also send Msg4 of 3-step CBRA to the AIoT device.

[0275] For example, in this implementation, such as Figure 6 As shown, the card reader sends message 504 to the AIoT device. This message 504 can correspond to Msg4 in 3-step CBRA. Message 504 can carry either ACK or NACK information. Taking message 504 carrying ACK information as an example, the AIoT device can determine that the card reader has successfully received the device ID based on the received ACK information. Taking message 504 carrying NACK information as an example, the AIoT device can determine that the card reader has not received the device ID, or has failed to successfully parse the device ID, based on the received NACK information.

[0276] Therefore, through the above Figures 2 to 6 For example, an AIoT device can indicate the RA type through a card reader and attempt to establish an AIoT communication connection with the card reader through the corresponding random access method.

[0277] Conversely, when an AIoT device randomly connects based on the RA type, if any message in the corresponding process (such as Msg2, Msg4, etc.) is not received, or Msg2 or Msg4 carries a NACK message, or the AIoT device has not received a Paging message from the beginning, then the AIoT device has not connected or has not completed the connection. Conversely, if all message exchanges in the process are completed, and / or Msg2 and / or Msg4 carry ACK messages, then the AIoT device has successfully connected, or the connection has been completed.

[0278] Taking the successful random connection of an AIoT device and a card reader as an example, that is, the successful establishment of an AIoT communication connection with the card reader.

[0279] In this way, AIoT devices can then communicate with card readers based on the AIoT communication connection.

[0280] Take the CN request as an example, which instructs the card reader to perform inventory processing on AIoT devices.

[0281] After successfully connecting to the card reader, the AIoT device can send a CN request to the card reader to report information (such as the product information of the AIoT device) when the corresponding time slot of the AIoT device arrives.

[0282] Combination Figures 4 to 7 As explained above, after receiving the Pageng message, the AIoT device can send Msg1 to the card reader to establish an AIoT communication connection with the card reader through one of the random access procedures described above.

[0283] In practice, a single card reader can interact with multiple AIoT devices simultaneously. To avoid signaling conflicts between different AIoT devices and the card reader, the card reader can configure a specific timing for each AIoT device. This allows the AIoT device to send data to the card reader when its designated timing arrives. For example, after receiving a Paging message, an AIoT device can send Msg1 to the card reader when its designated timing arrives.

[0284] As an example, see reference Figure 7 This paper provides a schematic diagram of the interaction timing between a card reader and an AIoT device.

[0285] like Figure 7 As shown, the card reader can send a Paging message to the AIoT device after receiving a CN request.

[0286] Correspondingly, the AIoT device can send Msg1 to the card reader based on the received Paging message and the RA type configured on the card reader, using the corresponding random access procedure.

[0287] In this example, the card reader can send a round start message to the AIoT device after sending the paging message. For example, the card reader can send a round start message to the AIoT device.

[0288] Next, the card reader can send messages such as "Slot 1 Start," "Slot 2 Start," etc., to the AIoT device to instruct it to start each slot. For example, the card reader can send a "Slot start" message to the AIoT device at the beginning of each slot.

[0289] In this example, each round consists of 2 slots.

[0290] Correspondingly, AIoT devices can send Msg1 to the card reader when their corresponding time slot arrives.

[0291] The parameters of the time slot corresponding to the AIoT device can be directly configured by the card reader, or the parameters of the time slot corresponding to the AIoT device can be calculated and obtained by the AIoT device itself based on the parameters configured by the card reader.

[0292] Take AIoT devices including device 1 and device 2 as an example.

[0293] The time slot corresponding to device 1 can be time slot 1. The time slot corresponding to device 2 can be time slot 2.

[0294] Thus, in Figure 7 In the example, the card reader can send a Paging message to device 1 and device 2 after receiving a CN request.

[0295] Correspondingly, device 1 can perform random access to the card reader based on the received Paging message.

[0296] Device 1 can receive a message indicating the start of round 1 from the card reader. Device 1 can also receive a message indicating the start of time slot 1 from the card reader. In this way, device 1 can determine that its own time slot has arrived and send Msg1 to the card reader.

[0297] Similarly, device 2 can perform random access to the card reader based on the received Paging message.

[0298] Device 2 can receive a message from the card reader indicating the start of round 2. Device 2 can also receive a message from the card reader indicating the start of time slot 1. At this point, device 2's own time slot has not yet arrived, and device 2 continues to wait for a subsequent time slot start message. Device 2 can also receive a message from the card reader indicating the start of time slot 2. In this way, device 2 can determine that its own time slot has arrived and send Msg1 to the card reader.

[0299] In some implementations, a paging process can include multiple rounds. This allows for paging of a large number of AIoT devices.

[0300] like Figure 7 As shown in the timing flow, after all time slots of round 1 have ended, the card reader can send a message indicating the start of round 2 to the AIoT device. Subsequently, the card reader can also send messages indicating the start of time slot 1 of round 2, the start of time slot 2 of round 2, and so on, to the AIoT device.

[0301] Figure 7 In the example, after sending the Paging message, the card reader can interact with the AIoT device through the round start message and the time slot start message, thus realizing the interaction with each AIoT device in the entire Paging process.

[0302] In some embodiments, the Paging message and / or round start message and / or time slot start message corresponding to the same CN request can carry the same Paging ID. Correspondingly, the AIoT device can determine that the received message corresponds to the same CN request based on the fact that the Paging message and / or round start message and / or time slot start message carry the same Paging ID.

[0303] Therefore, in this case Figure 7 In the example, a Paging process may include a Paging message, messages to start one or more rounds, and messages to start multiple time slots.

[0304] In other embodiments, reference is made to... Figure 8 This provides another timeline diagram illustrating the interaction between a card reader and an AIoT device.

[0305] In such Figure 8 In the example, the card reader can send a slot start message to the AIoT device after sending the Paging message.

[0306] In this example, after receiving a CN request, the card reader can send a Paging message to the AIoT device. In the first round, the card reader does not need to send a round start message to the AIoT device; it can directly send messages indicating the start of each time slot. For example, after sending the Paging message, the card reader can send messages indicating the start of time slot 1, the start of time slot 2, etc., to the AIoT device.

[0307] In the case of the end of the first round, unlike Figure 7 The example in the text is as follows. Figure 8 In the example, the card reader can send a Paging message to the AIoT device again, indicating to the AIoT device that the next round (such as the second round) is about to begin.

[0308] So, how should it be done? Figure 8 In the illustrated process, the card reader can send multiple Paging messages upon receiving a CN request. In some implementations, two or more Paging messages corresponding to the same CN request can carry the same Paging ID.

[0309] Correspondingly, AIoT devices can determine the start of the next round of the same CN request based on receiving Paging messages with the same Paging ID.

[0310] Therefore, in this case Figure 8 In the example, a Paging process can include multiple Paging messages and multiple timeslot start messages.

[0311] In other embodiments, reference is made to... Figure 9 This provides another timeline diagram illustrating the interaction between a card reader and an AIoT device.

[0312] In such Figure 9 In the example, we take an AIoT device with a timing function as an example.

[0313] In this example, the card reader can stop sending round start or time slot start messages after sending the Paging message. Correspondingly, the AIoT device can start timing automatically upon receiving the Paging message. The AIoT device can also send Msg1 to the card reader after its corresponding time slot arrives.

[0314] In some embodiments, as Figure 8 The scheme shown is similar; upon receiving a CNrequest, the card reader can resend the Paging message at the start of the next round. Correspondingly, the AIoT device can determine that a new round has begun based on receiving the Paging message again.

[0315] In some embodiments, after receiving a CN request, the Paging messages sent by the card reader for each round may carry the same Paging ID. Correspondingly, the AIoT device can determine the start of the next round for the same CN request based on receiving Paging messages with the same Paging ID.

[0316] Therefore, in this case Figure 9 In the example, a Paging process can include multiple Paging messages.

[0317] The above Figures 4 to 6 Several random access schemes for establishing AIoT communication connections are provided. Figures 7 to 9 Several communication schemes between card readers and AIoT devices are provided. In different embodiments, different random access schemes can be combined with different communication methods to establish AIoT communication connections between AIoT devices and card readers.

[0318] The following explanation uses specific examples.

[0319] It is understood that during communication between AIoT devices and card readers, data or signaling transmission can be based on resources configured on the network side. In different embodiments, the network side may include any one or more of core network devices, access network devices, and card readers.

[0320] In this application, the resource information used in the AIoT communication process may include at least one of the following:

[0321] Round information, time domain information, frequency domain information, Q value.

[0322] Among them, the round information is used to indicate the round in which AIoT communication is performed. The time domain information is used to indicate the time domain information of AIoT communication. The frequency domain information is used to indicate the frequency band and / or frequency point and / or channel information of AIoT communication, the number of frequency division multiplexing, and other information.

[0323] The Q value is used by AIoT devices to determine their own time-domain or frequency-domain information according to preset rules.

[0324] Taking the Q-value as an example to determine its corresponding time-domain information, AIoT devices can use the configured Q-value to determine the time-domain information within the range of 0 to (2π / 3). Q Choose any integer (such as N) between -1) as its corresponding time slot. In this way, after the AIoT device receives the message that the Nth time slot has started, it can confirm that its corresponding time slot has arrived and transmit data with the card reader within that time slot (such as sending Msg1).

[0325] In different embodiments of this application, several different resource configuration methods are provided in the AIoT communication process. These methods include, for example, communication between a card reader and an AIoT device via... Figure 7 The following example illustrates how to interact using the communication method shown.

[0326] In some embodiments, the card reader can configure resource information to the AIoT device via Paging messages.

[0327] In other embodiments, the card reader can configure resource information to the AIoT device via a round start message.

[0328] In other embodiments, the card reader can configure resource information to the AIoT device via a time slot start message.

[0329] In the three configuration methods described above, the configuration resource information can take effect within the corresponding message flow.

[0330] For example, a card reader can configure resource information 1 to an AIoT device via Paging message 1. This resource information 1 can take effect within the Paging message 1 process.

[0331] The process of Paging message 1 can be the logical flow between Paging message 1 and the next Paging message. Thus, the card reader can begin executing the process of Paging message 1 after sending it. The card reader can end the process of Paging message 1 when sending the next Paging message, or after all rounds of the process have been completed. Correspondingly, the AIoT device can enter the process of Paging message 1 after receiving it. The AIoT device can end the process of Paging message 1 after receiving the message indicating the start of the last time slot of Paging message 1.

[0332] Therefore, AIoT devices can use resource information 1 to communicate with card readers within the process of Paging message 1.

[0333] In some implementations, if the next Paging message 2 following Paging message 1 does not carry resource information, resource information 1 continues to be effective within the process corresponding to Paging message 2. In this way, the AIoT device can continue to use resource information 1 to communicate with the card reader within the process corresponding to Paging message 2.

[0334] If Paging message 2 carries resource information (such as resource information 2), and the resource type of resource information 2 is the same as the resource type of resource information 1, then the resource information configured in resource information 2 will replace the resource information configured in resource information 1 and take effect in the process corresponding to Paging message 2.

[0335] In this application, the resource type of resource information may include round information, time domain information, frequency domain information, Q value, etc.

[0336] For example, resource information 1 is configured with round information, time domain information, frequency domain information, and Q value, and resource information 2 is configured with round information, time domain information, frequency domain information, and Q value. Therefore, resource information 2 and resource information 1 have the same resource type. Resource information 2 takes effect.

[0337] For example, resource information 1 is configured with round information, time-domain information, and frequency-domain information, while resource information 2 is configured with frequency-domain information and Q-value. Therefore, the resource types that are duplicated between resource information 2 and resource information 1 can include frequency-domain information. Consequently, the frequency-domain information and Q-value of resource information 2 take effect, and the round information and time-domain information of resource information 1 also take effect.

[0338] For example, resource information 1 is configured with round information, time-domain information, and frequency-domain information, while resource information 2 is configured with a Q value. Therefore, resource information 2 and resource information 1 do not have duplicate resource information. Consequently, the frequency-domain information, Q value, round information, and time-domain information of resource information 2 and resource information 1 are effective.

[0339] In other words, resource information for resource types configured later can override resource information for resource types configured earlier. When resource information 1 includes resource types not configured in resource information 2, the resource information for those resource types not configured in resource information 2 in resource information 1 can take effect in conjunction with resource information 2.

[0340] In other implementations, resource information can also be configured through messages other than Paging messages (such as round start messages, slot start messages, Repaging messages, etc.). In specific implementations, the mechanisms for resource type overriding and / or the coordinated activation of resource types described above can also be followed.

[0341] Taking the example of a card reader configuring resource information 2 to an AIoT device via message 2 at the start of a round, this resource information 2 can take effect within the round corresponding to message 1 at the start of the round. The interaction logic executed within the round corresponding to message 1 at the start of the round is also the interaction logic executed within the process corresponding to message 1 at the start of the round.

[0342] Therefore, AIoT devices can use resource information 2 to communicate with the card reader within the round corresponding to message 1 at the beginning of the round.

[0343] In some implementations, if the resource information is not carried in the next round-starting message 3 following round-starting message 2, the resource information 2 sent in round-starting message 2 continues to be effective within the round corresponding to round-starting message 3. In this way, the AIoT device can continue to use resource information 2 to communicate with the card reader within the round corresponding to round-starting message 3.

[0344] Taking the example of a card reader configuring resource information 3 to an AIoT device via message 3 starting from a time slot, this resource information 3 can take effect within the time slot corresponding to message 3. The interaction logic executed within the round corresponding to message 1 starting from a round is also the interaction logic executed within the process corresponding to message 1 starting from a round.

[0345] Therefore, AIoT devices can use resource information 3 to communicate with card readers within the time slot corresponding to message 3 at the beginning of the time slot.

[0346] In some implementations, if the resource information is not carried in the message 4 that begins the next time slot after the message 3 that begins the time slot, the resource information 3 sent by the message 3 that began the time slot continues to be effective within the time slot corresponding to the message 4 that begins the time slot. In this way, the AIoT device can continue to use the resource information 3 to communicate with the card reader within the time slot corresponding to the message 4 that begins the time slot.

[0347] In other embodiments of this application, the card reader may use two or more of the following messages to configure resource information to the AIoT device: a Paging message, a round start message, and a time slot start message.

[0348] Take, for example, a card reader configuring resource information to an AIoT device via a Paging message and a round start message.

[0349] In some implementations, if resource information 1 is carried in the Paging message, but the round start message 1 does not carry a round start message, resource information 1 will be effective within the round corresponding to the round start message 1.

[0350] AIoT devices can use resource information 1 to communicate with the card reader within the round corresponding to message 1 at the beginning of this round.

[0351] In some other implementations, when resource information 1 is carried in the Paging message and resource information 2 is carried in the round-starting message 2, resource information 2 takes effect within the round corresponding to the round-starting message 2.

[0352] AIoT devices can use resource information 2 to communicate with the card reader within the round corresponding to message 2 at the beginning of this round.

[0353] It is understood that if resource information 2 only includes a portion of the resource configuration, then at least a portion of resource information 1 is effective with resource information 2. Specifically, at least a portion of resource information 1 includes resources in resource 1 that are not included in resource 2.

[0354] For example, the card reader configures resource information 1 to the AIoT device via a Paging message. This resource information 1 includes time-domain information and frequency-domain information 1. Within the process corresponding to this Paging message, the card reader configures resource information 2 to the AIoT device via round-start message 1. This resource information 2 includes frequency-domain information 2.

[0355] Thus, within the round corresponding to message 1 at the beginning of this round, the time-domain information configured in the Paging message and the frequency-domain information 2 configured in resource information 2 take effect. Correspondingly, the AIoT device can communicate with the card reader within the round corresponding to message 1 at the beginning of this round using the configured time-domain information and frequency-domain information 2.

[0356] For example, the card reader configures resource information 1 to the AIoT device via a Paging message. This resource information 1 includes frequency domain information 1. Within the process corresponding to this Paging message, the card reader configures resource information 2 to the AIoT device via round start message 1. This resource information 2 includes time domain information and Q. Resource information 1 and resource information 2 together form a complete resource configuration. The AIoT device can then use this configured resource, along with frequency domain information 1, time domain information, and Q, to communicate with the card reader within the round corresponding to round start message 1.

[0357] The above example uses the card reader device configuring resource information to the AIoT device through paging messages and round start messages.

[0358] In other embodiments, the card reader can also configure resource information to the AIoT device via a Paging message and a time slot start message, or a round start message and a time slot start message, or a Paging message, a round start message and a time slot start message.

[0359] For example, a card reader can configure frequency domain resource information to an AIoT device in a Paging message. A card reader can also configure time domain resource information to an AIoT device in a round start message. A card reader can also configure frequency domain resource information to an AIoT device in a time slot start message.

[0360] In this application, when a card reader configures resource information through multiple messages, the last sent resource information takes effect, or multiple messages configuring resource information take effect jointly. AIoT devices can communicate with the card reader using the updated resource information.

[0361] The above embodiments provide a detailed description of the specific implementation of configuring resource information from a card reader to an AIoT device. The AIoT device and the card reader can synchronize resource configurations through any of the above-described resource configuration methods, and then communicate with each other using the configured resources.

[0362] In some cases, when a card reader receives a CN request, it may be unable to page all AIoT devices through a single paging process. This means that some AIoT devices may fail to establish a random connection with the card reader during the paging process.

[0363] For example, refer to Figure 10 This is a schematic diagram of an AIoT communication scenario. Combined with... Figure 1 The explanation is as follows. Figure 10In this example, the card reader is taken as the UE. The vicinity of the UE may include multiple AIoT devices, such as AIoT device 1, AIoT device 2, and AIoT device 3.

[0364] like Figure 1 As shown in the interaction flow, in this... Figure 10 In the scenario shown, after receiving message 102 (i.e., receiving CN request), the card reader can send Paging messages (such as message 103) to each AIoT device.

[0365] In some implementations, one or more of AIoT device 1, AIoT device 2, and AIoT device 3 may fail to complete random access to the card reader in a single Paging process.

[0366] For example, AIoT device 1 did not receive the Paging message properly due to low battery or other issues. Combined with... Figure 3 The explanation is that if AIoT device 1 does not receive an AIoT paging message, random access to the card reader will not be triggered.

[0367] For example, the card reader configures Q1 and Q2 for AIoT devices 2 and 3 respectively. AIoT devices 2 and 3 calculate their respective Q values ​​and respond within the same time slot. This results in AIoT devices 2 and 3 sending Msg1 to the card reader within the same time slot. Consequently, the card reader (e.g., the UE) receives multiple Msg1 messages in the same time slot, leading to a problem where the UE cannot parse them. When AIoT device 2 or AIoT device 3 uses a method such as... Figure 5 The 2-step CBRA shown or as Figure 6 Random access is performed via the 3-step CBRA shown, or through methods such as... Figure 4 If the CFRA shown is used for random access and the CFRA includes Msg2, the UE will be unable to send Msg2 to AIoT device 2 and AIoT device 3 because the UE cannot parse Msg1 of AIoT device 2 and AIoT device 3. This will lead to the failure of AIoT device 2 and AIoT device 3 to access the card reader.

[0368] In this scenario, to enable random access to all AIoT devices, the card reader can perform a repeated paging process with the AIoT devices. For example, upon receiving the same CN request, the card reader can initiate a first paging message to each AIoT device. Subsequently, the card reader can initiate a second or more paging messages to one or more AIoT devices. The CN request associated with the repeated paging message is the same as the CN request associated with the initial paging message.

[0369] In the following description, to distinguish between the initial Paging message and the repeated Paging message, the initial Paging message will be referred to as a Paging message, and the repeated Paging message will be referred to as a Repaging message. It should be noted that this distinction in name is for illustrative purposes only, and in actual implementation, it is not required that the name and / or content of the repeated Paging message be consistent with the initial Paging message.

[0370] In some embodiments of this application, the Repaging message may include the same Paging ID as the Paging message. For example, the Paging message may carry the Paging ID corresponding to the CN request. The Repaging message may also include the Paging ID corresponding to the same CN request.

[0371] In this way, AIoT devices can determine that they have not entered the process of a new CN request based on the received Repaging message carrying the same Paging ID.

[0372] In different embodiments of this application, Paging messages and Repaging messages can be configured in different ways.

[0373] In some embodiments, the Paging message and the Repaging message may include an identifier bit. When the identifier bit is A, it indicates that the message is a Paging message. For example, A is 0. When the identifier bit is B, it indicates that the message is a Repaging message. For example, B is 1.

[0374] In this way, an AIoT device can determine that a received paging message is a paging message based on the identifier bit A. Similarly, an AIoT device can determine that a received paging message is a repaging message based on the identifier bit B.

[0375] Once an AIoT device determines that it has received a Paging or Repaging message, it can respond accordingly.

[0376] For example, refer to Figure 11 For example, we can distinguish between Paging messages and Repaging messages using flags.

[0377] Upon receiving a CN request, the card reader can execute S1101 and send message 111. Message 111 can be a Paging message. Message 111 may include ID 0 to indicate that the Paging ID is 0. The flag bits in message 111 can be configured to 0 to indicate that message 111 is an initial Paging message.

[0378] In this example, AIoT device 1 can receive message 111. AIoT device 1 determines that message 111 is an initial paging message based on the flag bit being 0. Correspondingly, AIoT device 1 can respond to message 111. For example, AIoT device can execute S1102, sending Msg1 to the card reader, thereby triggering a random access procedure with the card reader.

[0379] Take AIoT device 1 as an example, which successfully connects randomly after sending Msg1.

[0380] The card reader can execute S1103, sending message 112. Message 112 may include ID 0 to indicate that the Paging ID is 0. The flag bit in message 112 can be configured to be 1 to indicate that message 112 is a Repaging message.

[0381] In this example, AIoT device 1 can receive message 112. Based on the flag bit being 1, AIoT device 1 determines that message 112 is a Repaging message. AIoT device 1 can decide not to respond to this Repaging message based on the successful random access already established.

[0382] refer to Figure 12 It provides a schematic diagram of the interaction process between devices in the event of a failure to access randomly based on Paging messages.

[0383] like Figure 12 As shown, after receiving a CN request, the card reader can execute S1201 and send message 111. This message 111 is similar to... Figure 11 Message 111 carries ID 0 and a position 0.

[0384] In some embodiments, AIoT device 2 may not receive message 111 normally. Thus, AIoT device 2 does not initiate a random access procedure to the card reader. In other embodiments, AIoT device 2 receives message 111 normally, but is unable to send Msg1 to the card reader due to low battery. In other embodiments, such as... Figure 12 As shown, AIoT device 2 can receive message 111 normally and execute S1202 to send Msg1 to the card reader.

[0385] Correspondingly, the card reader may fail to receive Msg1 normally, or the card reader may not send a subsequent response (such as Msg2) to AIoT device 2, or the card reader may send Msg2 but AIoT device 2 may not receive it normally. In this case, random access of AIoT device 2 in the Paging process will fail.

[0386] Subsequently, the card reader can execute S1203, sending message 112. This message 112 is related to... Figure 11 The message shown is similar to Message 112, which is as follows: Figure 12 In the example, message 112 can carry ID 0 and a flag bit of 1.

[0387] In some implementations, AIoT device 2 can determine from the received message 112 that message 112 is a Repaging message within the same CN request process as message 111. Correspondingly, AIoT device 2 can respond to message 112 if the random access has not yet succeeded. For example, AIoT device 2 can execute S1204 to send Msg1 to the card reader, attempting random access to the card reader. Thus, within the Paging process of message 112, AIoT device 2 can complete the random access to the card reader.

[0388] Thus, based on such Figure 11 as well as Figure 12 The provided solution allows card readers to distinguish between Paging and Repaging messages by setting different flag bits in messages carrying the same Paging ID.

[0389] Correspondingly, the AIoT device can respond to the Repaging message with the flag bit set to 1 if the received message flag bit is 1 and random access has failed, or if random access has not yet been performed (e.g., the AIoT device did not receive message 111 normally). The AIoT device can perform random access to the card reader during this Repaging process, so as to complete the random access to the card reader within this Repaging process.

[0390] In the above example, the Paging message and the Repaging message have different flag bits. In other embodiments, the Paging message and the Repaging message may have different paging types. Messages with different paging types may have different data formats and / or different data lengths and / or different data contents and / or different message types.

[0391] In some embodiments, messages of different paging types can be distinguished by identification information. Identification information can be used to identify message types.

[0392] Taking an identification information consisting of 2 bits as an example, in some implementations, the identification information of a Paging message may include 00, while the identification information of a Repaging message may include 01.

[0393] In other embodiments, the identification information can also be used to represent other messages. For example, the identification information for Msg2 can be 10. Similarly, the identification information for Msg4 can be 11.

[0394] For example, when a device parses a data packet, it will first parse the data packet header or control information portion. The control information can be included in the control data packet. Including the paging type, flag bits, or paging procedure ID in the data packet header or control information portion can allow the device to avoid parsing the content of the data portion, such as resource information, when it determines that no reply is needed. The paging type of the message (such as the identification information mentioned above) and / or the paging procedure ID can be configured in the control data packet header or included in the control information.

[0395] For example, corresponding to such Figure 11 or Figure 12 In the example, the control data packet header of message 111 may include a field indicating that the paging type of message 111 is initial paging. Correspondingly, after receiving message 111, the AIoT device can parse the header of message 111 to determine that message 111 is an initial paging message. The AIoT device can then determine whether message 111 is an initial paging message. Figure 11 or Figure 12 The scheme shown is implemented to respond to message 111.

[0396] For example, the control information in message 112 may include a field indicating that the paging type of message 112 is a repeat paging message. Correspondingly, after receiving message 112, the AIoT device can parse the header of message 112 to determine that message 112 is a Repaging message. The AIoT device can then determine whether message 112 is a Repaging message based on the following... Figure 11 or Figure 12 The scheme shown determines whether to respond to message 112.

[0397] As explained above, Paging and Repaging messages can carry the same Paging ID. In some embodiments of this application, this Paging ID can be configured together with the paging type field in the control data header. This allows the AIoT device to determine whether the message is a Paging or Repaging message by parsing the control data packet header. Taking the AIoT device receiving a Repaging message as an example, if the AIoT device does not respond to the Repaging message, it does not need to parse the subsequent data (such as the control data packet) in the message header. This saves power consumption for the AIoT device.

[0398] The above Figures 11 to 12 The provided solution, as well as subsequent solutions related to paging types, provides the sending logic for Paging and Repaging messages corresponding to the same CNrequest.

[0399] In the example above, the Paging message and the Repaging message may include the same Paging ID, as well as a flag or paging type field indicating whether the message is an initial paging or a repeat paging.

[0400] In other embodiments, the Paging message may also include a field indicating support for repeated paging. This allows the AIoT device to determine, based on this field, that it may subsequently receive a Repaging message. If the AIoT device lacks power to initiate a random access procedure, or if the AIoT device has not completed random access during the Paging process, it can wait to receive a Repaging message. In some implementations, the AIoT device can charge during this waiting period. Conversely, the AIoT device can enter sleep mode after completing random access during the Paging process, thereby saving power. Similarly, if the Paging message does not include a field indicating support for repeated paging or does not support repeated paging, the AIoT device can determine, based on this field, that it will not receive a Repaging message subsequently and should select a later time slot for access so that it can charge in the earlier time slot. For example, it could select a time slot greater than a first threshold for access. The Paging message may also include the interval between the start of a time slot or the start of a round and the Paging message itself, so that the device can charge based on this information and receive the start indication of the time slot or round at the start of the time slot or round.

[0401] In other embodiments, the card reader can send a termination instruction to the AIoT device at the end of the paging process. For example, as shown in... Figure 7 Taking the interaction flow shown as an example, the card reader can send the end indication after all time slots of both rounds of the Paging message have ended. Correspondingly, the AIoT device can determine the end of the Paging process based on receiving this end indication. In some implementations, the AIoT device can determine the end of the CN request corresponding to the Paging process based on receiving the end indication, and will not receive any more Paging messages corresponding to this process. Thus, even if the random access process corresponding to this Paging is not completed, it can directly enter sleep mode. In other implementations, the AIoT device can enter sleep mode based on the end indication and no longer receive subsequent messages (such as Repaging or Paging messages).

[0402] The above provides a brief explanation of the logic for initial paging and repeated paging.

[0403] The example given is the response mechanism of an AIoT device after receiving a Repaging message, based on whether the device has completed random access in the Paging process.

[0404] In other embodiments, AIoT devices can determine their response logic to Repaging messages based on other rules. These will be detailed later.

[0405] In this application, in different device interaction methods, repeated paging messages (i.e., repaging messages) can be configured to be sent at different times.

[0406] Examples will be given below.

[0407] In some embodiments, the card reader can send a Repaging message to the AIoT device after the Paging process is completed.

[0408] For example, refer to Figure 13 This is another interactive process diagram provided in the embodiments of this application.

[0409] How Figure 13 In the example, AIoT devices and card readers are used via, for example... Figure 7 The above illustrates an example of communication via interactive methods. Figure 7As explained, in this interaction method, the card reader can send a Paging message to the AIoT device upon receiving a CNrequest from the core network device. During this Paging process, the card reader can send one or more round start messages and one or more time slot start messages to the AIoT device.

[0410] like Figure 13 As shown, the process may include:

[0411] S1301, The core network equipment sends a CN request to the card reader.

[0412] For example, the CN request may include an inventory command and / or a downlink command (DLcommand). Thus, through this CN request, the core network device can issue the corresponding service to be executed for the current AIoT communication to the card reader device.

[0413] In some embodiments, the CN request may also include information about the AIoT devices participating in AIoT communication.

[0414] Taking a CN request that includes an inventory command as an example, in this example, the CN request may include the device IDs of the AIoT devices participating in the inventory, or the device IDs of the AIoT devices not participating in the inventory, or the group IDs of the AIoT devices participating in the inventory, or the group IDs of the AIoT devices not participating in the inventory.

[0415] In some embodiments, the CN request may also include information indicating the RA type.

[0416] For example, the CN request can use the RA type to instruct AIoT devices to randomly access via CFRA, 2-step CBRA, or 3-step CBRA.

[0417] S1302, The card reader sends message 131 to the AIoT device.

[0418] For example, message 131 may include a Paging message. In some embodiments, the Paging message in message 131 may be an initial Paging message. Thus, the initial Paging process is initiated by the initial Paging message, and the AIoT device is paged for the first time.

[0419] Based on the foregoing description, in this example, the Paging message may include at least one of the following:

[0420] Shared and / or dedicated resources configured for AIoT communication; RA type information; Downlink command indication (DLcommand) information; Paging ID; Device ID indicating whether to receive paging or ignore paging; Card reader ID; Failed device paging indication; Information indicating whether duplicate messages exist; AIoT device type information.

[0421] S1303, The card reader sends a round start message to the AIoT device.

[0422] S1304, the card reader and the sending of a time slot start message to the AIoT device.

[0423] In this example, refer to Figure 7 As explained in the documentation, each paging process can include one or more rounds. At the start of each round, the card reader can send a round start message to the AIoT device.

[0424] Each round can include one or more time slots. At the start of each time slot, the card reader can send a "slot start" message to the AIoT device.

[0425] As explained above, the card reader can configure resource information to the AIoT device through Paging messages and / or round start messages and / or time slot start messages.

[0426] Resource information may include at least one of the following: time-domain information, frequency-domain information, and Q value for AIoT communication.

[0427] The specific mechanism for the activation of resource information is as explained above and will not be repeated here.

[0428] For AIoT devices, communication with card readers can be achieved based on the configured resource information.

[0429] For example, an AIoT device can determine whether to respond to a Paging message based on the Paging message.

[0430] Taking a paging message that includes a device ID requiring paging as an example, the paging message can include one or more device IDs. Each AIoT device among these device IDs can randomly access the card reader upon receiving the paging message.

[0431] For example, the Paging message includes the device ID of AIoT device 1 and indicates that the device corresponding to the device ID of AIoT device 1 needs to receive a paging message.

[0432] In this way, AIoT device 1 can include its own device ID in the Paging message, and the Paging message indicates that it needs to receive a paging message, thus determining that it needs to respond to this paging process.

[0433] In some implementations, AIoT device 1 can determine its corresponding time slot based on the Q value carried in the Paging message.

[0434] Therefore, when its own time slot arrives, AIoT device 1 can attempt to establish AIoT communication with the card reader according to the random access method indicated by the RA type in the Paging message. For example, when its corresponding time slot arrives, AIoT device 1 can send Msg1 to the card reader according to the resource information configured in the card reader and through the random access method indicated by the RA type.

[0435] The specific implementation process is as described in the previous example and will not be repeated here.

[0436] For each AIoT device within the communication range of the card reader, a random access to the card reader can be performed when communication with the card reader is required, following a similar process described above.

[0437] The initial paging process ends after all rounds and time slots have been completed. In some embodiments, the card reader may send an end indication to the AIoT device at the end of the initial paging process.

[0438] It is understandable that in some embodiments, some AIoT devices that need to access the card reader may experience random access failures during the initial Paging process for various reasons.

[0439] In this way, the card reader can send a Repaging message to the AIoT device to re-initiate the paging process (such as the Repaging process), so that the AIoT device can successfully establish a communication connection with the card reader through random access.

[0440] In this example, the card reader can send a Repaging message to the AIoT device after the initial Paging process is completed, when a Repaging process needs to be initiated.

[0441] In some embodiments, such as Figure 13 As shown, the card reader can determine whether to initiate a repaging process based on the repaging instruction sent by the core network device. For example, an AIoT device that has successfully connected randomly during the repaging process can determine whether to initiate a repaging process based on the following... Figure 3Steps B and / or C, as shown, involve sending D2R data to the card reader. The card reader can then send the acquired D2R data to the core network device. Therefore, the core network device can determine that there are AIoT devices experiencing random access failures based on the insufficient amount of received D2R data. Correspondingly, the core network device can send a Repaging instruction to the card reader. In some implementations, the core network device can include the device ID of the AIoT device that needs to participate in repeated paging, or the device ID of the AIoT device that does not need to participate in repeated paging, in the Repaging instruction.

[0442] In other embodiments, the card reader may determine on its own whether to initiate a Repaging process based on random access failures on some time-domain resources (such as time slots) and / or frequency-domain resources (such as frequency points).

[0443] In other embodiments, the card reader can determine whether to initiate a Repaging process based on the discrepancy between the amount of D2R data received in the Paging process and the number of devices that need to be inventoried.

[0444] In this way, after the initial paging process is completed, the card reader can initiate the repaging process to the AIoT device.

[0445] like Figure 13 As shown, the process may include:

[0446] S1305, The card reader sends message 132 to the AIoT device.

[0447] For example, message 132 may include a Repaging message. This Repaging message may carry the same Paging ID as the Paging message. By sending this Repaging message, the card reader can trigger the Repaging process.

[0448] In this example, the Repaging message may include at least one of the following:

[0449] Shared and / or dedicated resources configured for AIoT communication; RA type information; Downlink command indication (DLcommand) information; Paging ID; Device ID indicating whether to receive paging or ignore paging; Card reader ID; Failed device paging indication; Information indicating whether duplicate messages exist; AIoT device type information.

[0450] In some implementations, the Repaging message may also carry information indicating the number of times (M). This M-times information can indicate that the Repaging message is the Mth Paging or Repaging message sent. Here, M is an integer greater than or equal to 1.

[0451] In different embodiments, the content of the Paging message and the Repaging message may be the same or different.

[0452] Take the example where the content of the Repaging message is the same as the content of the Paging message.

[0453] Understandably, in some cases, the device ID for AIoT communication indicated by the core network device is not visible to the card reader. Therefore, the card reader can encapsulate the NAS PDU from the core network device within a Repaging message. The resulting Repaging message can then be identical to the Paging message.

[0454] Take the example of a difference between the content of the Repaging message and the content of the Paging message.

[0455] In this example, the card reader is visible to the device IDs. Thus, the card reader can determine the device IDs that need to participate in paging during the repaging process, based on the device IDs of the AIoT devices that have successfully and randomly connected during the paging process, and all device IDs required to participate in AIoT communication as indicated in the CN request. These devices that need to participate in paging can be devices that failed to connect randomly during the paging process or device IDs for which the card reader did not receive a response during the paging process.

[0456] For example, a card reader can carry the ID of the device or group ID that needs to participate in paging in the Repaging message.

[0457] For example, a card reader can carry the ID or group ID of a device that does not need to participate in paging in the Repaging message.

[0458] In some other embodiments of this application, the Repaging message may include information about resources that experienced conflicts or did not receive random access messages (such as Msg1, Msg3, etc.) during the Paging process. The information related to conflicts includes resource information such as the round, time slot, and frequency point of resources that simultaneously received two or more random access messages.

[0459] For example, the relevant information may include at least one of the following: information on the round in which a conflict occurred or a random access message was not received, information on the time slot in which a conflict occurred or a random access message was not received, and information on the frequency point in which a conflict occurred or a random access message was not received.

[0460] S1306, The card reader sends a round start message to the AIoT device.

[0461] S1307, The card reader sends a time slot start message to the AIoT device.

[0462] It should be noted that, in this example, the resource configuration method in the Repaging process can be referenced from the Paging process.

[0463] In some embodiments, the card reader can configure resource information to the AIoT device via a Repaging message and / or a round start message and / or a time slot start message in the Repaging process.

[0464] In other embodiments, the card reader may not configure resource information to the AIoT device during the repaging process. In this way, the AIoT device and the card reader can continue to use the resource information that took effect during the paging process.

[0465] When multiple resource information is configured via messages after receiving the same CN request, the last configured resource information takes effect.

[0466] In different embodiments of this application, AIoT devices can execute responses in the Repaging process according to different rules.

[0467] For example, in some embodiments, a card reader instructs an AIoT device to perform random access via CFRA. Combined with... Figure 4 The example in the text is that after receiving message 301 (Msg1), the card reader sends message 302 (Msg2) to the AIoT device.

[0468] An AIoT device can determine whether to respond to a Repaging message if it does not receive Msg2 during the Paging process.

[0469] Understandably, when an AIoT device attempts random access via CFRA during the Paging process, the CFRA will fail if Msg2 is not received. Therefore, the AIoT device can retry the random access process within the same Paging procedure after receiving the Repaging message.

[0470] In other embodiments, the example is that the card reader instructs the AIoT device to make random access via 2-setp CBRA.

[0471] Combination Figure 5 The example in the text is that after receiving message 401 (Msg1), the card reader sends message 402 (Msg2) to the AIoT device.

[0472] In some implementations, if the contention is successful, the card reader sends an acknowledgment (ACK) message to the AIoT device via Msg2. This allows the AIoT device to determine whether to respond to the Repaging message based on the absence of Msg2.

[0473] In other implementations, if the contention is successful, the card reader sends an acknowledgment (ACK) message to the AIoT device via Msg2; if the contention fails, the card reader sends a non-acknowledgment (NACK) message to the AIoT device via Msg2. This allows the AIoT device to determine whether to respond to the repaging message based on whether it has not received Msg2 or has received a Msg2 message carrying a NACK.

[0474] In other implementations, in the event of a contention failure, the card reader sends a non-acknowledgment (NACK) message to the AIoT device via Msg2. This allows the AIoT device to determine, based on the received Msg2, whether it can respond to the repaging message.

[0475] In the example above, we take the example of an AIoT device determining whether to respond to a Repaging message based on whether it receives Msg2.

[0476] In other embodiments, the Repaging message may include access resource information. The AIoT device may also use this access resource information to determine whether to respond to the Repaging message. This access resource information may be resource information from the previous Paging process in which a device successfully accessed the network, or resource information in which a device failed to access the network, or resource information in which no device accessed the network.

[0477] For example, in the event of a contention failure, the card reader sends a non-acknowledgment (NACK) message to the AIoT device via Msg2.

[0478] In some implementations, the access resource information indicates the resource information that was successfully accessed randomly during the paging process. Thus, the AIoT device can determine its response to the repaging message based on whether it receives Msg2 carrying NACK information, or whether the resources it uses are not included in the resource information carried by the access resource information.

[0479] In other implementations, the access resource information indicates the resources for which random access failed during the paging process. Thus, the AIoT device can determine its response to the repaging message based on whether it receives Msg2 carrying NACK information or whether the resources it uses are included in the access resource information.

[0480] In other embodiments, the example is that the card reader instructs the AIoT device to make random access via 3-setp CBRA.

[0481] Combination Figure 6 In the example, after receiving message 501 (Msg1), the card reader can send message 502 (Msg2) to the AIoT device. Msg1 can carry a random number corresponding to the AIoT device. If the contention is successful, Msg2 can carry the same random number as Msg1.

[0482] In this scenario, in some implementations, AIoT devices can determine to respond to the Repaging message based on the absence of Msg2.

[0483] In other implementations, such as Figure 6 As explained in the documentation, AIoT devices can send their device ID to the card reader in message 503 (Msg3). For example, the card reader sends Msg4 to the AIoT device after receiving Msg3.

[0484] In this example, if the AIoT device does not receive Msg4 after sending message 503, it can determine whether to respond to the Repaging message based on the access resource information in the Repaging message.

[0485] Based on the above explanation of the 2-setp CBRA scenario, in this example, the AIoT device can determine its response to the Repaging message based on whether it has not received Msg4, or has received Msg4 with NACK, and the resource information used by the AIoT device in the Paging process corresponds to a failed random access. Specifically, the AIoT device can determine the resource information indicating successful or failed random access in the Paging process based on the access resource information in the Repaging message.

[0486] In this way, under different RA type scenarios, AIoT devices can determine whether random access fails in the Paging process according to the above rules, and then respond to the Repaging message in the event of random access failure.

[0487] In other cases, AIoT devices may be unable or unable to determine in a timely manner whether a random access has been successful.

[0488] For example, consider a card reader instructing an AIoT device to perform random access via CFRA. In some cases, the AIoT device can execute S302 to send Msg1 to the card reader, but the card reader will not respond to Msg1. That is, the AIoT device completes the CFRA-based random access after sending Msg1. However, since the card reader does not send Msg2 to the AIoT device whether the random access is successful or not, the AIoT device cannot determine whether the random access was successful during the paging process.

[0489] For example, consider the scenario where a card reader instructs an AIoT device to perform random access via a 3-step CBRA. In some cases, the AIoT device can execute steps S502-S504, interacting with the card reader using Msg1, Msg2, and Msg3. The device ID is sent to the card reader in Msg3. The card reader does not respond to Msg3. Thus, since the card reader does not send Msg4 to the AIoT device regardless of whether the random access is successful or not, the AIoT device cannot determine whether the random access was successful during the paging process.

[0490] Correspondingly, AIoT devices can determine whether to respond to Repaging messages based on one or more of the following methods.

[0491] In some embodiments, the Repaging message includes information about resources that have experienced conflicts or have not received random access messages (such as Msg1, Msg3, etc.).

[0492] Correspondingly, upon receiving a Repaging message, the AIoT device can determine how to respond to the Repaging message based on the resources used in the previous round (i.e., in the Paging process), including those resources where conflicts occurred or random access messages (such as Msg1, Msg3, etc.) were not received.

[0493] When an AIoT device receives a Repaging message, it can determine not to respond to the Repaging message based on the resources used in the previous round (i.e., in the Paging process), excluding those resources that are conflicting or have not received random access messages (such as Msg1, Msg3, etc.).

[0494] For example, the time domain resource used by the AIoT device in the paging process corresponds to time slot 3. That is, the AIoT device initiated random access to the card reader in time slot 3 of the paging process (such as sending Msg1 in time slot 3).

[0495] If the resource in the Repaging message that has experienced a conflict or has not received a random access message includes time slot 3, the AIoT device can determine how to respond to the Repaging message based on the resources already used included in the Repaging message.

[0496] If the resources included in the Repaging message that have conflicted or have not received a random access message do not include time slot 3, the AIoT device can determine not to respond to the Repaging message based on the fact that the resources already used are not included in the Repaging message.

[0497] In other embodiments, the AIoT device can determine whether to respond to the Repaging message based on the paging ID and / or flag bits or the paging message type carried by the Repaging message.

[0498] For example, when an AIoT device receives such... Figure 13 In the case of message 132, it can be determined that the Repaging message has not been received based on the Paging ID and / or flag bits or the paging message type of message 132.

[0499] Under normal circumstances, the AIoT device can receive the paging message corresponding to message 131 and the repaging message corresponding to message 132. Thus, upon receiving message 132, the AIoT device can determine that it has already received the paging ID corresponding to the paging message carried in message 131. This allows the AIoT device to complete random access during the paging process. However, if the AIoT device does not receive the paging message, the paging ID in the repaging message of message 132 will be the first received paging ID. Therefore, random access, which cannot be performed without receiving the paging message, can be executed upon receiving the repaging message.

[0500] In some implementations, AIoT devices can determine whether to respond to a Repaging message based on whether the Paging ID of the Repaging message is being received for the first time, even if the device ID and / or group ID are not included in the Repaging message.

[0501] Correspondingly, if the Repaging message carries the device ID and / or group ID and instructs the device with the corresponding ID to respond, the AIoT device can respond to the Repaging message by including its own device ID in the Repaging message; or the AIoT device can choose not to respond to the Repaging message by not including its own device ID in the Repaging message.

[0502] When a Repaging message carries a device ID and / or group ID, and instructs the device with the corresponding ID not to respond, the AIoT device can either include its own device ID in the Repaging message and not respond to it, or exclude its own device ID from the Repaging message and respond to it.

[0503] The above Figure 13 In the example, the Repaging process is initiated after the Paging process has ended.

[0504] In some other implementations of this application, the Repaging process can also be performed within the Paging process.

[0505] For example, in some embodiments, the Repaging process can be triggered when the next round begins after one round of the Paging process has ended.

[0506] refer to Figure 14 This is a schematic diagram of an inter-device interaction process. Figure 14 In the example, AIoT devices and card readers are used via, for example... Figure 8 The example shown illustrates communication using the interactive method. Combined with... Figure 8 As explained in the example, within the same paging process, the paging message can indicate the start of paging or the start of the first round. After the first round ends, the card reader can send a paging message (or a repaging message) again to indicate the start of the second round.

[0507] like Figure 14 As shown, the solution may include:

[0508] S1401, The core network equipment sends a CN request to the card reader.

[0509] For example, the execution of S1401 can be referred to as follows: Figure 13 S1301 in the middle.

[0510] S1402, The card reader sends message 141 to the AIoT device.

[0511] For example, message 141 can correspond to, as follows: Figure 13 Message 131.

[0512] In this example, due to the use of, Figure 8 The interaction method shown may include a Paging message in message 141.

[0513] This paging message can be used to trigger the paging process or to indicate the start of a new round. For example, this paging message can indicate the start of a new round (such as round N). N is an integer greater than or equal to 1.

[0514] In this example, the format and specific configuration details for sending the Paging message can be found in the preceding text. Figure 13 The specific explanation is omitted here.

[0515] S1403, The card reader sends a time slot start message to the AIoT device.

[0516] Therefore, the card reader can instruct the AIoT device to communicate in the new round via S1402 to S1403, and the subsequent time slot start message.

[0517] Correspondingly, AIoT devices can determine whether to respond to the received Paging message. For specific implementation details, please refer to [link / reference]. Figure 13 The explanation in the document.

[0518] In this example, when the AIoT device responds to the Paging message, it can use the corresponding random access method according to the RA type configured in the card reader. When its corresponding time slot arrives, it sends Msg1 to the card reader to perform random access to the card reader.

[0519] If a round (e.g., the Nth round) ends, the card reader can execute the following S1404 at the beginning of the next round (e.g., the N+1th round) when it is determined that Repaging is required.

[0520] Combination Figure 13As explained in the example, in some implementations, the card reader can determine whether repaging is needed before the start of round N+1, based on the repaging instruction sent by the core network device. In other implementations, the card reader can determine whether repaging is needed automatically before the start of round N+1.

[0521] S1404, The card reader sends message 142 to the AIoT device.

[0522] For example, the card reader may send message 142 at the start of the next round (such as the N+1th round). Message 142 may include a Repaging message.

[0523] Understandably, in combination Figure 8 The interaction method shown illustrates that, without repaging, the card reader can send a paging message at the start of the next round to indicate that a new round of AIoT devices has begun.

[0524] In this example, if the card reader determines that there are AIoT devices that failed to access randomly in the previous round (e.g., round N), it can send a Repaging message at the beginning of the next round (e.g., round N+1) to perform repeated paging of the AIoT devices that failed to access randomly or did not respond in the previous round (e.g., round N+1).

[0525] With Figure 13 Similar to the description in the example, in this case, the content of the Repaging message can be the same as or different from the content of the Paging message. The Repaging message can carry the same Paging ID as the Paging message.

[0526] Therefore, by sending message 142, the card reader can, while triggering the N+1th paging round, instruct the AIoT devices that failed to access the network randomly in the Nth round to re-access the network randomly. Thus, during the N+1th paging round, the AIoT devices actually participating in the paging process can include both the AIoT devices configured to perform their first random access in the N+1th round and the AIoT devices that failed to access the network randomly in the Nth round.

[0527] In some embodiments, the Repaging message may include information about resources that experienced a conflict or did not receive random access messages (such as Msg1, Msg3, etc.) in the previous Paging process (e.g., the Nth round).

[0528] In other embodiments, the Repaging message may include information indicating the device ID or group ID that failed or was incomplete in the previous Paging process.

[0529] S1405, The card reader sends a time slot start message to the AIoT device.

[0530] In this way, AIoT devices configured to perform their first random access in round N+1, and AIoT devices that failed to perform random access in round N, can perform random access based on the arrival of their corresponding time slot in round N+1, according to the received Repaging message. For example, an AIoT device can arrive in its corresponding time slot in round N+1 and access the device through methods such as... Figure 4 The CFRA shown or as Figure 5 The 2-step CBRA shown or as Figure 6 The 3-step CBRA shown performs random access to the card reader. In some embodiments, the Repaging message may include RA type information, so that the AIoT device can perform the corresponding random access based on the random access type indicated by the RA type in the Repaging message. In other embodiments, the Repaging message does not include the RA type, so that the AIoT device can perform random access in the (N+1)th round based on the random access type indicated by the RA type carried in the previous round (e.g., the Nth round) Paging message or the Repaging message.

[0531] For example, a Repaging message can be used to indicate which device needs to be paged repeatedly by carrying the device ID of the device that failed or did not complete random access in the previous round (e.g., round N).

[0532] Upon receiving a Repaging message, an AIoT device can determine its response based on its own device ID, which is included in the Repaging message. Then, when its own time slot arrives, the AIoT device can perform a random access based on the RA type configured in the card reader.

[0533] For example, the Repaging message carries the device ID of a device that has successfully or completed random access in the Nth round, indicating the device that needs to be repeatedly paged.

[0534] Upon receiving a Repaging message, an AIoT device can determine its response based on whether its own device ID is included in the message. Then, when its own time slot arrives, the AIoT device can perform a random access based on the RA type configured in the card reader.

[0535] For example, Repaging messages carry information about resources that have experienced conflicts or have not received random access messages (such as Msg1, Msg3, etc.).

[0536] An AIoT device can determine how to respond to a Repaging message by including the resources used in the previous round (e.g., round N) in the Repaging message. Then, when its own time slot arrives, the AIoT device can perform a corresponding type of random access based on the RA type configured in the card reader.

[0537] For example, Repaging messages carry information about resources that have not experienced conflicts or have received random access messages (such as Msg1, Msg3, etc.).

[0538] An AIoT device can determine how to respond to a Repaging message based on the fact that the resources used in the previous round (e.g., round N) are not included in the Repaging message. Then, when its own time slot arrives, the AIoT device can perform a random access of the corresponding type based on the RA type configured in the card reader.

[0539] In some other embodiments of this application, the AIoT device may also determine whether the Paging ID carried in the Repaging message has been received when determining whether to respond to the Repaging message.

[0540] If the Paging ID has already been received, the AIoT device can determine that it has already performed random access in the corresponding round of the Paging message. Thus, the AIoT device can further determine whether to respond to the Repaging message based on the content of the Repaging message as described above.

[0541] If the Paging ID has not been received, the AIoT device may be configured to perform its first paging in round N+1, or it may have failed to receive the Paging message in round N due to a communication anomaly. In this case, the AIoT device can determine whether to respond to the Repaging message. For example, when its own time slot arrives, the AIoT device can perform a random access of the corresponding type based on the RA type configured in the card reader.

[0542] Therefore, it should be like this Figure 14 In the implementation of the scheme shown, repeated paging of AIoT devices is achieved by embedding the Repaging process into different rounds.

[0543] It should be noted that, in cases such as Figure 14 In the example, the resource configuration format in the corresponding round of Repaging is similar to that in the previous examples.

[0544] For example, the card reader can configure resource information to the AIoT device in the Paging message and / or Repaging message and / or the time slot start message.

[0545] Within the same CN request, the latest resource information received by the AIoT device can override the earlier resource configuration received. Therefore, the AIoT device can respond to the Repaging message using the updated resource configuration. Specifically, the AIoT device can identify that the Paging and Repaging messages correspond to the same CN request by carrying the same Paging ID.

[0546] For example, the card reader can configure resource information 1 to the AIoT device in message 141. The card reader can also configure resource information 2 to the AIoT device in message 142. Assuming that both resource information 1 and resource information 2 are configured with their respective time-domain information, frequency-domain information, and Q-value, the AIoT device can enable resource information 2 in a subsequent round (e.g., in round N+1). When a response to the Repaging message is required, the device can initiate random access to the card reader using this resource information 2.

[0547] The above Figure 13 In the example, the Repaging process is triggered after the Paging process has ended. Figure 14 In the example, the Repaging process is triggered after one round.

[0548] In other embodiments of this application, the Repaging process may also be triggered between time slots in a round.

[0549] For example, refer to Figure 15 This is a schematic diagram illustrating another type of device-to-device interaction process. In this example, a card reader and an AIoT device interact via, for example... Figure 7 The example shown illustrates communication using the interactive method. Combined with... Figure 7 As explained, after receiving a CN request, the card reader can send a Paging message to the AIoT device. During the Paging process, the card reader can also send a round start message to indicate to the AIoT device that a new round has begun. Within each round, the card reader can also send a time slot start message to indicate to the AIoT device that a new time slot has begun.

[0550] like Figure 15 As shown, the solution may include:

[0551] S1501, The core network equipment sends a CN request to the card reader.

[0552] For example, the execution of S1501 can be referred to as follows: Figure 13 S1301 in the text. Further details will not be provided.

[0553] S1502, The card reader sends message 151 to the AIoT device.

[0554] In this example, message 151 can correspond to, for example: Figure 13 Message 131 in the context of the Paging process. Message 151 may include a Paging message. For example, this Paging message can be used to trigger a Paging process.

[0555] In some embodiments, the Paging message may carry a Paging ID corresponding to the CN request.

[0556] S1503, The card reader sends a round start message to the AIoT device.

[0557] In this paging process, the card reader can indicate that a new paging cycle has begun for the AIoT device by sending a paging start message.

[0558] For example, after sending message 151, the card reader can send a message indicating the start of the current round. This message can indicate to the AIoT device that the Nth round has begun.

[0559] S1504, The card reader sends a time slot start message to the AIoT device.

[0560] Combination Figure 7 As explained in the documentation, in a normal Paging process, the card reader can send a message indicating the start of one or more time slots in each round.

[0561] For example, the card reader can send a message indicating the start of a time slot after sending a round start message. This time slot start message can be used to indicate the start of a new time slot for the AIoT device. In this example, the message indicating the start of a time slot in S1504 corresponds to the start of time slot 1.

[0562] In this way, the AIoT device can determine the start of time slot 1 based on the received message indicating the start of the time slot. Before receiving the message indicating the start of the next time slot, the AIoT device can determine that it is currently in time slot 1 in the time domain.

[0563] Therefore, when its own time slot is time slot 1, the AIoT device can initiate random access to the card reader through the random access method corresponding to the RA type configured on the card reader after receiving the round start message corresponding to S1503. For example, the AIoT device can send Msg1 to the card reader.

[0564] S1505, The card reader sends message 152 to the AIoT device.

[0565] In this example, the card reader can send a Repaging message between different time slots in the same round to trigger the Repaging process.

[0566] For example, message 152 may include a Repaging message. Similar to the foregoing embodiments, the content of the Repaging message may be the same as or different from the content of the Paging message.

[0567] In some embodiments, the device ID is made visible to the card reader device.

[0568] The card reader can include the device ID or group ID that was not paged in time slot 1 and / or an earlier time slot, or the device ID or group ID that failed to receive Msg1 or Msg3 in time slot 1 and / or an earlier time slot. In this way, the AIoT device can respond to the Repaging message by including its own device ID in the Repaging message upon receiving it.

[0569] For example, AIoT device 1 may choose or be configured to perform random access before time 1 of time slot 1. When time 1 arrives, the card reader can determine that AIoT device 1 has not completed random access based on the absence of Msg1 or Msg3 from AIoT device 1. Thus, within time slot 1, the card reader can send a Repaging message, which may include the device ID of AIoT device 1. Correspondingly, AIoT device 1 can receive this Repaging message within time slot 1 and, based on its own device ID carried in the Repaging message, re-initiate random access with the card reader within time slot 1. For example, after receiving the Repaging message within time slot 1, AIoT device 1 can send Msg1 to the card reader again.

[0570] In other embodiments, the device ID is not visible to the card reader as an example.

[0571] The card reader can carry information about resources that experienced conflicts or did not receive random access messages (such as Msg1, Msg3, etc.) in time slot 1 and / or earlier time slots in the Repaging message. In this way, when the AIoT device receives the Repaging message, it can respond to the Repaging message by including the resource configuration used in its own initiated random access procedure in Repaging message 1.

[0572] For example, a Repaging message can carry frequency domain information indicating a collision or the absence of a random access message (such as Msg1, Msg3, etc.). This Repaging message is sent within time slot 1.

[0573] Correspondingly, if the frequency domain information used in the random access procedure initiated by the AIoT device itself is the same as the frequency domain information indicated in the Repaging message, and the AIoT device's own time slot is time slot 1, then the AIoT device can respond to the Repaging message within time slot 1.

[0574] If the frequency domain information used in the random access procedure initiated by the AIoT device itself is different from the frequency domain information indicated in the Repaging message, and / or the AIoT device's own time slot is not time slot 1, then the AIoT device can respond to the Repaging message within time slot 1. If the Repaging message carries a group ID, then whether to respond can also be determined by checking if it is the same as the group ID.

[0575] In conjunction with the foregoing description, in some embodiments, the card reader may also carry a device ID or group ID in the Repaging message that does not require a response to the Repaging message. In other embodiments, the card reader may also carry information about resources that have not experienced conflicts or have received random access messages in the Repaging message. The response logic of the AIoT device is the same as the corresponding examples described above, and will not be repeated here.

[0576] In this way, within this time slot 1, the card reader can repeatedly paging the AIoT device that has failed to access the system randomly by sending a Repaging message.

[0577] It should be noted that in this example, the Repaging message is sent after the message at the beginning of time slot 1. In other embodiments, the Repaging message can also be used to indicate to the AIoT device that a new time slot has begun. In this case, at the beginning of time slot 1, the card reader device can skip S1503 and directly execute S1504. Correspondingly, the AIoT device can determine whether to respond to the Repaging message based on the received Repaging message, on the one hand, that a new time slot has begun; and on the other hand, determine whether to respond to the Repaging message according to the above rules.

[0578] S1506, The card reader sends a time slot start message to the AIoT device.

[0579] The time slot start message in S1506 can indicate that a new time slot has started for the AIoT device. For example, a card reader can use the time slot start message in S1506 to indicate that time slot 2 of the AIoT device has started, which means that time slot 1 has ended.

[0580] In some embodiments, similar to the example in S1505, the card reader can instruct the corresponding AIoT device to perform repeated paging by sending a Repaging message in this time slot 2.

[0581] Therefore, through this Figure 15 As shown in the example scheme, the card reader can instruct the AIoT device to perform repeated paging via Repaging messages within one or more time slots.

[0582] The above Figure 15 The section describes the scheme for sending Repaging messages within time slots, using, for example... Figure 7 The example shown is an example of inter-device interaction. In other embodiments, refer to... Figure 16 , as Figure 8 Taking the device-to-device interaction method shown as an example, this paper explains the implementation of the scheme for sending Repaging messages within a time slot.

[0583] like Figure 16 As shown, the solution may include:

[0584] S1601, The core network equipment sends a CN request to the card reader.

[0585] For example, step S1601 can correspond to, as follows: Figure 15 S1501 in the context of core network devices. Core network devices can instruct card readers to perform inventory processing or transmit DL commands for AIoT devices via CNrequest.

[0586] S1602, The card reader sends message 161 to the AIoT device.

[0587] For example, the execution of step S1602 can be referred to as follows: Figure 15 S1502 in the middle.

[0588] In this example, message 161 can correspond to message 151 in the previous example. Message 161 may include a Paging message. In some embodiments, the Paging message may include the Paging ID corresponding to the CN request.

[0589] It should be noted that, in combination Figure 8 The explanation in the text is as follows: Figure 16 In the example, message 161 carrying the Paging message can also be used to indicate the start of a new round for AIoT devices. For example, message 161 can be used to indicate the start of the Nth round.

[0590] S1603, The card reader sends a time slot start message to the AIoT device.

[0591] For example, the card reader can instruct the AIoT device to start time slot 1 by sending a time slot start message in S1603. Correspondingly, the AIoT device can determine that it is in time slot 1 in the time domain after receiving the time slot start message and before receiving the next time slot start message.

[0592] Within this time slot 1, based on the resource information configured by the card reader, an AIoT device whose own time slot is time slot 1 can attempt to initiate random access to the card reader corresponding to the configured RA type.

[0593] S1604, The card reader sends message 162 to the AIoT device.

[0594] In this example, message 162 can be used to trigger the Repaging process within time slot 1.

[0595] For example, in some embodiments, the Repaging message may include the device ID or group ID that did not respond in time slot 1 and / or a prior time slot, and / or the device ID or group ID that failed to receive Msg1 and / or Msg3 in time slot 1 and / or a prior time slot.

[0596] Correspondingly, when an AIoT device receives a Repaging message, it can respond to the Repaging message by including its own device ID in the Repaging message.

[0597] When an AIoT device receives a Repaging message, it can choose not to respond to the Repaging message if its own device ID is not included in the message.

[0598] In other embodiments, the Repaging message may include the device ID or group ID that has responded in time slot 1 and / or a prior time slot, and / or the device ID or group ID that successfully received Msg1 and / or Msg3 in time slot 1 and / or a prior time slot.

[0599] Correspondingly, when an AIoT device receives a Repaging message, it can include its own device ID in the Repaging message and not respond to the Repaging message.

[0600] When an AIoT device receives a Repaging message, it can respond to the Repaging message by specifying that its own device ID is not included in the Repaging message.

[0601] In other embodiments, the Repaging message may include information about resources that have experienced conflicts or have not received random access messages (such as Msg1, Msg3, etc.) in slot 1 and / or earlier slots.

[0602] Correspondingly, when an AIoT device receives a Repaging message, it can include the resource configuration used in the random access process it has initiated in the Repaging message in its response.

[0603] When an AIoT device receives a Repaging message, it may choose not to respond to the Repaging message, depending on the resource configuration used in its own initiated random access process, which is not included in the Repaging message.

[0604] For example, the Repaging message includes frequency domain information 1, which indicates that a collision occurred in frequency domain information 1 or no random access message was received.

[0605] In this way, if the AIoT device's corresponding time slot is time slot 1 and the random access procedure it has already initiated uses the frequency point corresponding to frequency domain information 1 (such as sending Msg1 through the frequency point corresponding to frequency domain information 1), it can respond to the Repaging message. For example, within time slot 1, the AIoT device can initiate a random access procedure (such as sending Msg1) again to the card reader according to the configured RA type.

[0606] Correspondingly, if the AIoT device's corresponding time slot is not time slot 1, or if the random access procedure that has been initiated does not use the frequency point corresponding to frequency domain information 1, it may not respond to the Repaging message.

[0607] In other embodiments, the Repaging message may include information about resources in slot 1 and / or earlier slots that have not experienced a conflict or have received random access messages (such as Msg1, Msg3, etc.).

[0608] Correspondingly, when an AIoT device receives a Repaging message, it can respond to the Repaging message by excluding the resource configuration used in the random access process it has already initiated from the Repaging message.

[0609] When an AIoT device receives a Repaging message, it can include the resource configuration used in its own initiated random access process in the Repaging message without responding to it.

[0610] S1605, The card reader sends a time slot start message to the AIoT device.

[0611] How Figure 16 In the example solution shown, the card reader and the AIoT device communicate via, for example... Figure 8 Taking the communication method shown as an example, the Repaging triggering mechanism within a time slot is illustrated. Figure 16 In the scenario shown, each step can be respectively mapped to, for example: Figure 15 The specific implementation steps can be referenced from each other.

[0612] In addition, this is how Figure 15 And such as Figure 16 The resource configuration used in the Paging and Repaging processes shown can also be the same as in the examples above.

[0613] For example, in the case of Figure 15 or Figure 16 In this solution, the card reader can configure resource information to the AIoT device via Paging messages and / or Repaging messages and / or timeslot start messages. If the resource information is updated, the updated resource information takes effect, and the AIoT device can use the updated resource information to communicate with the card reader (e.g., by sending Msg1).

[0614] Therefore, this application illustrates the access process of an AIoT device (such as a second device) to a card reader (such as a first device) based on initial messages and repeated messages through the above embodiments.

[0615] In the implementation of the solution provided in the above embodiments, after receiving a Repaging message, the AIoT device can determine how to respond to the Repaging message according to preset rules. These preset rules can correspond to situations where the device has not been connected or has not completed the connection process during the paging phase.

[0616] The specific methods for determining whether an connection has not been established or has not been completed can be as follows: the AIoT device can determine this based on whether the connection has been successfully established; the AIoT device can determine this based on the Reader's instructions; or the AIoT device can determine this based on whether the Msg message in the Paging process has completed the interaction or whether the Msg message indicates NACK.

[0617] In other embodiments, the device type of the AIoT device is carried in the Paging message as an example. The AIoT device can also determine its response to the Repaging message based on whether its device type is included in the Paging message and / or whether the above-mentioned preset rules are met.

[0618] In other embodiments, the AIoT device may also flexibly determine whether to respond to the Repaging message based on one or more of the following: the first device's identification information, the information indicating that the device that failed to access should receive the paging message, and the information indicating whether there is a duplicate message.

[0619] In addition, depending on when the Repaging message is sent, AIoT devices can flexibly adjust the timing of actions such as sleep, wake-up, and charging.

[0620] Take the response of an AIoT device to a Repaging message as an example.

[0621] For example, when a card reader sends a Repaging message within a time slot, an AIoT device can, without going to sleep or immediately starting to charge, wait to receive the Repaging message, even if it is not connected or has not completed the connection process.

[0622] For example, when a card reader sends a Repaging message at the start of a new cycle, an AIoT device can either not sleep or immediately start charging while waiting to receive the Repaging message, even if it is not connected or has not completed the connection process; or, an AIoT device can go to sleep if it is not connected or has not completed the connection process, and wake up before the start of the next cycle in order to receive the Repaging message.

[0623] For example, after the card reader finishes the Paging process, it sends a Repaging message. The AIoT device can either not go to sleep or start charging immediately while waiting to receive the Repaging message if it is not connected or has not completed the connection process; or, the AIoT device can go to sleep if it is not connected or has not completed the connection process, and wake up before the Paging process ends in order to receive the Repaging message.

[0624] It is understood that the electronic device provided in this application embodiment includes hardware structures and / or software modules corresponding to perform each function in order to achieve the above-mentioned functions. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the embodiments of this application.

[0625] This application embodiment can divide the above-described electronic device into functional modules based on the method example described above. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0626] For example, consider a card reader and an AIoT device that are configured with the same protocol layer division.

[0627] In some embodiments, a Media Access Control (MAC) layer may be provided within the device.

[0628] The card reader can configure Paging and / or Repaging messages to a format corresponding to a MAC PDU or MAC CE. In some embodiments, the Paging ID and / or the identifier bits used to distinguish between Paging and Repaging messages can be configured in the sub-header of the MAC PDU or MAC CE (MAC Control Element). This facilitates AIoT devices to quickly and efficiently identify Paging or Repaging messages.

[0629] In other embodiments, an AIoT access layer (ASlayer) may also be provided on the MAC layer.

[0630] In this way, the card reader can configure the Paging message and / or Repaging message to the format indicated by the control data packet (AS CE) corresponding to the AS layer. In some implementations, the Paging ID and / or the field used to distinguish between the Paging message and the Repaging message carried by the Paging message and / or Repaging message can be configured in the subheader of the AS CE.

[0631] The integrated modules described above can be implemented in hardware or as software functional modules. It should be noted that the module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0632] refer to Figure 17 This application also provides a schematic diagram of a chip system 1700. The chip system 1700 may include a processor 1701 and a communication interface 1702, used to support related devices (such as card readers or AIoT devices) in implementing the functions involved in the above embodiments. In one possible design, the chip system also includes a memory for storing necessary program instructions and data for the electronic device. The chip system may be composed of chips or may include chips and other discrete components. It should be noted that in some implementations of this application, the communication interface 1702 may also be referred to as an interface circuit.

[0633] It should be noted that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0634] This application also provides a network device. In some embodiments, the network device can be a card reader as described in the above embodiments. This network device can be used to implement the technical solutions corresponding to the card reader in any of the above method embodiments.

[0635] This application also provides a device product. In some embodiments, the device product can be an AIoT device as described in the above embodiments. The device product can be used to implement the technical solution corresponding to the AIoT device in any of the above method embodiments.

[0636] This application also provides a computer-readable storage medium storing a computer program thereon. When executed by a computer, the computer program implements the method flows related to the reader and / or device in any of the above method embodiments. Specifically, the computer can be the card reader device or an AIoT device.

[0637] This application also provides a computer program or a computer program product including a computer program, which, when executed on a computer, will cause the computer to implement the method flows related to the reader and / or device in any of the above method embodiments. Specifically, the computer can be the card reader device or the AIoT device described above.

[0638] It should be noted that the functions, actions, operations, or steps in the above embodiments can be implemented, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, they can be implemented, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or include one or more data storage devices such as servers and data centers that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks (SSDs)).

[0639] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method is applied to a first device, and the method includes: Send a first message, which is used by the second device to initiate random access to the first device; A second message is sent, which is used by the second device to initiate random access to the first device; the first message and the second message are associated with a first request, which instructs the first device to perform AIoT communication with the second device.

2. The method according to claim 1, characterized in that, The method further includes: Receive a first request, which carries a first process ID.

3. The method according to claim 1 or 2, characterized in that, The first message and / or the second message includes at least one of the following: Shared and / or dedicated resource information, resource allocation type, downlink command indication information, second process ID, information indicating whether to receive or ignore a paging message, identification information of the first device, information indicating whether a device that failed to access the paging message received a paging message, information indicating whether there is a duplicate message, and type information of the second device; The second process ID corresponds to the first request.

4. The method according to any one of claims 1-3, characterized in that, The first message and / or the second message are configured with a first flag bit, which is used to indicate whether the message carrying the first flag bit is an initial message or a repeat message.

5. The method according to claim 4, characterized in that, The first flag bit of the first message indicates that the first message is the initial message; The first flag bit of the second message indicates that the second message is the repeat message.

6. The method according to any one of claims 1-5, characterized in that, The first message is of type one, and the second message is of type two; The first type corresponds to the initial message, and the second type corresponds to the repeat message.

7. The method according to claim 6, characterized in that, Both the first message and the second message are configured with identification information. The identification information of the first message indicates that the first message is of the first type, and the identification information of the second message indicates that the second message is of the second type.

8. The method according to any one of claims 4-7, characterized in that, The header of the first message data packet or the control information includes the second process ID, the first flag bit of the first message, or the identification information of the first message; and / or, The second message's data packet header or control information includes the second process ID, the second message's first flag bit, or the second message's identification information.

9. The method according to any one of claims 1-8, characterized in that, The second message includes the device ID or group ID corresponding to at least one device that has not connected or has not completed connection, or... The second message includes resource information that has not been accessed or has not been accessed, the resource information that has not been accessed or has not been accessed indicates conflicting resource information and / or resource information that has failed to receive a response and / or resource information that has not received a response; the resource information includes at least one of the following: round information, time domain information, frequency domain information, Q value.

10. The method according to any one of claims 1-9, characterized in that, The second message includes at least one device ID or group ID corresponding to a device that has completed access, or... The second message includes resource information indicating that access has been completed, and the resource information indicating that a response resource information has been received; the resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value.

11. The method according to any one of claims 1-10, characterized in that, After sending the first message, the method further includes: The second message is sent within the first duration; or, the second message is sent after the first duration. The first duration is a preset duration, and / or the first duration is the duration from the start of the first time slot to the end of the first time slot.

12. The method according to claim 11, characterized in that, After sending the first message, the method further includes: Send a first time slot start message, which indicates the start of the first time slot, and / or, After sending the first message, the method further includes: Send a second time slot start message, which is used to indicate the end of the first time slot.

13. The method according to claim 11 or 12, characterized in that, The first message is used to indicate the start of a new round.

14. The method according to claim 13, characterized in that, After sending the first message, the method further includes: Send a third message, which indicates the start of a new round; The third message includes the first message, or the third message includes the second message.

15. The method according to claim 11 or 12, characterized in that, After sending the first message, the method further includes: Send a first round start message, which indicates the start of the first round.

16. The method according to any one of claims 11-15, characterized in that, Sending the second message includes: The second message is sent after all rounds and / or time slots corresponding to the first message have ended.

17. The method according to any one of claims 1-16, characterized in that, The method further includes: Receive Msg1, wherein Msg1 includes at least one of the following: upper-layer data, second process ID, first random ID; and / or, Receive Msg3, wherein Msg3 includes at least one of the following: upper-layer data, process ID; The upper-layer data includes the device ID of the second device, the second process ID corresponding to the first request, and the first random ID corresponding to the second device.

18. The method according to claim 17, characterized in that, The first message and / or the second message includes a resource allocation type; The resource allocation type indicates that the second device accesses the first device via a non-contention-based random access procedure (CFRA); or... The resource allocation type indicates that the second device accesses the first device through a two-step contention-based random access procedure (CBRA); or... The resource allocation type indicates that the second device accesses the first device through a three-step contention-based random access procedure (CBRA).

19. The method according to claim 18, characterized in that, The second message includes the resource allocation type, which indicates that the second device accesses the first device via CFRA; After sending the second message, the method further includes: Receive the Msg1 of the CFRA, wherein the Msg1 of the CFRA includes at least one of the following: the upper-layer data, the second process ID; or, The second message includes the resource allocation type, which instructs the second device to access the first device via 2-step CBRA; After sending the second message, the method further includes: The Msg1 of the 2-step CBRA is received, and the Msg1 of the 2-step CBRA includes at least one of the following: the upper-layer data, the second process ID; or, The second message includes the resource allocation type, which instructs the second device to access the first device via 3-step CBRA; After sending the second message, the method further includes: The Msg1 of the 3-step CBRA is received, wherein the Msg1 of the 3-step CBRA includes at least one of the following: the first random ID, the second process ID; Send Msg2 of the 3-step CBRA, wherein Msg2 of the 3-step CBRA includes a second random ID.

20. The method according to any one of claims 1-19, characterized in that, The method further includes: Resource information is configured to the second device via an initial message, and / or a repeat message, and / or a round start message, and / or a time slot start message, wherein the resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value; In the case of configuring resource information to the second device multiple times, the updated resource information is used for the second device to randomly access the first device.

21. The method according to claim 20, characterized in that, The method further includes: Configure the second device with first resource information and second resource information; When both the first resource information and the second resource information include the configuration corresponding to the first resource type, the first resource set is used for random access from the second device to the first device; The first resource set includes: the second resource information, and resource configurations in the first resource information that are different from the first resource type; or, When the resource types configured in the first resource information and the second resource information are different, the second resource set is used for random access from the second device to the first device; The second resource set includes: the first resource information and the second resource information; The first resource type includes one or more of the following: round information, time domain information, frequency domain information, and Q value.

22. The method according to claim 21, characterized in that, The step of configuring the first resource information to the second device includes: The first resource information is configured to the second device via the first message, and / or the round start message, and / or the time slot start message; The step of configuring the second resource information to the second device includes: The second resource information is configured to the second device via a round start message, and / or a time slot start message, and / or the second message.

23. A communication method, characterized in that, The method is applied to a second device, and the method includes: Receive a second message, which is used by the second device to initiate random access to the first device in order to conduct environmental Internet of Things (AIoT) communication with the first device. A fourth message is sent, which is used to initiate random access to the second device.

24. The method according to claim 23, characterized in that, The method further includes the following steps prior to receiving the second message: Receive a first message, which is used by the second device to initiate random access to the first device; the first message and the second message are associated with a first request, which instructs the first device to perform AIoT communication with the second device. Send a first random access message, which is used to perform random access to the first device.

25. The method according to claim 24, characterized in that, The first message and / or the second message includes at least one of the following: Shared and / or dedicated resource information, resource allocation type, downlink command indication information, second process ID, information indicating whether to receive a paging or ignore a paging, identification information of the first device, information indicating that the device that failed to access the device should receive a paging; Information indicating whether duplicate messages are supported; information indicating the end of the process corresponding to the first message; information indicating whether duplicate messages exist; and the type information of the second device. The second process ID corresponds to the first request.

26. The method according to claim 24 or 25, characterized in that, The first message and / or the second message are configured with a first flag bit, which is used to indicate whether the message carrying the first flag bit is an initial message or a repeat message.

27. The method according to claim 26, characterized in that, The first flag bit of the first message indicates that the first message is the initial message; The first flag bit of the second message indicates that the second message is a duplicate message.

28. The method according to claim 24 or 25, characterized in that, The first message is of type one, and the second message is of type two; The first type corresponds to the initial message, and the second type corresponds to the repeat message.

29. The method according to claim 28, characterized in that, Both the first message and the second message are configured with identification information. The identification information of the first message indicates that the first message is of the first type, and the identification information of the second message indicates that the second message is of the second type.

30. The method according to any one of claims 26-29, characterized in that, The header of the first message data packet or the control information includes the second process ID, the first flag bit of the first message, or the identification information of the first message; and / or, The second message's data packet header or control information includes the second process ID, the second message's first flag bit, or the second message's identification information.

31. The method according to any one of claims 24-30, characterized in that, After receiving the second message, the method further includes: Based on the second message, it is determined that a response should be made to the first device; Sending the fourth message includes: If it is determined that a response to the first device will be made, the fourth message is sent.

32. The method according to claim 31, characterized in that, If the second process ID included in the second message has not been received before, and / or the second message is an initial message, determine to respond to the second message; or... If the second process ID included in the second message has not been received before, and / or the second message is a duplicate message, determine to respond to the second message; or, If the second process ID included in the second message has been received, and / or the second message is a duplicate message, a response to the second message is determined according to a preset rule.

33. The method according to claim 32, characterized in that, The preset rules include: It was determined that random access to the first device was either not initiated or not completed.

34. The method according to claim 33, characterized in that, The failure to connect or complete the random access to the first device includes: Sending Msg1 and / or Msg3 fails, or Msg1 and / or Msg3 is not sent, or the first message is not received; And / or, Failed to receive Msg2, or Msg2 was not received; And / or, The reception of Msg4 failed, or the Msg4 was not received, or a Msg4 containing an unacknowledged message was received.

35. The method according to claim 33 or 34, characterized in that, Before receiving the second message, the method further includes: Send Msg1, wherein Msg1 includes at least one of the following: upper-layer data, second process ID, first random ID; and / or, Send Msg3, wherein Msg3 includes at least one of the following: upper-layer data, process ID; The upper-layer data includes the device ID of the second device, the second process ID corresponding to the first request, and the first random ID corresponding to the second device.

36. The method according to claim 35, characterized in that, The first message and / or the second message includes a resource allocation type; The resource allocation type indicates that the second device accesses the first device via a non-contention-based random access procedure (CFRA); or... The resource allocation type indicates that the second device accesses the first device through a two-step contention-based random access procedure (CBRA); or... The resource allocation type indicates that the second device accesses the first device through a three-step contention-based random access procedure (CBRA).

37. The method according to any one of claims 33-36, characterized in that, The second message includes the device ID corresponding to at least one device that has not connected or has not completed the connection process. Random access to the first device was either unsuccessful or incomplete, including: The device ID of the second device is included in the second message; or, The second message includes the device ID corresponding to at least one device that has completed the connection. Random access to the first device was either unsuccessful or incomplete, including: The device ID of the second device is not included in the second message; or, The second message includes a first group of IDs corresponding to at least one device that has not been connected or has not completed the connection. The first group of IDs corresponds to at least one device ID. Among the at least one device IDs corresponding to the first group of IDs, at least one device ID corresponds to a device that has not been connected or has not completed the connection. Random access to the first device was either unsuccessful or incomplete, including: The device ID of the second device is included in at least one device ID corresponding to the first group of IDs; or, The second message includes at least one second set of IDs, which includes the device ID of at least one device that has completed access. Random access to the first device was either unsuccessful or incomplete, including: The device ID of the second device is not included in the device IDs corresponding to the second group of IDs; or, The second message includes resource information that has not been accessed or has not been accessed; the resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value; Random access to the first device was either unsuccessful or incomplete, including: The resource information used by the second device when it last connected to the first device is included in the second message; or, The second message includes resource information that has been successfully accessed; Random access to the first device was either unsuccessful or incomplete, including: The resource information used by the second device when it last accessed the first device is not included in the second message.

38. The method according to any one of claims 24-37, characterized in that, After receiving the first message, the method further includes: The second message is received within the first duration; or, the second message is received after the first duration. The first duration is a preset duration, and / or the first duration is the duration from the start of the first time slot to the end of the first time slot.

39. The method according to claim 38, characterized in that, After receiving the first message, the method further includes: Receive a first time slot start message, which indicates the start of the first time slot.

40. The method according to claim 38 or 39, characterized in that, The first message is used to indicate the start of a new round.

41. The method according to claim 39, characterized in that, After receiving the first message, the method further includes: Receive a third message, which indicates the start of a new round; The third message includes the first message, or the third message includes the second message.

42. The method according to any one of claims 38-41, characterized in that, After receiving the first message, the method further includes: Receive the first round start message, which indicates the start of the first round.

43. The method according to any one of claims 38-42, characterized in that, The receipt of the second message includes: The second message is received after all rounds and / or time slots corresponding to the first message have ended.

44. The method according to any one of claims 24-43, characterized in that, The method further includes: Resource information is configured to the second device via an initial message, and / or a repeat message, and / or a round start message, and / or a time slot start message, wherein the resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value; When resource information is configured to the second device multiple times, the updated resource information is used for the second device to randomly access the first device.

45. The method according to claim 44, characterized in that, The method further includes: Configure the second device with first resource information and second resource information; the time of configuring the second resource information is later than the time of configuring the first resource information. When both the first resource information and the second resource information include the configuration corresponding to the first resource type, the first resource set is used for random access from the second device to the first device; The first resource set includes: the second resource information, and resource configurations in the first resource information that are different from the first resource type; or, When the resource types configured in the first resource information and the second resource information are different, the second resource set is used for random access from the second device to the first device; The second resource set includes: the first resource information and the second resource information; The first resource type includes one or more of the following: round information, time domain information, frequency domain information, and Q value.

46. ​​The method according to claim 45, characterized in that, The step of configuring the first resource information to the second device includes: The first resource information is configured to the second device via the first message, and / or the round start message, and / or the time slot start message; The step of configuring the second resource information to the second device includes: The second resource information is configured to the second device via a round start message, and / or a time slot start message, and / or the second message.

47. A communication device, characterized in that, The communication device is used to implement the method as described in any one of claims 1-22; or, the communication device is used to implement the method as described in any one of claims 23-46.

48. A communication system, characterized in that, The communication system includes a first device and a second device, the first device being used to perform the method as described in any one of claims 1-22, and the second device being used to perform the method as described in any one of claims 23-46.

Images