Indication method, device, system, storage medium, and program product

By sending and receiving indication information during the random access process of IoT devices, the problem of distinguishing different service types by IoT devices is solved, communication performance and efficiency are improved, and resources and energy are saved.

WO2026232470A1PCT designated stage Publication Date: 2026-11-12BEIJING XIAOMI MOBILE SOFTWARE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/093710
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

IoT devices struggle to effectively distinguish between different service types during random access, leading to a decline in communication performance.

Method used

By sending and receiving indication information during random access, the message type is clearly defined so that IoT devices can process it appropriately according to the service type.

Benefits of technology

It improves the communication performance of IoT devices, optimizes business processing efficiency, and saves signaling resources and energy consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025093710_12112026_PF_FP_ABST
    Figure CN2025093710_12112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to an indication method, a device, a system, a storage medium, and a program product. The method comprises: sending, to a second device, a first message used for random access; and receiving a second message sent by the second device, the second message comprising first indication information, and the first indication information being used for indicating a type corresponding to the second message. In the method, in a process of accessing the second device, a first device can learn about the type on the basis of the first indication information in the second message, so that the first device can perform appropriate service processing on the basis of the type corresponding to the second message, thereby improving communication performance.
Need to check novelty before this filing date? Find Prior Art

Description

Indication methods, devices, systems, storage media and program products Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to indication methods, devices, systems, storage media, and program products. Background Technology

[0002] The power consumption problem of traditional devices is becoming increasingly prominent. Passive Internet of Things (Ambient-IoT) or A-IoT technology can effectively improve the power consumption problem of devices. A-IoT devices or A-IoT terminals are passive devices that support ambient power or obtain power from the environment. They can obtain energy by collecting radio waves, light, motion, heat or any other suitable power source in the environment, and have lower complexity, cost and maintenance costs. Summary of the Invention

[0003] How IoT devices should handle different service types during random access is a question that needs to be clarified.

[0004] This disclosure provides an indication method, apparatus, system, storage medium, and program product.

[0005] In a first aspect, embodiments of this disclosure provide an indication method, executed by a first device, the method comprising:

[0006] Send a first message for random access to the second device;

[0007] The device receives a second message sent by a second device. The second message includes first indication information, which is used to indicate the type of the second message.

[0008] Secondly, embodiments of this disclosure provide an indication method, executed by a second device, the method comprising:

[0009] Receive a first message for random access sent by the first device;

[0010] A second message is sent to the first device. The second message includes first indication information, which is used to indicate the type of the second message.

[0011] Thirdly, embodiments of this disclosure provide a communication device for performing the method described in the first or second aspect.

[0012] Fourthly, embodiments of this disclosure provide a communication system, including a first device and a second device, wherein,

[0013] The first device is configured to implement the method as described in the first aspect;

[0014] The second device is configured to implement the method as described in the second aspect.

[0015] Fifthly, embodiments of this disclosure provide a communication method executed by a communication system, the communication system including a first device and a second device, wherein the method includes:

[0016] The first device sends a first message for random access to the second device;

[0017] The second device sends a second message to the first device. The second message includes first indication information, which is used to indicate the type of the second message.

[0018] Sixthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0019] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0020] In a seventh aspect, an embodiment of this disclosure provides a program product comprising at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0021] In this embodiment of the disclosure, when the first device accesses the second device, it can know the type based on the first indication information in the second message, so that the first device can perform reasonable business processing based on the type corresponding to the second message and improve communication performance. Attached Figure Description

[0022] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.

[0023] Figure 1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0024] Figures 1B to 1F are schematic diagrams of the topology of a communication system provided according to embodiments of the present disclosure;

[0025] Figure 1G is a schematic diagram of RFID provided according to an embodiment of the present disclosure;

[0026] Figures 2A to 2D are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;

[0027] Figures 3A to 3E are exemplary interactive schematic diagrams of the method provided according to embodiments of the present disclosure;

[0028] Figure 4A is a schematic diagram of the structure of a first device according to an embodiment of the present disclosure;

[0029] Figure 4B is a schematic diagram of the structure of a second device according to an embodiment of the present disclosure;

[0030] Figure 5A is a schematic diagram of a communication device according to an embodiment of the present disclosure;

[0031] Figure 5B is a schematic diagram of a chip according to an embodiment of the present disclosure. Detailed Implementation

[0032] This disclosure provides an indication method, apparatus, system, storage medium, and program product.

[0033] In a first aspect, embodiments of this disclosure provide an instruction method executed by a first device, the method comprising:

[0034] Send a first message for random access to the second device;

[0035] The device receives a second message sent by a second device. The second message includes first indication information, which is used to indicate the type of the second message.

[0036] In the above embodiments, during the process of the first device accessing the second device, the first device can know the type based on the first indication information in the second message, so that the first device can perform reasonable business processing based on the type corresponding to the second message and improve communication performance.

[0037] In conjunction with the embodiments of the first aspect, in some embodiments, the first indication information is used to indicate that the type corresponding to the second message is a first type or a second type, wherein the first type corresponds to inventory and command, and the second type corresponds to inventory only.

[0038] In the above embodiments, the type of the second message is directly indicated by the first indication information, which effectively distinguishes the second message under the inventory and command process and the inventory-only process. Thus, the first device can perform corresponding processing according to the corresponding service type, ensuring service processing efficiency and improving communication performance.

[0039] In conjunction with the embodiments of the first aspect, in some embodiments, the second message includes at least one temporary identifier, wherein each of the at least one temporary identifier corresponds to a first device that successfully sent the first message; wherein the type corresponding to the second message is a first type.

[0040] In the above embodiments, the temporary identifier corresponding to the first device can be indicated by the second information, so that in the corresponding business processing of the first type, the terminal can communicate based on the temporary identifier, ensuring the efficiency of business processing under inventory and command flow.

[0041] In conjunction with the embodiments of the first aspect, in some embodiments, the second message does not include at least one temporary identifier, wherein each of the at least one temporary identifier corresponds to a first device that successfully sent the first message; wherein the type corresponding to the second message is a second type.

[0042] In the above embodiments, when the type is the second type, the second information may not include the temporary identifier corresponding to the first device, thus saving signaling resources.

[0043] In conjunction with the embodiments of the first aspect, in some embodiments, the first message includes a random number identifier corresponding to the at least one first device.

[0044] In the above embodiments, the first message includes at least one random number identifier corresponding to the first device. The random number identifier can be used to distinguish different first devices, so that the second device can determine the first device for random access based on the random number identifier, thereby improving the random access efficiency.

[0045] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0046] Before sending the first message, a first paging message is received from the second device. The first paging message is used to page multiple first devices for contention-based random access (CBRA).

[0047] After receiving the second message, a third message is sent to or resent to the second device, the third message containing the device identifier of the first device.

[0048] In the above embodiments, for CBRA, the first device can initiate random access in a timely manner based on the second message, thereby improving the access success rate of CBRA.

[0049] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0050] After sending or retransmitting the third message, if the first device still does not receive the second indication information until it receives the second paging message sent by the second device to trigger reconnection, it is determined that the third message was sent successfully.

[0051] The second paging message has the same service identifier as the first paging message, and the second indication information is used to indicate one or more first devices that need to be reconnected.

[0052] In the above embodiments, the first device can determine whether the third message has been successfully sent so as to perform appropriate processing, such as determining the timing of releasing the relevant identifier, which is beneficial to saving equipment resources and energy consumption.

[0053] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0054] Upon receiving the second paging message, the random number identifier is released.

[0055] In the above embodiments, the terminal releases the original random number identifier at an appropriate time, which can save resources and is beneficial to energy saving of the device.

[0056] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0057] After sending or retransmitting the third message, the system receives a second indication message sent by the second device; wherein the second indication message is used to indicate one or more first devices that need to be reconnected.

[0058] In the above embodiments, the first device can perform reasonable processing based on the second instruction information, such as determining the timing of releasing the relevant identifier, which is beneficial to saving equipment resources and energy consumption.

[0059] In conjunction with the embodiments of the first aspect, in some embodiments, the second indication information does not contain the random number identifier of the first device, and the third message is successfully sent; or,

[0060] The second indication information contains the random number identifier of the first device, and the third message failed to be sent.

[0061] In the above embodiments, regardless of whether the third message is successfully sent, the first device can release the random number identifier in a timely manner, thereby saving resources.

[0062] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0063] Upon receiving the second instruction, the random number identifier is released.

[0064] In the above embodiments, the original random number identifier can be released in a timely manner upon receiving the second instruction information, which can save resources.

[0065] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0066] After sending or retransmitting the third message, a third paging message is received from the second device. The third paging message has a different service identifier than the first paging message and is used to paging the first device.

[0067] Upon receiving the third paging message, the random number identifier is released.

[0068] In the above embodiments, the original random number identifier can be released upon receiving a third paging message, saving resources and promoting energy efficiency. Furthermore, re-random access can be performed promptly based on the third paging message, thereby improving random access performance.

[0069] In conjunction with the embodiments of the first aspect, in some embodiments, after sending the third message, a fourth paging message sent by the second device is received, the fourth paging message having a different service identifier than the first paging message;

[0070] Upon receiving the fourth paging message, the random number identifier is released.

[0071] In the above embodiments, the original random number identifier can be released in a timely manner upon receiving the fourth paging message, thus saving resources.

[0072] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0073] The system receives a fifth paging message sent by the second device. The fifth paging message is used to page multiple first devices for Contention-Free Random Access (CFRA), and includes at least one of the following:

[0074] The device identifier of the plurality of first devices, and the random access resources corresponding to each of the plurality of first devices.

[0075] In the above embodiments, for CFRA, multiple first devices can perform random access based on the fifth paging message, thereby improving the efficiency and accuracy of random access.

[0076] In conjunction with the embodiments of the first aspect, in some embodiments, a fourth message is sent on the random access resources corresponding to the first device, the fourth message including the device identifier corresponding to the first device.

[0077] In the above embodiments, different first devices can initiate random access based on their respective device identifiers in CFRA, thereby improving the efficiency of random access.

[0078] In conjunction with the embodiments of the first aspect, in some embodiments, the method further includes:

[0079] The system receives a fifth message sent by the second device, the fifth message being used to indicate whether it contains temporary identifiers corresponding to the plurality of first devices.

[0080] In the above embodiments, the first device can determine whether it contains its own corresponding temporary identifier based on the fifth message, so that the first device can perform appropriate processing according to whether there is a corresponding temporary identifier, so as to adapt to the communication needs of different scenarios.

[0081] In conjunction with the embodiments of the first aspect, in some embodiments, the fifth message includes a bitmap, wherein each indicator bit in the bitmap is associated with a first device, and the indicator bit is used to indicate whether the fifth message includes a temporary identifier corresponding to the first device associated with the indicator bit; wherein, the indicator bit is a first value used to indicate that the fifth message includes a temporary identifier corresponding to the first device associated with the indicator bit, and the indicator bit is a second value used to indicate that the fifth message does not include a temporary identifier corresponding to the first device associated with the indicator bit;

[0082] Alternatively, the fifth message may include a temporary identifier corresponding to a resource index, the resource index being used to indicate the random access resource corresponding to the first device associated with the resource index.

[0083] In the above embodiments, the fifth message can indicate the temporary identifier corresponding to the first device in different ways, thereby effectively allocating temporary identifiers in scenarios with multiple first devices and improving communication efficiency.

[0084] In conjunction with the embodiments of the first aspect, in some embodiments, the fifth message is at least one of the following:

[0085] Paging messages, command messages.

[0086] In the above embodiments, temporary identifiers can be assigned to multiple devices through different types of fifth messages, improving flexibility.

[0087] Secondly, embodiments of this disclosure provide an instruction method executed by a second device, the method comprising:

[0088] Receive a first message for random access sent by the first device;

[0089] A second message is sent to the first device. The second message includes first indication information, which is used to indicate the type of the second message.

[0090] In the above embodiments, during the access process of the first device, the second device can indicate the type corresponding to the second message through the second message, so that the first device can perform reasonable business processing based on the type corresponding to the second message and improve communication performance.

[0091] In conjunction with the embodiments of the second aspect, in some embodiments, the first indication information is used to indicate that the type corresponding to the second message is a first type or a second type, wherein the first type corresponds to disk storage and commands, and the second type corresponds to disk storage only.

[0092] In conjunction with the embodiments of the second aspect, in some embodiments, the second message includes at least one temporary identifier, wherein each of the at least one temporary identifier corresponds to a first device that successfully sent the first message; wherein the type corresponding to the second message is a first type.

[0093] In conjunction with the embodiments of the second aspect, in some embodiments, the second message does not include at least one temporary identifier, wherein each of the at least one temporary identifier corresponds to a first device that successfully sent the first message; wherein the type corresponding to the second message is a second type.

[0094] In conjunction with the embodiments of the second aspect, in some embodiments, the first message includes a random number identifier corresponding to the at least one first device.

[0095] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0096] Before receiving the first message, a first paging message is sent to the first device. The first paging message is used to page multiple first devices for contention-based random access (CBRA).

[0097] After sending the second message, a third message is received from the first device, the third message containing the device identifier of the first device.

[0098] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0099] Send a second paging message to the first device to trigger reconnection.

[0100] In conjunction with the embodiments of the second aspect, in some embodiments,

[0101] The first device is configured to determine that the third message was successfully sent if, after sending or retransmitting the third message, it still has not received the second indication information after receiving the second paging message sent by the second device to trigger reconnection;

[0102] The second paging message has the same service identifier as the first paging message, and the second indication information is used to indicate one or more first devices that need to be reconnected.

[0103] In conjunction with the embodiments of the second aspect, in some embodiments,

[0104] The first device is used to receive the second paging message and release the random number identifier.

[0105] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0106] After receiving the third message, a second indication message is sent to the first device; wherein the second indication message is used to indicate one or more first devices that need to be reconnected.

[0107] In conjunction with the embodiments of the second aspect, in some embodiments, the first device is used to receive the second indication information and release the random number identifier.

[0108] In conjunction with the embodiments of the second aspect, in some embodiments, the second indication information does not contain the random number identifier of the first device, and the third message is successfully sent; or,

[0109] The second indication information contains the random number identifier of the first device, and the third message failed to be sent.

[0110] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0111] After receiving the third message, a third paging message is sent to the first device. The third paging message has a different service identifier than the first paging message and is used to paging the first device.

[0112] In conjunction with the embodiments of the second aspect, in some embodiments,

[0113] The first device is used to receive the third paging message and release the random number identifier.

[0114] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0115] After receiving the third message, a fourth paging message is sent to the first device, the fourth paging message having a different service identifier than the first paging message.

[0116] In conjunction with the embodiments of the second aspect, in some embodiments,

[0117] The first device is used to receive the fourth paging message and release the random number identifier.

[0118] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0119] A fifth paging message is sent to the first device. The fifth paging message is used to page multiple first devices for non-contention-based random access (CFRA). The fifth paging message includes at least one of the following:

[0120] The device identifier of the plurality of first devices, and the random access resources corresponding to each of the plurality of first devices.

[0121] In conjunction with the embodiments of the second aspect, in some embodiments, a fourth message is received on the random access resources corresponding to the first device, the fourth message including the device identifier corresponding to the first device.

[0122] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0123] A fifth message is sent to the first device, the fifth message being used to indicate whether the fifth message contains temporary identifiers corresponding to the plurality of first devices.

[0124] In conjunction with the embodiments of the second aspect, in some embodiments, the fifth message includes a bitmap, wherein each indicator bit in the bitmap is associated with a first device, and the indicator bit is used to indicate whether the fifth message includes a temporary identifier corresponding to the first device associated with the indicator bit; wherein, the indicator bit is a first value used to indicate that the fifth message includes a temporary identifier corresponding to the first device associated with the indicator bit, and the indicator bit is a second value used to indicate that the fifth message does not include a temporary identifier corresponding to the first device associated with the indicator bit;

[0125] Alternatively, the fifth message may include a temporary identifier corresponding to a resource index, the resource index being used to indicate the random access resource corresponding to the first device associated with the resource index.

[0126] In conjunction with the embodiments of the second aspect, in some embodiments, the fifth message is at least one of the following:

[0127] Paging messages, command messages.

[0128] Thirdly, embodiments of this disclosure provide a communication device for performing the method described in the first or second aspect.

[0129] Fourthly, embodiments of this disclosure provide a communication system, including a first device and a second device, wherein,

[0130] The first device is configured to implement the method as described in the first aspect;

[0131] The second device is configured to implement the method as described in the second aspect.

[0132] Fifthly, embodiments of this disclosure provide a communication method executed by a communication system, the communication system including a first device and a second device, wherein the method includes:

[0133] The first device sends a first message for random access to the second device;

[0134] The second device sends a second message to the first device. The second message includes first indication information, which is used to indicate the type of the second message.

[0135] Sixthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0136] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method as described in the first aspect or the second aspect.

[0137] In a seventh aspect, an embodiment of this disclosure provides a program product comprising at least one of a program and instructions, wherein when the program and instructions are executed by a communication device, they implement the method described in the first aspect or the second aspect.

[0138] It is understood that the aforementioned communication equipment, communication system, storage medium, program product, etc., are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0139] This disclosure provides an indication method, apparatus, system, storage medium, and program product. In some embodiments, the terms indication method, communication method, information processing method, etc., may be used interchangeably.

[0140] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0141] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0142] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0143] In the embodiments of this disclosure, "multiple" refers to two or more.

[0144] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0145] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0146] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0147] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0148] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0149] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0150] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0151] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0152] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0153] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0154] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0155] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0156] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0157] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0158] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0159] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0160] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0161] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0162] As shown in Figure 1A, the communication system 100 includes a first device 101 and a second device 102.

[0163] In some embodiments, the first device 101 is an IoT device, an A-IoT terminal, an A-IoT device, a tag, an environmental energy-based device, a passive device, a passive terminal, or a passive node, etc. In this embodiment, it may be referred to as a terminal or device.

[0164] The first device 101 can feature low memory usage, low processing power, low power consumption, small data transmission, and mass deployment capabilities. It is maintenance-free and has a long lifespan; for example, the lifespan of an A-IoT device can exceed 10 years. A-IoT devices support ambient power, are powered by energy harvesting, and have limited energy storage capacity (e.g., using capacitors). They obtain power by collecting radio waves, light, motion, heat, or any other suitable source. For example, an A-IoT device needs to collect radio waves transmitted by network nodes to obtain energy before it can operate. Therefore, before obtaining energy, the environmental IoT device is typically in a "shutdown" state, i.e., offline. For this reason, the communication system 100 needs to support data communication methods with shorter transmission times, lower memory consumption, and more convenient terminal management to complete the data communication process as quickly as possible.

[0165] In some embodiments, a wireless communication design for communication based on ambient energy devices is implemented using backscattering technology.

[0166] In some embodiments, the power acquisition and storage capabilities vary depending on the type and operating mode of the A-IoT device.

[0167] For example, A-IoT devices can include the following types:

[0168] Device 1 or Type 1: It has energy storage, no independent signal generation / amplification, and uplink transmission relies on backscatter transmission.

[0169] Device 2a or Type 2a: Features energy storage and independent signal amplification. Uplink transmission relies on backscatter transmission.

[0170] Device 2b or Type 3a: Features energy storage and independent signal amplification. Uplink transmission is based on internally generated signals.

[0171] In some embodiments, the aim is to study a harmonized air interface design that minimizes the diversity of environmental IoT (if necessary), such as supporting devices with the following characteristics, or environmental IoT devices that can meet the following characteristics or constraints:

[0172] The peak power consumption is approximately 1 microwatt (μW), and it has energy storage capabilities. The initial sampling frequency offset (SFO) is as high as 10X ppm. The device does not support downlink (DL) signal amplification or uplink (UL) signal amplification. The UL signal transmission of this device requires backscattering on an externally provided carrier.

[0173] Peak power consumption ≤ several hundred μW, with energy storage function, SFO up to 10X ppm, and the device has DL signal and / or UL signal amplification functions. The UL signal transmission of this device can be generated internally or backscattered on an externally provided carrier. X can be determined by a protocol.

[0174] In some embodiments, the second device 102 may include one or more network-side nodes or devices, or nodes or devices that assist in implementing network-side functions. Alternatively, in A-IoT, the second device 102 may include devices that implement reader functions or intermediate node functions.

[0175] Optionally, the second device 102 may be a network device, which may include at least one of an access network device and a core network device.

[0176] Optionally, the second device 102 may be a reader.

[0177] Optionally, the second device 102 may be a user equipment (UE) serving as a reader.

[0178] In some examples, to support data transmission for A-IoT devices, the second device 102 may implement one or more of the following functions:

[0179] Energy Source (ES) Function: Provides energy for environmental IoT devices, and can be used in devices 2a and 2b;

[0180] Downlink Transmission (DT) function: Triggers uplink transmission of IoT devices in the environment by sending indication information.

[0181] Continuous Wave (CW) Excitation Function: Provides the electromagnetic waves required for backscattering for environmental IoT devices. This can be used by Device 1 and Device 2a to achieve uplink transmission via backscattered CW. CW is actually a type of energy storage (ES), and environmental IoT devices can receive and store CW energy.

[0182] Uplink Receiver (UR) function: Receives uplink information backscattered by environmental IoT devices, or receives uplink information actively transmitted by environmental IoT devices.

[0183] The second device 102 can simultaneously perform multiple or all of the aforementioned functions; alternatively, the network device includes multiple network nodes, each of which performs one of the functions. The network node performing each function can be a user equipment (UE), a repeater, or a base station, etc. When each network node performs a function, the network can coordinate or control the behavior of different nodes.

[0184] In some examples, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.

[0185] In some examples, access network devices may include an A-IoT RAN (Ambient Internet of Things) or may include a reader.

[0186] In some examples, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0187] In some examples, access network equipment can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. The CU-DU structure can separate the protocol layer of the access network equipment. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU, which is centrally controlled by the CU. However, this is not the only example.

[0188] In some examples, a core network device can be a single device comprising one or more network elements, or it can be multiple devices or groups of devices, each comprising all or part of one or more network elements. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).

[0189] In some examples, core network equipment may include a core network for the Internet of Things in the Environment (A-IoT CN).

[0190] In some examples, core network equipment includes network elements with specific functions, such as Access Management Function (AMF) and Service Management Function (SMF).

[0191] In some embodiments, the UE includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0192] Figures 1B to 1F are schematic diagrams of the topology of a communication system according to embodiments of the present disclosure.

[0193] As shown in Topology 1 of Figure 1B, the first device 101 can communicate directly with the network device to directly receive and transmit DL and UL data. For example, the network device and the first device 101 directly interact with ambient IoT data or signaling.

[0194] As shown in Topology 2 in Figure 1C, the first device 101 indirectly receives and transmits DL and UL data with the network device, and forwards the data through the intermediate node 103.

[0195] In some embodiments, the intermediate node 103 may be a relay, repeater, integrated access backhaul (IAB), or UE.

[0196] As shown in Figures 1D and 1E, in topology 3, the first device 101 indirectly receives and transmits DL and UL data with the network device. Then, there is an assisting node 104 on the UL or DL, which is responsible for receiving or sending UL data or receiving DL data.

[0197] In some embodiments, the auxiliary node 104 may be a relay, repeater, IAB, or UE.

[0198] As shown in Topology 4 of Figure 1F, the first device 101 and UE 105 directly receive and transmit DL and UL data. UE 105 is responsible for collecting data and forwarding the collected data to the second device 102, such as an access network device or a core network device. UE refers to user equipment other than the first device 101, such as a user equipment with conventional capabilities.

[0199] In some embodiments, communication between the first device 101 and the network device, such as communication based on topology 1 and topology 2, can utilize spectrum resources in three forms: in-band, guard band, and stand-alone. In-band uses normal NR communication DL and / or UL spectrum resources, such as the spectrum resources used for DL / UL communication between the base station and other UEs (Figure 1B), or the spectrum resources used for DL / UL communication between the UE and the base station (Figure 1C). Guard band uses the spectrum resources of the guard band of normal NR communication DL and / or UL spectrum. Stand-alone uses spectrum resources unrelated to NR communication.

[0200] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0201] The following embodiments of this disclosure can be applied to the communication system 100 shown in Figures 1A to 1F, or to some of the main bodies, but are not limited thereto. The main bodies shown in Figures 1A to 1F are illustrative. The communication system may include all or some of the main bodies in Figures 1A to 1F, or it may include other main bodies outside of Figures 1A to 1F. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0202] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0203] In some implementations, traditional IoT devices are typically powered by batteries with limited lifespans. With the proliferation of IoT networks and the large number of IoT devices, issues such as battery maintenance, recycling, and replacement have become increasingly serious. Batteries that cannot be successfully recycled can also have harmful impacts on the ecosystem and environment. Therefore, environmentally friendly and secure battery-free communication has emerged. Battery-free communication can improve network performance and sustainability, expand application scenarios, and significantly reduce device size and cost.

[0204] In some implementations of 5G communication technology, existing low-power wide-area (LPMA) technologies, such as machine-type communication (MTC), narrowband Internet of Things (NB-IoT), and reduced capability (RedCap), can meet the growing demands of vertical industries, enabling low cost, low power consumption, and massive connectivity. However, they still cannot address the following needs: First, devices powered by traditional batteries are unsuitable, for example, under extreme environmental conditions (e.g., high voltage, extremely high / low temperatures, humid environments); second, maintenance-free devices are required (e.g., traditional batteries that do not require replacement); and finally, ultra-low complexity, very small device size or form factor (e.g., thickness in millimeters), and longer lifespan are required. IoT that supports ambient power or environmentally powered systems can meet these needs.

[0205] In some implementations, low-power IoT communication chips such as Bluetooth Low Energy (BLE) Long Range Radio (LoRa) or NB-IoT consume tens or even hundreds of milliwatts of power for transmission and reception. However, as described in the preceding embodiments, environmental energy harvesting yields only microwatts of energy. Harvesting energy from the environment to power sensing nodes such as terminal 101 for data transmission and wireless communication requires wireless communication technologies that can reduce communication power consumption to tens or even less than ten microwatts, such as backscatter communications.

[0206] In some implementations, backscatter communication is an extremely low-power modulation and transmission technology that utilizes the principle of radio frequency signal backscattering, serving as a means to achieve the Internet of Things (IoT). In backscatter communication, because a portion of the radio frequency signal, such as electromagnetic waves, is reflected when it reaches the surface of an object, a passive node, such as terminal 101, adjusts the matching between its receiving antenna and impedance according to the information to be transmitted, enhancing the reflection of the incident radio frequency signal. It then modulates the sensed data it acquires onto the reflected signal, completing the data transmission. Compared to other communication technologies, backscatter communication eliminates the need for complex radio frequency structures, reducing the use of devices such as power amplifiers, high-precision crystal oscillators, duplexers, and high-precision filters. It also eliminates the need for complex baseband processing, thus simplifying terminal design and significantly reducing terminal node costs.

[0207] In some implementations, in a Radio Frequency Identification (RFID) system using backscatter communication, as shown in Figure 1G, the receiver sends a radio frequency excitation signal to activate a passive node. The receiver, for example, is an RFID reader, corresponding to a network device such as access network device 102; the passive node, for example, is an RFID tag, corresponding to terminal 101. The tag uses backscatter communication to modulate its own information onto the radio frequency signal. The reader receives the reflected signal from the passive tag and demodulates it to achieve information transmission. RFID communication suffers from the following drawbacks: the wireless signal experiences double-path fading, resulting in significant path loss, short effective communication distance, and therefore limited coverage; it also requires single-channel transmission; strict tag alignment is required; and there is no power control. Therefore, it is necessary to integrate 3GPP communication technologies to improve the wireless communication performance of RFID technology in passive Internet of Things (IoT) applications.

[0208] In some implementations, data transmission from terminals in passive IoT systems falls into three categories: Device-originated Device-terminated triggered (DO-DTT), Device-terminated (DT), and Device-originated-autonomous (DO-A). DO-DTT can be understood as reader-triggered data transmission, such as inventory management; DT can be understood as data transmission terminating at the IoT device, such as an access command; and DO-A can be understood as tag-triggered data transmission, such as proactive reporting triggered by sensor functionality.

[0209] In some implementations, the first message that triggers initial access for a device can be called a paging message or an initial trigger message. A paging message can page one, a group, or all IoT devices. If a paging message pages one IoT device, it triggers non-contention-based random access. The paged IoT device responds to the paging message on non-contention-based resources, for example, by sending an acknowledgment (ACK) message containing the IoT device's identifier, such as an Electronic Product Code (EPC), and this ACK message is message 1 (msg1). If a paging message triggers access for a group or all IoT devices, it triggers contention-based random access. A group or all paging IoT devices generate a random number (RN16, 16 bits) based on parameters similar to Q. They then continue receiving Device-to-Reader (R2D) trigger messages. Based on these R2D trigger messages, they determine the starting boundary of the random access occasion and the IoT device's random access occasion, for example, the occasion of sending the generated random number (msg1). For IoT devices that have successfully accessed the network, the reader needs to send a message 2 (msg2) based on msg1. msg2 carries the random number corresponding to the successfully accessed IoT device. Upon receiving msg2, the IoT device confirms that msg2 contains its own generated random number, confirming successful random access, and continues to send message 3 (msg3). msg3 contains the IoT device's identifier, such as the device identifier assigned by the EPC or core network. The reader can trigger a retransmission of msg3 by retransmitting msg2, or it can trigger re-access by sending a Negative Acknowledgment (NACK) message. The NACK message is used to indicate to IoT devices that failed to send msg3 that a re-access has been triggered. Re-access refers to re-initiating the random access procedure via a paging message and retransmitting msg1 and / or msg3.

[0210] In some implementations, communication between the Device and Reader relying on the Device's device identifier (e.g., EPC) can result in high signaling overhead. Therefore, it can be determined whether communication between the Reader and Device can be achieved using an Access Stratum Identifier (AS ID), which is a shorter identifier than the Device's device identifier. The determination of the AS ID includes at least one of the following:

[0211] Option 1: The AS ID reuses the random number from the first D2R message;

[0212] Option 2: The Reader can assign an AS ID to the Device, which requires determining the R2D message that assigns the AS ID.

[0213] Option 3: The Reader can determine whether to reuse the random number in the first D2R message as the AS ID, or to assign a new AS ID to the Device, which requires determining the R2D message that assigns the AS ID.

[0214] In some implementations, for Contention-Based Random Access (CBRA), the Reader can determine whether to reuse the random number 16 (RN16) in msg1 or assign a new AS ID. In some implementations, the AS ID is only applicable to Inventory+Command processes; it is not applicable to inventory-only processes (or inventory processes). In the Contention-Free Random Access (CFRA) process within the Inventory+Command process, the AS ID is assigned via command. In the CBRA process within the Inventory+Command process, the AS ID is assigned via msg2, where msg2 is the Reader's response to a successfully accessed IoT device, carrying the random number sent by the successfully accessed IoT device in msg1. In addition, IoT devices need to release their AS ID in the following three situations: when the IoT device is powered off; when the IoT device receives a paging message that paging the device, and the transaction identifier carried in the paging message is different from the current paging message; when the IoT device receives a paging message that triggers the IoT device to send a new msg1.

[0215] In some implementations, the AS ID is applied in the Inventory+command scenario. The AS ID is not included in the D2R message except for msg1, where msg1 may contain RN16. For CFRA and CBRA, the AS ID size can be the same as RN16, i.e., 16 bits. The method of AS ID generation is not limited. The device can release the AS ID upon power loss. The device can retain only one AS ID at a time. For CFRA, command messages can be used for AS ID allocation. For CBRA, msg2 can be used for AS ID allocation.

[0216] The device releases the AS ID at least in the following circumstances: when a paging message with a new service ID is received for the device (i.e., a different session and / or service); when a new msg1 transmission is triggered by receiving a paging message (e.g., generating a random ID for CBRA); other circumstances for releasing the AS ID are not limited to avoid retaining the identifier indefinitely.

[0217] In some implementations: A-IoT msg2 contains one or more echoed or retransmitted random IDs from A-IoT msg1 from different A-IoT devices; the initial transmission and retransmission of msg2 use the same message format.

[0218] In some implementations, msg2 in the inventory-only process does not contain an AS ID, while msg2 in the inventory+command process may contain an AS ID assigned by the Reader. Therefore, IoT devices need to distinguish between msg2 in the inventory-only process and msg2 in the inventory+command process.

[0219] In some implementations, during the CFRA process within the Inventory+command flow, the AS ID is assigned via the command. Therefore, the first D2R message in the CFRA does not carry the RN16. The command uniquely identifies an IoT device through the AS ID. Only one IoT device is supported in this CFRA process, and only one IoT device communicates with the Reader. Therefore, the AS ID in the command is the one assigned to that IoT device.

[0220] In some implementations, CFRA may also support multiple IoT devices. If the CFRA process supports multiple IoT devices and assigns AS IDs to each IoT device separately via commands, each AS ID needs to be associated with a separate IoT device. Optionally, after an IoT device sends message 3, if it does not receive its own NACK indication before the next R2D message that triggers re-access, the IoT device considers message 3 to have been sent successfully. This R2D message can be an R2D trigger message or a paging message.

[0221] During the CFRA process, RN16 is not included in the first D2R message. Assuming that no multiple devices perform the process with a given Reader in the CFRA, the AS ID is a unique identifier used to address the device in the R2D command message.

[0222] As can be seen from the above implementation methods, IoT devices can distinguish between msg2 in the inventory-only process and msg2 in the inventory+command process using the implementation methods disclosed in the following text. In scenarios where CFRA supports multiple IoT devices, AS IDs can be assigned to multiple IoT devices separately using the implementation methods disclosed in the following text, and RN16 can be released at an appropriate time using the implementation methods disclosed in the following text.

[0223] Figure 2A is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 2A, an indication method according to an embodiment of the present disclosure includes:

[0224] In step S2101, the second device 102 sends a first paging message to the first device 101.

[0225] In some embodiments, the first device 101 receives a first paging message sent by the second device.

[0226] Optionally, the second device 102 may be a network device, such as a BS reader; or the second device 102 may be a UE that can act as a reader.

[0227] Optionally, the first device 101 may be an IoT or A-IoT device.

[0228] In some embodiments, the first paging message is used to page multiple first devices for CBRA access, and the multiple first devices 101 can initiate CBRA after receiving the first paging message.

[0229] Optionally, the first paging message can be used to represent the first message that triggers the first device 101 to perform random access or initial access; this name is for illustrative purposes only. For example, the first paging message can be replaced by an initial trigger message, or a Reader To Device (R2D) message, or an R2D trigger message.

[0230] Optionally, the first device 101 in step S2101 can be any one of the multiple first devices for paging.

[0231] In some embodiments, the first paging message may be associated with a transaction ID, or the first paging message may include the transaction ID of the corresponding service.

[0232] Optionally, the service identifier is used to indicate whether the first paging message is being sent repeatedly. The first device 101 can determine whether to respond to the first paging message based on the service identifier. Specifically, if the first device 101 has already responded to a first paging message, and that first paging message is being sent repeatedly, the first device 101 may choose not to respond again, such as ignoring the previously responded-to first paging message. The first device 101 may respond to the first paging message by initiating information for random access based on the first paging message, for example, sending message 1, which may contain a 16-bit random number RN16.

[0233] Optionally, the service identifier is used to identify at least one of the transactions, services, or sessions corresponding to this paging. For example, the service can be an IoT service or an A-IoT service.

[0234] In some embodiments, the first paging message may be the first paging message received when the first device 101 needs to perform random access or the first paging message received during the current access.

[0235] In some embodiments, the name of information, etc., is not limited to the name described in the embodiments, and terms such as "information", "message", "signal", and "signaling" can be used interchangeably.

[0236] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0237] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0238] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0239] In step S2102, the first device 101 sends a first message for random access to the second device 102.

[0240] In some embodiments, the second device 102 receives a first message sent by the first device.

[0241] In some embodiments, the first device 101 sends a first message to the second device 102 based on a first paging message.

[0242] In some embodiments, the first device 101 initiates a contention-based random access procedure (CBRA) by sending a first message, such as a contention-based three-step random access procedure (3-step CB access).

[0243] Optionally, the first message may be referred to as message 1 or msg1.

[0244] Optionally, the first device 101 may determine the timing or random access timing for sending the first message based on the message from the second device 102. For example, the first device 101 may determine the timing for sending the first message based on the first paging message or other R2D messages.

[0245] In some embodiments, the first message can be used to identify or distinguish different first devices. For example, for different first devices 101 that initiate access, each first device 101 sends a first message, and the first message of each first device 101 may include its own corresponding random number identifier; wherein, the random number identifier can be used to identify the corresponding first device 101.

[0246] Optionally, the random number identifier may be a random number generated by the first device 101 based on parameters (such as parameter Q) indicated by the second device 102.

[0247] Optionally, the random number identifier is one of a plurality of random number identifiers defined by the protocol.

[0248] Optionally, the random number identifier is an RN16 occupying 16 bits. For example, the first message includes an RN16 randomly selected by the first device 101 from a plurality of RN16s reserved by the system or defined by the protocol, or an RN16 generated by the first device 101.

[0249] In step S2103, the second device 102 sends a second message to the first device 101.

[0250] In some embodiments, the first device 101 receives a second message sent by the second device 102.

[0251] Optionally, in CBRA, the second message can be message 2 or msg2.

[0252] Optionally, the second device 102 may send a second message to the first device 101 after successfully receiving the first message from the first device 101. Optionally, the second device 102 may send the second message to at least one of the first devices 101 that have successfully accessed the system. Here, "the second device 102 successfully receiving the first message from the first device 101" can be replaced by "the first device 101 successfully sending the first message" or "the first device 101 successfully accessing the system."

[0253] Optionally, the second message may carry a random number identifier of the first device 101 that the first message was successfully sent, such as carrying at least one RN16 of the first device 101, to indicate successful random access.

[0254] Optionally, the first device 101 that receives the second message determines that the second message contains its own generated random number identifier, confirms that the random access is successful, and can continue to execute step S2104.

[0255] In some embodiments, the second message includes first indication information, which indicates the type corresponding to the second message, such as a business type, process type, or business process type. Here, business type, process type, or business process type refers to an IoT process, such as whether it is inventory only or inventory and command. Optionally, when the business type corresponding to the second message is different, the message type (R2D msg type) of the second message can be different, such as indicating different business types through second messages with different message types.

[0256] Optionally, the header of the second message may include the first instruction information or the service type corresponding to the second message, in order to distinguish different types of second messages.

[0257] In some embodiments, the first indication information is used to indicate that the type corresponding to the second message, such as business type or process type, is a first type or a second type, wherein the first type corresponds to inventory and command, and the second type corresponds to inventory only. Optionally, inventory and command can also be referred to as inventory and command process, and inventory only can also be referred to as inventory only process.

[0258] Optionally, the definition of the type corresponding to the second message can include either of the following two methods:

[0259] In the first embodiment, the message type of the second message is associated or bound to the business type or process type. For example, two types of second messages are defined, corresponding to the first type and the second type of business type or process type, respectively. The first type is inventory and command, and the second type is inventory only. The two types of second messages are associated with different R2D msg types.

[0260] In this embodiment, the first indication information includes N bits, which are used to indicate the service type corresponding to the second message.

[0261] Optionally, the N-bit indicator bit is a third value used to indicate that the service type corresponding to the second message is the first type, that is, the second message is a second message used for inventory and commands; the N-bit indicator bit is a fourth value used to indicate that the service type corresponding to the second message is the second type, that is, the second message is a second message used only for inventory. Wherein, N ≥ 1, for example, N is 1 or N is 4. Wherein, the third and fourth values ​​are different, for example, N is 1, the third value is 1, and the fourth value is 0, or the third value is 0 and the fourth value is 1; another example is N is 4, the third value is 1111, and the fourth value is 0001, or the third value is 0001 and the fourth value is 1111. It is worth noting that in this embodiment, the value of N (i.e., how many bits the indicator bit used to indicate the service type occupies), the value of the third value, and the value of the fourth value are not limited, and can also be other values ​​besides those exemplified in the above optional examples.

[0262] In the second embodiment, the message type of the second message is not directly associated with or bound to the business type or process type. For example, if a type of second message is defined, the business type corresponding to the second message may be the first type or the second type.

[0263] In this embodiment, the first indication information can be a first indication bit, which indicates that the service type corresponding to the second message is a first type or a second type, that is, it indicates that the second message is used for inventory and command or only for inventory.

[0264] Optionally, the first indicator bit is M bits. A fifth value of the first indicator bit indicates that the service type corresponding to the second message is a first type, i.e., the service type corresponding to the second message is inventory and command. A sixth value of the first indicator bit indicates that the service type corresponding to the second message is a second type, i.e., inventory only. Where M ≥ 1, for example, M is 1. The fifth and sixth values ​​are different; for example, M is 1, the fifth value is 1, and the sixth value is 0, or the fifth value is 0 and the sixth value is 1. It is worth noting that in this embodiment, the value of M (i.e., how many bits the first indicator bit occupies), the value of the fifth value, and the value of the sixth value are not limited and can be other values ​​besides those exemplified in the above optional examples.

[0265] In some embodiments, network device 102 may carry a temporary identifier in the second message. For example, in inventory and command service types, the second message may carry a temporary identifier.

[0266] Optionally, the second message includes at least one temporary identifier, and each temporary identifier corresponds to a first device that successfully sent the first message; wherein the type of the second message is the first type.

[0267] Optionally, for at least one first device that successfully sends the first message, or for the second device 102 that successfully receives the first message from the at least one first device, or for the at least one first device to successfully access the network, the second device 102 may carry a temporary identifier corresponding to each of the at least one first devices in the second message.

[0268] Optionally, the temporary identifier can be an AS ID, which can reuse a random number identifier such as RN16, or the AS ID can be an identifier reassigned by the base station or core network equipment. Optionally, for each first device that successfully accesses the network, the second message carries the AS ID of this first device. If the second device 102 determines that the random number identifier can be reused (or reused) as a temporary identifier, it can reuse the random number identifier of the first device that successfully accessed the network as an AS ID and carry it in the second message; if the random number identifier cannot be reused (or reused) as a temporary identifier, the second device 102 can reassign a temporary identifier.

[0269] Optionally, if the second device 102 determines that the random number identifier can be reused (or reused) as a temporary identifier, it can reuse the random number identifier of the first device that has successfully accessed the system as an AS ID and carry it in the second message; if the random number identifier cannot be reused (or reused) as a temporary identifier, the second device 102 can reallocate a temporary identifier, such as the second message including at least one reallocated temporary identifier corresponding to the first device.

[0270] Optionally, when the type corresponding to the second message is the second type, even if the first message from at least one first device is successfully received by the second device, the second message may not include at least one temporary identifier, where each temporary identifier corresponds to a first device that successfully sent the first message. For example, the temporary identifier may be used only for the first type of service, namely inventory and commands.

[0271] In some embodiments, the second message may be sent by the second device 102 to the first device 101 for the first time, or it may be retransmitted by the second device 101 to the first device 101.

[0272] Optionally, for the first sent second message, the first device may send a third message as a response, as described in the embodiments below. When retransmitting the second message, the retransmitted second message can be used to trigger the first device to retransmit the third message. For example, if the retransmitted second message carries a random number identifier of a certain first device, then the first device needs to retransmit the third message after receiving the retransmitted second message.

[0273] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0274] In step S2104, the first device 101 sends or retransmits the third message to the second device 102.

[0275] In some embodiments, the second device 101 receives a third message sent by the first device.

[0276] Optionally, the third message can be message 3 or msg3 in CBRA.

[0277] In some embodiments, the third message includes a device identifier of the first device 101, which is used to instruct the first device 101 corresponding to the device identifier to perform random access.

[0278] Optionally, the device identifier of the first device 101 may be an Electronic Product Code (EPC), a device identifier assigned by the core network, or a device identifier assigned by a third party.

[0279] In some embodiments, the third message may be sent by the first device 101 to the second device 102 for the first time after receiving the second message. Alternatively, the third message may be triggered by the second device 102 retransmitting the second message, and then be retransmitted by the first device 101 to the second device 102.

[0280] In step S2105, the second device 102 sends a second paging message to the first device 101.

[0281] In some embodiments, the first device 101 receives a second paging message sent by the second device 102.

[0282] In some embodiments, the second paging message is used to trigger re-access.

[0283] Optionally, the second paging message is used for the first device that failed to access the device randomly, or for the first device that failed to send the third message for re-access.

[0284] Optionally, the name of the second paging message is for illustrative purposes only. It may be a paging message, an R2D message other than a paging message, or an R2D trigger message.

[0285] In some embodiments, the second paging message is associated with a service identifier, or the second paging message includes a service identifier.

[0286] Optionally, the second paging message is associated with the same service identifier as the first paging message, and the second paging message is associated with the same service and / or session as the first paging message. For example, both the second paging message and the first paging message are associated with service identifier 1.

[0287] Optionally, the service identifier is used to identify the corresponding IoT service. For example, different service identifiers can indicate different IoT services under the same process, such as different IoT services in inventory and command processes.

[0288] In step S2106, when the first device 101 receives the second paging message but has not yet received the second instruction information, it determines that the third message has been successfully sent.

[0289] In some embodiments, if the first device 101 does not receive the second indication information after sending or retransmitting the third message until it receives the second paging message, it determines that the third message was successfully sent.

[0290] In this embodiment, the first device 101 receives the second paging message but does not receive the second indication information, indicating that the third message was successfully sent.

[0291] In some embodiments, the second indication information is used to indicate one or more first devices that need to be reconnected.

[0292] Optionally, the second indication information can be a NACK message.

[0293] Optionally, the NACK message is used to trigger one or more first devices that have failed to send a third message to reconnect.

[0294] In step S2107, the first device 101 receives the second paging message and releases the random number identifier and / or temporary identifier.

[0295] In some embodiments, the first device 101 may release the random number identifier after receiving the second paging message.

[0296] In some embodiments, the random number identifier may be a random number identifier contained in the first message.

[0297] Optionally, the first device 101 can directly release the random number identifier upon receiving the second paging message in step S2105. In this case, step S2106 can be omitted.

[0298] Optionally, if the second paging message has the same service identifier as the first paging message, the first device 101 can indicate that the second paging message is a paging message that the first device 101 has responded to. Therefore, upon receiving the second paging message in step S2105, the random number identifier can be released. In this case, step S2106 can be omitted.

[0299] Optionally, if the first device 101 determines that the third message has been successfully sent, indicating that the random number identifier has been used up, the random number identifier can be released. For example, the first device 101 can release the random number identifier upon receiving the second paging message.

[0300] In some embodiments, after receiving the second paging message, if the first device 101 determines that it needs to reconnect, it may trigger the first device 101 to initiate a CBRA. The first device 101 will generate a new random number identifier and replace the original random number identifier with the new random number identifier in the new first message. The original random number identifier is equivalent to being released.

[0301] In some embodiments, the implementation of releasing the random number identifier can be applied to both inventory and command service types, as well as inventory-only service types.

[0302] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2107. For example, steps S2102 and S2103 may be implemented as independent embodiments, steps S2101 to S2103 may be implemented as independent embodiments, steps S2102 to S2104 may be implemented as independent embodiments, steps S2102 to S2105 may be implemented as independent embodiments, and steps S2102 to S2107 may be implemented as independent embodiments, but are not limited thereto.

[0303] In some embodiments, steps S2106 and S2107 may be performed in an alternate order or simultaneously.

[0304] In some embodiments, steps S2101 and S2104 to S2107 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0305] In some embodiments, steps S2104 to S2107 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0306] In some embodiments, steps S2101 and S2105 to S2107 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0307] In some embodiments, steps S2101 and S2106 to S2107 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0308] In some embodiments, step S2101 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0309] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0310] Figure 2B is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 2B, an indication method according to an embodiment of the present disclosure includes:

[0311] In step S2201, the second device 102 sends a first paging message to the first device 101.

[0312] In some embodiments, the implementation of step S2201 can be found in the implementation of step S2101 in FIG2A.

[0313] In step S2202, the first device 101 sends a first message for random access to the second device 102.

[0314] In some embodiments, the implementation of step S2202 can be found in the implementation of step S2102 in FIG2A.

[0315] In step S2203, the second device 102 sends a second message to the first device 101.

[0316] In some embodiments, the implementation of step S2203 can be found in the implementation of step S2103 in FIG2A.

[0317] In step S2204, the first device 101 sends or retransmits the third message to the second device 102.

[0318] In some embodiments, the implementation of step S2204 can be found in the implementation of step S2104 in FIG2A.

[0319] In step S2205, the second device 102 sends a second instruction message to the first device 101.

[0320] In some embodiments, the first device 101 receives second instruction information sent by the second device 102.

[0321] Optionally, after sending or retransmitting the third message, the first device 101 receives the second instruction information sent by the second device.

[0322] In some embodiments, the second indication information is used to indicate one or more first devices that need to be reconnected.

[0323] In some embodiments, the second indication information does not include the random number identifier of the first device, indicating that the third message of the first device was successfully sent; or, the second indication information includes the random number identifier of the first device, indicating that the third message of the first device failed to be sent.

[0324] Optionally, if the second indication information does not include the random number identifier of the first device 101, it may also include the random number identifier of other first devices that need to be reconnected.

[0325] In step S2206, the first device 101 receives the second instruction information and releases the random number identifier and / or temporary identifier.

[0326] Optionally, the first device 101 may release the random number identifier upon receiving the second instruction information.

[0327] In some embodiments, the second indication information does not include the random number identifier of the first device, indicating that the third message of the first device was successfully sent. In this case, if the third message is successfully sent, the first device 101 can release the random number identifier upon receiving the second indication information.

[0328] In some embodiments, the second indication information includes a random number identifier of the first device, indicating that the third message transmission of the first device failed and the first device needs to reconnect. The first device 101 may release the random number identifier upon receiving the second indication information, and the first device needs to regenerate a new random number identifier for reconnection during the reconnection process.

[0329] In some embodiments, the second instruction information may also include a temporary identifier of the first device, or may not include a temporary identifier of the first device. In this embodiment, after receiving the second instruction information, the first device 101 may release the temporary identifier.

[0330] Optionally, the second indication information includes a temporary identifier for the first device. If the third message transmission of the first device fails, the first device needs to reconnect and can release the original temporary identifier. Communication is then conducted based on obtaining a new temporary identifier upon reconnection.

[0331] In some embodiments, the implementation of releasing the random number identifier can be applied to both inventory and command service types, as well as inventory-only service types.

[0332] It is worth noting that the timing of releasing the random number identifier in step S2206 is different from the timing of releasing the random number identifier in step S2107.

[0333] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2206. For example, steps S2202 and S2203 may be implemented as independent embodiments, steps S2201 to S2203 may be implemented as independent embodiments, steps S2202 to S2204 may be implemented as independent embodiments, steps S2202 to S2205 may be implemented as independent embodiments, and steps S2202 to S2206 may be implemented as independent embodiments, but are not limited thereto.

[0334] In some embodiments, steps S2201 and S2204 to S2206 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0335] In some embodiments, steps S2204 to S2206 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0336] In some embodiments, steps S2201 and S2205 to S2206 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0337] In some embodiments, steps S2201 and S2206 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0338] In some embodiments, step S2201 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0339] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0340] Figure 2C is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 2C, an indication method according to an embodiment of the present disclosure includes:

[0341] In step S2301, the second device 102 sends a first paging message to the first device 101.

[0342] In some embodiments, the implementation of step S2301 can be referred to the implementation of step S2101 in FIG2A.

[0343] In step S2302, the first device 101 sends a first message for random access to the second device 102.

[0344] In some embodiments, the implementation of step S2302 can be referred to the implementation of step S2102 in FIG2A.

[0345] In step S2303, the second device 102 sends a second message to the first device 101.

[0346] In some embodiments, the implementation of step S2303 can be found in the implementation of step S2103 in FIG2A.

[0347] In step S2304, the first device 101 sends or retransmits the third message to the second device 102.

[0348] In some embodiments, the implementation of step S2304 can be found in the implementation of step S2104 in FIG2A.

[0349] In step S2305, the second device 102 sends a third paging message or a fourth paging message to the first device 101.

[0350] In some embodiments, the first device 101 receives a third paging message or a fourth paging message sent by the second device 102.

[0351] In some embodiments, after the first device 101 sends or retransmits the third message, it receives the third paging message sent by the second device. Optionally, the service identifier of the third paging message is different from that of the first paging message. Alternatively, the service identifier of the third paging message is the same as that of the first paging message.

[0352] Optionally, the service identifier associated with the third paging message is different from that associated with the first paging message. For example, the third paging message is associated with service identifier 1, and the first paging message is associated with service identifier 2.

[0353] Optionally, the first device 101 may be included in the paging device for the third paging message.

[0354] Optionally, the third paging message is used to page the first device, such as if the first device 101 is a device paged by a third paging message with a different service identifier.

[0355] In some embodiments, after the first device 101 sends a third message, it receives a fourth paging message sent by the second device. The fourth paging message has a different service identifier than the first paging message.

[0356] Optionally, the service identifier associated with the fourth paging message is different from that associated with the first paging message. For example, the fourth paging message is associated with service identifier 1, and the first paging message is associated with service identifier 2.

[0357] Optionally, the fourth paging message does not page the first device 101. In other words, the device paged by the fourth paging message does not include the first device 101.

[0358] In step S2306, the first device 101 receives the third paging message or the fourth paging message and releases the random number identifier.

[0359] In some embodiments, when the first device 101 is paged by a third paging message, it needs to respond to the third paging message. Therefore, it generates a new random number identifier and releases the original random number identifier.

[0360] Optionally, if the first device 101 receives a third paging message with a different service identifier than the first paging message, and if the third paging message is paging the first device 101, or in other words, the first device 101 is a device paging the third paging message, the first device 101 can directly release the random number identifier upon receiving the third paging message.

[0361] Optionally, if the first device 101 receives a fourth paging message with a different service identifier than the first paging message, and if the fourth paging message does not page the first device 101, or in other words, the first device 101 is not a device paged by the fourth paging message, the first device 101 may release the random number identifier upon receiving the fourth paging message.

[0362] In some embodiments, after receiving a third paging message, the first device 101 responds to the third paging message by sending a new first message, or by triggering the first device 101 to initiate a CBRA. The first device 101 generates a new random number identifier, and replaces the original random number identifier with the new random number identifier in the new first message, effectively releasing the original random number identifier.

[0363] In some embodiments, in conjunction with the second paging message, after the first device 101 receives the second paging message, if the first device 101 determines that reconnection is required, it may trigger a CBRA (Continuous Access Redirect) initiation. The first device 101 will generate a new random number identifier, replacing the original random number identifier in a new first message; the original random number identifier is effectively released. Optionally, in different combinations of embodiments, the second paging message may be received before step S2305.

[0364] In some embodiments, when a first device 101 receives a fourth paging message, if the fourth paging message does not page the first device 101, or in other words, the first device 101 is not a device paged by the fourth paging message, the first device 101 releases a random number identifier.

[0365] It is worth noting that the fourth and third paging messages differ from the second paging message in that the fourth and third paging messages are associated with different service identifiers than the first paging message, while the second paging message is associated with the same service identifier as the first paging message. This also explains that after the first device 101 receives other paging messages (such as the second, third, or fourth paging message) besides the first paging message, it can release the original random number identifier regardless of whether the received other paging messages are associated with the same service identifier as the first paging message.

[0366] The communication method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2306. For example, steps S2302 and S2303 may be implemented as independent embodiments, steps S2301 to S2303 may be implemented as independent embodiments, steps S2302 to S2304 may be implemented as independent embodiments, steps S2302 to S2305 may be implemented as independent embodiments, and steps S2302 to S2306 may be implemented as independent embodiments, but are not limited thereto.

[0367] In some embodiments, steps S2301 and S2304 to S2306 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0368] In some embodiments, steps S2304 to S2306 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0369] In some embodiments, steps S2301 and S2305 to S2306 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0370] In some embodiments, steps S2301 and S2306 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0371] In some embodiments, step S2301 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0372] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0373] Figure 2D is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 2D, an indication method according to an embodiment of the present disclosure includes:

[0374] In step S2401, the second device 102 sends a fifth paging message to the first device 101.

[0375] In some embodiments, the first device 101 receives a fifth paging message sent by the second device.

[0376] Optionally, the fifth paging message may be referred to as a paging command.

[0377] In some embodiments, the fifth paging message is used to page multiple first devices for CFRA, and the fifth paging message includes at least one of the following:

[0378] The device identifier of multiple first devices, and the random access resources corresponding to each of the multiple first devices.

[0379] Optionally, the random access resource corresponding to the first device is a non-contentionable random access resource.

[0380] For example, the fifth paging message may carry the device identifiers of multiple first devices being paging, and each first device may be allocated corresponding random access resources. The random access resources corresponding to different first devices can be indicated by resource indexes; for instance, the fifth paging message may allocate resource indexes to different first devices to indicate the random access resources corresponding to that first device.

[0381] Optionally, random access resources include information such as the random access occasion.

[0382] In step S2402, the first device 101 sends a fourth message to the second device 102 on the random access resource corresponding to the first device.

[0383] In some embodiments, the second device 102 receives a fourth message sent by the first device 101 on the random access resources corresponding to the first device.

[0384] Optionally, different first devices 101 can send the fourth message on their respective random access resources.

[0385] Optionally, the fourth message can be message 1 or msg1 in CFRA.

[0386] In some embodiments, the fourth message includes the device identifier corresponding to the first device 101.

[0387] Optionally, the device identifier corresponding to the first device 101 can be a device identifier assigned by the EPC or the core network or a device identifier assigned by a third party.

[0388] Optionally, the name of the fourth message is only for distinction and illustration. For example, the fourth message can be message 1 in CFRA, and the first message can be message 1 in CBRA. Alternatively, the fourth message can still be named after the first message, but in this case, the meaning or content of the first message is different in CFRA and CBRA.

[0389] In step S2403, the second device 102 sends a fifth message to the first device 101.

[0390] In some embodiments, the first device 101 receives a fifth message sent by the second device.

[0391] In some embodiments, the fifth message is at least one of the following:

[0392] Paging messages, command messages, R2D messages.

[0393] Optionally, the command message can be a first command, for example, the first command is at least one of a read command, a write command, a kill command, or a disable command.

[0394] In some embodiments, the fifth message is used to indicate whether the fifth message contains temporary identifiers corresponding to multiple first devices.

[0395] For example, the fifth message includes third indication information, which is used to indicate whether the fifth message contains temporary identifiers corresponding to multiple first devices.

[0396] Optionally, the fifth message includes temporary identifiers corresponding to multiple first devices. For multiple first devices, the second device 102 can send the same fifth message to multiple first devices, and each first device can save the temporary identifier associated with that first device.

[0397] Optionally, the third indication information includes a bitmap, where each indication bit in the bitmap is associated with a first device, or each indication bit in the bitmap is associated with a random access resource (non-contentionable random access resource). The indication bits are used to indicate whether the fifth message includes a temporary identifier corresponding to the first device associated with the indication bit; a first value indicates that the fifth message includes the temporary identifier corresponding to the first device associated with the indication bit, and a second value indicates that the fifth message does not include the temporary identifier corresponding to the first device associated with the indication bit; the first and second values ​​are different, for example, the first value is 1 and the second value is 0, or the first value is 0 and the second value is 1. This method can indicate whether a temporary identifier for each first device is included. Optionally, the third indication information includes a temporary identifier corresponding to a resource index, where the resource index is used to indicate the random access resource corresponding to the first device associated with the resource index. For example, the third indication information indicates {resource index 1, AS ID 1; resource index 2, AS ID 2}, indicating that a temporary identifier AS ID 1 is assigned to the first device associated with resource index 1, and a temporary identifier AS ID 2 is assigned to the first device associated with resource index 2. This method can indicate devices configured with temporary identifiers.

[0398] Optionally, the fifth message includes a temporary identifier corresponding to each of the multiple first devices in the CFRA, and the temporary identifiers of each first device can be arranged in the order of the non-contention-based random access resource index. In this case, the temporary identifiers of multiple first devices can be carried directly in sequence in the fifth message, without needing to carry the aforementioned resource index or bitmap. After receiving the fifth message, each first device can determine its own AS ID based on the random access resource index.

[0399] Optionally, the fifth message includes a temporary identifier corresponding to the first device. For multiple first devices, the second device 102 can send the corresponding fifth message to each of the multiple first devices.

[0400] Optionally, the third indication information includes a bitmap, where each indication bit in the bitmap is associated with a first device, or each indication bit in the bitmap is associated with a random access resource (non-contentionable random access resource). The indication bits are used to indicate whether the fifth message includes a temporary identifier corresponding to the first device associated with the indication bit. Specifically, a first value for the indication bit indicates that the fifth message includes the temporary identifier corresponding to the first device associated with the indication bit, and a second value for the indication bit indicates that the fifth message does not include the temporary identifier corresponding to the first device associated with the indication bit; the first and second values ​​are different, for example, the first value is 1 and the second value is 0, or the first value is 0 and the second value is 1. This method can indicate whether the temporary identifier of each first device is included.

[0401] Optionally, the third indication information includes a bitmap, where each indication bit in the bitmap is associated with a first device, or each indication bit in the bitmap is associated with a random access resource (non-contentionable random access resource). The indication bits are used to indicate which first device's temporary identifier is contained in the fifth message. For example, when the indication bit is a first value or set to the first value, it indicates that the fifth message contains the temporary identifier of the first device associated with that indication bit. For example, the first value is 1.

[0402] Optionally, the third indication information includes a temporary identifier corresponding to the resource index, which is used to indicate the random access resource corresponding to the first device associated with the resource index. For example, the third indication information indicates that {resource index 1, AS ID 1} assigns a corresponding temporary identifier to the first device associated with resource index 1.

[0403] Optionally, the temporary identifier corresponding to the resource index can be a slot identifier, an access occasion identifier, or other identifier used to identify the random access resource.

[0404] The communication method involved in the embodiments of this disclosure may include at least one of steps S2401 to S2403. For example, step S2402 may be implemented as a separate embodiment, steps S2401 and S2402 may be implemented as separate embodiments, and steps S2402 and S2403 may be implemented as separate embodiments.

[0405] In some embodiments, steps S2401 and S2403 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0406] In some embodiments, step S2403 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0407] In some embodiments, step S2401 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0408] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0409] Figure 3A is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 3A, an indication method according to an embodiment of the present disclosure includes:

[0410] In step S3101, the first device 101 sends a first message for random access to the second device 102.

[0411] In some embodiments, the implementation of step S3101 can be referred to the implementation of step S2102 in FIG2A.

[0412] In step S3102, the second device 102 sends a second message to the first device 101.

[0413] In some embodiments, the implementation of step S3102 can be referred to the implementation of step S2103 in FIG2A.

[0414] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0415] Figure 3B is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 3B, an indication method according to an embodiment of the present disclosure includes:

[0416] Step S3201: The second device 102 sends a first paging message to the first device 101.

[0417] In some embodiments, the implementation of step S3201 can be referred to the implementation of step S2101 in FIG2A.

[0418] In step S3202, the first device 101 sends a first message for random access to the second device 102.

[0419] In some embodiments, the implementation of step S3202 can be found in the implementation of step S2102 in FIG2A.

[0420] In step S3203, the second device 102 sends a second message to the first device 101.

[0421] In some embodiments, the implementation of step S3203 can be found in the implementation of step S2103 in FIG2A.

[0422] In step S3204, the first device 101 sends or retransmits the third message to the second device 102.

[0423] In some embodiments, the implementation of step S3204 can be found in the implementation of step S2104 in FIG2A.

[0424] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0425] Figure 3C is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 3C, an indication method according to an embodiment of the present disclosure includes:

[0426] Step S3301: The second device 102 sends a first paging message to the first device 101.

[0427] In some embodiments, the implementation of step S3301 can be found in the implementation of step S2101 in FIG2A.

[0428] In step S3302, the first device 101 sends a first message for random access to the second device 102.

[0429] In some embodiments, the implementation of step S3302 can be found in the implementation of step S2102 in FIG2A.

[0430] In step S3303, the second device 102 sends a second message to the first device 101.

[0431] In some embodiments, the implementation of step S3303 can be found in the implementation of step S2103 in FIG2A.

[0432] In step S3304, the first device 101 sends or retransmits the third message to the second device 102.

[0433] In some embodiments, the implementation of step S3304 can be referred to the implementation of step S2104 in FIG2A.

[0434] Step S3305: The first device 101 releases the random number identifier.

[0435] In some embodiments, the implementation of step S3305 can refer to the implementation of steps S2105-S2107 in FIG2A, or the implementation of steps S2205-S2207 in FIG2B, or the implementation of steps S2305-S2306 in FIG2C.

[0436] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0437] Figure 3D is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 3D, an indication method according to an embodiment of the present disclosure includes:

[0438] In step S3401, the second device 102 sends a fifth paging message to the first device 101.

[0439] In some embodiments, the implementation of step S3401 can be found in the implementation of step S2401 in FIG2D.

[0440] In step S3402, the first device 101 sends a fourth message or a first message to the second device 102 on the random access resource corresponding to the first device.

[0441] In some embodiments, the implementation of step S3402 can be found in the implementation of step S2402 in FIG2D.

[0442] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0443] Figure 3E is an interactive schematic diagram illustrating an indication method according to an embodiment of the present disclosure. As shown in Figure 3E, an indication method according to an embodiment of the present disclosure includes:

[0444] In step S3501, the second device 102 sends a fifth paging message to the first device 101.

[0445] In some embodiments, the implementation of step S3501 can be found in the implementation of step S2401 in FIG2D.

[0446] In step S3502, the second device 102 sends a fifth message to the first device 101.

[0447] In some embodiments, the implementation of step S3502 can be found in the implementation of step S2403 in FIG2D.

[0448] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0449] This disclosure proposes an AS ID processing method, clarifying how IoT devices distinguish between msg2 in the inventory-only process and msg2 in the inventory+command process, clarifying how to assign AS IDs to multiple IoT devices through command in scenarios where CFRA supports multiple IoT devices, and clarifying how IoT devices release RN16.

[0450] In some embodiments, the IoT device corresponds to the first device in the foregoing embodiments, msg2 corresponds to the second message in the foregoing embodiments, AS ID corresponds to the temporary identifier in the foregoing embodiments, and RN16 corresponds to the random number identifier in the foregoing embodiments.

[0451] To facilitate understanding of the embodiments of this disclosure, some embodiments are listed below:

[0452] Example 1: Define two types of msg2, distinguished by message type.

[0453] Example 1-1: Define two types of msg2, used for inventory+command processes and inventory-only processes respectively. The two types of msg2 are distinguished by their msg type (R2D msg type). For example, this R2D msg type is a 4-bit indicator bit. Setting it to the first value (e.g., 0000) indicates the msg2 for inventory+command processes, and setting it to the second value (e.g., 0001) indicates the msg2 for inventory-only processes. The number of bits occupied by the R2D msg type, and the values ​​of the first and second values, are not specifically limited.

[0454] Optionally, the msg type corresponds to the service type in the foregoing embodiments.

[0455] Example 1-2: Define a type of msg2, which further indicates whether msg2 is used for inventory+command or inventory-only processes through a first indicator bit. For example, the first indicator bit is 1 bit, set to a third value (e.g., 0) to indicate msg2 for inventory+command processes, and set to a fourth value (e.g., 1) to indicate msg2 for inventory-only processes. The number of bits occupied by the first indicator bit, and the values ​​of the third and fourth values, are not specifically limited.

[0456] Examples 1-3: In the inventory+command's msg2, for each successfully connected IoT device, the AS ID of that IoT device is always carried. If the Reader determines that RN16 in msg1 can be reused as an AS ID, the Reader carries RN16 in msg1 as an AS ID in msg2. Alternatively, if the Reader determines that RN16 in msg1 cannot be reused as an AS ID, the Reader reassigns an AS ID.

[0457] Optionally, msg1 corresponds to the first message in the foregoing embodiments.

[0458] Example 2: For CFRA, the first command to assign an AS ID carries the resource index.

[0459] Example 2-1: CFRA supports multiple IoT devices. The paging command carries the identifiers of multiple IoT devices and the random access resources for each IoT device. These random access resources are non-contentionable random access resources. The first command can be a read command, write command, kill command, disable command, etc.

[0460] The resource index is the random access resource index corresponding to the IoT device. This random access resource is used to send the IoT device's msg1 (msg1 in CFRA, containing the device identifier of the IoT device, such as the device identifier assigned by the EPC or core network). The resource index can be a slot identifier, an access occasion identifier, or other identifier that can identify the random access resource. For example, the resource index can be a bitmap, where multiple IoT devices each correspond to an indicator bit in the bitmap, or multiple IoT devices' random access resources each correspond to an indicator bit in the bitmap. The indicator position (or indicator bit) is a fourth value used to indicate the AS ID of the IoT device corresponding to the indicator bit carried in the first command. The indicator position is a third value used to indicate the AS ID of the IoT device whose indicator bit is not carried in the first command.

[0461] Optionally, the paging command corresponds to the fifth paging message in the foregoing embodiments, the first command corresponds to the fifth message in the foregoing embodiments, the msg1 of the IoT device or the msg1 in CFRA corresponds to the fourth message or the first message in the foregoing embodiments, the resource index corresponds to the third indication information in the foregoing embodiments, the indication position is the fourth value corresponds to the indication bit is the first value in the foregoing embodiments, and the indication position is the third value corresponds to the indication bit is the first value in the foregoing embodiments.

[0462] Example 3: During CBRA, the IoT device receives an R2D message triggering re-access and releases RN16. The IoT device receives a paging message with a different transaction ID and releases RN16.

[0463] Optionally, the R2D message that triggers re-access corresponds to the second paging message in the foregoing embodiments, the transaction ID corresponds to the service identifier in the foregoing embodiments, and the paging message with a different transaction ID corresponds to the third or fourth paging message in the foregoing embodiments.

[0464] Example 3-1: The IoT device receives an R2D message that triggers re-access and releases RN16. RN16 is a 16-bit random number carried in msg1 during the CBRA process. For example, this R2D message can be a paging message. For example, this paging message has the same transaction ID as the paging message responded to by the IoT device.

[0465] Example 3-2: The IoT device confirms that msg3 (containing the IoT device identifier, such as the device identifier assigned by the EPC or the core network) was successfully sent, and the IoT device releases RN16.

[0466] Optionally, msg3 corresponds to the third message in the foregoing embodiments.

[0467] Example 3-3: After the IoT device sends msg3, it does not receive a NACK message. The IoT device receives an R2D message that triggers re-access and releases RN16.

[0468] Examples 3-4: For instance, after an IoT device sends msg3 and receives a NACK message, this NACK message does not contain the IoT device's RN16 and / or AS ID, and the IoT device releases the RN16 and / or AS ID. For instance, after an IoT device sends msg3 and receives a NACK message, this NACK message contains the IoT device's RN16 and / or AS ID, and the IoT device releases the RN16 and / or AS ID. For instance, this NACK message may contain the RN16 or AS ID of one or more IoT devices to trigger re-access for one or more IoT devices.

[0469] Optionally, the NACK message corresponds to the second indication information in the foregoing embodiments.

[0470] Example 3-5: When the IoT device receives a paging message with a different transaction ID (associated with different services and / or sessions), the IoT device releases RN16 (regardless of whether the IoT device is paged by the paging message with the different transaction ID).

[0471] Optionally, the paging messages with different transaction IDs in embodiments 3-5 correspond to the fourth paging message in the aforementioned embodiments.

[0472] Example 3-6: When the IoT device receives a paging message with a different transaction ID (associated with different services and / or sessions), the IoT device belongs to the IoT device paged by the paging message with the different transaction ID, and the IoT device releases RN16.

[0473] Optionally, the paging messages with different transaction IDs in embodiments 3-6 correspond to the third paging message in the aforementioned embodiments.

[0474] Examples 3-7: When an IoT device receives a paging message, this message triggers the device to send a new message (msg1), for example, triggering a CBRA (Continuous Transaction Redirect). The new RN16 in the new message replaces the old RN16. The paging message can have the same transaction ID (e.g., in a re-access case) or a different transaction ID.

[0475] Optionally, the paging messages in embodiments 3-7 correspond to the second paging message, the third paging message, or the fourth paging message in the foregoing embodiments.

[0476] Example 4: The solutions described in Examples 1 to 3 above are applicable to inventory-only processes. Examples 1 to 3 above are applicable to inventory+command processes.

[0477] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0478] This disclosure also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed that includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0479] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0480] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0481] Figure 4A is a schematic diagram of the terminal structure proposed in an embodiment of this disclosure. The first device 4100 is used to execute any of the above methods. In some embodiments, as shown in Figure 4A, the first device 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module 4101 is used to send a first message for random access to the second device; the transceiver module 4101 is also used to receive a second message sent by the second device, the second message including first indication information, the first indication information being used to indicate the service type corresponding to the second message. Optionally, the transceiver module 4101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module 4102 is used to execute at least one of the other steps performed by the terminal 101 in any of the above methods, which will not be elaborated here.

[0482] Figure 4B is a schematic diagram of the network device proposed in an embodiment of this disclosure. The second device 4200 is used to execute any of the above methods. In some embodiments, as shown in Figure 4B, the second device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to receive a first message for random access sent by the first device; the transceiver module 4201 is also used to send a second message to the first device, the second message including first indication information, the first indication information being used to indicate the service type corresponding to the second message. Optionally, the transceiver module 4201 is used to execute at least one of the communication steps (such as sending and / or receiving) executed by the second device 4200 in any of the above methods (but not limited to these), which will not be elaborated here. Optionally, the processing module 4202 is used to execute at least one of the other steps executed by the second device 4200 in any of the above methods, which will not be elaborated here.

[0483] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0484] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0485] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0486] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this disclosure. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0487] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0488] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above-described method, and the processor 5101 performs at least one of the other steps. In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0489] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.

[0490] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this disclosure is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection having one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0491] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this disclosure. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.

[0492] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0493] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0494] In some embodiments, the interface circuit 5202 performs at least one of the communication steps, such as sending and / or receiving, in the above-described method. For example, the interface circuit 5202 performing the communication steps, such as sending and / or receiving, in the above-described method means that the interface circuit 5202 performs data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of the other steps.

[0495] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0496] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0497] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0498] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0499] During the process of the first device accessing the second device, it can know the type based on the first indication information in the second message, so that the first device can perform reasonable business processing based on the type corresponding to the second message and improve communication performance.

Claims

A method of indicating, performed by a first device, the method comprising: sending, to a second device, a first message for random access; receiving a second message sent by the second device, the second message comprising first indication information, the first indication information being used to indicate a type of the second message. The method of claim 1, wherein the first indication information is used to indicate that the type of the second message is a first type or a second type, wherein the first type corresponds to inventory and command, and the second type corresponds to inventory only. The method of claim 1 or 2, wherein the second message comprises at least one temporary identifier, wherein each temporary identifier in the at least one temporary identifier corresponds to one first device that successfully sends the first message; and wherein the type of the second message is the first type. The method of claim 1 or 2, wherein the second message does not comprise at least one temporary identifier, wherein each temporary identifier in the at least one temporary identifier corresponds to one first device that successfully sends the first message; and wherein the type of the second message is the second type. The method of any one of claims 1 to 4, wherein, The method further comprises: before sending the first message, receiving a first paging message sent by the second device, the first paging message being used to page a plurality of first devices for contention-based random access (CBRA) access; after receiving the second message, sending or re-sending, to the second device, a third message, the third message comprising a device identifier of the first device. The method of claim 5, wherein the first message comprises a random number identifier corresponding to the first device. The method of claim 6, wherein, The method further comprises: after sending or re-sending the third message, until receiving a second paging message sent by the second device for triggering re-access, the first device has not received second indication information, determining that the sending of the third message is successful; wherein the second paging message has a same service identifier as the first paging message, and the second indication information is used to indicate one or more first devices that need to re-access. The method of claim 7, wherein, The method further comprises: after receiving the second paging message, releasing the random number identifier. The method of claim 6, wherein, The method further comprises: after sending or re-sending the third message, receiving second indication information sent by the second device; wherein the second indication information is used to indicate one or more first devices that need to re-access. According to claim 9, wherein the second indication information does not comprise the random number identifier of the first device, and the sending of the third message is successful; or the second indication information comprises the random number identifier of the first device, and the sending of the third message is failed. The method of claim 9 or 10, wherein, The method further comprises: after receiving the second indication information, releasing the random number identifier. The method of claim 6, wherein, The method further comprises: after sending or re-sending the first message, receiving a third paging message sent by the second device, the third paging message having a different service identifier from the first paging message, and the third paging message being used to page the first device. Receiving the third paging message releases the random number identifier. The method of claim 6, wherein, The method further includes: After sending the third message, receiving a fourth paging message sent by the second device, the fourth paging message being different from the service identifier of the first paging message; Receiving the fourth paging message releases the random number identifier. The method of claim 1, wherein, The method further includes: Receiving a fifth paging message sent by the second device, the fifth paging message being used for paging a plurality of first devices for contention-free random access (CFRA), the fifth paging message including at least one of the following: Device identifiers of the plurality of first devices, each first device of the plurality of first devices corresponding to a random access resource. The method of claim 14, wherein Sending a fourth message on the random access resource corresponding to the first device, the fourth message including a device identifier corresponding to the first device. The method of claim 14, wherein, The method further includes: Receiving a fifth message sent by the second device, the fifth message being used for indicating whether the temporary identifier corresponding to the first device is included in the fifth message. The method of claim 16, wherein The fifth message includes a bitmap, each indication bit in the bitmap being associated with a first device, the indication bit being used for indicating whether the temporary identifier corresponding to the first device associated with the indication bit is included in the fifth message; wherein the indication bit being a first value indicates that the temporary identifier corresponding to the first device associated with the indication bit is included in the fifth message, and the indication bit being a second value indicates that the temporary identifier corresponding to the first device associated with the indication bit is not included in the fifth message. Alternatively, the fifth message includes a temporary identifier corresponding to a resource index, the resource index being used for indicating the random access resource corresponding to the first device associated with the resource index. The method of claim 16 or 17, wherein, The fifth message is at least one of the following: A paging message, a command message. An indication method is performed by a second device, the method including: Receiving a first message sent by a first device for random access; Sending a second message to the first device, the second message including first indication information, the first indication information being used for indicating a type corresponding to the second message. The method of claim 19, wherein The first indication information is used for indicating that the type corresponding to the second message is a first type or a second type, wherein the first type corresponds to inventory and command, and the second type corresponds to inventory only. The method of claim 19 or 20, wherein The second message includes at least one temporary identifier, wherein each temporary identifier in the at least one temporary identifier corresponds to a first device that successfully sends the first message; wherein the type corresponding to the second message is the first type. The method of claim 19 or 20, wherein The second message does not include at least one temporary identifier, wherein each temporary identifier in the at least one temporary identifier corresponds to a first device that successfully sends the first message; wherein the type corresponding to the second message is the second type. The method of any one of claims 19 to 22, wherein, The method further includes: Before receiving the first message, a first paging message is sent to the first device, the first paging message being used to page a plurality of first devices for CBRA access; After sending the second message, a third message sent by the first device is received, the third message containing a device identity of the first device. The method of claim 23, wherein, The first message includes a random number identity corresponding to the first device. The method of claim 24, wherein, The method further includes: A second paging message is sent to the first device, the second paging message being used to trigger re-access. The method of claim 24, wherein, The method further includes: After receiving the third message, second indication information is sent to the first device; wherein the second indication information is used to indicate one or more first devices that need to re-access. The method of claim 26, wherein, The second indication information does not contain a random number identity of the first device, and the third message is sent successfully; or The second indication information contains a random number identity of the first device, and the third message is sent unsuccessfully. The method of claim 24, wherein, The method further includes: After receiving the third message, a third paging message is sent to the first device, the third paging message being different from a service identity of the first paging message, and the third paging message being used to page the first device. The method of claim 28, wherein, The method further includes: After receiving the third message, a fourth paging message is sent to the first device, the fourth paging message being different from a service identity of the first paging message. The method of claim 19, wherein, The method further includes: A fifth paging message is sent to the first device, the fifth paging message being used to page a plurality of first devices for CFRA, and the fifth paging message including at least one of the following: Device identities of the plurality of first devices, and random access resources corresponding to each of the plurality of first devices. The method of claim 30, wherein, A fourth message is received on the random access resources corresponding to the first device, the fourth message including a device identity corresponding to the first device. The method of claim 31, wherein, The method further includes: A fifth message is sent to the first device, the fifth message being used to indicate whether the fifth message contains temporary identities corresponding to the plurality of first devices. The method of claim 32, wherein, The fifth message includes a bitmap, each indication bit in the bitmap being associated with a first device, and the indication bit being used to indicate whether the fifth message includes a temporary identity corresponding to the first device associated with the indication bit; wherein the indication bit being a first value is used to indicate that the fifth message includes the temporary identity corresponding to the first device associated with the indication bit, and the indication bit being a second value is used to indicate that the fifth message does not include the temporary identity corresponding to the first device associated with the indication bit; Or, the fifth message includes a temporary identity corresponding to a resource index, the resource index being used to indicate random access resources corresponding to the first device associated with the resource index. The method of any one of claims 32 or 33, wherein, The fifth message is at least one of the following: A paging message, a command message. A communication device, wherein, The communication device is configured to perform the method of any one of claims 1-18 or any one of claims 19-34. A communication system comprising a first device and a second device, wherein The first device is configured to implement the method of any one of claims 1-18; The second device is configured to implement the method of any one of claims 19-34. A communication method performed by a communication system, the communication system comprising a first device and a second device, wherein The method comprises: The first device sends a first message for random access to the second device; The second device sends a second message to the first device, the second message comprising first indication information, the first indication information being used to indicate a type corresponding to the second message. A storage medium storing instructions, wherein The instructions, when executed on a communication device, cause the communication device to perform the method of any one of claims 1-18 or any one of claims 19-34. A program product comprising at least one of a program, instructions, wherein At least one of the program, the instructions, when executed on a communication device, implements the method of any one of claims 1-18 or any one of claims 19-34.