Identifier update method, communication apparatus and system

Abstract

Provided in the present application are an identifier update method, a communication apparatus and a system. In the method, a first core network element can send an update rule to a terminal, and the terminal can automatically update an identifier of the terminal on the basis of the update rule, without the need for determining, by means of an access network device, whether the identifier of the terminal needs to be updated, and for the access network device to request the core network element to allocate a new identifier to the terminal, such that interaction latency caused by the update of the identifier of the terminal can be reduced, thereby facilitating a reduction in information interaction latency between the terminal and another NF of a core network.

Description

Identification updating method, communication device and system

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on March 21, 2024, with application number 202410339075.6 and application name “Identification Update Method, Communication Device and System”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communications, and in particular to an identification updating method, a communication device, and a system. Background Art

[0003] Currently, in some network architectures, such as the fifth generation (5 th In the network architecture of the 5G generation mobile communication system, there is no direct interface between the radio access network (RAN) equipment (hereinafter referred to as the access network equipment) and other network functions (NF) of the core network (CN). Some core network elements are required to forward messages. For example, in 5G, the access and mobility management function (AMF) is required to forward messages, which may cause a large delay in the information exchange between the access network equipment and other NFs of the core network.

[0004] Therefore, a proposal has been made to add a direct connection interface between the access network equipment and other NFs in the core network in the future network architecture. The access network equipment can directly interact with other NFs in the core network through the direct connection interface without the need for forwarding by other core network elements, thereby reducing the interaction delay.

[0005] When a terminal registers with the core network, the core network's access and mobility management network element (such as the AMF) assigns an identifier to the terminal. To ensure communication security, the network element can also update the terminal's identifier and distribute the updated identifier through signaling. Therefore, even if a direct interface is added between the access network equipment and other core network NFs, the interaction between the terminal and other core network NFs may still be delayed. Summary of the Invention

[0006] The present application provides an identification update method, communication device and system, which are conducive to reducing the information interaction delay between the terminal and other NFs of the core network.

[0007] In a first aspect, a method for updating an identifier is provided. The method can be applied to a terminal, for example, and can be executed by the terminal, or by a component configured in the terminal (such as a processor, chip, or chip system), or can be implemented by a logic module or software capable of implementing all or part of the functions of the terminal. This application is not limited to this.

[0008] The method comprises: receiving an update rule from a first core network element, wherein the update rule is used for updating the identifier of a terminal; and updating the identifier of the terminal according to the update rule.

[0009] Based on the above solution, the first core network element can send an update rule to the terminal, which can be used to update the terminal's identity. In this way, the terminal can automatically update its identity according to the update rule, without having to rely on the access network device to determine whether the terminal's identity needs to be updated, nor does it require the access network device to request the core network element to allocate a new identity for the terminal. This can reduce the interaction delay caused by the terminal identity update, and further help reduce the information interaction delay between the terminal and other NFs in the core network.

[0010] In combination with the first aspect, in some implementations of the first aspect, the update rule indicates an update condition and / or an update method.

[0011] It should be understood that the update condition can be indicated by an update rule or predefined by the protocol, and this application does not limit this. It is understood that if the update rule is predefined, the update rule can indicate the update method without indicating the update condition. Of course, the update rule can also indicate the update condition, and the terminal executes the update condition according to the update condition indicated by the update rule, or in other words, executes the update condition indicated by the update rule as an update condition with higher priority.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the update condition includes one or more of the following: the time length from the last time the terminal identifier was obtained reaches a preset threshold; or the message type sent to the core network element is a preset message type.

[0013] The duration between the last time the terminal identifier was acquired may specifically refer to the duration between the current time and the last time the terminal identifier was acquired. The last acquired terminal identifier may be an initial identifier received from the first core network element, or a new terminal identifier updated by the terminal according to an update rule. The duration reaching a preset threshold may specifically refer to the duration being greater than or equal to the preset threshold.

[0014] The above-mentioned core network element can be understood as the first core network element, or it can be other core network elements, and this application does not limit this.

[0015] In combination with the first aspect, in certain implementations of the first aspect, the updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes multiple identifiers to be used, and the generation function is used to generate the identifiers to be used.

[0016] The above sequence includes multiple identifiers to be used. In other words, the sequence can be regarded as a set consisting of multiple identifiers to be used. Therefore, the sequence can also be called an identifier set. This application does not limit the specific form of the sequence.

[0017] The above generation function is used to generate an identifier to be used, or in other words, the generation function can be used to generate a new terminal identifier.

[0018] The above generation function may be used to generate a terminal identifier to be used next time based on a terminal identifier generated last time. The terminal identifier generated last time may be an initial identifier of the terminal or an updated identifier of the terminal.

[0019] In combination with the first aspect, in some implementations of the first aspect, a first message is received from the first core network element, where the first message indicates an initial identifier of the terminal and an allocation time of the initial identifier.

[0020] The first message indicates the time the initial identifier was assigned. One possible design is for the update condition to include the time since the last time the terminal identifier was acquired reaching a preset threshold. Since the first identifier acquired by the terminal is the initial identifier, the terminal can use the initial identifier assignment time as the starting time for determining whether the terminal identifier needs to be updated. Based on this starting time, the terminal can determine whether the terminal identifier needs to be updated and when to update it.

[0021] Alternatively, in another implementation, the first message may not indicate the allocation time of the terminal's initial identifier. In this case, the terminal may use the time of receiving the initial identifier as the starting time for the terminal to determine whether the terminal identifier needs to be updated.

[0022] In combination with the first aspect, in some implementations of the first aspect, the update rule is carried in the first message.

[0023] In one possible design, the update rule is carried in a first message. In other words, the first message may indicate the initial identification and update rule of the terminal.

[0024] In combination with the first aspect, in certain implementations of the first aspect, a second message is sent to the first core network element, the second message indicating the identifier most recently obtained by the terminal, and the second message is used to request selection of a functional network element; a third message is received from the first core network element, the third message indicating the identifier of the second core network element, and the second core network element is the selected functional network element.

[0025] In a second aspect, a method for updating an identifier is provided. The method can be applied to a first core network element. For example, the method can be performed by the first core network element, or by a component configured in the first core network element (such as a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the first core network element. This application is not limited to this.

[0026] The method comprises: determining an update rule, wherein the update rule is used for updating the identification of a terminal; and sending the update rule to the terminal.

[0027] Based on the above solution, the first core network element can send an update rule to the terminal, which can be used to update the terminal's identity. In this way, the terminal can automatically update its identity according to the update rule, without having to rely on the access network device to determine whether the terminal's identity needs to be updated, nor does it require the access network device to request the core network element to allocate a new identity for the terminal. This can reduce the interaction delay caused by the terminal identity update, and further help reduce the information interaction delay between the terminal and other NFs in the core network.

[0028] In combination with the second aspect, in some implementations of the second aspect, the update rule indicates an update condition and / or an update method.

[0029] In combination with the second aspect, in certain implementations of the second aspect, the update condition includes one or more of the following: the time length from the last time the identification of the terminal was obtained reaches a preset threshold; or the message type sent by the terminal to the core network element is a preset message type.

[0030] In combination with the second aspect, in certain implementations of the second aspect, the updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes multiple identifiers to be used, and the generation function is used to generate the identifiers to be used.

[0031] In combination with the second aspect, in some implementations of the second aspect, a first message is sent to the terminal, where the first message indicates an initial identifier of the terminal and an allocation time of the initial identifier.

[0032] In combination with the second aspect, in some implementations of the second aspect, the update rule is carried in the first message.

[0033] In combination with the second aspect, in certain implementations of the second aspect, a second message is received from the terminal, the second message indicating the identifier most recently obtained by the terminal, and the second message is used to request selection of a functional network element; a third message is sent to the terminal, the third message indicating the identifier of a second core network element, and the second core network element is the selected functional network element; a fourth message is sent to the second core network element, the fourth message indicating the update rule of the terminal, the initial identifier of the terminal, and the allocation time of the initial identifier.

[0034] It should be understood that the technical solution of the second aspect corresponds to the technical solution of the first aspect. For a more detailed description of various possible implementations of the second aspect, please refer to the relevant description of the first aspect, which will not be repeated here.

[0035] In a third aspect, an identification updating method is provided. The method can be applied to a second core network element. For example, the method can be executed by the second core network element, or by a component configured in the second core network element (such as a processor, chip, or chip system), or by a logic module or software capable of implementing all or part of the functions of the second core network element. This application is not limited to this.

[0036] The method includes: receiving a fourth message from a first core network element, the fourth message indicating an update rule of a terminal, an initial identifier of the terminal, and an allocation time of the initial identifier; and updating the identifier of the terminal according to the update rule.

[0037] Based on the above solution, the first core network element can send the terminal's update rules, the terminal's initial identifier, and the allocation time of the initial identifier to the second core network element. The update rules can be used to update the terminal identifier. In this way, the second core network element can automatically update the terminal identifier based on the update rules, without having to determine whether the terminal identifier needs to be updated through the access network device, nor does it require the access network device to request the core network element to allocate a new identifier for the terminal. This can reduce the interaction delay caused by the terminal identifier update, which in turn helps reduce the information interaction delay between the terminal and other NFs in the core network.

[0038] In combination with the third aspect, in certain implementations of the third aspect, the update rule indicates an update condition and / or an update method.

[0039] In combination with the third aspect, in certain implementations of the third aspect, the update condition includes one or more of the following: the time length from the last time the identification of the terminal was obtained reaches a preset threshold; or the message type received from the terminal is a preset message type.

[0040] In combination with the third aspect, in certain implementations of the third aspect, the updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes multiple identifiers to be used, and the generation function is used to generate the identifiers to be used.

[0041] It should be understood that the technical solution of the third aspect corresponds to the technical solution of the first and second aspects. For a more detailed description of various possible implementations of the third aspect, please refer to the relevant descriptions of the first and second aspects, which will not be repeated here.

[0042] In a fourth aspect, a communications device is provided that can implement the identification update method described in the first to third aspects and any possible implementation of the first to third aspects. The device includes one or more corresponding functional units or modules for executing the above-described method. The functional units or modules included in the device can be implemented in software and / or hardware.

[0043] In a fifth aspect, a communication device is provided, comprising at least one processor, wherein the at least one processor is configured to execute the identification update method described in the first to third aspects and any possible implementation of the first to third aspects.

[0044] Optionally, the apparatus may further include a memory for storing instructions and data. The memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the methods described in the above aspects may be implemented.

[0045] Optionally, the apparatus may further include a communication interface, which is used for the apparatus to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.

[0046] In the sixth aspect, a chip system is provided, which includes at least one processor for supporting the implementation of the functions involved in the above-mentioned first to third aspects and any possible implementation methods of the first to third aspects, for example, receiving or processing the data and / or information involved in the above-mentioned method.

[0047] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0048] In one possible design, the chip system further includes an interface circuit and / or a power supply circuit, where the interface circuit is used to transmit data and the power supply circuit is used to supply power to the chip system.

[0049] The chip system can be composed of chips, or can include chips and other discrete devices.

[0050] In a seventh aspect, a communication system is provided, which includes one or more of the aforementioned terminal, the first core network element or the second core network element.

[0051] In an eighth aspect, a computer-readable storage medium is provided, comprising a computer program, which, when executed on a computer, enables the computer to implement the method in the first to third aspects and any possible implementation of the first to third aspects.

[0052] In the ninth aspect, a computer program product is provided, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute the method in the first to third aspects and any possible implementation of the first to third aspects.

[0053] It should be understood that the fourth to ninth aspects of the present application correspond to the technical solutions of the first to third aspects of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0055] FIG2 is a schematic diagram of a 5G network architecture provided in an embodiment of the present application;

[0056] FIG3 is a schematic diagram of a future network architecture provided by an embodiment of the present application;

[0057] FIG4 is a schematic diagram of another future network architecture provided by an embodiment of the present application;

[0058] FIG5 is a schematic diagram of another future network architecture provided by an embodiment of the present application;

[0059] FIG6 is a schematic flowchart of terminal identification allocation provided in an embodiment of the present application;

[0060] FIG7 is a schematic flow chart of NF selection provided in an embodiment of the present application;

[0061] FIG8 is a schematic flowchart of information interaction between a terminal and an NF selected by an AMF according to an embodiment of the present application;

[0062] FIG9 is a schematic flow chart of an identification updating method provided in an embodiment of the present application;

[0063] FIG10 is another schematic flow chart of the identification updating method provided in an embodiment of the present application;

[0064] FIG11 is a schematic block diagram of a communication device provided in an embodiment of the present application;

[0065] FIG12 is another schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0066] The technical solution provided in this application will be described below in conjunction with the accompanying drawings.

[0067] To facilitate understanding of the embodiments of the present application, the following points are first explained:

[0068] First, in this application, indications include explicit indications (also called direct indications) and implicit indications (also called indirect indications). Specifically, explicit indication information A refers to including information A; implicit indication information A refers to indicating information A through the correspondence between information A and information B and directly indicating information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured; or, it can also refer to indicating information A through information B and preset rules.

[0069] Second, in this application, "at least one" means one or more, and "more" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship, but it does not exclude the situation where it indicates that the previous and next associated objects are in an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.

[0070] Third, in this application, the use of prefixes such as "first" and "second" is solely for the purpose of distinguishing and describing different things belonging to the same name category, and does not restrict the order, size, or quantity of things. For example, "first core network element" and "second core network element" are simply different core network elements, and do not limit the number or priority of core network elements; for another example, "first message" and "second message" are simply different messages, and there is no time sequence, size, or priority relationship between the two.

[0071] Fourth, the communication between different devices involved in the embodiments of the present application may refer to direct communication between different devices (i.e., no other devices are required to transfer or forward), or it may refer to communication between different devices through other devices (i.e., other devices are required to transfer or forward), or it may refer to the functional unit inside the device communicating with other devices through another functional unit.

[0072] "Sending" and "receiving" in this application indicate the direction of signal transmission. For example, "sending a message to AMF" can be understood as the destination end of the message is AMF, which can include direct sending, or indirect sending through other network elements, units or modules. "Receiving a message from a terminal" can be understood as the source end of the message is the terminal, which can include direct receiving from the terminal, or indirect receiving from the terminal through other network elements, units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.

[0073] In other words, sending and receiving can be performed between devices, for example, between different devices; or it can be performed within a device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through a bus, wiring or interface.

[0074] The information may be processed between the source and destination, such as format changes, digital-to-analog conversion, etc., but the destination can understand the valid information from the source. Similar expressions in this application can be understood similarly and will not be repeated here.

[0075] Fifth, in the embodiments of the present application, "when", "if" and "if" all mean that the device will perform corresponding processing under certain objective circumstances, which does not limit the time, nor does it require that the device must perform a judgment action when it is implemented, nor does it mean that there are other limitations.

[0076] Sixth, in this application, words such as "example," "exemplarily," "for example," or "such as" are used to indicate examples, illustrations, or explanations. Any embodiment or design described in this application as "example," "exemplarily," "for example," or "such as" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "example," "exemplarily," "for example," or "such as" is intended to present the relevant concepts in a concrete manner.

[0077] Seventh, this application involves multiple identifiers, such as terminal identifiers, AMF identifiers, NF identifiers, and so on. The identifier of each network element is used to indicate the corresponding network element. For the convenience of distinction and explanation, the various identifiers are named in the following manner as "network element + identifier". For example, the terminal identifier is recorded as the terminal identifier, the AMF identifier is recorded as the AMF identifier, the NF identifier is recorded as the NF identifier, and so on.

[0078] The technical solutions provided in this application can be applied to various communication systems, such as: fifth generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, wireless local area networks (WLAN) systems, satellite communication systems, future communication systems, such as sixth generation (6G) mobile communication systems, or a fusion system of multiple systems. The technical solutions provided in this application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0079] A device in a communication system can send a signal to another device or receive a signal from another device. The signal may include information, signaling, or data, etc. The device may also be replaced by an entity, a network entity, a communication device, a communication module, a node, a communication node, etc. The present disclosure uses the device as an example for description. For example, the communication system may include at least one terminal device and at least one network device. The network device may send a downlink signal to the terminal device, and / or the terminal device may send an uplink signal to the network device. It is understandable that the terminal device in the present disclosure may be replaced by a first communication device, and the network device may be replaced by a second communication device, and both perform the corresponding communication methods in the present disclosure.

[0080] Figure 1 is a schematic diagram of the architecture of a communication system applicable to the communication method provided in this application. Figure 1 shows a schematic diagram of a possible, non-limiting system architecture. As shown in Figure 1, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one RAN node (such as 110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal (such as 120a-120j in Figure 1, collectively referred to as 120). The RAN 100 may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The terminal 120 is connected to the RAN node 110 via a wireless connection. The RAN node 110 is connected to the core network 200 via a wireless or wired connection. The core network equipment in the core network 200 and the RAN node 110 in the RAN 100 can be different physical devices, or they can be the same physical device that integrates the core network logical functions and the radio access network logical functions.

[0081] The RAN 100 may be a cellular system related to the Third Generation Partnership Project (3GPP), such as a 4G or 5G mobile communication system, or a future-oriented evolutionary system (such as a 6G mobile communication system). The RAN 100 may also be an open access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (Wi-Fi) system. The RAN 100 may also be a communication system that integrates two or more of the above systems.

[0082] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, is a component of a communications system that facilitates wireless access for terminals and is a device or module with corresponding communication functions. RAN node 110 is typically equipped with a communication module, circuit, or chip that performs the corresponding communication functions. RAN node 110 may also be configured with program instructions for performing the corresponding communication functions and corresponding program instructions.

[0083] The multiple RAN nodes 110 in the communication system 10 can be nodes of the same type or different types. In some scenarios, the roles of the RAN nodes 110 and the terminals 120 are relative. For example, the network element 120i in Figure 1 can be a helicopter or a drone, which can be configured as a mobile base station. For the terminals 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; however, for the base station 110a, the network element 120i is a terminal. The RAN nodes 110 and the terminals 120 are sometimes referred to as communication devices. For example, the network elements 110a and 110b in Figure 1 can be understood as communication devices with base station functions, and the network elements 120a-120j can be understood as communication devices with terminal functions.

[0084] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a Wi-Fi system. A RAN node may be a macro base station (such as 110a in Figure 1 ), a micro base station or an indoor station (such as 110b in Figure 1 ), a relay node or a donor node, or a wireless controller in a CRAN scenario. Alternatively, a RAN node may be a server, a wearable device, a vehicle, or an onboard device. For example, the access network device in vehicle-to-everything (V2X) technology may be a roadside unit (RSU).

[0085] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, and different RAN nodes respectively implement part of the functions of the base station. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or they can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0086] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called open CU (O-CU), DU may also be called open DU (O-DU), CU-CP may also be called open CU-CP (O-CU-CP), CU-UP may also be called open CU-UP (O-CU-UP), and RU may also be called open RU (O-RU). For the convenience of description, this application uses CU, CU-CP, CU-UP, DU and RU as examples for description. Any unit of CU (or CU-CP, CU-UP), DU and RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0087] A terminal can be a device or module that accesses the above-mentioned communication system and has corresponding communication functions. A terminal can also be referred to as user equipment (UE), terminal, user device, access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, user terminal, terminal unit, terminal station, terminal device, wireless communication device, user agent, or user device. The terminal is typically equipped with a communication module, circuit, or chip that performs the corresponding communication functions. The terminal is also configured with program instructions for performing the corresponding communication functions.

[0088] For example, the terminal in the embodiment of the present application can be a mobile phone, a personal digital assistant (PDA), a laptop computer, a tablet computer, a drone, a computer with wireless transceiver function, a machine type communication (MTC) terminal, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an Internet of Things (IoT) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home (such as a game console, a smart TV, a smart speaker, a smart refrigerator, and fitness equipment, etc.), a transport vehicle with wireless communication function, a communication module, and a roadside unit (RSU) with a terminal function.

[0089] In the embodiments of the present application, the terminal and network device can be hardware devices, or software functions running on dedicated hardware, software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (for example, a cloud platform), or entities including dedicated or general-purpose hardware devices and software functions. The present application does not limit the specific form of the terminal and network device.

[0090] In the embodiments of the present application, the functions of the RAN node may also be performed by a module (such as a chip) in the RAN node, or by a control subsystem that includes the RAN node functions. The control subsystem that includes the RAN node functions here may be a control center in the application scenarios of the above-mentioned terminals, such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may also be performed by a module (such as a chip) in the terminal device, or by a device that includes the terminal device functions. This application does not limit this.

[0091] It will be understood that FIG1 is only a simplified schematic diagram for ease of understanding, and the communication system may also include other possible devices, such as wireless relay devices and wireless backhaul devices. Each device may also include different functional units, which are not shown in FIG1 .

[0092] Figure 2 shows a schematic diagram of the 5G network architecture. As shown in Figure 2, a 5G network primarily consists of three components: terminals, RAN, and core network. The RAN includes access network equipment (such as base stations (BS)), and the core network includes a series of network functions (NFs). For example, core network NFs include the AMF and other NFs (such as NF1, NF2, and NF3).

[0093] Among them, AMF is mainly used for mobility management and access management, etc. It can be used to implement other functions of the mobility management entity (MME) in addition to session management, such as user registration management, connectivity management, reachability management or access authorization (or authentication) and other functions.

[0094] Other NFs include, for example, session management function (SMF), unified data management function (UDM), location management function (LMF) network elements, and authentication server function (AUSF), etc. Among them, the SMF network element is mainly used for session management, tunnel maintenance, terminal Internet Protocol (IP) address allocation and management, selection of manageable user plane functions, policy control, or charging function interface termination points, and downlink data notification; UDM is mainly used for user identification and contract information management; LMF is mainly used for user positioning and location management; AUSF is mainly used for user authentication.

[0095] In a 5G network, there is a direct interface between the access network device and the AMF, but no direct interface with other NFs in the core network (such as NF1, NF2, and NF3). Therefore, the information exchanged between the access network device and other NFs in the core network needs to be forwarded through the AMF. As an example, the names of the information exchanged between various devices in a 5G network are as follows:

[0096] The information exchanged between the terminal and the access network equipment is called radio resource control (RRC) message;

[0097] The messages exchanged between the terminal and the AMF or other NF are called non-access stratum (NAS) messages. NAS messages need to be forwarded by access network devices, but access network devices do not parse the messages.

[0098] The messages exchanged between access network devices and AMF or other NFs are called Nx messages. Among them, the information exchanged between access network devices and other NFs needs to be forwarded by AMF, but AMF does not parse the messages;

[0099] The messages exchanged between AMF and other NFs are called Ny messages.

[0100] It should be noted that the names of the various network elements (such as AMF, SMF, LMF, etc.) included in Figure 2, as well as the names of the interactions between the network elements, are examples and should not constitute any limitation to this application. This application does not limit the functions and names of the network elements, nor does it limit the names of the messages transmitted between the network elements.

[0101] It is not difficult to see that in the 5G network, there is no direct connection interface between the access network equipment and other NFs in the core network, which may cause a large delay in information interaction between the access network equipment and other NFs in the core network.

[0102] Therefore, a proposal has been made to add a direct connection interface between the access network equipment and other NFs in the core network in the future network architecture, so that the access network equipment can directly exchange information with other NFs in the core network.

[0103] Figure 3 shows a schematic diagram of a future network architecture. As shown in Figure 3, the network includes terminals, a RAN, and a core network. The RAN includes access network equipment (e.g., a base station), and the core network includes a series of NFs. For example, the core network NFs include the AMF and other NFs (e.g., NF1, NF2, and NF3).

[0104] In the network shown in Figure 3, since the BS has direct interfaces with other NFs in the core network, the BS can directly exchange information with other NFs. The names of messages exchanged between devices can be the same as those in 5G networks. The messages exchanged between the terminal and the BS are called RRC messages; the messages exchanged between the terminal and the AMF or other NFs are called NAS messages. NAS messages need to be forwarded by the BS, but the BS does not parse them. The messages exchanged between the BS and the AMF or other NFs are called Nx messages; and the messages exchanged between the AMF and other NFs are called Ny messages.

[0105] It should be understood that the network architecture shown in Figure 3 shows access network equipment using a non-separated architecture. As mentioned above, the access network equipment may also use a separated architecture, as shown in Figures 4 and 5 below.

[0106] Figure 4 shows another schematic diagram of the future network architecture. The network architecture in Figure 4 shows an access network device using a separation architecture. The access network device can be divided into two parts: CU and DU. The CU is responsible for wireless high-layer protocols, and the DU is responsible for wireless low-layer protocols.

[0107] In the network shown in FIG4 , the interfaces between the access network devices and the core network elements, and the message names for interaction between the devices are similar to those in FIG3 and are not described again here.

[0108] Figure 5 shows another schematic diagram of the future network architecture. The network architecture shown in Figure 5 adopts an open radio access network, which can be called an open network architecture. As shown in Figure 5, the network architecture includes: terminals, O-RAN and core network. Among them, O-RAN includes a non-real-time radio access network intelligent controller (Non-RT RIC), a near-real-time radio access network intelligent controller (Near-RT RIC), O-CU-CP and O-DU, etc.

[0109] In the network shown in FIG5 , the interfaces between the access network devices and the core network elements, and the message names for interaction between the devices are similar to those in FIG3 and are not described again here.

[0110] Currently, when a terminal accesses the network, core network elements responsible for access and mobility management, such as the AMF, can assign a temporary identifier (or simply an identifier) ​​to the terminal, which is used by various devices in the network to identify the terminal. The following uses the network architecture shown in Figures 3 to 5 as an example, and combines Figures 6 to 8 to describe the three processes related to terminal identifier allocation: terminal identifier allocation, NF selection, and information exchange between the terminal and NF.

[0111] It should be noted that in the processes shown in Figures 6 to 8, the steps performed by the access network device can be performed by the BS in the network architecture shown in Figure 3, or by the CU in the network architecture shown in Figure 4, or by the O-CU-CP in the network architecture shown in Figure 5. Figure 6 shows the process of terminal identity allocation, and Figure 6 shows the process of the AMF allocating an identity to the terminal when the terminal initially accesses the network. The following describes the various steps in Figure 6.

[0112] In step 601, the terminal sends an RRC message to the access network device. The RRC message may include: a NAS message and an AMF identifier sent by the terminal to the AMF. The NAS message is used to request the AMF to allocate an identifier to the terminal.

[0113] The AMF identifier is used to indicate the AMF. Access network devices cannot parse NAS messages, but they can parse RRC messages and obtain the AMF identifier from them. Based on the AMF identifier, the access network device can determine to which AMF the NAS message should be sent.

[0114] For example, the AMF identifier may be a number (e.g., 0001), a string (e.g., "AMF#0001"), a network address (e.g., "192.168.1.03"), or other types of data, etc., which is not limited in this embodiment of the present application.

[0115] In step 602, the access network device sends an Nx message to the AMF, where the Nx message may include the NAS message received in step 601.

[0116] In step 603, the AMF allocates an identifier to the terminal.

[0117] The identifier assigned by the AMF to the terminal is a terminal identifier, which can be used to indicate the terminal. For example, the identifier of the terminal can be a number (e.g., 005), a string (e.g., "UE#005"), or other types of data, etc., which is not limited in this embodiment of the present application.

[0118] In step 604, the AMF sends an Nx message to the access network device. The Nx message may include: a NAS message and a terminal identifier sent by the AMF to the terminal. The NAS message may include the terminal identifier.

[0119] It should be understood that the access network device cannot parse the NAS message included in the Nx message, but can parse the terminal identifier included in the Nx message. Therefore, the access network device can obtain the terminal identifier based on the received Nx message. In other words, the AMF indicates the terminal identifier allocated in step 603 to the access network device via the Nx message and to the terminal via the NAS message.

[0120] In step 605 , the access network device sends an RRC message to the terminal. The RRC message may include the NAS message received in step 604 .

[0121] The access network device forwards the NAS message sent by the AMF to the terminal via an RRC message. The terminal can obtain the terminal identifier assigned by the AMF by parsing the received NAS message.

[0122] Figure 7 shows the NF selection process. Figure 7 illustrates the process by which a terminal that has successfully accessed the network requests the AMF to select an appropriate NF when it requires a service from the network. The following describes each step in Figure 7.

[0123] In step 701, the terminal sends an RRC message to the access network device. The RRC message may include: a NAS message and an AMF identifier sent by the terminal to the AMF. The NAS message includes a terminal identifier. The NAS message is used to request the AMF to select a suitable NF for the terminal.

[0124] Similar to step 601, the access network device can determine to which AMF to send the NAS message based on the AMF identifier included in the RRC message.

[0125] In step 702, the access network device sends an Nx message to the AMF, which may include the NAS message received in step 701.

[0126] In step 703, the AMF selects a suitable NF for the terminal according to the NAS message.

[0127] The AMF may select a suitable NF for the terminal based on the service requested by the terminal indicated in the NAS message and record the NF identifier, which is used to indicate the NF.

[0128] For example, the above NAS message indicates that the terminal requests the network to provide centimeter-level positioning services, then the AMF can select a NF with centimeter-level positioning capabilities (such as LMF) and record the NF identifier.

[0129] In step 704, the AMF sends an Nx message to the access network device. The Nx message may include: a NAS message, an NF identifier, and a terminal identifier. The NAS message includes the NF identifier selected by the AMF.

[0130] Similar to step 604, the access network device cannot parse the NAS message included in the above Nx message, but can parse the terminal identifier and NF identifier included in the above Nx message. Therefore, the access network device determines which NF is selected for which terminal based on the received Nx message.

[0131] In step 705, the AMF sends an Ny message to the NF, where the Ny message may include a terminal identifier.

[0132] The Ny message may be used to notify the NF that it can provide services for the terminal indicated by the terminal identifier.

[0133] In step 706 , the access network device sends an RRC message to the terminal. The RRC message may include the NAS message received in step 704 .

[0134] Similar to step 605, the access network device forwards the NAS message sent by the AMF to the terminal via an RRC message. The terminal can obtain the NF identifier by parsing the received NAS message, that is, it can determine the NF selected by the AMF.

[0135] Figure 8 shows the information exchange process between the terminal and the NF selected by the AMF. The following describes each step in Figure 8.

[0136] In step 801, the terminal sends an RRC message to the access network device. The RRC message may include: a NAS message sent by the terminal to the NF selected by the AMF, an NF identifier, and a terminal identifier. The NAS message may include the terminal identifier.

[0137] The NF identifier is used to indicate the NF. The NF may be the NF selected by the NF selection process shown in FIG7 . The RRC message is used to request the NF to provide a service to the terminal.

[0138] In step 802, the access network device determines whether the terminal identification needs to be updated.

[0139] Exemplarily, the access network device may determine that the terminal identifier needs to be updated when one or more of the following conditions are met: the time from the last terminal identifier allocation has reached a preset threshold or the NAS message is a preset message type, etc.

[0140] If the terminal identification does not need to be updated, then execute step 803. If the terminal identification needs to be updated, then execute steps 804 to 808.

[0141] In step 803 , the access network device sends an Nx message to the NF. The Nx message may include the NAS message received in step 801 .

[0142] The access network device may send the Nx message to the corresponding NF according to the NF identifier included in the RRC message received in step 801, so as to forward the NAS message received in step 801 to the NF.

[0143] In step 804, the access network device sends an Nx message to the AMF. The Nx message may include indication information and / or the NAS message received in step 801. The indication information may be used to indicate that the terminal identity needs to be updated.

[0144] In step 805, after receiving the Nx message, the AMF may allocate a new terminal identifier for the terminal. In step 806, the AMF sends an Nx message to the access network device. The Nx message may include: the NAS message sent by the AMF to the terminal and the new terminal identifier. The NAS message may include the new terminal identifier allocated by the AMF.

[0145] In step 807 , the access network device sends an RRC message to the terminal. The RRC message may include the NAS message received in step 806 .

[0146] In step 808, the AMF sends an Ny message to the NF, where the Ny message may include a new terminal identifier.

[0147] The Ny message is used to notify the NF that it can provide services for the terminal indicated by the new terminal identifier.

[0148] As shown in Figure 8, when a terminal sends an NAS message to an NF, the access network device determines whether the terminal's identity needs to be updated to ensure communication security. If so, the access network device requests the newly assigned terminal identity from the core network element responsible for access and mobility management (such as the AMF). This may cause delays in information exchange between the terminal and other NFs in the core network. Furthermore, the terminal identity is allocated and issued by the core network element responsible for access and mobility management, which may result in significant signaling overhead.

[0149] In view of this, this application proposes an identification update method in which the AMF can send an update rule to the terminal, which can be used to update the terminal identification. In this way, the terminal can automatically update the terminal identification according to the update rule, without having to determine whether the terminal identification needs to be updated through the access network device, nor does it require the access network device to request the core network element to allocate a new identification for the terminal. This can reduce the interaction delay caused by the terminal identification update, and further help reduce the information interaction delay between the terminal and other NFs in the core network.

[0150] The following describes in detail the identifier update method and communication device provided by this application in conjunction with the accompanying drawings. It should be understood that the technical solution of this application can be applied to a network architecture in which access network equipment and core network elements have directly connected interfaces, such as the network architectures shown in Figures 3, 4, or 5. It should be understood that the network architectures shown in Figures 3 through 5 can also be applied to the communication system shown in Figure 1.

[0151] It should be noted that the steps performed by the access network device in the following multiple figures can be performed by the BS in the network architecture shown in Figure 3, or by the CU in the network architecture shown in Figure 4, or by the O-CU-CP in the network architecture shown in Figure 5. In the embodiments shown in the following multiple figures, the various processes are described by taking the interaction process between the terminal, the access network device, the first core network element, and the second core network element as an example, but this should not constitute any limitation on the execution subject of this application. For example, the terminal can also be replaced by a component configured in the terminal, such as a chip, a chip system, or other modules that can be used to implement part or all of the functions of the terminal; the access network device can also be replaced by a component configured in the access network device, such as a chip, a chip system, or other modules that can be used to implement part or all of the functions of the access network device; the first core network element can also be replaced by a component configured in the first core network element, such as a chip, a chip system, or other modules that can be used to implement part or all of the functions of the first core network element; the second core network element can also be replaced by a component configured in the second core network element, such as a chip, a chip system, or other modules that can be used to implement part or all of the functions of the second core network element.

[0152] Among them, the first core network network element can be AMF, or it can be other core network network elements with similar functions to AMF; the second core network network element can be any core network network element among other NFs (such as NF1, NF2 and NF3, etc.) except the first core network element.

[0153] FIG9 shows an identification updating method 900 provided by an embodiment of the present application. The method 900 includes steps 901 to 902. Each step in the method 900 is described in detail below.

[0154] In step 901, a first core network element sends an update rule to a terminal, where the update rule is used to update the terminal's identifier. Correspondingly, the terminal receives the update rule from the first core network element.

[0155] In one possible implementation, the first core network element may send the update rule to the terminal via the access network device. In other words, step 901 may include: the first core network element sends the update rule to the access network device; and the access network device sends the update rule to the terminal.

[0156] For example, in conjunction with the network architectures shown in Figures 3 to 5, a NAS message may indicate an updated rule. The first core network element may include the NAS message in an Nx message and send it to the access network device. The Nx message may also indicate a terminal identifier. After receiving the Nx message, the access network device may include the NAS message indicating the updated rule in an RRC message and send it to the terminal corresponding to the terminal identifier indicated in the Nx message.

[0157] Optionally, the above-mentioned update rule indicates an update condition and / or an update method.

[0158] The update condition may refer to a condition for updating the identifier, or in other words, a trigger condition for updating the identifier. For example, the update condition may include one or more of the following:

[0159] i) the time from the last time the terminal identification was acquired reaches a preset threshold; or

[0160] ii) The message type sent to the core network element is a preset message type.

[0161] In condition i), the duration from the last time the terminal identifier was acquired may specifically refer to the duration from the current time to the last time the terminal identifier was acquired. The last time the terminal identifier was acquired may be an initial identifier received from the first core network element, or a new terminal identifier updated by the terminal according to an update rule. The duration reaching a preset threshold may specifically refer to the duration being greater than or equal to the preset threshold.

[0162] The preset threshold is, for example, 800 seconds, 1000 seconds or other values, which is not limited in the embodiment of the present application.

[0163] In one example, the update condition is: the time length between the last time the terminal identifier was obtained reaches 1000 seconds. That is, the terminal can update the terminal identifier when the time length between the current time and the last time the terminal identifier was obtained reaches 1000 seconds.

[0164] In condition ii), the core network element can be understood as the first core network element or other core network elements, and this application does not limit this.

[0165] The preset message type may include, for example, a registration request message, a service request message, or a location update message.

[0166] In one example, the update condition is: the type of message sent to the core network element is a positioning update message. When the terminal needs the network to provide positioning services, the terminal sends a positioning update message to the second core network element that provides the positioning service, thereby updating the terminal identifier.

[0167] In another example, the update condition is: the time from the last time the terminal's identifier was obtained reaches 1000 seconds, or the type of message sent to the core network element is a positioning update message. If any of the above conditions are met, the terminal can update its identifier.

[0168] As another example, the update condition is: the duration from the last time the terminal's identifier was obtained reaches 1000 seconds, and the message type sent to the core network element is a positioning update message. The terminal can update its identifier if both of the above conditions are met. Specifically, when sending a positioning update message to the core network element, the terminal can determine whether the duration from the current time to the last time the terminal's identifier was obtained reaches 1000 seconds. If so, the terminal identifier can be updated; if not, the terminal identifier may not be updated.

[0169] It should be understood that the update condition can be indicated by an update rule or predefined by the protocol, and this application does not limit this. It is understood that if the update rule is predefined, the update rule can indicate the update method without indicating the update condition. Of course, the update rule can also indicate the update condition, and the terminal executes the update condition according to the update condition indicated by the update rule, or in other words, executes the update condition indicated by the update rule as an update condition with higher priority.

[0170] The updating method may refer to a method for updating the identifier, for example, it may be a certain algorithm or rule, etc., without limitation.

[0171] Exemplarily, the above-mentioned updating method includes: updating based on a preset sequence or updating based on a preset generation function.

[0172] The sequence includes multiple identifiers to be used. In other words, the sequence can be regarded as a set consisting of multiple identifiers to be used. Therefore, the sequence can also be called an identifier set. This application does not limit the specific form of the sequence.

[0173] For example, the sequence may be {001, 002, 003, 004, ..., 100}. If the terminal can sequentially update the terminal identifier according to the order of the identifiers to be used in the sequence, for example, if the initial identifier obtained by the terminal is 000, the terminal can update the terminal identifier once each time the update condition is met. The terminal identifier can be updated sequentially to: 001, 002, ..., and so on.

[0174] The above generation function is used to generate an identifier to be used, or in other words, the generation function can be used to generate a new terminal identifier.

[0175] The generation function may be used to generate a terminal identifier to be used next time based on a terminal identifier generated last time. The terminal identifier generated last time may be an initial identifier of the terminal or an updated identifier of the terminal.

[0176] In one example, the generating function may be: f(n+1)=[2f(n)+1]mod100. The terminal may update the terminal identifier each time the update condition is met. For example, if the identifier f(n) obtained by the terminal is 001, the updated identifier f(n+1) of the terminal is 003.

[0177] In step 902, the terminal updates its identification according to the update rule.

[0178] When any one or both of the above update conditions are met, the terminal can update the terminal identification according to the above update method.

[0179] Based on the above solution, the first core network element can send an update rule to the terminal, which can be used to update the terminal's identity. In this way, the terminal can automatically update its identity according to the update rule, without having to rely on the access network device to determine whether the terminal's identity needs to be updated, nor does it need to request the core network element to allocate a new identity for the terminal. This can reduce the interaction delay caused by the terminal identity update, and further help reduce the information exchange delay between the terminal and other NFs in the core network.

[0180] Optionally, the method further includes: the first core network element sending a first message to the terminal, where the first message indicates an initial identifier of the terminal. Correspondingly, the terminal receives the first message from the first core network element.

[0181] In one possible implementation, the first core network element may send the first message to the terminal via the access network device. In other words, the first core network element sends the first message to the access network device; and the access network device sends the first message to the terminal.

[0182] For example, in conjunction with the network architectures shown in Figures 3 to 5, the first message may be a NAS message, which may indicate the initial identifier of the terminal. The first core network element may carry the NAS message in an Nx message and send it to the access network device. The Nx message may also indicate the initial identifier of the terminal. After receiving the Nx message, the access network device may carry the NAS message in an RRC message and send it to the terminal corresponding to the initial identifier of the terminal indicated in the Nx message.

[0183] In one possible design, information indicating the update rule is carried in a first message. In other words, the first message may indicate the initial identifier of the terminal and the update rule. For example, the first message carries the initial identifier of the terminal and the update rule. For the first core network element, the sending of the update rule and the sending of the first message in step 901 may be the same sending step. Correspondingly, for the terminal, the receiving of the update rule and the receiving of the first message in step 901 may be the same receiving step.

[0184] Furthermore, the first message also indicates the allocation time of the initial identifier of the terminal.

[0185] As previously mentioned, one possible design is for the update condition to include the time since the last time the terminal's identifier was acquired reaching a preset threshold. Since the identifier obtained by the terminal for the first time is the initial identifier, the terminal can use the time of allocation of the initial identifier as the starting time for determining whether the terminal identifier needs to be updated. Based on this starting time, the terminal can determine whether the terminal identifier needs to be updated and when to update it.

[0186] Alternatively, in another implementation, the first message may not indicate the allocation time of the terminal's initial identifier. In this case, the terminal may use the moment of receiving the initial identifier as the starting moment for the terminal to determine whether the terminal identifier needs to be updated.

[0187] When a terminal needs to obtain services from the core network, it can request the first core network element to select a suitable NF for it.

[0188] Optionally, the method further includes the terminal sending a second message to the first core network element, the second message indicating the identifier most recently acquired by the terminal, the second message being used to request selection of a functional network element. Correspondingly, the first core network element receives the second message from the terminal.

[0189] It should be understood that the identifier obtained most recently may be an initial identifier received from the first core network element, or may be an identifier updated by the terminal according to an update rule.

[0190] In one possible implementation, the terminal may send the second message to the first core network element via the access network device. In other words, the terminal sends the second message to the access network device; and the access network device sends the second message to the first core network element.

[0191] Exemplarily, in conjunction with the network architecture shown in Figures 3 to 5, the second message may be a NAS message, which may indicate the identifier most recently acquired by the terminal. The terminal may carry the NAS message in an RRC message and send it to the access network device. The RRC message may also indicate the identifier of the first core network element. After receiving the RRC message, the access network device may carry the NAS message in an Nx message and send it to the first core network element corresponding to the first core network element identifier indicated in the RRC message.

[0192] Optionally, the method further includes: the first core network element sending a third message to the terminal, the third message indicating an identifier of the second core network element, the second core network element being the selected functional network element. Correspondingly, the terminal receives the third message from the first core network element.

[0193] One possible implementation is that the first core network element may send the third message to the terminal via the access network device. In other words, the first core network element sends the third message to the access network device; and the access network device sends the third message to the terminal.

[0194] For example, in conjunction with the network architectures shown in Figures 3 to 5, the third message may be a NAS message, which may indicate the identifier of the second core network element. The first core network element may include the NAS message in an Nx message and send it to the access network device. The Nx message may also indicate the terminal identifier. Optionally, the Nx message may also indicate the second core network element identifier. After receiving the Nx message, the access network device may include the NAS message in an RRC message and send it to the terminal corresponding to the terminal identifier indicated in the Nx message.

[0195] The above-mentioned functional network element can be a second core network network element or other core network elements, and the embodiment of the present application does not make any specific limitations on this.

[0196] Optionally, the method further includes: the first core network element sending a fourth message to the second core network element, the fourth message indicating an update rule for the terminal identifier and the initial identifier of the terminal. Correspondingly, the second core network element receives the fourth message from the first core network element.

[0197] Exemplarily, in combination with the network architecture shown in Figures 3 to 5, the above-mentioned fourth message may be an Ny message, which may indicate the update rule of the terminal identifier and the initial identifier of the terminal, and the first core network element may send the Ny message to the second core network element.

[0198] Furthermore, the fourth message indicates the allocation time of the initial identifier of the terminal.

[0199] As mentioned above, the initial identifier allocation time is the starting time when the second core network element determines whether the terminal identifier needs to be updated. Therefore, the second core network element can determine whether the terminal identifier needs to be updated based on the starting time and can update it synchronously with the terminal.

[0200] Furthermore, the method also includes: the second core network element may update the terminal identifier according to the above-mentioned update rule.

[0201] For an explanation of the update rules, please refer to the relevant description in the above step 901. For a specific process of the second core network element updating the terminal identifier according to the update rules, please refer to the relevant description in the above step 902, which will not be repeated here.

[0202] Based on the above solution, the first core network element can send update rules to the terminal at the same time as allocating an initial identifier for the terminal. When the terminal needs to obtain services from the core network, the terminal identifier update rules and the initial identifier of the terminal can be sent to the selected second core network element. As a result, the terminal and the functional network element can update the terminal identifier based on the same update rules, without having to rely on the first core network element to update the terminal identifier or frequently send updated terminal identifiers to the terminal and functional network elements. This helps save signaling overhead and reduces the information exchange delay between the terminal and the second core network element.

[0203] For example, Figure 10 is an identification update method 1000 provided in an embodiment of the present application. The identification update method 1000 shows the following three processes: process 1 (terminal identification allocation), process 2 (functional network element selection), and process 3 (information interaction between the terminal and the second core network network element). The method 1000 shown in Figure 10 is based on the method 900 provided in Figure 9, and shows a more complete processing logic of the identification update method. The following description focuses on the steps that are different from those in method 900. The steps that are the same as those in method 900, as well as the description of the same terms, can refer to the relevant description in the above method 900 and will not be repeated.

[0204] Process 1 (terminal identification allocation) includes steps 1001 to 1005, and each step is described in detail below.

[0205] In step 1001, the terminal sends an RRC message to the access network device. The RRC message may include: a NAS message and a first core network element identifier. The NAS message is used to request the first core network element to allocate a terminal identifier.

[0206] In step 1002 , the access network device sends an Nx message to the first core network element. The Nx message may include the NAS message received in step 1001 .

[0207] In step 1003, the first core network element allocates an initial identifier to the terminal and determines a rule for updating the terminal identifier.

[0208] The update rules of the terminal identification have been described in detail in method 900. Please refer to the relevant description in method 900 and will not be repeated here.

[0209] In step 1004, the first access network element sends an Nx message to the access network device. The Nx message may include: the terminal identifier and a NAS message sent by the first core network element to the terminal. The NAS message may indicate the terminal initial identifier, the allocation time of the initial identifier, and the update rule of the terminal identifier.

[0210] The allocation time of the initial identifier has been described in detail in the above method 900. Please refer to the relevant description in method 900 and will not be repeated here.

[0211] In step 1005 , the access network device sends an RRC message to the terminal. The RRC message may include the NAS message received in step 1004 .

[0212] Process 2 (functional network element selection) may include steps 1006 to 1011. When the terminal requires the network to provide a certain service, the first core network element will select a suitable functional network element for the terminal. Each step is described in detail below.

[0213] In step 1006, the terminal sends an RRC message to the access network device. The RRC message may include: the first core network network element identifier and a NAS message sent by the terminal to the first core network network element. The NAS message is used to request the first core network network element to select a suitable functional network element (such as the second core network network element). The NAS message may indicate the terminal identifier.

[0214] In step 1007 , the access network device sends an Nx message to the first core network element. The Nx message may include the NAS message received in step 1006 .

[0215] In step 1008, the first core network element selects a suitable functional network element (such as the second core network element) for the terminal based on the content of the NAS message, and records the identifier of the selected functional network element (such as the second core network element).

[0216] The functional network element selected by the first core network element for the terminal may be the second core network element, or other core network elements, which is not limited in this embodiment of the present application.

[0217] In step 1009, the first core network element sends an Nx message to the access network device. The Nx message may include: the terminal identifier and an NAS message sent by the first core network element to the terminal. The NAS message may indicate the identifier of the second core network element. Optionally, the Nx message also includes the identifier of the second core network element.

[0218] In step 1010, the first core network element sends an Ny message to the second core network element. The Ny message may indicate the initial identifier of the terminal, the allocation time of the initial identifier, and the update rule of the terminal identifier.

[0219] The Ny message may be used to notify the second core network element that it can provide services for the terminal indicated by the initial terminal identifier, and may also indicate that the second core network element can update the terminal identifier according to the above-mentioned update rule.

[0220] The allocation time of the initial identifier has been described in detail in the above method 900. Please refer to the relevant description in method 900 and will not be repeated here.

[0221] In step 1011 , the access network device sends an RRC message to the terminal. The RRC message may include the NAS message received in step 1009 .

[0222] The above step 1010 and the above step 1011 may be executed simultaneously or at different times, without limitation.

[0223] Process 3 (information interaction between the terminal and the second core network element) may include steps 1012 to 1016, and each step is described in detail below.

[0224] It should be understood that in this process, the terminal identifier used by the terminal and the second core network element can be the initial identifier assigned to the terminal by the first core network element, or the terminal identifier updated according to the terminal identifier update rule.

[0225] In step 1012, the terminal determines whether a terminal identity update is required based on the terminal identity update rule. If an update is required (i.e., the terminal identity update condition is met), step 1013 is executed to update the terminal identity according to the update method; otherwise, the terminal identity update is not performed, i.e., step 1013 is not executed.

[0226] The updating of the terminal identification according to the updating rule by the terminal has been described in detail in the above method 900 , and reference may be made to the relevant description in the method 900 , which will not be repeated here.

[0227] In step 1014, the second core network element determines whether a terminal identifier update is required based on the terminal identifier update rule. If an update is required (i.e., the terminal identifier update conditions are met), step 1015 is executed to update the terminal identifier according to the update method. Otherwise, the terminal identifier is not updated, i.e., step 1015 is not executed.

[0228] The updating of the terminal identifier according to the updating rule by the second core network element is similar to the updating of the terminal identifier according to the updating rule by the terminal in the above method 900, and will not be repeated herein.

[0229] In addition, the sequence numbers of steps 1012, 1013 and steps 1014, 1015 do not imply a precedence in their execution order. For example, when the update condition of the above-mentioned update rule is that the time length from the last time the terminal's identifier was obtained reaches a preset threshold, the terminal updating the terminal's identifier in step 1013 and the second core network element updating the terminal's identifier in step 1015 can be executed simultaneously. For another example, when the update condition of the above-mentioned update rule is that the message type sent by the terminal to the second core network element is a preset message type, and the NAS message sent by the terminal to the second core network element through the access network device is a preset message type, the terminal can execute step 1013 to update the terminal's identifier; when the NAS message received from the terminal by the second core network element through the access network device is a preset message type, the second core network element can execute step 1015 to update the terminal's identifier. For another example, steps 1012 and 1013 can be executed simultaneously or asynchronously, without limitation.

[0230] In step 1016, the terminal sends an RRC message to the access network device. The RRC message may include the following information: the second core network network element identifier, the terminal identifier, and a NAS message sent by the terminal to the second core network network element. The NAS message may indicate the terminal identifier.

[0231] In step 1017 , the access network device sends an Nx message to the corresponding second core network element. The RRC message may include the NAS message received in step 1014 .

[0232] In step 1018, the second core network element determines whether to provide service to the terminal. If the terminal identifier stored in the second core network element includes the terminal identifier carried in the NAS message, the second core network element can provide service to the terminal; otherwise, the second core network element cannot provide service to the terminal.

[0233] The terminal identifier stored by the second core network element may be understood as the initial terminal identifier obtained by the second core network element, or the terminal identifier updated by the second core network element according to a terminal identifier update rule.

[0234] Based on the above solution, the first core network element can send an update rule to the terminal. This update rule can be used to update the terminal's identifier. In this way, the terminal can automatically update its identifier based on the update rule, without having to rely on the access network device to determine whether the terminal's identifier needs to be updated, nor does the access network device need to request a new identifier from the core network element. Furthermore, when the first core network element sends the update rule to the terminal, it also assigns an initial identifier to the terminal and sends the initial identifier assignment time to the terminal. When the terminal requires services from the core network, the terminal identifier update rule, the initial identifier, and the initial identifier assignment time can be sent to a selected second core network element. Thus, the terminal and the functional network element can update their terminal identifier based on the same update rule, without having to rely on the first core network element to update the terminal's identifier or frequently send updated terminal identifiers to the terminal and the functional network element. This helps save signaling overhead and reduces information exchange latency between the terminal and the second core network element.

[0235] It should be understood that the processes shown in Figures 9 and 10 are merely examples and should not constitute any limitation to the present application. In other embodiments, these processes may also include more or fewer steps.

[0236] It should also be understood that the size of the serial numbers of the above-mentioned processes does not 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 embodiments of this application.

[0237] Figures 11 and 12 are schematic block diagrams of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the terminal, the functions of the first core network element, the functions of the second core network element, or the functions of the access network device in the above-mentioned method embodiments, thereby also achieving the beneficial effects of the above-mentioned method embodiments.

[0238] A communication device provided in this application is shown in FIG11 , where the communication device 1100 includes a communication unit 1110 and a processing unit 1120. The communication unit 1110 may be used to perform receiving or sending actions, and the processing unit 1120 may be used to perform actions other than receiving and sending, such as generating information or messages, processing received information or messages, and so on.

[0239] In one possible design, the communication device 1100 is used to implement the functions of the terminal in the method embodiment shown in Figures 9 or 10. For example, the communication device can be a terminal, or a component configured in a terminal (such as a chip, a chip system, a processor, etc.), or a logic module or software that can implement some or all of the functions of the terminal.

[0240] Exemplarily, when the communication device 1100 is used to implement the function of method 900, the communication unit 1110 is used to receive update rules from the first core network network element, and the update rules are used to update the terminal identification; the processing unit 1120 is used to update the terminal identification according to the update rules.

[0241] Optionally, the update rule indicates an update condition and / or an update method.

[0242] Optionally, the update condition includes one or more of the following: the duration from the last time the identifier of the terminal was acquired reaches a preset threshold; or the message type sent to the core network element is a preset message type.

[0243] Optionally, the updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes a plurality of identifiers to be used, and the generation function is used to generate the identifiers to be used.

[0244] Optionally, the communication unit 1110 is further configured to receive a first message from the first core network element, where the first message indicates an initial identifier of the terminal and an allocation time of the initial identifier.

[0245] Optionally, the update rule is carried in the first message.

[0246] Optionally, the communication unit 1110 is also used to send a second message to the first core network network element, the second message indicating the identifier most recently obtained by the terminal, and the second message is used to request selection of a functional network element; and to receive a third message from the first core network network element, the third message indicating the identifier of the second core network network element, and the second core network element is the selected functional network element.

[0247] Another possible design is that the communication device 1100 is used to implement the functions of the first core network element in the method embodiment shown in Figure 9 or Figure 10. For example, the communication device can be the first core network element, or a component configured in the first core network element (such as a chip, a chip system, a processor, etc.), or a logic module or software capable of implementing some or all of the functions of the first core network element.

[0248] Exemplarily, when the communication device 1100 is used to implement the function of the method 900, the processing unit 1120 is used to determine an update rule, where the update rule is used to update the identifier of the terminal; and the communication unit 1110 is used to send the update rule to the terminal.

[0249] Optionally, the update rule indicates an update condition and / or an update method.

[0250] Optionally, the update condition includes one or more of the following: the time from the last time the identifier of the terminal was acquired reaches a preset threshold; or the type of the message received from the terminal is a preset message type.

[0251] Optionally, the updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes a plurality of identifiers to be used, and the generation function is used to generate the identifiers to be used.

[0252] Optionally, the communication unit 1110 is further configured to send a first message to the terminal, where the first message indicates an initial identifier of the terminal and an allocation time of the initial identifier.

[0253] Optionally, the update rule is carried in the first message.

[0254] Optionally, the communication unit 1110 is also used to receive a second message from the terminal, the second message indicating the identifier most recently obtained by the terminal, and the second message is used to request selection of a functional network element; and to send a third message to the terminal, the third message indicating the identifier of a second core network element, and the second core network element is the selected functional network element; and to send a fourth message to the second core network element, the fourth message indicating the update rule of the terminal, the initial identifier of the terminal, and the allocation time of the initial identifier.

[0255] In another possible design, the communication device 1100 is used to implement the functions of the second core network element in the method embodiment shown in Figure 9 or Figure 10. For example, the communication device can be the second core network element, or a component configured in the second core network element (such as a chip, a chip system, a processor, etc.), or a logic module or software capable of implementing some or all of the functions of the second core network element.

[0256] Exemplarily, when the communication device 1100 is used to implement the function of method 900, the communication unit 1110 is used to receive a fourth message from the first core network network element, wherein the fourth message indicates the update rule of the terminal, the initial identifier of the terminal, and the allocation time of the initial identifier; the processing unit 1120 is used to update the identifier of the terminal according to the update rule.

[0257] Optionally, the update rule indicates an update condition and / or an update method.

[0258] Optionally, the update condition includes one or more of the following: the time from the last time the identifier of the terminal was acquired reaches a preset threshold; or the type of the message received from the terminal is a preset message type.

[0259] Optionally, the updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes a plurality of identifiers to be used, and the generation function is used to generate the identifiers to be used.

[0260] It should also be understood that the communication unit 1110 in the communication device 1100 can also be referred to as a transceiver unit. The communication unit 1110 may include a transmitting module but not a receiving module. Alternatively, the communication unit 1110 may include a receiving module but not a transmitting module. The specific implementation depends on whether the above-mentioned solution executed by the communication device 1100 includes both transmitting and receiving actions. The receiving module may be used to perform the receiving action in the above-mentioned solution, and the transmitting module may be used to perform the transmitting action in the above-mentioned solution.

[0261] It is understandable that the division of units in the above-mentioned device is merely a division of logical functions, and each function may correspond to a functional unit, or two or more functions may be integrated into one functional unit. In actual implementation, all or part of the units may be integrated into one physical entity, or distributed across different physical entities. In addition, the above-mentioned functional units may be implemented in the form of hardware, software, or a combination of hardware and software. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0262] Another communication device provided by the present application is shown in FIG12 , where the communication device 1200 includes at least one processor 1210. The at least one processor 1210 may be configured to execute computer programs or instructions in a memory to implement the steps performed by the terminal, the steps performed by the first core network element, or the steps performed by the second core network element in the method embodiments shown in FIG9 or FIG10 .

[0263] Optionally, the communication device 1200 may further include at least one memory 1220 for storing instructions executed by the processor 1210 or storing input data required by the processor 1210 to execute instructions or storing data generated after the processor 1210 executes instructions. The at least one processor 1210 and the at least one memory 1220 may be provided separately. For example, each memory may be connected to one or more processors so that the connected processors can read information from the memory and store and / or write information in the memory. Alternatively, the at least one processor 1210 and the at least one memory 1220 may be integrated together, for example, one or more memories may be integrated into a processor.

[0264] Optionally, the communication device 1200 further includes an interface circuit 1230 that can be used to transmit data and / or signaling. The at least one processor 1210 and the interface circuit 1230 are coupled to each other. It is understood that the interface circuit 1230 can be a transceiver, input / output circuit, bus, module, pin, or other type of communication interface, wherein the input circuit of the input / output circuit can be used for receiving, and the output interface can be used for sending.

[0265] Optionally, the communication device 1200 further includes a power supply circuit 1240 , which can be used to supply power to the communication device 1200 .

[0266] When the communication device 1200 is used to implement the method shown in Figure 9 or Figure 10, the processor 1211 is used to perform the functions of the above-mentioned processing unit, and the interface circuit 1220 is used to perform the functions of the above-mentioned receiving unit and / or sending unit. Whether the interface circuit 1220 is used for sending or receiving can be determined by whether it is used to perform a sending action or a receiving action in the solution implemented by the communication device 1200.

[0267] It is understood that when the communication device 1200 is a communication device (e.g., a terminal, a first core network element, or a second core network element), the interface circuit 1220 may be a transceiver, specifically including a transmitter and a receiver, where the transmitter is used to transmit signals and the receiver is used to receive signals. When the communication device 1200 is a chip used in a communication device, the interface circuit 1220 may be an input / output circuit, a bus, a module, a pin, or other type of communication interface, where the input circuit in the input / output circuit may be used for receiving, and the output interface may be used for transmitting.

[0268] It should be understood that in the communication device 1200 shown in FIG. 12 , the processor 1210 may correspond to the processing unit 1120 in the above communication device 1100 , and the interface circuit 1220 may correspond to the communication unit 1110 in the above communication device 1100 .

[0269] It should also be understood that the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which can be electrical, mechanical or other forms, and is used for information exchange between devices, units or modules. In the embodiments of the present application, the specific connection medium between the at least one processor 1210, the at least one memory 1220, the interface circuit 1230 and the power supply circuit 1240 is not limited. In Figure 11, the embodiment of the present application shows that the processor 1210, the memory 1220, the interface circuit 1230 and the power supply circuit 1240 are connected via a bus 1250. The bus 1250 is represented by a bold line in Figure 12, and the connection method between other components is only for schematic illustration and is not limited. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one bold line is used in Figure 12, but it does not mean that there is only one bus or one type of bus.

[0270] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0271] The memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may 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), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0272] The present application also provides a communication system, which includes one or more of the aforementioned terminal, first core network element or second core network element.

[0273] The present application also provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables the computer to execute the method executed by the terminal in the embodiment shown in Figure 9 or Figure 10, the method executed by the first core network element, or the method executed by the second core network element.

[0274] The present application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed, the computer executes the method executed by the terminal, the method executed by the first core network element, or the method executed by the second core network element in the embodiments shown in FIG. 9 or FIG. 10 .

[0275] The terms "unit," "module," and the like used in this specification may be used to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution.

[0276] Those skilled in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented using electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. In the several embodiments provided in this application, it should be understood that the disclosed devices, equipment, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not performed. In addition, the coupling or direct coupling or communication connection shown or discussed can be through some interface, indirect coupling or communication connection of devices or units, and can be electrical, mechanical, or other forms.

[0277] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of the solution of this embodiment according to actual needs.

[0278] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0279] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (program) are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0280] If this function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0281] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for updating an identifier, characterized in that: The method comprises: receiving an update rule from a first core network element, where the update rule is used to update an identifier of a terminal; According to the update rule, the identification of the terminal is updated.

2. The method according to claim 1, characterized in that The update rule indicates an update condition and / or an update method.

3. The method according to claim 2, characterized in that The update conditions include one or more of the following: The time from the last time the terminal identifier was acquired reaches a preset threshold; or The message type sent to the core network element is a preset message type.

4. The method according to claim 2 or 3, characterized in that The updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes a plurality of identifiers to be used, and the generation function is used to generate the identifiers to be used.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: A first message is received from the first core network element, where the first message indicates an initial identifier of the terminal and an allocation time of the initial identifier.

6. The method according to claim 5, characterized in that The update rule is carried in the first message.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: Sending a second message to the first core network element, where the second message indicates the identifier most recently acquired by the terminal, and the second message is used to request selection of a functional network element; A third message is received from the first core network element, where the third message indicates an identifier of a second core network element, and the second core network element is a selected functional network element.

8. A method for updating an identifier, characterized in that: The method comprises: Determining an update rule, wherein the update rule is used to update the identification of the terminal; The updated rule is sent to the terminal.

9. The method according to claim 8, characterized in that The update rule indicates an update condition and / or an update method.

10. The method according to claim 9, characterized in that The update conditions include one or more of the following: The time from the last time the terminal identifier was acquired reaches a preset threshold; or The message type sent by the terminal to the core network element is a preset message type.

11. The method according to claim 9 or 10, characterized in that The updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes a plurality of identifiers to be used, and the generation function is used to generate the identifiers to be used.

12. The method according to any one of claims 8 to 11, characterized in that The method further comprises: A first message is sent to the terminal, where the first message indicates an initial identifier of the terminal and an allocation time of the initial identifier.

13. The method according to claim 12, characterized in that The update rule is carried in the first message.

14. The method according to any one of claims 8 to 13, characterized in that The method further comprises: receiving a second message from the terminal, where the second message indicates an identifier most recently acquired by the terminal, and the second message is used to request selection of a functional network element; Sending a third message to the terminal, where the third message indicates an identifier of a second core network element, where the second core network element is the selected functional network element; A fourth message is sent to the second core network element, where the fourth message indicates an update rule for the terminal identifier, an initial identifier of the terminal, and an allocation time of the initial identifier.

15. A method for updating an identifier, characterized in that: The method comprises: receiving a fourth message from the first core network network element, the fourth message indicating an identifier update rule of the terminal, an initial identifier of the terminal, and an allocation time of the initial identifier; According to the update rule, the identification of the terminal is updated.

16. The method according to claim 15, characterized in that The update rule indicates an update condition and / or an update method.

17. The method according to claim 16, characterized in that The update conditions include one or more of the following: The time from the last time the terminal identifier was acquired reaches a preset threshold; or The type of the message received from the terminal is a preset message type.

18. The method according to claim 16 or 17, characterized in that The updating method includes: updating based on a preset sequence or updating based on a preset generation function, the sequence includes a plurality of identifiers to be used, and the generation function is used to generate the identifiers to be used.

19. A communication device, characterized in that: The method comprises one or more functional units for implementing the method according to any one of claims 1 to 18.

20. A communication device, characterized in that: The device comprises a processor configured to execute instructions so as to enable the communication device to implement the method according to any one of claims 1 to 18.

21. The communication device according to claim 20, wherein: Also included is a memory for storing the instructions.

22. The communication device according to claim 20 or 21, characterized in that It also includes a communication interface for the communication device to communicate with other devices.

23. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 18 is performed.

24. A computer program product, characterized in that A computer program is included which, when executed, causes the method according to any one of claims 1 to 18 to be performed.

25. A communication system, characterized in that: It includes a first core network element and a second core network element, the first core network element is used to execute the method according to any one of claims 8 to 14, and the second core network element is used to execute the method according to any one of claims 15 to 18.

Images