Identifier updating method, communication equipment and storage medium

Abstract

The invention provides an identifier updating method, communication equipment and a storage medium. The identifier updating method applied to a first network element comprises the following steps: generating a new temporary identifier when an identifier updating condition is met; and sending the new temporary identifier to a first communication device, so that the first communication device updates the temporary identifier based on the new temporary identifier.

Description

Identifier update method, communication equipment and storage medium Technical Field

[0001] This application relates to the field of communication technology, specifically to an identifier update method, communication device, and storage medium. Background Technology

[0002] The Internet of Things (IoT) connects various physical objects to the internet through sensors and networked devices, enabling the automatic collection, transmission, and processing of information. In particular, Ambient IoT (AIoT), a key communication technology for IoT development, utilizes backscattering and environmental energy harvesting techniques to convert available signals and energy from the surrounding environment into electrical energy capable of driving its own circuitry. Simultaneously, it uses a backscattering-based communication mode to transmit information to target nodes. Therefore, it features low power consumption and low cost, making it widely applicable to various IoT scenarios.

[0003] Service operations on AIoT devices include inventory and command types; commands specifically include read, write, and disable. These operations require the AIoT device's identifier. Application Functions (AFs) carry the identifier of the targeted AIoT device when making service operation requests. This identifier is permanent and does not change after the AIoT device is enabled. Upon receiving a service operation request, the core network's AIOTF interacts with the readers (including base station readers and UE readers) and the corresponding AIoT device based on the AIoT device identifier in the request to complete the service operation process.

[0004] The permanent identifier of an AIoT device is considered privacy information and needs to be protected. One approach is to avoid using the permanent identifier during business operations, and instead use a temporary identifier assigned to the AIoT device to point to it; the temporary identifier is used to point to the AIoT device in business operation messages between AIOTF, the reader / writer, and the AIoT device.

[0005] The allocation, updating, and use of temporary identifiers for AIoT devices are technical issues that need to be addressed. Summary of the Invention

[0006] In view of this, embodiments of this application provide an identifier update method, communication device, and storage medium, which realize the effective update and use of temporary identifiers.

[0007] This application provides an identifier update method, applied to a first network element, including:

[0008] If the conditions for updating the identifier are met, a new temporary identifier is generated.

[0009] The new temporary identifier is sent to the first communication device so that the first communication device updates the temporary identifier based on the new temporary identifier.

[0010] This application provides an identifier update method, applied to a first communication device, including:

[0011] If the identifier update conditions are met, a new temporary identifier generated by the first network element will be received.

[0012] The temporary identifier is updated based on the new temporary identifier.

[0013] This application provides an identifier update device applied to a first network element, comprising:

[0014] The generation module is configured to generate a new temporary identifier if the identifier update conditions are met.

[0015] The sending module is configured to send the new temporary identifier to the first communication device so that the first communication device can update the temporary identifier based on the new temporary identifier.

[0016] This application provides an identifier updating device, applied to a first communication device, comprising:

[0017] The receiving module is configured to receive a new temporary identifier generated by the first network element when the identifier update conditions are met;

[0018] The update module is configured to update the temporary identifier based on the new temporary identifier.

[0019] This application provides a communication device, including: a memory, and one or more processors;

[0020] The memory is configured to store one or more programs;

[0021] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any of the above embodiments.

[0022] This application provides a storage medium storing a computer program, which, when executed by a processor, implements the methods described in any of the above embodiments. Attached Figure Description

[0023] Figure 1 is a schematic diagram of a network-connected AIoT device topology provided by the prior art;

[0024] Figure 2 is a schematic diagram of another network connection AIoT device topology provided by the prior art;

[0025] Figure 3 shows a system architecture that supports AIoT functionality provided by existing technology;

[0026] Figure 4 shows another system architecture that supports AIoT functionality provided by existing technologies;

[0027] Figure 5 is a flowchart of an identifier update method provided in an embodiment of this application;

[0028] Figure 6 is a flowchart of another identifier update method provided in an embodiment of this application;

[0029] Figure 7 is a schematic diagram of the update interaction of a temporary identifier provided in an embodiment of this application;

[0030] Figure 8 is a schematic diagram of another temporary identifier update interaction provided in an embodiment of this application;

[0031] Figure 9 is an interactive diagram illustrating a business operation using a temporary identifier, as provided in an embodiment of this application.

[0032] Figure 10 is an interactive schematic diagram of updating a temporary identifier during business operations provided in an embodiment of this application;

[0033] Figure 11 is a schematic diagram of the synchronous interaction of a temporary identifier provided in this application;

[0034] Figure 12 is a structural block diagram of an identifier updating device provided in an embodiment of this application;

[0035] Figure 13 is a structural block diagram of another identifier updating device provided in an embodiment of this application;

[0036] Figure 14 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0037] The embodiments of this application will be described below with reference to the accompanying drawings. The examples given are for illustrative purposes only and are not intended to limit the scope of this application.

[0038] Figure 1 is a schematic diagram of a network-connected AIoT device topology provided by the prior art; Figure 2 is a schematic diagram of another network-connected AIoT device topology provided by the prior art.

[0039] As shown in Figure 1, a base station reader (RAN Reader) connects to the AIoT device, acting as a reader to perform service operations on the AIoT device. The AIoT functions located in the core network manage and operate the AIoT device through the base station reader. In Figure 1, multiple base station readers may be connected to the same base station, which is connected to the core network. Messages from the core network to the base station readers are forwarded by the base stations serving these base station readers.

[0040] As shown in Figure 2, the User Equipment (UE) connects to the AIoT device and acts as a reader to perform business operations on the AIoT device; the AIoT function located in the core network connects to the UE reader through the base station to realize the management and business operations of the AIoT device.

[0041] Figure 3 shows a system architecture that supports AIoT functionality provided by existing technology; Figure 4 shows another system architecture that supports AIoT functionality provided by existing technology.

[0042] As shown in Figures 3 and 4, the management and service operations of AIoT devices are handled by the newly added AIoT Function (AIOTF) network element located in the core network. In addition to the newly added AIoTTF network element, other existing functional network elements, such as Unified Data Management (UDM), Authentication Server Function (AUSF), Network Exposure Function (NEF), and Network Repository Function (NRF), enhance their traditional functions for AIoT: UDM stores information related to AIoT devices or readers; ASF authenticates the UE's function as an AIoT reader; NEF receives and verifies service operation requests from the AF before forwarding them to the AIoTTF; and NRF stores information about the AIoTTF network element.

[0043] Figure 3 illustrates the scenarios for base station readers, including the architecture where the AIOTF is not directly connected to the base station reader (connected via Access Management Function (AMF)) and the architecture where the AIOTF is directly connected to the base station reader. Figure 4 illustrates the scenario for UE readers.

[0044] Business operations for AIoT devices include types such as inventory and command; among which commands specifically include read, write, and invalidate.

[0045] In the case of performing business operations on AIoT devices, a temporary identifier assigned to the AIoT device is used to point to the AIoT device; the temporary identifier is also used to point to the AIoT device in business operation messages between AIOTF, the reader / writer, and the AIoT device. This application provides a technical solution for updating and using the temporary identifier of an AIoT device.

[0046] This application proposes a method for updating passive IoT temporary identifiers. When the temporary identifier of an AIoT device needs to be updated, the AIOTF generates a new temporary identifier and sends a temporary identifier update command carrying the new temporary identifier to a reader (e.g., a base station reader or a UE reader). The reader then sends the new temporary identifier update command to the AIoT device, which updates its locally stored temporary identifier. The AIoT device sends a temporary identifier update success response to the reader, which forwards the response to the AIOTF.

[0047] This application also proposes a method for performing business operations using temporary identifiers of AIoT devices. Upon receiving a business operation request forwarded by NEF from AF, AIOTF locates the temporary identifier of the AIoT device based on the permanent identifier of the AIoT device in the business operation request. AIOTF uses the temporary identifier to interact with the reader / writer and the AIoT device to complete the business operation. AIOTF then uses the permanent identifier to return the business operation result to AF via NEF.

[0048] This application also proposes a method for updating the temporary identifier of an AIoT device during business operations. Upon receiving a business operation request forwarded by NEF from the AF, the AIOTF checks whether the temporary identifier of the AIoT device needs to be updated. If the validity period has expired, it decides to update the temporary identifier; otherwise, if the AIOTF uses a new temporary identifier for each business operation according to a policy, it also decides to update the temporary identifier. The AIOTF updates the temporary identifier in conjunction with the reader and the AIoT device. The AIOTF uses the new temporary identifier to interact with the reader and the AIoT device to complete the business operation. The AIOTF uses a permanent identifier to return the business operation result to the AF via NEF.

[0049] In one embodiment, Figure 5 is a flowchart of an identifier update method provided by an embodiment of this application. This embodiment is applied to the case of dynamically updating the temporary identifier of a passive Internet of Things (IoT) device. This embodiment can be executed by a first network element. As shown in Figure 5, this embodiment includes: S510-S520.

[0050] S510. If the conditions for updating the identifier are met, a new temporary identifier is generated.

[0051] In one example, the identifier update condition refers to the condition that indicates the original temporary identifier of the first communication device needs to be updated. When the first network element discovers that the original temporary identifier of the first communication device needs to be updated, the first network element can generate a new temporary identifier for the first communication device.

[0052] S520: Send a new temporary identifier to the first communication device so that the first communication device updates the temporary identifier based on the new temporary identifier.

[0053] In one example, the first network element can send a new temporary identifier to the first communication device through other devices, so that the first communication device can update the temporary identifier stored locally based on the new temporary identifier, that is, replace the original temporary identifier with the new temporary identifier to complete the temporary identifier update process.

[0054] In one embodiment, the identifier update condition includes one of the following: the validity period of the original temporary identifier expires; a service operation request is received, and a new temporary identifier is used for each service operation. In one example, the expiration of the validity period of the original temporary identifier means that the timer time of the original temporary identifier of the first communication device has expired, or the validity period has expired. In one example, the service operation request is used to request a service operation with the first communication device; the service operation may include types such as inventory and commands; commands may include types such as read, write, and invalidate. Using a new temporary identifier for each service operation means that the first communication device needs to use a new temporary identifier each time it performs a service operation. For the first network element, a new temporary identifier is set for each service operation with the first communication device: when the first network element receives a service operation request, the first network element automatically generates a new temporary identifier and sends the new temporary identifier to the first communication device, so that the first communication device updates its temporary identifier and uses the new temporary identifier for the service operation.

[0055] In one embodiment, when the second communication device is a first type of device, sending a new temporary identifier to the first communication device includes one of the following:

[0056] The second network element sends a temporary identifier update command carrying a new temporary identifier to the second communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

[0057] Send a temporary identifier update command carrying a new temporary identifier to the second communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

[0058] In one example, the second communication device refers to a reader / writer in AIoT; the second communication device can include both a first-type device and a second-type device. For example, the first-type device can be a base station reader / writer; the second-type device can be a UE reader / writer. In one example, in a scenario where the second communication node is a first-type device, the first network element can proactively update the temporary identifier of the first communication device. Specifically, when the first network element discovers that the temporary identifier of the first communication device needs to be updated, the first network element can generate a new temporary identifier and send a temporary identifier update command carrying the new temporary identifier to the second network element. The second network element forwards the temporary identifier update command carrying the new temporary identifier to the first-type device, and the first-type device sends the temporary identifier update command carrying the new temporary identifier to the first communication device, so that the first communication device uses the new temporary identifier to update the temporary identifier stored locally. In one example, in a scenario where the second communication node is a first type of device, the first network element can proactively update the temporary identifier of the first communication device. Specifically, when the first network element discovers that the temporary identifier of the first communication device needs to be updated, the first network element can generate a new temporary identifier and directly send a temporary identifier update command carrying the new temporary identifier to the first type of device. The first type of device will then send the temporary identifier update command carrying the new temporary identifier to the first communication device, so that the first communication device can use the new temporary identifier to update the temporary identifier stored locally.

[0059] In one embodiment, when the second communication device is a second type of device, sending a new temporary identifier to the first communication device includes:

[0060] The second network element and the third communication device send a temporary identifier update command carrying a new temporary identifier to the second communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

[0061] In one example, the second communication device refers to a reader / writer in AIoT; the second communication device can include both a first-type device and a second-type device. For example, the first-type device can be a base station reader / writer; the second-type device can be a UE reader / writer. In one example, in a scenario where the second communication node is a second-type device, the first network element can proactively update the temporary identifier of the first communication device. Specifically, when the first network element discovers that the temporary identifier of the first communication device needs to be updated, the first network element can generate a new temporary identifier and send a temporary identifier update command carrying the new temporary identifier to the second network element. The second network element forwards the temporary identifier update command carrying the new temporary identifier to the third communication device, which in turn forwards the temporary identifier update command carrying the new temporary identifier to the second-type device. The second-type device then sends the temporary identifier update command carrying the new temporary identifier to the first communication device, so that the first communication device uses the new temporary identifier to update the temporary identifier stored locally.

[0062] In one embodiment, the identifier update method applied to the first network element further includes:

[0063] Receive a successful temporary identifier update response from the first communication device;

[0064] The new temporary identifier is set to a valid state. In one example, a temporary identifier update success response indicates that the first communication device has successfully completed the temporary identifier update process; the temporary identifier update success response can be a message, an information, or a signaling. After the first communication device completes the temporary identifier update process, the first communication device generates and sends a temporary identifier update success response to the first network element; after the first network element successfully receives the temporary identifier update success response, the first network element sets the state of the new temporary identifier of the first communication device to a valid state, for example, by setting new timing information for the timer of the new temporary identifier.

[0065] In one embodiment, when the second communication device is a first type of device, receiving a temporary identifier update success response sent by the first communication device includes one of the following:

[0066] Receive a successful temporary identifier update response sent by the first communication device through the second network element and the second communication device;

[0067] Receive a successful temporary identifier update response sent by the first communication device through the second communication device.

[0068] In one example, when the second communication node is a type-one device, the first network element can proactively update the temporary identifier of the first communication device. Specifically, the first network element can send the new temporary identifier to the first communication device through the second network element and the type-one device. After the first communication device completes the update of the temporary identifier, it sends a temporary identifier update success response to the type-one device. The type-one device then forwards the temporary identifier update success response to the first network element through the second network element. Alternatively, in another example, when the second communication node is a type-one device, the first network element can proactively update the temporary identifier of the first communication device. Specifically, the first network element can directly send the new temporary identifier to the first communication device through the type-one device. After the first communication device completes the update of the temporary identifier, it sends a temporary identifier update success response to the type-one device. The type-one device then directly forwards the temporary identifier update success response to the first network element.

[0069] In one embodiment, when the second communication device is a second type of device, receiving a temporary identifier update success response sent by the first communication device includes:

[0070] Receive a successful temporary identifier update response sent by the first communication device through the second network element, the second communication device, and the third communication device.

[0071] In one example, in a scenario where the second communication node is a second type of device, the first network element can proactively update the temporary identifier of the first communication device. Specifically, when the first network element discovers that the temporary identifier of the first communication device needs to be updated, it can generate a new temporary identifier and send a temporary identifier update command carrying the new temporary identifier to the second network element. The second network element forwards the temporary identifier update command carrying the new temporary identifier to the third communication device, which in turn forwards the command to the second type of device. The second type of device then sends the command back to the first communication device, enabling the first communication device to update the locally stored temporary identifier using the new temporary identifier. After the first communication device completes the temporary identifier update, it sends a temporary identifier update success response to the second type of device. The second type of device then sends the response to the third communication device, which in turn sends it to the second network element. Finally, the second network element sends the response back to the first network element.

[0072] In one embodiment, the identifier update method applied to the first network element further includes:

[0073] Receive service operation requests sent by third network elements; wherein, the service operation request carries a permanent identifier;

[0074] Obtain a valid temporary identifier for the first communication device based on the permanent identifier;

[0075] A service operation request is sent to the second communication device using a valid temporary identifier, so that the second communication device can perform service operations with the first communication device using the valid temporary identifier.

[0076] In one example, a permanent identifier refers to a unique and unchanging identifier for the first communication device. In another example, the permanent identifier of each first communication device is unchanged by default after leaving the factory, meaning its validity period is unlimited; while a temporary identifier has a limited validity period. In another example, a valid temporary identifier refers to a temporary identifier currently used by the first communication device that is valid, meaning its validity period has not expired, or the timer has not expired. To accurately find the corresponding valid temporary identifier based on the permanent identifier of the first communication device, a mapping relationship can be established between the permanent identifier and the valid temporary identifier for each first communication device, or the temporary identifier can be configured based on the permanent identifier.

[0077] In one example, after the third network element receives a service operation request carrying a permanent identifier sent by the AF, the third network element queries the first network element serving the first communication device according to the first communication device targeted by the service operation request, and sends the service operation request to the first network element; then the first network element searches for a valid temporary identifier corresponding to the first communication device according to the permanent identifier carried in the service operation request, and uses the valid temporary identifier to directly send or forward the service operation request to the second communication device, so that the second communication device can use the valid temporary identifier to complete the service operation with the first communication device.

[0078] In one embodiment, when the second communication device is a first type of device, sending a service operation request to the second communication device using a valid temporary identifier includes one of the following:

[0079] The second network element uses a valid temporary identifier to forward the service operation request to the second communication device.

[0080] Use a valid temporary identifier to send a service operation request directly to the second communication device.

[0081] In one example, when the second communication device is a first-type device, the first network element can send a service operation request to the second network element using a valid temporary identifier; then, the second network element uses the valid temporary identifier to send a service operation request to the first-type device, enabling the first-type device to complete the service operation with the first communication device using the valid temporary identifier. In another example, when the second communication device is a first-type device, the first network element can directly send a service operation request to the first-type device using a valid temporary identifier, enabling the first-type device to complete the service operation with the first communication device using the valid temporary identifier.

[0082] In one embodiment, when the second communication device is a second type of device, sending a service operation request to the second communication device using a valid temporary identifier includes:

[0083] The service operation request is forwarded to the second communication device by using a valid temporary identifier through the second network element and the third communication device.

[0084] In one example, in a scenario where the second communication device is a second type of device, the first network element can send a service operation request to the second network element using a valid temporary identifier; then the second network element uses the valid temporary identifier to send a service operation request to the third communication device; then the third communication device uses the valid temporary identifier to send a service operation request to the second type of device, so that the second type of device can use the valid temporary identifier to complete the service operation with the first communication device.

[0085] In one embodiment, the identifier update method applied to the first network element further includes:

[0086] Receive the service operation results sent by the second communication device;

[0087] The associated permanent identifier is located based on the valid temporary identifier of the first communication device;

[0088] Use a permanent identifier to send the business operation results to the third network element.

[0089] In one example, the service operation result is used to characterize the result of the service operation between the first communication device and the second communication device; the service operation result may include: inventory result and command execution result. In one example, after completing the service operation with the first communication device, the second communication device directly sends or forwards the corresponding service operation result to the first network element. The first network element looks up the permanent identifier of the first communication device based on the valid temporary identifier of the first communication device, and uses the permanent identifier to send the service operation result to the third network element, so that the third network element sends the service operation result to the AF.

[0090] In one embodiment, when the second communication device is a first type of device, receiving the service operation result sent by the second communication device includes one of the following:

[0091] The second network element receives the service operation results sent by the second communication device.

[0092] It directly receives the service operation results sent by the second communication device.

[0093] In one example, when the second communication device is a first-type device, the first-type device can use the temporary identifier of the first communication device to perform service operations with the first communication device. The first-type device can send the service operation result to the second network element, and the second network element can then send the service operation result back to the first network element. Alternatively, in another example, when the second communication device is a first-type device, the first-type device can use the temporary identifier of the first communication device to perform service operations with the first communication device, and the first-type device can directly send the service operation result to the first network element.

[0094] In one embodiment, when the second communication device is a second type of device, receiving the service operation result sent by the second communication device includes one of the following:

[0095] The second network element and the third communication device receive the service operation results sent by the second communication device.

[0096] In one example, in a scenario where the second communication device is a second type of device, the first type of device can use the temporary identifier of the first communication device to perform service operations with the first communication device. The first type of device can send the service operation result to the third communication device. Then, the third communication device sends the service operation result to the second network element, and then sends the service operation result to the first network element through the second network element.

[0097] In one embodiment, the identifier update method applied to the first network element further includes:

[0098] An inventory operation is performed on the first communication device. Before the first network element sends a new temporary identifier to the first communication device, the first communication network element can perform an inventory operation on the first communication device so that the first network element can find the first communication device associated with the temporary identifier, which facilitates the successful transmission of the new temporary identifier.

[0099] In one embodiment, performing an inventory operation on the first communication device includes one of the following:

[0100] Use the original temporary identifier to perform an inventory operation on the first communication device;

[0101] A permanent identifier is used to perform an inventory operation on the first communication device. In one example, the first network element can use the original temporary identifier to perform an inventory operation on the first communication device. In another example, during the process of updating the temporary identifier of the first communication device, if the inventory operation fails when using the original temporary identifier, the permanent identifier of the first communication device can be used to perform the inventory operation, and the transmission process of the temporary identifier update command can be executed after the inventory operation is successful.

[0102] In one embodiment, the identifier update method applied to the first network element further includes:

[0103] The updated temporary identifier is synchronized to the fourth network element so that other first network elements can obtain the temporary identifier of the first communication device from the fourth network element. In one example, the fourth network element is a network element that can be accessed by multiple first network elements; for example, the fourth network element can be an ADM. In another example, after the first network element successfully updates the temporary identifier of the first communication device, the new temporary identifier can be stored in the fourth network element. When other first network elements need to use the temporary identifier of the first communication device, they can directly obtain the temporary identifier of the first communication device from the fourth network element, ensuring that different first network elements use the same temporary identifier for the same first communication device.

[0104] In one embodiment, FIG6 is a flowchart of another identifier update method provided by an embodiment of this application. This embodiment is applied to the case of dynamically updating the temporary identifier of a passive Internet of Things device. This embodiment can be executed by a first communication device. As shown in FIG6, this embodiment includes: S610-S620.

[0105] S610, if the identifier update conditions are met, receive a new temporary identifier generated by the first network element.

[0106] S620. Update the temporary identifier based on the new temporary identifier.

[0107] In one embodiment, the identifier update condition includes one of the following: the validity period of the original temporary identifier expires; a service operation request is received, and a new temporary identifier is used for each service operation.

[0108] In one embodiment, when the second communication device is a first type of device, receiving a new temporary identifier generated by the first network element includes one of the following:

[0109] A new temporary identifier generated by the first network element is received through the second network element and the second communication equipment;

[0110] The second communication device receives a new temporary identifier generated by the first network element.

[0111] In one embodiment, when the second communication device is a second type of device, receiving a new temporary identifier generated by the first network element includes one of the following:

[0112] The second network element, the second communication device, and the third communication device receive a new temporary identifier generated by the first network element.

[0113] In one embodiment, the identifier update method applied to the first communication device further includes:

[0114] Send a temporary identifier update success response to the first network element.

[0115] In one embodiment, when the second communication device is a first type of device, sending a temporary identifier update success response to the first network element includes one of the following:

[0116] A successful temporary identifier update response is sent to the first network element via the second network element and the second communication device;

[0117] The second communication device sends a temporary identifier update success response to the first network element.

[0118] In one embodiment, when the second communication device is a second type of device, sending a temporary identifier update success response to the first network element includes one of the following:

[0119] The second network element, the second communication device, and the third communication device send a temporary identifier update success response to the first network element.

[0120] In one embodiment, the identifier update method applied to the first communication device further includes:

[0121] The first network element uses a valid temporary identifier to perform service operations with the second communication device; wherein the valid temporary identifier is obtained by the first network element based on the permanent identifier carried in the service operation request.

[0122] It should be noted that the explanation and implementation of parameters such as the identifier update conditions, successful temporary identifier update response, permanent identifier, new temporary identifier, and original temporary identifier involved in the identifier update method applied to the first communication device can be found in the description of the corresponding parameters in the identifier update method applied to the first network element above, and will not be repeated here.

[0123] In the following embodiments, taking AIOTF as the first network element, AIoT device as the first communication device, reader as the second communication device, base station reader as the first type of device, UE reader as the second type of device, AMF as the second network element, base station as the third communication device, NEF as the third network element, and AIoT Data Management (ADM) as the fourth network element, the process of updating and using temporary identifiers will be explained.

[0124] Example 1:

[0125] Figure 7 is a schematic diagram illustrating the update interaction of a temporary identifier according to an embodiment of this application. In this embodiment, the process of AIOTF actively updating the temporary identifier of an AIoT device in a base station reader scenario is shown in Figure 7. This embodiment includes the following steps:

[0126] The original temporary identifiers for S710 and AIoT devices need to be updated.

[0127] In this embodiment, the AIOTF function detects that the original temporary identifier of the stored AIoT device needs to be updated, for example, if the expiration timer of the temporary identifier has expired.

[0128] S720 and AIOTF generate a new temporary identifier for the AIoT device.

[0129] For architectures where AIOTF and base station readers are not directly connected (connected via AMF), AIOTF and base station readers interact through AMF; for architectures where AIOTF and base station readers are directly connected, AIOTF and base station readers interact directly.

[0130] S730 and AIOTF use the original temporary identifier to interact with base station readers and AIoT devices to perform inventory operations on AIoT devices.

[0131] For AIoT devices that have been successfully inventoried, execute the following temporary identifier update command.

[0132] S741 and AIOTF forward the temporary identifier update command carrying the new temporary identifier to the base station reader via AMF.

[0133] For the non-direct connection architecture between AIOTF and the base station reader, AIOTF forwards the temporary identifier update command to the base station reader through AMF, carrying the new temporary identifier of the AIoT device.

[0134] S742 and AIOTF send a temporary identifier update command carrying the new temporary identifier to the base station reader.

[0135] For the direct connection architecture between AIOTF and the base station reader, AIOTF sends a temporary identifier update command to the base station reader, carrying the new temporary identifier of the AIoT device.

[0136] The S750 base station reader sends a temporary identifier update command to the AIoT device.

[0137] S760 and AIoT devices update the temporary identifier stored locally.

[0138] The S770 and AIoT devices send a successful temporary identifier update response to the base station reader.

[0139] For an architecture where the AIOTF is not directly connected to the base station reader (connected via AMF), execute S781; for an architecture where the AIOTF is directly connected to the base station reader, execute S782.

[0140] S781, the base station reader forwards the temporary identifier update success response to AIOTF via AMF.

[0141] S782, the base station reader sends a temporary identifier update success response to AIOTF.

[0142] S790 and AIOTF set a new temporary identifier for AIoT devices to be valid.

[0143] For example, if a temporary identifier contains a timer, then new timer information is set.

[0144] Example 2:

[0145] Figure 8 is a schematic diagram illustrating another temporary identifier update interaction provided in an embodiment of this application. In this embodiment, the process of AIOTF actively updating the temporary identifier of the AIoT device in a UE reader / writer scenario is shown in Figure 8. This embodiment includes the following steps:

[0146] The original temporary identifiers for S810 and AIoT devices need to be updated.

[0147] In this embodiment, the AIOTF function detects that the original temporary identifier of the stored AIoT device needs to be updated, for example, if the validity period timer of the temporary identifier has expired.

[0148] S820 and AIOTF generate a new temporary identifier for the AIoT device.

[0149] S830 and AIOTF use the original temporary identifier to interact with the UE reader and AIoT device to perform inventory operations on the AIoT device.

[0150] For AIoT devices that have been successfully inventoried, execute the following temporary identifier update command.

[0151] S840 and AIOTF send a temporary identifier update command carrying the new temporary identifier to the UE reader through the base station serving the UE reader and AMF forwarding.

[0152] The S850 and UE reader send temporary identifier update commands to the AIoT devices.

[0153] S860 and AIoT devices update the temporary identifier stored locally.

[0154] The S870 and AIoT devices send a temporary identifier update success response to the UE reader.

[0155] The S880 and UE reader forward the message to the AIOTF via the base station and AMF, and send a temporary identifier update success response.

[0156] S890 and AIOTF set a new temporary identifier for AIoT devices to be valid.

[0157] For example, if a temporary identifier contains a timer, then new timer information is set.

[0158] Example 3:

[0159] Figure 9 is an interactive schematic diagram of using a temporary identifier for service operations according to an embodiment of this application. In this embodiment, the process of using an AIoT device's temporary identifier for service operations in a base station reader scenario is shown in Figure 9. This embodiment includes the following steps:

[0160] S910 and AF send the service operation request of the AIoT device to NEF, carrying the permanent identifier of the target AIoT device.

[0161] Business operations on AIoT devices include inventory and command types; commands specifically include read, write, and disable. In one example, the target AIoT device is the AIoT device that requires business operations.

[0162] S920 and NEF query the AIOTF that serves the AIoT device based on the AIoT device targeted by the business operation request, and forward the business operation request to the AIOTF.

[0163] S930 and AIOTF obtain the valid temporary identifier of the AIoT device based on the permanent identifier of the AIoT device.

[0164] For an architecture where the AIOTF is not directly connected to the base station reader (connected via AMF), execute S941; for an architecture where the AIOTF is directly connected to the base station reader, execute S942.

[0165] S941 and AIOTF forward through AMF, using the valid temporary identifier of the AIoT device, to send service operation requests to the base station reader.

[0166] S942 and AIOTF use the valid temporary identifier of the AIoT device to send a service operation request to the base station reader.

[0167] The S950 and base station reader use valid temporary identifiers to interact with AIoT devices and complete business operations.

[0168] For an architecture where the AIOTF is not directly connected to the base station reader (connected via AMF), execute S961; for an architecture where the AIOTF is directly connected to the base station reader, execute S962.

[0169] S961, the base station reader forwards the service operation results to the AIOTF via AMF.

[0170] S962, The base station reader sends the service operation results to AIOTF.

[0171] S970 and AIOTF find the permanent identifier of the AIoT device based on the temporary identifier of the AIoT device.

[0172] S980 and AIOTF use the permanent identifier of the AIoT device to send the business operation results to NEF.

[0173] S990 and NEF use the permanent identifier of the AIoT device to send the business operation results to AF.

[0174] Example 4:

[0175] In this embodiment, the process of using the temporary identifier of the AIoT device for service operations in the UE reader scenario is similar to that shown in Figure 9 of the embodiment, except that:

[0176] In steps S941-S962, the AIOTF interacts with the UE reader, and the interaction process is carried out through the base station serving the UE reader and the AMF; the UE reader interacts with the AIoT device to complete the service operation.

[0177] Example 5:

[0178] Figure 10 is an interactive schematic diagram illustrating the updating of a temporary identifier during business operations, provided by an embodiment of this application. In this embodiment, the process of updating the temporary identifier of an AIoT device during business operations in a base station reader scenario is shown in Figure 10.

[0179] S1010 and AF send the service operation request of the AIoT device to NEF, carrying the permanent identifier of the target AIoT device.

[0180] S1020 and NEF query the AIOTF that serves the AIoT device based on the AIoT device targeted by the business operation request, and forward the business operation request to the AIOTF.

[0181] AIOTF triggers an update to the temporary identifier of the AIoT device. It checks whether the temporary identifier needs updating; for example, if the expiration timer for the temporary identifier has expired, it updates the temporary identifier of the AIoT device; proceed to S1031. Alternatively, according to the policy, AIOTF uses a new temporary identifier for each operation on the AIoT device; proceed to S1032.

[0182] S1031, AIOTF uses the permanent identifier of the AIoT device to find the temporary identifier of the AIoT device and discovers that the validity period of the temporary identifier has expired.

[0183] S1032, AIOTF uses a new temporary identifier for each business operation according to the policy.

[0184] S1040 and AIOTF generate a new temporary identifier for the AIoT device.

[0185] S1050, AIOTF and AMF, base station reader, and AIoT device interact to update the temporary identifier of the AIoT device.

[0186] For non-directly connected architectures, as shown in Figure 7, S741, S750, S760, S770, and S781 interact with the AMF, base station reader, and AIoT device to update the temporary identifier of the AIoT device. S1060 and AIOTF use the new temporary identifier to interact with the AMF, base station reader, and AIoT device to complete the service operations on the AIoT device.

[0187] For non-direct connection architecture, S941, S950, S961, and S970, as shown in Figure 9, interact with AMF, base station reader, and AIoT device to complete business operations on AIoT device.

[0188] S1070 and AIOTF find the permanent identifier of the AIoT device based on the temporary identifier of the AIoT device.

[0189] S1080 and AIOTF use the permanent identifier of the AIoT device to send the business operation results to NEF.

[0190] S1090 and NEF use the permanent identifier of the AIoT device to send the business operation results to AF.

[0191] Example 6:

[0192] The process of updating the temporary identifier of the AIoT device during service operations in the UE reader scenario is similar to that shown in Figure 10 of the embodiment, except that:

[0193] In steps S1050 and S1060, the AIOTF interacts with the UE reader, and the interaction process is carried out through the base station serving the UE reader and the AMF; the UE reader interacts with the AIoT device to complete the service operation.

[0194] Example 7:

[0195] In the AIOTF process of updating the temporary identifier of an AIoT device, the disk entry may fail when using the old temporary identifier to disk the AIoT device. This may be due to the failure to retrieve the old temporary identifier stored internally by the AIoT device. In this case, AIOTF should use the permanent identifier of the AIoT device to disk the AIoT device, and execute the command process to update the temporary identifier after the disk entry is successful.

[0196] Example 8:

[0197] Figure 11 is a schematic diagram of the synchronization interaction of a temporary identifier provided in this application. After successfully updating the temporary identifier of an AIoT device, the AIOTF can save it in the ADM; other AIOTFs can retrieve the temporary identifier of the AIoT device from the ADM when they need to use it, thus ensuring that different AIOTFs use the same temporary identifier of the AIoT device. The process of synchronizing the temporary identifier of the AIoT device through the ADM is shown in Figure 11.

[0198] After S1110 and AIOTF1 successfully update the temporary identifier of the AIoT device, they will synchronize this temporary identifier to ADM.

[0199] S1120, ADM stores this temporary identifier.

[0200] S1130 and AIOTF2 obtain the temporary identifier of the AIoT device from the ADM when they need to use it.

[0201] In one embodiment, FIG12 is a structural block diagram of an identifier update device provided in an embodiment of this application. This embodiment is applied to a first network element. As shown in FIG12, the identifier update device in this embodiment includes: a generation module 1210 and a sending module 1220.

[0202] The generation module 1210 is configured to generate a new temporary identifier when the identifier update conditions are met.

[0203] The sending module 1220 is configured to send a new temporary identifier to the first communication device so that the first communication device can update the temporary identifier based on the new temporary identifier.

[0204] In one embodiment, the identifier update condition includes one of the following: the validity period of the original temporary identifier expires; a service operation request is received, and a new temporary identifier is used for each service operation.

[0205] In one embodiment, when the second communication device is a first type of device, sending a new temporary identifier to the first communication device includes one of the following:

[0206] The second network element sends a temporary identifier update command carrying a new temporary identifier to the second communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

[0207] Send a temporary identifier update command carrying a new temporary identifier to the second communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

[0208] In one embodiment, when the second communication device is a second type of device, sending a new temporary identifier to the first communication device includes:

[0209] The second network element and the third communication device send a temporary identifier update command carrying a new temporary identifier to the second communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

[0210] In one embodiment, the identifier update device applied to the first network element further includes:

[0211] The receiving module is also configured to receive a successful temporary identifier update response sent by the first communication device;

[0212] The module is configured to set the status of the new temporary identifier to be valid.

[0213] In one embodiment, when the second communication device is a first type of device, receiving a temporary identifier update success response sent by the first communication device includes one of the following:

[0214] Receive a successful temporary identifier update response sent by the first communication device through the second network element and the second communication device;

[0215] Receive a successful temporary identifier update response sent by the first communication device through the second communication device.

[0216] In one embodiment, when the second communication device is a second type of device, receiving a temporary identifier update success response sent by the first communication device includes:

[0217] Receive a successful temporary identifier update response sent by the first communication device through the second network element, the second communication device, and the third communication device.

[0218] In one embodiment, the identifier update device applied to the first network element further includes:

[0219] The receiving module is also configured to receive service operation requests sent by a third network element; wherein the service operation request carries a permanent identifier;

[0220] The acquisition module is configured to obtain the valid temporary identifier of the first communication device based on the permanent identifier;

[0221] The sending module is configured to send a service operation request to the second communication device using a valid temporary identifier, so that the second communication device can use the valid temporary identifier to perform service operations with the first communication device.

[0222] In one embodiment, when the second communication device is a first type of device, sending a service operation request to the second communication device using a valid temporary identifier includes one of the following:

[0223] The second network element uses a valid temporary identifier to forward the service operation request to the second communication device.

[0224] Use a valid temporary identifier to send a service operation request directly to the second communication device.

[0225] In one embodiment, when the second communication device is a second type of device, sending a service operation request to the second communication device using a valid temporary identifier includes:

[0226] The service operation request is forwarded to the second communication device by using a valid temporary identifier through the second network element and the third communication device.

[0227] In one embodiment, the identifier update device applied to the first network element further includes:

[0228] The receiving module is also configured to receive the service operation results sent by the second communication device;

[0229] The lookup module is configured to look up an associated permanent identifier based on a valid temporary identifier of the first communication device;

[0230] The sending module is also configured to send the results of the business operation to the third network element using a permanent identifier.

[0231] In one embodiment, when the second communication device is a first type of device, receiving the service operation result sent by the second communication device includes one of the following:

[0232] The second network element receives the service operation results sent by the second communication device.

[0233] It directly receives the service operation results sent by the second communication device.

[0234] In one embodiment, when the second communication device is a second type of device, receiving the service operation result sent by the second communication device includes one of the following:

[0235] The second network element and the third communication device receive the service operation results sent by the second communication device.

[0236] In one embodiment, the identifier update device applied to the first network element further includes:

[0237] The inventory module is configured to perform inventory operations on the first communication device.

[0238] In one embodiment, performing an inventory operation on the first communication device includes one of the following:

[0239] Use the original temporary identifier to perform an inventory operation on the first communication device;

[0240] Use a permanent identifier to perform an inventory operation on the first communication device.

[0241] In one embodiment, the identifier update device applied to the first network element further includes:

[0242] The synchronization module is configured to synchronize the updated temporary identifier to the fourth network element, so that other first network elements can obtain the temporary identifier of the first communication device from the fourth network element.

[0243] The identifier update device provided in this embodiment is configured to implement the identifier update method applied to the first network element in the embodiment shown in Figure 5. The implementation principle and technical effect of the identifier update device provided in this embodiment are similar, and will not be described again here.

[0244] In one embodiment, FIG13 is a structural block diagram of another identifier updating device provided in this application. This embodiment is applied to a first communication device. As shown in FIG13, the identifier updating device in this embodiment includes: a receiving module 1310 and an updating module 1320.

[0245] The receiving module 1310 is configured to receive a new temporary identifier generated by the first network element when the identifier update conditions are met;

[0246] Update module 1320 to update temporary identifiers based on the new temporary identifier.

[0247] In one embodiment, the identifier update condition includes one of the following: the validity period of the original temporary identifier expires; a service operation request is received, and a new temporary identifier is used for each service operation.

[0248] In one embodiment, when the second communication device is a first type of device, receiving a new temporary identifier generated by the first network element includes one of the following:

[0249] A new temporary identifier generated by the first network element is received through the second network element and the second communication equipment;

[0250] The second communication device receives a new temporary identifier generated by the first network element.

[0251] In one embodiment, when the second communication device is a second type of device, receiving a new temporary identifier generated by the first network element includes one of the following:

[0252] The second network element, the second communication device, and the third communication device receive a new temporary identifier generated by the first network element.

[0253] In one embodiment, the identifier update device applied to the first communication device further includes:

[0254] The sending module is configured to send a temporary identifier update success response to the first network element.

[0255] In one embodiment, when the second communication device is a first type of device, sending a temporary identifier update success response to the first network element includes one of the following:

[0256] A successful temporary identifier update response is sent to the first network element via the second network element and the second communication device;

[0257] The second communication device sends a temporary identifier update success response to the first network element.

[0258] In one embodiment, when the second communication device is a second type of device, sending a temporary identifier update success response to the first network element includes one of the following:

[0259] The second network element, the second communication device, and the third communication device send a temporary identifier update success response to the first network element.

[0260] In one embodiment, the identifier update device applied to the first communication device further includes:

[0261] The operation module is configured to perform service operations with the second communication device using a valid temporary identifier; wherein the valid temporary identifier is obtained by the first network element based on the permanent identifier carried in the service operation request.

[0262] The identifier update device provided in this embodiment is configured to implement the identifier update method applied to the first communication device in the embodiment shown in FIG6. The implementation principle and technical effect of the identifier update device provided in this embodiment are similar, and will not be described again here.

[0263] In one embodiment, FIG14 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. As shown in FIG14, the device provided in this application includes: a processor 1410, a memory 1420, and a communication module 1430. The number of processors 1410 in the device can be one or more; FIG14 shows an example of one processor 1410. The number of memories 1420 in the device can be one or more; FIG14 shows an example of one memory 1420. The processor 1410, memory 1420, and communication module 1430 of the device can be connected via a bus or other means; FIG14 shows an example of connection via a bus. In this embodiment, the device can be a first network element or a first communication device.

[0264] The memory 1420, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the device in any embodiment of this application (e.g., generation module 1210 and transmission module 1220 applied to the identifier update device of the first network element). The memory 1420 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created according to the use of the device, etc. Furthermore, the memory 1420 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 1420 may further include memory remotely located relative to the processor 1410, and these remote memories can be connected to the device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0265] When the communication device is the first network element, the device provided above can be configured to execute the identifier update method for the first network element provided in any of the above embodiments, and has the corresponding functions and effects.

[0266] When the communication device is the first communication device, the device provided above can be configured to execute the identifier update method for the first communication device provided in any of the above embodiments, and has the corresponding functions and effects.

[0267] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform an identifier update method applied to a first network element. The method includes: satisfying identifier update conditions and generating a new temporary identifier; sending the new temporary identifier to a first communication device so that the first communication device updates the temporary identifier based on the new temporary identifier.

[0268] This application embodiment also provides a storage medium containing computer-executable instructions. When executed by a computer processor, the computer-executable instructions are used to perform an identifier update method applied to a first communication device. The method includes: meeting the identifier update conditions and receiving a new temporary identifier generated by a first network element; and updating the temporary identifier based on the new temporary identifier.

[0269] Those skilled in the art will understand that the term user equipment covers any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0270] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0271] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0272] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disc (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0273] The above are merely preferred embodiments of this application and are not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for updating an identifier, characterized in that, Applied to a first network element, the method includes: generating a new temporary identifier when the identifier update conditions are met; and sending the new temporary identifier to a first communication device so that the first communication device updates the temporary identifier based on the new temporary identifier.

2. The method according to claim 1, characterized in that, The conditions for updating the identifier include one of the following: the validity period of the original temporary identifier expires; a business operation request is received, and a new temporary identifier is used for each business operation.

3. The method according to claim 1, characterized in that, When the second communication device is a first type of device, sending the new temporary identifier to the first communication device includes one of the following: sending a temporary identifier update command carrying the new temporary identifier to the second communication device through a second network element, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device; or sending a temporary identifier update command carrying the new temporary identifier to the second communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

4. The method according to claim 1, characterized in that, When the second communication device is a second type of device, sending the new temporary identifier to the first communication device includes: sending a temporary identifier update command carrying the new temporary identifier to the second communication device through the second network element and the third communication device, so that the second communication device sends the temporary identifier update command carrying the new temporary identifier to the first communication device.

5. The method according to claim 1, characterized in that, The method further includes: receiving a temporary identifier update success response sent by the first communication device; and setting the status of the new temporary identifier to a valid status.

6. The method according to claim 5, characterized in that, When the second communication device is a first type of device, receiving the temporary identifier update success response sent by the first communication device includes one of the following: receiving the temporary identifier update success response sent by the first communication device through the second network element and the second communication device; or receiving the temporary identifier update success response sent by the first communication device through the second communication device.

7. The method according to claim 5, characterized in that, When the second communication device is a second type of device, receiving the temporary identifier update success response sent by the first communication device includes: receiving the temporary identifier update success response sent by the first communication device through the second network element, the second communication device, and the third communication device.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: receiving a service operation request sent by a third network element; wherein the service operation request carries a permanent identifier; obtaining a valid temporary identifier of the first communication device based on the permanent identifier; and sending a service operation request to a second communication device using the valid temporary identifier, so that the second communication device uses the valid temporary identifier to perform service operations with the first communication device.

9. The method according to claim 8, characterized in that, When the second communication device is a first type of device, sending a service operation request to the second communication device using the valid temporary identifier includes one of the following: forwarding the service operation request to the second communication device using the valid temporary identifier through a second network element; or directly sending the service operation request to the second communication device using the valid temporary identifier.

10. The method according to claim 8, characterized in that, When the second communication device is a second type of device, sending a service operation request to the second communication device using the valid temporary identifier includes: forwarding the service operation request to the second communication device using the valid temporary identifier through the second network element and the third communication device.

11. The method according to claim 8, characterized in that, The method further includes: receiving a service operation result sent by a second communication device; searching for an associated permanent identifier based on a valid temporary identifier of the first communication device; and sending the service operation result to a third network element using the permanent identifier.

12. The method according to claim 11, characterized in that, When the second communication device is a first type of device, receiving the service operation result sent by the second communication device includes one of the following: receiving the service operation result sent by the second communication device through the second network element; or directly receiving the service operation result sent by the second communication device.

13. The method according to claim 11, characterized in that, When the second communication device is a second type of device, receiving the service operation result sent by the second communication device includes one of the following: receiving the service operation result sent by the second communication device through the second network element and the third communication device.

14. The method according to any one of claims 1-7, characterized in that, The method further includes: performing an inventory operation on the first communication device.

15. The method according to claim 14, characterized in that, The inventory operation of the first communication device includes one of the following: performing an inventory operation on the first communication device using the original temporary identifier; or performing an inventory operation on the first communication device using a permanent identifier.

16. The method according to any one of claims 1-7, characterized in that, The method further includes: synchronizing the updated temporary identifier to the fourth network element, so that other first network elements can obtain the temporary identifier of the first communication device from the fourth network element.

17. A method for updating an identifier, characterized in that, Applied to a first communication device, the method includes: meeting the identifier update conditions, receiving a new temporary identifier generated by a first network element; and updating the temporary identifier based on the new temporary identifier.

18. The method according to claim 17, characterized in that, The conditions for updating the identifier include one of the following: the validity period of the original temporary identifier expires; a business operation request is received, and a new temporary identifier is used for each business operation.

19. The method according to claim 17, characterized in that, When the second communication device is a first type of device, receiving a new temporary identifier generated by the first network element includes one of the following: receiving a new temporary identifier generated by the first network element through the second network element and the second communication device; or receiving a new temporary identifier generated by the first network element through the second communication device.

20. The method according to claim 17, characterized in that, When the second communication device is a second type of device, receiving a new temporary identifier generated by the first network element includes one of the following: receiving a new temporary identifier generated by the first network element through the second network element, the second communication device, and the third communication device.

21. The method according to claim 17, characterized in that, The method further includes sending a temporary identifier update success response to the first network element.

22. The method according to claim 21, characterized in that, When the second communication device is a first type of device, sending a temporary identifier update success response to the first network element includes one of the following: sending a temporary identifier update success response to the first network element through the second network element and the second communication device; or sending a temporary identifier update success response to the first network element through the second communication device.

23. The method according to claim 21, characterized in that, When the second communication device is a second type of device, a temporary identifier update success response is sent to the first network element, including one of the following: sending a temporary identifier update success response to the first network element through the second network element, the second communication device, and the third communication device.

24. The method according to any one of claims 17-23, characterized in that, The method further includes: performing service operations with the second communication device using a valid temporary identifier; wherein the valid temporary identifier is obtained by the first network element based on the permanent identifier carried in the service operation request.

25. A communication device, characterized in that, include: Memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors perform the method as described in any one of claims 1-16 or 17-24.

26. A storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1-16 or 17-24.

Images