Wireless communication method, and communication device

Abstract

Provided are a wireless communication method, and a communication device. The method comprises: a first network element sending a first temporary identifier of a terminal device to a second network element; and the first network element receiving a permanent identifier of the terminal device that is sent by the second network element. In the embodiments of the present application, a first network element can send a first temporary identifier of a terminal device to a second network element, so as to acquire a permanent identifier of the terminal device from the second network element. In this way, when an access network element communicates with the first network element by means of a service-based interface, the first network element can also acquire the permanent identifier of the terminal device, such that the first network element subsequently communicates with other network elements (e.g., a core network element) on the basis of the permanent identifier of the terminal device, thereby facilitating the management of the terminal device by the other network elements on the basis of the permanent identifier of the terminal device.

Description

Wireless communication methods and communication equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method and device for wireless communication. Background Technology

[0002] In traditional communication systems, mobility management elements (MMIs) can store the association between temporary and permanent identifiers of terminal devices. Thus, access network elements can communicate with MMIs based on the temporary identifiers of terminal devices. Subsequently, the MMI can determine the permanent identifier of the terminal device based on the temporary identifier and the association. With technological advancements, in later evolved communication systems, access network elements can interact with core network elements through service-oriented interfaces. In this case, access network elements can communicate with other core network elements without needing to connect to the MMI and then communicate through the MMI. That is, access network elements can bypass the MMI and interact with other core network elements (e.g., session management function (SMF) elements or policy control function (PCF) elements).

[0003] However, as mentioned above, access network elements communicate based on the temporary identifier of the terminal device, while other network elements (e.g., other core network elements) interact based on the permanent identifier of the terminal device. In this case, if the access network element communicates with other network elements based on the temporary identifier, the other network elements will not be able to identify the terminal device corresponding to the temporary identifier, resulting in the inability to manage the terminal device.

[0004] Summary of the Invention

[0005] This application provides a method and apparatus for wireless communication. The various aspects covered in this application are described below.

[0006] In a first aspect, a wireless communication method is provided, comprising: a first network element sending a first temporary identifier of a terminal device to a second network element; and the first network element receiving a permanent identifier of the terminal device sent by the second network element.

[0007] In a second aspect, a wireless communication method is provided, comprising: a second network element receiving a first temporary identifier of a terminal device sent by a first network element; and the second network element sending a permanent identifier of the terminal device to the first network element.

[0008] Thirdly, a wireless communication method is provided, comprising: an access network element sending a permanent identifier of a terminal device to a first network element through a service interface.

[0009] Fourthly, a wireless communication method is provided, comprising: a first network element receiving a permanent identifier of a terminal device sent by an access network element through a service interface.

[0010] Fifthly, a communication device is provided, the communication device being a first network element, comprising: a transmitting unit for transmitting a first temporary identifier of a terminal device to a second network element; and a receiving unit for receiving a permanent identifier of the terminal device transmitted by the second network element.

[0011] In a sixth aspect, a communication device is provided, the communication device being a second network element, comprising: a receiving unit for receiving a first temporary identifier of a terminal device sent by a first network element; and a sending unit for sending a permanent identifier of the terminal device to the first network element.

[0012] In a seventh aspect, a communication device is provided, the communication device being an access network element, comprising: a transmitting unit, used to transmit a permanent identifier of a terminal device to a first network element through a service interface.

[0013] Eighthly, a communication device is provided, the communication device being a first network element, comprising: a receiving unit, configured to receive a permanent identifier of a terminal device sent by an access network element through a service-oriented interface.

[0014] A ninth aspect provides a communication device, including a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to invoke the computer programs in the memory to cause the communication device to perform some or all of the steps of the methods described in the preceding aspects.

[0015] Tenthly, embodiments of this application provide a communication system including the aforementioned communication device. In another possible design, the system may further include other devices that interact with the communication device as described in the embodiments of this application.

[0016] Eleventhly, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.

[0017] In a twelfth aspect, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0018] In a thirteenth aspect, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects.

[0019] In this embodiment, the first network element can send a first temporary identifier of the terminal device to the second network element in order to obtain the permanent identifier of the terminal device from the second network element. In this way, when the access network element communicates with the first network element through the service interface, the first network element can also obtain the permanent identifier of the terminal device. This allows the first network element to communicate with other network elements (e.g., core network elements) based on the permanent identifier of the terminal device, which helps other network elements manage the terminal device based on the permanent identifier of the terminal device. Attached Figure Description

[0020] Figure 1 is a schematic diagram of a communication system architecture applicable to an embodiment of this application.

[0021] Figure 2 is an architecture diagram of the communication system in which AN interacts with other network elements in the core network through service-oriented interfaces.

[0022] Figure 3 is a schematic flowchart of a wireless communication method according to an embodiment of this application.

[0023] Figure 4 is a schematic diagram of the scheme for the first network element to obtain the permanent identifier of the terminal device in an embodiment of this application.

[0024] Figure 5 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application.

[0025] Figure 6 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application.

[0026] Figure 7 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application.

[0027] Figure 8 is a flowchart of a wireless communication method according to another embodiment of this application.

[0028] Figure 9 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application.

[0029] Figure 10 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application.

[0030] Figure 11 is a schematic diagram of a communication device according to an embodiment of this application.

[0031] Figure 12 is a schematic diagram of a communication device according to an embodiment of this application.

[0032] Figure 13 is a schematic diagram of a communication device according to an embodiment of this application.

[0033] Figure 14 is a schematic diagram of a communication device according to an embodiment of this application.

[0034] Figure 15 is a schematic structural diagram of a communication device according to an embodiment of this application. Detailed Implementation

[0035] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0036] Figure 1 is a schematic diagram of a communication system architecture applicable to an embodiment of this application. This network architecture may include terminal equipment, access network (AN) elements, and core network elements.

[0037] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: 5th generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems, satellite communication systems, and so on.

[0038] The terminal device in this application embodiment can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), MT, remote station, remote terminal, mobile device, user terminal, terminal, wireless core network element, user agent, or user device. The terminal device in this application embodiment can be a device that provides voice and / or data connectivity to a user, and can be used to connect people, objects, and machines, such as a handheld device with wireless connectivity, vehicle-mounted device, etc. The terminal devices in the embodiments of this application can be mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. Optionally, the terminal device can be used to act as a base station. For example, the terminal device can act as a dispatching entity, providing sidelink signals between terminal devices in vehicle-to-everything (V2X) or device-to-device (D2D) communications. For example, cellular phones and cars communicate with each other using sidelink signals. Cellular phones and smart home devices communicate without relaying communication signals through base stations.

[0039] Access network elements can be any network device that allows a terminal to wirelessly access the network architecture. They are primarily responsible for air interface-side radio resource management, Quality of Service (QoS) management, data compression, and encryption. Access network elements can also be called radio access network (RAN) devices, such as base stations. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNB (MeNB), secondary eNB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the access network elements.

[0040] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0041] In some deployments, the access network element in this application embodiment may refer to a CU or a DU, or the access network element may include both a CU and a DU. The gNB may also include an AAU.

[0042] The core network elements can be categorized into several types, including User Plane Function (UPF) elements, Access and Mobility Management Function (AMF) elements, SMF elements, PCF elements, Application Function (AF) elements, Data Network (DN) elements, Network Slice Selection Function (NSSF) elements, Authentication Server Function (AUSF) elements, Unified Data Management (UDM) elements, Network Exposure Function (NEF) elements, Network Repository Function (NRF) elements, and Network Slice-Specific Authentication and Authorization Function (NSSAAF). UPF elements are primarily responsible for user data transmission. The other elements, which can be referred to as Control Plane Function elements, are mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control to ensure reliable and stable user data transmission.

[0043] UPF network elements can be used to forward and receive data from terminals. For example, a UPF network element can receive service data from the data network and transmit it to the terminal through the access network element; a UPF network element can also receive user data from the terminal through the access network element and forward it to the data network. The transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element can include: the user plane connection between the UPF network element and the access network element, and the establishment of a channel between the access network element and the terminal. The user plane connection allows for the establishment of a QoS flow for data transmission between the UPF network element and the access network element.

[0044] AMF network elements can be used to manage terminal access to the core network, such as terminal location updates, network registration, access control, terminal mobility management, and terminal attachment and detachment. When providing services for a terminal's session, AMF network elements can also provide control plane storage resources for that session to store session identifiers and the associated SMF network element identifiers.

[0045] SMF network elements can be used to select user plane network elements for terminals, redirect user plane network elements for terminals, assign Internet Protocol (IP) addresses to terminals, establish bearers (also known as sessions) between terminals and UPF network elements, modify and release sessions, and perform QoS control.

[0046] PCF network elements are used to provide policies to AMF and SMF network elements, such as QoS policies and slice selection policies.

[0047] AF network elements are used to interact with 3GPP core network elements to support the routing of application-affected data, access network exposure functions, and interact with PCF network elements for policy control, etc.

[0048] A Data Network (DN) can provide data services to users for networks such as IP Multimedia Service (IMS) and the Internet. A DN can contain various application servers (AS) that provide different application services, such as carrier services, Internet access, or third-party services. The AS can implement the functions of an Application Server (AF).

[0049] NSSF is used for network slice selection and supports the following functions: selecting a set of network slice instance examples to serve the end device; determining allowed network slice selection assistance information (NSSAI), and, when necessary, determining the mapping to the subscribed single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI, and, when necessary, determining the mapping to the subscribed S-NSSAI; determining the set of AMFs that may be used to query the end device, or determining a list of candidate AMFs based on the configuration.

[0050] AUSF is used to receive AMF requests for terminal authentication. It requests a key from UDM and then forwards the issued key to AMF for authentication processing.

[0051] UDM includes functions such as generating and storing user subscription data and managing authentication data, and supports interaction with external third-party servers.

[0052] NEF is used for capability exposure, meaning that based on NEF, network capabilities can be exported to external networks. Untrusted external applications can access core network data through NEF to ensure network security. NEF can provide functions such as QoS capability exposure for external applications, event subscription, and AF request distribution.

[0053] The Network Request Forwarder (NRF) is used for the registration, management, and status detection of core network elements, thereby achieving automated management of core network elements. When a core network element starts up, it must register with the NRF before it can provide services. Registration information may include, for example, the type, address, and service list of the core network element.

[0054] In addition, some networks (such as 5G networks) have added network data analytics function (NWDAF) to the core network. Based on NWDAF, data can be collected from various network elements and network management systems in the core network, and big data statistics, analysis or intelligent data analysis can be performed to obtain network-side analysis or prediction data, thereby assisting various network elements to more effectively control terminal device access based on the data analysis results.

[0055] In some communication systems (such as 5G systems), core network elements can also be called network functions (NFs).

[0056] The network elements in Figure 1 can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions implemented on a platform (e.g., a cloud platform). It should be noted that the network architecture shown in the above figures is merely an illustrative representation of the network elements included in the overall network architecture. In this application embodiment, the network elements included in the entire network architecture are not limited.

[0057] Those skilled in the art will understand that the network architecture shown in Figure 1 does not constitute a limitation on the network architecture. In specific implementations, the network architecture may include more or fewer network elements than shown in the figure, or combine certain network elements, etc. It should be understood that AN or RAN is represented in Figure 1 as (R)AN.

[0058] In some scenarios, network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenarios in which the network devices and terminal devices are located.

[0059] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of this application, the network device may also be a base station located on land, water, or other similar locations.

[0060] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0061] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0062] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0063] The “configuration” in this application embodiment may include configuration via at least one of system messages, radio resource control (RRC) signaling, and media access control element (MAC CE).

[0064] In some embodiments of this application, "predefined" or "preset" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, "predefined" can refer to what is defined in the protocol.

[0065] In some embodiments of this application, the term "protocol" may refer to standard protocols in the field of communications, such as LTE protocols, NR protocols, and related protocols applied in future communication systems. This application does not limit the scope of the term.

[0066] As shown in Figure 1, the communication system supports service-oriented interfaces for interactions between some core network elements. However, the N1 interface between the terminal device and the AMF, the N2 interface between the AN and the AMF, and the N4 interface between the SMF and the UPF still use traditional reference points for interaction. The service-oriented architecture evolution is not complete. Therefore, in future network designs (e.g., 6G network design), designs where the AN interacts with other core network elements through service-oriented interfaces can be considered. For ease of understanding, the following section, in conjunction with Figure 2, describes the architecture of a communication system where the AN interacts with other core network elements through service-oriented interfaces. Here, the interaction between the AN and other core network elements through service-oriented interfaces can be understood as the AN accessing the bus like a 5G core network element and interacting with any core network element through a service-oriented interface.

[0067] Referring to the communication system shown in Figure 2, this system may include multiple network elements (also known as "nodes" or "devices"), such as terminal equipment, access network elements, UPF network elements, mobility management network elements (6G mobility management (MM) as shown in Figure 2), session management network elements (6G session management (SM) as shown in Figure 2), and application function (AF) network elements. The communication system may also include a data network (DN), etc. The functions of some network elements in the communication system shown in Figure 2 are the same as or similar to the functions of some network elements in the communication system shown in Figure 1. For example, the function of 6G MM is the same as or similar to the function of AMF. Similarly, the functions of 6G SM and SMF are the same as or similar.

[0068] It should be understood that in the communication system shown in Figure 2, the 5G network and the 6G network may share some NFs, such as sharing UDM, UPF and NRF.

[0069] It should be understood that the terminal device, access network element, mobility management network element (also known as "mobility management network element"), and session management network element shown in Figure 2 are merely names, and these names do not limit the devices themselves. In 6G networks and other future networks, the network elements corresponding to the terminal device, access network element, mobility management network element, and session management network element may also have other names, and this application embodiment does not specifically limit them.

[0070] Currently, in traditional communication systems (such as 5G networks), operators assign a permanent identifier (e.g., a "subscription permanent identifier" (SUPI)) to each subscriber identification module (SIM) card (or terminal device). This SUPI is a permanent identifier for the SIM card, or in other words, it is used to uniquely identify the SIM. If the SUPI is sent in plaintext over the air interface, a third party can use the permanent identifier to identify, locate, and track the user. Therefore, to avoid this privacy breach, the network also assigns a temporary identifier to the SIM card (e.g., a globally unique temporary identifier (GUTI) or a temporary mobile subscription identifier (S-TMSI)). Temporary identifiers can be changed frequently, making them more secure for identifying users.

[0071] In traditional communication systems (such as 5G systems), when terminal devices, access network devices, and the AMF (Access Module Function) interact, signaling is transmitted over the air interface. Therefore, using temporary identifiers helps improve communication security. When core network elements interact within the core network, since interactions within the core network do not involve the air interface and are inherently more secure, permanent identifiers are used to identify terminal devices. The AMF can act as a network element that converts the temporary identifier of a terminal device into a permanent identifier used by the core network elements; that is, the AMF stores the association between the temporary and permanent identifiers of the terminal device.

[0072] As described above, in traditional communication systems (such as the communication system shown in Figure 1), mobility management network elements (MMIs) can store the association between temporary identifiers (also known as "temporary identifiers") and permanent identifiers (also known as "permanent identifiers") of terminal devices. Thus, access network elements can communicate with MMIs based on the temporary identifiers of terminal devices. Subsequently, the MMI can determine the permanent identifier of the terminal device based on the temporary identifier and the association. With technological advancements, in subsequent evolved communication systems (such as the communication system shown in Figure 2), access network elements can interact with core network elements through service-oriented interfaces. In this case, access network elements can communicate with other core network elements without needing to connect to the MMI and then communicate through the MMI. That is, access network elements can bypass the MMI and interact with other core network elements (e.g., SMF or PCF).

[0073] However, as mentioned above, access network elements communicate based on the temporary identifier of the terminal device, while other network elements (e.g., other core network elements) interact based on the permanent identifier of the terminal device. In this case, if the access network element communicates with other network elements based on the temporary identifier, the other network elements will not be able to determine the terminal device corresponding to the temporary identifier, and thus the other network elements will not be able to manage the terminal device.

[0074] Taking the SMF as an example of other core network elements, if the access network element sends a temporary identifier of the terminal device to the SMF, the SMF cannot obtain the terminal device's subscription information from the UDM based on the temporary identifier of the terminal device.

[0075] Taking PCF as an example of other core network elements, if the access network element sends a temporary identifier of the terminal device to the PCF, the PCF cannot find the UE control policy of the terminal device based on the temporary identifier of the terminal device.

[0076] Therefore, to address the aforementioned problems, this application provides a scheme for obtaining the permanent identifier of a terminal device. This allows other core network elements to obtain the permanent identifier of the terminal device and manage it based on that identifier when access network elements communicate with other core networks through service interfaces. The following descriptions are based on Embodiments 1 and 2.

[0077] Example 1

[0078] Figure 3 is a schematic flowchart of a wireless communication method according to an embodiment of this application. The method shown in Figure 3 is illustrated using the interaction between a first network element and a second network element as an example. In this embodiment, the first network element and the second network element are not limited. In some implementations, the first network element and / or the second network element can be network elements located in the core network; therefore, the first network element is also called a "first core network element," and the second network element is also called a "second core network element."

[0079] In some implementations, the first network element includes one or more of the following: a session management network element (e.g., SMF and / or 6GSM); a location management network element; and a PCF. Of course, in this embodiment, the first network element can also be other network elements that need to obtain the permanent identifier of the terminal device. In some implementations, the second network element can include a mobility management network element and / or a data storage network element. The mobility management network element can, for example, include the AMF shown in Figure 1 and / or the 6G MM shown in Figure 2. Additionally, the data storage network element can, for example, include a UDM and / or an NRF. Of course, in this embodiment, the second network element can also be other network elements that store the association relationship between the temporary identifier and the permanent identifier of the terminal device (e.g., the first association, second association, or third association described below).

[0080] The method shown in Figure 3 includes steps S310 and S320.

[0081] In step S310, the first network element sends the first temporary identifier of the terminal device to the second network element.

[0082] In some implementations, the first temporary identifier may include a temporary identifier assigned to the terminal device by a mobility management network element. For example, it may include a GUTI and / or S-TMSI from a known network (e.g., 5G). Of course, in the embodiments of this application, the first temporary identifier may also be other temporary identifiers assigned to the terminal device in a future network.

[0083] In this embodiment, the method by which the first network element obtains the first temporary identifier is not limited. In some implementations, the first network element can obtain the first temporary identifier from the mobility management network element obtained by the terminal device. For example, the first network element can obtain the first temporary identifier from the terminal device through a non-access stratum (NAS) message; that is, the NAS message may include the first temporary identifier obtained by the terminal device from the mobility management network element.

[0084] In other implementations, the first network element can obtain the first temporary identifier from the access network element through a service-oriented interface. For example, an access stratum (AS) message can carry a NAS message and a first temporary identifier (the first temporary identifier can be obtained by the terminal device from the mobility management network element, for example). Correspondingly, when the access network element sends the NAS message to the first network element through the service-oriented interface, it can also send the first temporary identifier to the first network element.

[0085] In step S320, the second network element sends the permanent identifier of the terminal device to the first network element.

[0086] In some implementations, the permanent identifier may include SUPI. Of course, in the embodiments of this application, the permanent identifier of the terminal device may also be other permanent identifiers introduced in future communication systems.

[0087] In this embodiment, the first network element can send a first temporary identifier of the terminal device to the second network element in order to obtain the permanent identifier of the terminal device from the second network element. In this way, when the access network element communicates with the first network element through the service interface, the first network element can also obtain the permanent identifier of the terminal device, so that the first network element can communicate with other network elements (e.g., core network elements) based on the permanent identifier of the terminal device.

[0088] As described above, the second network element may include a data storage network element. In this case, the second network element can obtain the association between the permanent identifier of the terminal device and the first temporary identifier of the terminal device from the mobility management network element. In this embodiment, the data storage network element provides the permanent identifier of the terminal device to the first network element, which helps to reduce the load on the mobility management network element. This will be described below with reference to Figure 5.

[0089] In some implementations, the first network element can maintain the association between the first temporary identifier and the permanent identifier (also known as the first association relationship) locally, which helps reduce the signaling overhead required for the first network element to obtain the permanent identifier of the terminal device from the second network element. That is to say, the above method also includes: the first network element storing the first association relationship between the first temporary identifier and the permanent identifier.

[0090] For example, the first temporary identifier includes 5G-S-TMSI, and the permanent identifier may include 5G-GUTI. Correspondingly, the first association relationship can be represented as the association relationship between 5G-GUTI and 5G-S-TMSI. Here, 5G-GUTI may include the mobile country code (MCC), mobile network code (MNC), AMF Region ID, AMF Set ID, AMF Pointer, and 5G-TMSI. 5G-S-TMSI includes the AMF Set ID, AMF Pointer, and 5G-TMSI. The corresponding codes can be found below: <5G-GUTI>:= <mcc> <mnc><AMF Region ID><AMF Set ID><AMF Pointer><5G-TMSI>; <5G-S-TMSI>:=<AMF Set ID><AMF Pointer> <5G-TMSI>.

[0091] As described above, the first network element can maintain the first association locally. In some scenarios, the temporary identifier of the terminal device may change. For example, if the temporary identifier of the terminal device is updated from the first temporary identifier to the second temporary identifier, the first network element needs to update the first association locally maintained to the second association. In this case, the second association includes the association between the permanent identifier of the terminal device and the second temporary identifier.

[0092] In this embodiment, the type of the second temporary identifier is not limited. In some implementations, the second temporary identifier can be a TMSI or an S-TMSI.

[0093] In this embodiment, the method of updating the first temporary identifier to the second temporary identifier is not limited. Taking 5G-S-TMSI as an example, updating the first temporary identifier to the second temporary identifier may include updating the 5G-TMSI in the first temporary identifier to obtain the second temporary identifier. That is, the AMF set identifier and AMF reference point in the first temporary identifier and the second temporary identifier can be the same, and the 5G-TMSI in the first temporary identifier and the second temporary identifier can be different. Of course, in this embodiment, the AMF set identifier, AMF reference point, and 5G-TMSI in the first temporary identifier can all be different from those in the second temporary identifier.

[0094] In some implementations, the second network element can instruct the first network element to update the first association relationship to the second association relationship via the first information. That is, the above method also includes: the second network element sending the first information to the first network element, the first information instructing the first association relationship to be updated to the second association relationship.

[0095] In some implementations, the first information carries a second temporary identifier. Of course, in this embodiment, the first information may also carry a permanent identifier of the terminal device corresponding to the second temporary identifier. Alternatively, the first information may also carry a second association relationship.

[0096] As mentioned above, the second network element may include a data storage network element. In this case, if the temporary identifier of the terminal device is updated, the mobility management network element can send the association between the updated temporary identifier and the permanent identifier to the second network element. That is, if the temporary identifier of the terminal device is updated from the first temporary identifier to the second temporary identifier, the mobility management network element can send an indication message to the second network element to instruct the terminal device to update its first temporary identifier to the second temporary identifier. Correspondingly, the second network element can establish the association between the second temporary identifier and the permanent identifier of the terminal device. This will be further explained below with reference to Figure 5.

[0097] In some implementations, the aforementioned indication information can be used to carry information indicating that the first temporary identifier is changed to the second temporary identifier. In other implementations, the aforementioned indication information can be used to carry the association between the second temporary identifier and the permanent identifier. This application does not limit the implementation method of the indication information.

[0098] In some implementations, the first network element can send a first request to the second network element to request a change in the temporary identifier of the subscribed terminal device. That is, the method further includes: the first network element sending a first request to the second network element, the first request being used to request a change in the temporary identifier of the subscribed terminal device, or, in other words, the first request being used to notify the second network element of a change in the temporary identifier of the subscribed terminal device.

[0099] For ease of understanding, the following description, in conjunction with Figures 4 and 5, will use the second network element as either a mobility management network element or a data storage network element as examples.

[0100] Figure 4 is a schematic diagram of the scheme for the first network element to obtain the permanent identifier of the terminal device in an embodiment of this application. Assuming that the second network element is a mobility management network element, the method shown in Figure 4 includes steps S410 to S480.

[0101] In step S410, the terminal device obtains a first temporary identifier from the mobility management network element.

[0102] In some implementations, the mobility management network element can store the first association between the first temporary identifier and the permanent identifier of the terminal device.

[0103] In some implementations, if the terminal device has already registered with the network, the mobility management network element can send a first temporary identifier to the terminal device.

[0104] In step S420, the terminal device sends an AS message to the access network element.

[0105] In some implementations, the AS message mentioned above may include RRC messages defined in the 5G system. These RRC messages may include, for example, one or more of the following: RRC Setup Request messages, RRC Setup Complete messages, RRC Re-establishment Complete messages, and UL Information Transfer messages. In other implementations, the AS message may include AS messages newly defined in the 6G network.

[0106] As described above, the AS message may carry a NAS message sent to the first network element. Taking a session management network element as an example, the NAS message may include one or more of the following: a message for session establishment; a message for session update; a message for session deletion. Taking a location management network element as an example, the NAS message may include one or more of the following: a message for location reporting; a message for location services. The AS message or other AS messages associated with it may include a first temporary identifier.

[0107] In step S430, the access network element sends the NAS message to the first network element through the service interface.

[0108] In some implementations, if the access network element obtains the first temporary identifier from the terminal device in step S420, the access network element sends the first temporary identifier along with the NAS message to the first network element. Of course, in this embodiment, the first network element can obtain the first temporary identifier from the terminal device via the NAS message.

[0109] In step S440, the first network element sends a first temporary identifier to the mobility management network element.

[0110] In step S450, the mobility management network element sends the permanent identifier of the terminal device to the first network element.

[0111] In some implementations, the first network element can use the permanent identifier of the terminal device when interacting with other core network elements.

[0112] In step S460, the first network element sends a first request to the mobility management network element to request a notification of change of the temporary identifier of the subscribed terminal device.

[0113] In step S470, the mobility management network element assigns a second temporary identifier to the terminal device and saves the association between the second temporary identifier and the permanent identifier of the terminal device.

[0114] In step S480, the mobility management network element sends a second temporary identifier to the first network element to instruct the first network element to save the second association relationship between the second temporary identifier and the permanent identifier.

[0115] In this embodiment, over-the-air communication (e.g., between the terminal device, access network element, and mobility management network element) continues to use the terminal device's temporary identifier (e.g., a first temporary identifier and / or a second temporary identifier), which helps improve communication security and prevent user privacy leaks. On the other hand, the first network element can obtain the terminal device's permanent identifier from the mobility management network element, thereby enabling it to interact with other core network elements based on the terminal device's permanent identifier (e.g., obtaining the terminal device's subscription information, obtaining control policies for the terminal device, etc.), which helps the core network to manage the terminal devices accessing the network normally.

[0116] Figure 5 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application. Assuming that the second network element is a data storage network element, the method shown in Figure 5 includes steps S510 to S555.

[0117] In step S510, the terminal device obtains a first temporary identifier from the mobility management network element.

[0118] In some implementations, the mobility management network element can store the first association between the first temporary identifier and the permanent identifier of the terminal device.

[0119] In some implementations, if the terminal device has already registered with the network, the mobility management network element can send a first temporary identifier to the terminal device.

[0120] In step S515, the mobility management network element sends the first association relationship between the first temporary identifier of the terminal device and the permanent identifier of the terminal device to the data storage network element.

[0121] In step S520, the terminal device sends an AS message to the access network element.

[0122] In some implementations, the AS message mentioned above may include RRC messages defined in the 5G system. These RRC messages may include, for example, one or more of the following: RRCSetupRequest, RRCSetupComplete, RRCResumeComplete, ULInformationTransfer, etc. In other implementations, the AS message may include AS messages newly defined in the 6G network.

[0123] As described above, the AS message may carry a NAS message sent to the first network element. Taking a session management network element as an example, the NAS message may include one or more of the following: a message for session establishment; a message for session update; a message for session deletion. Taking a location management network element as an example, the NAS message may include one or more of the following: a message for location reporting; a message for location services. The AS message or other AS messages associated with it may include a first temporary identifier.

[0124] In step S525, the access network element sends the NAS message to the first network element through the service interface.

[0125] In some implementations, if the access network element obtains the first temporary identifier from the terminal device in step S520, the access network element sends the first temporary identifier along with the NAS message to the first network element. Of course, in this embodiment, the first network element can obtain the first temporary identifier from the terminal device via the NAS message.

[0126] In step S530, the first network element sends a first temporary identifier to the data storage network element.

[0127] In step S535, the data storage network element sends the permanent identifier of the terminal device to the first network element.

[0128] In some implementations, the first network element can use the permanent identifier of the terminal device when interacting with other core network elements.

[0129] In step S540, the first network element sends a first request to the data storage network element to request a change notification of the temporary identifier of the subscribed terminal device.

[0130] In step S545, the mobility management network element assigns a second temporary identifier to the terminal device and saves the second association relationship between the second temporary identifier and the permanent identifier of the terminal device.

[0131] In step S550, the mobility management network element sends the second association relationship between the second temporary identifier and the permanent identifier of the terminal device to the data storage network element.

[0132] In step S555, the data storage network element sends a second temporary identifier to the first network element to instruct the first network element to save the second association relationship between the second temporary identifier and the permanent identifier.

[0133] In this embodiment, over-the-air communication (e.g., between the terminal device, access network element, and mobility management network element) continues to use the terminal device's temporary identifier (e.g., a first temporary identifier and / or a second temporary identifier), which helps improve communication security and prevent user privacy leaks. On the other hand, the first network element can obtain the terminal device's permanent identifier from the data storage network element, thereby enabling interaction with other core network elements based on the terminal device's permanent identifier (e.g., obtaining the terminal device's subscription information, obtaining control policies for the terminal device, etc.), which helps the core network to manage the terminal devices accessing the network normally. Furthermore, the first network element obtaining the terminal device's permanent identifier from the data storage network element helps reduce the load on the mobility management network element.

[0134] As described above, if the temporary identifier of the terminal device is updated, the first network element needs to update the temporary identifier associated with the permanent identifier accordingly. Therefore, to reduce the signaling overhead required to update the temporary identifier, a third temporary identifier is introduced in this embodiment. This third temporary identifier is used to identify the terminal device within the first network element. The third temporary identifier may be different from the temporary identifier assigned to the terminal device by the mobility management network element (e.g., the first temporary identifier or the second temporary identifier). Of course, in this embodiment, the third temporary identifier may be the same as the temporary identifier assigned to the terminal device by the mobility management network element (e.g., the first temporary identifier or the second temporary identifier).

[0135] In some implementations, the first network element stores the third association relationship between the third temporary identifier and the permanent identifier.

[0136] In some implementations, the first network element can send a third temporary identifier to the terminal device so that the terminal device can subsequently communicate with the first network element based on the third temporary identifier. The method also includes: the first network element sending a third temporary identifier to the terminal device.

[0137] In some implementations, the first network element sends a third temporary identifier to the terminal device, which may include the first network element allocating a third temporary identifier to the terminal device.

[0138] In some implementations, the terminal device communicates with the first network element based on a third temporary identifier, which may include the first network element obtaining the third temporary identifier from the terminal device via a NAS message. In this embodiment, the NAS message is not limited. In some implementations, the NAS message may include a session update message and / or a session deletion message.

[0139] In some implementations, the third temporary identifier can be obtained from the access network element through a service-oriented interface. For example, the access network element can obtain an AS message from the terminal device, which includes a NAS message and a third temporary identifier. Accordingly, the access network element can send the NAS message and the third temporary identifier to the first network element.

[0140] For ease of understanding, the following describes the wireless communication method of this application embodiment with reference to Figures 6 and 7, taking the second network element as a mobility management network element or a data storage network element as an example.

[0141] Figure 6 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application. Assuming that the second network element is a mobility management network element, the method shown in Figure 6 includes steps S610 to S680.

[0142] In step S610, the terminal device obtains a first temporary identifier from the mobility management network element.

[0143] In some implementations, the mobility management network element can store the first association between the first temporary identifier and the permanent identifier of the terminal device.

[0144] In some implementations, if the terminal device has already registered with the network, the mobility management network element can send a first temporary identifier to the terminal device.

[0145] In step S620, the terminal device sends an AS message to the access network element.

[0146] In some implementations, the aforementioned AS message may include an AS message from the first interaction between the terminal device and the first network element. For example, this AS message may be a session establishment request message.

[0147] In step S630, the access network element sends the NAS message to the first network element through the service interface.

[0148] In some implementations, if the access network element obtains the first temporary identifier from the terminal device in step S420, the access network element sends the first temporary identifier along with the NAS message to the first network element. Of course, in this embodiment, the first network element can obtain the first temporary identifier from the terminal device via the NAS message.

[0149] In step S640, the first network element sends a first temporary identifier to the mobility management network element.

[0150] In step S650, the mobility management network element sends the permanent identifier of the terminal device to the first network element.

[0151] In some implementations, the first network element can use the permanent identifier of the terminal device when interacting with other core network elements.

[0152] In step S660, the first network element assigns a third temporary identifier to the terminal device.

[0153] In some implementations, the third temporary identifier is used to identify the terminal device within the first network element. Accordingly, the first network element stores a third association between the third temporary identifier and the permanent identifier of the terminal device.

[0154] In step S670, the terminal device sends a NAS message to the first network element through the access network element, and the NAS message or the AS message carrying the NAS message includes a third temporary identifier.

[0155] In some implementations, NAS messages may include, for example, session update and session deletion messages.

[0156] In step S680, the access network element sends a NAS message to the first network element through the service interface.

[0157] In some implementations, if the access network element obtains a third temporary identifier from the terminal device in step S670, the access network element can send the third temporary identifier along with the NAS message to the first network element. Accordingly, the first network element can determine the permanent identifier of the terminal device based on the third temporary identifier and the third association relationship between the third temporary identifier stored locally and the permanent identifier of the terminal device.

[0158] In this embodiment, over-the-air communication (e.g., between terminal devices, access network elements, and mobility management network elements) continues to use the temporary identifier of the terminal device (e.g., a first temporary identifier and / or a third temporary identifier), which helps improve communication security and prevent user privacy leaks. On the other hand, the first network element can obtain the permanent identifier of the terminal device from the data storage network element, thereby enabling interaction with other core network elements based on the permanent identifier of the terminal device (e.g., obtaining the terminal device's subscription information, obtaining control policies for the terminal device, etc.), which helps the core network to manage the terminal devices accessing the network normally. Furthermore, the first network element can identify the terminal device internally based on the third identifier. In this case, if the first temporary identifier corresponding to the terminal device changes, the first network element does not need to update the terminal device's temporary identifier (or, the first network element does not need to subscribe to communication regarding changes in the terminal device's temporary identifier), which helps reduce the overhead required for network signaling interaction.

[0159] Figure 7 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application. Assuming that the second network element is a data storage network element, the method shown in Figure 7 includes steps S710 to S750.

[0160] In step S710, the terminal device obtains a first temporary identifier from the mobility management network element.

[0161] In some implementations, the mobility management network element can store the first association between the first temporary identifier and the permanent identifier of the terminal device.

[0162] In some implementations, if the terminal device has already registered with the network, the mobility management network element can send a first temporary identifier to the terminal device.

[0163] In step S715, the mobility management network element sends the first association relationship between the first temporary identifier of the terminal device and the permanent identifier of the terminal device to the data storage network element.

[0164] In step S720, the terminal device sends an AS message to the access network element.

[0165] In some implementations, the aforementioned AS message may include an AS message from the first interaction between the terminal device and the first network element. For example, this AS message may be a session establishment request message.

[0166] In step S725, the access network element sends the NAS message to the first network element through the service interface.

[0167] In some implementations, if the access network element obtains the first temporary identifier from the terminal device in step S720, the access network element sends the first temporary identifier along with the NAS message to the first network element. Of course, in this embodiment, the first network element can obtain the first temporary identifier from the terminal device via the NAS message.

[0168] In step S730, the first network element sends a first temporary identifier to the data storage network element.

[0169] In step S735, the data storage network element sends the permanent identifier of the terminal device to the first network element.

[0170] In some implementations, the first network element can use the permanent identifier of the terminal device when interacting with other core network elements.

[0171] In step S740, the first network element assigns a third temporary identifier to the terminal device.

[0172] In some implementations, the third temporary identifier is used to identify the terminal device within the first network element. Accordingly, the first network element stores a third association between the third temporary identifier and the permanent identifier of the terminal device.

[0173] In step S745, the terminal device sends a NAS message to the first network element through the access network element, and the NAS message or the AS message carrying the NAS message includes a third temporary identifier.

[0174] In some implementations, NAS messages may include, for example, session update messages and session deletion messages.

[0175] In step S750, the access network element sends a NAS message to the first network element through the service interface.

[0176] In some implementations, if the access network element obtains a third temporary identifier from the terminal device in step S745, the access network element can send the third temporary identifier along with the NAS message to the first network element. Accordingly, the first network element can determine the permanent identifier of the terminal device based on the third temporary identifier and the third association relationship between the third temporary identifier stored locally and the permanent identifier of the terminal device.

[0177] In this embodiment, over-the-air communication (e.g., between terminal devices, access network elements, and mobility management network elements) continues to use the temporary identifier of the terminal device (e.g., a first temporary identifier and / or a third temporary identifier), which helps improve communication security and prevent user privacy leaks. On the other hand, the first network element can obtain the permanent identifier of the terminal device from the data storage network element, thereby enabling interaction with other core network elements based on the permanent identifier of the terminal device (e.g., obtaining the terminal device's subscription information, obtaining control policies for the terminal device, etc.), which helps the core network to manage the terminal devices accessing the network normally. Furthermore, the first network element can identify the terminal device internally based on the third identifier. In this case, if the first temporary identifier corresponding to the terminal device changes, the first network element does not need to update the terminal device's temporary identifier (or, the first network element does not need to subscribe to communication regarding changes in the terminal device's temporary identifier), which helps reduce the overhead required for network signaling interaction.

[0178] Example 2:

[0179] Figure 8 is a flowchart of a wireless communication method according to another embodiment of this application. The method shown in Figure 8 includes step S810. In step S810, the access network element sends the permanent identifier of the terminal device to the first network element through a service interface.

[0180] In some implementations, the first network element can be a network element located in the core network; therefore, the first network element is also called the "first core network element." In other implementations, the first network element includes one or more of the following: a session management network element (e.g., SMF and / or 6G SM); a location management network element; and a PCF. Of course, in the embodiments of this application, the first network element can also be other network elements that need to obtain the permanent identifier of the terminal device.

[0181] In some implementations, the permanent identifier may include SUPI. Of course, in the embodiments of this application, the permanent identifier of the terminal device may also be other permanent identifiers introduced in future communication systems.

[0182] In this embodiment, the access network element can send the permanent identifier of the terminal device to the first network element through a service interface. Compared with the traditional solution where the mobility management network element provides the permanent identifier of the terminal device, this helps to enable other core network elements to obtain the permanent identifier of the terminal device in scenarios where the access network element directly interacts with other network elements (e.g., core network elements) through a service interface.

[0183] In some implementations, the access network element can obtain the permanent identifier of the terminal device from the second network element. For example, the above method further includes: the access network element sending a first temporary identifier of the terminal device to the second network element; correspondingly, the second network element sending the permanent identifier of the terminal device to the access network element.

[0184] In some implementations, the first temporary identifier may include a temporary identifier assigned to the terminal device by the mobility management network element, such as a GUTI and / or S-TMSI from a known network (e.g., 5G). Of course, in the embodiments of this application, the first temporary identifier may also be other temporary identifiers assigned to the terminal device in a future network.

[0185] In some implementations, the second network element can be a network element located in the core network; therefore, the second network element is also called a "second core network element." In other implementations, the second network element may include a mobility management network element and / or a data storage network element. The mobility management network element may, for example, include the AMF shown in Figure 1 and / or the 6G MM shown in Figure 2. Additionally, the data storage network element may, for example, include a UDM and / or an NRF. Of course, in the embodiments of this application, the second network element may also be other network elements that store the association between the temporary identifier and the permanent identifier of the terminal device.

[0186] In this embodiment, the mobility management network element provides a permanent identifier for the terminal device to the first network element, which helps to continue the traditional scheme of the mobility management network element providing a permanent identifier for the terminal device, thereby reducing the need for modifications to the traditional communication system.

[0187] In addition, in this embodiment of the application, the data storage network element provides a permanent identifier of the terminal device to the first network element, which helps to reduce the load on the mobility management network element.

[0188] As described above, the second network element may include a data storage network element. In this case, the second network element can obtain the association relationship between the permanent identifier of the terminal device and the first temporary identifier of the terminal device from the mobility management network element. The implementation method of this association relationship can be found in the above description of the first association relationship.

[0189] In some implementations, step S810 includes: the access network element sending a permanent identifier and a NAS message to the first network element through a service interface.

[0190] In some implementations, the terminal device sends an AS message to the access network element. The AS message carries the terminal device's first temporary identifier and a NAS message. In some implementations, the AS message may include RRC messages from the 5G network. For example, RRC messages may include one or more of the following: RRCSetupRequest, RRCSetupComplete, RRCResumeComplete, and ULInformationTransfer. In other implementations, the AS message may include newly defined AS messages from the 6G network.

[0191] As described above, the AS message may carry a NAS message sent to the first network element. Taking a session management network element as an example, the NAS message may include one or more of the following: a message for session establishment; a message for session update; a message for session deletion. Taking a location management network element as an example, the NAS message may include one or more of the following: a message for location reporting; a message for location services. The AS message or other AS messages associated with it may include a first temporary identifier.

[0192] For ease of understanding, the following describes the wireless communication method of this application embodiment with reference to Figures 9 and 10, taking the second network element as a mobility management network element or a data storage network element as an example.

[0193] Figure 9 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application. Assuming that the second network element is a mobility management network element, the method shown in Figure 9 includes steps S910 to S950.

[0194] In step S910, the terminal device obtains a first temporary identifier from the mobility management network element.

[0195] In some implementations, the mobility management network element can store the first association between the first temporary identifier and the permanent identifier of the terminal device.

[0196] In some implementations, if the terminal device has already registered with the network, the mobility management network element can send a first temporary identifier to the terminal device.

[0197] In step S920, the terminal device sends an AS message to the access network element.

[0198] In some implementations, the AS message may include RRC messages defined in the 5G system. These RRC messages may include, for example, one or more of the following: RRCSetupRequest, RRCSetupComplete, RRCResumeComplete, ULInformationTransfer, etc. In other implementations, the AS message may include AS messages newly defined in the 9G network.

[0199] As described above, the AS message may carry a NAS message sent to the first network element. Taking a session management network element as an example, the NAS message may include one or more of the following: a message for session establishment; a message for session update; a message for session deletion. Taking a location management network element as an example, the NAS message may include one or more of the following: a message for location reporting; a message for location services. The AS message or other AS messages associated with it may include a first temporary identifier.

[0200] In step S930, the access network element sends the first temporary identifier of the terminal device to the mobility management network element.

[0201] In step S940, the mobility management network element sends the permanent identifier of the terminal device to the access network element.

[0202] In step S950, the access network element sends the permanent identifier of the terminal device and NAS message to the first network element through the service interface.

[0203] In some implementations, the first network element can use the permanent identifier of the terminal device when interacting with other core network elements.

[0204] In this embodiment, air interface communication (e.g., between terminal devices, access network elements, and mobility management network elements) continues to use the temporary identifier of the terminal device (e.g., a first temporary identifier) ​​for communication, which helps improve communication security and avoid user privacy leaks. On the other hand, access network elements can communicate with the first network element based on the permanent identifier of the terminal device, thereby enabling the first network element to interact with other core network elements based on the permanent identifier of the terminal device (e.g., to obtain the terminal device's subscription information, obtain control policies for the terminal device, etc.), which helps the core network to manage the terminal devices in the access network normally. Furthermore, the fact that access network elements can communicate with the first network element based on the permanent identifier of the terminal device helps simplify the complexity of the first network element obtaining the permanent identifier of the terminal device.

[0205] Figure 10 is a schematic diagram of a scheme for the first network element to obtain the permanent identifier of the terminal device in another embodiment of this application. Assuming that the second network element is a data storage network element, the method shown in Figure 10 includes steps S1010 to S1060.

[0206] In step S1010, the terminal device obtains a first temporary identifier from the mobility management network element.

[0207] In some implementations, the mobility management network element can store the first association between the first temporary identifier and the permanent identifier of the terminal device.

[0208] In some implementations, if the terminal device has already registered with the network, the mobility management network element can send a first temporary identifier to the terminal device.

[0209] In step S1020, the mobility management network element sends the first association relationship between the first temporary identifier of the terminal device and the permanent identifier of the terminal device to the data storage network element.

[0210] In step S1030, the terminal device sends an AS message to the access network element.

[0211] In some implementations, the AS message may include RRC messages defined in the 5G system. These RRC messages may include, for example, one or more of the following: RRCSetupRequest, RRCSetupComplete, RRCResumeComplete, ULInformationTransfer, etc. In other implementations, the AS message may include newly defined AS messages in the 10G network.

[0212] As described above, the AS message may carry a NAS message sent to the first network element. Taking a session management network element as an example, the NAS message may include one or more of the following: a message for session establishment; a message for session update; a message for session deletion. Taking a location management network element as an example, the NAS message may include one or more of the following: a message for location reporting; a message for location services. The AS message or other AS messages associated with it may include a first temporary identifier.

[0213] In step S1040, the access network element sends the first temporary identifier of the terminal device to the data storage network element.

[0214] In step S1050, the data storage network element sends the permanent identifier of the terminal device to the access network element.

[0215] In step S1060, the access network element sends the permanent identifier of the terminal device and NAS message to the first network element through the service interface.

[0216] In some implementations, the first network element can use the permanent identifier of the terminal device when interacting with other core network elements.

[0217] In this embodiment, air interface communication (e.g., between terminal devices, access network elements, and mobility management network elements) continues to use the temporary identifier of the terminal device (e.g., a first temporary identifier) ​​for communication, which helps improve communication security and avoid user privacy leaks. On the other hand, access network elements can communicate with the first network element based on the permanent identifier of the terminal device, thereby enabling the first network element to interact with other core network elements based on the permanent identifier of the terminal device (e.g., to obtain the terminal device's subscription information, obtain control policies for the terminal device, etc.), which helps the core network to manage the terminal devices in the access network normally. Furthermore, the fact that access network elements can communicate with the first network element based on the permanent identifier of the terminal device helps simplify the complexity of the first network element obtaining the permanent identifier of the terminal device.

[0218] The method embodiments of this application have been described in detail above with reference to Figures 1 to 10. The apparatus embodiments of this application will be described in detail below with reference to Figures 11 to 15. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0219] Figure 11 is a schematic diagram of a communication device according to an embodiment of this application. The communication device 1100 shown in Figure 11 is a first network element, and the communication device 1100 includes: a transmitting unit 1110 and a receiving unit 1120.

[0220] The sending unit 1110 is used to send the first temporary identifier of the terminal device to the second network element;

[0221] The receiving unit 1120 is used to receive the permanent identifier of the terminal device sent by the second network element.

[0222] In some implementations, the communication device further includes: a first processing unit for storing a first association relationship between the first temporary identifier and the permanent identifier.

[0223] In some implementations, the receiving unit is further configured to receive first information sent by the second network element, the first information indicating that the first association relationship be updated to a second association relationship, the second association relationship including the association relationship between the second temporary identifier and the permanent identifier of the terminal device.

[0224] In some implementations, the first information carries the second temporary identifier.

[0225] In some implementations, the sending unit is further configured to send a first request to the second network element, the first request being used to request subscription to the change of the temporary identifier of the terminal device.

[0226] In some implementations, the sending unit is further configured to send a third temporary identifier to the terminal device, the third temporary identifier being used to identify the terminal device within the first network element.

[0227] In some implementations, the communication device further includes a second processing unit, which is also used to store a third association between the third temporary identifier and the permanent identifier.

[0228] In some implementations, the first network element obtains the first temporary identifier and / or the third temporary identifier through one or more of the following methods: obtaining it from the terminal device via a NAS message; or obtaining it from the access network element via a service-oriented interface.

[0229] In some implementations, the first network element includes a session management network element and / or a location management network element, and / or the second network element includes a mobility management network element and / or a data storage network element.

[0230] Figure 12 is a schematic diagram of a communication device according to an embodiment of this application. The communication device 1200 shown in Figure 12 is a second network element, and the communication device 1200 includes: a receiving unit 1210 and a transmitting unit 1220.

[0231] The receiving unit 1210 is used to receive the first temporary identifier of the terminal device sent by the first network element;

[0232] The sending unit 1220 is used to send the permanent identifier of the terminal device to the first network element.

[0233] In some implementations, the first association between the first temporary identifier and the permanent identifier is stored in the first network element.

[0234] In some implementations, the sending unit is further configured to send first information to the first network element, the first information indicating that the first association relationship be updated to a second association relationship, the second association relationship including the association relationship between the second temporary identifier and the permanent identifier of the terminal device.

[0235] In some implementations, the first information carries the second temporary identifier.

[0236] In some implementations, the receiving unit is further configured to receive a first request sent by the first network element, the first request being used to request subscription to changes in the temporary identifier of the terminal device.

[0237] In some implementations, the first network element includes a session management network element and / or a location management network element, and / or the second network element includes a mobility management network element and / or a data storage network element.

[0238] Figure 13 is a schematic diagram of a communication device according to an embodiment of this application. The communication device 1300 shown in Figure 13 is an access network element, and the communication device 1300 includes: a transmitting unit 1310.

[0239] The sending unit 1310 is used to send the permanent identifier of the terminal device to the first network element through the service interface.

[0240] In some implementations, the communication device includes a first receiving unit, the sending unit being configured to send a first temporary identifier of the terminal device to a second network element; the first receiving unit being configured to receive the permanent identifier sent by the second network element.

[0241] In some implementations, the second network element includes a mobility management network element and / or a data storage network element.

[0242] In some implementations, the sending unit is further configured to send the permanent identifier and NAS message to the first network element through the service interface.

[0243] In some implementations, the communication device further includes a second receiving unit, which is used to receive an AS message sent by the terminal device, the AS message carrying a first temporary identifier and a NAS message of the terminal device.

[0244] In some implementations, the first network element includes a session management network element and / or a location management network element.

[0245] Figure 14 is a schematic diagram of a communication device according to an embodiment of this application. The communication device 1400 shown in Figure 14 is a first network element, and the communication device 1400 includes: a receiving unit 1410.

[0246] The receiving unit 1410 is used to receive the permanent identifier of the terminal device sent by the access network element through the service interface.

[0247] In some implementations, the receiving unit is configured to receive the permanent identifier of the terminal device and NAS messages sent by the access network element through the service interface.

[0248] In some implementations, the first network element includes a session management network element and / or a location management network element.

[0249] Figure 15 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 15 indicate that the unit or module is optional. This device 1500 can be used to implement the methods described in the above method embodiments. Device 1500 can be a chip, a terminal device, or a network device.

[0250] Apparatus 1500 may include one or more processors 1510. The processor 1510 may support apparatus 1500 in implementing the methods described in the preceding method embodiments. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0251] The apparatus 1500 may further include one or more memories 1520. The memories 1520 store a program that can be executed by the processor 1510, causing the processor 1510 to perform the methods described in the preceding method embodiments. The memories 1520 may be independent of the processor 1510 or integrated into the processor 1510.

[0252] The device 1500 may also include a transceiver 1530. The processor 1510 can communicate with other devices or chips via the transceiver 1530. For example, the processor 1510 can send and receive data with other devices or chips via the transceiver 1530.

[0253] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal or network device provided in this application, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0254] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0255] This application also provides a computer program. This computer program can be applied to the terminal or network device provided in this application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of this application.

[0256] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0257] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0258] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0259] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship of instruction and being instructed, configuration and being configured, etc.

[0260] In this application, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0261] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0262] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0263] In the various embodiments of this application, the order of the above-mentioned processes does not imply 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.

[0264] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0265] The units described as separate components may or may not be physically separate. 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 can be selected to achieve the purpose of this embodiment according to actual needs.

[0266] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0267] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. 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. 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 wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0268] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.< / mnc> < / mcc>

Claims

1. A method for wireless communication, characterized in that, include: The first network element sends the first temporary identifier of the terminal device to the second network element; The first network element receives the permanent identifier of the terminal device sent by the second network element.

2. The method as described in claim 1, characterized in that, The method further includes: The first network element stores the first association relationship between the first temporary identifier and the permanent identifier.

3. The method as described in claim 2, characterized in that, The method further includes: The first network element receives first information sent by the second network element. The first information indicates that the first association relationship should be updated to a second association relationship. The second association relationship includes the association relationship between the second temporary identifier and the permanent identifier of the terminal device.

4. The method as described in claim 3, characterized in that, The first information carries the second temporary identifier.

5. The method as described in claim 3 or 4, characterized in that, The method further includes: The first network element sends a first request to the second network element, the first request being used to request subscription to the change of the temporary identifier of the terminal device.

6. The method as described in claim 1, characterized in that, The method further includes: The first network element sends a third temporary identifier to the terminal device, the third temporary identifier being used to identify the terminal device within the first network element.

7. The method as described in claim 6, characterized in that, The method further includes: The first network element stores the third association relationship between the third temporary identifier and the permanent identifier.

8. The method as described in claim 6 or 7, characterized in that, The first network element obtains the first temporary identifier and / or the third temporary identifier through one or more of the following methods: Obtained from the terminal device via NAS messages; Obtained from access network elements through service-oriented interfaces.

9. The method according to any one of claims 1-8, characterized in that, The first network element includes a session management network element and / or a location management network element, and / or The second network element includes a mobility management network element and / or a data storage network element.

10. A method for wireless communication, characterized in that, include: The second network element receives the first temporary identifier of the terminal device sent by the first network element; The second network element sends the permanent identifier of the terminal device to the first network element.

11. The method as described in claim 10, characterized in that, The first association between the first temporary identifier and the permanent identifier is stored in the first network element.

12. The method as described in claim 11, characterized in that, The method further includes: The second network element sends first information to the first network element, the first information indicating that the first association relationship be updated to a second association relationship, the second association relationship including the association relationship between the second temporary identifier and the permanent identifier of the terminal device.

13. The method as described in claim 12, characterized in that, The first information carries the second temporary identifier.

14. The method as described in claim 12 or 13, characterized in that, The method further includes: The second network element receives a first request sent by the first network element, the first request being used to request subscription to the change of the temporary identifier of the terminal device.

15. The method according to any one of claims 10-14, characterized in that, The first network element includes a session management network element and / or a location management network element, and / or The second network element includes a mobility management network element and / or a data storage network element.

16. A method for wireless communication, characterized in that, include: The access network element sends the permanent identifier of the terminal device to the first network element through the service interface.

17. The method as described in claim 16, characterized in that, The method further includes: The access network element sends the first temporary identifier of the terminal device to the second network element; The access network element receives the permanent identifier sent by the second network element.

18. The method as described in claim 17, characterized in that, The second network element includes a mobility management network element and / or a data storage network element.

19. The method according to any one of claims 16-18, characterized in that, The access network element sends the permanent identifier of the terminal device to the first network element through a service interface, including: The access network element sends the permanent identifier and NAS message to the first network element through the service interface.

20. The method according to any one of claims 16-19, characterized in that, The method further includes: The access network element receives an AS message sent by the terminal device, the AS message carrying the terminal device's first temporary identifier and NAS message.

21. The method according to any one of claims 16-20, characterized in that, The first network element includes a session management network element and / or a location management network element.

22. A method for wireless communication, characterized in that, include: The first network element receives the permanent identifier of the terminal device sent by the access network element through a service interface.

23. The method as described in claim 22, characterized in that, The first network element receives the permanent identifier of the terminal device sent by the access network element through a service-oriented interface, including: The first network element receives the permanent identifier of the terminal device and the NAS message sent by the access network element through the service interface.

24. The method as described in claim 22 or 23, characterized in that, The first network element includes a session management network element and / or a location management network element.

25. A communication device, characterized in that, The communication device is a first network element, including: The sending unit is used to send the first temporary identifier of the terminal device to the second network element; The receiving unit is used to receive the permanent identifier of the terminal device sent by the second network element.

26. The communication device as described in claim 25, characterized in that, The communication device also includes: The first processing unit is used to store the first association relationship between the first temporary identifier and the permanent identifier.

27. The communication device as described in claim 26, characterized in that, The receiving unit is further configured to receive first information sent by the second network element, the first information indicating that the first association relationship be updated to a second association relationship, the second association relationship including the association relationship between the second temporary identifier and the permanent identifier of the terminal device.

28. The communication device as described in claim 27, characterized in that, The first information carries the second temporary identifier.

29. The communication device as described in claim 27 or 28, characterized in that, The sending unit is further configured to send a first request to the second network element, the first request being used to request subscription to the change of the temporary identifier of the terminal device.

30. The communication device as described in claim 25, characterized in that, The sending unit is further configured to send a third temporary identifier to the terminal device, the third temporary identifier being used to identify the terminal device within the first network element.

31. The communication device as described in claim 30, characterized in that, The communication device also includes: The second processing unit is also used to store the third association relationship between the third temporary identifier and the permanent identifier.

32. The communication device as described in claim 30 or 31, characterized in that, The first network element obtains the first temporary identifier and / or the third temporary identifier through one or more of the following methods: Obtained from the terminal device via NAS messages; Obtained from access network elements through service-oriented interfaces.

33. The communication device as described in any one of claims 25-32, characterized in that, The first network element includes a session management network element and / or a location management network element, and / or The second network element includes a mobility management network element and / or a data storage network element.

34. A communication device, characterized in that, The communication device is a second network element, including: The receiving unit is used to receive the first temporary identifier of the terminal device sent by the first network element; The sending unit is used to send the permanent identifier of the terminal device to the first network element.

35. The communication device as described in claim 34, characterized in that, The first association between the first temporary identifier and the permanent identifier is stored in the first network element.

36. The communication device as described in claim 35, characterized in that, The sending unit is further configured to send first information to the first network element, the first information indicating that the first association relationship be updated to a second association relationship, the second association relationship including the association relationship between the second temporary identifier and the permanent identifier of the terminal device.

37. The communication device as described in claim 36, characterized in that, The first information carries the second temporary identifier.

38. The communication device as described in claim 36 or 37, characterized in that, The receiving unit is further configured to receive a first request sent by the first network element, the first request being used to request subscription to the change of the temporary identifier of the terminal device.

39. The communication device as described in any one of claims 34-38, characterized in that, The first network element includes a session management network element and / or a location management network element, and / or The second network element includes a mobility management network element and / or a data storage network element.

40. A communication device, characterized in that, The communication equipment is an access network element, including: The sending unit is used to send the permanent identifier of the terminal device to the first network element through the service interface.

41. The communication device as described in claim 40, characterized in that, Including the first receiving unit, The sending unit is used to send the first temporary identifier of the terminal device to the second network element; The first receiving unit is used to receive the permanent identifier sent by the second network element.

42. The communication device as described in claim 41, characterized in that, The second network element includes a mobility management network element and / or a data storage network element.

43. The communication device as described in any one of claims 40-42, characterized in that, The sending unit is further configured to send the permanent identifier and NAS message to the first network element through the service interface.

44. The communication device as described in any one of claims 40-43, characterized in that, The communication device further includes a second receiving unit. The second receiving unit is used to receive an AS message sent by the terminal device, wherein the AS message carries a first temporary identifier and a NAS message of the terminal device.

45. The communication device as described in any one of claims 40-44, characterized in that, The first network element includes a session management network element and / or a location management network element.

46. ​​A communication device, characterized in that, The communication device is a first network element, including: The receiving unit is used to receive the permanent identifier of the terminal device sent by the access network element through the service interface.

47. The communication device as described in claim 46, characterized in that, The receiving unit is configured to receive the permanent identifier of the terminal device and the NAS message sent by the access network element through the service interface.

48. The communication device as described in claim 46 or 47, characterized in that, The first network element includes a session management network element and / or a location management network element.

49. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs one of the following: the method as claimed in any one of claims 1-9, the method as claimed in any one of claims 10-15, the method as claimed in any one of claims 16-21, or the method as claimed in any one of claims 22-24.

50. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the apparatus to perform one of the following: the method of any one of claims 1-9, the method of any one of claims 10-15, the method of any one of claims 16-21, or the method of any one of claims 22-24.

51. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform one of the following: the method of any one of claims 1-9, the method of any one of claims 10-15, the method of any one of claims 16-21, or the method of any one of claims 22-24.

52. A computer-readable storage medium, characterized in that, It stores a program that causes a computer to perform one of the following: the method as claimed in any one of claims 1-9, the method as claimed in any one of claims 10-15, the method as claimed in any one of claims 16-21, or the method as claimed in any one of claims 22-24.

53. A computer program product, characterized in that, The program includes a method that causes a computer to perform one of the following: the method of any one of claims 1-9, the method of any one of claims 10-15, the method of any one of claims 16-21, or the method of any one of claims 22-24.

54. A computer program, characterized in that, The computer program causes the computer to perform one of the following: the method as claimed in any one of claims 1-9, the method as claimed in any one of claims 10-15, the method as claimed in any one of claims 16-21, or the method as claimed in any one of claims 22-24.

Images