Information processing method, first device, internet of things device, communication system, and storage medium

Abstract

The present disclosure relates to an information processing method, a first device, an Internet of Things device, a communication system, and a storage medium. The method comprises: a first device sending first information, wherein the first information is used for requesting an Internet of Things device to send second information; and receiving the second information, wherein the second information is used for indicating information of the Internet of Things device. Therefore, the first device can reliably acquire the information of the Internet of Things device, thereby realizing reliable reading of data information of the Internet of Things device.

Description

Information processing method, first device, Internet of Things device, communication system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to an information processing method, a first device, an Internet of Things device, a communication system, and a storage medium. Background Art

[0002] Ambient-IoT (Ambient Internet of Things) is a new IoT technology. Compared with traditional IoT technology, a notable feature is the large number of Ambient-IoT devices in the network, which can inventory and store large quantities of items.

[0003] Summary of the Invention

[0004] The problem of how to obtain data information of IoT devices in IoT-based networks remains to be solved.

[0005] The embodiments of the present disclosure provide an information processing method, a first device, an Internet of Things device, a communication system, and a storage medium, which are used to solve the problem of how to obtain data information of an Internet of Things device.

[0006] According to a first aspect of an embodiment of the present disclosure, an information processing method is provided, which is executed by a first device. The method includes:

[0007] Sending first information, where the first information is used to request the IoT device to send second information;

[0008] The second information is received, where the second information is used to indicate information of the IoT device.

[0009] According to a second aspect of an embodiment of the present disclosure, an information processing method is proposed, which is executed by an Internet of Things device. The method includes:

[0010] Receive first information sent by a first device, where the first information is used to request the IoT device to send second information;

[0011] The second information is sent, where the second information is used to indicate information of the IoT device.

[0012] According to a third aspect of an embodiment of the present disclosure, a first device is provided, the first device including:

[0013] a transceiver module, configured to send first information, where the first information is used to request the IoT device to send second information;

[0014] The transceiver module is further configured to receive the second information, where the second information is used to indicate information of the IoT device.

[0015] According to a fourth aspect of the embodiments of the present disclosure, an Internet of Things device is provided, comprising:

[0016] a transceiver module, configured to receive first information sent by a first device, where the first information is used to request the IoT device to send second information;

[0017] The transceiver module is further configured to send the second information, where the second information is used to indicate information of the IoT device.

[0018] According to a fifth aspect of the embodiments of the present disclosure, a first device is provided, including:

[0019] one or more processors;

[0020] A memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the first device executes the information processing method described in the first aspect.

[0021] According to a sixth aspect of the embodiments of the present disclosure, an Internet of Things device is provided, including:

[0022] one or more processors;

[0023] A memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the Internet of Things device executes the information processing method described in the second aspect.

[0024] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a first device and an Internet of Things device, wherein the first device is configured to implement the information processing method described in the first aspect, and the Internet of Things device is configured to implement the information processing method described in the second aspect.

[0025] According to an eighth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the information processing method as described in the first aspect or the second aspect.

[0026] By implementing the above aspects of the present disclosure, the first device can reliably obtain the information of the IoT device, thereby achieving reliable reading of the data information of the IoT device. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0028] FIG1A is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0029] FIG1B is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0030] FIG1C is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0031] FIG1D is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0032] FIG1E is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.

[0033] [Corrected 31.01.2024 according to Rule 91] Figure 2 is an exemplary interactive diagram of the information processing method provided according to an embodiment of the present disclosure.

[0034] FIG3A is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0035] FIG3B is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0036] FIG3C is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0037] FIG3D is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0038] FIG4A is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0039] FIG4B is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0040] FIG4C is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0041] FIG4D is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0042] FIG5 is an exemplary interaction diagram of an information processing method provided according to an embodiment of the present disclosure.

[0043] FIG6 is a schematic diagram of an exemplary flow chart of an information processing method provided according to an embodiment of the present disclosure.

[0044] FIG7A is a schematic diagram of an exemplary structure of a first device provided according to an embodiment of the present disclosure.

[0045] FIG7B is a schematic diagram of an exemplary structure of an Internet of Things device provided according to an embodiment of the present disclosure.

[0046] FIG8A is a schematic diagram of an exemplary structure of a communication device provided according to an embodiment of the present disclosure.

[0047] FIG8B is a schematic diagram of an exemplary structure of a communication device provided according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0048] The embodiments of the present disclosure provide an information processing method, a first device, an Internet of Things device, a communication system, and a storage medium.

[0049] In a first aspect, an embodiment of the present disclosure provides an information processing method, which is executed by a first device. The method includes:

[0050] Sending first information, where the first information is used to request the IoT device to send second information;

[0051] The second information is received, where the second information is used to indicate information of the IoT device.

[0052] In the above embodiment, the first device sends the first information to the IoT device, which enables the IoT device to send the second information to the first device, thereby enabling the first device to reliably obtain the information of the IoT device, thereby realizing reliable reading of the IoT device information.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following:

[0054] IoT device identifier, used to identify the IoT device;

[0055] The IoT device group identifier is used to identify the IoT device group to which the IoT device belongs.

[0056] In the above embodiment, by sending the IoT device identifier and / or IoT device group identifier, the first device can accurately send the request for obtaining information to the target IoT device, and thus can more reliably read the data information of the target IoT device.

[0057] In combination with some embodiments of the first aspect, in some embodiments, the IoT device identifier and / or the IoT device group identifier are configured by the first device for the IoT device.

[0058] In the above embodiment, the first device can pre-configure the IoT device identifier and / or IoT device group identifier for the IoT device before obtaining the information of the IoT device, which can effectively ensure that the reading request of the data information of the IoT device can be reliably sent to the target IoT device, thereby improving the accuracy of data information acquisition.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes an identity verification code, and the identity verification code is used by the Internet of Things device to perform identity verification on the first device;

[0060] The second information is sent by the IoT device when it determines that the identity verification has passed based on the identity verification code.

[0061] In the above embodiment, the first device sends an identity verification code, so that the Internet of Things device can verify the identity of the sender of the first information based on the identity verification code, which can reliably prevent illegal devices from obtaining data information of the Internet of Things device and effectively ensure the security of the data.

[0062] In combination with some embodiments of the first aspect, in some embodiments, the first identity verification code sent by the first device to the Internet of Things device is different from the second identity verification code sent by the second device to the Internet of Things device; or

[0063] The third identity verification code sent by the first device to the first Internet of Things device is different from the fourth identity verification code sent by the first device to the second Internet of Things device.

[0064] In the above embodiment, different first devices can configure different identity verification codes for different Internet of Things devices, which effectively improves the flexibility of identity verification code configuration, further avoids the Internet of Things devices sending their data information to illegal devices, and effectively improves data security.

[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes scheduling request information, where the scheduling request information is used to request the IoT device to send the second information;

[0066] The second information is sent by the IoT device in response to the scheduling request information.

[0067] In the above embodiment, the IoT device may be requested to send the second information by sending a scheduling request message, which can effectively save signaling and improve the reliability of data interaction between the first device and the IoT device.

[0068] In conjunction with some embodiments of the first aspect, in some embodiments, the first information includes scheduling indication information, where the scheduling indication information is used to indicate a type of data included in the second information;

[0069] The second information is determined by the IoT device based on the scheduling indication information.

[0070] In the above embodiment, the first device can instruct the IoT device to send specific data information to the first device by sending scheduling indication information, so that the IoT device only sends the data required by the first device, effectively reducing the data transmission volume and saving resource overhead.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the second information includes at least one of the following:

[0072] sensor data detected by the IoT device;

[0073] The coding information of the Internet of Things device includes at least one code field.

[0074] In the above embodiment, the IoT device can send the sensor data collected by its sensor through the second information, and can also send part or all of the code field of its encoded information, so that the first device can effectively obtain this information, and then further control or configure the IoT device based on this information.

[0075] In conjunction with some embodiments of the first aspect, in some embodiments, before receiving the second information, the method includes:

[0076] Receive third information, the third information including at least one of the following:

[0077] first feedback information, where the first feedback information is used to indicate whether the IoT device allows the first device to read data information;

[0078] second feedback information, where the second feedback information is used to request energy supply from the first device;

[0079] Third feedback information, where the third feedback information is used to indicate a time offset when the first device sends the second information.

[0080] In the above embodiment, the IoT device can send the third information so that the first device can obtain the feedback information of the IoT device regarding the first information, and then determine whether to expect to receive the second information, and / or send a charging signal, and / or determine the time to receive the second information. This can reduce the monitoring power or stop monitoring when there is no need to receive the second information, effectively reducing the power consumption of the first device, and can also more accurately realize the reception of the second information, thereby improving the robustness of communication.

[0081] With reference to some embodiments of the first aspect, in some embodiments, receiving the second information includes:

[0082] Ensure that the first condition is met;

[0083] The second information is received, wherein the first condition includes at least one of the following:

[0084] receiving the first feedback information, where the first feedback information is used to instruct the IoT device to allow the first device to read data information;

[0085] The second feedback information is received, and the charging signal is sent for a first duration;

[0086] The third feedback information is received, and the waiting time reaches the time offset.

[0087] In the above embodiment, one or more of the first feedback information, the second feedback information, and the third feedback information can be used to more accurately determine whether to receive the second information or the time to receive the second information, effectively reducing the power consumption of the first device while improving the reliability of communication.

[0088] In combination with some embodiments of the first aspect, in some embodiments, the first duration is determined based on the time offset; or, the first duration is predefined by a protocol.

[0089] In the above embodiment, the first duration can be determined by time offset, and can also be determined based on a protocol, so that the first device can receive the second information more reliably, thereby improving the reliability of information reading of the IoT device.

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

[0091] receiving fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device;

[0092] The scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the first data type.

[0093] In the above embodiment, the IoT device can report the data types it can support to the first device through the fourth information, so that the first device can send the first information based on the data types it can support, thereby avoiding the first device requesting to obtain data types it does not support, resulting in a waste of resource overhead.

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

[0095] receiving fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device;

[0096] Sending fifth information, where the fifth information is used to configure a data type of the IoT device to be a second data type, where the second data type includes at least one data type included in the first data type;

[0097] The scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the second data type.

[0098] In the above embodiment, the first device can obtain the data type that the Internet of Things device can support by receiving the fourth information, and configure the data type of the Internet of Things device to the data type that it can support through the fifth information, which can effectively ensure that the data type of the Internet of Things device is the data type it supports, thereby improving the effectiveness of the data information reading of the first device.

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

[0100] Sending sixth information, where the sixth information is used to configure the data type of the IoT device to be the third data type;

[0101] The scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the third data type.

[0102] In the above embodiment, the first device can configure the data type of the IoT device to the data type it requires by sending the sixth information, thereby enabling the first device to effectively obtain the data it requires.

[0103] In conjunction with some embodiments of the first aspect, in some embodiments, the first device includes at least one of the following:

[0104] Access network equipment, core network equipment, terminals, radio frequency readers, intermediate node equipment, and auxiliary node equipment.

[0105] In the above embodiment, all the above devices capable of communicating with the IoT device can reliably obtain the data of the IoT device.

[0106] In combination with some embodiments of the first aspect, in some embodiments, the first information includes at least one of the following: an Internet of Things device identifier, used to identify the Internet of Things device; an Internet of Things device group identifier, used to identify the Internet of Things device group in which the Internet of Things device is located; an identity verification code, used to perform identity verification on the Internet of Things device; scheduling request information, the scheduling request information is used to request the Internet of Things device to send the second information; scheduling indication information, used to indicate the type of data included in the second information.

[0107] In combination with some embodiments of the first aspect, in some embodiments, the second information is sent when a third condition is met, and the third condition includes at least one of the following: the Internet of Things device determines that the identity verification is passed based on the identity verification code; the Internet of Things device receives scheduling request information; the Internet of Things device receives scheduling indication information, and determines to obtain the second information based on the scheduling indication information.

[0108] In a second aspect, an embodiment of the present disclosure provides an information processing method, which is executed by an IoT device. The method includes:

[0109] Receive first information sent by a first device, where the first information is used to request the IoT device to send second information;

[0110] The second information is sent, where the second information is used to indicate information of the IoT device.

[0111] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes at least one of the following:

[0112] IoT device identifier, used to identify the IoT device;

[0113] The IoT device group identifier is used to identify the IoT device group to which the IoT device belongs.

[0114] In combination with some embodiments of the second aspect, in some embodiments, the IoT device identifier and / or the IoT device group identifier are configured by the first device for the IoT device.

[0115] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes an identity verification code, and the identity verification code is used by the Internet of Things device to perform identity verification on the first device;

[0116] The second information is sent by the IoT device when it determines that the identity verification has passed based on the identity verification code.

[0117] In combination with some embodiments of the second aspect, in some embodiments, the first identity verification code received by the Internet of Things device from the first device is different from the second identity verification code received by the Internet of Things device from the second device; or

[0118] The Internet of Things device is a first Internet of Things device, and the third identity verification code received by the first Internet of Things device from the first device is different from the fourth identity verification code received by the second Internet of Things device from the first device.

[0119] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes scheduling request information, where the scheduling request information is used to request the IoT device to send the second information;

[0120] The second information is sent by the IoT device in response to the scheduling request information.

[0121] In conjunction with some embodiments of the second aspect, in some embodiments, the first information includes scheduling indication information, where the scheduling indication information is used to indicate a type of data included in the second information;

[0122] The second information is determined by the IoT device based on the scheduling indication information.

[0123] In conjunction with some embodiments of the second aspect, in some embodiments, the second information includes at least one of the following:

[0124] sensor data detected by the IoT device;

[0125] The coding information of the Internet of Things device includes at least one code field.

[0126] In conjunction with some embodiments of the second aspect, in some embodiments, before sending the second information, the method includes:

[0127] Sending third information, wherein the third information includes at least one of the following:

[0128] first feedback information, where the first feedback information is used to indicate whether the IoT device allows the first device to read data information;

[0129] second feedback information, where the second feedback information is used to request energy supply from the first device;

[0130] Third feedback information, where the third feedback information is used to indicate a time offset when the first device sends the second information.

[0131] With reference to some embodiments of the second aspect, in some embodiments, sending the second information includes:

[0132] Determining that the second condition is met;

[0133] The second information is sent, where the second condition includes at least one of the following:

[0134] The first feedback information has been sent, and the first feedback information is used to instruct the IoT device to allow the first device to read data information;

[0135] The second feedback information has been sent;

[0136] The third feedback information has been sent.

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

[0138] Sending fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device;

[0139] The data type indicated by the scheduling indication information is at least one data type included in the first data type.

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

[0141] Sending fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device;

[0142] Receive fifth information, where the fifth information is used to configure a data type of the IoT device to be a second data type, where the second data type includes at least one data type included in the first data type;

[0143] The data type indicated by the scheduling indication information is at least one data type included in the second data type.

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

[0145] receiving sixth information, where the sixth information is used to configure a data type of the IoT device to be a third data type;

[0146] The data type indicated by the scheduling indication information is at least one data type included in the third data type.

[0147] In conjunction with some embodiments of the second aspect, in some embodiments, the first device includes at least one of the following:

[0148] Access network equipment, core network equipment, terminals, radio frequency readers, intermediate node equipment, and auxiliary node equipment.

[0149] In a third aspect, an embodiment of the present disclosure proposes a first device, which includes at least one of a transceiver module and a processing module; wherein the first device is used to execute an optional implementation method of the first aspect.

[0150] In a fourth aspect, an embodiment of the present disclosure proposes an Internet of Things device, which includes at least one of a transceiver module and a processing module; wherein the Internet of Things device is used to execute the optional implementation method of the second aspect.

[0151] In a fourth aspect, an embodiment of the present disclosure proposes a first device, which includes: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the first device executes an optional implementation method of the first aspect.

[0152] In a fifth aspect, an embodiment of the present disclosure proposes an Internet of Things device, which includes: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the Internet of Things device is enabled.

[0153] In a sixth aspect, an embodiment of the present disclosure proposes a communication system, which includes: a first device and an Internet of Things device; wherein the first device is configured to execute the method described in the optional implementation manner of the first aspect, and the Internet of Things device is configured to execute the method described in the optional implementation manner of the second aspect.

[0154] In a seventh aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0155] In an eighth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first and second aspects.

[0156] In a ninth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first and second aspects.

[0157] In a tenth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first and second aspects above.

[0158] It is understandable that the first device, IoT device, communication system, storage medium, program product, computer program, chip, or chip system described above are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0159] The present disclosure provides an information processing method, a first device, an Internet of Things device, a communication system, and a storage medium. In some embodiments, the terms "information processing method" and "information reading method" and "information sending method" and "communication method" are interchangeable; the terms "information processing device" and "information reading device" and "information sending device" and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0160] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0161] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0162] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0163] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0164] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0165] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0166] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0167] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0168] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0169] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0170] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0171] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

[0172] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0173] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0174] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or 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", "bandwidth part (BWP)", etc.

[0175] In some embodiments, "terminal" or "terminal device" may be referred to as "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, client, etc.

[0176] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

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

[0178] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0179] FIG1A is a schematic diagram illustrating the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1A , a communication system 100 includes a first device 101 and an IoT device 102 .

[0180] In some embodiments, the IoT device 102 may be an A-IoT (Ambient Internet of Things) device, an Ambient-IoT device, or an Ambient-IoT terminal. Alternatively, an A-IoT device may also be referred to as an "A-IOT device," "A-IOT Tag," "A-IOT UE," etc., which is not limited in the present disclosure.

[0181] In some embodiments, the intermediate node device and the auxiliary node device may be devices in an Ambient-IoT network. Optionally, the intermediate node device and the auxiliary node device may also be Ambient-IoT devices.

[0182] 1B , in some embodiments, the IoT device 102 may be directly connected to a base station 1011. In such a networking approach, the base station 1011 may be provided as the first device 101.

[0183] 1C , in some embodiments, a base station 1011 can be connected to an intermediate node device 1012 for uplink and downlink communications, and an IoT device 102 can be connected to the intermediate node device 1012 for uplink and downlink communications. In such a networking configuration, both the base station 1011 and the intermediate node device 1012 can be provided as the first device 101.

[0184] 1D , in some embodiments, a base station 1011 is connected to an auxiliary node device 1013 for uplink and downlink communications, and the auxiliary node device 1013 is also connected to an IoT device 102 for uplink and downlink communications. In such a networking configuration, both the base station 1011 and the auxiliary node device 1013 can be provided as the first device 101.

[0185] 1E , in some embodiments, UE 1014 is connected to and performs uplink and downlink communications with IoT device 102 . In such a networking approach, UE 1014 may be provided as first device 101 .

[0186] Optionally, UE 1014 may also be connected to an access network device and perform uplink and downlink communications.

[0187] In some embodiments of the present disclosure, IoT device 102 is an Ambient-IoT device within an Ambient-IoT network architecture. In some embodiments, the number of Ambient-IoT devices within an Ambient-IoT network is substantial, enabling the inventory and storage of large quantities of items. Compared to NB-IoT devices, Ambient-IoT devices have a simpler structure, lower hardware and maintenance costs, and may or may not include a power supply.

[0188] Alternatively, devices with power supplies can be called active devices, while those without power supplies can be called passive devices. Passive devices are characterized by being powered by other devices or natural conditions, requiring no maintenance. Active devices may contain a small amount of energy storage devices, such as capacitors, to provide power for communications.

[0189] In some embodiments, Ambient-IoT devices can be divided into three categories: Device A has no energy storage capability and cannot perform independent signal generation / amplification; Device B has energy storage capability but cannot perform independent signal generation; and Device C has energy storage capability and can generate signals independently.

[0190] In some embodiments, the first device 101 may be any one of the following: an access network device, a core network device, a terminal, a radio frequency reader / writer, an intermediate node device, or an auxiliary node device.

[0191] In some embodiments, the RF reader is a device capable of reading data from an Ambient-IoT device and / or writing data to an Ambient-IoT device. Optionally, the RF reader can also be integrated into a communication device such as a terminal, an intermediate node device, an auxiliary node device, or a network device such as a base station.

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

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

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

[0195] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0196] In some embodiments, the core network device may be a single device including a first network element, a second network element, etc., or may be a plurality of devices or a group of devices, each including all or part of the first network element, the second network element, etc. The network element may be virtual or physical. The core network may include, for example, at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next generation core (NGC).

[0197] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0198] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1A , or a portion thereof, but are not limited thereto. The entities shown in FIG1A are illustrative only. The communication system may include all or part of the entities shown in FIG1A , or may include other entities other than those shown in FIG1A . The number and form of the entities may be arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0199] The embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0200] In some embodiments, the structure of an Ambient-IoT device is relatively simple, and the data information it contains potentially includes various types, such as data information and control information. In some embodiments, one form of data information is coded information, such as Ambient-IoT code. Ambient-IoT code can include multiple code fields, which can be configured in the same or different ways.

[0201] In some embodiments, there are three configuration modes for a certain code domain: static configuration, semi-static configuration, and dynamic configuration.

[0202] In some embodiments, when the first device reads the information of the Ambient-IoT device, the identification of the Ambient-IoT device is already known. Optionally, when the Ambient-IoT device accesses the network, the Ambient-IoT device has informed the first device of the Ambient-IoT device identification information, or the Ambient-IoT device identification information is written, entered, or configured to the Ambient-IoT device by the first device.

[0203] In some embodiments, there are multiple situations for reading data information of Ambient-IoT: reading data information by access network equipment; reading data information by intermediate nodes; reading data information by auxiliary nodes; reading data information by terminals; reading data information by radio frequency readers.

[0204] In order to enable the first device to read the data information of the IoT device more reliably, the embodiments of the present disclosure provide the information processing method, first device, IoT device, communication system and storage medium involved in the following embodiments.

[0205] FIG2 is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in FIG2 , an embodiment of the present disclosure relates to an information processing method, which is applied to a communication system including a first device 101 and an IoT device 102. The method includes:

[0206] In step S2101 , the IoT device 102 sends fourth information (eg, capability information).

[0207] In some embodiments, the fourth information may be used to indicate the first data type. Optionally, the first data type is a data type supported by the IoT device 102. Optionally, the first data type is a data type that the IoT device 102 can read or obtain. Optionally, the first data type is a data type that the IoT device 102 can send.

[0208] It can be understood that the first data type may include multiple data types, and the embodiment of the present disclosure does not limit the number of data types included in the first data type.

[0209] In some embodiments, the fourth information is used to indicate the capability of the IoT device 102. For example, the fourth information may be used to indicate a field or code domain of data information stored by the IoT device 102.

[0210] Optionally, the fourth information may be used to indicate sensor data that can be detected by the sensor of the IoT device 102. For example, the fourth information may be used to indicate that the IoT device 102 can detect one or more of temperature data, humidity data, vibration intensity data, vibration duration data, light intensity data, pressure data, altitude data, speed data, angle data, etc. Accordingly, the data types supported by the IoT device 102 may include the data types corresponding to the above-mentioned sensor data.

[0211] Optionally, the fourth information may also be used to indicate a code field included in the encoding information of the IoT device 102. For example, the fourth information may be used to indicate that the encoding information of the IoT device 102 includes a code field. Optionally, the encoding information may include a code field corresponding to the ID information and / or a code field corresponding to the item information. Optionally, the encoding information of the IoT data may include one or more of the following code fields: codebook type; encoding version number; domain name administrator; country / region code; administrative region code within a country; item status type; item status indication field; item type; codebook application scenario; cell number; operator code; item serial number; and associated code.

[0212] In some embodiments, the fourth information may be "capability information", "capability reporting information", "field information", etc. The embodiment of the present disclosure does not limit the name of the fourth information.

[0213] In some embodiments, the first device 101 receives the fourth information. Optionally, the fourth information is sent by the IoT device 102.

[0214] Step S2102: The first device 101 sends fifth information (eg, data type configuration information).

[0215] In some embodiments, the fifth information is used to configure a data type of IoT device 102. Optionally, the fifth information is used to configure the data type of IoT device 102 to a second data type. Optionally, the second data type includes at least one data type included in the first data type. Optionally, the fifth information is used to configure the data type of IoT device 102 to a data type that IoT device 102 can support.

[0216] For example, if the first device 101 determines, based on the fourth information, that the first data type includes data types corresponding to temperature data, humidity data, vibration intensity data, and vibration duration data, the first device 101 can determine the second data type corresponding to the fifth information as including one or more of temperature data, humidity data, vibration intensity data, and vibration duration data.

[0217] In some embodiments, the IoT device 102 receives the fifth information. Optionally, the IoT device 102 configures a data type according to the fifth information. Optionally, the IoT device 102 obtains corresponding data according to its data type.

[0218] For example, after receiving the fifth information, IoT device 102 may configure its data type to the second data type corresponding to the fifth information based on the fifth information, and obtain corresponding data based on the second data type. For example, if the second data type includes data types corresponding to temperature data, humidity data, and vibration intensity data, IoT device 102 may obtain the corresponding temperature data, humidity data, and vibration intensity data.

[0219] In some embodiments, step S2102 is performed after the first device 101 receives the fourth information sent by the IoT device 102. Optionally, the first device 101 sends the fifth information in response to the fourth information. Optionally, the first device 101 sends the fifth information upon receiving the fourth information.

[0220] In some embodiments, the fifth information may be “configuration information”, “data type indication information”, “data configuration indication”, etc. The embodiment of the present disclosure does not limit the name of the fifth information.

[0221] Step S2103: The first device 101 sends sixth information (eg, data type configuration information).

[0222] In some embodiments, the sixth information is used to configure the data type of IoT device 102. Optionally, the sixth information is used to configure the data type of IoT device 102 to a third data type. Optionally, the third data type may be determined by first device 101. Optionally, the third data type may be indicated by a higher layer of first device 101. Optionally, the third data type may be determined by first device 101 based on its needs. Optionally, the third data type may be pre-agreed upon by a protocol.

[0223] For example, if the first device 101 determines that it may need the item type, code book application scenario and cell number of the Internet of Things device 102, the first device 101 can configure the data type of the Internet of Things device 102 to include the data type corresponding to the item type, code book application scenario and cell number through the sixth information, and the Internet of Things device 102 can obtain the corresponding data from the corresponding code field of the coding information based on the sixth information.

[0224] In a possible implementation scenario, if the IoT device 102 cannot obtain data corresponding to a certain data type based on the sixth information, or the third data type corresponding to the sixth information includes a data type not supported by the IoT device 102, the IoT device 102 can determine the data corresponding to the data type as preset data. For example, if the coding information of the IoT device 102 does not include a code field corresponding to the item type, the data corresponding to the item type can be determined as "0" or "none", etc.

[0225] In some embodiments, the sixth information may be “configuration information”, “data type indication information”, “data configuration indication”, etc. The embodiment of the present disclosure does not limit the name of the sixth information.

[0226] In some embodiments, the above-mentioned step S2102 and step S2103 may be performed alternatively.

[0227] Step S2104: The first device 101 determines scheduling indication information.

[0228] In some embodiments, the scheduling indication information is used to indicate the type of data included in the second information. Optionally, the scheduling indication information is used to indicate the type of data requested by the first device 101. Optionally, the scheduling indication information is used to instruct the IoT device 102 to determine the type of data included in the second information based on the scheduling indication information. Optionally, the scheduling indication information is used by the IoT device 102 to generate the second information. Optionally, the type of data included in the second information generated by the IoT device 102 includes the type of data indicated by the scheduling indication information. Optionally, the scheduling indication information is used to indicate the specific data information requested by the first device 101 from the IoT device 102.

[0229] In some embodiments, the first device 101 determines that the data type indicated by the scheduling indication information is at least one data type included in the first data type. Optionally, the data type indicated by the scheduling indication information is at least one data type supported by the IoT device 102.

[0230] For example, if the data types supported by IoT device 102 include data types corresponding to temperature data, humidity data, vibration intensity data, and vibration duration data, then the data type indicated by the scheduling indication information may include one or more of the data types corresponding to temperature data, humidity data, vibration intensity data, and vibration duration data. IoT device 102 may then generate second information based on the data type indicated by the scheduling indication information, and include data corresponding to all or part of the data type indicated by the scheduling indication information.

[0231] In some embodiments, the first device 101 determines that the data type indicated by the scheduling indication information is at least one data type included in the second data type.

[0232] In some embodiments, the first device 101 determines that the data type indicated by the scheduling indication information is at least one data type included in the third data type.

[0233] Optionally, the data type indicated by the scheduling indication information includes at least one of the data types configured by the first device 101 for the IoT device 102 .

[0234] For example, if the data type configured by the first device 101 for the IoT device 102 includes the item type, the code book application scenario, and the data type corresponding to the cell number, that is, the second data type or the third data type includes the item type, the code book application scenario, and the data type corresponding to the cell number, then the data type indicated by the scheduling indication information may include one or more of the above data types. For example, the data type indicated by the scheduling indication information may include the data type corresponding to the code book application scenario and the cell number.

[0235] In some embodiments, the scheduling indication information may be a "scheduling request indication", "scheduling indication", "type indication information", etc., and the embodiments of the present disclosure do not limit their names.

[0236] Step S2105: The first device 101 sends first information (eg, data request information).

[0237] In some embodiments, the first information is used to request the IoT device 102 to send the second information. Alternatively, the first information is used to instruct the IoT device 102 to send the second information. Alternatively, the first information is used to control the IoT device 102 to send the second information.

[0238] In some embodiments, the first information includes at least one of the following: an IoT device identifier; an IoT device group identifier. Optionally, the IoT device identifier is used to identify the IoT device 102. Optionally, the IoT device group identifier is used to identify the IoT device group to which the IoT device 102 belongs. Optionally, the IoT device identifier can be represented as "A-IOT device ID." Optionally, the IoT device group identifier can be represented as "A-IOT device group ID."

[0239] In some embodiments, IoT device 102 receives first information. Optionally, IoT device 102 receives the first information based on an IoT device identifier and / or an IoT device group identifier. Optionally, the first information is sent by first device 101. Optionally, IoT device 102 determines and sends second information based on the first information.

[0240] For example, the IoT device 102 determines whether the IoT device identifier and / or IoT device group identifier in the first information is the IoT device identifier and / or IoT device group identifier corresponding to the IoT device 102. If it is determined that the IoT device identifier and / or IoT device group identifier in the first information is the IoT device identifier and / or IoT device group identifier corresponding to the IoT device 102, the first information is received; otherwise, the first information can be discarded or no further operation is performed on the first information.

[0241] In some embodiments, the IoT device identifier and / or IoT device group identifier corresponding to the IoT device 102 may be pre-set at the factory.

[0242] In some embodiments, the IoT device identifier and / or IoT device group identifier corresponding to the IoT device 102 may be configured for it by the first device 101. For example, before sending the first information, the first device 101 may first send identifier configuration information to the IoT device 102. The identifier configuration information is used to configure the IoT device identifier and / or IoT device group identifier of the IoT device 102. After receiving the identifier configuration information, the IoT device 102 may set its IoT device identifier and / or IoT device group identifier to the identifier corresponding to the identifier configuration information.

[0243] In some embodiments, the first information may further include an identity verification code. This identity verification code may be used by IoT device 102 to verify the identity of first device 101. Alternatively, this identity verification code may be used by first device 101 to identify itself to IoT device 102 or to declare that first device 101 has the right to read the data corresponding to the second information.

[0244] Optionally, the identity verification code may be a symmetric key such as a random number or a pseudo-random number. Optionally, verification information for verifying the identity verification code may be stored in the IoT device 102. Optionally, the verification information may be pre-configured for the IoT device 102 by the first device 101. Optionally, the verification information may be, for example, information corresponding to the identity verification code. For example, the first device 101 may send the verification information to the IoT device 102 before sending the first information, so that the IoT device 102 configures the verification information and, after receiving the identity verification information corresponding to the first device 101, the IoT device 102 can verify the identity verification information based on the verification information.

[0245] Optionally, the IoT device 102 may determine whether to send the second information to the first device 101 based on whether the first information includes the identity verification code. For example, if the IoT device 102 receives the first information and determines that the first information does not include the identity verification code, the IoT device 102 may discard the first information or not send the second information to the first device 101. If the first information includes the identity verification code, the IoT device 102 may generate and send the second information based on the first information.

[0246] Optionally, the IoT device 102 may determine whether to send the second information to the first device 101 based on the identity verification code in the first information. For example, the IoT device 102 may compare its own stored verification information with the identity verification code in the first information to see if they match. If they do not match, the IoT device 102 may discard the first information or not send the second information to the first device 101. Optionally, the second information may be sent when the IoT device 102 determines that identity verification has passed based on the identity verification code.

[0247] In some embodiments, the first identity verification code sent by the first device 101 to the IoT device 102 is different from the second identity verification code sent by the second device to the IoT device 102; or the third identity verification code sent by the first device 102 to the first IoT device is different from the fourth identity verification code sent by the first device to the second IoT device. Optionally, the second device may be a device of the same type as the first device.

[0248] In some embodiments, the first identity verification code received by IoT device 102 from first device 101 is different from the second identity verification code received by IoT device 102 from the second device; or, if IoT device 102 is the first IoT device, the third identity verification code received by the first IoT device from first device 102 is different from the fourth identity verification code received by the second IoT device from the first device. In some embodiments, the identity verification codes correspond to both first device 101 and IoT device 102.

[0249] Optionally, the identity verification codes included in the first information are different for the same first device and different IoT devices, or for different first devices and the same IoT device. For example, if there is a first device that is communicatively connected to multiple IoT devices, the first device can configure different verification information for each IoT device, and the first device can send different identity verification codes to different IoT devices. In another example, if there are multiple first devices, and each first device is communicatively connected to one IoT device, each first device can configure different verification information for the IoT device and send a different identity verification code.

[0250] In some embodiments, the first information may also include scheduling request information. Optionally, the scheduling request information may be used to request IoT device 102 to transmit the second information. Optionally, IoT device 102 may transmit the second information in response to the scheduling request information. Optionally, the second information is transmitted by IoT device 102 in response to the scheduling request. Optionally, IoT device 102 may transmit the second information upon receiving the scheduling request information. Optionally, after receiving the scheduling request information, IoT device 102 may determine whether to allow first device 101 to obtain the second information.

[0251] For example, after receiving the scheduling request information, the IoT device 102 may determine whether to allow the first device 101 to obtain the second information based on the identity verification code in the first information. If it is determined that the first device 101 is not allowed to obtain the first information, the second information may not be sent to the first device 101.

[0252] Optionally, after receiving the scheduling request information, the IoT device 102 may independently determine whether to send the second information to the first device 101 or whether to allow the first device 101 to obtain the second information. For example, after receiving the scheduling request information, the IoT device 102 may determine whether to send the second information to the first device 101 based on its own load or power information. For example, if the power level is lower than a preset threshold, the IoT device 102 may not send the second information to the first device 101 or may not allow the first device 101 to obtain the second information.

[0253] In some embodiments, the first information may further include scheduling indication information. Optionally, the scheduling indication information is used to indicate the type of data included in the second information. Optionally, the second information is determined by IoT device 102 based on the scheduling indication information. Optionally, the scheduling indication information is used to indicate the type of data requested by first device 101. Optionally, the scheduling indication information may be determined based on step S2104 above. For specific implementations, please refer to the optional implementations of step S2104 and other related sections, and will not be repeated here.

[0254] In some embodiments, the data type requested by the first information is at least one of the data types of the IoT device 102. For example, the data type indicated by the scheduling indication information in the first information is at least one of the second data types.

[0255] In some embodiments, the first information includes at least one of the following: an IoT device identifier, used to identify the IoT device 102; an IoT device group identifier, used to identify the IoT device group in which the IoT device 102 is located; an identity verification code, used to perform identity verification on the IoT device 102; scheduling request information, the scheduling request information is used to request the IoT device 102 to send the second information; scheduling indication information is used to indicate the type of data included in the second information.

[0256] In some embodiments, the first information may be “data request information”, “data information acquisition instruction”, “IoT device data reading request”, etc., and the embodiments of the present disclosure do not limit their names.

[0257] In step S2106 , the IoT device 102 sends third information (eg, feedback information).

[0258] In some embodiments, the third information indicates feedback from IoT device 102 regarding the first information. Optionally, IoT device 102 sends the third information in response to the first information. Optionally, IoT device 102 sends the third information upon receiving the first information. Optionally, IoT device 102 sends the third information based on the first information.

[0259] In some embodiments, step S2106 may be performed when the IoT device 102 determines that the identity verification code in the first information is successful. Alternatively, step S2106 may be performed when the IoT device 102 determines that the IoT device identifier and / or IoT device group identifier in the first information corresponds to its own IoT device identifier and / or IoT device group identifier.

[0260] In some embodiments, the third information may be determined by the IoT device 102 based on at least one of the scheduling request information, the scheduling indication information, and the identity authentication information in the first information.

[0261] For example, after receiving the first information, if the IoT device 102 determines that the IoT device identifier and / or IoT device group identifier stored in itself matches the IoT device identifier and / or IoT device group identifier in the first information, it can authenticate the first device 101 based on the identity verification code, and if the verification is successful, determine whether the first device 101 is allowed to obtain the data type indicated in the scheduling indication information, or determine whether the first device 101 is allowed to obtain the second information requested by the scheduling request information, and then obtain the third information.

[0262] In some embodiments, the third information includes at least one of the following: first feedback information; second feedback information; and third feedback information. Optionally, the first feedback information indicates whether the IoT device allows first device 101 to obtain the second information. Optionally, the second feedback information requests power from first device 101. Optionally, the second feedback information instructs first device 101 to send a charging signal to IoT device 102. Optionally, the third feedback information indicates a time offset for first device 101 to send the second information.

[0263] Alternatively, whether to send the second feedback information may be determined by the IoT device 102 based on its own power level. For example, if the power level of the IoT device 102 is lower than a preset threshold, the IoT device 102 may send the second feedback information to the first device 101 via the third information to request power supply.

[0264] In some embodiments, the first device 101 receives the third message. Alternatively, the first device 101 may receive the second information based on the third information, or determine whether to receive the second information, or whether to expect to receive the second information.

[0265] For example, if the first feedback information indicates that IoT device 102 does not allow first device 101 to obtain the second information, first device 101 may not receive the second information, or may not expect to receive the second information. For another example, first device 101 may determine when to receive the second information based on the second feedback information and / or the third feedback information. This will be described in detail in the optional implementation of step S2107 in the present embodiment and will not be further described here.

[0266] In step S2107 , the IoT device 102 sends second information (eg, data information).

[0267] In some embodiments, the second information is used to indicate information of the IoT device 102. Alternatively, the second information may be used to indicate any information of the IoT device 102. For example, the second information may be used to indicate some or all of the information such as status information, device information, control information, configuration information, item information, and sensor data information of the IoT device 102.

[0268] In some embodiments, the second information includes at least one of the following: sensor data detected by the IoT device 102; or encoded information of the IoT device 102. Alternatively, the encoded information of the IoT device 102 may include at least one code field within the encoded information. Alternatively, the sensor data may include data detected by some or all sensors of the IoT device 102.

[0269] In some embodiments, the content included in the second information may be determined by IoT device 102 based on the scheduling instruction information in the first information. For example, if the data type indicated by the scheduling instruction information includes the data type corresponding to the temperature sensor and the humidity sensor, as well as the data type of the code field corresponding to the item type, cell number, and item serial number, then after receiving the first information, IoT device 102 may generate second information based on the scheduling instruction information, and the second information may include the data collected by the temperature sensor and the humidity sensor, as well as the data in the code field corresponding to the item type, cell number, and item serial number.

[0270] In some embodiments, step S2107 may be executed after step S2106 is completed.

[0271] In some embodiments, the IoT device 102 may send the second information after determining that the identity verification has passed. Alternatively, the second information is sent when the IoT device 102 determines that the identity verification has passed.

[0272] In some embodiments, the IoT device 102 determines that the second condition is satisfied and sends the second information. Optionally, the second condition includes at least one of the following: the IoT device 102 has sent the first feedback information, and the first feedback information is used by the IoT device 102 to allow the first device 101 to read the data information; the IoT device 102 has sent the second feedback information and received a charging signal or charging is complete; the IoT device 102 has sent the third feedback information.

[0273] In some embodiments, the first device 101 receives the second information. Optionally, the first device 101 determines that a first condition is satisfied and receives the second information. Optionally, the first condition includes at least one of the following: the first device 101 receives first feedback information, and the first feedback information is used to indicate that the IoT device 102 allows the first device 101 to read the data information; the first device 101 receives second feedback information and sends a charging signal for a first duration; the first device 101 receives third feedback information and the waiting duration reaches a time offset.

[0274] Optionally, the time offset may be determined by the first device 101 based on the third feedback information. Optionally, the first duration may be determined based on the time offset. For example, the first duration may be equal to the time offset plus a preset duration. Optionally, the first duration may be indicated by upper layer signaling. Optionally, the first duration may be predefined by a protocol. Optionally, the first duration may be equal to, greater than, or less than the time offset. This disclosure is not limited in this regard.

[0275] In some embodiments, the second information is sent when a third condition is met, and the third condition includes at least one of the following: the IoT device 102 determines that the identity verification is passed based on the identity verification code; the IoT device 102 receives the scheduling request information; the IoT device 102 receives the scheduling indication information, and determines to obtain the second information based on the scheduling indication information.

[0276] In some embodiments, the second information may be, for example, "data information", "IoT device information", "coding information", "sensor information", etc. The embodiment of the present disclosure does not limit the name of the second information.

[0277] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "data type", "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "code element", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0278] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" may be used interchangeably. For example, a codebook may be a collection of one or more codewords / precoding matrices.

[0279] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0280] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0281] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0282] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0283] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0284] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0285] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0286] The information processing method according to the embodiments of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2015 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2106 may be implemented as an independent embodiment, steps S2101 and S2102 may be implemented as independent embodiments, and steps S2105 to S2107 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0287] In some embodiments, step S2106 and step S2107 may be executed in an interchangeable order or simultaneously.

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

[0289] In some embodiments, steps S2102 to S2107 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0291] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0292] FIG3A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3A , the embodiment of the present disclosure relates to an information processing method, which includes:

[0293] Step S3101, obtain the fourth information.

[0294] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0295] In some embodiments, the first device 101 receives the fourth information sent by the IoT device 102, but is not limited thereto and may also receive the fourth information sent by other entities.

[0296] In some embodiments, the first device 101 obtains fourth information specified by the protocol.

[0297] In some embodiments, the first device 101 obtains the fourth information from an upper layer(s).

[0298] In some embodiments, the first device 101 performs processing to obtain the fourth information.

[0299] In some embodiments, step S3101 is omitted, and the first device 101 autonomously implements the function indicated by the fourth information, or the above function is default or by default.

[0300] Step S3102, sending the fifth information.

[0301] The optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0302] In some embodiments, the first device 101 sends the fifth information to the IoT device 102 , but is not limited thereto and the fifth information may also be sent to other entities.

[0303] Step S3103: determine the scheduling instruction information.

[0304] The optional implementation of step S3103 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0305] In some embodiments, the data type indicated by the scheduling indication information may be determined according to the second data type configured by the fifth information.

[0306] In some other embodiments, the data type indicated by the scheduling indication information may be determined according to the first data type indicated by the fourth information.

[0307] In some embodiments, the data type indicated by the scheduling indication information may be specified by a protocol, or indicated by an upper layer(s), or determined by the first device 101 itself.

[0308] Step S3104, sending the first information.

[0309] The optional implementation of step S3104 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0310] In some embodiments, the first device 101 sends the first information to the IoT device 102 , but is not limited thereto and the first information may also be sent to other entities.

[0311] Step S3105, obtain third information.

[0312] The optional implementation of step S3105 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0313] In some embodiments, the first device 101 receives the third information sent by the IoT device 102, but is not limited thereto and may also receive the third information sent by other entities.

[0314] In some embodiments, step S3101 is omitted, and the first device 101 autonomously implements the function indicated by the third information, or the above function is default or by default.

[0315] Step S3106, obtaining the second information.

[0316] The optional implementation of step S3106 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0317] In some embodiments, the first device 101 receives the third information sent by the IoT device 102, but is not limited thereto and may also receive the second information sent by other entities.

[0318] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3106. For example, step S3104 can be implemented as an independent embodiment, step S3105 can be implemented as an independent embodiment, step S3101 can be implemented as an independent embodiment, steps S3104 to S3106 can be implemented as independent embodiments, steps S3101 to S3103 can be implemented as an independent embodiment, and step S3101 and steps S3103 to S3106 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0319] In some embodiments, steps S3101 to S3103 and steps S3105 to S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0320] In some embodiments, steps S3102 to S3106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0321] FIG3B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3B , the embodiment of the present disclosure relates to an information processing method, which includes:

[0322] Step S3201, sending the sixth information.

[0323] The optional implementation of step S3201 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0324] In some embodiments, the first device 101 sends the sixth information to the IoT device 102 , but is not limited thereto and the sixth information may also be sent to other entities.

[0325] Step S3202: Determine scheduling instruction information.

[0326] The optional implementation of step S3202 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0327] In some embodiments, the data type indicated by the scheduling indication information may be determined according to the third data type configured by the sixth information.

[0328] In some embodiments, the data type indicated by the scheduling indication information may be specified by a protocol, or indicated by an upper layer(s), or determined by the first device 101 itself.

[0329] Step S3203, sending the first information.

[0330] The optional implementation of step S3203 can refer to step S2105 in Figure 2, the optional implementation of step S3104 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0331] Step S3204, obtain third information.

[0332] The optional implementation of step S3204 can refer to step S2106 in Figure 2, the optional implementation of step S3105 in Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0333] Step S3205, obtain the second information.

[0334] The optional implementation of step S3205 can refer to step S2107 of Figure 2, the optional implementation of step S3106 of Figure 3A, and other related parts in the embodiments involved in Figures 2 and 3A, which will not be repeated here.

[0335] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3205. For example, step S3203 can be implemented as an independent embodiment, step S3205 can be implemented as an independent embodiment, step S3201 can be implemented as an independent embodiment, steps S3201 to S3203 can be implemented as an independent embodiment, steps S3203 to S3205 can be implemented as an independent embodiment, and step S3101 and steps S3103 to S3106 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0336] In some embodiments, steps S3201 to S3202 and steps S3203 to S3205 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0337] In some embodiments, steps S3201 to S3204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0338] FIG3C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3C , the embodiment of the present disclosure relates to an information processing method, which includes:

[0339] Step S3301, sending the first information.

[0340] The optional implementation of step S3301 can be found in step S2105 of Figure 2, step S3104 of Figure 3A, the optional implementation of step S3203 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0341] Step S3302, obtain third information.

[0342] The optional implementation of step S3302 can be found in step S2106 of Figure 2, step S3105 of Figure 3A, the optional implementation of step S3204 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0343] Step S3303, obtain the second information.

[0344] The optional implementation of step S3303 can be found in step S2107 of Figure 2, step S3106 of Figure 3A, the optional implementation of step S3205 of Figure 3B, and other related parts in the embodiments involved in Figures 2, 3A, and 3B, which will not be repeated here.

[0345] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3301 can be implemented as an independent embodiment, step S3302 can be implemented as an independent embodiment, and step S3303 can be implemented as an independent embodiment. Steps S3301 to S3302 can be implemented as an independent embodiment, and steps S3302 to S3303 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0346] In some embodiments, steps S3301 to S3302 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0347] In some embodiments, steps S3302 to S3303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0348] In some embodiments, step S3301 and step S3303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0349] In some embodiments, steps S3301 to S3303 may be combined with steps S3101 to S3103 in Figure 3A or steps S3101 and S3103 in Figure 3A. Steps S3301 to S3303 may also be combined with steps S3201 to S3202 in Figure 3B.

[0350] FIG3D is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG3D , the embodiment of the present disclosure relates to an information processing method, which includes:

[0351] Step S3401, sending the first information.

[0352] The optional implementation of step S3401 can be found in step S2105 of Figure 2, step S3104 of Figure 3A, step S3203 of Figure 3B, the optional implementation of step S3301 of Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0353] Step S3402, obtaining second information.

[0354] The optional implementation of step S3402 can be found in step S2107 of Figure 2, step S3106 of Figure 3A, step S3205 of Figure 3B, the optional implementation of step S3303 of Figure 3C, and other related parts in the embodiments involved in Figures 2, 3A, 3B, and 3C, which will not be repeated here.

[0355] The information processing method involved in the embodiment of the present disclosure may include at least one of steps S3401 and S3402. For example, step S3401 may be implemented as an independent embodiment, and step S3402 may be implemented as an independent embodiment.

[0356] In some embodiments, step S3401 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0357] In some embodiments, step S3402 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0358] In some embodiments, steps S3401 to S3402 can be combined with steps S3101 to S3103 in Figure 3A or steps S3101 and S3103 in Figure 3A. Steps S3401 to S3402 can also be combined with steps S3201 to S3202 in Figure 3B.

[0359] In some embodiments, the first information includes at least one of the following:

[0360] An IoT device identifier, used to identify the IoT device 102;

[0361] The IoT device group identifier is used to identify the IoT device group to which the IoT device 102 belongs.

[0362] In some embodiments, the IoT device identifier and / or the IoT device group identifier is configured by the first device 101 for the IoT device 102 .

[0363] In some embodiments, the first information includes an identity verification code, and the identity verification code is used by the IoT device 102 to verify the identity of the first device 101;

[0364] The second information is sent when the IoT device 102 determines that the identity verification has passed based on the identity verification code.

[0365] In some embodiments, the identity verification code corresponds to the first device and the IoT device.

[0366] In some embodiments, the first information includes scheduling request information, and the scheduling request information is used to request the IoT device 102 to send the second information;

[0367] The second message is sent by the IoT device 102 in response to the scheduling request message.

[0368] In some embodiments, the first information includes scheduling indication information, and the scheduling indication information is used to indicate the type of data included in the second information;

[0369] The second information is determined by the IoT device 102 according to the scheduling instruction information.

[0370] In some embodiments, the second information includes at least one of the following:

[0371] sensor data detected by the IoT device 102;

[0372] The encoding information of the IoT device 102 includes at least one code field.

[0373] In some embodiments, before receiving the second information, the method includes:

[0374] Receive third information, where the third information includes at least one of the following:

[0375] First feedback information, the first feedback information is used to indicate whether the Internet of Things device 102 allows the first device 101 to read the data information;

[0376] Second feedback information, where the second feedback information is used to request energy supply from the first device 101;

[0377] The third feedback information is used to indicate a time offset when the first device 101 sends the second information.

[0378] In some embodiments, receiving the second information includes:

[0379] Determine that a first condition is met, and receive second information, where the first condition includes at least one of the following:

[0380] The first feedback information is received, and the first feedback information is used to instruct the Internet of Things device 102 to allow the first device 101 to read the data information;

[0381] The second feedback information is received, and the first duration has elapsed since the charging signal was sent;

[0382] The third feedback information is received, and the waiting time reaches the time offset.

[0383] In some embodiments, the first duration is determined according to a time offset; or, the first duration is predefined by a protocol.

[0384] In some embodiments, the method comprises:

[0385] Receive fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device 102;

[0386] Scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the first data type.

[0387] In some embodiments, the method further comprises:

[0388] Receive fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device 102;

[0389] Sending fifth information, where the fifth information is used to configure the data type of the IoT device 102 to be a second data type, where the second data type includes at least one data type included in the first data type;

[0390] Scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the second data type.

[0391] In some embodiments, the method comprises:

[0392] Sending sixth information, where the sixth information is used to configure the data type of the IoT device 102 to be the third data type;

[0393] Scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the third data type.

[0394] In some embodiments, the first device 101 is any one of the following:

[0395] Access network equipment, core network equipment, terminals, radio frequency readers, intermediate node equipment, and auxiliary node equipment.

[0396] FIG4A is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4A , the embodiment of the present disclosure relates to an information processing method, which includes:

[0397] Step S4101, sending the fourth information.

[0398] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0399] In some embodiments, the IoT device 102 sends the fourth information to the first device 101 , but is not limited thereto and may also send the fourth information to other entities.

[0400] Step S4102, obtain the fifth information.

[0401] The optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0402] In some embodiments, the IoT device 102 receives the fifth information sent by the first device 101, but is not limited thereto and may also receive the fifth information sent by other entities.

[0403] In some embodiments, the IoT device 102 obtains fifth information specified by the protocol.

[0404] In some embodiments, the IoT device 102 obtains the fifth information from an upper layer(s).

[0405] In some embodiments, the IoT device 102 performs processing to obtain the fifth information.

[0406] In some embodiments, step S4102 is omitted, and the IoT device 102 autonomously implements the function indicated by the fifth information, or the above function is default or by default.

[0407] Step S4103, obtaining first information.

[0408] The optional implementation of step S4103 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0409] In some embodiments, the IoT device 102 receives the first information sent by the first device 101, but is not limited thereto and may also receive the first information sent by other entities.

[0410] In some embodiments, the IoT device 102 obtains first information specified by a protocol.

[0411] In some embodiments, the IoT device 102 obtains the first information from an upper layer(s).

[0412] In some embodiments, the IoT device 102 performs processing to obtain the first information.

[0413] In some embodiments, step S4103 is omitted, and the IoT device 102 autonomously implements the function indicated by the first information, or the above function is default or by default.

[0414] Step S4104, sending the third information.

[0415] The optional implementation of step S4104 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0416] In some embodiments, the IoT device 102 sends the third information to the first device 101 , but is not limited thereto and may also send the third information to other entities.

[0417] Step S4105, sending the second information.

[0418] The optional implementation of step S4105 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0419] In some embodiments, the IoT device 102 sends the second information to the first device 101 , but is not limited thereto and may also send the second information to other entities.

[0420] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4105. For example, step S4104 can be implemented as an independent embodiment, step S4105 can be implemented as an independent embodiment, step S4106 can be implemented as an independent embodiment, steps S4103 to S4105 can be implemented as an independent embodiment, and steps S4101 to S4102 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0421] In some embodiments, steps S4101 to S4102 and steps S4104 to S4105 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0422] In some embodiments, steps S4101 to S4104 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0423] FIG4B is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4B , the embodiment of the present disclosure relates to an information processing method, which includes:

[0424] Step S4201, obtain sixth information.

[0425] The optional implementation of step S4201 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0426] In some embodiments, the IoT device 102 receives the sixth information sent by the first device 101, but is not limited thereto and may also receive the sixth information sent by other entities.

[0427] In some embodiments, the IoT device 102 obtains sixth information specified by the protocol.

[0428] In some embodiments, the IoT device 102 obtains the sixth information from an upper layer(s).

[0429] In some embodiments, the IoT device 102 performs processing to obtain the sixth information.

[0430] In some embodiments, step S4102 is omitted, and the IoT device 102 autonomously implements the function indicated by the sixth information, or the above function is default or by default.

[0431] Step S4202, obtain first information.

[0432] The optional implementation of step S4202 can refer to step S2105 of Figure 2, the optional implementation of step S4103 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0433] Step S4203, sending the third information.

[0434] The optional implementation of step S4203 can refer to step S2106 of Figure 2, the optional implementation of step S4104 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0435] Step S4204, sending the second information.

[0436] The optional implementation of step S4204 can refer to step S2107 of Figure 2, the optional implementation of step S4105 of Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0437] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S4201 to S4204. For example, step S4204 may be implemented as an independent embodiment, step S4203 may be implemented as an independent embodiment, step S4201 may be implemented as an independent embodiment, steps S4203 to S4204 may be implemented as an independent embodiment, and steps S4201 to S4202 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0438] In some embodiments, step S4201 and steps S4203 to S4204 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0439] In some embodiments, steps S4201 to S4203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0440] FIG4C is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4C , the embodiment of the present disclosure relates to an information processing method, which includes:

[0441] Step S4301, obtain first information.

[0442] The optional implementation of step S4301 can be found in step S2105 of Figure 2, step S4103 of Figure 4A, the optional implementation of step S4202 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0443] Step S4302, sending the third information.

[0444] The optional implementation of step S4302 can be found in step S2106 of Figure 2, step S4104 of Figure 4A, the optional implementation of step S4203 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0445] Step S4303, sending the second information.

[0446] The optional implementation of step S4303 can be found in step S2107 of Figure 2, step S4105 of Figure 4A, the optional implementation of step S4204 of Figure 4B, and other related parts in the embodiments involved in Figures 2, 4A, and 4B, which will not be repeated here.

[0447] The information processing method involved in the embodiments of the present disclosure may include at least one of steps S4301 to S4303. For example, step S4301 can be implemented as an independent embodiment, step S4302 can be implemented as an independent embodiment, and step S4303 can be implemented as an independent embodiment. Steps S4301 to S4302 can be implemented as an independent embodiment, and steps S4302 to S4303 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0448] In some embodiments, steps S4301 to S4302 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0449] In some embodiments, steps S4302 to S4303 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0450] In some embodiments, steps S4301 to S4103 may be combined with steps S4101 to S4102 in FIG. 4A , steps S4301 to S4303 may be combined with step S4101 in FIG. 4A , and steps S4301 to S4303 may be combined with step S4201 in FIG. 4B .

[0451] FIG4D is a flow chart of an information processing method according to an embodiment of the present disclosure. As shown in FIG4D , the embodiment of the present disclosure relates to an information processing method, which includes:

[0452] Step S4401, obtain first information.

[0453] The optional implementation of step S4401 can be found in step S2105 of Figure 2, step S4103 of Figure 4A, step S4202 of Figure 4B, the optional implementation of step S4301 of Figure 4C, and other related parts in the embodiments involved in Figures 2, 4A, 4B, and 4C, which will not be repeated here.

[0454] Step S4402, sending the second information.

[0455] The optional implementation of step S4402 can be found in step S2107 of Figure 2, step S4105 of Figure 4A, step S4204 of Figure 4B, the optional implementation of step S4303 of Figure 4C, and other related parts in the embodiments involved in Figures 2, 4A, 4B, and 4C, which will not be repeated here.

[0456] The information processing method involved in the embodiment of the present disclosure may include at least one of steps S4401 and S4402. For example, step S4401 may be implemented as an independent embodiment, and step S4402 may be implemented as an independent embodiment.

[0457] In some embodiments, step S4401 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0458] In some embodiments, step S4402 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0459] In some embodiments, steps S4401 to S4402 may be combined with steps S4101 to S4102 in FIG. 4A , steps S4401 to S4402 may be combined with step S4101 in FIG. 4A , and steps S4401 to S4402 may be combined with step S4201 in FIG. 4B .

[0460] In some embodiments, the first information includes at least one of the following:

[0461] An IoT device identifier, used to identify the IoT device 102;

[0462] The IoT device group identifier is used to identify the IoT device group to which the IoT device 102 belongs.

[0463] In some embodiments, the IoT device identifier and / or the IoT device group identifier is configured by the first device 101 for the IoT device 102 .

[0464] In some embodiments, the first information includes an identity verification code, which is used by the IoT device 102 to verify the identity of the first device 101;

[0465] The second information is sent when the IoT device 102 determines that the identity verification has passed based on the identity verification code.

[0466] In some embodiments, the identity verification code corresponds to the first device and the IoT device.

[0467] In some embodiments, the first information includes scheduling request information, and the scheduling request information is used to request the IoT device 102 to send the second information;

[0468] The second message is sent by the IoT device 102 in response to the scheduling request message.

[0469] In some embodiments, the first information includes scheduling indication information, and the scheduling indication information is used to indicate the type of data included in the second information;

[0470] The second information is determined by the IoT device 102 according to the scheduling instruction information.

[0471] In some embodiments, the second information includes at least one of the following:

[0472] sensor data detected by the IoT device 102;

[0473] The encoding information of the IoT device 102 includes at least one code field.

[0474] In some embodiments, before sending the second information, the method includes:

[0475] Sending third information, where the third information includes at least one of the following:

[0476] First feedback information, the first feedback information is used to indicate whether the Internet of Things device 102 allows the first device 101 to read the data information;

[0477] Second feedback information, where the second feedback information is used to request energy supply from the first device 101;

[0478] The third feedback information is used to indicate a time offset when the first device 101 sends the second information.

[0479] In some embodiments, sending the second information includes:

[0480] Determining that a second condition is met, sending a second message, where the second condition includes at least one of the following:

[0481] The IoT device 102 has sent first feedback information, and the first feedback information is used to indicate that the IoT device 102 allows the first device 101 to read the data information;

[0482] The IoT device 102 has sent the second feedback information;

[0483] The IoT device 102 has sent the third feedback information.

[0484] In some embodiments, the method comprises:

[0485] Sending fourth information, where the fourth information is used to indicate the first data type, where the first data type is a data type that can be supported by the IoT device 102;

[0486] The data type indicated by the scheduling indication information is at least one data type included in the first data type.

[0487] In some embodiments, the method further comprises:

[0488] Sending fourth information, where the fourth information is used to indicate the first data type, where the first data type is a data type that can be supported by the IoT device 102;

[0489] Receive fifth information, where the fifth information is used to configure a data type of the IoT device 102 to be a second data type, where the second data type includes at least one data type included in the first data type;

[0490] The data type indicated by the scheduling indication information is at least one data type included in the second data type.

[0491] In some embodiments, the method comprises:

[0492] receiving sixth information, where the sixth information is used to configure the data type of the IoT device 102 to be the third data type;

[0493] The data type indicated by the scheduling indication information is at least one data type included in the third data type.

[0494] In some embodiments, the first device 101 is any one of the following:

[0495] Access network equipment, core network equipment, terminals, radio frequency readers, intermediate node equipment, and auxiliary node equipment.

[0496] Figure 5 is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in Figure 5, the embodiment of the present disclosure relates to an information processing method, which includes:

[0497] Step S5101: The first device 101 sends first information.

[0498] For the optional implementation of step S5101, please refer to step S2105 of Figure 2, step S3104 of Figure 3A, step S3203 of Figure 3B, step S3301 of Figure 3C, step S3401 of Figure 3D, step S4103 of Figure 4A, step S4202 of Figure 4B, step S4301 of Figure 4C, optional implementation of step S4401 of Figure 4D, and other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C, 3D, 4A, 4B, 4C, and 4D, which will not be repeated here.

[0499] Step S5202: The IoT device 102 sends second information.

[0500] For the optional implementation of step S5101, please refer to step S2107 of Figure 2, step S3106 of Figure 3A, step S3205 of Figure 3B, step S3303 of Figure 3C, step S3402 of Figure 3D, step S4105 of Figure 4A, step S4204 of Figure 4B, step S4303 of Figure 4C, and the optional implementation of step S4402 of Figure 4D, as well as other related parts in the embodiments involved in Figures 2, 3A, 3B, 3C, 3D, 4A, 4B, 4C, and 4D, which will not be repeated here.

[0501] In some embodiments, the above method may include the method described in the above embodiments of the communication system side, the first device side, the Internet of Things device side, etc., which will not be repeated here.

[0502] Figure 6 is an interactive diagram of an information processing method according to an embodiment of the present disclosure. As shown in Figure 6, the embodiment of the present disclosure relates to an information processing method, which includes:

[0503] Step S6101: The first device determines to read data information from the A-IOT device.

[0504] In some embodiments, the first device includes at least one of the following: a radio frequency reader, a network device (eg, a base station), an intermediate node, an auxiliary node, a network terminal device, and a core device.

[0505] In some embodiments, the first device sends at least one of first information and second information to the A-IOT device. The first information includes at least one of the following information:

[0506] A-IOT device ID information, which is used to identify the A-IOT device;

[0507] A-IOT device group ID information, which indicates the ID of the group to which the A-IOT device belongs;

[0508] From the perspective of the first device, the identity verification code is used by the first device to identify itself to the A-IOT device or to assert read permission. From the perspective of the A-IOT device, the A-IOT device verifies the identity of the first device. Specifically, this code includes, but is not limited to, symmetric keys such as random numbers and pseudo-random numbers.

[0509] The second information includes at least one of the following information:

[0510] A scheduling request, used to determine that the first device initiates a scheduling request to the A-IOT device;

[0511] The scheduling request indication is used to determine specific data information requested by the first device to the A-IOT device, for example, indicating different information fields and indicating different sensor data types.

[0512] In some embodiments, after the A-IOT device receives the first information and passes the identity verification, it further determines to send third information to the first device based on the scheduling request indication and / or the scheduling request. The first device determines to receive the third information from the A-IOT device, and the third information includes at least one of the following:

[0513] Sensor data, including but not limited to temperature, humidity, vibration intensity, vibration duration, light intensity, pressure, altitude, speed, angle, etc.;

[0514] The coding information corresponding to the A-IOT device, including but not limited to ID information, item information, etc.;

[0515] The first feedback information is used by the A-IOT device to provide feedback to the first device on whether the A-IOT device allows the first device to read data information;

[0516] The second feedback information is used by the A-IOT device to request energy supply from the first device;

[0517] The third feedback information is used for the time offset of the A-IOT device reporting feedback data information to the first device;

[0518] Ambient-IoT coded information, where the Ambient-IoT code includes at least one code field, and one code field is used to indicate a specific type of information.

[0519] In some embodiments, the first information is written / entered / configured to the A-IOT device by the first device.

[0520] In some embodiments, the first device can write / enter / configure different identity verification codes for different A-IOT devices.

[0521] In some embodiments, the data types supported by the A-IOT device are reported by the A-IOT device to the first device through the first capability, or configured by the first device to the A-IOT device, or configured by the first device to the A-IOT device within the capability range of the A-IOT device.

[0522] In some embodiments, the first device sends a charging signal to the A-IOT device and / or the first device waits for a first time period before receiving third information from the A-IOT device, where the first time period is predefined by the protocol or determined based on a time offset, and the triggering condition for the above behavior is at least one of the following:

[0523] The first device receives the first feedback information sent by the A-IOT device and allows the first device to read the data information;

[0524] The first device receives the second feedback information sent by the A-IOT device and requests energy supply;

[0525] The first device receives third feedback information sent by the A-IOT device.

[0526] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0527] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0528] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0529] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution 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 relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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 implementing the hardware circuit configuration 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. In addition, 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), a deep learning processing unit (DPU), etc.

[0530] Figure 7A is a schematic diagram of the structure of the first device proposed in an embodiment of the present disclosure. As shown in Figure 7A, the first device 7100 may include: at least one of a transceiver module 7101 and a processing module 7102. In some embodiments, the transceiver module 7101 is used to send first information, where the first information is used to request the IoT device to send second information. The transceiver module 7101 is also used to receive the second information, where the second information is used to indicate information about the IoT device. Optionally, the transceiver module 7101 is used to execute at least one of the communication steps such as sending and / or receiving performed by the first device 101 in any of the above methods (for example, step S2101, step S2102, step S2103, step S2105, step S2106, and step S2107, but not limited thereto), which are not further described here. Optionally, the processing module 7102 is used to execute at least one of the other steps (for example, step S2104, but not limited thereto) performed by the first device 101 in any of the above methods, which are not further described here.

[0531] Figure 7B is a schematic diagram of the structure of the Internet of Things device proposed in an embodiment of the present disclosure. As shown in Figure 7B, the Internet of Things device 7200 may include: at least one of a transceiver module 7201, a processing module 7202, etc. In some embodiments, the transceiver module 7201 is used to receive a first message sent by a first device, the first message being used to request the Internet of Things device to send a second message; and to send the second message, the second message being used to indicate information of the Internet of Things device. Optionally, the transceiver module 7201 is used to execute at least one of the communication steps such as sending and / or receiving performed by the Internet of Things device 102 in any of the above methods (for example, step S2101, step S2102, step S2103, step S2105, step S2106, step S2107, but not limited thereto), which are not described in detail here. Optionally, the processing module 7202 is used to execute at least one of the other steps performed by the Internet of Things device 102 in any of the above methods (for example, generating the second message), which are not described in detail here.

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

[0533] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0534] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. The communication device 8100 can be a first device or an Internet of Things device. The first device can be, for example, a network device (such as an access network device, a core network device, etc.), or a terminal (such as a user device, etc.), or a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. The communication device 8100 can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.

[0535] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0536] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0537] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2102, step S2103, step S2105, step S2106, and step S2107, but not limited thereto), and the processor 8101 performs at least one of the other steps (for example, step S2104, but not limited thereto).

[0538] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0539] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

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

[0541] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0542] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0543] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.

[0544] In some embodiments, the interface circuit 8202 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step S2101, step S2102, step S2103, step S2105, step S2106, step S2107, but not limited to these), and the processor 8201 executes at least one of the other steps (for example, step S2104, but not limited to this).

[0545] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0546] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0547] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute 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 is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0548] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0549] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. An information processing method, characterized in that: Executed by a first device, the method includes: Sending first information, where the first information is used to request the Internet of Things device to send second information; The second information is received, where the second information is used to indicate information of the Internet of Things device.

2. The method according to claim 1, characterized in that The first information includes at least one of the following: An IoT device identifier, used to identify the IoT device; The IoT device group identifier is used to identify the IoT device group to which the IoT device belongs.

3. The method according to claim 2, characterized in that The IoT device identifier and / or the IoT device group identifier are configured by the first device for the IoT device.

4. The method according to any one of claims 1 to 3, characterized in that: The first information includes an identity verification code, and the identity verification code is used by the Internet of Things device to perform identity verification on the first device; The second information is sent by the IoT device when it is determined that the identity verification has passed according to the identity verification code.

5. The method according to claim 4, characterized in that The first identity verification code sent by the first device to the Internet of Things device is different from the second identity verification code sent by the second device to the Internet of Things device; or The third identity verification code sent by the first device to the first Internet of Things device is different from the fourth identity verification code sent by the first device to the second Internet of Things device.

6. The method according to any one of claims 1 to 5, characterized in that: The first information includes scheduling request information, and the scheduling request information is used to request the Internet of Things device to send the second information; The second information is sent by the IoT device in response to the scheduling request information.

7. The method according to any one of claims 1 to 6, characterized in that: The first information includes scheduling indication information, where the scheduling indication information is used to indicate the type of data included in the second information; The second information is determined by the Internet of Things device according to the scheduling indication information.

8. The method according to any one of claims 1 to 7, characterized in that: The second information includes at least one of the following: Sensor data detected by the IoT device; The coding information of the Internet of Things device includes at least one code field.

9. The method according to any one of claims 1 to 8, characterized in that: Before receiving the second information, the method includes: Receive third information, wherein the third information includes at least one of the following: first feedback information, where the first feedback information is used to indicate whether the IoT device allows the first device to read data information; second feedback information, where the second feedback information is used to request energy supply from the first device; The third feedback information is used to indicate a time offset when the first device sends the second information.

10. The method according to claim 9, characterized in that The receiving the second information comprises: Determine that the first condition is met; The second information is received, wherein the first condition includes at least one of the following: The first device receives the first feedback information, and the first feedback information is used to instruct the Internet of Things device to allow the first device to read data information; The first device receives the second feedback information and sends a charging signal for a first duration; The first device receives the third feedback information and waits for a period of time reaching the time offset.

11. The method according to claim 10, characterized in that The first duration is determined according to the time offset; or, the first duration is predefined by a protocol.

12. The method according to claim 6, characterized in that The method comprises: receiving fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device; The scheduling indication information is determined, where a data type indicated by the scheduling indication information is at least one data type included in the first data type.

13. The method according to claim 6, characterized in that The method further comprises: receiving fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device; Sending fifth information, where the fifth information is used to configure the data type of the Internet of Things device to be a second data type, where the second data type includes at least one data type included in the first data type; The scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the second data type.

14. The method according to claim 6, characterized in that The method comprises: Sending sixth information, where the sixth information is used to configure the data type of the IoT device to be a third data type; The scheduling indication information is determined, where the data type indicated by the scheduling indication information is at least one data type included in the third data type.

15. The method according to any one of claims 1 to 13, characterized in that: The first device includes at least one of the following: Access network equipment, core network equipment, terminals, radio frequency readers, intermediate node equipment, and auxiliary node equipment.

16. An information processing method, characterized in that: The method is performed by an IoT device and includes: Receiving first information sent by a first device, where the first information is used to request the IoT device to send second information; The second information is sent, where the second information is used to indicate information of the Internet of Things device.

17. The method according to claim 15, characterized in that The first information includes at least one of the following: An IoT device identifier, used to identify the IoT device; The IoT device group identifier is used to identify the IoT device group to which the IoT device belongs.

18. The method according to claim 17, characterized in that The IoT device identifier and / or the IoT device group identifier are configured by the first device for the IoT device.

19. The method according to any one of claims 16 to 18, characterized in that: The first information includes an identity verification code, and the identity verification code is used by the Internet of Things device to perform identity verification on the first device; The second information is sent by the IoT device when it is determined that the identity verification has passed according to the identity verification code.

20. The method according to claim 19, characterized in that The first identity verification code received by the IoT device from the first device is different from the second identity verification code received by the IoT device from the second device; or The Internet of Things device is a first Internet of Things device, and the third identity verification code received by the first Internet of Things device from the first device is different from the fourth identity verification code received by the second Internet of Things device from the first device.

21. The method according to any one of claims 16 to 20, characterized in that: The first information includes scheduling request information, and the scheduling request information is used to request the Internet of Things device to send the second information; The second information is sent by the IoT device in response to the scheduling request information.

22. The method according to any one of claims 16 to 21, characterized in that: The first information includes scheduling indication information, where the scheduling indication information is used to indicate the type of data included in the second information; The second information is determined by the Internet of Things device according to the scheduling indication information.

23. The method according to any one of claims 16 to 22, characterized in that: The second information includes at least one of the following: Sensor data detected by the IoT device; The coding information of the Internet of Things device includes at least one code field.

24. The method according to any one of claims 16 to 23, characterized in that: Before sending the second information, the method includes: Sending third information, wherein the third information includes at least one of the following: first feedback information, where the first feedback information is used to indicate whether the IoT device allows the first device to read data information; second feedback information, where the second feedback information is used to request energy supply from the first device; The third feedback information is used to indicate a time offset when the first device sends the second information.

25. The method according to claim 24, characterized in that The sending the second information comprises: Determining that the second condition is satisfied; The second information is sent, wherein the second condition includes at least one of the following: The IoT device has sent the first feedback information, and the first feedback information is used to indicate that the IoT device allows the first device to read data information; The IoT device has sent the second feedback information and received a charging signal; The Internet of Things device has sent the third feedback information.

26. The method according to claim 22, characterized in that The method comprises: Sending fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device; The data type indicated by the scheduling indication information is at least one data type included in the first data type.

27. The method according to claim 22, characterized in that The method further comprises: Sending fourth information, where the fourth information is used to indicate a first data type, where the first data type is a data type that can be supported by the IoT device; Receive fifth information, where the fifth information is used to configure a data type of the Internet of Things device to be a second data type, where the second data type includes at least one data type included in the first data type; The data type indicated by the scheduling indication information is at least one data type included in the second data type.

28. The method according to claim 22, characterized in that The method comprises: receiving sixth information, where the sixth information is used to configure a data type of the IoT device as a third data type; The data type indicated by the scheduling indication information is at least one data type included in the third data type.

29. The method according to any one of claims 16 to 28, characterized in that: The first device includes at least one of the following: Access network equipment, core network equipment, terminals, radio frequency readers, intermediate node equipment, and auxiliary node equipment.

30. A first device, characterized in that: The first device comprises: A transceiver module is configured to send first information, where the first information is used to request the IoT device to send second information; The transceiver module is further configured to receive the second information, where the second information is used to indicate information of the Internet of Things device.

31. An Internet of Things device, characterized in that: The IoT devices include: A transceiver module is configured to receive first information sent by a first device, where the first information is used to request the IoT device to send second information; The transceiver module is further configured to send the second information, where the second information is used to indicate information of the Internet of Things device.

32. A first device, characterized in that: include: one or more processors; A memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the first device executes the information processing method according to any one of claims 1 to 15.

33. An Internet of Things device, characterized in that: include: one or more processors; A memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the Internet of Things device executes the information processing method described in any one of claims 16-29.

34. A communication system, characterized in that: The invention comprises a first device and an Internet of Things device, wherein the first device is configured to implement the information processing method described in any one of claims 1 to 15, and the Internet of Things device is configured to implement the information processing method described in any one of claims 16 to 29.

35. A storage medium storing instructions, characterized in that: When the instruction is executed on the communication device, the communication device executes the information processing method according to any one of claims 1-15 or 16-29.

Images