Communication method, device, and system

Abstract

Embodiments of the present application relate to the technical field of communications, and provide a communication method, a device, and a system. The method provides a repeated paging mechanism between a card reader device and an ambient Internet of Things (AIoT) device, so that the AIoT device can re-attempt to perform random access with the card reader device by means of repeated paging. The solution may comprise: sending a first message, wherein the first message is used for a second device to initiate random access to a first device; and sending a second message, wherein the second message is used for the second device to initiate random access to the first device. The first message and the second message are associated with a first request, wherein the first request instructs the first device to perform AIoT communication on the second device.

Description

Communication method, device and system

[0001] The present application claims priority to the Chinese patent application No. 202411378332.3, filed on September 29, 2024, and entitled "A communication method, device and system", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] Embodiments of the present application relate to the field of communication technology, and in particular to a communication method, device and system. BACKGROUND

[0003] Currently, in the communication process based on Ambient Internet of Things (AIoT), a card reading device can page one or more AIoT devices through a paging message. Correspondingly, the AIoT devices can attempt to perform random access to the card reading device according to the paging message, so as to establish an AIoT communication connection between the devices.

[0004] In some cases, there is a situation that the AIoT devices fail to perform random access. As a result, the AIoT devices cannot normally perform data transmission with the card reading device. SUMMARY

[0005] The present application provides a communication method, device and system, which provides a repeated paging mechanism for the card reading device and the AIoT device, so that the AIoT device can attempt to perform random access to the card reading device again through repeated paging.

[0006] To achieve the above technical purposes, the present application adopts the following technical solutions:

[0007] In a first aspect, a communication method is provided, the method being applied to a first device, and the method comprising: sending a first message, the first message being used for a second device to initiate random access to the first device; and sending a second message, the second message being used for 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 that the first device performs Ambient Internet of Things (AIoT) communication with the second device.

[0008] For example, the first message can include a Paging message or an initial message. The second message can be a Repaging message. The first device can be a card reading device. For example, the card reading device can be a user equipment (UE) or a base station, etc.

[0009] In some implementations of the example, the first message and / or the second message can be a message triggering random access. In other implementations, the first message and / or the second message can have other contents different from directly triggering random access. Correspondingly, the second device can determine whether to trigger random access according to the first message and / or the second message.

[0010] For example, the second device can determine whether to initiate random access according to the first message and / or device identification information of the second device (such as a card reading device ID indicating the first device carried by the first message and / or the second message), or flow identification information (such as a flow ID) carried by the first message and / or the second message.

[0011] Based on the scheme, the first device can indicate the second device (such as an AIoT device) to perform random access through the first message. Correspondingly, some second devices can successfully establish an AIoT communication connection with the first device through the random access based on the first message. However, some other second devices can not access (such as not receive the first message) or not complete access (such as receiving the first message and then performing random access, but the random access fails) in the Paging flow corresponding to the first message. In this way, the first device can indicate the first device to initiate random access again through the second message. Thus, the second device that does not establish an AIoT connection with the card reading device in the Paging flow can initiate random access to the first device again according to the second message. In this way, through the configuration of the second device, the second device that does not access or does not complete access in the Paging flow is provided with an opportunity to initiate random access again, thereby improving the possibility of successfully establishing an AIoT communication connection between the second device and the first device.

[0012] In some possible designs, the method further includes receiving a first request carrying a first flow ID. For example, the first request can be a CN request from a core network device. In some embodiments, the first request can include an inventory instruction and / or a downlink command (DL command). The first flow ID can be a CN request ID of the CN request.

[0013] 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 flow ID, information indicating receiving paging or ignoring paging, identification information of the first device, information indicating that the device receiving paging has failed to access, type information of the second device, and information indicating whether there is a duplicate message. The second flow ID corresponds to the first request.

[0014] In the present application, the second procedure ID sent by the second device can be the same as the first procedure ID. Alternatively, the second procedure ID can have a mapping relationship with the first procedure ID, so that the same CN request can be associated with different Paging (or Repaging) messages through the second procedure ID.

[0015] In the specific implementation of the present application, not accessing can include that the first message has been received, but due to power or other reasons, access is not initiated in the procedure (such as the Paging procedure) corresponding to the first message. In this way, taking the first message as an example, the first message includes information indicating that there is a repeated message. The second device can receive the first message, and in the case of sufficient power, it does not enter sleep and waits for the second message to arrive. Further, the second device can perform Repaging according to the second message. Alternatively, in the case of insufficient power of the second device, it can actively or passively charge, or first enter sleep and wake up before the second message arrives, so as to receive the second message and perform Repaging.

[0016] In some possible designs, the first message and / or the second message is configured with a first flag bit, and the first flag bit is used to indicate that the message carrying the first flag bit is an initial message or a repeated message.

[0017] In the present application, the initial message can include the message corresponding to the first request sent by the first device for the first time after receiving the first request message (such as CN request). For example, the initial message can include the Paging message.

[0018] Correspondingly, the repeated message can include the message corresponding to the first request sent by the first device for the second time or one time after the second time after receiving the first request message (such as CN request). For example, the repeated message can include the Repaging message.

[0019] 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 repeated message.

[0020] For example, the first flag bit of the first message is configured as a first value, and the first flag bit being the first value indicates that the first message is an initial message. The first flag bit of the second message is configured as a second value, and the first flag bit being the second value indicates that the second message is a repeated message.

[0021] In other possible designs, the first message can also be a repeated message.

[0022] In this way, by setting the flag bit, the initial message and the repeated message can be distinguished.

[0023] In some possible design, the first message is of a first type, and the second message is of a second type. The first type corresponds to an initial message, and the second type corresponds to a repeated message.

[0024] In this way, the initial message and the repeated message can be distinguished by configuring the initial message and the repeated message as different types.

[0025] In some possible design, the first message and the second message are both 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.

[0026] In this way, the indication of the initial message and the repeated message can be implemented by corresponding configuration in the identification information.

[0027] In some possible design, the second flow ID, the first flag of the first message, or the identification information of the first message is included in a packet subheader or control information of the first message. And / or, the second flow ID, the first flag of the second message, or the identification information of the second message is included in a packet subheader or control information of the second message.

[0028] In this way, the second flow ID and / or the identification information and / or the flag can be configured in the subheader or the control information, so that the second device can know whether the currently received message is an initial message or a repeated message, and can also know whether the flow ID corresponding to the message has been received, without parsing the data part.

[0029] It can be understood that, when the second flow ID has been received, and the identification information and the flag indicate that the message is a repeated message, the second device can determine whether to respond to the repeated message. When the second flow ID has not been received, or the identification information and the flag indicate that the message is an initial message, the second device can directly respond to the message without additional determination. Through this mechanism, the first device can configure the second flow ID and the identification information and the flag according to actual needs, so as to control the second device to respond accordingly.

[0030] The following provides several examples of the content of the second message.

[0031] In some possible designs, the second message includes at least one of a device ID or a group ID corresponding to a device that has not accessed or has not completed accessing, or the second message includes resource information of a device that has not accessed or has not completed accessing, the resource information of the device that has not accessed or has not completed accessing indicating resource information of a conflict and / or resource information of a failed response reception and / or resource information of which no response is received. The resource information includes at least one of round information, time domain information, frequency domain information, and a Q value.

[0032] The round information can indicate a round in which a response is made. The time domain information can indicate a time slot in which a response is made. The frequency domain information can indicate a frequency, a frequency point, a channel, or the like, in which a response is made. The Q value can be used to determine the time domain information, the frequency domain information, and / or the round information.

[0033] In some possible designs, the second message includes at least one of a device ID or a group ID corresponding to a device that has completed accessing, or the second message includes resource information of a device that has completed accessing, the resource information of the device that has completed accessing indicating resource information of which a response is received. The resource information includes at least one of round information, time domain information, frequency domain information, and a Q value.

[0034] Based on this example, the first device can control, through the second message, the second device to determine, based on the device ID or the group ID, whether to make a response to a repeated message. Alternatively, the first device can control, through the second message, the second device to determine, based on the resource information, whether to make a response to a repeated message.

[0035] In some possible designs, after the first message is sent, the method further includes: sending the second message within a first time length. Alternatively, the second message is sent after the first time length. The first time length is a preset time length, and / or the first time length is a time length from the beginning of a first time slot to the end of the first time slot. For example, the first time length can be a length of one time slot. In this way, the first device can initiate a Repaging process between time slots. In some implementations, the second device can start charging after receiving the first message. A charging time length of the second device is related to a time when the first device sends the second message. For example, if the first device sends the second message within the first time length, the charging time length of the second device is less than the first time length. For another example, if the first device sends the second message after the first time length, the charging time length of the second device can be greater than or equal to the first time length.

[0036] In some possible designs, after the first message is sent, the method further includes: sending a first time slot start message, the first time slot start message being used to indicate the beginning of the first time slot.

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

[0038] In some possible designs, the first message is used to indicate the start of a new round. In this example, the first device can not need to send a message to indicate the start of a new round separately from the first message (e.g., the paging message).

[0039] In some possible designs, after sending the first message, the method further includes sending a third message, the third message being used to indicate the start of a new round. The third message includes the first message, or the third message includes 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 can be a paging message corresponding to the first message. That is, in the procedure of the same CN request, the first device can send multiple paging messages to indicate the start of a new round for the second device. Alternatively, the third message can be a repaging message corresponding to the second message. When the third message is a repaging message, the first device can trigger a repaging procedure at the end of a round and / or the start of a new round in one paging procedure.

[0040] In some possible designs, after sending the first message, the method further includes sending a first round start message, the first round start message being used 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.

[0041] In some possible designs, the sending the second message includes sending the second message after the end of all rounds and / or time slots corresponding to the first message. In this implementation, sending the second message after the end of all rounds corresponds to sending the second message after the end of a paging procedure, so that the second device performs repeated paging. Sending the second message after the end of all time slots corresponds to sending the second message after the end of a round, or after the end of a paging procedure in an interaction mode without a round start message, so that the second device performs repeated paging.

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

[0043] In different implementations, the random access procedure can be different. Examples are provided below respectively.

[0044] In some possible designs, the first message and / or the second message includes a resource allocation type. When the resource allocation type is a first type, the second device is instructed to access the first device through a contention-free random access procedure (CFRA). When the resource allocation type is a second type, the second device is instructed to access the first device through a two-step contention-based random access procedure (2-step CBRA). When the resource allocation type is a third type, the second device is instructed to access the first device through a three-step contention-based random access procedure (3-step CBRA).

[0045] In some possible designs, the second message includes the resource allocation type, and the resource allocation type indicates the first type. After the sending the second message, the method further includes receiving a Msg1 of the CFRA, where the Msg1 of the CFRA includes at least one of the following: the upper layer data, the second procedure ID. In this way, in the CFRA, the first device can send a Msg1 with data to the second device.

[0046] In some possible designs, the method further includes sending a Msg2 of the CFRA, where the Msg2 of the CFRA includes an acknowledgement (ACK) message or a non-acknowledgement (NACK) message.

[0047] In some implementations of the CFRA, after the first device receives the Msg1, the first device can not send the Msg2. That is, after the second device sends the Msg1, the second device can consider that the access is completed (successful).

[0048] In some implementations of the CFRA, after the first device receives the Msg1, the first device can send the Msg2. That is, after the second device sends the Msg1, the second device can consider that the access is completed (successful) after receiving the Msg2 carrying the ACK message. Correspondingly, after the second device sends the Msg1, the second device can consider that the access is not completed if the Msg2 is not received. After the second device sends the Msg1, the second device can consider that the access fails if the Msg2 carrying the NACK message is received.

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

[0050] In some possible designs, the method further includes sending a Msg2 of the 2-step CBRA, where the Msg2 of the 2-step CBRA includes an acknowledgement (ACK) message or a non-acknowledgement (NACK) message.

[0051] In some possible designs, the first device determines whether the second device succeeds in the contention based on a device ID of the second device. In a case that the second device succeeds in the contention, a Msg2 of the 2-step CBRA carrying the confirmation message is transmitted. In a case that the second device fails in the contention, a Msg2 of the 2-step CBRA carrying the non-confirmation message is transmitted.

[0052] In some possible designs, the second message includes a resource allocation type, and the resource allocation type indicates the third type. After the second message is transmitted, the method further includes receiving a Msg1 of the 3-step CBRA, and the Msg1 of the 3-step CBRA includes at least one of the following: the first random ID, the second procedure ID. A Msg2 of the 3-step CBRA is transmitted, and the Msg2 of the 3-step CBRA includes a second random ID.

[0053] In some possible designs, the second random ID is the same as the first random ID, which corresponds to an indication that the second device succeeds in the contention. The second random ID is different from the first random ID, which corresponds to an indication that the second device fails in the contention.

[0054] In some possible designs, in a case that the second random ID is the same as the first random ID, the method further includes receiving a Msg3 of the 3-step CBRA, and the Msg3 of the 3-step CBRA includes a device ID of the second device.

[0055] In some possible designs, the method further includes transmitting a Msg4 of the 3-step CBRA, and the Msg4 of the 3-step CBRA includes a confirmation ACK message or a non-confirmation NACK message. Similar to a procedure of the CFRA, the Msg4 is optional in the 3-step CBRA procedure. A function of the Msg4 is similar to a function of a Msg2 of the CFRA.

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

[0057] In some possible designs, in a case that multiple pieces of resource information are configured to the second device, updated resource information is used for random access of the second device to the first device.

[0058] Thus, a specific solution for configuring resource information to the second device is provided. In the present application, the first device can configure resource to the second device through one or more of the following: a Paging message, a Repaging message, a round start message, a time slot start message.

[0059] In some possible designs, the method further includes: configuring the second device with first resource information, and second resource information. The second resource information is configured later than the first resource information. When the first resource information and the second resource information both include a first resource type, a first resource set is used for random access of the second device to the first device. The first resource set includes: the second resource information, and resource configuration different from the first resource type in the first resource information. When the first resource information and the second resource information do not both include the same resource type, a second resource set is used for random access of 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, Q value.

[0060] In some possible designs, the configuring the second device with the first resource information includes: configuring the second device with the first resource information through the first message, and / or a round start message, and / or a time slot start message. The configuring the second device with the second resource information includes: configuring the second device with the second resource information through a round start message, and / or a time slot start message, and / or the second message.

[0061] Thus, the specific implementation of the first device configuring resource to the second device is clarified.

[0062] For example, when the first device configures resource information to the second device multiple times, if the multiple times of resource information includes repeated types (e.g., both round information, time domain information, frequency domain information, Q value, etc.), the resource at the later time (i.e., after update) is effective. If the multiple times of resource information does not include repeated types, joint configuration can be implemented, i.e., the multiple times of resource information are all effective.

[0063] In a second aspect, a method for communication is provided. The method is applied to a second device. The method comprises: receiving a second message, the second message indicating that the second device initiates random access to a first device to facilitate AIoT communication with the first device; and sending a fourth message, the fourth message being used to initiate random access to the second device. In an example, the second device can be an AIoT device. In some embodiments, the second message can indicate that the second device initiates random access to the first device repeatedly (or again). In this example, the second device can have performed one or more random access before receiving the second message, and the one or more random access can not be successful. For example, the second message can comprise a Repaging message.

[0064] Based on the scheme, the second device can perform random access to the first device according to the received second message. It can be understood that in the communication process, the second device can fail to complete the access in time due to some reasons. In this way, by receiving the second message, the second device can attempt to access again under the indication of the first device (e.g., a card reading device).

[0065] In a possible design, before receiving the second message, the method further comprises: receiving a first message, the first message being used to initiate random access to the first device by the second device. The first message and the second message are associated with a first request, the first request indicating that the first device performs AIoT communication with the second device. The method further comprises: sending a first random access message, the first random access message being used to perform random access to the first device.

[0066] In this example, the second device can receive the first message before receiving the second message. The first message and the second message can be associated with the first request, so that the second device can know that the first message and the second message correspond to the same first request (e.g., a CN request). In this example, the second device receives the first message. The second device can attempt to perform random access according to the first message. In the case where the random access is not successful, the second device can perform access again according to the received second message.

[0067] In a possible design, the first message and / or the second message comprises at least one of the following: shared resource and / or dedicated resource information, resource allocation type, downlink command indication information, a second procedure ID, information indicating whether to receive paging or ignore paging, identification information of the first device, information indicating that the device receiving paging fails to access, information indicating whether there is a repeated message, and type information of the second device. The second procedure ID corresponds to the first request. In some implementations, the first request can comprise a first procedure ID. The second procedure ID can be the same as or correspond to the first procedure ID.

[0068] In a possible design, the first message and / or the second message is configured with a first flag bit, where the first flag bit is used to indicate whether the message carrying the first flag bit is an initial message or a repeated message.

[0069] In a 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 repeated message.

[0070] In this way, by configuring the flag bit, the second device can accurately determine whether the received message is an initial message or a repeated message. The initial message can be the first message sent by the card reading device after receiving the CN request, for example, the first Paging message. The repeated message can be the second or subsequent message sent by the card reading device after receiving the CN request, for example, the Repaging message.

[0071] In a possible design, the first message is of a first type, and the second message is of a second type. The first type corresponds to an initial message, and the second type corresponds to a repeated message.

[0072] In a possible design, the first message and the second message are both 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.

[0073] This scheme provides another implementation of distinguishing an initial message and a repeated message. For example, the initial message and the repeated message are distinguished by different types.

[0074] In a possible design, the second flow ID, the first flag bit of the first message, or the identification information of the first message is included in a packet subheader or control information of the first message. And / or, the second flow ID, the first flag bit of the second message, or the identification information of the second message is included in a packet subheader or control information of the second message. In this way, after receiving a message (such as the first message, the second message, or the like), the second device can parse the subheader or the control information, and determine whether to respond to the message, and then parse the subsequent data part, thereby saving power consumption of the second device.

[0075] In a possible design, after receiving the second message, the method further includes: determining, according to the second message, to respond to the second message. The sending the fourth message includes: sending the fourth message in a case where it is determined to respond to the second message.

[0076] In a possible design, the second message is determined to be responded to in a case where the second procedure ID included in the second message is not received and / or the second message is an initial message. Alternatively, the second message is determined to be responded to in a case where the second procedure ID included in the second message is not received and / or the second message is a repeated message. Alternatively, the second message is determined to be responded to according to a preset rule in a case where the second procedure ID included in the second message is received and / or the second message is a repeated message.

[0077] In a possible design, the preset rule includes: determining that random access to the first device is not accessed or not completed.

[0078] In this example, the response to the message can include random access to the first device based on the message.

[0079] In this way, the second device can respond to all initial messages. For example, the second device can respond to a Paging message. For another example, the second device can receive a Repaging message without receiving a Paging message, and directly respond to the Repaging message since the second procedure ID of the Repaging message is not received.

[0080] The second device can determine to receive a repeated message (e.g., a second message, a Repaging message) according to the second procedure ID that has been received, in combination with a flag bit, identification information, and the like. The second device can determine whether to respond according to a preset rule.

[0081] For example, the second message (e.g., a Repaging message) does not include related content (e.g., an ID, a group ID, a resource, and the like) indicating that a response is required or not required. In this case, the second device can determine whether to respond to the second message according to whether the access is successful. The second device can respond to the second message in a case where the access is not accessed or not completed. This scheme can be applied to a scenario where the second device can determine whether the access is successful.

[0082] For another example, the second message includes related content indicating that a response is required or not required. In this case, the second device can determine whether to respond according to a preset rule and content carried in the second message. This scheme can be applied to a scenario where the second device has the capability of determining whether the access is successful, or the second device does not have the capability of determining whether the access is successful.

[0083] In a possible design, before receiving the second message, the method further includes: sending Msg1, where the Msg1 includes at least one of the following: upper layer data, a second procedure ID, and a first random ID. And / or, sending Msg3, where the Msg3 includes at least one of the following: upper layer data and a procedure ID. The upper layer data includes a device ID of the second device, the second procedure ID corresponds to the first request, and the first random ID corresponds to the second device. Here, Msg1 can be Msg1 (e.g., the first message) in a random access procedure. Msg3 can be Msg3 (e.g., the third message) in the random access procedure. In different random access procedures, the content of Msg1 and / or Msg3 can be the same or different.

[0084] In a possible design, 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 through a contention-free random access procedure CFRA. Alternatively, the resource allocation type indicates that the second device accesses the first device through a two-step contention-based random access procedure 2-step CBRA. Alternatively, the resource allocation type indicates that the second device accesses the first device through a three-step contention-based random access procedure 3-step CBRA.

[0085] In a possible design, the first message includes the resource allocation type, which indicates that the second device accesses the first device through CFRA. Alternatively, the resource allocation type indicates that the second device accesses the first device through 2-step CBRA. After receiving the first message, the method further includes: sending Msg1, where the Msg1 includes at least one of the following: the upper layer data and the second procedure ID.

[0086] In a possible design, the random access to the first device is not accessed or not completed, including: failing to send the Msg1, or not sending the Msg1, or not receiving the first message.

[0087] In this example, the second device can determine, in a case where the second device performs random access through CFRA or 2-step CBRA, that the random access is not accessed or not completed according to that the Msg1 is not normally sent. In this way, the second device can respond to the second message (e.g., a Repaging message) accordingly, for example, by sending a fourth message. The fourth message can include one or more messages (e.g., Msg1, Msg3, etc.) in the random access procedure.

[0088] In one possible design, the first message includes the resource allocation type, which indicates that the second device accesses the first device through CFRA. Alternatively, the resource allocation type indicates that the second device accesses the first device through 2-step CBRA. After sending the Msg1, the method further includes receiving a Msg2, which includes an acknowledgement (ACK) message or a non-acknowledgement (NACK) message.

[0089] In one possible design, the random access to the first device is not accessed or not completed, including: failing to receive the Msg2, or not receiving the Msg2, or receiving the Msg2 including a non-acknowledgement message.

[0090] In this example, the second device can determine that the random access is not accessed or not completed according to the related procedure of the Msg2 in the case of random access through CFRA or 2-step CBRA.

[0091] In one possible design, the first message includes the resource allocation type, which indicates that the second device accesses the first device through 3-step CBRA. After receiving the first message, the method further includes sending a Msg1, which includes a first random ID corresponding to the second device. Receiving a Msg2, which includes a second random ID. In the case that the first random ID is the same as the second random ID, sending a Msg3, which includes a device ID of the second device.

[0092] In one possible design, the random access to the first device is not accessed or not completed, including: failing to send the Msg1 and / or Msg3, or not sending the Msg1 and / or Msg3, or not receiving the first message. And / or, failing to receive the Msg2, or not receiving the Msg2.

[0093] In one possible design, after sending the Msg3, the method further includes receiving a Msg4, which includes an acknowledgement (ACK) message or a non-acknowledgement (NACK) message.

[0094] In one possible design, the random access to the first device is not accessed or not completed, including: failing to receive the Msg4, or not receiving the Msg4, or receiving the Msg4 including a non-acknowledgement message.

[0095] In this example, the second device can determine that the random access is not accessed or not completed according to the failure of normal sending or receiving or indication of each message in the procedure in the case of random access through 3-step CBRA.

[0096] In the above examples, it is assumed that the second device determines that the second message needs to be responded to based on that a random access procedure performed by the second device before receiving the second message is not successful.

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

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

[0099] In one possible design, the second message includes at least one first set of IDs corresponding to devices that have not accessed or have not completed accessing, and the at least one first set of IDs corresponds to at least one set of device IDs, and the at least one set of device IDs includes at least one device ID corresponding to a device that has not accessed or has not completed accessing. The random access to the first device that has not accessed or has not completed accessing includes that the device ID of the second device is included in the at least one set of device IDs corresponding to the first set of IDs. Alternatively, the second message includes at least one second set of IDs, and the at least one second set of IDs includes at least one device ID corresponding to a device that has completed accessing, and the random access to the first device that has not accessed or has not completed accessing includes that the device ID of the second device is not included in the at least one set of device IDs corresponding to the second set of IDs.

[0100] In one possible design, the second message includes resource information for devices that have not accessed or have not completed accessing. The resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value. The random access to the first device that has not accessed or has not completed accessing includes that resource information used by the second device when the second device last accessed the first device is included in the second message. Alternatively, the second message includes resource information for devices that have completed accessing. The random access to the first device that has not accessed or has not completed accessing includes that resource information used by the second device when the second device last accessed the first device is not included in the second message.

[0101] In different implementations of the disclosure, the transmission timing of the repeated message can also be different. The following are described separately.

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

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

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

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

[0106] In a possible design, after receiving the first message, the method further includes: receiving a third message, where the third message is used to indicate the start of a new round. The third message includes the first message, or the third message includes the second message.

[0107] In a possible design, after receiving the first message, the method further includes: receiving a first round start message, where the first round start message is used to indicate the start of a first round.

[0108] In a possible design, the receiving the second message includes: receiving the second message after the end of all rounds and / or time slots corresponding to the first message.

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

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

[0111] In a possible design, in the case of configuring multiple pieces of resource information to the second device, the updated resource information is used for random access of the second device to the first device.

[0112] In a possible design, the method further includes: configuring, for the second device, first resource information and second resource information. The second resource information is configured at a time later than the time at which the first resource information is configured. When the first resource information and the second resource information both include configuration of a first resource type, a first resource set is used for random access of the second device to the first device. The first resource set includes the second resource information and resource configuration different from the first resource type in the first resource information. When the first resource information and the second resource information are configured for different resource types, a second resource set is used for random access of 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.

[0113] In a possible design, the configuring, for the second device, the first resource information includes: configuring, for the second device, the first resource information through the first message, and / or a round start message, and / or a slot start message. The configuring, for the second device, the second resource information includes: configuring, for the second device, the second resource information through a round start message, and / or a slot start message, and / or the second message.

[0114] In a third aspect, a communication device is provided. The communication device can be used to perform the method provided in the first aspect and any possible design thereof. For example, the communication device can be a card reader. For example, the base station in the topology 1; for another example, the UE in the topology 2.

[0115] In a fourth aspect, a communication device is provided. The communication device can be used to perform the method provided in the first aspect and any possible design thereof. For example, the communication device can be an AIoT device.

[0116] In a fifth aspect, a communication system is provided. The communication system includes the communication device provided in the third aspect and the fourth aspect.

[0117] In a sixth aspect, a chip system is provided. The chip system is applied to a first device. The chip system can include one or more interface circuits and one or more processors. The interface circuit and the processor are interconnected through a line. The interface circuit is configured to receive a signal from a memory of the first device and send the signal to the processor. The signal includes computer instructions stored in the memory. When the processor executes the computer instructions described above, the first device performs the method provided in the first aspect and any possible design thereof.

[0118] In a seventh aspect, a chip system is provided for use in the second device. The chip system can include one or more interface circuits and one or more processors. The interface circuits and the processors are interconnected by wires. The interface circuits are configured to receive a signal from a memory of the second device and send the signal to the processors. The signal includes computer instructions stored in the memory. When the processors execute the computer instructions, the second device performs the method provided in the second aspect and any possible design thereof.

[0119] In an eighth aspect, a computer readable storage medium is provided. The computer readable storage medium includes computer instructions. When the computer instructions are run on an electronic device, the first device or the second device performs the technical solutions provided in the first aspect to the second aspect and any possible implementation thereof.

[0120] In a ninth aspect, a computer program product is provided. When the computer program product is run on a computer (e.g., the first device or the second device), the computer performs the technical solutions provided in the first aspect to the second aspect and any possible implementation thereof.

[0121] It can be understood that the technical solutions provided in the third aspect to the ninth aspect of the present application can correspond to the first aspect and any possible design thereof, respectively, and thus can achieve similar beneficial effects, which will not be described here again. BRIEF DESCRIPTION OF DRAWINGS

[0122] FIG. 1 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0123] FIG. 2 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0124] FIG. 3 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0125] FIG. 4 is a schematic diagram of an interaction flow of a random access method according to an embodiment of the present application;

[0126] FIG. 5 is a schematic diagram of an interaction flow of a random access method according to an embodiment of the present application;

[0127] FIG. 6 is a schematic diagram of an interaction flow of a random access method according to an embodiment of the present application;

[0128] FIG. 7 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0129] FIG. 8 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0130] FIG. 9 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0131] FIG. 10 is a schematic diagram of a communication scenario according to an embodiment of the present application;

[0132] FIG. 11 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0133] FIG. 12 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0134] FIG. 13 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0135] FIG. 14 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0136] FIG. 15 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0137] FIG. 16 is a schematic diagram of an interaction flow of a communication method according to an embodiment of the present application;

[0138] FIG. 17 is a schematic diagram of a chip system according to an embodiment of the present application. DETAILED DESCRIPTION

[0139] Hereinafter, the terms "first" and "second" are used only for the purpose of description, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first" and "second" can explicitly or implicitly include one or more of the features. In the description of the embodiments, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0140] The following first describes the related concepts involved in the embodiments of the present application.

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

[0142] AIoT aims to provide a low-power, low-complexity and low-cost Internet of Things solution. In the standard system of the third generation partnership project (3GPP), it is a lower capability standard than narrow band internet of things (NB-IoT), and in the non-3GPP system, it aims at the market demand of radio frequency identification (RFID) and provides a comparable and more advantageous technical solution.

[0143] The demand source of AIoT is to solve the scenarios that are not covered by current 3GPP technology, for example, the following three scenarios:

[0144] 1) extreme environmental conditions, such as high pressure, extremely high / low temperature, humid environment;

[0145] 2) one or more of the following requirements: ultra-low complexity, very small device size / shape factor (e.g., millimeter thickness), maintenance-free (e.g., no need to replace the traditional battery of the device), and longer life cycle;

[0146] 3) device scenarios where traditional battery driving is not applicable.

[0147] AIoT is also an Internet of Things service, which aims to provide AIoT devices with low power consumption and low complexity, very small size, and longer life cycle. AIoT devices are powered by energy harvesting, can be battery-free, or have limited energy storage capacity (i.e., use capacitors). It can communicate with other devices without a traditional power source, and / or avoid human intervention for charging or replacement.

[0148] Generally, an Internet of Things device that supports environmental power supply does not have a traditional battery. The device itself uses energy obtained from radio waves or any other form of energy that can be obtained in a specific use case. For example, in some scenarios, AIoT devices can obtain energy from radio waves, which can come from a 5G NR network entity or a terminal device. In other scenarios, an Internet of Things device that supports environmental power supply can obtain energy from solar energy, light, motion / vibration, heat, pressure, or any other source of energy.

[0149] AIoT devices can be divided into the following types:

[0150] Type one: AIoT devices of this type have no energy storage capability, no independent signal generation / amplification, and can use backscatter transmission;

[0151] Type two: AIoT devices of this type have energy storage capability, no independent signal generation, can participate in backscatter transmission, and stored energy can be used for backscatter signal amplification;

[0152] Type three: AIoT devices of this type have energy storage capability and independent signal generation;

[0153] Type four: the device originated traffic is triggered by the device terminated traffic or signalling. This type can also be referred to as Device-originated-device-terminated triggered (DO-DTT) type.

[0154] Type five: the traffic is terminated at the AIoT device. This type can also be referred to as Device-terminated (DT) type.

[0155] Type six: the device can autonomously originate traffic.

[0156] 2. Inventory.

[0157] The inventory can refer to a process in which a reader identifies a device to obtain an identity (ID) of the device. This process can be applied in various scenarios, such as logistics management or warehouse management, especially for scenarios in which a large number of terminal devices exist, which can save a lot of manpower and resources and achieve fast and accurate inventory.

[0158] 3. RFID technology.

[0159] RFID (Radio Frequency Identification) is a communication technology. Network devices and terminal devices can communicate with each other through wireless radio frequency. Network devices (e.g., readers) can identify devices (e.g., tags) and read and write related data through wireless radio frequency.

[0160] For example, application scenarios of AIoT technology can include product inventory, indoor command communication, etc.

[0161] Taking product inventory as an example. The product inventory scenario can also be referred to as indoor inventory. In this scenario, a communication system can implement inventory processing of products within a limited range based on AIoT technology to obtain product information of the products. The product information can include at least one of the following: product quantity, product type, product identity, product location, etc.

[0162] 4、initial message and repeat message. The initial message can be the first message sent after the start of a procedure (e.g., a paging procedure). For example, the initial message can include a Paging message. The repeat message can be the Nth message sent after the start of a procedure (e.g., a paging procedure), where N is an integer greater than 1. For example, the repeat message can include a Repaging message. In the description of the present application, the initial message includes a Paging message, and the repeat message includes a Repaging message, where the repeat message can include information indicating the number of times the paging message is sent. In other implementations, the initial message and / or the repeat message can include other messages, and / or, the initial message can be other than a Paging message, and / or, the repeat message can be other than a Paging message.

[0163] Referring to FIG. 1, a logical diagram of AIoT communication is provided.

[0164] In this example, devices participating in AIoT communication can include a core network device, an access network device, a reader device, and an AIoT device.

[0165] The core network device can also be referred to as an AIoT controller (AIoT CN, CN for short). The core network device can be an Access and Mobility Management Function (AMF) or a User Plane Function (UPF).

[0166] The access network device can be a base station. The access network device can be a base station specially configured for AIoT communication, or the access network device can be a base station multiplexed in 4G, 5G, 6G, etc. cellular communication. For example, the access network device multiplexes a base station in 5G communication, and the access network device can be referred to as gNB.

[0167] The reader device (Reader) can be a device that directly communicates with the AIoT device. For example, the reader device can be a mobile phone, a tag reader, etc. Taking the reader device as a mobile phone as an example, the reader device can also be referred to as a UE (i.e., user equipment).

[0168] The AIoT device can be referred to as a device (Device). In some embodiments, the AIoT device can be configured with an RFID chip. The AIoT device can communicate with the reader device through the RFID chip.

[0169] In FIG. 1, a device-to-device communication flow diagram of AIoT communication is also provided.

[0170] As shown in FIG. 1, under the topology 2 scenario, the flow can include the following steps.

[0171] S101. The core network device sends a message 101 to the access network device.

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

[0173] In this example as shown in FIG. 1, the message 101 can include an inventory command and / or a downlink command (DL command).

[0174] In some embodiments, the message 101 can also be referred to as a CN request (CN request).

[0175] S102. The access network device sends a message 102 to the card reading device.

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

[0177] In some embodiments, the base station can establish a communication connection with the Reader through a radio resource control (RRC) communication link.

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

[0179] S103. The card reading device sends a message 103 to the AIoT device.

[0180] For example, the message 103 can be an initial message. The message 103 can include a paging message for one or more devices.

[0181] The paging message can include at least one of the following information:

[0182] shared resource and / or dedicated resource configured for AIoT communication; resource allocation type (RA type); downlink command indication (DL command) information; paging procedure ID; device ID (Device ID) needs to receive paging or ignore paging; card reading device ID; failed Device receiving paging indication; information indicating whether there is a repeated message; type information of AIoT device.

[0183] The type of the AIoT device can be any one of the above types one to type six. Through the type information of the AIoT device, the AIoT device can determine whether its device type is consistent with the type indicated by the Paging message. In the case of the same device type, the AIoT device can respond to the Paging message. In the case of the same device type, the AIoT device can re-access according to the repeated message received subsequently when it has not accessed or has not completed access in the procedure corresponding to the initial message. Alternatively, in the case of the same device type, the AIoT device can determine whether to respond to the repeated message according to whether other conditions are met (such as whether a preset rule is met, which will be described later) when it has not accessed or has not completed access in the procedure corresponding to the initial message. Alternatively, in the case that the device type of the AIoT device is different from the type indicated by the Paging message, the AIoT device does not respond to the repeated message. Alternatively, in the case that the device type of the AIoT device is different from the type indicated by the Paging message, the AIoT device determines whether to respond to the repeated message according to whether a preset rule is met.

[0184] The information indicating whether there is a repeated message is used to indicate whether there is a repeated message after the initial message. Taking the case that there is a repeated message after the initial message as an example. Through the information indicating whether there is a repeated message, the AIoT device can remain awake after receiving the initial message (or when it has not accessed or has not completed access in the procedure corresponding to the initial message) in order to receive the subsequent repeated message (such as Repaging message) for re-access; or the AIoT device can charge after receiving the initial message (or when it has not accessed or has not completed access in the procedure corresponding to the initial message), and the AIoT device can also wake up before receiving the repeated message in order to receive the subsequent repeated message (such as Repaging message) for re-access.

[0185] The shared resource and / or dedicated resource configured for AIoT communication can include time domain resource and / or frequency domain resource configured for AIoT communication.

[0186] The RA type can include one or more. For example, the RA type includes three (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.

[0187] For example, when the RA type is a first value, the device can use a non-contention random access process (contention free random access, CFRA) to attempt to establish an AIoT communication connection with the reader. For example, the first value can be 0, or binary 00.

[0188] For another example, when the RA type is a second value, the device can use a 2-step contention-based random access process (2-step CBRA) to attempt to establish an AIoT communication connection with the reader. For example, the second value can be 1, or binary 01.

[0189] For another example, when the RA type is a third value, the device can use a 3-step contention-based random access process (3-step CBRA) to attempt to establish an AIoT communication connection with the reader. For example, the third value can be 2, or binary 10.

[0190] The downlink command indication (DL command) information can be used to indicate whether the paging message is used to establish an AIoT communication for DL command transmission.

[0191] The device ID (Device ID) needs to receive the paging or ignore the paging field indication needs to receive the paging, the device corresponding to the device ID carried in the paging message can receive the paging message and perform subsequent response. Correspondingly, the device ID (Device ID) needs to ignore the paging field indication needs to receive the paging, the device corresponding to the device ID carried in the paging message can not receive the paging message, or receive the paging message and do not respond to the paging message or do not parse the paging message.

[0192] The paging procedure ID can correspond to the Paging message. For example, different paging procedure IDs can correspond to the Paging messages generated based on different CN requests. In the case of receiving one CN request, the paging procedure IDs corresponding to the multiple Paging messages (e.g., including the Paging message and the repaging message) generated by the Reader can be the same or different.

[0193] 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 according to the CN request ID.

[0194] In the following examples, the paging procedure ID can be denoted as paging ID.

[0195] In the case of receiving the paging indication that the failed Device has been configured, the Device receiving the indication that the random access has failed can receive and respond to the current Paging message according to the configuration.

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

[0197] In some embodiments, the paging message can include a message containing an ID of a single A-IoT device.

[0198] In this example, in the case of receiving the paging message, the Device can compare whether the device ID carried in the paging message is consistent with the device ID of the Device itself. In the case of the device ID carried in the paging message being consistent with the device ID of the Device itself, the Device can attempt to establish an AIoT communication connection with the Reader.

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

[0200] In this example, upon receiving the paging message, the Device can determine whether the group ID of the plurality of Devices mapped by the paging message corresponds to a group that includes the current Device. When the Device is included in the plurality of Devices corresponding to the group ID, the Device can attempt to establish an AIoT communication connection with the Reader.

[0201] In other embodiments, the paging message can be a message that does not contain an ID, i.e., addressed for all devices that can receive the AIoT message. For example, all Devices that receive the paging message can attempt to establish an AIoT communication connection with the Reader.

[0202] In the above example of FIG. 1, the access network device and the card reading device are separate. In other scenarios, the access network device and the card reading device can also be the same device. In this way, the access network device can directly communicate with the AIoT device.

[0203] For example, referring to FIG. 2, another communication scenario is provided for the topology 1 scenario.

[0204] In this example, the core network device can send a message 201 to the access network device through S201. The message 201 can include a CN request.

[0205] The access network device can send a message 202 to directly communicate with the AIoT device through AIoT communication through S202. For example, the message 202 can include a Paging message.

[0206] For example, the Device receives the Paging message and establishes an AIoT communication connection with the Reader. In this way, corresponding to the scenario shown in FIG. 1, the Device can establish an AIoT communication connection with the UE according to the Paging message. Corresponding to the scenario shown in FIG. 2, the Device can establish an AIoT communication connection with the access network device (such as a base station) according to the Paging message.

[0207] Referring to FIG. 3, after the card reading device sends a Paging message to the AIoT device in an AIoT communication scenario, the AIoT communication between the card reading device and the AIoT device can be implemented through steps A, B, and C.

[0208] As shown in FIG. 3, at step A, the card reading device can send an AIoT paging message to the AIoT device. The AIoT paging message can correspond to the paging message in FIG. 1 or FIG. 2.

[0209] As shown in step B of FIG. 3, the AIoT device can attempt to establish an AIoT communication connection with the card reading device through an AIoT random access procedure according to the received AIoT paging message.

[0210] In the case of successful establishment of the AIoT communication connection, the AIoT device can send data of the AIoT device to the card reading device through the established AIoT communication connection (such as performing D2R data transmission).

[0211] In the present application, random access failure is opposite to random access success. For example, in the case that all message interactions in the random access procedure are completed, and / or the message indicates that the random access is successful (such as ACK), the random access is successful. For another example, in the case that one or more message interactions in the random access procedure are not completed in the paging procedure, or the message indicates that the random access is failed (such as NACK), the random access is failed.

[0212] In some implementations, after step B, the AIoT communication can further include step C. In step C, the card reading device can further send an indication of other data reporting to the AIoT device through an R2D data transmission indication. Correspondingly, the AIoT device can perform D2R data transmission to the card reading device through the established AIoT communication connection.

[0213] In different implementations of the present application, in step B of FIG. 3, the AIoT device and the card reading device can establish the AIoT communication connection in different ways. For example, in the communication scenario shown in FIG. 1.

[0214] In some embodiments, the AIoT device can attempt to establish an AIoT communication connection with the card reading device through a contention free random access procedure (CFRA) after receiving the paging message (such as message 103).

[0215] For example, referring to FIG. 4, an access flow diagram of a CFRA is shown.

[0216] As shown in FIG. 4, the scheme can include:

[0217] S301, the card reading device sends message 103 to the AIoT device.

[0218] For example, the execution of S301 can refer to the aforementioned S103 in FIG. 1. In the message 103, the Paging message sent by the card reading device to the AIoT device can be included.

[0219] For example, the AIoT device determines to perform random access to the card reading device according to the Paging message. In the case of successful random access, the AIoT device can establish an AIoT communication connection with the card reading device.

[0220] In combination with the above example, in some implementations of the example, the Paging message sent by the card reading device to the AIoT device can carry information indicating that the RA type is type0.

[0221] Therefore, the AIoT device can perform CFRA according to the RA type being type0, and attempt to establish an AIoT communication connection with the card reading device. The process of the CFRA can specifically include the following S302 or S302-S303.

[0222] S302, the AIoT device sends a message 301 to the card reading device.

[0223] For example, the message 301 can include the message 1 (Msg1) of the CFRA.

[0224] In some embodiments, the Msg1 can carry upper layer data. The upper layer data can include the device ID of the AIoT device and / or other upper layer data.

[0225] In another embodiment, the Paging ID carried in the Paging message is taken as an example. The Paging ID can also be carried in the Msg1 corresponding to the message 301.

[0226] In some implementations, through the S302, the AIoT device can achieve CFRA-based access to the card reading device.

[0227] In another implementation, after performing S302, the CFRA-based access process can further include S303:

[0228] S303, the card reading device sends a message 302 to the AIoT device.

[0229] For example, in this implementation, the card reading device can send the following message 302 to the AIoT device upon receiving the Msg1. The message 302 can also be referred to as the message 3 (Msg2) of the CFRA.

[0230] In some embodiments, the message 302 can comprise acknowledgement (ACK) information. Thus, the card reading device can indicate the random access to the AIoT device is successful by sending the message 302 carrying the ACK information. Correspondingly, the AIoT device can determine the random access to the card reading device is successful according to the reception of the message 302.

[0231] In some other embodiments, the message 302 can comprise non-acknowledgement (NACK) information. Thus, the card reading device can indicate the random access to the AIoT device is failed by sending the message 302 carrying the NACK information. Correspondingly, the AIoT device can determine the random access to the card reading device is failed according to the reception of the message 302.

[0232] Thus, through the above S302 or S302-S303, the AIoT device can attempt to establish the AIoT communication connection with the card reading device through CFRA in the case of receiving the Paging message.

[0233] In some other embodiments, the AIoT device can attempt to establish the AIoT communication connection with the card reading device through 2-step CBRA after receiving the Paging message.

[0234] For example, referring to FIG. 5, an access flow diagram of 2-step CBRA is shown.

[0235] As shown in FIG. 5, the scheme can comprise:

[0236] S401, the card reading device sends a message 103 to the AIoT device.

[0237] For example, the execution of S401 can refer to the aforementioned S103 in FIG. 1. In the message 103, the Paging message sent by the card reading device to the AIoT device can be included.

[0238] For example, the AIoT device determines to perform the random access to the card reading device according to the Paging message. In the case of successful random access, the AIoT device can establish the AIoT communication connection with the card reading device.

[0239] In combination with the above example, in some implementations of the example, the Paging message sent by the card reading device to the AIoT device can carry information indicating the RA type is type1.

[0240] Thus, the AIoT device can perform 2-step CBRA to attempt to establish the AIoT communication connection with the card reading device according to the RA type being type1. The process of 2-step CBRA can comprise the following S402 or S402-S403.

[0241] S402, the AIoT device sends a message 401 to the card reading device.

[0242] For example, the message 401 can include a message 1 (Msg1) of 2-step CBRA.

[0243] In some embodiments, the Msg1 can carry upper layer data. The upper layer data can include a device ID of the AIoT device and / or other upper layer data.

[0244] In another embodiment, the Paging ID carried in the Paging message is taken as an example. The Paging ID can also be carried in the Msg1 corresponding to the message 201.

[0245] In some implementations, through the S402, the AIoT device can complete the 2-step CBRA-based access to the card reading device.

[0246] In another implementation, after performing the S402, the 2-step CBRA-based access process can further include S403:

[0247] S403, the card reading device sends a message 402 to the AIoT device.

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

[0249] In some embodiments, the message 402 can include acknowledgement (ACK) information. Thus, the card reading device can indicate that the random access of the AIoT device is successful by sending the message 402 carrying the ACK information. Correspondingly, the AIoT device can determine that the random access to the card reading device is successful according to the reception of the message 402.

[0250] In another embodiment, the message 402 can include non-acknowledgement (NACK) information. Thus, the card reading device can indicate that the random access of the AIoT device fails by sending the message 402 carrying the NACK information. Correspondingly, the AIoT device can determine that the random access to the card reading device fails according to the reception of the message 402.

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

[0252] In some embodiments, the AIoT device can attempt to establish the AIoT communication connection with the card reading device through a 2-step contention-based random access procedure (2-step CBRA) after receiving the Paging message.

[0253] For example, referring to FIG. 6, an access flow diagram of a 3-step CBRA is shown.

[0254] As shown in FIG. 6, the scheme can include the following steps.

[0255] S501, the card reading device sends a message 103 to the AIoT device.

[0256] For example, the execution of S501 can refer to the aforementioned S103 in FIG. 1. In the message 103, the Paging message sent by the card reading device to the AIoT device can be included.

[0257] For example, the AIoT device determines to perform random access to the card reading device according to the Paging message. In the case of successful random access, the AIoT device can establish an AIoT communication connection with the card reading device.

[0258] In some implementations of the above example, the Paging message sent by the card reading device to the AIoT device can carry information indicating that the RA type is type2.

[0259] Therefore, the AIoT device can perform 3-step CBRA according to the RA type being type2 to attempt to establish an AIoT communication connection with the card reading device. The process of the 3-step CBRA can include the following S502-S503 or S502-S504.

[0260] S502, the AIoT device sends a message 501 to the card reading device.

[0261] For example, the message 501 can include a message 1 (Msg1) of the 3-step CBRA.

[0262] In some embodiments, the Msg1 can include a random ID. The random ID can be a random ID generated by the AIoT device to the card reading device (A-IoT Msg1 including one random ID generated by the A-IoT AIoT device to the card reading device), which can be determined according to the number of slots obtained.

[0263] S503, the card reading device sends a message 502 to the AIoT device.

[0264] Exemplarily, in this implementation, the card reading device can send the card reading device the following message 502 in the case that the card reading device receives the Msg1. The message 502 can also be referred to as a message 2 (Msg2) of the 3-step CBRA.

[0265] In this example, the message 502 can include a random ID. For example, the message 502 can include the random ID received through the message 501.

[0266] Correspondingly, the AIoT device can receive the message 502.

[0267] In some implementations, the AIoT device can perform the following S504 according to that the message 502 is received and the random ID carried in the message 502 is the same as the random ID sent by the AIoT device in the message 501. It can be understood that in the case that the random ID carried in the message 502 is the same as the random ID sent by the AIoT device in the message 501, the AIoT device can confirm the success of the competition. In this way, the AIoT device can perform subsequent operations with the card reading device, such as performing S504.

[0268] In some implementations, the AIoT device can determine that the competition fails according to that the message 502 is not received, or the message 502 is received but the random ID carried in the message 502 is different from the random ID sent by the AIoT device in the message 501. Thus, the 3-step CBRA is exited this time.

[0269] Taking the case that the AIoT device determines the success of the competition according to that the message 502 is received as an example.

[0270] S504, the AIoT device sends the card reading device the message 503.

[0271] Exemplarily, the message 503 can correspond to a Msg3 of the 3-step CBRA.

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

[0273] Thus, the AIoT device can attempt to establish an AIoT communication connection with the card reading device through the 3-step CBRA in the case that the AIoT device receives the Paging message.

[0274] In some embodiments, the 3-step CBRA has ended through the above S502-S504.

[0275] In some other embodiments, the card reading device can also send the AIoT device a Msg4 of the 3-step CBRA after S504.

[0276] For example, in this implementation, as shown in FIG. 6, the card reading device sends a message 504 to the AIoT device. This message 504 can correspond to Msg4 of the 3-step CBRA. ACK information or NACK information can be carried in this message 504. Taking the case where ACK information is carried in the message 504 as an example, the AIoT device can determine, according to the reception of the ACK information, that the card reading device has successfully received the device ID. Taking the case where NACK information is carried in the message 504 as an example, the AIoT device can determine, according to the reception of the NACK information, that the card reading device has not received the device ID or has not successfully parsed the device ID.

[0277] Thus, through the above examples of FIGS. 2 to 6, the AIoT device can indicate the RAtype through the card reading device, and attempt to establish an AIoT communication connection with the card reading device through the corresponding random access mode.

[0278] Correspondingly, when the AIoT device performs random access according to the RAtype, if any message (such as Msg2, Msg4, etc.) in the corresponding process is not received, or Msg2 or Msg4 carries NACK information, or the AIoT device has not received a Paging message since the beginning. Then, the AIoT device does not access or does not complete the access. Correspondingly, if all message interactions in the process are completed, and / or Msg2 and / or Msg4 carries ACK information, the AIoT device accesses successfully, or is said to complete the access.

[0279] Taking the case where the AIoT device successfully performs random access with the card reading device, i.e., successfully establishes an AIoT communication connection with the card reading device, as an example.

[0280] In this way, the AIoT device can perform subsequent communication with the card reading device based on the AIoT communication connection.

[0281] Taking the case where the CN request indicates that the card reading device performs inventory processing on the AIoT device as an example.

[0282] The AIoT device can send a CN request indicating the reported information (such as product information of the AIoT device, etc.) to the card reading device when the AIoT device corresponding time slot arrives after successfully performing random access with the card reading device.

[0283] In combination with the description of FIGS. 4 to 7, the AIoT device can send Msg1 to the card reading device after receiving the Paging message, so as to establish an AIoT communication connection with the card reading device through one of the random access processes described above.

[0284] In actual implementation, one card reading device can interact with multiple AIoT devices at the same time. In this way, in order to avoid signaling conflict of different AIoT devices and the card reading device, the card reading device can configure a corresponding occasion for each AIoT device, so that the AIoT device can send data to the card reading device when the occasion corresponding to the AIoT device arrives. For example, the AIoT device can send Msg1 to the card reading device when the occasion corresponding to the AIoT device arrives after receiving the Paging message.

[0285] As an example, referring to FIG. 7, an interaction timing diagram between a card reading device and an AIoT device is provided.

[0286] As shown in FIG. 7, the card reading device can send a Paging message to the AIoT device after receiving a CN request.

[0287] Correspondingly, the AIoT device can send Msg1 to the card reading device according to the RA type configured by the card reading device according to the received Paging message.

[0288] In this example, the card reading device can send a message starting round 1 to the AIoT device after sending the Paging message. For example, the card reading device can send a round start message to the AIoT device.

[0289] Then, the card reading device can send a message starting slot 1, a message starting slot 2, etc. to the AIoT device at a time, so as to indicate the start of each slot of the AIoT device. For example, the card reading device can send a slot start message to the AIoT device at the start of each slot.

[0290] In this example, each round includes 2 slots as an example.

[0291] Correspondingly, the AIoT device can send Msg1 to the card reading device according to the arrival of the slot corresponding to the AIoT device.

[0292] The parameters of the slot corresponding to the AIoT device can be directly configured by the card reading device, or the parameters of the slot corresponding to the AIoT device can be calculated and obtained by the AIoT device according to the parameters configured by the card reading device.

[0293] Taking an example of the AIoT device including device 1 and device 2.

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

[0295] Thus, in the example of FIG. 7, the card reading device can send the Paging message to the device 1 and the device 2 after receiving the CN request.

[0296] Correspondingly, the device 1 can perform random access to the card reading device according to the received Paging message.

[0297] The device 1 can receive the message sent by the card reading device that round 1 starts. The device 1 can also receive the message sent by the card reading device that time slot 1 starts. Thus, the device 1 can determine that its time slot arrives, and send Msg1 to the card reading device.

[0298] Similarly, the device 2 can perform random access to the card reading device according to the received Paging message.

[0299] The device 2 can receive the message sent by the card reading device that round 2 starts. The device 2 can also receive the message sent by the card reading device that time slot 1 starts. At this time, the time slot of the device 2 does not arrive, and the device 2 continues to wait for the message that the subsequent time slot starts. The device 2 can also receive the message sent by the card reading device that time slot 2 starts. Thus, the device 2 can determine that its time slot arrives, and send Msg1 to the card reading device.

[0300] In some implementations, multiple rounds can be included in one paging process. In this way, paging of a large number of AIoT devices can be implemented.

[0301] As shown in the timing flow of FIG. 7, after all time slots of round 1 end, the card reading device can send the message that round 2 starts to the AIoT device. Thereafter, the card reading device can also send the message that time slot 1 of round 2 starts, the message that time slot 2 of round 2 starts, and the like, to the AIoT device.

[0302] In the example of FIG. 7, the card reading device can interact with the AIoT device through the round start message and the time slot start message after sending the Paging message, to implement the interaction with each AIoT device in the entire Paging process.

[0303] In some embodiments, the Paging message and / or the round start message and / or the 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 according to the Paging message and / or the round start message and / or the time slot start message carrying the same Paging ID.

[0304] Thus, in the example as shown in FIG. 7, one Paging procedure can include one Paging message, one or more round start messages, and multiple slot start messages.

[0305] In some embodiments, referring to FIG. 8, another timing diagram of the interaction between the card reading device and the AIoT device is provided.

[0306] In the example as shown in FIG. 8, the card reading device can send a slot start message to the AIoT device after sending the Paging message.

[0307] In the example, the card reading device can send a Paging message to the AIoT device after receiving a CN request. In the first round, the card reading device can send each slot start message directly to the AIoT device without sending a round start message. For example, the card reading device can send a slot 1 start message, a slot 2 start message, and so on to the AIoT device after sending the Paging message.

[0308] In the case of the end of the first round, unlike the example as shown in FIG. 7, the card reading device can send a Paging message to the AIoT device again to indicate the start of the next round (e.g., the second round) of the AIoT device in the example as shown in FIG. 8.

[0309] In this way, in the procedure as shown in FIG. 8, the card reading device can send multiple Paging messages in the case of receiving one CN request. In some implementations, the two or more Paging messages corresponding to the same CN request can carry the same Paging ID.

[0310] Correspondingly, the AIoT device can determine the start of the next round of the same CN request according to the received Paging messages with the same Paging ID.

[0311] Thus, in the example as shown in FIG. 8, one Paging procedure can include multiple Paging messages and multiple slot start messages.

[0312] In some embodiments, referring to FIG. 9, another timing diagram of the interaction between the card reading device and the AIoT device is provided.

[0313] In the example as shown in FIG. 9, the AIoT device is taken as an example with a timing function.

[0314] In this example, the card reading device can not send a round start message or a time slot start message after sending the Paging message. Correspondingly, the AIoT device can start timing by itself in the case of receiving the Paging message. The AIoT device can also send Msg1 to the card reading device after the arrival of its corresponding time slot.

[0315] In some embodiments, similar to the scheme as shown in FIG. 8, the card reading device can send the Paging message again at the start of the next round in the case of receiving a CN request. Correspondingly, the AIoT device can determine that a new round has started according to the reception of the Paging message again.

[0316] In some embodiments, the Paging message corresponding to each round sent by the card reading device after receiving a CN request can carry the same Paging ID. Correspondingly, the AIoT device can determine that the next round of the same CN request starts according to the reception of the Paging message with the same Paging ID.

[0317] Thus, in this example as shown in FIG. 9, multiple Paging messages can be included in one Paging process.

[0318] The above FIGs. 4 to 6 provide several random access schemes for establishing AIoT communication connection, and FIGs. 7 to 9 provide several schemes for communication mode between the card reading device and the AIoT device. In different embodiments, different random access schemes can be matched with different communication modes to realize the establishment of AIoT communication connection between the AIoT device and the card reading device.

[0319] The following is described in combination with specific examples.

[0320] It can be understood that in the process of communication between the AIoT device and the card reading device, data or signaling transmission can be based on the resources configured by the network side. In different embodiments, the network side can include any one or more of the core network device, the access network device, and the card reading device.

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

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

[0323] The round information is used to indicate the information of the round for AIoT communication. The time domain information is used to indicate the information of the time domain for AIoT communication. The frequency domain information is used to indicate the information of the frequency band and / or frequency point and / or channel for AIoT communication, the number of frequency division multiplexing, and the like.

[0324] The Q value is used for the AIoT device to determine its corresponding time domain information or frequency domain information according to a preset rule.

[0325] Taking the use of the Q value to determine its corresponding time domain information as an example, the AIoT device can determine an integer (such as N) between 0 and (2 Q -1) as its corresponding time slot according to the configured Q value. In this way, after the AIoT device receives a message starting at the Nth time slot, it can confirm that its corresponding time slot has arrived, and perform data transmission (such as sending Msg1) with the card reading device in the time slot.

[0326] In different embodiments of the present application, several different resource configuration methods in AIoT communication processes are provided. Taking the interaction between the card reading device and the AIoT device through the communication mode shown in FIG. 7 as an example.

[0327] In some embodiments, the card reading device can configure resource information to the AIoT device through a Paging message.

[0328] In other embodiments, the card reading device can configure resource information to the AIoT device through a round start message.

[0329] In other embodiments, the card reading device can configure resource information to the AIoT device through a time slot start message.

[0330] In the above three configuration methods, the configured resource information can take effect within the flow of the corresponding message.

[0331] Taking the case that the card reading device can configure resource information 1 to the AIoT device through Paging message 1 as an example. The resource information 1 can take effect within the flow of the Paging message 1.

[0332] The flow of the Paging message 1 can be a logical process between the Paging message 1 and the next Paging message. In this way, the card reading device can start to execute the flow of the Paging message 1 after sending the Paging message 1. The card reading device can end the flow of the Paging message 1 when sending the next Paging message, or after the flow of all rounds ends. Correspondingly, the AIoT device can enter the flow of the Paging message 1 after receiving the Paging message 1. The AIoT device can end the flow of the Paging message 1 after receiving a message starting at the last time slot of the Paging message 1.

[0333] Therefore, the AIoT device can use the resource information 1 to communicate with the card reading device within the flow of the Paging message 1.

[0334] In some implementations, in the case that no resource information is carried in the next Paging message 2 after the Paging message 1, the resource information 1 continues to be effective within the flow corresponding to the Paging message 2. In this way, the AIoT device can continue to use the resource information 1 to communicate with the card reading device within the flow corresponding to the Paging message 2.

[0335] In the case that resource information (such as resource information 2) is carried in the Paging message 2, and the resource type of the resource information 2 is the same as that of the resource information 1, the resource information configured by the resource information 2 replaces the resource information configured by the resource information 1 and is effective in the flow corresponding to the Paging message 2.

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

[0337] For example, the resource information 1 configures round information, time domain information, frequency domain information, and Q value, and the resource information 2 configures round information, time domain information, frequency domain information, and Q value. Then the resource type of the resource information 2 is the same as that of the resource information 1. The resource information 2 is effective.

[0338] For another example, the resource information 1 configures round information, time domain information, and frequency domain information, and the resource information 2 configures frequency domain information and Q value. Then the repeated resource type of the resource information 2 and the resource information 1 can include frequency domain information. Thus, the frequency domain information and Q value of the resource information 2 are effective. The round information and time domain information of the resource information 1 are also effective.

[0339] For another example, the resource information 1 configures round information, time domain information, and frequency domain information, and the resource information 2 configures Q value. Then the resource information 2 and the resource information 1 have no repeated resource information. Thus, the frequency domain information and Q value of the resource information 2 and the resource information 1 are effective, and the round information and time domain information are effective.

[0340] That is, the resource information of the resource type configured later can cover the resource information of the resource type configured earlier. In the case that the resource information 1 includes the resource type not configured by the resource information 2, the resource information of the resource type not configured by the resource information 2 in the resource information 1 can be effective in cooperation with the resource information 2.

[0341] In other implementations, the resource information can also be configured through other messages (such as a round start message, a time slot start message, a Repaging message, etc.) other than the Paging message. In specific implementations, the above-mentioned covering of the resource type and / or the cooperative effectiveness of the resource type can also be followed.

[0342] For example, the card reading device can configure resource information 2 to the AIoT device through a round start message 2. The resource information 2 can take effect within a round corresponding to the round start message 1. The interaction logic performed within the round corresponding to the round start message 1 is also the interaction logic performed within the flow corresponding to the round start message 1.

[0343] Therefore, the AIoT device can communicate with the card reading device using the resource information 2 within the round corresponding to the round start message 1.

[0344] In some implementations, in the case that no resource information is carried in a next round start message 3 after the round start message 2, the resource information 2 sent by the round start message 2 continues to take effect within a round corresponding to the round start message 3. In this way, the AIoT device can continue to communicate with the card reading device using the resource information 2 within the round corresponding to the round start message 3.

[0345] For example, the card reading device can configure resource information 3 to the AIoT device through a time slot start message 3. The resource information 3 can take effect within a time slot corresponding to the time slot start message 3. The interaction logic performed within the round corresponding to the round start message 1 is also the interaction logic performed within the flow corresponding to the round start message 1.

[0346] Therefore, the AIoT device can communicate with the card reading device using the resource information 3 within the time slot corresponding to the time slot start message 3.

[0347] In some implementations, in the case that no resource information is carried in a next time slot start message 4 after the time slot start message 3, the resource information 3 sent by the time slot start message 3 continues to take effect within a time slot corresponding to the time slot start message 4. In this way, the AIoT device can continue to communicate with the card reading device using the resource information 3 within the time slot corresponding to the time slot start message 4.

[0348] In some other embodiments of the present application, the card reading device can use two or more of the Paging message, the round start message, and the time slot start message to configure resource information to the AIoT device.

[0349] For example, the card reading device can configure resource information to the AIoT device through a Paging message and a round start message.

[0350] In some implementations, the resource information 1 carried in the Paging message takes effect within a round corresponding to the round start message 1, and no round start message is carried in the round start message 1.

[0351] The AIoT device can use the resource information 1 to communicate with the card reading device in a round corresponding to the message 1 of the round start.

[0352] In some other implementations, the resource information 1 is carried in the Paging message, and the resource information 2 is carried in the message 2 of the round start, and the resource information 2 takes effect in a round corresponding to the message 2 of the round start.

[0353] The AIoT device can use the resource information 2 to communicate with the card reading device in a round corresponding to the message 2 of the round start.

[0354] It can be understood that, in the case that the resource information 2 only includes part of the resource configuration, at least part of the resource information 1 takes effect with the resource information 2. The at least part of the resource information 1 includes resources in the resource 1 that are not included in the resource 2.

[0355] For example, the card reading device configures the resource information 1 to the AIoT device through the Paging message, and the resource information 1 includes time domain information and frequency domain information 1. In the process corresponding to the Paging message, the card reading device configures the resource information 2 to the AIoT device through the message 1 of the round start. The resource information 2 includes frequency domain information 2.

[0356] In this way, in a round corresponding to the message 1 of the round start, the time domain information configured by the Paging message and the frequency domain information 2 configured by the resource information 2 take effect. Correspondingly, the AIoT device can communicate with the card reading device in the round corresponding to the message 1 of the round start through the configured time domain information and frequency domain information 2.

[0357] For example, the card reading device configures the resource information 1 to the AIoT device through the Paging message, and the resource information 1 includes frequency domain information 1. In the process corresponding to the Paging message, the card reading device configures the resource information 2 to the AIoT device through the message 1 of the round start. The resource information 2 includes time domain information and Q. The resource information 1 and the resource information 2 constitute a complete resource configuration, and the AIoT device can use the frequency domain information 1, the time domain information, and Q to communicate with the card reading device in a round corresponding to the message 1 of the round start through the configured resource.

[0358] In the above examples, the card reading device configures the resource information to the AIoT device through the paging message and the message of the round start.

[0359] In some other embodiments, the card reading device can also configure the resource information to the AIoT device through the Paging message and the time slot start message, or the round start message and the time slot start message, or the Paging message, the round start message, and the time slot start message.

[0360] For example, the card reading device can configure the frequency domain resource information to the AIoT device in the Paging message. The card reading device can also configure the time domain resource information to the AIoT device in the message of the start of the round. The card reading device can also configure the frequency domain resource information to the AIoT device in the message of the start of the time slot.

[0361] In this application, when the card reading device configures resource information through multiple messages, the last sent resource information takes effect or multiple message configured resource information takes effect jointly. The AIoT device can communicate with the card reading device through the updated resource information.

[0362] The above embodiments detail the specific implementation of the card reading device configuring resource information to the AIoT device. The AIoT device and the card reading device can synchronize resource configuration through any of the above resource configuration forms, and then communicate between devices through the configured resources.

[0363] In some cases, the card reading device may not be able to page all AIoT devices through a Paging process when it receives a CN request. In this way, there will be some AIoT devices that cannot complete random access with the card reading device in this Paging process.

[0364] For example, referring to FIG. 10, a schematic diagram of an AIoT communication scenario is shown. In the example of FIG. 10, the card reading device is taken as an example of a UE. The UE can include multiple AIoT devices, such as AIoT device 1, AIoT device 2, and AIoT device 3.

[0365] As shown in the interaction flow of FIG. 1, in the scenario shown in FIG. 10, the card reading device can send a Paging message (such as message 103) to each AIoT device after receiving message 102 (i.e., receiving a CN request).

[0366] In some implementations, one or more of AIoT device 1, AIoT device 2, and AIoT device 3 can not be able to complete random access with the card reading device in a Paging process.

[0367] For example, AIoT device 1 does not normally receive the Paging message due to low battery or other issues. In the case that AIoT device 1 does not receive the AIoT paging message, it will not trigger random access to the card reading device, as described in conjunction with FIG. 3.

[0368] For example, the card reading device configures Q1 and Q2 for the AIoT device 2 and the AIoT device 3 respectively. The AIoT device 2 and the AIoT device 3 calculate the time slots for replying according to the respective Q values. In this way, the AIoT device 2 and the AIoT device 3 send Msg1 to the card reading device in the same time slot. Further, the card reading device (such as UE) receives multiple Msg1 in the same time slot, which causes the problem that the UE cannot parse. In the case that the AIoT device 2 or the AIoT device 3 performs random access through 2-step CBRA as shown in FIG. 5 or 3-step CBRA as shown in FIG. 6, or performs random access through CFRA as shown in FIG. 4, and the CFRA includes Msg2, since the UE cannot parse the Msg1 of the AIoT device 2 and the AIoT device 3, the UE cannot send Msg2 to the AIoT device 2 and the AIoT device 3, which further causes the random access of the AIoT device 2 and the AIoT device 3 to the card reading device to fail.

[0369] In this case, in order to realize random access to all AIoT devices, the card reading device can perform the process of repeated Paging to the AIoT devices. For example, the card reading device can initiate the first paging to each AIoT device through an initial Paging message in the case of receiving the same CN request. Thereafter, the card reading device can initiate the second or more times of paging to one or more AIoT devices through a repeated Paging message. The CN request associated with the repeated Paging message and the CN request associated with the initial Paging message are the same.

[0370] In the following description, in order to distinguish the initial Paging message and the repeated Paging message, the initial Paging message is denoted as a Paging message, and the repeated Paging message is denoted as a Repaging message. It should be noted that the distinction of the names is only for convenience of description, and in actual implementation, whether the name and / or content of the repeated Paging message is consistent with the initial Paging message is not limited.

[0371] In some embodiments of the present application, the Repaging message can include the same Paging ID as the Paging message. For example, the paging message can carry the paging ID corresponding to the CN request. The Paging ID corresponding to the same CN request can also be included in the Repaging message.

[0372] In this way, the AIoT device can determine that it has not entered the process of a new CN request according to the reception of the Repaging message carrying the same Paging ID.

[0373] In different embodiments of the present application, the Paging message and the Repaging message can have different configurations.

[0374] In some embodiments, an identification bit can be included in the Paging message and the Repaging message. When the identification bit is A, it means that the message is a Paging message. For example, A is 0. When the identification bit is B, it means that the message is a Repaging message. For example, B is 1.

[0375] In this way, the AIoT device can determine that the received paging message is a Paging message according to the identification bit A. The AIoT device can determine that the received paging message is a Repaging message according to the identification bit B.

[0376] After the AIoT device determines that the Paging message or the Repaging message is received, the corresponding response can be performed.

[0377] For example, referring to FIG. 11, taking the example of distinguishing the Paging message and the Repaging message by the flag bit.

[0378] The card reading device can receive the CN request and perform S1101 to send message 111. The message 111 can be a Paging message. The message 111 can include ID 0 to indicate that the Paging ID is 0. The flag bit in the message 111 can be configured as 0 to indicate that the message 111 is an initial Paging message.

[0379] In this example, the AIoT device 1 can receive the message 111. The AIoT device 1 determines that the message 111 is an initial Paging message according to the flag bit 0. Correspondingly, the AIoT device 1 can respond to the message 111. For example, the AIoT device can perform S1102 to send Msg1 to the card reading device, thereby triggering the random access process between the card reading device.

[0380] Taking the example that the AIoT device 1 successfully performs random access after sending Msg1.

[0381] The card reading device can perform S1103 to send message 112. The message 112 can include ID 0 to indicate that the Paging ID is 0. The flag bit in the message 112 can be configured as 1 to indicate that the message 112 is a Repaging message.

[0382] In this example, the AIoT device 1 can receive the message 112. The AIoT device 1 determines that the message 112 is a Repaging message according to the flag bit being 1. The AIoT device 1 can determine not to respond to the Repaging message according to that the random access has succeeded.

[0383] Referring to FIG. 12, an interaction flow diagram between devices in a case where the random access according to the Paging message fails is provided.

[0384] As shown in FIG. 12, the card reading device can send the message 111 after receiving the CN request, performing S1201. The message 111 is similar to the message 111 in FIG. 11, carrying the ID 0 and the flag bit 0.

[0385] In some embodiments, the AIoT device 2 can not normally receive the message 111. In this way, the AIoT device 2 does not initiate a random access procedure to the card reading device. In other embodiments, the AIoT device 2 normally receives the message 111, but cannot send Msg1 to the card reading device due to low power. In other embodiments, as shown in FIG. 12, the AIoT device 2 can normally receive the message 111 and perform S1202 to send Msg1 to the card reading device.

[0386] Correspondingly, the card reading device can not normally receive Msg1, or the card reading device does not send a subsequent response (such as Msg2) to the AIoT device 2, or the card reading device sends Msg2 but the AIoT device 2 does not normally receive the Msg2. In this way, the AIoT device 2 fails in the random access in the Paging procedure.

[0387] Thereafter, the card reading device can perform S1203 to send the message 112. The message 112 is similar to the message 112 shown in FIG. 11. In the example of FIG. 12, the message 112 can carry the ID 0 and the flag bit 1.

[0388] In some implementations, the AIoT device 2 can determine that the message 112 is a Repaging message in the same CN request procedure as the message 111 according to receiving the message 112. Correspondingly, the AIoT device 2 can respond to the message 112 according to that the random access has not succeeded. For example, the AIoT device 2 can perform S1204 to send Msg1 to the card reading device to attempt random access to the card reading device. In this way, the AIoT device 2 can complete the random access to the card reading device in the Paging procedure of the message 112.

[0389] In this way, based on the scheme provided in FIG. 11 and FIG. 12, the card reading device can distinguish the Paging message and the Repaging message by carrying the message with the same PagingID and setting different flag bits in the message.

[0390] Correspondingly, the AIoT device can respond to the Repaging message with the flag bit being 1 according to that the flag bit of the received message is 1 and the random access fails or the random access has not been performed (for example, the AIoT device does not normally receive the message 111). The AIoT device can perform random access to the card reading device in the Repaging process, so as to be able to complete the random access to the card reading device in the Repaging process.

[0391] In the above examples, the Paging message and the Repaging message have different flag bits as an example. In other embodiments, the Paging message and the Repaging message can have different paging types. The messages with different paging types can have different data formats and / or different data lengths and / or different data contents and / or different message types.

[0392] In some embodiments, the messages with different paging types can be distinguished by identification information. The identification information can be used to identify the message type.

[0393] Taking that the identification information includes a 2-bit flag bit as an example. In some implementations, the identification information of the Paging message can include 00, and the identification information of the Repaging message can include 01.

[0394] In other embodiments, the identification information can also be used to represent other messages. For example, the identification information of Msg2 can be 10. For another example, the identification information of Msg4 can be 11.

[0395] As an example, when the device parses the data packet, the data packet subheader or the control information part is parsed first, wherein the control information can be included in the control data packet. Including the paging type, the flag bit or the paging process ID in the data packet subheader or the control information part can make the device avoid parsing the content of the data part such as the resource information when it is determined that it is not necessary to reply. The paging type (such as the above identification information) of the message and / or the paging process ID can be configured in the control data packet subheader or included in the control information.

[0396] For example, corresponding to the examples in FIG. 11 or FIG. 12, a field indicating that the paging type of the message 111 is initial paging can be included in the control packet subheader of the message 111. Correspondingly, after receiving the message 111, the AIoT device can parse the subheader of the message 111, and then determine that the message 111 is an initial paging message (Paging message). The AIoT device can respond to the message 111 according to the scheme shown in FIG. 11 or FIG. 12.

[0397] For another example, a field indicating that the paging type of the message 112 is repeated paging can be included in the control information of the message 112. Correspondingly, after receiving the message 112, the AIoT device can parse the subheader of the message 112, and then determine that the message 112 is a Repaging message. The AIoT device can determine whether to respond to the message 112 according to the scheme shown in FIG. 11 or FIG. 12.

[0398] As described above, the Paging message and the Repaging message can carry the same Paging ID. In some embodiments of the present application, the Paging ID can be configured in the control data packet subheader together with the paging type field. In this way, the AIoT device can determine that the message is a Paging message or a Repaging message by parsing the control data packet subheader. Taking the case where the AIoT device receives a Repaging message as an example. In the case where the AIoT device does not respond to the Repaging message, the AIoT device does not need to parse the subsequent data (such as control data packets) of the subheader of the message. This can save the power consumption of the AIoT device.

[0399] The schemes provided in FIG. 11 to FIG. 12 above, and subsequent paging type related schemes, provide the sending logic of the Paging message and the Repaging message corresponding to the same CN request.

[0400] In the above examples, the Paging message and the Repaging message can include the same Paging ID, and a flag bit or a paging type field indicating that the message is initial paging or repeated paging.

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

[0402] In other embodiments, the card reader can send an end indication to the AIoT device when the Paging process is complete. For example, consider the interaction flow shown in Figure 7. The card reader can send this 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 procedure corresponding to the Paging process has not been 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).

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

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

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

[0406] In the present application, in different device interaction modes, the repeated paging message (i.e., Repaging message) can be configured to be sent at different time.

[0407] The following are illustrated respectively.

[0408] In some embodiments, the card reading device can send a Repaging message to the AIoT device after the Paging process ends.

[0409] For example, referring to FIG. 13, another kind of interaction process schematic diagram provided by the embodiments of the present application is shown.

[0410] In the example of FIG. 13, the AIoT device and the card reading device communicate through the interaction mode shown in FIG. 7. As described above in FIG. 7, in this interaction mode, the card reading device can send a Paging message to the AIoT device in the case of receiving a CN request from the core network device. In this Paging process, the card reading device can send one or more round start messages and one or more time slot start messages to the AIoT device.

[0411] As shown in FIG. 13, the process can include:

[0412] S1301, the core network device sends a CN request to the card reading device.

[0413] For example, the CN request can include an inventory command and / or a downlink command (DL command). Thus, through the CN request, the core network device can issue the current AIoT communication corresponding service to the card reading device.

[0414] In some embodiments, the information of the AIoT device participating in the AIoT communication can also be included in the CN request.

[0415] For example, the CN request includes an inventory command. In this example, the device ID of the AIoT device participating in the inventory, or the device ID of the AIoT device not participating in the inventory, or the group ID of the AIoT device participating in the inventory, or the group ID of the AIoT device not participating in the inventory can be included in the CN request.

[0416] In some embodiments, the information indicating the RA type can also be included in the CN request.

[0417] For example, the CN request can indicate, by the RA type, that the AIoT device performs random access by CFRA or 2-step CBRA or 3-step CBRA.

[0418] S1302, the card reading device sends a message 131 to the AIoT device.

[0419] For example, the message 131 can include a Paging message. In some embodiments, the Paging message in the message 131 can be an initial Paging message. Thus, by the initial Paging message, an initial Paging procedure is started, and the AIoT device is paged for the first time.

[0420] In the present example, the Paging message can include at least one of the following, in combination with the foregoing description:

[0421] shared resources and / or dedicated resources configured for AIoT communication; information of the RA type; downlink command indication (DL command) information; paging procedure ID (Paging ID); device ID needs to receive paging or ignore paging; card reading device ID; failed device receiving paging indication; information indicating whether there is a duplicate message; type information of the AIoT device.

[0422] S1303, the card reading device sends a round start message to the AIoT device.

[0423] S1304, the card reading device sends a slot start message to the AIoT device.

[0424] In the present example, referring to the description in FIG. 7, each Paging procedure can include one or more rounds. At the start of each round, the card reading device can send a round start message to the AIoT device.

[0425] In each round, one or more slots can be included. At the start of each slot, the card reading device can send a slot start message to the AIoT device.

[0426] As described above, the card reading device can configure resource information to the AIoT device through the Paging message and / or the round start message and / or the slot start message.

[0427] The resource information can include at least one of the following: time domain information, frequency domain information, and Q value for AIoT communication.

[0428] The validity mechanism of the specific resource information is as described above, and will not be repeated here.

[0429] For the AIoT device, the AIoT device can communicate with the card reading device according to the configured resource information.

[0430] For example, the AIoT device can determine whether to respond to the Paging message according to the Paging message.

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

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

[0433] In this way, the AIoT device 1 can determine that it needs to respond to this paging process according to the fact that its own device ID is included in the Paging message and the Paging message indicates that it needs to receive paging.

[0434] In some implementations, the AIoT device 1 can determine its own time slot according to the Q value carried in the Paging message.

[0435] Therefore, the AIoT device 1 can attempt to establish AIoT communication with the card reading device according to the random access mode indicated by the RA type indicated by the Paging message when its own time slot arrives. For example, the AIoT device 1 can send Msg1 to the card reading device according to the random access mode indicated by the RA type according to the resource information configured by the card reading device when its own time slot arrives.

[0436] The specific implementation process is as described in the foregoing examples, which will not be described here.

[0437] For each AIoT device within the communication range of the card reading device, the AIoT device can perform random access to the card reading device when it needs to communicate with the card reading device according to the similar process described above.

[0438] After all rounds and time slots end, the initial Paging process ends. In some embodiments, the card reading device can send an end indication to the AIoT device when the initial Paging process ends.

[0439] It can be understood that in some embodiments, some AIoT devices that need to access the card reading device may fail to perform random access in the initial Paging process due to various reasons.

[0440] In this way, the card reading device can send a Repaging message to the AIoT device to initiate a paging process again (e.g., a Repaging process) so that the AIoT device can successfully establish a communication connection with the card reading device through random access.

[0441] In this example, the card reading device can send a Repaging message to the AIoT device when it needs to initiate a Repaging process after the initial Paging process ends.

[0442] In some embodiments, as shown in FIG. 13, the card reading device can determine that it needs to initiate a Repaging process according to a Repaging indication sent by the core network device. For example, the AIoT device that successfully performs random access in the Paging process can send D2R data to the card reading device according to steps B and / or C shown in FIG. 3. The card reading device can send the obtained D2R data to the core network device. In this way, the core network device can determine that there is an AIoT device that fails to perform random access according to the number of received D2R data. Correspondingly, the core network device can send a Repaging indication to the card reading device. In some implementations, the core network device can carry 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 indication.

[0443] In other embodiments, the card reading device can determine that it needs to initiate a Repaging process on its own according to random access failure in some time domain resources (e.g., time slots) and / or frequency domain resources (e.g., frequency points).

[0444] In other embodiments, the card reading device can determine that it needs to initiate a Repaging process on its own according to the number of D2R data received in the Paging process being inconsistent with the number of devices that need to be inventoried.

[0445] In this way, the card reading device can initiate a Repaging process for the AIoT device after the initial Paging process ends.

[0446] As shown in FIG. 13, the process can include:

[0447] S1305, the card reading device sends a message 132 to the AIoT device.

[0448] For example, the message 132 can include a Repaging message. The Repaging message can carry the same Paging ID as the Paging message. By sending the Repaging message, the card reading device can trigger a Repaging process.

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

[0450] shared resources and / or dedicated resources configured for AIoT communication; information of RA type; downlink command indication (DL command) information; paging flow ID (Paging ID); device ID needs to receive paging or ignore paging; card reading device ID; failed Device receiving paging indication; information indicating whether there is a duplicate message; type information of AIoT device.

[0451] In some implementations, the Repaging message can also carry M-time information. The M-time information can indicate that the Repaging message is the Mth sent Paging or Repaging message. Wherein, M is an integer greater than or equal to 1.

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

[0453] Taking the case that the content of the Repaging message is the same as that of the Paging message.

[0454] It can be understood that in some cases, the device ID indicated by the core network device to participate in AIoT communication is not visible to the card reading device. In this way, the card reading device can encapsulate the NAS PDU from the core network device in the Repaging message. The Repaging message obtained thereby can be consistent with the content of the Paging message.

[0455] Taking the case that the content of the Repaging message is different from that of the Paging message.

[0456] In this example, the card reading device is visible to the device ID. In this way, the card reading device can determine the device ID that needs to participate in paging in the Repaging flow according to the device ID of the AIoT device that has successfully accessed in the Paging flow and all device IDs indicated by the CN request to participate in AIoT communication. The device that needs to participate in paging in the Repaging flow can be a device that fails to access in the Paging flow or a device ID that the card reading device does not receive a response in the Paging flow.

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

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

[0459] In some embodiments of the present application, the Repaging message can include information about the resources in the Paging procedure in which a conflict occurs or a random access message (such as Msg1, Msg3, etc.) is not received. Among them, the information about the conflict includes information about the round, time slot, frequency point, etc. of the resources in which two or more random access messages are received at the same time.

[0460] For example, the relevant information can include at least one of the following: information about the round in which a conflict occurs or a random access message is not received, information about the time slot in which a conflict occurs or a random access message is not received, and information about the frequency point in which a conflict occurs or a random access message is not received.

[0461] S1306, the card reading device sends a message about the start of the round to the AIoT device.

[0462] S1307, the card reading device sends a message about the start of the time slot to the AIoT device.

[0463] It should be noted that in this example, the resource configuration method in the Repaging procedure can refer to the Paging procedure.

[0464] In some embodiments, the card reading device can configure resource information to the AIoT device through the Repaging message and / or the message about the start of the round in the Repaging procedure and / or the message about the start of the time slot in the Repaging procedure.

[0465] In another embodiment, the card reading device can also not configure resource information to the AIoT device in the Repaging procedure. In this way, in this Repaging procedure, the AIoT device and the card reading device can continue to use the resource information that takes effect in the Paging procedure.

[0466] When receiving the same CN request, the last configured resource information takes effect.

[0467] In different embodiments of the present application, the AIoT device can perform a response in the Repaging procedure according to different rules.

[0468] For example, in some embodiments, the card reading device instructs the AIoT device to perform random access through CFRA. In combination with the example in FIG. 4, the card reading device sends message 302 (Msg2) to the AIoT device after receiving message 301 (Msg1).

[0469] The AIoT device can determine to respond to the Repaging message according to not receiving Msg2 in the Paging procedure.

[0470] It can be understood that, in the Paging procedure, the AIoT device performs random access by CFRA, and in the case that Msg2 is not received, CFRA failure corresponds. In this way, the AIoT device can attempt random access again in the Repaging procedure after receiving the Repaging message.

[0471] In some embodiments, the card reading device instructs the AIoT device to perform random access by 2-setp CBRA.

[0472] In combination with the example in FIG. 5, the card reading device sends message 402 (Msg2) to the AIoT device after receiving message 401 (Msg1).

[0473] In some implementations, in the case of successful competition, the card reading device sends an acknowledgment (ACK) message to the AIoT device through Msg2. In this way, the AIoT device can determine to respond to the Repaging message according to the fact that Msg2 is not received.

[0474] In some implementations, in the case of successful competition, the card reading device sends an acknowledgment (ACK) message to the AIoT device through Msg2; in the case of failed competition, the card reading device sends a non-acknowledgment (NACK) message to the AIoT device through Msg2. In this way, the AIoT device can determine to respond to the Repaging message according to the fact that Msg2 is not received, or according to the fact that Msg2 carrying the NACK message is received.

[0475] In some implementations, in the case of failed competition, the card reading device sends a non-acknowledgment (NACK) message to the AIoT device through Msg2. In this way, the AIoT device can determine that the Repaging message can be responded to according to the fact that Msg2 is received.

[0476] In the above examples, the AIoT device determines whether to respond to the Repaging message according to whether Msg2 is received.

[0477] In some embodiments, access resource information can be included in the Repaging message. The AIoT device can also determine whether to respond to the Repaging message in combination with the access resource information. The access resource information can be resource information in which a device successfully accesses in the last Paging procedure, or resource information in which a device fails to access, or resource information in which no device accesses.

[0478] For example, in the case of failed competition, the card reading device sends a non-acknowledgment (NACK) message to the AIoT device through Msg2.

[0479] In some implementations, the access resource information indicates resource information of successful random access in the Paging procedure. In this way, the AIoT device can determine to respond to the Repaging message according to that the Msg2 carrying the NACK information is received, or the resource used by the AIoT device is not included in the resource information carried in the access resource information.

[0480] In some other implementations, the access resource information indicates resource information of failed random access in the Paging procedure. In this way, the AIoT device can determine to respond to the Repaging message according to that the Msg2 carrying the NACK information is received, or the resource used by the AIoT device is included in the resource information carried in the access resource information.

[0481] In some other embodiments, taking the case that the card reading device indicates the AIoT device to perform random access through 3-step CBRA as an example.

[0482] In combination with the example in FIG. 6, the card reading device can send the message 502 (Msg2) to the AIoT device after receiving the message 501 (Msg1). The random number corresponding to the AIoT device can be carried in the Msg1. In the case of successful contention, the same random number as in the Msg1 can be carried in the Msg2.

[0483] In this scenario, in some implementations, the AIoT device can determine to respond to the Repaging message according to that the Msg2 is not received.

[0484] In some other implementations, as illustrated in FIG. 6, the AIoT device can send the device ID to the card reading device in the message 503 (Msg3). Taking the case that the card reading device sends the Msg4 to the AIoT device after receiving the Msg3 as an example.

[0485] In this example, the AIoT device can determine whether to respond to the Repaging message according to the access resource information in the Repaging message in the case that the Msg4 is not received after the message 503 is sent.

[0486] In combination with the above description of the 2-step CBRA scenario. In this example, the AIoT device can determine to respond to the Repaging message according to that the Msg4 is not received, or the Msg4 carrying the NACK is received, and the resource information used by the AIoT device in the Paging procedure corresponds to failed random access. The AIoT device can determine the resource information of successful or failed random access in the Paging procedure according to the access resource information in the Repaging message.

[0487] In this way, in different RAtype scenarios, the AIoT device can determine whether random access fails in the Paging procedure according to the above rules, and further respond to the Repaging message in the case of random access failure.

[0488] In some other cases, the AIoT device can not be able to or in time to determine whether random access is successful.

[0489] For example, taking the case that the card reading device instructs the AIoT device to perform random access through CFRA as an example. In some cases, the AIoT device can perform S302 to send Msg1 to the card reading device, and the card reading device will not respond to the Msg1. That is, the AIoT device completes the random access based on CFRA after sending Msg1. Since the card reading device will not send Msg2 to the AIoT device in the case of successful or failed random access, the AIoT device cannot determine whether random access is successful in the Paging procedure.

[0490] For example, taking the case that the card reading device instructs the AIoT device to perform random access through 3-step CBRA as an example. In some cases, the AIoT device can perform S502-S504 to interact with the card reading device for Msg1, Msg2 and Msg3. The device ID is sent to the card reading device in Msg3. The card reading device will not respond to the Msg3. In this way, since the card reading device will not send Msg4 to the AIoT device in the case of successful or failed random access, the AIoT device cannot determine whether random access is successful in the Paging procedure.

[0491] Correspondingly, the AIoT device can determine whether to respond to the Repaging message according to one or more of the following.

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

[0493] Correspondingly, the AIoT device can determine to respond to the Repaging message according to the resources used in the last round (i.e., in the Paging procedure), including the resources that have conflicts or have not received random access messages (such as Msg1, Msg3, etc.) in the case of receiving the Repaging message.

[0494] In a case that the AIoT device receives the Repaging message, the AIoT device can determine not to respond to the Repaging message according to the resources used in the last round (i.e. in the Paging procedure), excluding the resources in which the random access message (such as Msg1, Msg3, etc.) is collided or not received.

[0495] For example, the time domain resource used by the AIoT device in the paging procedure corresponds to time slot 3. That is, the AIoT device initiates random access to the card reading device in time slot 3 in the Paging procedure (such as sending Msg1 in the time slot 3).

[0496] In a case that the resources in which the random access message is collided or not received included in the Repaging message includes the time slot 3, the AIoT device can determine to respond to the Repaging message according to the resources that have been used and included in the Repaging message.

[0497] In a case that the resources in which the random access message is collided or not received included in the Repaging message does not include the time slot 3, the AIoT device can determine not to respond to the Repaging message according to the resources that have been used and not included in the Repaging message.

[0498] In other embodiments, the AIoT device can determine whether to respond to the Repaging message according to the paging ID and / or flag bit or paging message type carried by the Repaging message.

[0499] For example, in a case that the AIoT device receives the message 132 in FIG. 13, the AIoT device can determine to respond to the Repaging message according to the Paging ID and / or flag bit or paging message type of the message 132 not being received.

[0500] It can be understood that in a normal case, the AIoT device can normally receive the paging message corresponding to the message 131 and the Repaging message corresponding to the message 132. In this way, the AIoT device can determine that the Paging ID corresponding to the Paging message carried in the message 131 has been received when receiving the message 132. In this way, the AIoT device can complete random access in the Paging procedure. If the AIoT device does not receive the Paging message, the Paging ID of the Repaging message in the message 132 is received for the first time. Then, since the random access cannot be performed without receiving the Paging message, the Repaging message can be executed after being received.

[0501] In some implementations, the AIoT device can determine whether to respond to the Repaging message according to whether the Paging ID of the Repaging message is received for the first time, without including the device ID and / or group ID in the Repaging message.

[0502] Correspondingly, in a case where the device ID and / or group ID are carried in the Repaging message and devices corresponding to the IDs are instructed to respond, the AIoT device can respond to the Repaging message according to whether the device ID of the AIoT device is included in the Repaging message.

[0503] In a case where the device ID and / or group ID are carried in the Repaging message and devices corresponding to the IDs are instructed not to respond, the AIoT device can not respond to the Repaging message according to whether the device ID of the AIoT device is included in the Repaging message.

[0504] In the example of FIG. 13, the Repaging procedure is initiated after the Paging procedure ends.

[0505] In some other implementations of the present disclosure, the Repaging procedure can also be performed in the Paging procedure.

[0506] For example, in some embodiments, the Repaging procedure can be triggered after the end of one round of the Paging procedure and the start of the next round.

[0507] Referring to FIG. 14, an example of an inter-device interaction procedure is shown. In the example of FIG. 14, the AIoT device and the card reading device communicate with each other in the manner shown in FIG. 8. In this example, within the same Paging procedure, the Paging information can indicate the start of paging and the start of the first round. After the end of the first round, the card reading device can send a Paging message (or a Repaging message) again to indicate the start of the second round.

[0508] As shown in FIG. 14, the scheme can include the following steps.

[0509] S1401. The core network device sends a CN request to the card reading device.

[0510] For example, the execution of S1401 can refer to S1301 in FIG. 13.

[0511] S1402, the card reading device sends a message 141 to the AIoT device.

[0512] For example, the message 141 can correspond to the message 131 in FIG. 13.

[0513] In this example, since the interaction mode shown in FIG. 8 is adopted, the message 141 can include a Paging message.

[0514] The Paging message can be used to trigger a Paging process, and can also be used to indicate the start of a new round. For example, the Paging message can indicate the start of a new round (such as the Nth round). N is an integer greater than or equal to 1.

[0515] In this example, the sending form and specific configuration content of the Paging message can refer to the description of FIG. 13.

[0516] S1403, the card reading device sends a message indicating the start of a time slot to the AIoT device.

[0517] In this way, the card reading device can instruct the AIoT device to communicate in the new round through S1402 to S1403 and the subsequent message indicating the start of a time slot.

[0518] Correspondingly, the AIoT device can determine whether to respond to the Paging message according to the reception of the Paging message. The specific implementation can refer to the description in FIG. 13.

[0519] In this example, in the case that the AIoT device responds to the Paging message, the AIoT device can adopt a corresponding random access mode according to the RA type configured by the card reading device, and send a Msg1 to the card reading device to perform random access to the card reading device when the corresponding time slot of the AIoT device arrives.

[0520] In the case that one round (such as the Nth round) ends, the card reading device can determine that Repaging is needed when the next round (such as the N+1th round) starts, and perform the following S1404.

[0521] In combination with the description in FIG. 13, in some implementations of this example, the card reading device can determine that Repaging is needed according to the Repaging indication sent by the core network device before the N+1th round starts. In other implementations, the card reading device can determine that Repaging is needed by itself before the N+1th round starts.

[0522] S1404, the card reading device sends a message 142 to the AIoT device.

[0523] For example, the card reading device can send the message 142 at the beginning of the next round (e.g., the N+1th round). The message 142 can include a Repaging message.

[0524] It can be understood that in combination with the interaction mode shown in FIG. 8, without Repaging, the card reading device can send a Paging message at the beginning of the next round to indicate that the new round of the AIoT device has started.

[0525] In this example, the card reading device can send a Repaging message at the beginning of the next round (e.g., the N+1th round) to perform repeated paging of the AIoT devices that failed random access or did not reply in the previous round (e.g., the Nth round) in the case where it is determined that there are AIoT devices that failed random access in the previous round (e.g., the Nth round).

[0526] Similar to the description in FIG. 13, in this example, the content of the Repaging message can be the same as or different from that of the Paging message. The Repaging message can carry the same PagingID as the Paging message.

[0527] Thus, by sending the message 142, the card reading device can indicate that the AIoT devices that failed random access in the Nth round perform random access to the card reading device again while triggering the N+1th round of paging. In this way, in the paging process of the N+1th round, the AIoT devices that actually participate in the paging can include the AIoT devices that perform first random access in the N+1th round and the AIoT devices that failed random access in the Nth round.

[0528] In some embodiments, the Repaging message can include information about the resources that failed or did not receive random access messages (e.g., Msg1, Msg3, etc.) in the previous Paging process (e.g., the Nth round).

[0529] In other embodiments, the Repaging message can include information indicating the device ID or group ID of the devices that failed or did not complete random access in the previous Paging process.

[0530] S1405. The card reading device sends a message indicating the start of a time slot to the AIoT device.

[0531] In this way, the AIoT device configured to perform the first random access in the N+1th round, and the AIoT device that fails to perform the random access in the Nth round, can perform the random access in the time slot corresponding to the AIoT device itself in the N+1th round according to the reception of the Repaging message. For example, the AIoT device can perform the random access to the card reading device in the time slot corresponding to the AIoT device itself in the N+1th round by CFRA as shown in FIG. 4, or 2-step CBRA as shown in FIG. 5, or 3-step CBRA as shown in FIG. 6. In some embodiments, the Repaging message can include the information of RAtype, so that the AIoT device can perform the corresponding random access according to the random access type indicated by the RA type in the Repaging message. In another embodiment, the Repaging message does not include the RA type, so that the AIoT device can perform the random access in the N+1th round according to the random access type indicated by the RA type carried in the Paging message or the Repaging message in the last round (such as the Nth round).

[0532] For example, the Repaging message indicates the device that needs to be repeatedly paged by carrying the device ID that fails or does not complete the random access in the last round (such as the Nth round).

[0533] The AIoT device can determine to respond to the Repaging message according to whether the device ID of the AIoT device is included in the Repaging message after receiving the Repaging message. Then, when the time slot of the AIoT device itself comes, the AIoT device can perform the random access of the corresponding type according to the RA type configured by the card reading device.

[0534] For example, the Repaging message indicates the device that needs to be repeatedly paged by carrying the device ID that succeeds or completes the random access in the Nth round.

[0535] The AIoT device can determine to respond to the Repaging message according to whether the device ID of the AIoT device is included in the Repaging message after receiving the Repaging message. Then, when the time slot of the AIoT device itself comes, the AIoT device can perform the random access of the corresponding type according to the RA type configured by the card reading device.

[0536] For example, the Repaging message indicates the device that needs to be repeatedly paged by carrying the information of the resource that appears conflict or does not receive the random access message (such as Msg1, Msg3, etc.).

[0537] The AIoT device can determine to respond to the Repaging message according to the resources used in the last round (e.g., the Nth round). Then, when the time slot of the AIoT device itself comes, the AIoT device can perform random access of the corresponding type according to the RA type configured by the card reading device.

[0538] Taking the Repaging message as an example, the Repaging message carries information about resources that have not appeared conflicts or have received random access messages (such as Msg1, Msg3, etc.).

[0539] The AIoT device can determine to respond to the Repaging message according to the resources used in the last round (e.g., the Nth round). Then, when the time slot of the AIoT device itself comes, the AIoT device can perform random access of the corresponding type according to the RA type configured by the card reading device.

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

[0541] If the Paging ID has been received, the AIoT device can determine that it has 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 according to the content in the Repaging message in the above implementation.

[0542] If the Paging ID has not been received, the AIoT device can be a device configured to perform first paging in the N+1th round, or the AIoT device can not have normally received the Paging message in the Nth round due to communication abnormalities. Thus, the AIoT device can determine to respond to the Repaging message. For example, when the time slot of the AIoT device itself comes, the AIoT device can perform random access of the corresponding type according to the RA type configured by the card reading device.

[0543] Thus, in the implementation of the scheme shown in FIG. 14, the Repaging process is embedded in different rounds to achieve repeated paging of the AIoT device.

[0544] It should be noted that in the example of FIG. 14, the resource configuration form in the Repaging corresponding round is similar to that in the foregoing example.

[0545] Exemplarily, the card reading device can configure resource information to the AIoT device in the Paging message and / or the Repaging message and / or the message of the start of a time slot.

[0546] In the same CN request, the resource information received by the AIoT device at the latest can cover the resource configuration received at an earlier time. Thus, the AIoT device can perform a response to the Repaging message through the updated resource configuration. Wherein, the AIoT device can determine that the Paging message and the Repaging message correspond to the same CN request through the same Paging ID carried by the two messages.

[0547] For example, the card reading device can configure resource information 1 to the AIoT device in the message 141. The card reading device can also configure resource information 2 to the AIoT device in the message 142. Taking the case that the resource information 2 and the resource information 1 are both configured with respective time domain information, frequency domain information and Q value as an example. The AIoT device can enable the resource information 2 in the round after the Repaging message (such as the N+1 round). In the case of needing to respond to the Repaging message, the card reading device is initiated through the resource information 2.

[0548] In the example of the above FIG. 13, the Repaging process is triggered after the Paging process ends. In the example of FIG. 14, the Repaging process is triggered after the end of a round.

[0549] In some other embodiments of the present application, the Repaging process can also be triggered and executed between time slots in a round.

[0550] Exemplarily, referring to FIG. 15, another flowchart of the interaction between devices is shown. In this example, the card reading device and the AIoT device communicate through the interaction mode shown in FIG. 7. In combination with the description in FIG. 7, the card reading device can send a Paging message to the AIoT device after receiving a CN request. In the Paging process, the card reading device can also send a message of the start of a round to indicate the start of a new round of the AIoT device. In each round, the card reading device can also send a message of the start of a time slot to indicate the start of a new time slot of the AIoT device.

[0551] As shown in FIG. 15, the scheme can include:

[0552] S1501, the core network device sends a CN request to the card reading device.

[0553] Exemplarily, the execution of S1501 can refer to S1301 in FIG. 13. Details are not repeated.

[0554] S1502, the card reading device sends a message 151 to the AIoT device.

[0555] In this example, the message 151 can correspond to the message 131 in FIG. 13. The message 151 can include a Paging message. For example, the Paging message can be used to trigger the Paging procedure.

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

[0557] S1503, the card reading device sends a round start message to the AIoT device.

[0558] In the Paging procedure, the card reading device can indicate that a new round has started for the AIoT device by sending a round start message.

[0559] For example, the card reading device can send the round start message after sending the message 151. The round start message can indicate that the Nth round has started for the AIoT device.

[0560] S1504, the card reading device sends a time slot start message to the AIoT device.

[0561] In combination with the description in FIG. 7, in the normal Paging procedure, the card reading device can send one or more time slot start messages in each round.

[0562] For example, the card reading device can send the time slot start message after sending the round start message. The time slot start message can be used to indicate that a new time slot has started for the AIoT device. In this example, the time slot start message in S1504 corresponds to the start of time slot 1.

[0563] In this way, the AIoT device can determine that time slot 1 has started according to the reception of the time slot start message. Before receiving the next time slot start message, the AIoT device can determine that it is currently in time slot 1 in the time domain.

[0564] Thus, in the case of its own time slot being time slot 1, the AIoT device can initiate random access to the card reading device through the random access mode corresponding to the RA type configured by the card reading device after receiving the round start message corresponding to S1503. For example, the AIoT device can send Msg1 to the card reading device.

[0565] S1505, the card reading device sends a message 152 to the AIoT device.

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

[0567] In an example, the message 152 can include a Repaging message. Similar to the previous embodiment, the content of the Repaging message can be the same as or different from the content of the Paging message.

[0568] In some embodiments, the card reading device can be visible to the device ID.

[0569] The card reading device can carry in the Repaging message the device ID or group ID that is not paged in time slot 1 and / or the previous time slot, or the device ID or group ID that fails to receive Msg1 or Msg3 in time slot 1 and / or the previous time slot. In this way, the AIoT device can respond to the Repaging message according to whether its device ID is included in the Repaging message.

[0570] For example, the AIoT device 1 is selected or configured to perform random access before time 1 of time slot 1. The card reading device can determine that the AIoT device 1 has not completed random access according to the failure to receive Msg1 or Msg3 of the AIoT device 1 when time 1 arrives. In this way, the card reading device can send a Repaging message including the device ID of the AIoT device 1 in this time slot 1. Correspondingly, the AIoT device 1 can receive the Repaging message in this time slot 1 and re-initiate random access to the card reading device according to the device ID of itself carried in the Repaging message. For example, the AIoT device 1 can send Msg1 to the card reading device again in time slot 1 after receiving the Repaging message.

[0571] In other embodiments, the card reading device can be invisible to the device ID.

[0572] The card reading device can carry in the Repaging message the information about the resources that have conflicts or fail to receive random access messages (such as Msg1, Msg3, etc.) in time slot 1 and / or the previous time slot. In this way, the AIoT device can respond to the Repaging message according to whether the resources used in the random access process it has initiated are included in the Repaging message 1.

[0573] For example, the Repaging message can carry the frequency domain information of the random access message (such as Msg1, Msg3, etc.) that has not been received or has a conflict. The Repaging message is sent in time slot 1.

[0574] Correspondingly, the AIoT device can respond to the Repaging message in time slot 1 if the frequency domain information used by the random access process initiated by the AIoT device itself is the same as the frequency domain information indicated in the Repaging message, and the time slot of the AIoT device itself is time slot 1.

[0575] If the frequency domain information used by the random access process initiated by the AIoT device itself is different from the frequency domain information indicated in the Repaging message, and / or the time slot of the AIoT device itself is not time slot 1, the AIoT device can respond to the Repaging message in time slot 1. If the Repaging message carries the group ID, it can also be determined whether to respond by determining whether the group ID is the same.

[0576] In combination with the foregoing description, in other embodiments, the card reading device can also carry the device ID or group ID that does not need to respond to the Repaging message in the Repaging message. In other embodiments, the card reading device can also carry the information of the resource that has not appeared conflict or has received the random access message in the Repaging message. The response logic of the AIoT device is the same as the corresponding examples described above, and will not be described here.

[0577] In this way, in time slot 1, the card reading device can implement repeated paging of the AIoT device that fails in random access by sending the Repaging message.

[0578] It should be noted that in the present example, the message sent after the Repaging message starting in time slot 1 of time slot 1 is taken as an example. In other embodiments, the Repaging message can also be used to indicate the AIoT device that a new time slot has started. In this way, at the start of time slot 1, the card reading device can no longer perform S1503, and directly perform S1504. Correspondingly, the AIoT device can determine that a new time slot has started according to the received Repaging message, and can also determine whether to respond to the Repaging message according to the above rules.

[0579] S1506, the card reading device sends a message indicating the start of a time slot to the AIoT device.

[0580] The message of time slot start in S1506 can indicate that a new time slot has started for the AIoT device. For example, the card reading device can indicate that time slot 2 has started, i.e., time slot 1 has ended, through the message of time slot start in S1506.

[0581] In some embodiments, similar to the example in S1505, the card reading device can indicate repeated paging for the corresponding AIoT device through sending a Repaging message in the time slot 2.

[0582] Thus, through the scheme example as shown in FIG. 15, the card reading device can indicate repeated paging for the AIoT device through the Repaging message in one or more time slots.

[0583] The above description of the scheme of sending the Repaging message in the time slot in FIG. 15 is based on the example of the device interaction mode as shown in FIG. 7. In other embodiments, referring to FIG. 16, the scheme implementation of sending the Repaging message in the time slot is described based on the example of the device interaction mode as shown in FIG. 8.

[0584] As shown in FIG. 16, the scheme can include:

[0585] S1601, the core network device sends a CN request to the card reading device.

[0586] For example, the step S1601 can correspond to S1501 in FIG. 15. The core network device can indicate the card reading device to perform the inventory processing or transmit the DL command through the CN request.

[0587] S1602, the card reading device sends a message 161 to the AIoT device.

[0588] For example, the execution of the step S1602 can refer to S1502 in FIG. 15.

[0589] In this example, the message 161 can correspond to the message 151 in the above example. The message 161 can include the Paging message. In some embodiments, the Paging message can include the Paging ID corresponding to the CN request.

[0590] It should be noted that in combination with the description in FIG. 8, the message 161 carrying the Paging message in the example of FIG. 16 can also be used to indicate the start of a new round for the AIoT device. For example, the message 161 can be used to indicate the start of the Nth round.

[0591] S1603, the card reading device sends a message of time slot start to the AIoT device.

[0592] For example, the card reading device can indicate the AIoT device that the time slot 1 starts by sending a time slot start message of S1603. Correspondingly, the AIoT device can determine that it is in the time slot 1 in the time domain after receiving the time slot start message and before receiving the next time slot start message.

[0593] In the time slot 1, according to the resource information configured by the card reading device, the AIoT device whose own time slot is time slot 1 can attempt to initiate a random access corresponding to the configured RA type to the card reading device.

[0594] S1604, the card reading device sends a message 162 to the AIoT device.

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

[0596] For example, in some embodiments, the Repaging message can include the device ID or group ID that has not replied in the time slot 1 and / or the previous time slot, and / or the device ID or group ID that fails to receive Msg1 and / or Msg3 in the time slot 1 and / or the previous time slot.

[0597] Correspondingly, the AIoT device can respond to the Repaging message according to whether its own device ID is included in the Repaging message.

[0598] The AIoT device can not respond to the Repaging message according to whether its own device ID is included in the Repaging message.

[0599] In other embodiments, the Repaging message can include the device ID or group ID that has replied in the time slot 1 and / or the previous time slot, and / or the device ID or group ID that successfully receives Msg1 and / or Msg3 in the time slot 1 and / or the previous time slot.

[0600] Correspondingly, the AIoT device can not respond to the Repaging message according to whether its own device ID is included in the Repaging message.

[0601] The AIoT device can respond to the Repaging message according to whether its own device ID is included in the Repaging message.

[0602] In some embodiments, the Repaging message can include information about the resources in time slot 1 and / or the preceding time slots in which the random access message (e.g., Msg1, Msg3, etc.) has not been received or has collided.

[0603] Correspondingly, the AIoT device can respond to the Repaging message in a case where the resource configuration used by the AIoT device for the random access procedure that has been initiated by the AIoT device is included in the Repaging message.

[0604] The AIoT device can not respond to the Repaging message in a case where the resource configuration used by the AIoT device for the random access procedure that has been initiated by the AIoT device is not included in the Repaging message.

[0605] For example, the Repaging message includes frequency domain information 1, and the Repaging message indicates that the random access message has not been received or has collided in the frequency domain information 1.

[0606] In this way, the AIoT device can respond to the Repaging message in a case where the time slot corresponding to the AIoT device is time slot 1, and the frequency point corresponding to the frequency domain information 1 (e.g., Msg1 sent through the frequency point corresponding to the frequency domain information 1) is used by the AIoT device for the random access procedure that has been initiated by the AIoT device. For example, the AIoT device can initiate the random access procedure (e.g., send Msg1) again to the card reading device according to the configured RA type in the time slot 1.

[0607] Correspondingly, the AIoT device can not respond to the Repaging message in a case where the time slot corresponding to the AIoT device is not time slot 1, or the frequency point corresponding to the frequency domain information 1 is not used by the AIoT device for the random access procedure that has been initiated by the AIoT device.

[0608] In some embodiments, the Repaging message can include information about the resources in time slot 1 and / or the preceding time slots in which the random access message (e.g., Msg1, Msg3, etc.) has been received or has not collided.

[0609] Correspondingly, the AIoT device can respond to the Repaging message in a case where the resource configuration used by the AIoT device for the random access procedure that has been initiated by the AIoT device is not included in the Repaging message.

[0610] The AIoT device can not respond to the Repaging message in a case where the resource configuration used by the AIoT device for the random access procedure that has been initiated by the AIoT device is included in the Repaging message.

[0611] S1605. The card reading device sends a time slot start message to the AIoT device.

[0612] In the scheme as shown in FIG. 16, taking the card reading device and the AIoT device communicating through the interaction mode as shown in FIG. 8 as an example, the Repaging triggering mechanism in the time slot is exemplified. In the scenario as shown in FIG. 16, each step can correspond to the step in FIG. 15, and the specific implementation can be mutually referred.

[0613] In addition, the resource configuration form used in the Paging process and the Repaging process as shown in FIG. 15 and FIG. 16 can also be the same as the way in the foregoing example.

[0614] For example, in the scheme implementation as shown in FIG. 15 or FIG. 16, the card reading device can configure resource information to the AIoT device through the Paging message and / or the Repaging message and / or the time slot start message. In the case that 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 reading device (such as sending Msg1, etc.).

[0615] Therefore, through the above embodiments, the access process of the AIoT device (such as the second device) to the card reading device (such as the first device) based on the initial message and the repeated message is exemplified.

[0616] In the scheme implementation provided by the foregoing embodiments, after receiving the Repaging message, the AIoT device can determine to respond to the Repaging message according to a preset rule. The preset rule can correspond to not accessing or not completing the access in the Paging process.

[0617] The specific determination of not accessing or not completing the access can be determined by the AIoT device according to whether the access is successful, or determined by the AIoT device according to the indication of the Reader, or determined by the AIoT device according to whether the Msg message in the Paging process is completed or whether the Msg indicates NACK.

[0618] In other embodiments, taking the device type of the AIoT device carried in the Paging message as an example, the AIoT device can also determine to respond to the Repaging message according to the device type of the AIoT device included in the Paging message and / or satisfying the foregoing preset rule.

[0619] In some embodiments, the AIoT device can also receive information indicating whether to respond to the Repaging message according to one or more of the following: indication in the Paging message, identification information of the first device, information indicating that the device with access failure receives the paging, information indicating whether there is a repeated message.

[0620] In addition, according to the timing of sending the Repaging message, the AIoT device can also flexibly adjust the timing of sleep, wake-up, charging and the like.

[0621] Taking the AIoT device responding to the Repaging message as an example.

[0622] For example, when the card reading device sends the Repaging message in the time slot, the AIoT device can not sleep / start charging immediately in the case of not accessing or not completing access, and wait to receive the Repaging message.

[0623] For another example, when the card reading device sends the Repaging message at the beginning of a new round, the AIoT device can not sleep / start charging immediately in the case of not accessing or not completing access, and wait to receive the Repaging message; or, the AIoT device can enter sleep in the case of not accessing or not completing access, and wake up before the beginning of the next round to receive the Repaging message.

[0624] For another example, when the card reading device sends the Repaging message after the end of the Paging process, the AIoT device can not sleep / start charging immediately in the case of not accessing or not completing access, and wait to receive the Repaging message; or, the AIoT device can enter sleep in the case of not accessing or not completing access, and wake up before the end of the Paging process to receive the Repaging message.

[0625] It can be understood that, in order to implement the above functions, the electronic device provided by the embodiments of the present application contains the corresponding hardware structure and / or software modules for executing each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed in the present text, the embodiments of the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. 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 the present application.

[0626] The embodiments of the present application can divide the functional modules of the electronic device according to the above method examples. For example, each functional module can be divided according to each function, or two or more functions can be integrated in one processing module. The integrated module can be realized in the form of hardware or in the form of a software functional module. It should be noted that the division of the modules in the embodiments of the present application is illustrative, and is only a logical functional division. When actually implemented, there can be another division manner.

[0627] For example, the same protocol layer is configured in the card reading device and the AIoT device.

[0628] In some embodiments, a media access control (MAC) layer can be arranged in the device.

[0629] The card reading device can configure the Paging message and / or the Repaging message in the format corresponding to the MAC PDU or the MAC CE. In some embodiments, the fields of the Paging ID and / or the indication bit for distinguishing the Paging message and the Repaging message in the Paging message and / or the Repaging message can be configured in the subheader of the MAC PDU or the MAC CE (MAC Control Element). In this way, the AIoT device can quickly and efficiently identify the Paging message or the Repaging message.

[0630] In another embodiment, an AIoT access layer (AS layer) can also be arranged on the MAC layer.

[0631] In this way, the card reading device can configure the Paging message and / or the Repaging message in the format indicated by the AS layer corresponding control data packet (referred to as AS CE). In some implementations, the Paging ID and / or the indication bit for distinguishing the Paging message and the Repaging message carried by the Paging message and / or the Repaging message can be configured in the subheader of the AS CE.

[0632] The integrated module can be realized in the form of hardware or in the form of a software functional module. It should be noted that the division of the modules in the embodiments of the present application is illustrative, and is only a logical functional division. When actually implemented, there can be another division manner.

[0633] Referring to FIG. 17, the embodiments of the present application further provide a schematic diagram of a chip system 1700. The chip system 1700 can include a processor 1701 and a communication interface 1702, which are configured to support the related devices (such as a card reading device or an AIoT device) to implement the functions involved in the above embodiments. In a possible design, the chip system further includes a memory configured to store the necessary program instructions and data of the electronic device. The chip system can be composed of a chip, or can include a chip and other discrete devices. It should be noted that, in some implementations of the present application, the communication interface 1702 can also be referred to as an interface circuit.

[0634] It should be noted that all related contents of each step involved in the above method embodiments can be cited to the function description of the corresponding function module, and will not be repeated here.

[0635] The embodiments of the present application further provide a network device. In some embodiments, the network device can be the card reading device in the above embodiments. The network device can be used to implement the technical solutions corresponding to the card reading device in any of the above method embodiments.

[0636] The embodiments of the present application further provide a device product. In some embodiments, the device product can be the AIoT device in the above embodiments. The device product can be used to implement the technical solutions corresponding to the AIoT device in any of the above method embodiments.

[0637] The embodiments of the present application further provide a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the method processes related to the card reader and / or the device in any of the above method embodiments are implemented. Specifically, the computer can be the card reading device or the AIoT device.

[0638] The embodiments of the present application further provide a computer program or a computer program product including a computer program. When the computer program is executed on a computer, the computer will implement the method processes related to the card reader and / or the device in any of the above method embodiments. Specifically, the computer can be the card reading device or the AIoT device.

[0639] It should be noted that the functions or actions or operations or steps etc. in the above embodiments can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the whole or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or include one or more data storage devices such as servers, data centers, etc. that can be integrated with the medium. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0640] Although the present application is described in conjunction with specific features and embodiments thereof, it is evident that many alternatives, modifications and combinations of features will be apparent to those skilled in the art in view of the foregoing description. Accordingly, the description and drawings are to be regarded as illustrative in nature and not as restrictive. The scope of the application is indicated by the appended claims, and all changes which come within the meaning and range of equivalents are intended to be embraced therein. It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application cover the modifications and variations of this application provided they come within the scope of the appended claims and their equivalents.

Claims

1. A communication method characterized by comprising: The method is applied to a first device, and the method comprises: sending a first message, the first message being used for a second device to initiate random access to the first device; sending a second message, the second message being used for 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 that the first device performs ambient Internet of Things (AIoT) communication with the second device.

2. The method of claim 1, wherein, The method further comprises: receiving a first request, the first request carrying a first flow ID.

3. The method of claim 1 or 2, wherein the first message and / or the second message comprises at least one of the following: shared resource and / or dedicated resource information, resource allocation type, downlink command indication information, second flow ID, information indicating receiving paging or ignoring paging, identification information of the first device, information indicating that a device with access failure receives paging, information indicating whether there is a repeated message, type information of the second device; the second flow ID corresponds to the first request.

4. The method of any one of claims 1-3, wherein the first message and / or the second message is configured with a first flag, and the first flag is used to indicate whether a message carrying the first flag is an initial message or a repeated message.

5. The method of claim 4, wherein the first flag of the first message indicates that the first message is the initial message; and the first flag of the second message indicates that the second message is the repeated message.

6. The method of any one of claims 1-5, wherein the first message is of a first type, and the second message is of a second type; the first type corresponds to an initial message, and the second type corresponds to a repeated message.

7. The method of claim 6, wherein the first message and the second message are both 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 of any one of claims 4-7, wherein the second flow ID, the first flag of the first message, or the identification information of the first message are included in a packet subheader or control information of the first message; and / or the second flow ID, the first flag of the second message, or the identification information of the second message are included in a packet subheader or control information of the second message.

9. The method of any one of claims 1-8, wherein the second message comprises at least one device ID or group ID corresponding to a device that has not accessed or has not completed access, or The second message includes unaccessed or uncompleted accessed resource information, the unaccessed or uncompleted accessed resource information indicates conflicting resource information and / or failed response receiving resource information and / or non-received response resource information; the resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value.

10. The method of any one of claims 1-9, wherein, The second message includes at least one device ID or group ID corresponding to a completed accessed device, or, The second message includes completed accessed resource information, the completed accessed resource information indicates received response resource information; the resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value.

11. The method of any one of claims 1-10, wherein, After sending the first message, the method further includes: sending the second message within a first time length; or sending the second message after the first time length; The first time length is a preset time length, and / or the first time length is the time length from the beginning of the first time slot to the end of the first time slot.

12. The method of claim 11, wherein, After sending the first message, the method further includes: sending a first time slot start message, the first time slot start message is used to indicate the beginning of the first time slot, and / or, After sending the first message, the method further includes: sending a second time slot start message, the second time slot start message is used to indicate the end of the first time slot.

13. The method of claim 11 or 12, wherein, The first message is used to indicate the beginning of a new round.

14. The method of claim 13, wherein, After sending the first message, the method further includes: sending a third message, the third message is used to indicate the beginning of a new round; The third message includes the first message, or the third message includes the second message.

15. The method of claim 11 or 12, wherein, After sending the first message, the method further includes: sending a first round start message, the first round start message is used to indicate the beginning of a first round.

16. The method of any one of claims 11-15, wherein, The sending of the second message includes: sending the second message after the end of all rounds and / or time slots corresponding to the first message.

17. The method of any one of claims 1-16, wherein, The method further includes: receiving Msg1, the Msg1 includes at least one of the following: upper layer data, a second flow ID, and a first random ID; and / or, receiving Msg3, the Msg3 includes at least one of the following: upper layer data and a flow ID; The upper layer data includes a device ID of the second device, the second flow ID corresponds to the first request, and the first random ID corresponds to the second device.

18. The method of claim 17, wherein, The first message and / or the second message comprises a resource allocation type; The resource allocation type indicates that the second device accesses the first device through a contention-free 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 (2-step CBRA); or The resource allocation type indicates that the second device accesses the first device through a three-step contention-based random access procedure (3-step CBRA).

19. The method of claim 18, wherein: The second message comprises the resource allocation type, and the resource allocation type indicates that the second device accesses the first device through CFRA; After the sending the second message, the method further comprises: receiving a Msg1 of the CFRA, the Msg1 of the CFRA comprising at least one of: the upper layer data, the second procedure ID; or The second message comprises the resource allocation type, and the resource allocation type indicates that the second device accesses the first device through 2-step CBRA; After the sending the second message, the method further comprises: receiving a Msg1 of the 2-step CBRA, the Msg1 of the 2-step CBRA comprising at least one of: the upper layer data, the second procedure ID; or The second message comprises the resource allocation type, and the resource allocation type indicates that the second device accesses the first device through 3-step CBRA; After the sending the second message, the method further comprises: receiving a Msg1 of the 3-step CBRA, the Msg1 of the 3-step CBRA comprising at least one of: the first random ID, the second procedure ID; sending a Msg2 of the 3-step CBRA, the Msg2 of the 3-step CBRA comprising a second random ID.

20. The method of any one of claims 1-19, wherein: The method further comprises: configuring, to the second device, resource information through an initial message, and / or a repetition message, and / or a round start message, and / or a slot start message, the resource information comprising at least one of: round information, time domain information, frequency domain information, Q value; wherein, in a case that multiple resource information is configured to the second device, updated resource information is used for random access of the second device to the first device.

21. The method of claim 20, wherein, The method further comprises: configuring, to the second device, first resource information and second resource information; in a case that the first resource information and the second resource information both comprise configuration of a first resource type, a first resource set is used for random access of the second device to the first device; the first resource set comprises the second resource information and resource configuration different from the first resource type in the first resource information; or The first resource information and the second resource information are configured with different resource types, and the second resource set is used for random access of 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 of claim 21, wherein, The first resource information is configured to the second device by: The first resource information is configured to the second device by the first message, a round start message, and / or a time slot start message; The second resource information is configured to the second device by: The second resource information is configured to the second device by a round start message, a time slot start message, and / or the second message.

23. A method of communication, comprising: The method is applied to a second device, and the method includes: Receiving a second message, the second message being used for the second device to initiate random access to a first device to facilitate environmental Internet of Things (AIoT) communication with the first device; Sending a fourth message, the fourth message being used for initiating random access to the second device.

24. The method of claim 23, wherein, Before receiving the second message, the method further includes: Receiving a first message, the first message being used for 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 indicating that the first device performs environmental Internet of Things (AIoT) communication with the second device; Sending a first random access message, the first random access message being used for random access to the first device.

25. The method of claim 24, wherein, 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 flow ID, information indicating receiving paging or ignoring paging, identification information of the first device, information indicating that the device receiving paging has access failure; Information indicating whether to support repeated messages; information indicating that the flow corresponding to the first message is ended, information indicating whether there is a repeated message, and type information of the second device; The second flow ID corresponds to the first request.

26. The method of claim 24 or 25, wherein, The first message and / or the second message is configured with a first flag bit, the first flag bit being used to indicate whether a message carrying the first flag bit is an initial message or a repeated message.

27. The method of claim 26, wherein, 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 repeated message.

28. The method of claim 24 or 25, wherein, The first message is of a first type, and the second message is of a second type; The first type corresponds to an initial message, and the second type corresponds to a repeated message.

29. The method of claim 28, wherein the first message and the second message are both configured with identification information, wherein the identification information of the first message indicates that the first message is of the first type, and wherein the identification information of the second message indicates that the second message is of the second type.

30. The method of any one of claims 26-29, wherein the second flow ID is included in a packet subheader or control information of the first message, a first flag bit of the first message, or identification information of the first message; and / or wherein the second flow ID is included in a packet subheader or control information of the second message, a first flag bit of the second message, or identification information of the second message.

31. The method of any one of claims 26-30, wherein, after receiving the second message, the method further comprises: determining, based on the second message, whether to respond to the first device; and sending the fourth message based on the determination.

32. The method of claim 31, wherein the determination of whether to respond to the second message is based on at least one of: whether the second flow ID included in the second message has not been received, and / or whether the second message is an initial message; or whether the second flow ID included in the second message has been received, and / or whether the second message is a repeated message; or whether the second flow ID included in the second message has not been received, and / or whether the second message is a repeated message, and wherein the determination of whether to respond to the second message is further based on a predetermined rule.

33. The method of claim 32, wherein the predetermined rule comprises: determining that a random access to the first device has not been initiated or has not been completed.

34. The method of claim 33, wherein the random access to the first device has not been initiated or has not been completed comprises at least one of: a failure to send or a failure to receive the Msgl and / or Msg3; and / or a failure to receive the Msg2; and / or a failure to receive the Msg4 or a reception of the Msg4 including a non-acknowledgement message.

31. The method of any one of claims 24-30, wherein, 35. The method of any one of claims 26-34, wherein, prior to receiving the second message, the method further comprises: sending the Msgl, the Msgl including at least one of: upper layer data, the second flow ID, and a first random ID; and / or sending the Msg3, the Msg3 including at least one of: upper layer data, and the flow ID; wherein the upper layer data includes a device ID of the second device, the second flow ID corresponds to the first request, and the first random ID corresponds to the second device.

36. The method of any one of claims 26-35, wherein the first message and / or the second message includes a resource allocation type, and wherein the resource allocation type indicates that the second device is to access the first device via a contention-free random access procedure (CFRA). ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ ​ 35. The method of claim 33 or 34, wherein, ​ ​ ​ ​ 36. The method of claim 35, wherein, ​ ​ The resource allocation type indicates that the second device accesses the first device through a two-step contention-based random access process 2-step CBRA; or The resource allocation type indicates that the second device accesses the first device through a three-step contention-based random access process 3-step CBRA.

37. The method of any one of claims 33-36, wherein The second message includes at least one device ID corresponding to a device that has not accessed or has not completed access, The random access to the first device has not accessed or has not completed access, including: The device ID of the second device is included in the second message; or The second message includes at least one device ID corresponding to a device that has completed access, The random access to the first device has not accessed or has not completed access, including: The device ID of the second device is not included in the second message; Or The second message includes at least one first group ID corresponding to a device that has not accessed or has not completed access, the first group ID corresponds to at least one device ID, and the at least one device ID corresponding to the first group ID includes at least one device ID corresponding to a device that has not accessed or has not completed access; The random access to the first device has not accessed or has not completed access, including: The device ID of the second device is included in the at least one device ID corresponding to the first group ID; or The second message includes at least one second group ID, and the second group ID includes at least one device ID of a device that has completed access, The random access to the first device has not accessed or has not completed access, including: The device ID of the second device is not included in the device ID corresponding to the second group ID; Or The second message includes resource information of a device that has not accessed or has not completed access; the resource information includes at least one of the following: round information, time domain information, frequency domain information, and Q value; The random access to the first device has not accessed or has not completed access, including: The resource information used by the second device when it last accessed the first device is included in the second message; or The second message includes resource information of a device that has completed access; The random access to the first device has not accessed or has not completed access, 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 of any one of claims 24-37, wherein After receiving the first message, the method further includes: receiving the second message within a first time duration; or receiving the second message after the first time duration; The first time duration is a preset time duration, and / or the first time duration is the duration from the start of the first time slot to the end of the first time slot.

39. The method of claim 38, wherein After receiving the first message, the method further includes: receiving a first time slot start message, the first time slot start message being used to indicate the start of the first time slot.

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

41. The method of claim 39, wherein, After receiving the first message, the method further includes: receiving a third message, the third message being used to indicate the start of a new round; The third message includes the first message, or the third message includes the second message.

42. The method of any one of claims 38-41, wherein, After receiving the first message, the method further includes: receiving a first round start message, the first round start message being used to indicate the start of a first round.

43. The method of any one of claims 38-42, wherein, The receiving the second message includes: receiving the second message after the end of all rounds and / or time slots corresponding to the first message.

44. The method of any one of claims 24-43, wherein, The method further includes: configuring resource information to the second device through an initial message, and / or a repeated 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, Q value; In the case of configuring multiple resource information to the second device, the updated resource information is used for the random access of the second device to the first device.

45. The method of claim 44, wherein, The method further includes: configuring first resource information and second resource information to the second device; the time of configuring the second resource information is later than the time of configuring the first resource information; When the first resource information and the second resource information both include a first resource type, a first resource set is used for the random access of the second device to the first device; The first resource set includes the second resource information and resource configurations different from the first resource type in the first resource information; Or, When the resource types configured by the first resource information and the second resource information are all different, a second resource set is used for the random access of 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, Q value.

46. The method of claim 45, wherein, The configuring the first resource information to the second device includes: configuring the first resource information to the second device through the first message, and / or a round start message, and / or a time slot start message; The configuring the second resource information to the second device includes: configuring the second resource information to the second device through a round start message, and / or a time slot start message, and / or the second message.

47. A communications device, characterized by The communication device is configured to implement the method of any one of claims 1-22; or, the communication device is configured to implement the method of any one of claims 23-46.

48. A communication system, characterized by The communication system comprises a first device for performing the method according to any one of claims 1-22 and a second device for performing the method according to any one of claims 23-46.

Images