Communication methods and apparatus, and storage medium

Abstract

Provided in the embodiments of the present disclosure are communication methods and apparatus, a system, a storage medium and a program product. A method comprises: sending a first request to a second network element, the first request being used for requesting network element information of a third network element providing a service within a first area, and the second network element being used for storing network element information of at least one network element; and receiving a first response sent by the second network element, the first response comprising the network element information of at least one third network element providing the service within the first area. In the embodiments, the first network element obtains the network element information of at least one third network element by means of the request for requesting the third network element that provides the service in the first area, so as to ensure that the obtained at least one third network element can provide the service in the first area, thereby improving the accuracy of the obtained third network element and the accuracy of subsequently performing operation on an Internet of Things device by means of the third network element, and further ensuring the stability of an Internet of Things system.

Description

Communication methods, devices and storage media Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to communication methods, apparatus and storage media. Background Technology

[0002] With the integration of mobile communication technology and Internet of Things (IoT) technology, a scheme has been proposed to support IoT functions through the core network, thereby enabling operations to be performed on IoT devices. Summary of the Invention

[0003] When receiving an operation request for an IoT device, determining the network element that stores the IoT reader becomes a pressing issue.

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

[0005] According to a first aspect of the present disclosure, a communication method is provided, the method being executed by a first network element, the first network element being used to manage Internet of Things (IoT) devices, the method comprising:

[0006] Send a first request to the second network element, the first request being used to request network element information of a third network element providing services in the first area, the second network element being used to store network element information of at least one network element;

[0007] The system receives a first response sent by the second network element, the first response including network element information of at least one third network element providing services in the first area.

[0008] According to a second aspect of the present disclosure, a communication method is provided, the method being executed by a second network element, the second network element being used to store network element information of at least one network element, the method comprising:

[0009] Receive a first request sent by a first network element, the first request being used to request network element information of a third network element providing services in a first area, the first network element being used to manage IoT devices;

[0010] Send a first response to the first network element, the first response including network element information of at least one third network element providing services in the first area.

[0011] According to a third aspect of the present disclosure, a communication method is provided, the method being executed by a third network element that provides services in a first area, the method comprising:

[0012] Receive a second request sent by a first network element, the second request being used to request information on IoT readers available in the first area;

[0013] Send a second response to the first network element, the second response including information from at least one first IoT reader / writer.

[0014] According to a fourth aspect of the present disclosure, a communication device is provided for performing the communication method described in the first, second, or third aspect.

[0015] According to a fifth aspect of the present disclosure, a communication device is provided, comprising:

[0016] A transceiver module is used to perform the information receiving method described in the first, second, or third aspect.

[0017] According to a sixth aspect of the present disclosure, a network element is provided, comprising: one or more processors; wherein the processors are configured to perform the method described in any one of the first, second, or third aspects.

[0018] According to a seventh aspect of the present disclosure, an Internet of Things (IoT) system is proposed, comprising: a first network element, a second network element, and a third network element, wherein the first network element is configured to implement the communication method described in the first aspect, the second network element is configured to implement the communication method described in the second aspect, and the third network element is configured to implement the communication method described in the third aspect.

[0019] According to an eighth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a method as described in any one of the first, second, or third aspects.

[0020] In this embodiment of the disclosure, the first network element can request a request from a third network element providing services in the first area to obtain network element information of at least one third network element. This ensures that at least one third network element obtained can provide services in the first area, improves the accuracy of the obtained third network element, improves the accuracy of subsequent operations performed on IoT devices through the third network element, and thus ensures the stability of IoT system communication. Attached Figure Description

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

[0022] Figure 1A is a schematic diagram of the architecture of an Internet of Things system according to an embodiment of the present disclosure;

[0023] Figures 1B to 1C are schematic diagrams of the architecture of an Internet of Things (IoT) system according to embodiments of the present disclosure;

[0024] Figure 1D is a schematic diagram of a protocol stack according to an embodiment of the present disclosure;

[0025] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure;

[0026] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0027] Figure 4 is a flowchart illustrating a communication method according to an embodiment of the present disclosure;

[0028] Figure 5A is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure;

[0029] Figure 5B is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure;

[0030] Figure 5C is a schematic diagram of the structure of the third network element proposed in an embodiment of this disclosure;

[0031] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure;

[0032] Figure 6B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation

[0033] This disclosure provides a communication method, device, system, storage medium, and program product.

[0034] In a first aspect, embodiments of this disclosure propose a communication method, the method being executed by a first network element, the first network element being used to manage Internet of Things (IoT) devices, the method comprising:

[0035] Send a first request to the second network element, the first request being used to request network element information of a third network element providing services in the first area, the second network element being used to store network element information of at least one network element;

[0036] The system receives a first response sent by the second network element, the first response including network element information of at least one third network element providing services in the first area.

[0037] In the above embodiments, the first network element obtains network element information of at least one third network element by requesting a third network element to provide services in the first area. This ensures that at least one third network element obtained can provide services in the first area, improves the accuracy of the obtained third network element, improves the accuracy of subsequent operations performed on IoT devices through the third network element, and thus ensures the stability of the IoT system.

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

[0039] The region information of the first region;

[0040] The first indication information is used to indicate that the network element information requested by the first request is the network element information of a third network element.

[0041] In the above embodiments, the first request includes regional information indicating the first region, and the first indication information indicates the network element information of the third network element that needs to be obtained. Therefore, based on the regional information and the first indication information, the network element information of the third network element that provides services in the first region can be filtered out, preventing the situation where the obtained network element information of the third network element does not support providing services in the first region, and ensuring the accuracy of the obtained third network element information.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the first response includes a network element list, the network element list including network element information of the at least one third network element.

[0043] In the above embodiments, the second network element provides the network element information of the third network element through the network element list, and the network element list can carry the network element information of each third network element.

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

[0045] Send a second request to the target third network element, the second request being used to request information on IoT readers available in the first area;

[0046] Receive a second response sent by the target third network element, the second response including information from at least one first IoT reader / writer;

[0047] The target third network element is one or more of the at least one third network element mentioned in the first response.

[0048] In the above embodiments, by sending a second request to the target third network element to request information on IoT readers available in the first area, it is possible to obtain information on at least one first IoT reader. The obtained at least one first IoT reader is available in the first area, which means that the obtained at least one first IoT reader may be able to perform operations on IoT devices. When selecting an IoT reader for performing operations on IoT devices from the at least one first IoT reader, the accuracy of the selected IoT reader can be improved.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, ...

[0050] In the above embodiments, the target third network element can be selected from one or more of the third network elements in the first response, which improves the flexibility of the selected target third network element.

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

[0052] Regional information, wherein the regional information is used to indicate the first region;

[0053] The second instruction information is used to request the capabilities supported by the IoT reader / writer;

[0054] Event information, which indicates the event that triggers the sending of the second response.

[0055] In the above embodiments, the comprehensiveness of the parameters included in the second request is ensured, thereby ensuring the reliability of obtaining information from the first IoT reader based on the second request.

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

[0057] Information from the first IoT reader / writer;

[0058] The capabilities supported by the first IoT reader / writer.

[0059] In the above embodiments, by carrying the information of the first IoT reader and its supported capabilities in the second response, the comprehensiveness of the parameters included in the second response is ensured.

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

[0061] The third request is received from a fourth network element, which requests to perform an operation on an IoT device in the first area. The fourth network element is used for network opening.

[0062] A third response is sent to the fourth network element, the third response being used to indicate the result of the operation performed by the IoT reader on the IoT device.

[0063] In the above embodiments, the need to perform operations on IoT devices in the first area is determined by the third request, thereby ensuring that the third network element providing services in the first area is subsequently obtained based on the first area. The third request instructs the first area, enabling the first network element to select the third network element and IoT reader based on the first area, ensuring the reliability of the source of the first area, and thus including the reliability of the subsequent operations performed on the IoT devices.

[0064] In conjunction with some embodiments of the first aspect, in some embodiments, after receiving the second response sent by the target third network element, the method further includes:

[0065] Based on the information of the IoT reader included in the second response and the third request, a second IoT reader that meets the conditions is selected from at least one first IoT reader included in the second response, wherein the second IoT reader refers to the IoT reader corresponding to the information included in the third request.

[0066] In the above embodiments, the third request includes the IoT reader / writer expected to be used when requesting to perform operations on the IoT device, and the second response includes at least one first IoT reader / writer that is available based on the first area. By taking into account the information of the IoT reader / writer in the third request and the second response, a matching second IoT reader / writer can be found. The second IoT reader / writer can perform operations on the IoT device, thereby improving the success rate of performing operations on the IoT device.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, the third request includes at least one of the following:

[0068] The device identifier of the IoT device;

[0069] Information from the second IoT reader;

[0070] The region information of the first region;

[0071] An operation request, which instructs the IoT reader to perform an operation on an IoT device.

[0072] In the above embodiments, the information included in the third request is expanded to ensure the comprehensiveness of the information included in the third request, thereby improving the accuracy of subsequently determining the first region and the second IoT reader based on the third request.

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

[0074] Send a first message to the third network element corresponding to the second IoT reader / writer. The first message includes an operation request, which is used to instruct the second IoT reader / writer to perform an operation on the IoT device.

[0075] The system receives a fourth response from a third network element corresponding to the second IoT reader, the fourth response being used to indicate the result of the second IoT reader's action on the IoT device.

[0076] In the above embodiments, by sending a request to the second IoT reader for the operation to be performed by the second IoT reader on the IoT device, the operation on the IoT device is realized, thus ensuring the stability of the IoT system.

[0077] In conjunction with some embodiments of the first aspect, in some embodiments, the operation request or the fourth response includes information from the second IoT reader.

[0078] Secondly, embodiments of this disclosure propose a communication method, the method being executed by a second network element, the second network element being used to store network element information of at least one network element, the method comprising:

[0079] Receive a first request sent by a first network element, the first request being used to request network element information of a third network element providing services in a first area, the first network element being used to manage IoT devices;

[0080] Send a first response to the first network element, the first response including network element information of at least one third network element providing services in the first area.

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

[0082] The region information of the first region;

[0083] The first indication information is used to indicate that the network element information requested by the first request is the network element information of a third network element.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the first response includes a network element list, the network element list including network element information of at least one third network element.

[0085] Thirdly, embodiments of this disclosure propose a communication method, the method being executed by a third network element, the third network element providing services within a first area, the method comprising:

[0086] Receive a second request sent by a first network element, the second request being used to request information on IoT readers available in the first area;

[0087] Send a second response to the first network element, the second response including information from at least one first IoT reader / writer.

[0088] In conjunction with some embodiments of the third aspect, in some embodiments, the second request includes at least one of the following:

[0089] The second indication information is used to indicate whether the IoT reader is located in the first area;

[0090] Regional information, wherein the regional information is used to indicate the first region;

[0091] The second instruction information is used to request the capabilities supported by the IoT reader / writer;

[0092] Event information, which indicates the event that triggers the sending of the second response.

[0093] In conjunction with some embodiments of the third aspect, in some embodiments, the second response includes at least one of the following:

[0094] Information from the first IoT reader / writer;

[0095] The capabilities supported by the first IoT reader / writer.

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

[0097] The system receives a first message sent by the first network element. The first message includes an operation request, which is used to instruct the second IoT reader to perform an operation on the IoT device. The operation command is used to instruct the IoT reader to perform an operation on the IoT device.

[0098] A fourth response is sent to the first network element, the fourth response being used to indicate the result of the second IoT reader / writer's action on the IoT device.

[0099] In conjunction with some embodiments of the third aspect, in some embodiments, the first message or the fourth response includes information from the second IoT reader.

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

[0101] Send the operation request to the second IoT reader;

[0102] The system receives a fifth response sent by the second IoT reader, the fifth response being used to indicate the result of the second IoT reader's action on the IoT device.

[0103] Fourthly, embodiments of this disclosure provide a communication device for performing the communication methods described in the first, second, or third aspects.

[0104] Fifthly, embodiments of this disclosure provide a communication device, which includes at least one of a transceiver module and a processing module; wherein the communication device is used to execute the optional implementations described in the first, second, or third aspects.

[0105] In a sixth aspect, embodiments of this disclosure provide a network element, including: one or more processors; wherein the processors are configured to perform the method described in any one of the first, second, or third aspects.

[0106] In a seventh aspect, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in any one of the first, second, or third aspects.

[0107] Eighthly, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method described in any of the first, second, or third aspects.

[0108] In a ninth aspect, embodiments of this disclosure provide a computer program that, when run on a communication device, causes the communication device to perform the method described in any of the first, second, or third aspects.

[0109] In a tenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in any of the first, second, or third aspects.

[0110] It is understood that the aforementioned communication devices, IoT systems, storage media, and program products are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0111] This disclosure provides a communication method, device, system, storage medium, and program product. In some embodiments, the terms communication method, information processing method, discovery method, etc., may be used interchangeably.

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

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

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

[0115] In the embodiments disclosed herein, "multiple" refers to two or more.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0133] As shown in Figure 1A, the Internet of Things (IoT) system 100 includes a first network element 101, a second network element 102, a third network element 103, a fourth network element 104, an IoT reader / writer 105, an IoT device 106, and a fifth network element 107.

[0134] In some embodiments, the IoT device 106 is an environmental IoT device. For example, an environmental IoT device is an AIoT device.

[0135] In some embodiments, the first network element 101 is an AIOTF (Ambient IoT function) network element. This AIOTF network element is used to manage the IoT device 106. Optionally, this AIOTF network element is a newly proposed network element in the IoT system, which can directly or indirectly send requests to the IoT reader 105 to perform operations on the IoT device 106 via the AMF (Access and Mobility Management Function).

[0136] Optionally, it is assumed that the AIoT RAN supports environment-specific IoT functions. There is no assumption as to whether the AIoT RAN (i.e., BS Reader) also has NR-Uu radio access network nodes.

[0137] Alternatively, NGAPNGAP may be used when AIOTF communicates directly with AIOT RAN (i.e., via the Nx reference point) or indirectly with AIOT RAN via AMF (i.e., via the N2 reference point).

[0138] Alternatively, it is assumed that the environmental IoT service can be deployed independently of existing deployments.

[0139] Optionally, it is not desirable for deployments to use both direct communication between the AIOT RAN and AIOTF and indirect communication between the AIOT RAN and AIOTF via AMF. Deployment choices can be based on, for example, using a direct communication path for local deployments.

[0140] —On the AIoT RAN node, the signaling transmission protocol for NGAP is SCTP / IP.

[0141] Optionally, the AIOTF can perform IoT reader selection. The AF (Application Function) provides information to identify the reader for inclusion in the initial reader selection network. This information can identify multiple or a single reader for the request.

[0142] It should be noted that the identification of which readers are identified by the AF information depends on the network deployment, configuration, or implementation.

[0143] - If the AF provides a single UE Reader ID for operation via NEF (Network Exposure Function), then use it as the selected Reader.

[0144] - If reader selection information or the UE reader ID is not provided, then how AIOTF determines which reader to use is implementation-based. For example, AIOTF may pre-configure the reader to use, or take into account the last known location of the requested target AIoT (Ambient IoT) device, etc.

[0145] If there are no readers to choose from, the request is rejected.

[0146] Optionally, AIoT device identification information is determined based on information from the AF. This information is included in the paging message on the AIoT radio interface to locate the AIoT device. The AIoT device compares the AIoT device identification information with its own AIoT device identifier (partial or complete) to determine whether to respond to the paging message.

[0147] Optionally, taking into account the auxiliary information provided by AF, determine the reader auxiliary information required for the operation of the reader.

[0148] Optionally, an inventory operation request is constructed using the AIoT device identification information page of the determined AIoT device, and an association identifier is constructed for AIOTF to associate the inventory response with the request. The inventory request is routed to the reader selected by the initial reader.

[0149] Optionally, the Reader executes the inventory request, reporting the AIoT-specific NAS (Non-Access Stratum) message response from the AIoT device to AIOTF, including its Reader ID and the associated identifier from AIOTF. The Reader can aggregate results from multiple AIoT devices in the response message. AIOTF can then determine which request the result using the associated identifier belongs to.

[0150] Alternatively, AIOTF can obtain similar subscription information from any of the following sources, based on information within the AIoT device identifier:

[0151] - The service network that performs the operation (identified by the AIoT device identifier or operator policy to check if it provides information about a specific AIoT device), or

[0152] - Another network identified by the AIoT device identifier, or

[0153] - A third party identified by the AIoT device identifier.

[0154] Optionally, check if the AIoT device has already subscribed.

[0155] Optionally, if the operation is a command operation, the AIoT generates a request including an AIoT-specific NAS message for that command, as well as any additional information required by the Reader to execute the command, such as the task ID. The request is then routed to the Reader. The Reader executes the command, delivering the AIoTF-specific NAS message to the AIoT device and collecting any AIoT-specific NAS responses. The AIoT-specific NAS responses are then routed back to the AIOTF.

[0156] Note 3: Whether and how to apply security protections to AIoT-specific NAS messages sent to AIoT devices and AIoT-specific NAS messages responded to by AIoT devices depends on SA WG3.

[0157] Optionally, results can be provided to NEF. Results from multiple AIoT devices may be included / aggregated in the service response.

[0158] In some embodiments, the second network element 102 is an NRF (Network Repository Function) used to store network element information of at least one network element. For example, the NRF can store network element information of network elements such as the first network element 101, the third network element 103, and the fourth network element 104.

[0159] In some embodiments, the third network element 103 is an AMF (Active Mobile Component) used to provide services within a first area. Additionally, the AMF is also used to store information from the IoT reader 105.

[0160] In some embodiments, the fourth network element 104 is a NRF (Network Frame Function) used to provide open functionality. Additionally, the NRF is also used to provide communication between the fifth network element 107 and the first network element 101.

[0161] In some embodiments, the IoT reader 105 can be a terminal or a network device. Optionally, the name of the IoT reader 105 is not limited, and it can be, for example, IoT reader, reader, etc.

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

[0163] In some embodiments, the network device includes at least one of the access network devices.

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

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

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

[0167] In some embodiments, the Internet of Things device 106 may be a device with lower functionality, such as a card or sensor.

[0168] In some embodiments, the fifth network element 107 is AF.

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

[0170] The following embodiments of this disclosure can be applied to the Internet of Things (IoT) system 100 shown in FIG1A, or to some of its subjects, but are not limited thereto. The subjects shown in FIG1A are illustrative. The IoT system may include all or some of the subjects in FIG1A, or it may include other subjects outside of FIG1A. The number and form of each subject are arbitrary. Each subject may be physical or virtual. The connection relationship between the subjects is illustrative. The subjects may not be connected or may be connected. The connection may be in any way, such as direct connection or indirect connection, wired connection or wireless connection.

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

[0172] In some embodiments, referring to Figure 1B, taking the first network element 101 as AIOTF, the third network element as AMF, and the IoT reader / writer 105 as AIOT RAN (Radio Access Network) as an example, the AIOTF communicates indirectly with the AIOT RAN through the AMF. Optionally, the AIOTF connects to the AIOT RAN through the AMF. The NGAP at the N2 reference point between the AIOT RAN and the AMF supports environmental IoT services, including delivery inventory / command messages. It should be noted that if network isolation is required, an AMF instance is deployed to support communication between the AIOTF and the AIOT RAN. The NGAP between the AIOT RAN and the AMF is enhanced to support environmental IoT services. Specifically, the NGAP at the N2 reference point between the AIOT RAN and the AMF supports IoT services. Additionally, at the Nz reference point, the AMF supports services used by the AIoTF for environmental IoT operations, such as sending AIoT requests to the AIoT RAN and receiving AIoT responses from the AIoT RAN. At the N2 reference point, the AMF supports sending AIoT information (such as operation requests) to the AIoT RAN and receiving responses from the AIoT RAN. The AMF routes AIoT messages between the AIoT RAN (based on the N2 reference point) and the AIOTF (based on the Nz reference point).

[0173] Referring to Figure 1C, taking the first network element 101 as AIOTF, the third network element as AMF, and the IoT reader / writer 105 as AIOT RAN (terminal) as an example, the AIOTF communicates indirectly with the AIOT RAN through the AMF.

[0174] Figure 1C specifies two architecture options:

[0175] -Subscription aspect: -Terminal subscriptions in UDM will be expanded to terminal reader / writer subscription information, including the following: -Information on whether the terminal is allowed to act as a terminal reader / writer.

[0176] -AMF and AIoTF can obtain UE Reader subscription information.

[0177] —If the AMF receives an instruction that the terminal is authorized to operate as a UE Reader as part of the subscription information, the AMF notifies the NG-RAN that the terminal is authorized to operate as a UE Reader.

[0178] Optionally, whether and how to enable authorization for the terminal is FFS.

[0179] -Radio resource management for UE Reader operations;

[0180] —If the gNB has received an instruction that a terminal has been authorized to operate as a terminal reader, the gNB may allocate radio resources to that terminal for terminal reader operation.

[0181] - Assume that the UE reader requests radio resources from the gNB to perform reader operations (e.g., consider assistance information received from the AIoTF).

[0182] —Messages between the UE Reader and AIoTF use RRC (Radio Resource Control) between the UE and RRC, NGAP (Next Generation Application Protocol) between the gNB and AMF, and the SBI (System Information Block) interface between the AMF and AIoTF. The protocol stack is shown in Figure 1D.

[0183] Figure 2 is an interactive schematic diagram of an information sending and receiving method according to an embodiment of the present disclosure. As shown in Figure 2, the embodiments of the present disclosure relate to an information sending and receiving method, which includes:

[0184] Step S2101: The fifth network element sends a fourth request to the fourth network element.

[0185] In some embodiments, the fourth network element receives a fourth request sent by the fifth network element. Optionally, the fifth network element is AF and the fourth network element is NEF.

[0186] In some embodiments, the fourth request is used to request the performance of an operation on an IoT device. Alternatively, it can be understood as the fourth request to request the performance of an operation on an IoT device that meets certain conditions. These conditions are indicated by parameters included in the fourth request.

[0187] In some embodiments, the fourth request includes at least one of the following: a device identifier of an IoT device, a reader identifier of an IoT reader, operation parameters, or an operation request. Optionally, the fourth request is used to request the IoT device indicated by the device identifier to perform an operation. Optionally, the operation to be performed on the IoT device is indicated by an operation request. For example, the operation request can be an inventory operation, or it can be a command operation, wherein the command operation can be a read command or a write command to the IoT device, or it can be other commands. Optionally, the fourth request can perform an operation on the IoT device through the IoT reader indicated by the reader identifier. Optionally, the operation parameters can indicate a first area, which can also be understood as the area where the operation is performed on the IoT device.

[0188] In some embodiments, the fourth request includes at least one of the following: a device identifier of an IoT device, a reader identifier of an IoT reader, operating parameters, or an operating request. The device identifier of the IoT device is an identifier for the device from outside the core network; the reader identifier of the IoT reader is an identifier for the reader from outside the core network; and the operating parameters or operating request are parameters or indications for performing operations on the IoT device through the IoT reader from outside the core network. In some embodiments, the fourth request includes at least one of the following: an external device identifier of the IoT device, an external reader identifier of the IoT reader, external operating parameters, or an operating request. Optionally, the fourth request is used to request the IoT device indicated by the external device identifier to perform an operation. Optionally, the operation to be performed on the IoT device is indicated by an operating request. For example, the operating request can be an inventory operation, or it can be a command operation, wherein the command operation can be a read command or a write command to the IoT device, or it can be other commands. Optionally, the fourth request can perform an operation on the IoT device through the IoT reader indicated by the external reader identifier. Optionally, the external operating parameters can indicate a first area, which can also be understood as the area where the operation is performed on the IoT device.

[0189] In this embodiment of the disclosure, after receiving the fourth request, the fourth network element can determine which operations the fifth network element performs on which IoT device through which IoT reader / writer based on the fourth request.

[0190] In step S2102, the fourth network element transforms the parameters included in the fourth request to obtain the third request.

[0191] In some embodiments, after receiving the fourth request, the fourth network element converts the parameters included in the fourth request to obtain the third request.

[0192] In some embodiments, since the parameters included in the fourth request are at least one of the following: the identifier of the device outside the core network, the identifier of the reader outside the core network, or the parameters or instructions of the IoT device performed by the IoT reader outside the core network, other network elements may not be able to recognize the parameters included in the fourth request. Therefore, the fourth network element needs to first convert the parameters outside the core network included in the fourth request into parameters inside the core network so that other core network elements can recognize them, and then carry the converted parameters in the third request.

[0193] The fourth network element needs to send parameters to other network elements. However, other network elements may not be able to recognize the parameters included in the fourth request. Therefore, the fourth network element needs to convert the parameters included in the fourth request to obtain parameters that other network elements can recognize, and then carry the converted parameters in the third request.

[0194] In some embodiments, since the fourth network element needs to send parameters to other network elements, and other network elements may not be able to recognize the parameters included in the fourth request, the fourth network element needs to first convert the parameters included in the fourth request to obtain parameters that other network elements can recognize, and then carry the converted parameters in the third request.

[0195] Optionally, the third request is an Nnef_AIoT_inventory request or an Nnef_AIoT_command request.

[0196] Optionally, the fourth network element can convert the external device identifier into the device identifier of the IoT device, or it can be said to convert it into the internal device identifier of the IoT device.

[0197] Optionally, the fourth network element can convert the external reader identifier into the reader identifier of the IoT reader, or it can be said to convert it into the internal reader identifier of the IoT reader.

[0198] Optionally, the operating parameters include parameters indicating the first area, and the fourth network element can convert the parameters used to indicate the first area into area information for the first area. This area information may include an area identifier. For example, the area information may include an AOI (Area of ​​Interest) or a TAI (Tracking Area Identity). For example, the area information may be identified by an AOI. For example, the area information may be identified by a TA (Tracking Area).

[0199] In some embodiments, the third request includes at least one of the following:

[0200] (1) Device identification of Internet of Things (IoT) devices.

[0201] In this embodiment of the disclosure, after the fourth network element sends a third request to the first network element, the first network element can determine the IoT device that needs to perform the operation based on the device identifier of the IoT device included in the received third request.

[0202] (2) Information of the second IoT reader.

[0203] In this embodiment of the disclosure, after the fourth network element sends a third request to the first network element, the first network element can determine the IoT reader that needs to perform an operation on the IoT device based on the information of the second IoT reader included in the received third request.

[0204] (3) Regional information of the first region.

[0205] In this embodiment of the disclosure, after the fourth network element sends a third request to the first network element, the first network element can determine the first region based on the region information included in the received third request.

[0206] It should be noted that the fourth network element can select a first network element that meets the requirements, and then send a third request to the selected first network element. For example, if the fourth network element is NEF and the first network element is AIOTF, then NEF can select a qualified AIOTF and then send a third request to the selected AIOTF.

[0207] (4) Operation request: The operation request is used to instruct the IoT reader to perform an operation on the IoT device.

[0208] For example, the operation request can be an inventory operation or a command operation, wherein the command operation can be a read command or a write command to the IoT device, or other commands. In this embodiment of the disclosure, after the fourth network element sends the third request to the first network element, the first network element can determine the operation performed by the IoT reader on the IoT device based on the operation request included in the received third request.

[0209] In step S2103, the fourth network element sends a third request to the first network element.

[0210] In some embodiments, the first network element receives a third request sent by the fourth network element. Optionally, the first network element is an AIOTF.

[0211] In some embodiments, the third request includes at least one of the following:

[0212] (1) Device identification of Internet of Things (IoT) devices.

[0213] In this embodiment of the disclosure, after the fourth network element sends a third request to the first network element, the first network element can determine the IoT device that needs to perform the operation based on the device identifier of the IoT device included in the received third request.

[0214] (2) Information of the second IoT reader.

[0215] In this embodiment of the disclosure, after the fourth network element sends a third request to the first network element, the first network element can determine the IoT reader that needs to perform an operation on the IoT device based on the information of the second IoT reader included in the received third request.

[0216] (3) Regional information of the first region.

[0217] In this embodiment of the disclosure, after the fourth network element sends a third request to the first network element, the first network element can determine the first region based on the region information included in the received third request.

[0218] It should be noted that the fourth network element can select a first network element that meets the requirements, and then send a third request to the selected first network element. For example, if the fourth network element is NEF and the first network element is AIOTF, then NEF can select a qualified AIOTF and then send a third request to the selected AIOTF.

[0219] (4) Operation request: The operation request is used to instruct the IoT reader to perform an operation on the IoT device.

[0220] For example, the operation request can be an inventory operation or a command operation, wherein the command operation can be a read command or a write command to the IoT device, or other commands. In this embodiment of the disclosure, after the fourth network element sends the third request to the first network element, the first network element can determine the operation performed by the IoT reader on the IoT device based on the operation request included in the received third request.

[0221] Step S2104: The first network element sends a first request to the second network element.

[0222] In some embodiments, after receiving a third request from a fourth network element, the first network element sends a first request to the second network element.

[0223] In some embodiments, the second network element receives a first request sent by the first network element. Optionally, the first request is an Nnrf_NFDiscovery_Request. Optionally, the second network element is an NRF.

[0224] In some embodiments, the first request is used to request network element information of a third network element providing services in a first area. In some embodiments, the second network element is used to store network element information of at least one network element.

[0225] In this embodiment of the disclosure, the second network element can store network element information of at least one network element. After receiving the first request, the second network element can determine, based on the first request, at least one third network element that can provide services in the first area indicated by the first request.

[0226] Optionally, the second network element determines at least one third network element that can provide services in the first area by querying the network element information of the stored network elements.

[0227] In some embodiments, the first request includes at least one of the following:

[0228] (1) Regional information of the first region.

[0229] In this embodiment of the disclosure, the second network element can determine the first region based on the region information included in the received first request, and then select a network element that can provide services to the first region.

[0230] This area information may include an area identifier. For example, the area information may include an AOI (Area of ​​Interest) or a TAI (Tracking Area Identity). For example, the area information may be identified by an AOI. For example, the area information may be identified by a TA (Tracking Area).

[0231] (2) First indication information, the first indication information is used to indicate that the network element information requested by the first request is the network element information of the third network element.

[0232] In this embodiment of the disclosure, the second network element can determine the requested network element information as the network element information of the third network element based on the first indication information included in the received first request.

[0233] Optionally, the second network element can determine, based on the regional information and the first indication information, that the network element information requested by the first request refers to a third network element that supports providing services in the first region.

[0234] In step S2105, the second network element sends a first response to the first network element.

[0235] In some embodiments, after receiving a first request from a first network element, the second network element sends a first response to the first network element.

[0236] In some embodiments, the first network element receives a first response sent by the second network element. Optionally, the first response is Nnrf_NFDiscovery_Response. In this embodiment of the disclosure, after receiving the first response sent by the second network element, the first network element can determine a third network element that can provide services in the first area, and subsequently use the determined third network element to find the IoT reader / writer.

[0237] In some embodiments, the first request includes area information of a first region, and the second network element determines network element information of at least one third network element providing services in the first region based on the area information of the first region included in the first request.

[0238] In some embodiments, the first request includes area information of a first region and first indication information. The second network element determines network element information of at least one third network element providing services in the first region based on the area information of the first region and the first indication information included in the first request.

[0239] In some embodiments, the second network element determines network element information of at least one third network element providing services within a first area, and sends a first response to the first network element, the first response including network element information of at least one third network element providing services within the first area.

[0240] In some embodiments, the first response includes network element information of at least one third network element providing services within a first area. Optionally, the first response includes a network element list, which includes network element information of at least one third network element. For example, the network element information of the third network element is a network element identifier. Optionally, the network element list can be a GUAMI (Global Unique AMF Identifier) ​​list, or other lists.

[0241] Optionally, the third network element is an AMF.

[0242] Step S2106: The first network element determines the target third network element based on at least one third network element in the first response.

[0243] In some embodiments, after receiving a first response from a second network element, the first network element determines a target third network element based on network element information of at least one third network element providing services within a first area contained in the first response.

[0244] In some embodiments, the target third network element refers to a third network element that can be subsequently selected as supporting IoT readers to perform operations on IoT devices. In some embodiments, the target third network element is one or more of at least one third network element in the first response.

[0245] Optionally, the first network element may determine the third network element with the largest overlap with the first region among at least one third network element as the target third network element. Optionally, the first network element may randomly select one third network element as the target third network element. It should be noted that the embodiments of this disclosure are used as examples to illustrate how the first network element selects the target third network element. Optionally, the first network element may determine all at least one third network element included in the first response as target third network elements. It should be noted that the first network element may select the target third network element based on the actual implementation, and the embodiments of this disclosure do not limit how the first network element selects the target third network element.

[0246] Step S2107: The first network element sends a second request to the target third network element.

[0247] In some embodiments, the target third network element receives a second request sent by the first network element. Optionally, the second request is a Namf_EventExposure_Subscribe Request or a Namf_UEinfo Request.

[0248] In some embodiments, the second request is used to request information about IoT readers available in the first area.

[0249] In some embodiments, the second request is used to request information about terminals available in the first area, wherein the terminal may be an Internet of Things (IoT) reader / writer.

[0250] In some embodiments, the second request is used to request information on available wireless access network nodes in a first area, wherein the wireless access network nodes may act as IoT readers.

[0251] In some embodiments, the second request is used to request information on IoT readers available in the first area. In this disclosure embodiment, if the target third network element receives the second request, it can determine that it needs to send information on IoT readers available in the first area to the first network element.

[0252] In some embodiments, the second request includes at least one of the following:

[0253] (1) Second indication information, which is used to request the capability supported by the Internet of Things reader.

[0254] (2) Area information, which is used to indicate the first area.

[0255] (3) Event information, which is used to indicate the event that triggers the sending of the second response.

[0256] Optionally, the event information includes an event identifier or the target of the event report, with the event identifier indicating the event that triggers the sending of a second response. For example, if the event indicated by the event information is met, a second response is sent. The target of the event report refers to which IoT readers can trigger the event indicated by the event identifier.

[0257] For example, the event information indicates that the second response is sent when the IoT reader enters the first area. Alternatively, the second response is sent when the IoT reader leaves the first area.

[0258] For example, the event information indicates that the event is when the IoT reader sends a second response when it has positioning capabilities.

[0259] Alternatively, the above events can also be considered together, and a second response can be sent if the IoT reader enters the first area and has positioning capabilities.

[0260] Optionally, the event information includes an IoT reader identifier, meaning the target of the event report is the IoT reader indicated by the IoT reader identifier. For example, if the IoT reader is a terminal and the IoT reader identifier is a terminal identifier, then the target of the event report is the terminal indicated by the terminal identifier.

[0261] Optionally, if the target of the event is a terminal, the event information includes the following parameters:

[0262] The event report's target is "any terminal", and the event ID is "user device enters / leaves area of ​​interest" / "user device enters or leaves area of ​​interest" to indicate whether the user device is in the area. Optionally, another event ID, "reachability filter", can be used to indicate whether the user device is reachable.

[0263] Optionally, if the target of the event is a terminal, the event information includes the following parameters:

[0264] The event report's target is "any device" and the event ID is "reachability filter" to indicate whether the user device is reachable.

[0265] In this embodiment of the disclosure, the target third network element can determine whether the information of the available IoT reader / writer is in the first area based on the area information.

[0266] In step S2108, the target third network element sends a second response to the first network element.

[0267] In some embodiments, after receiving a second request from a first network element, the target third network element sends a second response to the first network element.

[0268] In some embodiments, the first network element receives a second response sent by the target third network element. Optionally, the second response is a Namf_EventExposure_Subscribe Response or a Namf_UEinfo Response.

[0269] In some embodiments, the second response includes information from at least one first IoT reader / writer.

[0270] In some embodiments, the third network element retrieves at least one of the terminal information and access network information stored in the area information to determine at least one first IoT reader that satisfies the second request.

[0271] In some embodiments, the third network element retrieves at least one of the terminal information and access network information stored in the area information, determines at least one first IoT reader that satisfies the second request, and sends a second response to the first network element, the second response including information of at least one first IoT reader.

[0272] Optionally, the second response includes at least one of the following:

[0273] (1) Information of the first Internet of Things reader.

[0274] Optionally, the second response includes a list of readers, which includes information about at least one first IoT reader. For example, when the IoT reader is a terminal, the information can be a terminal identifier. For example, the terminal information can be a SUPI (Subscriber Permanent Identifier) ​​list.

[0275] It should be noted that if the second response is event-triggered, there is a possibility that a feedback message may be subsequently sent to the first network element. Optionally, a feedback message can be sent when the event information indicates that the event has been triggered. Optionally, the feedback message is Namf_EventExposure_Subscribe Notify. It should be noted that the parameters included in the event information are the same as those included in the second response in the above embodiments. Optionally, the feedback message includes information about the first IoT reader, the capabilities supported by the first IoT reader, and the corresponding event information.

[0276] Optionally, if the IoT reader is a network device, the information of the first IoT reader is the identifier of the network device.

[0277] (2) Capabilities supported by the first IoT reader.

[0278] In some embodiments, the capabilities supported by the first IoT reader may be positioning capabilities or other capabilities.

[0279] It should be noted that if the second request includes the second instruction information, it indicates that the capability of the IoT reader needs to be sent. Therefore, the second response includes the capability supported by the first IoT reader.

[0280] Step S2109: The first network element selects a second IoT reader from at least one first IoT reader.

[0281] In some embodiments, the first network element selects a second IoT reader that meets the conditions from at least one first IoT reader included in the second response, based on the information included in the second response and the third request.

[0282] In this embodiment of the disclosure, since the third network element sends information about IoT readers available in the first area to the first network element, and the third request received by the first network element also includes information about IoT readers expected by the fifth network element, the second IoT device that meets the conditions can be determined based on the information about IoT readers expected by the fifth network element and the information about IoT readers available in the first area.

[0283] In some embodiments, the first network element may select one or more second IoT readers that meet the conditions. This disclosure does not limit the number of second IoT readers.

[0284] In some embodiments, the second IoT reader refers to the IoT reader corresponding to the information included in the third request.

[0285] It should be noted that, in this embodiment of the present disclosure, the first network element can also determine the corresponding IoT device based on the device identifier of the IoT device included in the third request, and then carry the device identifier of the IoT device to indicate the IoT device when sending the first message in the future.

[0286] In some embodiments, the first network element selects a second IoT reader that meets the conditions from at least one first IoT reader included in the second response.

[0287] Optionally, the first network element selects the IoT reader / writer with the largest overlap between its coverage area and the first area from at least one first IoT reader / writer to determine it as the second IoT reader / writer. Alternatively, the first network element randomly selects an IoT reader / writer from at least one first IoT reader / writer to determine it as the second IoT reader / writer. Alternatively, the first network element selects the IoT reader / writer with the highest priority from at least one first IoT reader / writer to determine it as the second IoT reader / writer.

[0288] In step S2110, the first network element sends a first message to the third network element corresponding to the second IoT reader.

[0289] In some embodiments, after the first network element determines the second IoT reader, the first network element sends a first message to the third network element corresponding to the second IoT reader.

[0290] In some embodiments, a third network element corresponding to the second IoT reader receives a first message sent by the first network element. Optionally, the first message is a Namf_Communication_N1N2MessageTransfer message.

[0291] In some embodiments, the first message includes an operation request, which instructs the second IoT reader to perform an operation on the IoT device. Optionally, the operation request includes an inventory request / command request. In some embodiments, the operation request includes information about the second IoT reader. Alternatively, it can be understood that the first message includes information about the second IoT reader, and the operation request is a request to the second IoT reader indicated by the information to perform an operation on the IoT device.

[0292] In some embodiments, the operation request included in the first message comes from a third request, or the operation request included in the first message refers to the operation request included in the third request.

[0293] In some embodiments, the first message further indicates a device identifier of an IoT device, which also comes from the third request; or, the device identifier of the IoT device in the first message refers to the device identifier of the IoT device included in the third request.

[0294] In step S2111, the third network element sends an operation request to the second IoT reader.

[0295] In some embodiments, the third network element will pass the operation request to the second IoT reader.

[0296] In this embodiment of the disclosure, since the first message includes information about the second IoT reader, the corresponding second IoT reader can be determined based on the information, and the operation request can be directly sent to the second IoT reader.

[0297] In some embodiments, if the second IoT reader is a terminal, the operation request can be carried in a NAS message and sent to the terminal. Alternatively, if the second IoT reader is a network device, the operation request can be carried in an NGAP message and sent to the network device.

[0298] In step S2112, the second IoT reader sends an operation request to the IoT device.

[0299] In some embodiments, the IoT device receives an operation request sent by a second IoT reader / writer.

[0300] In step S2113, the IoT device sends a sixth response to the second IoT reader.

[0301] In some embodiments, the second IoT reader receives a sixth response sent by the IoT device.

[0302] In some embodiments, the sixth response is used to indicate the result of the IoT device performing the operation request. Optionally, the result includes success or failure.

[0303] In some embodiments, if the operation request is an inventory operation, the IoT device performs the inventory operation. Alternatively, if the operation request is a command request, the IoT device executes the command.

[0304] In this embodiment of the disclosure, after receiving the operation request, the IoT device can perform the corresponding operation based on the operation request, and then send a sixth response to the second IoT device to indicate the result of the operation request.

[0305] In some embodiments, the sixth response includes at least one of the following: a result, network element information of the first network element, and a notification-related identifier. Optionally, the notification-related identifier is used by the fourth network element to identify the operation request.

[0306] In step S2114, the second IoT reader sends a fifth response to the third network element.

[0307] In some embodiments, the third network element receives a fifth response sent by the second IoT device.

[0308] In some embodiments, the fifth response is used to indicate the result of the second IoT reader / writer performing an action on the IoT device.

[0309] In some embodiments, the fifth response includes at least one of the following: a result, network element information of the first network element, and a notification-related identifier.

[0310] In some embodiments, if the second IoT reader is a terminal, the fifth response is carried in a NAS message. Alternatively, if the second IoT reader is a network device, the fifth response is carried in an NGAP message.

[0311] In step S2115, the third network element sends a fourth response to the first network element.

[0312] In some embodiments, the first network element receives a fourth response sent by the third network element.

[0313] In some embodiments, the fourth response is used to indicate the result of the second IoT reader / writer performing an action on the IoT device.

[0314] In this embodiment of the disclosure, the fifth response received by the third network element includes the network element information of the first network element. The first network element can be determined based on the network element information, and then the fourth response can be sent to the first network element.

[0315] Optionally, the third network element sends a fourth response to the first network element via transparent transmission.

[0316] In some embodiments, the fourth response includes at least one of the results or information from the second IoT reader.

[0317] Optionally, if the second IoT reader is a terminal, the fourth response is carried in Namf_Communication_N1MessageNotify. Alternatively, if the second IoT reader is a network device, the fourth response is carried in Namf_Communication_N2MessageNotify.

[0318] In step S2116, the first network element sends a third response to the fourth network element.

[0319] In some embodiments, the fourth network element receives a third response sent by the first network element.

[0320] In some embodiments, the third response is used to indicate the result of the operation performed by the IoT reader on the IoT device.

[0321] In step S2117, the fourth network element sends a seventh response to the fifth network element.

[0322] In some embodiments, the fifth network element receives a seventh response sent by the fourth network element.

[0323] In some embodiments, the seventh response is used to indicate the result of an operation performed by the IoT reader on an IoT device.

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

[0325] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

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

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

[0328] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2117. For example, any of steps S2101 to S2117 may be implemented as an independent embodiment, but is not limited thereto.

[0329] In some embodiments, at least one of steps S2101 to S2117 is optional, and one or more of these steps may be omitted or substituted in different embodiments.

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

[0331] Figure 3 is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3, the present disclosure relates to a communication method, which includes:

[0332] Step S3101: The first network element sends a first request to the second network element.

[0333] In some embodiments, the first request is used to request network element information of a third network element providing services in a first area, and the second network element is used to store network element information of at least one network element.

[0334] In step S3102, the second network element receives the first request sent by the first network element.

[0335] In some embodiments, the implementation of steps S3101-S3102 can be referred to the implementation of step S2104 in FIG2, and will not be repeated here.

[0336] In some embodiments, the first request includes at least one of the following:

[0337] The region information of the first region;

[0338] The first indication information is used to indicate that the network element information requested by the first request is the network element information of a third network element.

[0339] In some embodiments, the first response includes a list of network elements, which includes network element information of the at least one third network element.

[0340] In step S3103, the second network element sends a first response to the first network element.

[0341] In some embodiments, the first response includes network element information of at least one third network element providing services in the first area.

[0342] In step S3104, the first network element receives the first response sent by the second network element.

[0343] In some embodiments, the implementation of steps S3103-S3104 can be referred to the implementation of step S2105 in FIG2, and will not be repeated here.

[0344] In step S3105, the first network element sends a second request to the third network element.

[0345] In some embodiments, the second request is used to request information about IoT readers available in the first area.

[0346] Step S3106: The third network element receives the second request sent by the first network element.

[0347] In some embodiments, the implementation of steps S3105-S3106 can be referred to the implementation of step S2107 in FIG2, and will not be repeated here.

[0348] In step S3107, the third network element sends a second response to the first network element.

[0349] In some embodiments, the second response includes information from at least one first IoT reader / writer.

[0350] In step S3108, the first network element receives the second response sent by the third network element.

[0351] In some embodiments, the implementation of steps S3107-S3108 can be referred to the implementation of step S2108 in FIG2, and will not be repeated here.

[0352] In some embodiments, the target third network element is one or more of the at least one third network element mentioned in the first response.

[0353] In some embodiments, the second request includes at least one of the following:

[0354] The second indication information is used to indicate whether the IoT reader is located in the first area;

[0355] Event information, which is used to indicate an event, wherein the event refers to the IoT reader being located in the first area or the IoT reader not being located in the first area;

[0356] The second instruction information is used to request the capabilities supported by the IoT reader / writer;

[0357] Regional information, which is used to indicate the first region.

[0358] In some embodiments, the second response includes at least one of the following:

[0359] Information from the first IoT reader / writer;

[0360] The capabilities supported by the first IoT reader / writer.

[0361] In some embodiments, the method further includes:

[0362] The third request is received from a fourth network element, which requests to perform an operation on an IoT device in the first area. The fourth network element is used for network opening.

[0363] A third response is sent to the fourth network element, the third response being used to indicate the result of the operation performed by the IoT reader on the IoT device.

[0364] In some embodiments, after receiving the second response sent by the target third network element, the method further includes:

[0365] Based on the information included in the second response and the third request, a second IoT reader that meets the conditions is selected from at least one first IoT reader included in the second response.

[0366] In some embodiments, the second IoT reader / writer refers to the IoT reader / writer corresponding to the information included in the third request.

[0367] In some embodiments, the third request includes at least one of the following:

[0368] The device identifier of the IoT device;

[0369] Information from the second IoT reader;

[0370] The region information of the first region;

[0371] An operation request, which instructs the IoT reader to perform an operation on an IoT device.

[0372] In some embodiments, the method further includes:

[0373] Send a first message to the third network element corresponding to the second IoT reader / writer. The first message includes an operation request, which is used to instruct the second IoT reader / writer to perform an operation on the IoT device.

[0374] The system receives a fourth response from a third network element corresponding to the second IoT reader, the fourth response being used to indicate the result of the second IoT reader's action on the IoT device.

[0375] In some embodiments, the operation request or the fourth response includes information from the second IoT reader.

[0376] Figure 4 is a flowchart illustrating an information method according to an embodiment of the present disclosure. As shown in Figure 4, the embodiment of the present disclosure relates to a method for determining a start time, the method including:

[0377] In step S4101, AF sends an inventory / command request to NEF.

[0378] In some embodiments, the inventory / command request is similar to the operation request in the embodiments described above.

[0379] Optionally, the AF sends a service request to the NEF, which includes an AIOT service request message and parameters to determine the target AIOT device, the target reader / writer, and service operation-specific parameters. The AIOT service request message includes: a manifest message and a command message.

[0380] This service request is similar to the fourth request in the above embodiments. The target AIoT device is similar to the external device identifier of the aforementioned IoT device, the target reader is similar to the external reader identifier of the aforementioned IoT reader, and the service operation specific parameters are similar to the aforementioned external operation parameters.

[0381] In step S4102, NEF selects AIOTF.

[0382] In some embodiments, NEF determines an AIOTF for the requested operation.

[0383] Optionally, NEF converts the external target AIoT device ID, target reader ID, and service operation-specific parameters into internal target AIoT device ID, target reader ID, and service operation-specific parameters. For example, NEF further transfers the external region to the internal region (e.g., AoI, Region of Interest), which includes a cell ID or a list of TAIs.

[0384] The internal target AIoT device ID is similar to the device identifier of the aforementioned IoT device, and the target reader ID is similar to the reader identifier of the aforementioned IoT reader.

[0385] Optionally, based on the transmitted parameters and service request message, NEF determines an AIOTF for the requested operation.

[0386] Step S4103: NEF sends Nnef_AIoT_inventory / command request(inventory / command request(AoI)) to AIOTF.

[0387] The Nnef_AIoT_inventory / command request is similar to the third request in the above embodiments.

[0388] Optionally, NEF invokes a new service operation on AIOTF, such as an Nnef_AIoT_inventory request or an Nnef_AIoT_command request. This message includes the target AIoT device ID to be received or mapped, the target reader ID, and service operation-specific parameters, as well as an inventory / command message. Additionally, the region being passed (e.g., AOI) is also included in the Nnef_AIoT_inventory / command request.

[0389] Step S4104: AIOTF sends Nnrf_NFDiscovery_Request (AoI / target TAI, AMF indication) to NRF.

[0390] In some embodiments, based on the received target TAI or AoI, the AIOTF invokes the Nnrf_NFDiscovery_Request service operation to the NRF to discover the AMF that provides services for the area of ​​interest.

[0391] Optionally, Nnrf_NFDiscovery_Request(AoI / target TAI, AMF indicator) is similar to the first request in the above embodiments.

[0392] In step S4105, NRF sends Nnrf_NFDiscovery_Response(AMF ID list) to AIOTF.

[0393] In some embodiments, the NRF provides the AIOTF with a list of AMF IDs (e.g., a list of GUAMIs) in the response message based on the region provided by the AIOTF.

[0394] In some embodiments, Nnrf_NFDiscovery_Response is similar to the first response.

[0395] In step S4106, AIOTF sends a Namf_EventExposure_Subscribe Request to AMF.

[0396] In some embodiments, the Namf_EventExposure_Subscribe Request includes parameters for event exposure and optionally includes a reader / writer functionality indication to indicate that the AMF also provides reader / writer functionality in the response message.

[0397] Optionally, the Event Reporting Target = "any UE", Event ID = "UE in / out of interest area" / "UE moving in / out of interest area" indicates whether the UE is in the area, and can be combined with another event Event ID = "Reachability Filter" to indicate whether the UE is reachable.

[0398] The Namf_EventExposure_Subscribe Request is similar to the second request mentioned above.

[0399] In some embodiments, the AIOTF may send a request to the AMF to obtain the readers available in the AoI / target TAI and may choose to use their features.

[0400] Optionally, the Namf_UEinfo Request includes the AoI / target TAI, an AIOT reader capability indication.

[0401] The Namf_UEinfo Request is similar to the second request mentioned above.

[0402] In step S4107, AMF sends Namf_EventExposure_Subscribe ReSponse to AIOTF.

[0403] In some embodiments, a list of SUPIs in the region of interest. If reader / writer capabilities are also included, AIoT reader / writer capabilities for each terminal in the terminal list are also provided.

[0404] Among them, Namf_EventExposure_Subscribe ReSponse includes the SUPI list and AIOT reader / writer functionality.

[0405] In some embodiments, after subscription, AMF will also notify AIOTF when an event subscribed to by AIOTF occurs.

[0406] AMF sends a Namf_EventExposure_Subscribe Notify to AIOTF, including SUPI and the event ID.

[0407] Step S4108, AIOTF selects the reader / writer.

[0408] In some embodiments, AIOTF performs initial reader selection based on parameters received from NEF in the command / catalog and the reader ID (AIOT reader functionality provided by AMF).

[0409] Step S4109, AIOTF identifies the AIOT device.

[0410] In some embodiments, the AIOTF determines A-IoT device identification information based on information from the AF, which is included in a paging message on the AIoT radio interface to locate the AIoT device.

[0411] In step S4110, AIOTF sends a Namf_Communication_N1N2MessageTransfer request (inventory / command request) to AMF.

[0412] In some embodiments, the Namf_Communication_N1N2MessageTransfer request is similar to the first message described above.

[0413] In step S4111, the AMF sends either N1 message or N2 message to the AIOT reader / writer.

[0414] In some embodiments, for a UE reader, N1 message or N2 message is a NAS message, such as a DL NAS transfer message, and an inventory request / command request is a container (e.g., an AIOT container). For a RAN node reader, N1 message or N2 message is a new NGAP message.

[0415] In some embodiments, the N1 message or N2 message is similar to an operation request sent by a third network element to a second IoT reader.

[0416] In step S4112, the AIOT reader sends out the received inventory request / command request and obtains a response from the AIOT device.

[0417] In step S4113, the AIOT reader sends either N1 message or N2 message to the AMF.

[0418] In some embodiments, the N1 message or N2 message is similar to the fifth response sent by the second IoT reader to the third network element.

[0419] In some embodiments, the AIOT reader sends the inventory response / command response, along with the received associated ID / routing ID and / or notification associated ID, to the AMF.

[0420] For UE readers, the message is a NAS message, such as a UL NAS TRANSPORT message, in which the inventory response / command response is contained within a container. For RAN node readers, the message is a new NGAP message.

[0421] In step S4114, AMF sends a Namf_Communication_N1 / N2MessageNotify request to AIOTF.

[0422] The Namf_Communication_N1 / N2MessageNotify request is similar to the fourth response.

[0423] Optionally, for RAN nodes, the message is Namf_Communication_N2MessageNotify(Inventory Response / Command Response, Reader ID);

[0424] For the UE, the message is Namf_Communication_N1MessageNotify(Inventory Response / Command Response, Reader ID).

[0425] In step S4115, AIOTF sends an Nnef_AIoT_inventory / command response to NEF.

[0426] The Nnef_AIoT_inventory / command response is similar to the third response.

[0427] In step S4116, NEF sends an inventory / command response to AF.

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

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

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

[0431] Figure 5A is a schematic diagram of the structure of the first network element proposed in an embodiment of this disclosure. The first network element 5100 is used to perform any of the above methods. In some embodiments, as shown in Figure 5A, the first network element 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is used to send a first request to a second network element, the first request being used to request network element information of a third network element providing services in a first area, the second network element being used to store network element information of at least one network element; and to receive a first response sent by the second network element, the first response including network element information of at least one third network element providing services in the first area.

[0432] Figure 5B is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure. The second network element 5200 is used to perform any of the above methods. In some embodiments, as shown in Figure 5B, the second network element 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to receive a first request sent by a first network element, the first request being used to request network element information of a third network element providing services in a first area, the first network element being used to manage IoT devices; and to send a first response to the first network element, the first response including network element information of at least one third network element providing services in the first area.

[0433] Figure 5C is a schematic diagram of the structure of the second network element proposed in an embodiment of this disclosure. The third network element 5300 is used to perform any of the above methods. In some embodiments, as shown in Figure 5C, the third network element 5300 may include at least one of a transceiver module 5301, a processing module 5302, etc. In some embodiments, the transceiver module 5301 is used to receive a second request sent by the first network element, the second request being used to request information on IoT readers available in the first area; and to send a second response to the first network element, the second response including information on at least one first IoT reader.

[0434] Optionally, the transceiver module described above is used to perform at least one of the communication steps such as sending and / or receiving performed by the terminal in any of the above methods, which will not be elaborated here. Optionally, the processing module described above is used to perform at least one of the other steps performed by the terminal in any of the above methods, which will not be elaborated here.

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

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

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

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

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

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

[0441] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.

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

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

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

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

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

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

[0448] The first network element obtains network element information of at least one third network element by requesting a third network element to provide services within the first area. This ensures that at least one obtained third network element can provide services within the first area, improving the accuracy of the obtained third network element information and the accuracy of subsequent operations performed on IoT devices through the third network element, thereby ensuring the stability of the IoT system. Furthermore, in the above embodiment, by sending a second request to the target third network element to request information on IoT readers / writers available within the first area, information on at least one first IoT reader / writer can be obtained, ensuring the accuracy of the obtained first IoT reader / writer information and thus improving the accuracy of subsequent selection of IoT readers / writers to perform operations on IoT devices.

Claims

1. A communication method, characterized in that, The method is executed by a first network element, which is used to manage IoT devices, and the method includes: Send a first request to the second network element, the first request being used to request network element information of a third network element providing services in the first area, the second network element being used to store network element information of at least one network element; The system receives a first response sent by the second network element, the first response including network element information of at least one third network element providing services in the first area.

2. The method according to claim 1, characterized in that, The first request includes at least one of the following: The region information of the first region; The first indication information is used to indicate that the network element information requested by the first request is the network element information of a third network element.

3. The method according to claim 1 or 2, characterized in that, The first response includes a network element list, which includes network element information of the at least one third network element.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Send a second request to the target third network element, the second request being used to request information on IoT readers available in the first area; The system receives a second response from the target third network element, the second response including information from at least one first IoT reader / writer; wherein the target third network element is one or more of the at least one third network element mentioned in the first response.

5. The method according to claim 4, characterized in that, The second request includes at least one of the following: Regional information, wherein the regional information is used to indicate the first region; The second instruction information is used to request the capabilities supported by the IoT reader / writer; Event information, which indicates the event that triggers the sending of the second response.

6. The method according to claim 4 or 5, characterized in that, The second response includes at least one of the following: Information from the first IoT reader / writer; The capabilities supported by the first IoT reader / writer.

7. The method according to any one of claims 4 to 6, characterized in that, The method further includes: The third request is received from a fourth network element, which requests to perform an operation on an IoT device in the first area. The fourth network element is used for network opening. A third response is sent to the fourth network element, the third response being used to indicate the result of the operation performed by the IoT reader on the IoT device.

8. The method according to claim 7, characterized in that, After receiving the second response sent by the target third network element, the method further includes: Based on the information of the IoT reader included in the second response and the third request, a second IoT reader that meets the conditions is selected from at least one first IoT reader included in the second response; wherein, the second IoT reader refers to the IoT reader corresponding to the information included in the third request.

9. The method according to claim 7 or 8, characterized in that, The third request includes at least one of the following: The device identifier of the IoT device; Information from IoT readers; The region information of the first region; An operation request, which instructs the IoT reader to perform an operation on an IoT device.

10. The method according to any one of claims 7 to 9, characterized in that, The method further includes: Send a first message to the third network element corresponding to the second IoT reader / writer. The first message includes an operation request, which is used to instruct the second IoT reader / writer to perform an operation on the IoT device. The system receives a fourth response from a third network element corresponding to the second IoT reader / writer, the fourth response being used to indicate the result of the second IoT reader / writer's action on the IoT device.

11. The method according to claim 10, characterized in that, The first message or the fourth response includes information about the second IoT reader.

12. A communication method, characterized in that, The method is executed by a second network element, which stores network element information of at least one network element. The method includes: Receive a first request sent by a first network element, the first request being used to request network element information of a third network element providing services in a first area, the first network element being used to manage IoT devices; Send a first response to the first network element, the first response including network element information of at least one third network element providing services in the first area.

13. The method according to claim 12, characterized in that, The first request includes at least one of the following: The region information of the first region; The first indication information is used to indicate that the network element information requested by the first request is the network element information of a third network element.

14. The method according to claim 12 or 13, characterized in that, The first response includes a network element list, which includes network element information of at least one third network element.

15. A communication method, characterized in that, The method is executed by a third network element, which provides services within a first area, and the method includes: Receive a second request sent by a first network element, the second request being used to request information on IoT readers available in the first area; Send a second response to the first network element, the second response including information from at least one first IoT reader / writer.

16. The method according to claim 15, characterized in that, The second request includes at least one of the following: Regional information, wherein the regional information is used to indicate the first region; The second instruction information is used to request the capabilities supported by the IoT reader / writer; Event information, which indicates the event that triggers the sending of the second response.

17. The method according to claim 15 or 16, characterized in that, The second response includes at least one of the following: Information from the first IoT reader / writer; The capabilities supported by the first IoT reader / writer.

18. The method according to any one of claims 17 to 19, characterized in that, The method further includes: The system receives a first message sent by the first network element. The first message includes an operation request, which is used to instruct the second IoT reader to perform an operation on the IoT device. The operation command is used to instruct the IoT reader to perform an operation on the IoT device. A fourth response is sent to the first network element, the fourth response being used to indicate the result of the second IoT reader / writer's action on the IoT device.

19. The method according to claim 18, characterized in that, The first message or the fourth response includes information about the second IoT reader.

20. The method according to claim 18 or 19, characterized in that, The method further includes: Send the operation request to the second IoT reader; The system receives a fifth response sent by the second IoT reader, the fifth response being used to indicate the result of the second IoT reader's action on the IoT device.

21. A communication device, wherein, The communication device is used to perform the method according to any one of claims 1 to 11, or any one of claims 12 to 14, or any one of claims 15 to 20.

22. An Internet of Things (IoT) system, comprising a first network element, a second network element, and a third network element, wherein, The first network element is configured to implement the method as described in any one of claims 1 to 11; The second network element is configured to implement the method as described in any one of claims 12 to 14; The third network element is configured to implement the method as described in any one of claims 15 to 20.

23. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1 to 11, or any one of claims 12 to 14, or any one of claims 15 to 20.

24. A program product comprising at least one of a program and instructions, wherein, When at least one of the programs or instructions is executed by the communication device, it implements the method as described in any one of claims 1 to 11, or any one of claims 12 to 14, or any one of claims 15 to 20.

Images