WO2023050799A1 - 一种注册方法、终端设备、核心网设备及存储介质 - Google Patents

一种注册方法、终端设备、核心网设备及存储介质 Download PDF

Info

Publication number
WO2023050799A1
WO2023050799A1 PCT/CN2022/090050 CN2022090050W WO2023050799A1 WO 2023050799 A1 WO2023050799 A1 WO 2023050799A1 CN 2022090050 W CN2022090050 W CN 2022090050W WO 2023050799 A1 WO2023050799 A1 WO 2023050799A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
registration
request message
identifier
core network
Prior art date
Application number
PCT/CN2022/090050
Other languages
English (en)
French (fr)
Inventor
刘宇泽
游世林
彭锦
邢真
林兆骥
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020247011250A priority Critical patent/KR20240049681A/ko
Publication of WO2023050799A1 publication Critical patent/WO2023050799A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration

Definitions

  • the embodiments of the present application relate to the technical field of communications, for example, to a registration method, terminal equipment, core network equipment, and storage media.
  • the standard 3rd generation partnership project (3rd generation partnership project, 3GPP) defines the registration process of user equipment (user equipment, UE) in the 5th generation mobile communication technology (5th-generation, 5G) system. However, during the UE registration process, if two UEs have the same 5G-Globally Unique Temporary UE Identity (5G-GUTI), when one of the UEs is registered, it may cause another UE cannot register normally.
  • 5G-GUTI 5G-Globally Unique Temporary UE Identity
  • An embodiment of the present application provides a registration method, which is applied to a core network device, including: obtaining a first registration request message sent by a first terminal device, where the first registration request message includes a first identifier of the first terminal device; Identify the related information of the second terminal device; if the related information of the second terminal device is in an activated state, obtain the second identification of the first terminal device; register the first terminal device according to the second identification.
  • An embodiment of the present application provides a registration method, which is applied to a first terminal device, including: sending a first registration request message to a core network device, where the first registration request message includes a first identifier of the first terminal device; meeting a preset condition, Sending the second identification of the first terminal device to the core network device to complete the registration, the preset condition is to obtain the identification request message sent by the core network device, or not to obtain any registration information sent by the core network device within a preset time relevant news.
  • An embodiment of the present application provides a core network device, including: a processor; the processor is configured to implement the method in any one of the foregoing embodiments when executing a computer program.
  • An embodiment of the present application provides a terminal device, including: a processor; the processor is configured to implement the method in any one of the foregoing embodiments when executing a computer program.
  • An embodiment of the present application further provides a computer-readable storage medium storing a computer program, and the computer program implements the method in any one of the foregoing embodiments when executed by a processor.
  • FIG. 1 is a schematic diagram of networking of a wireless communication system provided by an embodiment
  • Fig. 2 is a schematic diagram of networking of another wireless communication system provided by an embodiment
  • FIG. 3 is a schematic diagram of a UE registration process in a 5G system provided by an embodiment
  • Fig. 4 is a schematic flowchart of a registration method provided by an embodiment
  • Fig. 5 is a schematic flowchart of another registration method provided by an embodiment
  • Fig. 6 is a process interaction diagram of a registration method provided by an embodiment
  • Fig. 7 is an interactive flowchart of another registration method provided by an embodiment
  • Fig. 8 is a process interaction diagram of another registration method provided by an embodiment
  • Fig. 9 is an interactive flowchart of another registration method provided by an embodiment
  • FIG. 10 is a schematic structural diagram of a core network device provided by an embodiment
  • FIG. 11 is a schematic structural diagram of another core network device provided by an embodiment
  • Fig. 12 is a schematic structural diagram of a terminal device provided by an embodiment
  • Fig. 13 is a schematic structural diagram of an AMF provided by an embodiment
  • Fig. 14 is a schematic structural diagram of a UE provided by an embodiment.
  • Fig. 1 shows a schematic diagram of networking of a wireless communication system provided by an embodiment.
  • the wireless communication system includes a terminal device 110 , an access network device 120 and a core network device 130 .
  • the terminal device 110 may also be called a terminal, a UE, a mobile station, a mobile terminal, and the like.
  • a terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like. Examples of some terminals are: mobile phones, tablet computers, computers with wireless transceiver functions, virtual reality terminal equipment, augmented reality terminal equipment, wireless terminals in industrial control, wireless terminals in unmanned driving, wireless terminals in remote surgery, Wireless terminals in smart grids, wireless terminals in transportation security, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the embodiment of the present application does not limit the technology and device form adopted by the terminal device.
  • the access network device 120 is an access device for the terminal device 110 to access the wireless communication system in a wireless manner, and may be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (transmission reception point) , TRP), the next generation base station (next generation NodeB, gNB) in the 5G mobile communication system, the base station in the future mobile communication system or the access node in the WiFi system, etc.; it can also be a module or unit that completes some functions of the base station, For example, it can be a centralized unit (central unit, CU) or a distributed unit (distributed unit, DU).
  • the embodiments of the present application do not limit the technologies and equipment forms adopted by the access network equipment.
  • the core network device 130 may include an access and mobility management network element and a session management network element.
  • the terminal device 110 can access the core network through the access network device 120, so as to realize data transmission.
  • Fig. 2 shows a schematic diagram of networking of another wireless communication system provided by an embodiment.
  • the wireless communication system includes:
  • (wireless) access network radio access network, (R) AN: It is used to provide network access functions for authorized users in a specific area, and can use transmission tunnels of different qualities according to user levels and business requirements.
  • (R)AN network elements can manage wireless resources, provide access services for terminal equipment, and then complete the forwarding of control signals and user data between terminal equipment and the core network.
  • (R)AN can also be understood as a base station in a traditional network .
  • Access and mobility management function (access and mobility management function, AMF): mainly used for mobility management and access management.
  • the AMF can be used to implement functions of a mobility management entity (mobility management entity, MME) other than session management, for example, functions such as lawful interception or access authorization (or authentication).
  • MME mobility management entity
  • session management for example, functions such as lawful interception or access authorization (or authentication).
  • Session Management Function SMF
  • Session Management Function SMF
  • Session Management Function It can also be called session management function network element, which is mainly used for session management, Internet Protocol (IP) address allocation and management of terminal equipment, and selection of manageable Termination point of user plane function, policy control, or charging function interface and downlink data notification, etc.
  • IP Internet Protocol
  • the access network device 120 may be the RAN in FIG. 2; the access and mobility management network element may be the AMF in FIG. 2; the session management network element may be is the SMF in Figure 2.
  • the wireless communication system may also include:
  • User plane function also known as user plane function or user plane network element or user plane function network element, used for packet routing and forwarding, or user plane data quality of service (quality of service) , QoS) processing, etc.
  • UPF is divided into intermediate-UPF (intermediate-UPF, I-UPF) and anchor UPF (anchor-UPF, A-UPF).
  • I-UPF intermediate-UPF
  • anchor UPF anchor-UPF
  • the I-UPF is connected to the access network RAN
  • the A-UPF is the UPF of the session anchor
  • the A-UPF may also be called a protocol data unit (protocol data unit, PDU) session anchor (PDU session anchor, PSA).
  • Data network (data network, DN): a network used to provide data transmission, for example, Internet network, etc.
  • DN data network
  • the PSA accesses the remote DN.
  • Authentication server function (authentication server function, AUSF): mainly used for user authentication, etc.
  • PCF Policy control function
  • Unified data management used to handle user identification, access authentication, registration, or mobility management.
  • Application function (Application function, AF): It mainly supports interaction with the 3GPP core network to provide services, for example, affecting data routing decisions, policy control functions, or providing some third-party services to the network side. It can be understood as a third-party server, such as an application server in the Internet, providing relevant service information, including providing service quality requirement information corresponding to the service to the PCF, and sending user plane data information of the service to the PSA-UPF.
  • the AF may be a service provider (content provider, CP).
  • Network slice selection function (network slice selection function, NSSF): used to select network slices.
  • the N1 interface is the reference point between the terminal equipment and the AMF; the N2 interface is the reference point between the (R)AN and the AMF, and is used for sending non-access stratum (NAS) messages etc.; N3 interface is the reference point between (R)AN and I-UPF, used to transmit user plane data, etc.; N4 interface is the reference point between SMF and I-UPF, used to transmit tunnels such as N3 connections Information such as identification information, data cache indication information, and downlink data notification messages; N5 interface is the reference point between PCF and AF; N6 interface is the reference point between UPF and DN, used to transmit user plane data, etc.; N7 The interface is the reference point between SMF and PCF; the N8 interface is the reference point between AMF and UDM; the N9 interface is the reference point between UPF; the N10 interface is the reference point between SMF and UDM; The reference point between SMF; the N12 interface is the reference point between AMF and AUSF; the N13 interface is the
  • the wireless communication system may also include:
  • Multicast control plane function used to control multicast services
  • MCF interfaces with service providers to receive information related to multicast services (such as descriptions of multicast services)
  • MCF and
  • the PCF is connected to create resources for multicast services.
  • MCF network element can also have other names, and it realizes the control plane function of the multicast service.
  • Multicast user plane function used to transmit multicast service-related data, that is, send the multicast data received from the CP to the UPF.
  • MUF multicast user plane function
  • the MCF may be integrated into the PCF (or SMF), and the MUF may be integrated into the UPF, which is not limited in this embodiment of the present application.
  • the above wireless communication system applied to the embodiment of the present application is only an example of a network architecture described from the perspective of the reference point architecture, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture that can achieve the above The functional network architecture of each network element is applicable to this embodiment of the present application.
  • the names of interfaces between network elements in FIG. 2 are just examples, and the names of interfaces in implementation may be other names.
  • the names of network elements (such as SMF, AF, UPF, etc.) included in FIG. 2 are only examples, and do not limit the functions of the network elements themselves.
  • the foregoing network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • some or all of the above network elements may use the terms in 5G, or may use other names, and so on.
  • the names of the messages (or signaling) transmitted between the foregoing network elements are only examples, and do not constitute any limitation on the functions of the messages themselves.
  • Fig. 3 shows a schematic diagram of a UE registration process in a 5G system provided by an embodiment. As shown in Figure 3, the registration process may include the following steps:
  • AMF selection process that is, (R)AN selects AMF according to its own strategy
  • the new AMF sends a complete registration request to the historical AMF
  • the historical AMF replies with a complete registration request response
  • the new AMF initiates an authentication request to the UE
  • the UE replies with an Authentication Request Response
  • the new AMF sends a registration completion notification to the historical AMF
  • the new AMF initiates an authentication request to the UE and receives the authentication response returned by the UE;
  • the new AMF initiates the equipment identity authentication process to the Equipment Identity Register (EIR);
  • EIR Equipment Identity Register
  • the new AMF sends a notification that the requested data is modified to the UDM
  • the UDM sends a registration notification (Nudm_UECM_DeregistrationNotification) to the historical AMF, so that the historical AMF deletes the context information of the UE;
  • the historical AMF sends an unsubscribe message to UDM
  • the new AMF performs AM policy association establishment/modification
  • the new AMF sends a network slice management function (network slice management function, NSMF) session content update/release context request to the SMF;
  • NSMF network slice management function
  • the new AMF sends a N2 AMF mobile request (such as UE context modification request) to the non-3GPP interworking function (N3IWF)/trusted non-3GPP gateway function (TNGF)/wired access gateway function (W-AGF);
  • N3IWF non-3GPP interworking function
  • TNGF trusted non-3GPP gateway function
  • W-AGF wireless access gateway function
  • N3IWF/TNGF/W-AGF replies N2 AMF mobile request response (such as UE context modification response) to the new AMF;
  • the new AMF After the new AMF receives the N2 AMF Move Request Response from the N3IWF/TNGF/W-AGF in step 19, the new AMF registers with the UDM using Nudm_UECM_Registration as step 14c, but sets the Access Type to "Non-3GPP Access" ;
  • UDM When UDM stores the access type (ie non-3GPP) with the serving AMF, UDM initiates Nudm_UECM_DeregistrationNotification to the historical AMF corresponding to the same (ie non-3GPP) access, and the old AMF removes the UE for non-3GPP access context;
  • the new AMF sends a registration acceptance message to the UE
  • the UE sends a registration complete message to the new AMF
  • the new AMF provides Nudm_SDM_Info used by UE to confirm UDM;
  • the new AMF For registration via 3GPP access, if the new AMF has not released the signaling connection, the new AMF sends the RRC invalidation assistance information to the (R)AN; for non-3GPP access registration, if the UE is also on 3GPP access In the CM-CONNECTED state, the new AMF sends the RRC invalid auxiliary information to (R)AN;
  • the new AMF uses Nudm_UECM_Update to send the "same support for IMS voice based on PS session" indication to UDM;
  • AMF performs steps 4-22 in Figure 3 above.
  • the context of UE A is in the active state.
  • UE B's 5G-GUTI is the same as UE A's 5G-GUTI, since AMF has established a security context with UE A and has enabled NAS security, the NAS message Integrity protection; UE B also performs integrity protection on the NAS message according to the context of UE B.
  • the 5G-GUTI identifies the context of UE A, so the NAS message of UE B cannot pass the integrity check of AMF, and AMF will discard the registration message of UE B, causing UE B to fail to register normally.
  • the 5G-GUTI of UE B is the same as the 5G-GUTI of UE A.
  • the reason for this phenomenon may be:
  • the same AMF may assign the same 5G Temporary Mobile Subscriber Identity (5G-TMSI) to different UEs, resulting in different UEs having the same 5G-GUTI.
  • 5G-TMSI 5G Temporary Mobile Subscriber Identity
  • AMF allocates a 5G-GUTI to UE B. After UE B leaves the network, AMF reassigns the 5G-GUTI to UE A, and then UE B re-connects to the network.
  • a registration method, terminal device, core network device, and storage medium operable in the above-mentioned wireless communication system are provided, which can solve the problem that the terminal device cannot normally register to the network and improve user experience.
  • Fig. 4 shows a schematic flowchart of a registration method provided by an embodiment. As shown in Fig. 4, the method provided by this embodiment is applicable to a core network device (such as AMF), and the method includes the following steps.
  • a core network device such as AMF
  • step S410 is to solve the problem that the terminal device cannot normally register to the network
  • step S410 when step S410 is executed, the second terminal device has been connected to the network, and the third identifier of the second terminal device is the same as the first identifier.
  • the third identification is the same as the first identification, and may include any of the following two situations:
  • the core network device obtains the second registration request message sent by the second terminal device, the second registration request message includes the third identification of the second terminal device, and the third identification is the same as the first identification; according to The third identifier is for registering the second terminal device.
  • Case 2 After the registration of the second terminal device is completed and before step S410 is executed, the core network device assigns a third identifier to the second terminal device, where the third identifier is the same as the first identifier.
  • the first identifier and the third identifier are identifiers of the same type, such as 5G-GUTI.
  • the information related to the second terminal device includes any one or more of the following information: the context of the second terminal device, the security context of the second terminal device, the non-access stratum NAS security of the second terminal device context.
  • the relevant information of the second terminal device is in an activated state, which means that the second terminal device has a NAS security connection at this time, and the core network device can no longer register for the first terminal device through the first identifier. At this time, the core network device acquires the second identifier of the first terminal device.
  • the first identifier and the second identifier are identifiers of different types.
  • the second identifier may be a subscription concealed identifier (subscription concealed identifier, SUCI).
  • the method of "obtaining the second identification" in step S430 may include any one of the following two methods:
  • Method A1 The core network device sends an identification request message to the first terminal device; obtains an identification response message sent by the first terminal device, where the identification response message includes the second identification.
  • the core network device can actively send an identification request message to the first terminal device to acquire the second identification.
  • Method A2 Obtain a third registration request message sent by the first terminal device, where the third registration request message includes the second identifier.
  • the core network device does not actively acquire the second identifier, and the second identifier is actively sent to the core network device by the first terminal device.
  • the timing for the first terminal device to actively send the second identifier to the core network device is: the first terminal device does not obtain any registration-related messages sent by the core network device within the preset time, the first terminal device retries the registration process and After a certain number of failures, send the second identifier to the core network device.
  • the core network device may also: obtain a fourth registration request message sent by the first terminal device, where the fourth registration request message includes the first identifier; obtain The second terminal device-related information related to the first identifier; the second terminal device-related information is in an active state, and the fourth registration request message is discarded.
  • the core network device when the core network device cannot register for the first terminal device through the first identifier, it may obtain the second identifier to register for the first terminal device. This ensures that the first terminal device can be successfully registered to the network, thereby improving user experience.
  • Fig. 5 shows a schematic flowchart of another registration method provided by an embodiment. As shown in Fig. 5, the method provided by this embodiment is applicable to a first terminal device (such as UE A), and the method includes the following steps.
  • a first terminal device such as UE A
  • S510 Send a first registration request message to the core network device, where the first registration request message includes a first identifier of the first terminal device.
  • the first identifier may be 5G-GUTI.
  • the preset condition is that the identifier request message sent by the core network device is obtained, or the core is not obtained within the preset time Any registration-related messages sent by network devices.
  • the first identifier and the second identifier are identifiers of different types.
  • the second identifier may be SUCI.
  • the first terminal device when the preset condition is to obtain the identification request message sent by the core network device, the first terminal device sends the second identification to the core network device, including: sending an identification response message to the core network device, the identification response message Include the second identifier.
  • the first terminal device when the preset condition is that no registration-related message sent by the core network device is obtained within the preset time, the first terminal device sends the second identification to the core network device, including: The device sends a third registration request message, where the third registration request message includes the second identifier.
  • the first terminal device Before the first terminal device sends the third registration request message to the core network device, it also includes:
  • the first terminal device makes the current number of iterations K equal to 0, and sends a fourth registration request message to the core network device.
  • the first terminal device is marked as UE B
  • the second terminal device is marked as UE A
  • the core network device is marked as AMF
  • the first identifier of the first terminal device is marked as 5G-GUTI of UE B
  • the second identifier of the first terminal device is recorded as UE B's SUCI
  • the third identifier of the second terminal device is recorded as UE A's 5G-GUTI.
  • FIG. 6 shows an interactive flowchart of a registration method provided by an embodiment. As shown in Fig. 6, the method includes the following steps.
  • UE A sends a second registration request message to the AMF, where the second registration request message includes UE A's 5G-GUTI.
  • the AMF registers UE A according to the 5G-GUTI of UE A.
  • UE B sends a first registration request message to the AMF, where the first registration request message includes the 5G-GUTI of UE B, and the 5G-GUTI of UE A is the same as the 5G-GUTI of UE B.
  • the AMF judges whether the UE A-related information related to the 5G-GUTI can be obtained.
  • the AMF cannot obtain the relevant information of UE A, it means that the AMF has not established a security context with UE A at this time.
  • the 5G-GUTI of UE B refer to step 4-22 in Figure 3 to register for UE B.
  • the relevant information of UE A is in an inactive state, it means that although the AMF has established a security context with UE A, NAS security has not been enabled. At this time, according to the 5G-GUTI of UE B, refer to steps 4-22 in Figure 3 Register for UE B.
  • the relevant information of UE A is in the active state, it means that AMF has established a security context with UE A and enabled NAS security, and has protected the integrity of NAS messages.
  • the 5G-GUTI identifies the context of UE A, so the NAS message of UE B cannot pass the integrity check of AMF, so AMF needs to send an identification request message to UE B.
  • UE B sends an identification response message to the AMF, where the identification response message includes the SUCI of UE B.
  • the AMF registers the UE B according to the SUCI of the UE B.
  • AMF performs registration for UE B with reference to steps 8-22 in Figure 3. This ensures that UE B can successfully register with the network and improves user experience.
  • FIG. 7 shows an interactive flowchart of another registration method provided by an embodiment. As shown in Fig. 7, the method includes the following steps.
  • the AMF allocates UE A's 5G-GUTI to UE A.
  • step S701 UE A has registered to the network using other 5G-GUTIs. Due to factors such as bandwidth requirements, AMF can re-allocate a 5G-GUTI for UE A, that is, UE A's 5G-GUTI.
  • UE B sends a first registration request message to the AMF, where the first registration request message includes the 5G-GUTI of UE B, and the 5G-GUTI of UE A is the same as the 5G-GUTI of UE B.
  • the AMF judges whether the UE A-related information related to the 5G-GUTI can be obtained.
  • the AMF cannot obtain the relevant information of UE A, it means that the AMF has not established a security context with UE A at this time.
  • the 5G-GUTI of UE B refer to step 4-22 in Figure 3 to register for UE B.
  • the relevant information of UE A is in an inactive state, it means that although the AMF has established a security context with UE A, NAS security has not been enabled. At this time, according to the 5G-GUTI of UE B, refer to steps 4-22 in Figure 3 Register for UE B.
  • the relevant information of UE A is in the active state, it means that AMF has established a security context with UE A and enabled NAS security, and has protected the integrity of NAS messages.
  • the 5G-GUTI identifies the context of UE A, so the NAS message of UE B cannot pass the integrity check of AMF, so AMF needs to send an identification request message to UE B.
  • UE B sends an identification response message to the AMF, where the identification response message includes the SUCI of UE B.
  • the AMF registers the UE B according to the SUCI of the UE B.
  • AMF performs registration for UE B with reference to steps 8-22 in Figure 3. This ensures that UE B can successfully register with the network and improves user experience.
  • FIG. 8 shows an interactive flowchart of another registration method provided by an embodiment. As shown in Fig. 8, the method includes the following steps.
  • UE A sends a second registration request message to the AMF, where the second registration request message includes UE A's 5G-GUTI.
  • the AMF registers UE A according to the 5G-GUTI of UE A.
  • UE B sends a first registration request message to the AMF, where the first registration request message includes the 5G-GUTI of UE B, and the 5G-GUTI of UE A is the same as the 5G-GUTI of UE B.
  • the AMF judges whether the UE A-related information related to the 5G-GUTI can be obtained.
  • the AMF cannot obtain the relevant information of UE A, it means that the AMF has not established a security context with UE A at this time.
  • the 5G-GUTI of UE B refer to step 4-22 in Figure 3 to register for UE B.
  • the relevant information of UE A is in an inactive state, it means that although the AMF has established a security context with UE A, NAS security has not been enabled. At this time, according to the 5G-GUTI of UE B, refer to steps 4-22 in Figure 3 Register for UE B.
  • the relevant information of UE A is in the active state, it means that AMF has established a security context with UE A and enabled NAS security, and has protected the integrity of NAS messages.
  • the 5G-GUTI identifies the context of UE A, so the NAS message of UE B cannot pass the integrity check of AMF, and AMF discards the first registration request message.
  • UE B does not obtain any registration-related message sent by AMF within the preset time, so that the current iteration number K is equal to 0, and sends a fourth registration request message to AMF.
  • the fourth registration request message includes UE B's 5G- GUTI.
  • the AMF judges whether UE A-related information related to the 5G-GUTI can be obtained. If not, register UE B according to UE B's 5G-GUTI. If yes, judge whether UE A-related information is activated. state; if it is in an inactive state, register for UE B according to the 5G-GUTI of UE B, and if it is in an active state, discard the fourth registration request message.
  • the number of attempts can be designed according to the actual situation, for example, the maximum number of iterations is 3 times.
  • UE B sends a third registration request message to the AMF, where the third registration request message includes the SUCI of UE B.
  • the AMF registers the UE B according to the SUCI of the UE B.
  • UE B actively sends a third registration request message including UE B's SUCI to AMF, so that AMF performs registration for UE B according to UE B's SUCI with reference to steps 8-22 in Figure 3. This ensures that UE B can successfully register with the network and improves user experience.
  • FIG. 9 shows an interactive flowchart of another registration method provided by an embodiment. As shown in Fig. 9, the method includes the following steps.
  • the AMF allocates UE A's 5G-GUTI to UE A.
  • step S901 UE A has registered to the network using other 5G-GUTIs. Due to factors such as bandwidth requirements, AMF can re-allocate a 5G-GUTI for UE A, that is, UE A's 5G-GUTI.
  • UE B sends a first registration request message to the AMF, where the first registration request message includes the 5G-GUTI of UE B, and the 5G-GUTI of UE A is the same as the 5G-GUTI of UE B.
  • the AMF judges whether the UE A-related information related to the 5G-GUTI can be obtained.
  • the AMF cannot obtain the relevant information of UE A, it means that the AMF has not established a security context with UE A at this time.
  • the 5G-GUTI of UE B refer to step 4-22 in Figure 3 to register for UE B.
  • the relevant information of UE A is in an inactive state, it means that although the AMF has established a security context with UE A, NAS security has not been enabled. At this time, according to the 5G-GUTI of UE B, refer to steps 4-22 in Figure 3 Register for UE B.
  • the relevant information of UE A is in the active state, it means that AMF has established a security context with UE A and enabled NAS security, and has protected the integrity of NAS messages.
  • the 5G-GUTI identifies the context of UE A, so the NAS message of UE B cannot pass the integrity check of AMF, and AMF discards the first registration request message.
  • UE B does not obtain any registration-related message sent by AMF within the preset time, so that the current iteration number K is equal to 0, and sends a fourth registration request message to AMF.
  • the fourth registration request message includes UE B's 5G- GUTI.
  • the AMF judges whether the UE A-related information related to the 5G-GUTI can be obtained. If not, register for UE B according to the 5G-GUTI of UE B. If yes, judge whether the UE A-related information is activated. state; if it is in an inactive state, register for UE B according to the 5G-GUTI of UE B, and if it is in an active state, discard the fourth registration request message.
  • the number of attempts can be designed according to the actual situation, for example, the maximum number of iterations is 3 times.
  • the UE B sends a third registration request message to the AMF, where the third registration request message includes the SUCI of the UE B.
  • the AMF registers the UE B according to the SUCI of the UE B.
  • UE B actively sends a third registration request message including UE B's SUCI to AMF, so that AMF performs registration for UE B according to UE B's SUCI with reference to steps 8-22 in FIG. 3 . This ensures that UE B can successfully register with the network and improves user experience.
  • FIG. 10 shows a schematic structural diagram of a core network device provided by an embodiment.
  • the core network device includes: a receiving module 10 and a processing module 11 .
  • the receiving module 10 is configured to obtain a first registration request message sent by the first terminal device, where the first registration request message includes a first identifier of the first terminal device;
  • the processing module 11 is configured to obtain information related to the second terminal device related to the first identifier
  • the receiving module 10 is further configured to obtain the second identification of the first terminal device when the related information of the second terminal device is in an active state;
  • the processing module 11 is further configured to perform registration for the first terminal device according to the second identifier.
  • the core network device provided in this embodiment implements the registration method of the above embodiment, and the implementation principle and technical effect of the core network device provided in this embodiment are similar to those of the above embodiment, and will not be repeated here.
  • the information related to the second terminal device includes any one or more of the following information: the context of the second terminal device, the security context of the second terminal device, the non-access stratum NAS security of the second terminal device context.
  • the receiving module 10 is further configured to acquire a second registration request message sent by the second terminal device, where the second registration request message includes a third identifier of the second terminal device, and the third identifier is the same as the first identifier;
  • the processing module 11 is further configured to perform registration for the second terminal device according to the third identifier.
  • the processing module 11 is further configured to assign a third identifier to the second terminal device after the registration of the second terminal device is completed, and the third identifier is the same as the first identifier.
  • FIG. 11 shows a schematic structural diagram of another core network device provided by an embodiment.
  • the core network device further includes: a sending module 12;
  • the sending module 12 is configured to send an identification request message to the first terminal device
  • the receiving module 10 is configured to acquire an identification response message sent by the first terminal device, where the identification response message includes the second identification.
  • the receiving module 10 is configured to acquire a third registration request message sent by the first terminal device, where the third registration request message includes the second identifier.
  • the receiving module 10 is further configured to obtain a fourth registration request message sent by the first terminal device, where the fourth registration request message includes the first identifier;
  • the processing module 11 is further configured to acquire the second terminal device related information related to the first identifier; the second terminal device related information is in an active state, and discard the fourth registration request message.
  • FIG. 12 shows a schematic structural diagram of a terminal device provided by an embodiment.
  • the terminal device includes: a sending module 20 and a processing module 21 .
  • the sending module 20 is configured to send a first registration request message to the core network device, where the first registration request message includes a first identifier of the first terminal device;
  • the processing module 21 is configured to confirm that a preset condition is met, and the preset condition is that the identification request message sent by the core network device is obtained, or any registration-related message sent by the core network device is not obtained within a preset time;
  • the sending module 20 is further configured to send the second identifier of the first terminal device to the core network device, so as to complete the registration.
  • the terminal device provided in this embodiment implements the registration method in the above embodiment, and the implementation principle and technical effect of the terminal device provided in this embodiment are similar to those in the above embodiment, and will not be repeated here.
  • the preset condition is to obtain the identification request message sent by the core network equipment
  • the sending module 20 is configured to send an identification response message to the core network device, where the identification response message includes the second identification.
  • the preset condition is that no registration-related message sent by the core network device is obtained within a preset time
  • the sending module 20 is configured to send a third registration request message to the core network device, where the third registration request message includes the second identifier.
  • the processing module 21 is further configured to make the current number of iterations K equal to 0; the sending module 20 is further configured to send a fourth registration request message to the core network device, where the fourth registration request message includes the first identifier;
  • An embodiment of the present application further provides a core network device, including: a processor, configured to implement the method provided in any embodiment of the present application when executing a computer program.
  • a core network device including: a processor, configured to implement the method provided in any embodiment of the present application when executing a computer program.
  • the following embodiments provide a schematic structural diagram in which the core network device is an AMF.
  • FIG. 13 shows a schematic structural diagram of an AMF provided by an embodiment.
  • the AMF includes a processor 60, a memory 61 and a communication interface 62; the number of processors 60 in the AMF can be one or more
  • a processor 60 is taken as an example; the processor 60, memory 61, and communication interface 62 in the AMF can be connected through a bus or in other ways.
  • the connection through a bus is taken as an example.
  • Bus refers to one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus structures.
  • the memory 61 can be configured to store software programs, computer-executable programs and modules, such as program instructions/modules corresponding to the methods in the embodiments of the present application.
  • the processor 60 executes at least one function application and data processing of the AMF by running the software programs, instructions and modules stored in the memory 61 , that is, realizes the above-mentioned registration method.
  • the memory 61 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the terminal, and the like.
  • the memory 61 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • memory 61 may include memory located remotely from processor 60, and such remote memory may be connected to the AMF via a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, networks, mobile communication networks, and combinations thereof.
  • the communication interface 62 can be configured to receive and send data.
  • An embodiment of the present application further provides a terminal device, including: a processor, configured to implement the method provided in any embodiment of the present application when the processor executes a computer program.
  • a terminal device including: a processor, configured to implement the method provided in any embodiment of the present application when the processor executes a computer program.
  • the following embodiments provide a schematic structural diagram in which a terminal device is a UE.
  • FIG 14 shows a schematic structural diagram of a UE provided by an embodiment.
  • the UE can be implemented in various forms.
  • the UE in this embodiment of the application can include but not limited to mobile phones, smart phones, notebook computers, digital broadcasting Receiver, personal digital assistant (Personal Digital Assistant, PDA), tablet computer (Portable Device, PAD), portable multimedia player (Portable Media Player, PMP), navigation device, vehicle terminal equipment, vehicle display terminal, vehicle electronic rear view Mirrors and other mobile terminal devices and fixed terminal devices such as digital television (television, TV) and desktop computers.
  • PDA Personal Digital Assistant
  • PAD tablet computer
  • PMP portable multimedia player
  • navigation device vehicle terminal equipment
  • vehicle display terminal vehicle electronic rear view Mirrors
  • vehicle electronic rear view Mirrors and other mobile terminal devices and fixed terminal devices
  • digital television television
  • TV television
  • the UE 50 may include a wireless communication unit 51, an audio/video (Audio/Video, A/V) input unit 52, a user input unit 53, a sensing unit 54, an output unit 55, a memory 56, an interface unit 57, processor 58 and power supply unit 59 and so on.
  • FIG. 14 illustrates a UE including various components, but it is understood that implementing all illustrated components is not a requirement. Greater or fewer components may alternatively be implemented.
  • the wireless communication unit 51 allows radio communication between the UE 50 and a base station or a network.
  • A/V input unit 52 is configured to receive audio or video signals.
  • the user input unit 53 can generate key input data to control various operations of the UE 50 according to commands input by the user.
  • the sensing unit 54 detects the current state of the UE 50, the position of the UE 50, the presence or absence of the user's touch input to the UE 50, the orientation of the UE 50, the acceleration or deceleration movement and direction of the UE 50, etc., and generates 50 commands or signals for operation.
  • the interface unit 57 serves as an interface through which at least one external device can be connected with the UE 50.
  • the output unit 55 is configured to provide output signals in a visual, audio and/or tactile manner.
  • the memory 56 may store software programs and the like for processing and control operations executed by the processor 58, or may temporarily store data that has been output or will be output.
  • the memory 56 may include at least one type of storage media.
  • the UE 50 may cooperate with a network storage device performing a storage function of the memory 56 through a network connection.
  • Processor 58 generally controls the overall operation of UE 50.
  • the power supply unit 59 receives external power or internal power and supplies appropriate power required to operate various elements and components under the control of the processor 58 .
  • the processor 58 executes at least one function application and data processing by running the program stored in the memory 56, for example, implementing the method provided in the embodiment of the present application.
  • the embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method provided in any embodiment of the present application is implemented.
  • the computer storage medium in the embodiments of the present application may use any combination of one or more computer-readable media.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer-readable storage medium may be, for example but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof.
  • Computer-readable storage media include (non-exhaustive list): electrical connections with one or more conductors, portable computer disks, hard disks, Random Access Memory (RAM), Read-Only Memory (Read-Only Memory) , ROM), erasable programmable read-only memory (electrically erasable, programmable Read-Only Memory, EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage components, magnetic storage devices, or any suitable combination of the above.
  • a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a data signal carrying computer readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. .
  • the program code contained on the computer readable medium can be transmitted by any appropriate medium, including but not limited to wireless, electric wire, optical cable, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • any appropriate medium including but not limited to wireless, electric wire, optical cable, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • Computer program codes for performing the operations of the present application can be written with one or more programming languages or a combination of programming languages, including object-oriented programming languages (such as Java, Smalltalk, C++, Ruby, Go), also includes conventional procedural programming languages (such as the "C" language or similar programming languages).
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer can be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or it can be connected to an external computer such as use an Internet service provider to connect via the Internet).
  • LAN Local Area Network
  • WAN Wide Area Network
  • user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • Any logic flow block diagrams in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random-access memory (RAM), optical memory devices and systems (digital versatile disc DVD or CD), etc.
  • Computer readable media may include non-transitory storage media.
  • Data processors can be of any type suitable for the local technical environment, such as but not limited to general purpose computers, special purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC ), programmable logic devices (Field-Programmable Gate Array, FGPA) and processors based on multi-core processor architecture.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FGPA programmable logic devices

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Databases & Information Systems (AREA)

Abstract

一种注册方法、终端设备、核心网设备及存储介质。该方法应用于核心网设备，包括：获取第一终端设备发送的第一注册请求消息，第一注册请求消息包括第一终端设备的第一标识(S410)；获取与第一标识相关的第二终端设备相关信息(S420)；第二终端设备相关信息处于激活态，则获取第一终端设备的第二标识(S430)；根据第二标识，为第一终端设备进行注册(S440)。

Description

一种注册方法、终端设备、核心网设备及存储介质
相关申请的交叉引用
本申请基于申请号为202111162260.5、申请日为2021年09月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请实施例涉及通信技术领域，例如涉及一种注册方法、终端设备、核心网设备及存储介质。
背景技术
标准第三代合作伙伴项目(3rd generation partnership project，3GPP)定义了在第五代移动通信技术(5th-generation，5G)系统中，用户设备(user equipment，UE)的注册流程。然而，在UE注册的过程中，如果两个UE具有相同的5G全球唯一临时UE标识(5G-Globally Unique Temporary UE Identity，5G-GUTI)，那么当其中一个UE注册完成后，可能会导致另一个UE无法正常注册。
发明内容
本申请实施例提供一种注册方法，应用于核心网设备，包括：获取第一终端设备发送的第一注册请求消息，第一注册请求消息包括第一终端设备的第一标识；获取与第一标识相关的第二终端设备相关信息；第二终端设备相关信息处于激活态，则获取第一终端设备的第二标识；根据第二标识，为第一终端设备进行注册。
本申请实施例提供一种注册方法，应用于第一终端设备，包括：向核心网设备发送第一注册请求消息，第一注册请求消息包括第一终端设备的第一标识；满足预设条件，向核心网设备发送第一终端设备的第二标识，以完成注册，预设条件为获取到核心网设备发送的标识请求消息，或者在预设时间内未获取到核心网设备发送的任意与注册相关的消息。
本申请实施例提供一种核心网设备，包括：处理器；处理器用于在执行计算机程序时实现上述任一实施例的方法。
本申请实施例提供一种终端设备，包括：处理器；处理器用于在执行计算机程序时实现上述任一实施例的方法。
本申请实施例还提供一种计算机可读存储介质，存储有计算机程序，计算机程序被处理器执行时实现上述任一实施例的方法。
关于本申请的以上实施例和其他方面以及其实现方式，在附图说明、具体实施方式和权利要求中提供更多说明。
附图说明
图1是一实施例提供的一种无线通信系统的组网示意图；
图2是一实施例提供的另一种无线通信系统的组网示意图；
图3是一实施例提供的一种5G系统中UE的注册流程示意图；
图4是一实施例提供的一种注册方法的流程示意图；
图5是一实施例提供的另一种注册方法的流程示意图；
图6是一实施例提供的一种注册方法的流程交互图；
图7是一实施例提供的另一种注册方法的流程交互图；
图8是一实施例提供的又一种注册方法的流程交互图；
图9是一实施例提供的再一种注册方法的流程交互图；
图10是一实施例提供的一种核心网设备的结构示意图；
图11是一实施例提供的另一种核心网设备的结构示意图；
图12是一实施例提供的一种终端设备的结构示意图；
图13是一实施例提供的一种AMF的结构示意图；
图14是一实施例提供的一种UE的结构示意图。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。下文中将结合附图对本申请的实施例进行详细说明。
本申请实施例提供的注册方法可以应用于各类无线通信系统中，例如长期演进(long term evolution，LTE)系统、5G系统、LTE与5G混合架构系统、5G新无线(new radio，NR)系统、以及未来通信发展中出现的新的通信系统，如第六代移动通信技术(6th-generation，6G)系统等。图1示出了一实施例提供的一种无线通信系统的组网示意图。如图1所示，该无线通信系统包括终端设备110、接入网设备120和核心网设备130。
终端设备110也可以称为终端、UE、移动台、移动终端等。终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。一些终端的举例为：手机、平板电脑、带无线收发功能的电脑、虚拟现实终端设备、增强现实终端设备、工业控制中的无线终端、无人驾驶中的无线终端、远程手术中的无线终端、智能电网中的无线终端、运输安全中的无线终端、智慧城市中的无线终端、智慧家庭中的无线终端等等。本申请的实施例对终端设备所采用的技术和设备形态不做限定。
接入网设备120是终端设备110通过无线方式接入到该无线通信系统中的接入设备，可以是基站(base station)、演进型基站(evolved NodeB，eNodeB)、发送接收点(transmission reception point，TRP)、5G移动通信系统中的下一代基站(next generation NodeB，gNB)、未来移动通信系统中的基站或WiFi系统中的接入节点等；也可以是完成基站部分功能的模块或单元，例如，可以是集中式单元(central unit，CU)，也可以是分布式单元(distributed unit，DU)。本申请的实施例对接入网设备所采用的技术和设备形态不做限定。
核心网设备130可以包括接入与移动性管理网元和会话管理网元。示例性地，终端设备110可以通过接入网设备120接入核心网，从而实现数据传输。
由于本申请实施例的注册方法主要基于5G移动通信技术以及未来的其他移动通信技术，下面结合图2介绍本申请实施例的另一种无线通信系统架构——5G系统架构。图2示出了一实施例提供的另一种无线通信系统的组网示意图。如图2所示，该无线通信系统包括：
1、用户设备UE。
2、(无线)接入网(radio access network，(R)AN)：用于为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道。(R)AN网元能够管理无线资源，为终端设备提供接入服务，进而完成控制信号和用户数据在终端设备和核心网之间的转发，(R)AN也可以理解为传统网络中的基站。
3、接入和移动性管理功能(access and mobility management function，AMF)：主要用于移动性管理和接入管理等。AMF可以用于实现移动性管理实体(mobility management entity，MME)的功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能。
4、会话管理功能(Session Management Function，SMF)：又可称为会话管理功能网元，主要用于会话管理、终端设备的网络互连协议(Internet Protocol，IP)地址分配和管理、选择可管理用户平面功能、策略控制、或收费功能接口的终结点以及下行数据通知等。
可以理解的是，在图1所示的无线通信系统中，接入网设备120可以为图2中的RAN；接入与移动性管理网元可以为图2中的AMF；会话管理网元可以为图2中的SMF。
该无线通信系统还可以包括：
5、用户平面功能(user plane function，UPF)：又可称为用户面功能或用户面网元或用户面功能网元，用于分组路由和转发、或用户面数据的服务质量(quality of service，QoS)处理等。UPF分为中间-UPF(intermediate-UPF，I-UPF)和锚点UPF(anchor-UPF，A-UPF)。其中，I-UPF与接入网RAN连接，A-UPF为会话锚点的UPF，A-UPF又可以称为协议数据单元(protocol data unit，PDU)会话锚点(PDU session anchor，PSA)。
6、数据网络(data network，DN)：用于提供传输数据的网络，例如，Internet网络等。在本申请实施例的架构中，PSA接入远端DN。
7、认证服务功能(authentication server function，AUSF)：主要用于用户鉴权等。
8、策略控制功能(policy control function，PCF)：用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF、SMF网元等)提供策略规则信息等。
9、统一数据管理(unified data management，UDM)：用于处理用户标识、接入鉴权、注册、或移动性管理等。
10、应用功能(application function，AF)：主要支持与3GPP核心网交互来提供服务，例如，影响 数据路由决策、策略控制功能、或者向网络侧提供第三方的一些服务。可理解为第三方服务器，例如，Internet中的应用服务器，提供相关业务信息，包括向PCF提供业务对应的服务质量需求信息，以及向PSA-UPF发送业务的用户面数据信息。AF可以是服务提供商(content provider，CP)。
11、网络切片选择功能(network slice selection function，NSSF)：用于进行网络切片的选择。
在该无线通信系统中，N1接口为终端设备与AMF之间的参考点；N2接口为(R)AN和AMF的参考点，用于非接入层(non-access stratum，NAS)消息的发送等；N3接口为(R)AN和I-UPF之间的参考点，用于传输用户面的数据等；N4接口为SMF和I-UPF之间的参考点，用于传输例如N3连接的隧道标识信息、数据缓存指示信息、以及下行数据通知消息等信息；N5接口为PCF与AF之间的参考点；N6接口为UPF和DN之间的参考点，用于传输用户面的数据等；N7接口为SMF和PCF之间的参考点；N8接口为AMF和UDM之间的参考点；N9接口为UPF之间的参考点；N10接口为SMF与UDM之间的参考点；N11接口为AMF与SMF之间的参考点；N12接口为AMF与AUSF之间的参考点；N13接口为AUSF与UDM之间的参考点；N22接口为AMF与NSSF之间的参考点。
该无线通信系统还可以包括：
12、组播控制面功能(multicast control plane function，MCF)：用于对组播业务进行控制，MCF与服务提供商对接，以便接收组播业务相关信息(例如组播业务的描述)，MCF与PCF对接，以便为组播业务创建资源。此处应注意，在5G网络中，上述MCF网元还可以是其它名称，其实现的是组播业务的控制面功能。
13、组播用户面功能(multicast user plane function，MUF)：用于传递组播业务相关数据，即，将从CP接收到的组播数据发送给UPF。此处应注意，在5G网络中，上述MUF网元还可以是其它名称，其实现的是组播业务的用户面功能。
该无线通信系统中，MCF可以集成到PCF(或SMF)中，MUF可集成到UPF中，本申请实施例对此不作限定。
可以理解的是，上述应用于本申请实施例的无线通信系统仅是举例说明的从参考点架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
另外，图2中的各个网元之间的接口名称只是一个示例，实现中接口的名称可能为其他的名称。图2中包括的各个网元(比如SMF、AF、UPF等)的名称也仅是一个示例，对网元本身的功能不构成限定。在5G网络以及未来其它的网络中，上述各个网元也可以是其他的名称，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称，等等。此外，应理解，上述各个网元之间所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
图3示出了一实施例提供的一种5G系统中UE的注册流程示意图。如图3所示，注册流程可以包括如下步骤：
1.UE向(R)AN发送注册请求；
2.AMF选择过程，即(R)AN按照自身策略选择AMF；
3.(R)AN向新AMF发送注册请求；
4.新AMF向历史AMF发送完整注册请求；
5.历史AMF回复完整注册请求响应；
6.新AMF向UE发起认证请求；
7.UE回复认证请求响应；
8.AUSF选择过程；
9.鉴权流程与安全流程；
10.新AMF向历史AMF发送注册完成通知；
11.新AMF向UE发起认证请求，并接收UE返回的认证响应；
12.新AMF向设备标识寄存器(Equipment Identity Register，EIR)发起设备身份认证流程；
13.UDM选择过程；
14a.向UDM发起注册请求(Nudm_UECM_Registration)；
14b.检索SMF数据中的访问和移动订阅数据；
14c.新AMF向UDM发送请求的数据被修改通知；
14d.UDM向历史AMF发送注册通知(Nudm_UECM_DeregistrationNotification)，以使历史AMF删除UE的上下文信息；
14e.历史AMF向UDM发送取消订阅消息；
15.PCF选择过程；
16.新AMF执行AM策略关联建立/修改；
17.新AMF向SMF发送网络切片管理功能(network slice management function，NSMF)会话内容更新/释放上下文请求；
18.新AMF向非3GPP互通功能(N3IWF)/受信任的非3GPP网关功能(TNGF)/有线接入网关功能(W-AGF)发送N2 AMF移动请求(如UE context modification request)；
19.N3IWF/TNGF/W-AGF向新AMF回复N2 AMF移动请求响应(如UE context modification response)；
19a.在新AMF在步骤19中从N3IWF/TNGF/W-AGF接收到N2 AMF移动请求响应之后，新AMF使用Nudm_UECM_Registration作为步骤14c向UDM注册，但是将接入类型设置为“非3GPP接入”；
19b.当UDM将接入类型(即非3GPP)与服务的AMF一起存储时，UDM向历史AMF发起Nudm_UECM_DeregistrationNotification对应于相同(即非3GPP)的访问，旧AMF移除用于非3GPP接入的UE上下文；
19c.历史AMF使用Nudm_SDM_unsubscribe取消订阅UDM；
21.新AMF向UE发送注册接受消息；
21b.UE政策协会成立(UE Policy Association Establishment)，对于紧急注册，将跳过此步骤；
22.UE向新AMF发送注册完成消息；
23.新AMF提供UE使用的Nudm_SDM_Info对UDM确认；
23a.对于通过3GPP接入的注册，如果新AMF未释放信令连接，则新AMF将RRC无效辅助信息发送到(R)AN；对于非3GPP接入的注册，如果UE在3GPP接入上也处于CM-CONNECTED状态，则新AMF将RRC无效辅助信息发送到(R)AN；
24.新AMF使用Nudm_UECM_Update向UDM发送“基于PS会话的IMS语音的同类支持”指示；
25.特定网络切片的身份验证和授权。
假设UE A通过5G-GUTI向AMF发起注册流程，AMF执行上述图3中的步骤4-22。当UE A完成注册后，UE A的上下文处于激活态。此时如果UE B通过5G-GUTI向AMF发起注册流程，UE B的5G-GUTI和UE A的5G-GUTI相同，由于AMF已经和UE A建立了安全上下文并且已经启用NAS安全，对NAS消息进行了完整性保护；UE B同样根据UE B的上下文对NAS消息进行完整性保护。但在AMF中，该5G-GUTI标识的是UE A的上下文，因此UE B的NAS消息无法通过AMF的完整性校验，AMF会丢弃UE B的注册消息，导致UE B无法正常注册。
UE B的5G-GUTI和UE A的5G-GUTI相同，这种现象发生的原因可能是：
1)AMF为UE A和UE B分配了相同的5G-GUTI：按照3GPP TS 23.501第5.9.4章节的描述，<5G-GUTI>:＝<GUAMI><5G-TMSI>，全球唯一AMF ID(Globally Unique AMF Identifier，GUAMI)标识了一个或者多个AMF。同一个AMF可能为不同的UE分配了相同的5G临时移动用户识别码(5G-Temporary Mobile Subscriber Identity，5G-TMSI)导致不同的UE具有相同的5G-GUTI。
2)AMF为UE B分配了一个5G-GUTI，UE B离开网络后，AMF将这个5G-GUTI重新分配给了UE A，此后UE B重新接入网络。
在本申请实施例中，提供一种可运行于上述无线通信系统的注册方法、终端设备、核心网设备及存储介质，能够解决终端设备无法正常注册到网络的问题，提升用户体验。
下面，对注册方法、终端设备、核心网设备及其技术效果进行描述。
图4示出了一实施例提供的一种注册方法的流程示意图，如图4所示，本实施例提供的方法适用于核心网设备(如AMF)，该方法包括如下步骤。
S410、获取第一终端设备发送的第一注册请求消息，第一注册请求消息包括第一终端设备的第一标识。
由于本申请实施例要解决终端设备无法正常注册到网络的问题，因此当步骤S410执行时，网络内已经接入了第二终端设备，且第二终端设备的第三标识与第一标识相同。
第三标识与第一标识相同，可以包括如下两种情况中的任一种：
情况一、在步骤S410执行前，核心网设备获取第二终端设备发送的第二注册请求消息，第二注册请求消息包括第二终端设备的第三标识，第三标识与第一标识相同；根据第三标识，为第二终端设备进行注册。
情况二、在第二终端设备完成注册后、且在步骤S410执行前，核心网设备为第二终端设备分配第三标识，第三标识与第一标识相同。
在一实施例中，第一标识和第三标识为同一类型的标识，例如5G-GUTI。
S420、获取与第一标识相关的第二终端设备相关信息。
在一实施例中，第二终端设备相关信息包括以下信息中的任意一种或多种：第二终端设备的上下文、第二终端设备的安全上下文、第二终端设备的非接入层NAS安全上下文。
S430、第二终端设备相关信息处于激活态，则获取第一终端设备的第二标识。
第二终端设备相关信息处于激活态，表示此时第二终端设备存在NAS安全连接，那么核心网设备无法再通过第一标识为第一终端设备进行注册。此时，核心网设备获取第一终端设备的第二标识。
在一实施例中，第一标识和第二标识为不同类型的标识。第二标识可以为订阅隐藏标识符(subscription concealed identifier，SUCI)。
在一实施例中，步骤S430中“获取第二标识”的方法可以包括如下两种方法中的任一种：
方法A1、核心网设备向第一终端设备发送标识请求消息；获取第一终端设备发送的标识响应消息，标识响应消息包括第二标识。
在方法A1中，核心网设备能够主动向第一终端设备发送标识请求消息，以获取第二标识。
方法A2、获取第一终端设备发送的第三注册请求消息，第三注册请求消息包括第二标识。
在方法A2中，核心网设备不会主动获取第二标识，第二标识由第一终端设备主动向核心网设备发送。第一终端设备主动向核心网设备发送第二标识的时机为：第一终端设备在预设时间内未获取到核心网设备发送的任意与注册相关的消息，第一终端设备重新尝试注册流程并失败一定次数后，向核心网设备发送第二标识。
即，在核心网设备获取第一终端设备发送的第三注册请求消息前，核心网设备还可以：获取第一终端设备发送的第四注册请求消息，第四注册请求消息包括第一标识；获取与第一标识相关的第二终端设备相关信息；第二终端设备相关信息处于激活态，丢弃第四注册请求消息。
S440、根据第二标识，为第一终端设备进行注册。
在本申请实施例中，核心网设备当无法通过第一标识为第一终端设备进行注册时，可以获取第二标识，为第一终端设备进行注册。保证了第一终端设备能够顺利注册到网络，提升用户体验。
图5示出了一实施例提供的另一种注册方法的流程示意图，如图5所示，本实施例提供的方法适用于第一终端设备(如UE A)，该方法包括如下步骤。
S510、向核心网设备发送第一注册请求消息，第一注册请求消息包括第一终端设备的第一标识。
在一实施例中，第一标识可以为5G-GUTI。
S520、满足预设条件，向核心网设备发送第一终端设备的第二标识，以完成注册，预设条件为获取到核心网设备发送的标识请求消息，或者在预设时间内未获取到核心网设备发送的任意与注册相关的消息。
在一实施例中，第一标识和第二标识为不同类型的标识。第二标识可以为SUCI。
在一实施例中，当预设条件为获取到核心网设备发送的标识请求消息时，第一终端设备向核心网设备发送第二标识，包括：向核心网设备发送标识响应消息，标识响应消息包括第二标识。
在一实施例中，当预设条件为在预设时间内未获取到核心网设备发送的任意与注册相关的消息时，第一终端设备向核心网设备发送第二标识，包括：向核心网设备发送第三注册请求消息，第三注册请求消息包括第二标识。
在第一终端设备向核心网设备发送第三注册请求消息前，还包括：
第一终端设备令当前迭代次数K等于0，向核心网设备发送第四注册请求消息，第四注册请求消息包括第一标识；在预设时间内未获取到核心网设备发送的任意与注册相关的消息，令当前迭代次数K＝K+1，且在当前迭代次数K小于最大迭代次数时，返回执行向核心网设备发送第四注册请求消息的步骤，直至当前迭代次数等于最大迭代次数为止。
下面罗列一些示例性实施方式，用于解释说明本申请实施例图4-图5提供的注册方法，下述示例性实施方式可以单一执行，也可以组合执行。在下述示例性实施方式中，第一终端设备记为UE B，第二终端设备记为UE A，核心网设备记为AMF，第一终端设备的第一标识记为UE B的5G-GUTI，第一终端设备的第二标识记为UE B的SUCI，第二终端设备的第三标识记为UE A的5G-GUTI。
在第一个示例性实施方式中，图6示出了一实施例提供的一种注册方法的流程交互图。如图6所示，该方法包括如下步骤。
S601、UE A向AMF发送第二注册请求消息，第二注册请求消息包括UE A的5G-GUTI。
S602、AMF根据UE A的5G-GUTI，为UE A进行注册。
为UE A进行注册的方法可以参考图3中的步骤4-22，为了简洁，此处不再赘述。
S603、UE B向AMF发送第一注册请求消息，第一注册请求消息包括UE B的5G-GUTI，UE A的5G-GUTI与UE B的5G-GUTI相同。
S604、AMF判断是否能获取到与该5G-GUTI相关的UE A相关信息。
S605、若AMF不能获取到UE A相关信息，则根据UE B的5G-GUTI，为UE B进行注册。
若AMF不能获取到UE A相关信息，表示此时AMF尚未和UE A建立安全上下文，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S606、若AMF能获取到与UE A相关信息，则判断UE A相关信息是否处于激活态。
S607、若UE A相关信息处于未激活态，则根据UE B的5G-GUTI，为UE B进行注册。
若UE A相关信息处于未激活态，表示此时AMF虽然和UE A建立了安全上下文，但并未启用NAS安全，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S608、若UE A相关信息处于激活态，则向UE B发送标识请求消息。
若UE A相关信息处于激活态，表示此时AMF已经和UE A建立了安全上下文并且已经启用NAS安全，对NAS消息进行了完整性保护。在AMF中，该5G-GUTI标识的是UE A的上下文，因此UE B的NAS消息无法通过AMF的完整性校验，因此AMF需要向UE B发送标识请求消息。
S609、UE B向AMF发送标识响应消息，标识响应消息包括UE B的SUCI。
S610、AMF根据UE B的SUCI，为UE B进行注册。
AMF根据UE B的SUCI，参考图3中的步骤8-22为UE B进行注册。从而保证了UE B能够顺利注册到网络，提升用户体验。
在第二个示例性实施方式中，图7示出了一实施例提供的另一种注册方法的流程交互图。如图7所示，该方法包括如下步骤。
S701、在UE A完成注册后，AMF为UE A分配UE A的5G-GUTI。
在步骤S701执行之前，UE A已经利用其他5G-GUTI注册至网络，由于带宽需要等因素，AMF可以为UE A重新分配一个5G-GUTI，即UE A的5G-GUTI。
S702、UE B向AMF发送第一注册请求消息，第一注册请求消息包括UE B的5G-GUTI，UE A的5G-GUTI与UE B的5G-GUTI相同。
S703、AMF判断是否能获取到与该5G-GUTI相关的UE A相关信息。
S704、若AMF不能获取到UE A相关信息，则根据UE B的5G-GUTI，为UE B进行注册。
若AMF不能获取到UE A相关信息，表示此时AMF尚未和UE A建立安全上下文，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S705、若AMF能获取到与UE A相关信息，则判断UE A相关信息是否处于激活态。
S706、若UE A相关信息处于未激活态，则根据UE B的5G-GUTI，为UE B进行注册。
若UE A相关信息处于未激活态，表示此时AMF虽然和UE A建立了安全上下文，但并未启用NAS安全，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S707、若UE A相关信息处于激活态，则向UE B发送标识请求消息。
若UE A相关信息处于激活态，表示此时AMF已经和UE A建立了安全上下文并且已经启用NAS安全，对NAS消息进行了完整性保护。在AMF中，该5G-GUTI标识的是UE A的上下文，因此UE B的NAS消息无法通过AMF的完整性校验，因此AMF需要向UE B发送标识请求消息。
S708、UE B向AMF发送标识响应消息，标识响应消息包括UE B的SUCI。
S709、AMF根据UE B的SUCI，为UE B进行注册。
AMF根据UE B的SUCI，参考图3中的步骤8-22为UE B进行注册。从而保证了UE B能够顺利注册到网络，提升用户体验。
在第三个示例性实施方式中，图8示出了一实施例提供的又一种注册方法的流程交互图。如图8所示，该方法包括如下步骤。
S801、UE A向AMF发送第二注册请求消息，第二注册请求消息包括UE A的5G-GUTI。
S802、AMF根据UE A的5G-GUTI，为UE A进行注册。
为UE A进行注册的方法可以参考图3中的步骤4-22，为了简洁，此处不再赘述。
S803、UE B向AMF发送第一注册请求消息，第一注册请求消息包括UE B的5G-GUTI，UE A的5G-GUTI与UE B的5G-GUTI相同。
S804、AMF判断是否能获取到与该5G-GUTI相关的UE A相关信息。
S805、若AMF不能获取到UE A相关信息，则根据UE B的5G-GUTI，为UE B进行注册。
若AMF不能获取到UE A相关信息，表示此时AMF尚未和UE A建立安全上下文，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S806、若AMF能获取到与UE A相关信息，则判断UE A相关信息是否处于激活态。
S807、若UE A相关信息处于未激活态，则根据UE B的5G-GUTI，为UE B进行注册。
若UE A相关信息处于未激活态，表示此时AMF虽然和UE A建立了安全上下文，但并未启用NAS安全，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S808、若UE A相关信息处于激活态，则丢弃第一注册请求消息。
若UE A相关信息处于激活态，表示此时AMF已经和UE A建立了安全上下文并且已经启用NAS安全，对NAS消息进行了完整性保护。在AMF中，该5G-GUTI标识的是UE A的上下文，因此UE B的NAS消息无法通过AMF的完整性校验，AMF丢弃第一注册请求消息。
S809、UE B在预设时间内未获取到AMF发送的任意与注册相关的消息，令当前迭代次数K等于0，向 AMF发送第四注册请求消息，第四注册请求消息包括UE B的5G-GUTI。
S810、AMF判断是否能获取到与该5G-GUTI相关的UE A相关信息，若不能，则根据UE B的5G-GUTI，为UE B进行注册，若能，则判断UE A相关信息是否处于激活态；若处于未激活态，则根据UE B的5G-GUTI，为UE B进行注册，若处于激活态，则丢弃第四注册请求消息。
S811、UE B在预设时间内未获取到AMF发送的任意与注册相关的消息，令当前迭代次数K＝K+1，且在当前迭代次数K小于最大迭代次数时，返回执行向AMF发送第四注册请求消息的步骤，直至当前迭代次数等于最大迭代次数为止。
为了保证UE B能够顺利接入网络，UE B在预设时间内未获取到AMF发送的任意与注册相关的消息时，可以重新尝试若干次注册流程。其中，尝试的次数(最大迭代次数)可以根据实际情况进行设计，例如最大迭代次数为3次。
在这个过程中，如果AMF和UE A断开安全上下文，或者关闭NAS安全，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册；如果AMF仍旧和UE A建立了安全上下文并且已经启用NAS安全，则继续执行下述步骤S812-S813。
S812、UE B向AMF发送第三注册请求消息，第三注册请求消息包括UE B的SUCI。
S813、AMF根据UE B的SUCI，为UE B进行注册。
UE B主动向AMF发送包括UE B的SUCI的第三注册请求消息，以使得AMF根据UE B的SUCI，参考图3中的步骤8-22为UE B进行注册。从而保证了UE B能够顺利注册到网络，提升用户体验。
在第四个示例性实施方式中，图9示出了一实施例提供的再一种注册方法的流程交互图。如图9所示，该方法包括如下步骤。
S901、在UE A完成注册后，AMF为UE A分配UE A的5G-GUTI。
在步骤S901执行之前，UE A已经利用其他5G-GUTI注册至网络，由于带宽需要等因素，AMF可以为UE A重新分配一个5G-GUTI，即UE A的5G-GUTI。
S902、UE B向AMF发送第一注册请求消息，第一注册请求消息包括UE B的5G-GUTI，UE A的5G-GUTI与UE B的5G-GUTI相同。
S903、AMF判断是否能获取到与该5G-GUTI相关的UE A相关信息。
S904、若AMF不能获取到UE A相关信息，则根据UE B的5G-GUTI，为UE B进行注册。
若AMF不能获取到UE A相关信息，表示此时AMF尚未和UE A建立安全上下文，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S905、若AMF能获取到与UE A相关信息，则判断UE A相关信息是否处于激活态。
S906、若UE A相关信息处于未激活态，则根据UE B的5G-GUTI，为UE B进行注册。
若UE A相关信息处于未激活态，表示此时AMF虽然和UE A建立了安全上下文，但并未启用NAS安全，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册。
S907、若UE A相关信息处于激活态，则丢弃第一注册请求消息。
若UE A相关信息处于激活态，表示此时AMF已经和UE A建立了安全上下文并且已经启用NAS安全，对NAS消息进行了完整性保护。在AMF中，该5G-GUTI标识的是UE A的上下文，因此UE B的NAS消息无法通过AMF的完整性校验，AMF丢弃第一注册请求消息。
S908、UE B在预设时间内未获取到AMF发送的任意与注册相关的消息，令当前迭代次数K等于0，向AMF发送第四注册请求消息，第四注册请求消息包括UE B的5G-GUTI。
S909、AMF判断是否能获取到与该5G-GUTI相关的UE A相关信息，若不能，则根据UE B的5G-GUTI，为UE B进行注册，若能，则判断UE A相关信息是否处于激活态；若处于未激活态，则根据UE B的5G-GUTI，为UE B进行注册，若处于激活态，则丢弃第四注册请求消息。
S910、UE B在预设时间内未获取到AMF发送的任意与注册相关的消息，令当前迭代次数K＝K+1，且在当前迭代次数K小于最大迭代次数时，返回执行向AMF发送第四注册请求消息的步骤，直至当前迭代次数等于最大迭代次数为止。
为了保证UE B能够顺利接入网络，UE B在预设时间内未获取到AMF发送的任意与注册相关的消息时，可以重新尝试若干次注册流程。其中，尝试的次数(最大迭代次数)可以根据实际情况进行设计，例如最大迭代次数为3次。
在这个过程中，如果AMF和UE A断开安全上下文，或者关闭NAS安全，此时可以根据UE B的5G-GUTI，参考图3中的步骤4-22为UE B进行注册；如果AMF仍旧和UE A建立了安全上下文并且已经启用NAS安全，则继续执行下述步骤S911-S912。
S911、UE B向AMF发送第三注册请求消息，第三注册请求消息包括UE B的SUCI。
S912、AMF根据UE B的SUCI，为UE B进行注册。
UE B主动向AMF发送包括UE B的SUCI的第三注册请求消息，以使得AMF根据UE B的SUCI，参考图 3中的步骤8-22为UE B进行注册。从而保证了UE B能够顺利注册到网络，提升用户体验。
图10示出了一实施例提供的一种核心网设备的结构示意图，如图10所示，核心网设备包括：接收模块10和处理模块11。
接收模块10，设置为获取第一终端设备发送的第一注册请求消息，第一注册请求消息包括第一终端设备的第一标识；
处理模块11，设置为获取与第一标识相关的第二终端设备相关信息；
接收模块10，还设置为第二终端设备相关信息处于激活态，则获取第一终端设备的第二标识；
处理模块11，还设置为根据第二标识，为第一终端设备进行注册。
本实施例提供的核心网设备为实现上述实施例的注册方法，本实施例提供的核心网设备实现原理和技术效果与上述实施例类似，此处不再赘述。
在一实施例中，第二终端设备相关信息包括以下信息中的任意一种或多种：第二终端设备的上下文、第二终端设备的安全上下文、第二终端设备的非接入层NAS安全上下文。
在一实施例中，接收模块10，还设置为获取第二终端设备发送的第二注册请求消息，第二注册请求消息包括第二终端设备的第三标识，第三标识与第一标识相同；
处理模块11，还设置为根据第三标识，为第二终端设备进行注册。
在一实施例中，处理模块11，还设置为在第二终端设备完成注册后，为第二终端设备分配第三标识，第三标识与第一标识相同。
在一实施例中，图11示出了一实施例提供的另一种核心网设备的结构示意图，如图11所示，核心网设备还包括：发送模块12；
发送模块12，设置为向第一终端设备发送标识请求消息；
接收模块10，是设置为获取第一终端设备发送的标识响应消息，标识响应消息包括第二标识。
在一实施例中，接收模块10，是设置为获取第一终端设备发送的第三注册请求消息，第三注册请求消息包括第二标识。
在一实施例中，接收模块10，还设置为获取第一终端设备发送的第四注册请求消息，第四注册请求消息包括第一标识；
处理模块11，还设置为获取与第一标识相关的第二终端设备相关信息；第二终端设备相关信息处于激活态，丢弃第四注册请求消息。
图12示出了一实施例提供的一种终端设备的结构示意图，如图12所示，终端设备包括：发送模块20和处理模块21。
发送模块20，设置为向核心网设备发送第一注册请求消息，第一注册请求消息包括第一终端设备的第一标识；
处理模块21，设置为确认满足预设条件，预设条件为获取到核心网设备发送的标识请求消息，或者在预设时间内未获取到核心网设备发送的任意与注册相关的消息；
发送模块20，还设置为向核心网设备发送第一终端设备的第二标识，以完成注册。
本实施例提供的终端设备为实现上述实施例的注册方法，本实施例提供的终端设备实现原理和技术效果与上述实施例类似，此处不再赘述。
在一实施例中，预设条件为获取到核心网设备发送的标识请求消息；
发送模块20，是设置为向核心网设备发送标识响应消息，标识响应消息包括第二标识。
在一实施例中，预设条件为在预设时间内未获取到核心网设备发送的任意与注册相关的消息；
发送模块20，是设置为向核心网设备发送第三注册请求消息，第三注册请求消息包括第二标识。
在一实施例中，处理模块21，还设置为令当前迭代次数K等于0；发送模块20，还设置为向核心网设备发送第四注册请求消息，第四注册请求消息包括第一标识；
处理模块21，还设置为确认在预设时间内未获取到核心网设备发送的任意与注册相关的消息，令当前迭代次数K＝K+1，且在当前迭代次数K小于最大迭代次数时，发送模块20返回执行向核心网设备发送第四注册请求消息的步骤，直至当前迭代次数等于最大迭代次数为止。
本申请实施例还提供了一种核心网设备，包括：处理器，处理器用于在执行计算机程序时实现如本申请任意实施例所提供的方法。示例性的，下述实施例提供一种核心网设备为AMF的结构示意图。
图13示出了一实施例提供的一种AMF的结构示意图，如图13所示，该AMF包括处理器60、存储器61和通信接口62；AMF中处理器60的数量可以是一个或多个，图13中以一个处理器60为例；AMF中的处理器60、存储器61、通信接口62可以通过总线或其他方式连接，图13中以通过总线连接为例。总线表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器，外围总线，图形加速端口，处理器或者使用多种总线结构中的任意总线结构的局域总线。
存储器61作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例中的方法对应的程序指令/模块。处理器60通过运行存储在存储器61中的软件程序、指令以及模块，从而执行AMF的至少一种功能应用以及数据处理，即实现上述的注册方法。
存储器61可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据终端的使用所创建的数据等。此外，存储器61可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器61可包括相对于处理器60远程设置的存储器，这些远程存储器可以通过网络连接至AMF。上述网络的实例包括但不限于互联网、企业内部网、网络、移动通信网及其组合。
通信接口62可设置为数据的接收与发送。
本申请实施例还提供了一种终端设备，包括：处理器，处理器用于在执行计算机程序时实现如本申请任意实施例所提供的方法。示例性的，下述实施例提供一种终端设备为UE的结构示意图。
图14示出了一实施例提供的一种UE的结构示意图，UE可以以多种形式来实施，本申请实施例中的UE可以包括但不限于诸如移动电话、智能电话、笔记本电脑、数字广播接收器、个人数字助理(Personal Digital Assistant，PDA)、平板电脑(Portable Device，PAD)、便携式多媒体播放器(Portable Media Player，PMP)、导航装置、车载终端设备、车载显示终端、车载电子后视镜等等的移动终端设备以及诸如数字电视(television，TV)、台式计算机等等的固定终端设备。
如图14所示，UE 50可以包括无线通信单元51、音频/视频(Audio/Video，A/V)输入单元52、用户输入单元53、感测单元54、输出单元55、存储器56、接口单元57、处理器58和电源单元59等等。图14示出了包括多种组件的UE，但是应理解的是，并不要求实施所有示出的组件。可以替代地实施更多或更少的组件。
本实施例中，无线通信单元51允许UE 50与基站或网络之间的无线电通信。A/V输入单元52设置为接收音频或视频信号。用户输入单元53可以根据用户输入的命令生成键输入数据以控制UE 50的多种操作。感测单元54检测UE 50的当前状态、UE 50的位置、用户对于UE 50的触摸输入的有无、UE 50的取向、UE 50的加速或减速移动和方向等等，并且生成用于控制UE 50的操作的命令或信号。接口单元57用作至少一个外部装置与UE 50连接可以通过的接口。输出单元55被构造为以视觉、音频和/或触觉方式提供输出信号。存储器56可以存储由处理器58执行的处理和控制操作的软件程序等等，或者可以暂时地存储己经输出或将要输出的数据。存储器56可以包括至少一种类型的存储介质。而且，UE 50可以与通过网络连接执行存储器56的存储功能的网络存储装置协作。处理器58通常控制UE 50的总体操作。电源单元59在处理器58的控制下接收外部电力或内部电力并且提供操作多种元件和组件所需的适当的电力。
处理器58通过运行存储在存储器56中的程序，从而执行至少一种功能应用以及数据处理，例如实现本申请实施例所提供的方法。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，该计算机程序被处理器执行时实现如本申请任意实施例所提供的方法。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是但不限于：电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质包括(非穷举的列表)：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、可擦式可编程只读存储器(electrically erasable,programmable Read-Only Memory，EPROM)、闪存、光纤、便携式紧凑磁盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本申请中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，数据信号中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于无线、电线、光缆、射频(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或多种程序设计语言组合来编写用于执行本申请操作的计算机程序代码，程序设计语言包括面向对象的程序设计语言(诸如Java、Smalltalk、C++、Ruby、Go)，还包括常规的过程式程序设计语言(诸如“C”语言或类似的程序设计语言)。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意 种类的网络(包括网络(Local Area Network，LAN)或广域网(Wide Area Network，WAN))连接到用户计算机，或者，可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(ROM)、随机访问存储器(RAM)、光存储器装置和系统(数码多功能光碟DVD或CD光盘)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field－Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。

Claims (14)

  1. 一种注册方法，应用于核心网设备，包括：
    获取第一终端设备发送的第一注册请求消息，所述第一注册请求消息包括所述第一终端设备的第一标识；
    获取与所述第一标识相关的第二终端设备相关信息；
    所述第二终端设备相关信息处于激活态，则获取所述第一终端设备的第二标识；以及
    根据所述第二标识，为所述第一终端设备进行注册。
  2. 根据权利要求1所述的注册方法，其中，所述第二终端设备相关信息包括以下信息中的任意一种或多种：第二终端设备的上下文、或第二终端设备的安全上下文、或第二终端设备的非接入层NAS安全上下文。
  3. 根据权利要求1所述的注册方法，其中，在获取第一终端设备发送的第一注册请求消息前，还包括：
    获取第二终端设备发送的第二注册请求消息，所述第二注册请求消息包括所述第二终端设备的第三标识，所述第三标识与所述第一标识相同；
    根据所述第三标识，为所述第二终端设备进行注册。
  4. 根据权利要求1所述的注册方法，其中，在获取第一终端设备发送的第一注册请求消息前，还包括：
    在第二终端设备完成注册后，为所述第二终端设备分配第三标识，所述第三标识与所述第一标识相同。
  5. 根据权利要求1-4中任一所述的注册方法，其中，所述获取第二标识，包括：
    向所述第一终端设备发送标识请求消息；
    获取所述第一终端设备发送的标识响应消息，所述标识响应消息包括所述第二标识。
  6. 根据权利要求1-4中任一所述的注册方法，其中，所述获取第二标识，包括：
    获取所述第一终端设备发送的第三注册请求消息，所述第三注册请求消息包括所述第二标识。
  7. 根据权利要求6所述的注册方法，其中，在获取所述第一终端设备发送的第三注册请求消息前，还包括：
    获取所述第一终端设备发送的第四注册请求消息，所述第四注册请求消息包括第一标识；
    获取与所述第一标识相关的第二终端设备相关信息；以及
    所述第二终端设备相关信息处于激活态，丢弃所述第四注册请求消息。
  8. 一种注册方法，应用于第一终端设备，包括：
    向核心网设备发送第一注册请求消息，所述第一注册请求消息包括所述第一终端设备的第一标识；
    满足预设条件，向所述核心网设备发送所述第一终端设备的第二标识，以完成注册，所述预设条件为获取到所述核心网设备发送的标识请求消息，或者在预设时间内未获取到所述核心网设备发送的任意与注册相关的消息。
  9. 根据权利要求8所述的方法，其中，所述预设条件为获取到所述核心网设备发送的标识请求消息；所述向所述核心网设备发送第二标识，包括：
    向所述核心网设备发送标识响应消息，所述标识响应消息包括所述第二标识。
  10. 根据权利要求8所述的方法，其中，所述预设条件为在预设时间内未获取到所述核心网设备发送的任意与注册相关的消息；所述向所述核心网设备发送第二标识，包括：
    向所述核心网设备发送第三注册请求消息，所述第三注册请求消息包括所述第二标识。
  11. 根据权利要求10所述的方法，其中，在向所述核心网设备发送第三注册请求消息前，还包括：
    令当前迭代次数K等于0，向所述核心网设备发送第四注册请求消息，所述第四注册请求消息包括第一标识；
    在预设时间内未获取到所述核心网设备发送的任意与注册相关的消息，令当前迭代次数K＝K+1，且在当前迭代次数K小于最大迭代次数时，返回执行向所述核心网设备发送第四注册请求消息的步骤，直至当前迭代次数等于最大迭代次数为止。
  12. 一种核心网设备，包括：处理器；所述处理器用于在执行计算机程序时实现如权利要求1-7中任一所述的注册方法。
  13. 一种终端设备，包括：处理器；所述处理器用于在执行计算机程序时实现如权利要求8-11中任一所述的注册方法。
  14. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-7中任一所述的注册方法，或者实现如权利要求8-11中任一所述的注册方法。
PCT/CN2022/090050 2021-09-30 2022-04-28 一种注册方法、终端设备、核心网设备及存储介质 WO2023050799A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020247011250A KR20240049681A (ko) 2021-09-30 2022-04-28 등록 방법, 단말 기기, 코어 네트워크 기기 및 저장 매체

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111162260.5A CN115915386A (zh) 2021-09-30 2021-09-30 一种注册方法、终端设备、核心网设备及存储介质
CN202111162260.5 2021-09-30

Publications (1)

Publication Number Publication Date
WO2023050799A1 true WO2023050799A1 (zh) 2023-04-06

Family

ID=85729506

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/090050 WO2023050799A1 (zh) 2021-09-30 2022-04-28 一种注册方法、终端设备、核心网设备及存储介质

Country Status (3)

Country Link
KR (1) KR20240049681A (zh)
CN (1) CN115915386A (zh)
WO (1) WO2023050799A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110769420A (zh) * 2018-07-25 2020-02-07 中兴通讯股份有限公司 网络接入方法、装置、终端、基站和可读存储介质
WO2020088941A1 (en) * 2018-10-31 2020-05-07 Ntt Docomo, Inc. Network component, communication terminal, method for serving a communication terminal and method for using a communication network
CN112567833A (zh) * 2018-08-13 2021-03-26 苹果公司 使用用户设备（ue）标识符以在第五代（5g）系统中注册
CN112867001A (zh) * 2019-11-26 2021-05-28 维沃移动通信有限公司 鉴权方法、终端设备和网络设备
CN113316151A (zh) * 2021-06-04 2021-08-27 展讯通信（上海）有限公司 通信方法、装置及设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110769420A (zh) * 2018-07-25 2020-02-07 中兴通讯股份有限公司 网络接入方法、装置、终端、基站和可读存储介质
CN112567833A (zh) * 2018-08-13 2021-03-26 苹果公司 使用用户设备（ue）标识符以在第五代（5g）系统中注册
WO2020088941A1 (en) * 2018-10-31 2020-05-07 Ntt Docomo, Inc. Network component, communication terminal, method for serving a communication terminal and method for using a communication network
CN112867001A (zh) * 2019-11-26 2021-05-28 维沃移动通信有限公司 鉴权方法、终端设备和网络设备
CN113316151A (zh) * 2021-06-04 2021-08-27 展讯通信（上海）有限公司 通信方法、装置及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "5G-GUTI not globally unique in an SNPN", 3GPP DRAFT; C1-194784_WAS_4623_SNPN_GLOBAL_UNIQUENESS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Wroclaw (Poland); 20190826 - 20190830, 29 August 2019 (2019-08-29), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051759555 *

Also Published As

Publication number Publication date
KR20240049681A (ko) 2024-04-16
CN115915386A (zh) 2023-04-04

Similar Documents

Publication Publication Date Title
JP7187580B2 (ja) セッション管理の方法、装置、およびシステム
EP3764696B1 (en) Method and apparatus for transmitting data
KR102224248B1 (ko) 통신 시스템에서 PDU(Protocol Data Unit) 세션을 설립하는 방법
WO2020259509A1 (zh) 一种应用迁移方法及装置
US11812496B2 (en) User group session management method and apparatus
WO2018082490A1 (zh) 用户终端位置区域更新方法、接入网实体、用户终端及核心网实体
WO2018232570A1 (zh) 一种注册及会话建立的方法、终端和amf实体
WO2019184651A1 (zh) 一种通信方法及装置
EP3713372A1 (en) Method and device for creating user group
EP3923671A1 (en) Session establishment method and device
EP3987881B1 (en) Method and apparatus for admission control of sessions based on priority
WO2020253701A1 (zh) 管理背景数据传输策略的方法、装置和系统
EP3651432A1 (en) Selection of ip version
KR20210024160A (ko) 통신 방법 및 장치
WO2017167153A1 (zh) 移动通讯系统及寻呼方法
WO2019242525A1 (zh) 数据传输方法、相关装置及系统
WO2021227965A1 (zh) 通信方法及装置
WO2019184721A1 (zh) 一种重定向的方法及装置
KR20220158018A (ko) 접속 수립 방법, 통신 장치, 및 시스템
WO2022199451A1 (zh) 会话切换的方法和装置
CN113938911A (zh) 一种通信方法、设备及系统
WO2019137169A1 (zh) 数据传输方法、装置、设备及计算机可读存储介质
WO2022016558A1 (zh) 一种业务连续性事件的通知方法及装置
WO2020200057A1 (zh) 一种通信方法及装置
WO2021184271A1 (zh) 一种消息转发方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22874197

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20247011250

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2022874197

Country of ref document: EP

Effective date: 20240430