Label operation method, network element, storage medium and computer program product
By simplifying the process in the core network and using query and operation requests between network elements, the problem of missing standard technical processes for the integration of passive IoT devices and core networks is solved, and the deep integration of passive IoT devices and core networks is achieved. and the reduction in resource overhead.
Patent Information
- Application Number
- CN202410517122.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-04-26
- Publication Date
- 2024-11-08
AI Technical Summary
In the prior art, there is a lack of standard technical processes for core networks and passive IoT tags, and the low-complexity terminal capabilities of passive IoT tags are difficult to adapt to the existing core network mechanism, resulting in high resource overhead.
By sending query requests and operation requests between the first network element and the third network element, using the second network element and the fourth network element to perform access management and operation of passive IoT devices, simplifying the core network process and reducing resources Overhead and adaptable to the low-complexity terminal capabilities of passive IoT devices.
It realizes the deep integration of passive IoT devices and core networks, simplifies the core network process, reduces resource overhead, adapts to the low-complexity terminal capabilities of passive IoT devices, and promotes passive IoT technology and core networks. deep fusion.
Smart Images

Figure CN118921643A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of core networks, and specifically to a label operation method, a network element, a storage medium, and a computer program product. Background Art
[0002] Passive IoT tags can work normally without power or battery support. These devices can absorb Radio Frequency Identification (RFID) signals from base stations or readers and use this signal for simple processing to respond to requests or send back information. At present, there is no standard technical process for the integration of core network and passive IoT tags in related technologies. In addition, passive IoT tags include inventory, reading, writing, deactivation and other operations. Due to the weak capabilities of tags, the existing mechanisms of the core network need to be simplified to adapt to the low-complexity terminal capabilities of passive IoT. Summary of the invention
[0003] In view of this, embodiments of the present application provide a label operation method, a network element, a storage medium, and a computer program product.
[0004] The technical solution of the embodiment of the present application is implemented as follows:
[0005] On the one hand, an embodiment of the present application provides a label operation method, which is applied to a first network element, and the method includes:
[0006] Based on the first operation request for the passive Internet of Things device sent by the application function network element, a query request for a third network element corresponding to the passive Internet of Things device is sent to the second network element, where the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or read-write device associated with the passive Internet of Things device;
[0007] Sending a second operation request for the passive Internet of Things device to the queried third network element, so that the third network element sends the third operation request to the passive Internet of Things device through the read-write device;
[0008] Receive a response message sent by the third network element, where the response message is a response message of the passive Internet of Things device sent by the read-write device and received by the third network element;
[0009] Return the response message to the application function network element.
[0010] In the above solution, after sending a query request of a third network element corresponding to the passive Internet of Things device to the second network element, the method further includes:
[0011] A query request for the second network element is sent to a fourth network element, where the fourth network element stores the second network element to which the first network element is connected when it is registered.
[0012] In the above solution, before sending a query request of the third network element corresponding to the passive Internet of Things device to the second network element, the method further includes:
[0013] Sending a legitimacy verification request for the application function network element and the passive Internet of Things device to the second network element;
[0014] If the legitimacy verification is passed, a query request for the third network element corresponding to the passive Internet of Things device is sent to the second network element.
[0015] In the above solution, the method further includes:
[0016] Based on the fifth network element receiving the first operation request, the first network element is determined by the fifth network element
[0017] On the other hand, an embodiment of the present application further provides a label operation method, which is applied to a third network element, including:
[0018] Receiving a query request sent by the first network element based on a first operation request for a passive Internet of Things device sent by an application function network element, wherein the query request is used to query a third network element corresponding to the passive Internet of Things device, and the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or read-write device associated with the passive Internet of Things device;
[0019] The queried third network element is returned to the first network element.
[0020] In the above solution, before receiving the query request sent by the first network element based on the first operation request for the passive Internet of Things device sent by the application function network element, the method further includes:
[0021] Receive a legitimacy verification request for the application function network element and the passive Internet of Things device sent by the first network element.
[0022] In the above solution, the method further includes:
[0023] Receive an update request sent by a third network element, where the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or a third network element and / or a read-write device associated with the passive Internet of Things device that is not related to the first operation request.
[0024] On the other hand, an embodiment of the present application further provides a label operation method, which is applied to a third network element, including:
[0025] receiving a second operation request for a passive Internet of Things device sent by a first network element; the third network element is obtained by the first network element from a second network element, and the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or the read-write device associated with the passive Internet of Things device;
[0026] Based on the second operation request, sending a third operation request to the passive Internet of Things device through a read-write device;
[0027] Receiving a response message of the passive Internet of Things device sent by a read-write device;
[0028] Send the response message to the first network element.
[0029] In the above solution, the method further includes:
[0030] Based on the response message, an update request is sent to the second network element, where the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or a third network element and / or a read-write device associated with the passive Internet of Things device that is not related to the first operation request.
[0031] On the other hand, an embodiment of the present application provides a network element, comprising: a processor and a memory for storing a computer program that can be run on the processor, wherein:
[0032] The processor is used to execute the steps of the label operation method described in the embodiment of the present application when running a computer program.
[0033] On the other hand, an embodiment of the present application provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the label operation method described in the embodiment of the present application are implemented.
[0034] On the other hand, an embodiment of the present application provides a computer program product, including a computer program, which implements the steps of the label operation method described in the embodiment of the present application when executed by a processor.
[0035] The first network element of the embodiment of the present application sends a query request for the third network element corresponding to the passive Internet of Things device to the second network element based on the first operation request for the passive Internet of Things device sent by the application function network element. The third network element is used for access management of the passive Internet of Things device, and the second network element stores the third network element and / or read-write device associated with the passive Internet of Things device. Send a second operation request for the passive Internet of Things device to the queried third network element, so that the third network element sends the third operation request to the passive Internet of Things device through the read-write device, receives a response message sent by the third network element, and the response message is the response message of the passive Internet of Things device sent by the read-write device received by the third network element, and returns the response message to the application function network element. The embodiment of the present application provides a standard technical process for the integration of passive Internet of Things devices and core networks, simplifies the core network process and reduces the resource overhead of the core network, can adapt to the low-complexity terminal capabilities of passive Internet of Things devices, and promote the deep integration of passive Internet of Things technology and the core network. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] Figure 1 It is a schematic diagram of the principles of traditional ultra-high frequency radio frequency identification (RFID) and passive Internet of Things (Passive IoT) in related technologies;
[0037] Figure 2 It is a schematic diagram of the RFID inventory process in the related art;
[0038] Figure 3 is a schematic diagram of a label operation method provided in an embodiment of the present application;
[0039] Figure 4 is a schematic diagram of another tag operation method provided in an embodiment of the present application;
[0040] Figure 5 is a schematic diagram of another tag operation method provided in an embodiment of the present application;
[0041] Figure 6 is a schematic diagram of a label operation process provided by an embodiment of the present invention;
[0042] Figure 7 is a schematic diagram of another tag operation process provided by an embodiment of the present invention;
[0043] Figure 8 A schematic diagram of the structure of a network element provided in an embodiment of the present application. DETAILED DESCRIPTION
[0044] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0045] It should be understood that the passive IoT terminal in the embodiment of the present application refers to a passive IoT device or an ambient IoT device (Ambient IoT Device). The passive IoT terminal includes but is not limited to: passive devices based on the backscattering principle (for example, passive tags), semi-passive devices based on the backscattering principle (for example, semi-passive tags) and active communication devices with power consumption at the level of hundreds of microwatts; IoT devices with power consumption at the level of hundreds of microwatts can also be called ultra-low power consumption terminals. It can be understood that the tag is only one form of the IoT terminal. Those skilled in the art can understand that the passive IoT terminal is not limited to the tag form. The ultra-low power consumption terminal can be a passive tag, a tag with active reporting capability, or other communication devices based on radio frequency energy harvesting technology, backscattering technology, low-power computing technology, etc. The power consumption of the ultra-low power consumption terminal is at or below the level of hundreds of microwatts.
[0046] Passive IoT is a low-cost, low-power IoT technology based on passive tags. Currently, there is a certain demand in industry and application. Figure 1 As shown, Figure 1 This is a schematic diagram of the principles of traditional ultra-high frequency radio frequency identification (RFID) and Passive IoT. The differences in their business experience and market expansion can be found in Table 1.
[0047]
[0048] Table 1
[0049] In related technologies, the RFID inventory process is as follows: Figure 2 As shown, including:
[0050] 1) The reader selects the inventory tag through the Select command.
[0051] 2) The Reader starts an inventory cycle through the Query command (inventory naming). An inventory cycle can inventory all tags selected by the Select command. The first command of the inventory cycle is Query, and the subsequent commands are QueryRep or QueryAdjust. The inventory command can carry a Q value, which is used by the tag to generate a random number for the Q bit. The tag determines whether to respond to Query / QueryRep / QueryAdjust based on the random number.
[0052] 3) If the tag responds to the inventory command, the tag selects a 16-bit random number RN and sends RN to the reader.
[0053] 4) If the card reader receives RN, the card reader sends an Ack response carrying the RN.
[0054] 5) The tag matches the RN in the Ack with the RN sent previously. If they are the same, the random access process is successful. The tag now successfully establishes a connection with the reader and sends the EPC.
[0055] 6) The card reader can perform subsequent operations on the tag, such as reading information from the tag or writing information to the tag, authenticating the tag, etc.
[0056] 7) After completing the operation of the tag, the card reader repeats steps 2-6 to read and write the next tag.
[0057] Passive IoT tags usually include operations such as inventory, reading, writing, and deactivation. There is currently no standard technical process for integrating the core network with passive IoT tags in related technologies. Due to the weak capabilities of the tags, the existing mechanisms of the core network need to be simplified to adapt to the low-complexity terminal capabilities of passive IoT.
[0058] In view of the shortcomings of the above-mentioned related technologies, an embodiment of the present invention provides a tag operation method. In order to illustrate the technical solution of the present invention, a specific embodiment is used for description below.
[0059] Figure 3 The present invention provides a flowchart of a method for implementing a label operation, wherein the execution subject of the label operation method is a first network element, which may be a network exposure function (NEF) network element or a session management function (SMF) network element. Figure 3 , label operation methods include:
[0060] S301, based on a first operation request for a passive Internet of Things device sent by an application function network element, a query request for a third network element corresponding to the passive Internet of Things device is sent to a second network element, wherein the third network element is used for access management of the passive Internet of Things device; the second network element stores a third network element and / or a read-write device associated with the passive Internet of Things device.
[0061] Among them, the application function (AF) network element can determine that the tag / tag group can use the low-mobility data delivery process based on the current service ID, slice, deep-learning neural network (DNN), external identifier, external group identifier, etc., then the AF initiates a first operation request to the first network element, and the first operation request can be an inventory / read / write / deactivation request for passive IoT devices. When the AF initiates an inventory read / write operation, it will specify a tag, which is generally based on the tag code number and tag group number inside the network.
[0062] After receiving the first operation request sent by AF, the first network element initiates a query request of the third network element to the second network element. Here, the second network element can be a unified data management function (UDM) network element or an authentication server function (AUSF) network element. The third network element can be an access and mobility management function (AMF) network element or an artificial intelligence & Internet of Things management function (AIoTMF).
[0063] The second network element stores a third network element and / or a read-write device associated with the passive IoT device. For example, the first network element initiates an AMF / AIoTMF query request to UDM / AUSF, and UDM / AUSF returns the AMF / AIoTMF where the current tag is stored, as well as the tag movement range signed by the tag when it is issued.
[0064] Among them, the second network element is the tag network location management network element (which can be UDM / AUSF, can be jointly set up with AMF / AIoTMF, or can be a dedicated new network element), which can sign a contract for the tag movement range. AMF / AIoTMF can report the tag network location for each inventory, and can also report the tag network location to UDM / AUSF in batches.
[0065] S302: Send a second operation request for the passive Internet of Things device to the queried third network element, so that the third network element sends the third operation request to the passive Internet of Things device through a read-write device.
[0066] For example, the queried third network element may be one or more AMF / AIoTMFs (the operation instructions may be issued first according to the AMF / AIoTMF returned by the second network element. If the operation instructions cannot be executed normally, the operation range of the AMF / AIoTMF set may be gradually expanded until the maximum tag movement range of the contract is reached). The second operation request corresponds to the first operation request. If the first operation request is an inventory / read / write / deactivation request, the second operation request is also an inventory / read / write / deactivation request.
[0067] After receiving the second operation request, the third network element sends the third operation request to the passive IoT device through the read / write device. For example, the read / write device may be a radio access network (RAN) / reader, and the AMF / AIoTMF sends an inventory / read / write / deactivation request to one / multiple tags through one / multiple RAN / Readers.
[0068] The first operation request, the second operation request and the third operation request are all corresponding. For example, if the first operation request is an inventory request, the second operation request and the third operation request are also inventory requests.
[0069] S303: Receive a response message sent by the third network element, where the response message is a response message of the passive Internet of Things device sent by the read-write device and received by the third network element.
[0070] After receiving the third operation request, the passive Internet of Things device sends a response message to the read-write device, the read-write device sends the response message to the third network element, and the third network element sends the response message to the first network element.
[0071] S304: Return the response message to the application function network element.
[0072] The first network element returns the response message to the application function network element to complete the label operation process.
[0073] The first network element of the embodiment of the present application sends a query request for the third network element corresponding to the passive Internet of Things device to the second network element based on the first operation request for the passive Internet of Things device sent by the application function network element. The third network element is used for access management of the passive Internet of Things device, and the second network element stores the third network element and / or read-write device associated with the passive Internet of Things device. Send a second operation request for the passive Internet of Things device to the queried third network element, so that the third network element sends the third operation request to the passive Internet of Things device through the read-write device, receives a response message sent by the third network element, and the response message is the response message of the passive Internet of Things device sent by the read-write device received by the third network element, and returns the response message to the application function network element. The embodiment of the present application provides a standard technical process for the integration of passive Internet of Things devices and core networks, simplifies the core network process and reduces the resource overhead of the core network, can adapt to the low-complexity terminal capabilities of passive Internet of Things devices, and promote the deep integration of passive Internet of Things technology and the core network.
[0074] In one embodiment, after sending a query request of a third network element corresponding to the passive Internet of Things device to the second network element, the method further includes:
[0075] A query request for the second network element is sent to a fourth network element, where the fourth network element stores the second network element to which the first network element is connected when it is registered.
[0076] Here, the fourth network element may be a Network Repository Function (NRF) network element, in which the UDM / AUSF connected when the first network element is registered is stored.
[0077] In one embodiment, before sending a query request of a third network element corresponding to the passive Internet of Things device to the second network element, the method further includes:
[0078] Sending a legitimacy verification request for the application function network element and the passive Internet of Things device to the second network element;
[0079] If the legitimacy verification is passed, a query request for the third network element corresponding to the passive Internet of Things device is sent to the second network element.
[0080] For example, the first network element initiates AF and tag legitimacy verification to UDM / AUSF. If the verification is successful, it initiates an AMF / AIoTMF query request to UDM / AUSF.
[0081] In one embodiment, the method further comprises:
[0082] The first operation request is received based on a fifth network element, where the first network element is determined by the fifth network element.
[0083] For example, the first network element is SMF, the fifth network element is UPF, AF initiates an inventory / read / write / deactivation request to UPF, UPF randomly selects or searches for SMF based on configuration, and SMF initiates an AMF / AIoTMF query request to UDM / AUSF.
[0084] The embodiment of the present application also provides a label operation method, which is applied to a second network element, and the second network element may be a UDM / AUSF, such as Figure 4 As shown, the method includes:
[0085] Step 401, receiving a query request sent by a first network element based on a first operation request for a passive Internet of Things device sent by an application function network element, wherein the query request is used to query a third network element corresponding to the passive Internet of Things device, and the third network element is used for access management of the passive Internet of Things device; the second network element stores a third network element and / or a read-write device associated with the passive Internet of Things device.
[0086] Among them, the first network element can be SMF / NEF. After receiving the first operation request sent by AF, the first network element initiates a query request for the third network element to the second network element. The second network element can be UDM / AUSF, and the third network element can be AMF / AIoTMF.
[0087] Step 402: Return the queried third network element to the first network element.
[0088] The second network element returns the queried third network element to the first network element, for example, UDM / AUSF returns the AMF / AIoTMF where the current tag is stored.
[0089] In one embodiment, before receiving the query request sent by the first network element based on the first operation request for the passive Internet of Things device sent by the application function network element, the method further includes:
[0090] Receive a legitimacy verification request for the application function network element and the passive Internet of Things device sent by the first network element.
[0091] The first network element initiates AF and tag legitimacy verification to UDM / AUSF. If the verification passes, the first network element initiates an AMF / AIoTMF query request to UDM / AUSF.
[0092] In one embodiment, the method further comprises:
[0093] Receive an update request sent by a third network element, where the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or a third network element and / or a read-write device associated with the passive Internet of Things device that is not related to the first operation request.
[0094] After receiving the response message sent by the passive IoT device through the read-write device, the third network element updates the network location information of the passive IoT device to the second network element. Here, the network location information refers to the third network element and / or read-write device associated with the passive IoT device, that is, the third network element and / or read-write device connected to the passive IoT device.
[0095] For example, AMF / AIoTMF updates the network location information of tags in batches to UDM / AUSF (obtaining tag identity authentication information from the tag side, including all tag information in the coverage area). When performing inventory / read / write / deactivation operations, other unrelated tags will also respond. After receiving the responses, AMF / AIoTMF can directly update the network location information of the operated tags, and update the network location information of unrelated tags to UDM / AUSF based on the policy.
[0096] The embodiment of the present application also provides a tag operation method, which is applied to a third network element, and the third network element may be AMF / AIoTMF, such as Figure 5 As shown, the method includes:
[0097] Step 501, receiving a second operation request for a passive Internet of Things device sent by a first network element; the third network element is obtained by the first network element from a second network element, and the third network element is used for access management of the passive Internet of Things device; the second network element stores a third network element and / or a read-write device associated with the passive Internet of Things device.
[0098] For example, the first network element sends an inventory / read / write / deactivation request to one or more AMF / AIoTMFs. It can first send an operation instruction based on the AMF / AIoTMF returned by UDM / AUSF. If it cannot be executed normally, the operation range of the AMF / AIoTMF set can be gradually expanded to the maximum range of the contracted tag movement.
[0099] Step 502: Based on the second operation request, a third operation request is sent to the passive Internet of Things device through a read-write device.
[0100] For example, AMF / AIoTMF sends inventory / read / write / deactivation requests to one / multiple tags through one / multiple RAN / Readers.
[0101] Step 503: Receive a response message from the passive Internet of Things device sent by the read-write device.
[0102] Step 504: Send the response message to the first network element.
[0103] The tag returns an inventory / read / write / deactivation response to the RAN / Reader, the RAN / Reader sends the response message to the AMF / AIoTMF, the AMF / AIoTMF returns the response message to the first network element, and the first network element returns the response message to the AF.
[0104] In one embodiment, the method further comprises:
[0105] Based on the response message, an update request is sent to the second network element, where the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or a third network element and / or a read-write device associated with the passive Internet of Things device that is not related to the first operation request.
[0106] After receiving the response message from the passive IoT device, the third network element updates the network location information of the passive IoT device to the second network element. Here, the network location information refers to the third network element and / or read-write device associated with the passive IoT device, that is, the third network element and / or read-write device connected to the passive IoT device.
[0107] like Figure 6 As shown, Figure 6 Schematic diagram of a label operation process provided by an embodiment of the present invention, including:
[0108] 0. AF determines that the label / label group can use the low mobility data delivery process based on the current service ID, slice, DNN, External Identifier, External Group Identifier, etc.
[0109] 1. AF initiates inventory / read / write / deactivate request to NEF.
[0110] 2. NEF initiates a UDM / AUSF query request to NRF.
[0111] 3.1. NEF initiates AF and tag legitimacy verification to UDM / AUSF.
[0112] 3.2. NEF initiates an AMF / AIoTMF query request to UDM / AUSF.
[0113] Get tag authentication information from NEF, including only the tag information that needs to be counted. UDM / AUSF returns the AMF / AIoTMF where the current tag is stored, and the tag movement range signed when the tag is issued.
[0114] 4. NEF sends inventory / read / write / deactivate requests to one or more AMF / AIoTMF.
[0115] You can first issue operation instructions based on the AMF / AIoTMF returned by UDM / AUSF. If it cannot be executed normally, you can gradually expand the operation range of the AMF / AIoTMF set to the maximum range of the contracted tag movement.
[0116] 5.1. AMF / AIoTMF sends inventory / read / write / deactivation requests to one / multiple tags through one / multiple RAN / Readers.
[0117] 5.2. The tag returns an inventory / read / write / deactivation response through RAN / Reader.
[0118] 6. AMF / AIoTMF updates the network location information of the tag to UDM / AUSF respectively (obtains the tag identity authentication information from the tag side, including all tag information in the coverage area). When performing inventory / read / write / deactivation operations, other unrelated tags will also respond. After receiving the response, AMF / AIoTMF can directly update the network location information of the operated tag, and update the network location information of unrelated tags to UDM / AUSF based on the policy.
[0119] 7. After AMF / AIoTMF or NEF confirms that there is no problem with the tag identity, it returns inventory / read / write / deactivation information to AF through NEF tag by tag or in batches.
[0120] like Figure 7 As shown, Figure 7 Schematic diagram of another tag operation process provided by an embodiment of the present invention, including:
[0121] 1. AF initiates inventory / read / write / deactivate requests to UPF.
[0122] 2. UPF randomly selects or searches for SMF based on configuration.
[0123] 3. SMF initiates a UDM / AUSF query request to NRF.
[0124] 4.1. SMF initiates AF and label legitimacy verification to UDM / AUSF.
[0125] 4.2. SMF initiates an AMF / AIoTMF query request to UDM / AUSF.
[0126] Get tag authentication information from NEF, including only the tag information that needs to be counted. UDM / AUSF returns the AMF / AIoTMF where the current tag is stored, and the tag movement range signed when the tag is issued.
[0127] 5. SMF sends inventory / read / write / deactivation requests to one or more AMF / AIoTMFs.
[0128] You can first issue operation instructions based on the AMF / AIoTMF returned by UDM / AUSF. If it cannot be executed normally, you can gradually expand the operation range of the AMF / AIoTMF set to the maximum range of the contracted tag movement.
[0129] 6.1. AMF / AIoTMF sends inventory / read / write / deactivation requests to one / multiple tags through one / multiple RAN / Readers.
[0130] 6.2. The tag returns an inventory / read / write / deactivation response through RAN / Reader.
[0131] 7. AMF / AIoTMF updates the network location information of the tag to UDM / AUSF respectively.
[0132] Obtain tag identity authentication information from the tag side, including all tag information in the coverage area. When performing inventory / read / write / deactivation operations, other unrelated tags will also respond. After receiving the response, AMF / AIoTMF can directly update the network location information of the operated tag, and update the network location information of unrelated tags to UDM / AUSF based on the policy.
[0133] 8. After AMF / AIoTMF or SMF / UPF confirms that there is no problem with the tag identity, it returns inventory / read / write / deactivation information to AF through SMF / UPF tag by tag or in batches.
[0134] Among them, AMF / AIoTMF can update the network location to UDM / AUSF in batches based on time, quantity, etc. The time granularity is, for example, 5 minutes or 10 minutes, and batch reports are made to UDM / AUSF after the time expires; the quantity granularity is, for example, after collecting 5 or 10, batch updates are made to UDM.
[0135] When performing inventory / read / write / deactivation operations, other unrelated tags will also respond. After receiving the responses, AMF / AIoTMF can directly update the network location information of the operated tags, and update the network location information of unrelated tags to UDM / AUSF based on the policies.
[0136] In 5GC, SMF / UPF and NEF can complete inventory / read / write / deactivation operations based on the designed process without the need for prior registration and PDU session establishment, and AMF / AIoTMF or SMF / UPF or NEF returns a message to AF after completing identity authentication based on the tag return message.
[0137] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.
[0138] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.
[0139] It should be noted that the technical solutions described in the embodiments of the present invention can be arbitrarily combined without conflict.
[0140] An embodiment of the present invention provides a label operation device, the device comprising:
[0141] A first sending module is used to send a query request for a third network element corresponding to the passive Internet of Things device to a second network element based on a first operation request for the passive Internet of Things device sent by the application function network element, wherein the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or the read-write device associated with the passive Internet of Things device;
[0142] A second sending module is used to send a second operation request for the passive Internet of Things device to the queried third network element, so that the third network element sends the third operation request to the passive Internet of Things device through the read-write device;
[0143] A first receiving module is used to receive a response message sent by the third network element, where the response message is a response message of the passive Internet of Things device sent by the read-write device and received by the third network element;
[0144] The third sending module is used to return the response message to the application function network element.
[0145] In one embodiment, the device further comprises:
[0146] The fourth sending module is used to send a query request of the second network element to a fourth network element, and the fourth network element stores the second network element connected when the first network element is registered.
[0147] In one embodiment, the device further comprises:
[0148] The fifth sending module is used to send a legitimacy verification request for the application function network element and the passive Internet of Things device to the second network element; if the legitimacy verification passes, a query request for the third network element corresponding to the passive Internet of Things device is sent to the second network element.
[0149] In one embodiment, the device further comprises:
[0150] The second receiving module is used to receive the first operation request based on a fifth network element, where the first network element is determined by the fifth network element.
[0151] The embodiment of the present invention further provides another label operation device, which includes:
[0152] A third receiving module is used to receive a query request sent by the first network element based on the first operation request for the passive Internet of Things device sent by the application function network element, wherein the query request is used to query the third network element corresponding to the passive Internet of Things device, and the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or the read-write device associated with the passive Internet of Things device;
[0153] The sixth sending module is used to return the queried third network element to the first network element.
[0154] In one embodiment, the device further comprises:
[0155] The fourth receiving module is used to receive a legitimacy verification request for the application function network element and the passive Internet of Things device sent by the first network element.
[0156] In one embodiment, the device further comprises:
[0157] The fifth receiving module is used to receive an update request sent by a third network element, where the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or the third network element and / or the read-write device associated with the passive Internet of Things device that is not related to the first operation request.
[0158] The embodiment of the present invention further provides another label operation device, which includes:
[0159] A sixth receiving module, configured to receive a second operation request for a passive Internet of Things device sent by a first network element; the third network element is obtained by the first network element from a second network element, and the third network element is used for access management of the passive Internet of Things device; the second network element stores a third network element and / or a read-write device associated with the passive Internet of Things device;
[0160] A seventh sending module, configured to send a third operation request to the passive Internet of Things device through a read-write device based on the second operation request;
[0161] A seventh sending module, used to receive a response message of the passive Internet of Things device sent by the reading and writing device;
[0162] An eighth sending module is used to send the response message to the first network element.
[0163] In one embodiment, the device further comprises:
[0164] The ninth sending module is used to send an update request to the second network element based on the response message, wherein the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or the third network element and / or the read-write device associated with the passive Internet of Things device that is not related to the first operation request.
[0165] In actual application, the first determination module, the second determination module, the third determination module and the fourth determination module can be implemented by a processor in the server, such as a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a programmable gate array (FPGA).
[0166] It should be noted that: when the device provided in the above embodiment performs label operation, only the division of the above modules is used as an example. In actual application, the above processing can be assigned to different modules as needed, that is, the internal structure of the device is divided into different modules to complete all or part of the processing described above. In addition, the device and method embodiments provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.
[0167] The above-mentioned device can be in the form of an image file, and after the image file is executed, it can be run in the form of a container or a virtual machine to implement the method described in this application. Of course, it is not limited to the image file form, as long as some software forms that can implement the method described in this application are within the scope of protection of this application.
[0168] Based on the hardware implementation of the above program module, and in order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a network element, and the above method is implemented by a processor of the network element. Figure 8 Only an exemplary structure of the network element is shown, not the entire structure, and can be implemented as needed. Figure 8 Partial or complete structure shown.
[0169] like Figure 8 As shown, the network element 800 provided in the embodiment of the present application includes: at least one processor 801, a memory 802 and a user interface 803. The various components in the network element 800 are coupled together through a bus system 804. It can be understood that the bus system 804 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 804 also includes a power bus, a control bus and a status signal bus. However, for the sake of clarity, Figure 8 Various buses are labeled as bus system 804 .
[0170] The user interface 803 may include a display, a keyboard, a mouse, a trackball, a click wheel, keys, buttons, a touch pad or a touch screen.
[0171] The memory 802 in the embodiment of the present application is used to store various types of data to support the operation of the network element. Examples of such data include: any computer program used to operate on the network element.
[0172] The label operation method of the network element disclosed in the embodiment of the present application can be applied to the processor 801, or implemented by the processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the label operation method of the network element can be completed by the hardware integrated logic circuit or software instructions in the processor 801. The above-mentioned processor 801 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 801 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 802. The processor 801 reads the information in the memory 802 and completes the steps of the label operation method of the network element provided in the embodiment of the present application in combination with its hardware.
[0173] In an exemplary embodiment, the network element 800 may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), field programmable gate array (FPGA), general purpose processor, controller, microcontroller (MCU), microprocessor, or other electronic components to execute the aforementioned method.
[0174] It can be understood that the memory 802 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), direct memory bus random access memory (DRRAM). The memory described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.
[0175] In an exemplary embodiment, the embodiment of the present application further provides a storage medium, namely a computer storage medium, which may be a computer-readable storage medium, for example, a memory 802 storing a computer program, and the computer program may be executed by a processor 801 of a network element 800 to complete the steps described in the method of the embodiment of the present application. The computer-readable storage medium may be a memory such as a ROM, a PROM, an EPROM, an EEPROM, a Flash Memory, a magnetic surface memory, an optical disk, or a CD-ROM.
[0176] In an exemplary embodiment, the embodiment of the present application further provides a computer program product, including a computer program, and the computer program can be executed by the processor 801 of the network element 800 to complete the steps of any of the aforementioned methods.
[0177] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0178] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.
[0179] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A label operation method, characterized in that: Applied to a first network element, the method includes: Based on the first operation request for the passive Internet of Things device sent by the application function network element, a query request for a third network element corresponding to the passive Internet of Things device is sent to the second network element, where the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or read-write device associated with the passive Internet of Things device; Sending a second operation request for the passive Internet of Things device to the queried third network element, so that the third network element sends the third operation request to the passive Internet of Things device through the read-write device; Receive a response message sent by the third network element, where the response message is a response message of the passive Internet of Things device sent by the read-write device and received by the third network element; Return the response message to the application function network element.
2. The method according to claim 1, characterized in that: After sending a query request of a third network element corresponding to the passive Internet of Things device to the second network element, the method further includes: A query request for the second network element is sent to a fourth network element, where the fourth network element stores the second network element to which the first network element is connected when it is registered.
3. The method according to claim 1, characterized in that Before sending a query request of a third network element corresponding to the passive Internet of Things device to the second network element, the method further includes: Sending a legitimacy verification request for the application function network element and the passive Internet of Things device to the second network element; If the legitimacy verification is passed, a query request for the third network element corresponding to the passive Internet of Things device is sent to the second network element.
4. The method according to claim 1, characterized in that: The method further comprises: The first operation request is received based on a fifth network element, where the first network element is determined by the fifth network element.
5. A label operation method, characterized in that: Applied to a second network element, the method includes: Receiving a query request sent by the first network element based on a first operation request for a passive Internet of Things device sent by an application function network element, wherein the query request is used to query a third network element corresponding to the passive Internet of Things device, and the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or read-write device associated with the passive Internet of Things device; The queried third network element is returned to the first network element.
6. The method according to claim 5, characterized in that Before receiving the query request sent by the first network element based on the first operation request for the passive Internet of Things device sent by the application function network element, the method further includes: Receive a legitimacy verification request for the application function network element and the passive Internet of Things device sent by the first network element.
7. The method according to claim 5, characterized in that The method further comprises: Receive an update request sent by a third network element, where the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or a third network element and / or a read-write device associated with the passive Internet of Things device that is not related to the first operation request.
8. A label operation method, characterized in that: Applied to a third network element, the method includes: receiving a second operation request for a passive Internet of Things device sent by a first network element; the third network element is obtained by the first network element from a second network element, and the third network element is used for access management of the passive Internet of Things device; the second network element stores the third network element and / or the read-write device associated with the passive Internet of Things device; Based on the second operation request, sending a third operation request to the passive Internet of Things device through a read-write device; Receiving a response message of the passive Internet of Things device sent by a read-write device; Send the response message to the first network element.
9. The method according to claim 8, characterized in that The method further comprises: Based on the response message, an update request is sent to the second network element, where the update request is used to update the passive Internet of Things device corresponding to the first operation request and / or a third network element and / or a read-write device associated with the passive Internet of Things device that is not related to the first operation request.
10. A network element, characterized in that: include: A processor and a memory for storing a computer program that can be executed on the processor, wherein: The processor, when used to run a computer program, executes the steps of the method described in any one of claims 1 to 4, or executes the steps of the method described in any one of claims 5 to 7, or executes the steps of the method described in any one of claims 8 to 9.
11. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method described in any one of claims 1 to 4 are implemented, or the steps of the method described in any one of claims 5 to 7 are implemented, or the steps of the method described in any one of claims 8 to 9 are implemented.
12. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 4, or implements the steps of the method according to any one of claims 5 to 7, or implements the steps of the method according to any one of claims 8 to 9.
Citation Information
Cited By
Communication methods and apparatus, and storage medium
WO2026152307A1
