A registration method and system

Abstract

This application provides a registration method and system. The method is applied to an AMF entity and includes: in response to a first registration request sent by a UE, sending a first authentication generation request to an AMF entity; wherein the first registration request includes information indicating IMS registration and a private user identifier; after receiving second authentication data sent by the AMF entity, sending an authentication request to the UE; after receiving the authentication response from the UE, if it is determined that the authentication response is successful, sending a second registration request carrying the private user identifier to the IMS. By integrating IMS registration into 5GC registration, the IMS registration process is simplified, network requests and signaling interactions are reduced, and network resources are saved.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a registration method and system. Background Technology

[0002] In the 5G core network (5GCore, 5GC), user registration with the 5GC and registration with the IP Multimedia Subsystem (IMS) are separate. Specifically, after successful 5GC registration, the user needs to establish a session with the default bearer set to 5G QoS Identifier (5QI) = 5. This session is established for IMS signaling transmission. After successful session establishment, the User Equipment (UE) will send a Session Initiation Protocol (SIP) registration request through the 5QI = 5 session, which is then transmitted to the relevant IMS network elements via the User Plane Function (UPF) entity to complete the SIP registration process.

[0003] However, the two registration processes mentioned above involve complex signaling interactions, consume a significant amount of network resources, and are time-consuming. Summary of the Invention

[0004] This application provides a registration method and system for performing 5GC and IMS fusion registration.

[0005] In a first aspect, embodiments of this application provide a first registration method applied to an Authentication Management Function (AMF) entity, the method comprising:

[0006] In response to the first registration request sent by the UE, a first authentication generation request is sent to the Authentication Server Function (AUSF) entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier;

[0007] After receiving the second authentication data sent by the AUSF entity, an authentication request is sent to the UE;

[0008] Upon receiving the authentication response from the UE, if it is determined that the authentication response was successful, a second registration request carrying the private user identifier is sent to the IMS.

[0009] In some optional implementations, following the first registration request sent by the UE, the method further includes:

[0010] Determine whether the first registration request contains information representing security protection for the user terminal;

[0011] If the first registration request contains information representing the security protection of the user terminal, then an authentication request is sent to the UE, including:

[0012] Send an authentication request carrying information representing the security protection server to the UE.

[0013] In some optional implementations, after sending a second registration request carrying the private user identifier to the IMS, the method further includes:

[0014] Receive the IMS registration result sent by the IMS;

[0015] Send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and the public identifier.

[0016] Some optional implementations also include:

[0017] In response to the first deregistration request sent by the UE, if it is determined that the authentication of the first deregistration request is successful, the session is released through the UPF entity; wherein, the first deregistration request includes information instructing IMS to deregister and the private user identifier;

[0018] Send a second deregistration request carrying the private user identifier to the IMS.

[0019] Some optional implementations also include:

[0020] Receive the IMS deregistration result sent by the IMS;

[0021] Send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0022] Secondly, this application provides a second registration method applied to a UE, the method comprising:

[0023] Send a first registration request to the AMF entity; wherein the first registration request includes information indicating IMS registration and a private user identifier; the first registration request is used by the AMF entity to send a first authentication generation request to the AUSF entity;

[0024] Receive the authentication request sent by the AMF entity;

[0025] Send an authentication response to the AMF entity; wherein, the authentication response is used by the AMF entity to send a second registration request carrying the private user identifier to the IMS after determining that the authentication response is successful.

[0026] In some optional implementations, if the first registration request contains information representing the security protection client, then the authentication request contains information representing the security protection server.

[0027] In some optional implementations, after sending the authentication response to the AMF entity, the method further includes:

[0028] Receive a registration acceptance message sent by the AMF entity; wherein the registration acceptance message includes an IMS registration result and a public identifier; the IMS registration result is sent by the IMS to the AMF entity.

[0029] Some optional implementations also include:

[0030] A first deregistration request carrying information instructing the IMS to deregister and the private user identifier is sent to the AMF entity; wherein, if the AMF entity determines that the authentication of the first deregistration request is successful, the session is released through the UPF entity; and a second deregistration request carrying the private user identifier is sent to the IMS; the second deregistration request is used by the IMS to deregister the UE based on the private user identifier.

[0031] Some optional implementations also include:

[0032] Receive a deregistration acceptance message sent by the AMF entity; wherein the deregistration acceptance message contains a deregistration result; the deregistration result is sent by the IMS to the AMF entity.

[0033] Thirdly, this application provides a third registration method applied to IMS, which includes:

[0034] Receive a second registration request sent by an AMF entity; wherein the second registration request contains a private user identifier;

[0035] Register the UE based on the private user identifier;

[0036] The second registration request is generated by the AMF entity in the following manner:

[0037] In response to the first registration request sent by the UE, a first authentication generation request is sent to the AUSF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier;

[0038] After receiving the second authentication data sent by the AUSF entity, an authentication request is sent to the UE;

[0039] Upon receiving the authentication response from the UE, if it is determined that the authentication response was successful, the second registration request is sent to the IMS.

[0040] In some optional implementations, UE registration is performed based on the private user identifier, including:

[0041] The second registration request is forwarded to the Interrogating-Call Session Control Function (ICSCF) entity through the Proxy-Call Session Control Function (PCSCF) entity;

[0042] The second registration request is forwarded to the Service-Call Session Control Function (SCSCF) entity through the ICSCF entity;

[0043] The SSCCF entity queries the Home Subscriber Server (HSS) and the Unified Data Management (UDM) entity to determine whether the private user identifier exists and to confirm the IMS registration result.

[0044] In some optional implementations, after determining the IMS registration result, the following steps are also included:

[0045] The IMS registration result is sent to the ICSCF entity through the SSCCF entity;

[0046] The IMS registration result is sent to the PCSCF entity through the ICSCF entity;

[0047] The PCSCF entity sends the IMS registration result to the AMF entity; wherein the IMS registration result is used by the AMF entity to send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and a public identifier.

[0048] Some optional implementations also include:

[0049] The PCSCF entity receives the second deregistration request sent by the AMF entity and forwards the second deregistration request to the ICSCF entity; wherein the second deregistration request includes the private user identifier; wherein the second deregistration request is triggered by the AMF entity in response to the first deregistration request sent by the UE; the first deregistration request includes information instructing IMS deregistration and the private user identifier;

[0050] The ICSCF entity forwards the second deregistration request to the SSCCF entity;

[0051] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and determines the IMS registration result.

[0052] In some optional implementations, after determining the IMS deregistration result, the following steps are also included:

[0053] The IMS deregistration result is sent to the ICSCF entity through the SSCCF entity;

[0054] The IMS deregistration result is sent to the PCSCF entity through the ICSCF entity;

[0055] The PCSCF entity sends the IMS deregistration result to the AMF entity; wherein the IMS deregistration result is used by the AMF entity to send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0056] Fourthly, embodiments of this application provide a converged registration system, which includes a UE, an AMF entity, an AUSF entity, a UDM entity, and an IMS; wherein:

[0057] The UE is used to send a first registration request to the AMF entity, carrying information indicating IMS registration and a private user identifier;

[0058] The AMF entity is used to send a first authentication generation request to the AUSF entity in response to the first registration request.

[0059] The AUSF entity is used to send the second authentication data to the AMF entity;

[0060] An AMF entity is used to send an authentication request to the UE after receiving the second authentication data.

[0061] The UE is used to send an authentication response to the AMF entity;

[0062] An AMF entity is used to send a second registration request carrying the private user identifier to the IMS after determining that the authentication response is successfully authenticated.

[0063] IMS is used to register the UE based on the private user identifier.

[0064] Fifthly, embodiments of this application provide a first fusion registration apparatus applied to an AMF entity, the apparatus comprising:

[0065] The first sending module is configured to send a first authentication generation request to the AUSF entity in response to a first registration request sent by the UE; wherein the first registration request includes information indicating IMS registration and a private user identifier;

[0066] The first receiving module is used to receive the second authentication data sent by the AUSF entity;

[0067] The first sending module is also used to send an authentication request to the UE;

[0068] The first sending module is further configured to, after the first receiving module receives the authentication response from the UE, if it determines that the authentication response is successful, send a second registration request carrying the private user identifier to the IMS.

[0069] In some optional implementations, after responding to the first registration request sent by the UE, the first sending module is further configured to:

[0070] Determine whether the first registration request contains information representing security protection for the user terminal;

[0071] The first sending module is specifically used for:

[0072] Send an authentication request carrying information representing the security protection server to the UE.

[0073] In some optional implementations, after the first sending module sends a second registration request carrying the private user identifier to the IMS, the first receiving module is also used to receive the IMS registration result sent by the IMS;

[0074] The first sending module is further configured to send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and a public identifier.

[0075] In some alternative implementations, a first deregistration module is also included, for:

[0076] In response to the first deregistration request sent by the UE, if it is determined that the authentication of the first deregistration request is successful, the session is released through the UPF entity; wherein, the first deregistration request includes information instructing IMS to deregister and the private user identifier;

[0077] Send a second deregistration request carrying the private user identifier to the IMS.

[0078] In some alternative implementations, the first deregistration module is also used for:

[0079] Receive the IMS deregistration result sent by the IMS;

[0080] Send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0081] Sixthly, embodiments of this application provide a second fusion registration apparatus applied to a UE, the apparatus comprising:

[0082] The second sending module is used to send a first registration request to the AMF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier; the first registration request is used by the AMF entity to send a first authentication generation request to the AUSF entity;

[0083] The second receiving module is used to receive the authentication request sent by the AMF entity;

[0084] The second sending module is further configured to send an authentication response to the AMF entity; wherein, the authentication response is used by the AMF entity to send a second registration request carrying the private user identifier to the IMS after determining that the authentication response is successful.

[0085] In some optional implementations, if the first registration request contains information representing the security protection client, then the authentication request contains information representing the security protection server.

[0086] In some optional implementations, after the second sending module sends the authentication response to the AMF entity, the second receiving module is further configured to:

[0087] Receive a registration acceptance message sent by the AMF entity; wherein the registration acceptance message includes an IMS registration result and a public identifier; the IMS registration result is sent by the IMS to the AMF entity.

[0088] In some alternative implementations, a second deregistration module is also included, for:

[0089] A first deregistration request carrying information instructing the IMS to deregister and the private user identifier is sent to the AMF entity; wherein, if the AMF entity determines that the authentication of the first deregistration request is successful, the session is released through the UPF entity; and a second deregistration request carrying the private user identifier is sent to the IMS; the second deregistration request is used by the IMS to deregister the UE based on the private user identifier.

[0090] In some alternative implementations, the second deregistration module is also used for:

[0091] Receive a deregistration acceptance message sent by the AMF entity; wherein the deregistration acceptance message contains a deregistration result; the deregistration result is sent by the IMS to the AMF entity.

[0092] In a seventh aspect, embodiments of this application provide a third type of fusion registration apparatus applied to IMS, the apparatus comprising:

[0093] The third receiving module is used to receive a second registration request sent by an AMF entity; wherein the second registration request contains a private user identifier;

[0094] The IMS registration module is used to register the UE based on the private user identifier;

[0095] The second registration request is generated by the AMF entity in the following manner:

[0096] In response to the first registration request sent by the UE, a first authentication generation request is sent to the AUSF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier;

[0097] After receiving the second authentication data sent by the AUSF entity, an authentication request is sent to the UE;

[0098] Upon receiving the authentication response from the UE, if it is determined that the authentication response was successful, the second registration request is sent to the IMS.

[0099] In some optional implementations, the IMS registration module is specifically used for:

[0100] The PCSCF entity forwards the second registration request to the ICSCF entity;

[0101] The second registration request is forwarded to the SSCCF entity through the ICSCF entity;

[0102] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and then determines the IMS registration result.

[0103] In some optional implementations, the IMS registration module is also used for:

[0104] The IMS registration result is sent to the ICSCF entity through the SSCCF entity;

[0105] The IMS registration result is sent to the PCSCF entity through the ICSCF entity;

[0106] The PCSCF entity sends the IMS registration result to the AMF entity; wherein the IMS registration result is used by the AMF entity to send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and a public identifier.

[0107] Some alternative implementations also include an IMS deregistration module for:

[0108] The PCSCF entity receives the second deregistration request sent by the AMF entity and forwards the second deregistration request to the ICSCF entity; wherein the second deregistration request includes the private user identifier; wherein the second deregistration request is triggered by the AMF entity in response to the first deregistration request sent by the UE; the first deregistration request includes information instructing IMS deregistration and the private user identifier;

[0109] The ICSCF entity forwards the second deregistration request to the SSCCF entity;

[0110] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and determines the IMS registration result.

[0111] In some optional implementations, after determining the IMS deregistration result, the IMS deregistration module is further used for:

[0112] The IMS deregistration result is sent to the ICSCF entity through the SSCCF entity;

[0113] The IMS deregistration result is sent to the PCSCF entity through the ICSCF entity;

[0114] The PCSCF entity sends the IMS deregistration result to the AMF entity; wherein the IMS deregistration result is used by the AMF entity to send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0115] Eighthly, embodiments of this application provide an AMF entity, including at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform any of the registration methods described in the first aspect above.

[0116] Ninthly, embodiments of this application provide a UE, including at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform any of the registration methods described in the second aspect above.

[0117] In a tenth aspect, embodiments of this application provide an IMS including at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform any of the registration methods described in the third aspect above.

[0118] Eleventhly, embodiments of this application provide a computer-readable storage medium storing a computer program executable by a processor, which, when run on the processor, causes the processor to perform the registration method described in any of the first, second, or third aspects above.

[0119] In this embodiment, the first registration request sent by the UE to the AMF entity carries information indicating IMS registration and a private user identifier. The AMF entity determines the IMS and 5GC integrated registration process based on the information indicating IMS registration. After receiving and successfully authenticating the UE's authentication response, the AMF entity sends a second registration request carrying the aforementioned private user identifier to the IMS, and the IMS registers the UE with the IMS. By integrating IMS registration into 5GC registration, the IMS registration process is simplified, unnecessary network requests and signaling interactions are reduced, network overhead is lowered, and network resources are saved. The entire integration process requires only one authentication, reducing the overhead required for core network authentication. Integrated registration shortens the registration process time. Furthermore, the entire registration process does not require the UPF entity, avoiding the impact of UPF entity overload or other failures on IMS registration, thus enhancing system stability and reliability. Attached Figure Description

[0120] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0121] Figure 1The interactive flowchart of the 5GC registration method provided in the embodiments of this application;

[0122] Figure 2 An interactive flowchart of the IMS registration method provided in the embodiments of this application;

[0123] Figure 3 An interactive flowchart of the first registration method provided in the embodiments of this application;

[0124] Figure 4 A schematic diagram of a first registration request provided for an embodiment of this application;

[0125] Figure 5 A schematic diagram of an authentication request provided for an embodiment of this application;

[0126] Figure 6 A schematic diagram of a second registration request provided for an embodiment of this application;

[0127] Figure 7 An interactive flowchart illustrating the second registration method provided in this application embodiment;

[0128] Figure 8 This is a schematic diagram of the registration acceptance message provided in an embodiment of this application;

[0129] Figure 9 This is an interactive flowchart of the 5GC deregistration method provided in the embodiments of this application;

[0130] Figure 10 The interactive flowchart of the IMS deregistration method provided in the embodiments of this application is shown.

[0131] Figure 11 An interactive flowchart of the first fusion deregistration method provided in this application embodiment;

[0132] Figure 12 This is a schematic diagram of a first deregistration request provided in an embodiment of this application;

[0133] Figure 13 This is a schematic diagram illustrating the process of receiving messages without registering, as provided in an embodiment of this application.

[0134] Figure 14 A flowchart illustrating the first registration method provided in this application embodiment;

[0135] Figure 15 A flowchart illustrating the second registration method provided in this application embodiment;

[0136] Figure 16 A flowchart illustrating the third registration method provided in this application embodiment;

[0137] Figure 17This is a schematic diagram of the structure of the first type of fusion registration device provided in the embodiments of this application;

[0138] Figure 18 This is a schematic diagram of the structure of the second type of fusion registration device provided in the embodiments of this application;

[0139] Figure 19 This is a schematic diagram of the structure of the third type of fusion registration device provided in the embodiments of this application;

[0140] Figure 20 This is a schematic diagram of the structure of the AMF entity provided in the embodiments of this application. Detailed Implementation

[0141] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0142] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0143] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the term "connection" should be interpreted broadly. For example, it can refer to a direct connection, an indirect connection through an intermediate medium, or a connection within two devices. Those skilled in the art can understand the specific meaning of the above term in this application based on the specific circumstances.

[0144] In 5GC, user registration in 5GC and IMS registration are separate. Specifically, after successful 5GC registration, the user needs to establish a session with a default bearer of 5QI=5. This session is established for IMS signaling transmission. After the session is successfully established, the UE will send a Session Initiation Protocol (SIP) registration request through the 5QI=5 session, which will be transmitted to the relevant IMS network elements through the UPF entity to complete the SIP registration process.

[0145] For the 5GC registration process, please refer to [link / reference]. Figure 1 As shown:

[0146] 1. The UE sends a registration request to the AMF entity via Non-access stratum (NAS) signaling.

[0147] 2. After receiving the registration request, the AMF entity parses the NAS message to obtain the user hidden identifier (SUbscriptionConcealed Identifier, SUCI) and sends an authentication generation request (generate auth data request) to the AUSF entity.

[0148] 3. The AUSF entity sends an authentication generation request to the UDM entity.

[0149] 4. The UDM entity generates the first authentication data (authentication data) based on the account opening information corresponding to the authentication generation request, such as 5G HE AV, including RAND, AUTH, XRES* and KAUSF entities (quadruple authentication parameters); and sends the first authentication data to the AUSF entity.

[0150] 5. After receiving the first authentication data, the AUSF entity generates the second authentication data and sends it to the AMF entity. If the AUSF entity stores the aforementioned XRES* and calculates HXRES* using XRES* and the KAUSF entity, it replaces the KAUSF entity with KSEAF, generating 5GAV(RAND, AUTH, and HXRES*). The AUSF entity then sends information containing 5GAV to the AMF entity.

[0151] 6. The AMF entity sends an authentication request to the UE, including RAND and AUTH.

[0152] 7. Upon receiving RAND and AUTH, the UE calculates RES* and sends it to the AMF entity via an authentication response. The AMF entity forwards RES* to the AUSF entity. The AUSF entity compares RES* with XRES*, and if they are equal, notifies the AMF entity that authentication has been successful (the authentication process is not shown in the diagram).

[0153] 8. The AMF entity sends a security mode command to the UE to negotiate the security and encryption algorithms.

[0154] 9. The UE replies with a security mode complete message to the AMF entity.

[0155] 10. The AMF entity replies with a registration acceptance message.

[0156] For the IMS registration process, please refer to [link / reference]. Figure 2As shown:

[0157] 1. The UE sends a registration request A to the service port of the PCSCF entity (which needs to pass through the UPF entity, not shown in the figure). The registration request A carries the user's IMS Private User Identifier (IMPI) and security-client header, instructing the PCSCF entity to establish a standard (IP Security, IPsec) secure tunnel to protect secure communication of the IP protocol.

[0158] 2. The PCSCF entity forwards the SIP request to the ICSCF entity.

[0159] 3. The ICSCF entity sends a user authentication request to the HSS, requesting the UE's home SSCCF entity address.

[0160] 4. The HSS replies with a user authentication response, informing the ICSCF entity of the address of the SSCCF entity to which it belongs.

[0161] 5. The ICSCF entity sends a SIP request to the SSCCF entity.

[0162] 6. The SCSCF entity interacts with the HSS to generate an unauthorized instruction (401 unauthorized), which contains the IPsec encryption key and the UE's authentication information and sends it to the ICSCF entity.

[0163] 7. The ICSCF entity forwards a 401 unauthorized error to the PCSCF entity.

[0164] 8. Upon receiving a 401 unauthorized error, the PCSCF entity removes the key, adds a security-server header containing IPsec, prepares an IPsec secure tunnel, and sends the 401 unauthorized error to the UE.

[0165] 9. The UE resends the registration request B carrying authentication information through the protected port.

[0166] 10. The PCSCF entity sends registration request B to the ICSCF entity.

[0167] 11. The ICSCF entity sends registration request B to the SSCCF entity.

[0168] 12. The SSCCF entity sends a server-assignment request to the HSS, which includes authentication information.

[0169] 13. The HSS responds with a server-assignment response to the SSCCF entity, carrying an authentication success message.

[0170] 14. The SSCCF entity replies with a 200 OK message indicating that the request was successful to the ICSCF entity.

[0171] 15. The ICSCF entity replies with a 200 OK response to the PCSCF entity.

[0172] 16. The PCSCF entity replies with a 200 OK response and the IP Multimedia Public Identity (IMPU) to the UE, and the UE's SIP registration is successful.

[0173] It is evident that the above registration process has the following problems:

[0174] 1. Increased complexity of signaling process and waste of network resources: Users need to complete 5GC registration before they can register for IMS. The two registrations involve complex signaling interactions, and some processes are repeated, such as the need to transmit user identity information in both registration processes.

[0175] 2. Repeated signaling process: Users repeatedly perform 5GC authentication and IMS authentication, both of which use the Authentication and Key Agreement (AKA) algorithm, resulting in repeated processes and increasing the overhead of authentication calculation for AUSF entities, UDM entities, SSCCF entities and HSS network elements in the core network.

[0176] 3. Low efficiency: Since the two registration processes are executed sequentially, this may lead to a longer registration process, affecting the user experience, especially in situations where a communication connection needs to be established quickly, such as an emergency call.

[0177] 4. Limited by UPF entity: If the UPF entity's resources are completely occupied or the UPF entity malfunctions, the UPF entity cannot send the SIP registration request to the PCSCF entity in a timely manner, affecting IMS registration and deregistration.

[0178] In summary, both registration processes described above involve complex signaling interactions, consume significant network resources, and are time-consuming.

[0179] In view of this, embodiments of this application propose a registration method and system for performing 5GC and IMS fusion registration.

[0180] This application provides a fusion registration system, which includes a UE, an AMF entity, an AUSF entity, a UDM entity, and an IMS; wherein:

[0181] The UE is used to send a first registration request to the AMF entity, carrying information indicating IMS registration and a private user identifier;

[0182] The AMF entity is used to send a first authentication generation request to the AUSF entity in response to the first registration request.

[0183] The AUSF entity is used to send the second authentication data to the AMF entity;

[0184] An AMF entity is used to send an authentication request to the UE after receiving the second authentication data.

[0185] The UE is used to send an authentication response to the AMF entity;

[0186] An AMF entity is used to send a second registration request carrying the private user identifier to the IMS after determining that the authentication response is successfully authenticated.

[0187] IMS is used to register the UE based on the private user identifier.

[0188] In the above scheme, the first registration request sent by the UE to the AMF entity carries information indicating IMS registration and a private user identifier. The AMF entity determines the IMS and 5GC integrated registration process based on the information indicating IMS registration. After receiving the UE's authentication response and successfully authenticating it, the AMF entity sends a second registration request carrying the aforementioned private user identifier to the IMS, and the IMS registers the UE with IMS. By integrating IMS registration into 5GC registration, the IMS registration process is simplified, unnecessary network requests and signaling interactions are reduced, network overhead is lowered, and network resources are saved. The entire integration process only requires one authentication, reducing the overhead required for core network authentication. The integrated registration shortens the registration process time. In addition, the entire registration process does not require the UPF entity, avoiding the impact of UPF entity overload or other failures on IMS registration, thus enhancing the stability and reliability of the system.

[0189] The technical solution of this application and how it solves the above-mentioned technical problems will be described in detail below with reference to the accompanying drawings and specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0190] Figure 3 The interactive flowchart of the first registration method provided in the embodiments of this application is as follows: Figure 3 As shown, it includes the following steps:

[0191] Step S301: The UE sends a first registration request to the AMF entity, carrying information indicating IMS registration and a private user identifier.

[0192] For example, the UE sends a first registration request to the AMF entity via NAS signaling.

[0193] See Figure 4 As shown, the first registration request adds information indicating IMS registration (used to instruct the core network to merge 5GC and IMS registration) to the original NAS signaling, such as the IMS indication 1 field.

[0194] In addition, IMS registration requires IMPI, so the first registration request adds IMPI to the original NAS signaling.

[0195] During implementation, some UEs need to instruct IMS to establish an IPsec secure tunnel and a protected port for the UE when registering with IMS;

[0196] See Figure 4 As shown, in some optional implementations, the first registration request may also include information characterizing the security protection client, such as the security-client field.

[0197] Step S302: In response to the first registration request, the AMF entity sends a first authentication generation request to the AUSF entity.

[0198] During implementation, after receiving the first registration request containing information indicating IMS registration and a private user identifier, the AMF entity determines that 5GC and IMS fusion registration is required; first, the process of requesting authentication data in 5GC registration needs to be performed.

[0199] Step S303: The AUSF entity sends a second authentication generation request to the UDM entity.

[0200] By sending a first authentication generation request to the AUSF entity, the AUSF entity then sends a second authentication generation request to the UDM entity, requesting the UE's authentication data from the UDM entity.

[0201] Step S304: The UDM entity generates the first authentication data of the UE based on the second authentication generation request.

[0202] For example, the UDM entity generates a 5G HE AV (including the aforementioned RAND, AUTH, XRES*, and KAUSF entities) based on the UE's account opening information.

[0203] Step S305: The UDM entity sends the first authentication data to the AUSF entity.

[0204] Step S306: The AMF entity generates second authentication data based on the first authentication data and sends the second authentication data to the AMF entity.

[0205] For example, the AUSF entity generates 5GAV (containing the aforementioned RAND, AUTH, and HXRES*) based on 5G HE AV.

[0206] Step S307: After receiving the second authentication data, the AMF entity sends an authentication request to the UE.

[0207] For example, the authentication request includes the RAND and AUTH mentioned above.

[0208] As mentioned above, some UEs need to instruct IMS to establish an IPsec secure tunnel and a protected port for the UE when registering with IMS;

[0209] See Figure 5 As shown, in some optional implementations, the authentication request includes information characterizing the security protection server, such as the security-server field.

[0210] Step S308: The UE sends an authentication response to the AMF entity.

[0211] For example, the UE calculates RES* based on the above RAND and AUTH, and sends it to the AMF entity through an authentication response.

[0212] Step S309: After confirming that the authentication response is successfully authenticated, the AMF entity sends a second registration request carrying the private user identifier to the IMS.

[0213] For example, the AMF entity forwards the authentication information to the AUSF entity, which performs the authentication and notifies the AMF entity of the authentication result.

[0214] After confirming successful authentication of the authentication response, the AMF entity sends a second registration request carrying the private user identifier to the IMS to proceed with subsequent IMS registration.

[0215] See Figure 6 As shown, the second registration request includes IMPI.

[0216] In some optional implementations, before step S308, the AMF entity and the UE need to negotiate the security protection and encryption algorithm. The AMF entity sends a security mode command to the UE, and the UE replies with a security mode complete message to the AMF entity.

[0217] Step S310: IMS registers the UE based on the private user identifier.

[0218] In practice, after receiving the second registration request, IMS registers the UE through internal network element interaction.

[0219] In the above scheme, the first registration request sent by the UE to the AMF entity carries information indicating IMS registration and a private user identifier. The AMF entity determines the IMS and 5GC integrated registration process based on the information indicating IMS registration. After receiving the UE's authentication response and successfully authenticating it, the AMF entity sends a second registration request carrying the aforementioned private user identifier to the IMS, and the IMS registers the UE with IMS. By integrating IMS registration into 5GC registration, the IMS registration process is simplified, unnecessary network requests and signaling interactions are reduced, network overhead is lowered, and network resources are saved. The entire integration process only requires one authentication, reducing the overhead required for core network authentication. The integrated registration shortens the registration process time. In addition, the entire registration process does not require the UPF entity, avoiding the impact of UPF entity overload or other failures on IMS registration, thus enhancing the stability and reliability of the system.

[0220] Figure 7 The interactive flowchart of the second registration method provided in the embodiments of this application is as follows: Figure 7 As shown, it includes the following steps:

[0221] Step S701: The UE sends a first registration request to the AMF entity, carrying information indicating IMS registration and a private user identifier.

[0222] Step S702: In response to the first registration request, the AMF entity sends a first authentication generation request to the AUSF entity.

[0223] Step S703: The AUSF entity sends a second authentication generation request to the UDM entity.

[0224] Step S704: The UDM entity generates the first authentication data of the UE based on the second authentication generation request.

[0225] Step S705: The UDM entity sends the first authentication data to the AUSF entity.

[0226] Step S706: The AFS entity generates second authentication data based on the first authentication data and sends the second authentication data to the AMF entity.

[0227] Step S707: After receiving the second authentication data, the AMF entity sends an authentication request to the UE.

[0228] Step S708: The UE sends an authentication response to the AMF entity.

[0229] Step S709: After confirming that the authentication response is successfully authenticated, the AMF entity sends a second registration request carrying the private user identifier to the IMS.

[0230] Step S710: IMS registers the UE based on the private user identifier.

[0231] The specific implementation methods of steps S701 to S710 can be referred to the above embodiments, and will not be repeated here.

[0232] Step S711: IMS sends the IMS registration result to the AMF entity.

[0233] For example, IMS sends the IMS registration result (IMS result1) to the AMF entity, indicating whether the IMS registration was successful or failed through different bits.

[0234] Step S712: The AMF entity sends a registration acceptance message to the UE.

[0235] See Figure 8 As shown, the registration acceptance message includes the IMS registration result (IMS result1) and IMPU.

[0236] In practice, the AMF entity can send the interval of periodic registration of 5GC and IMS to the UE through the T3512 timer.

[0237] In some optional implementations, steps S310 and S710 can be implemented in, but are not limited to, the following ways:

[0238] The PCSCF entity forwards the second registration request to the ICSCF entity;

[0239] The second registration request is forwarded to the SSCCF entity through the ICSCF entity;

[0240] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and then determines the IMS registration result.

[0241] In this embodiment, the second registration request is forwarded to the SSCCF entity via the PCSCF entity and the ICSCF entity;

[0242] The UE registration is performed by querying the HSS and UDM entities through the SSCCF entity to see if the private user identifier carried in the second registration request is present.

[0243] In some optional implementations, step S711 above can be implemented in, but is not limited to, the following ways:

[0244] The IMS registration result is sent to the ICSCF entity through the SSCCF entity;

[0245] The IMS registration result is sent to the PCSCF entity through the ICSCF entity;

[0246] The IMS registration result is sent to the AMF entity through the PCSCF entity.

[0247] In this embodiment, the IMS registration result is forwarded to the PCSCF entity via the SSCF entity and the ICSCF entity; the PCSCF entity then sends the IMS registration result to the AMF entity.

[0248] In practice, the deregistration processes for 5GC and IMS are also separate.

[0249] For the 5GC registration process, please refer to [link / reference]. Figure 9 As shown:

[0250] 1. The UE initiates a registration request to the AMF entity.

[0251] The 2AMF entity and UDM entity + HSS interact to authenticate whether the UE has passed the authentication.

[0252] 3. The AMF entity sends a session release request to the SMF.

[0253] 4. The SMF sends a session release request to the UPF entity.

[0254] 5. The UPF entity replies with a session release success message to the SMF.

[0255] 6. The SMF replies with a session release success message to the AMF entity.

[0256] 7. If a dynamic policy and charging control rule (PCC rule) was used when establishing the session, the SMF initiates a session management policy connection termination (SM Policy Association Termination) procedure to the Policy Control Function (PCF) entity to delete the associated PCF entity.

[0257] 8. If this is the UE's last Protocol Data Unit (PDU) session, the SMF sends an internal deregistration (NUDM entity_UECM_Deregistration) service operation to the UDM entity to delete all associated Data Network Names (DNNs) and PDU Session IDs stored in the storage.

[0258] 9. An AMF entity triggers the AM Policy Association Termination process to delete the associated PCF entity.

[0259] 10. The AMF entity replies to the UE with a successful registration message.

[0260] For the IMS registration process, please refer to [link / reference]. Figure 10 As shown:

[0261] 1. The UE sends a registration request to the service port (protected) of the PCSCF entity, carrying the user's private user identifier.

[0262] 2. The PCSCF entity forwards the registration request to the ICSCF entity.

[0263] 3. The ICSCF entity sends a user authentication request to the UDM entity +HSS, requesting the UE's home SSCCF entity address.

[0264] 4. The HSS replies to the UDM entity + HSS with a user authentication response, informing the ICSCF entity of the address of the SSCCF entity to which it belongs.

[0265] 5. The ICSCF entity sends a registration request to the SSCCF entity.

[0266] 6. The SSCCF entity sends a server-assignment request to the HSS, which includes authentication information.

[0267] 7. HSS replies to the SSCCF entity with a server-assignment response, carrying an authentication success message.

[0268] 8. The SSCCF entity sends a registration success message to the PCSCF entity.

[0269] 9. The PCSCF entity replied to the UE that registration was successful.

[0270] It is evident that the registration process also suffers from problems such as complex signaling interaction procedures, high network resource consumption, and long processing time.

[0271] Based on this, this embodiment provides an interactive flowchart of the integrated registration removal method, see below. Figure 11 As shown, it includes the following steps:

[0272] Step S1101: The UE sends a first deregistration request to the AMF entity, carrying information instructing the IMS to deregister and the private user identifier.

[0273] See Figure 12 As shown, the first deregistration request adds information instructing the IMS to deregister (used to instruct the core network to merge 5GC and IMS registration) to the original NAS signaling, such as using the IMS indication2 field. In implementation, the information instructing the IMS to deregister and the information instructing the IMS to register can be the same or different.

[0274] In addition, IMS registration also requires the aforementioned IMPI. Therefore, the first registration request adds IMPI to the original NAS signaling.

[0275] Step S1102: In response to the first deregistration request sent by the UE, the AMF entity authenticates the first deregistration request through the UDM entity and the HSS.

[0276] For example, when the AMF entity receives the first deregistration request, it performs authentication through the UDM entity + HSS and receives the authentication result returned by the UDM entity.

[0277] Step S1103: If the AMF entity determines that the authentication of the first deregistration request is successful, it releases the session through the UPF entity.

[0278] For example, the AMF entity sends a session release request to the UPF entity via the SMF, and the UPF entity deletes the session within the core network. After successful release, the UPF entity replies to the AMF entity with a message indicating successful session release via the SMF.

[0279] In addition, if dynamic PCC rules are used when establishing a session, it is also necessary to perform the process of deleting PCF entities. For details, please refer to the above embodiments, which will not be repeated here.

[0280] Step S1104: The AMF entity sends a second deregistration request carrying the private user identifier to the IMS.

[0281] In practice, after completing the 5GC deregistration, the AMF entity sends a second deregistration request carrying a private user identifier to the IMS to proceed with the subsequent IMS deregistration.

[0282] Step S1105: IMS deregisters the UE based on the private user identifier.

[0283] In practice, after receiving a request to deregister from the second registration point, IMS performs UE deregistration through internal network element interaction.

[0284] In some optional implementations, after step S1105 above, the following steps are also included:

[0285] IMS sends the IMS registration result to the AMF entity;

[0286] The AMF entity sends a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0287] For example, IMS sends the IMS registration result (IMS result2) to the AMF entity, indicating whether the IMS registration was successful or failed through different bits.

[0288] See Figure 13 As shown, the registration acceptance message includes the IMS registration result mentioned above.

[0289] In some optional implementations, step S1105 above can be implemented in, but is not limited to, the following ways:

[0290] The PCSCF entity receives the second deregistration request sent by the AMF entity and forwards the second deregistration request to the ICSCF entity.

[0291] The ICSCF entity forwards the second deregistration request to the SSCCF entity;

[0292] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and determines the IMS registration result.

[0293] In this embodiment, the second deregistration request is forwarded to the SSCCF entity via the PCSCF entity and the ICSCF entity;

[0294] The UE deregisters by querying the HSS and UDM entities through the SSCCF entity to see if the private user identifier carried in the second deregistration request exists.

[0295] In some optional implementations, the step of IMS sending the IMS registration result to the AMF entity can be achieved in the following ways, but not limited to:

[0296] The IMS deregistration result is sent to the ICSCF entity through the SSCCF entity;

[0297] The IMS deregistration result is sent to the PCSCF entity through the ICSCF entity;

[0298] The PCSCF entity sends the IMS deregistration result to the AMF entity; wherein the IMS deregistration result is used by the AMF entity to send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0299] In this embodiment, the IMS deregistration result is forwarded to the PCSCF entity via the SSCF entity and the ICSCF entity; the PCSCF entity then sends the IMS deregistration result to the AMF entity.

[0300] The registration method performed by the AMF entity in the embodiments of this application is as follows: Figure 14 As shown, it includes the following steps:

[0301] Step S1401: In response to the first registration request sent by the UE, send a first authentication generation request to the AUSF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier;

[0302] Step S1402: After receiving the second authentication data sent by the AUSF entity, send an authentication request to the UE;

[0303] Step S1403: After receiving the authentication response from the UE, if it is determined that the authentication response is successful, a second registration request carrying the private user identifier is sent to the IMS.

[0304] In some optional implementations, following the first registration request sent by the UE, the method further includes:

[0305] Determine whether the first registration request contains information representing security protection for the user terminal;

[0306] If the first registration request contains information representing the security protection of the user terminal, then an authentication request is sent to the UE, including:

[0307] Send an authentication request carrying information representing the security protection server to the UE.

[0308] In some optional implementations, after sending a second registration request carrying the private user identifier to the IMS, the method further includes:

[0309] Receive the IMS registration result sent by the IMS;

[0310] Send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and the public identifier.

[0311] Some optional implementations also include:

[0312] In response to the first deregistration request sent by the UE, if it is determined that the authentication of the first deregistration request is successful, the session is released through the UPF entity; wherein, the first deregistration request includes information instructing IMS to deregister and the private user identifier;

[0313] Send a second deregistration request carrying the private user identifier to the IMS.

[0314] Some optional implementations also include:

[0315] Receive the IMS deregistration result sent by the IMS;

[0316] Send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0317] The registration method performed by the UE in this application embodiment is as follows: Figure 15 As shown, it includes the following steps:

[0318] Step S1501: Send a first registration request to the AMF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier; the first registration request is used by the AMF entity to send a first authentication generation request to the AUSF entity;

[0319] Step S1502: Receive the authentication request sent by the AMF entity;

[0320] Step S1503: Send an authentication response to the AMF entity; wherein, the authentication response is used by the AMF entity to send a second registration request carrying the private user identifier to the IMS after determining that the authentication response is successful.

[0321] In some optional implementations, if the first registration request contains information representing the security protection client, then the authentication request contains information representing the security protection server.

[0322] In some optional implementations, after sending the authentication response to the AMF entity, the method further includes:

[0323] Receive a registration acceptance message sent by the AMF entity; wherein the registration acceptance message includes an IMS registration result and a public identifier; the IMS registration result is sent by the IMS to the AMF entity.

[0324] Some optional implementations also include:

[0325] A first deregistration request carrying information instructing the IMS to deregister and the private user identifier is sent to the AMF entity; wherein, if the AMF entity determines that the authentication of the first deregistration request is successful, the session is released through the UPF entity; and a second deregistration request carrying the private user identifier is sent to the IMS; the second deregistration request is used by the IMS to deregister the UE based on the private user identifier.

[0326] Some optional implementations also include:

[0327] Receive a deregistration acceptance message sent by the AMF entity; wherein the deregistration acceptance message contains a deregistration result; the deregistration result is sent by the IMS to the AMF entity.

[0328] The registration method performed by IMS in the embodiments of this application is as follows: Figure 16 As shown, it includes the following steps:

[0329] Step S1601: Receive a second registration request sent by the AMF entity; wherein the second registration request contains a private user identifier;

[0330] Step S1602: Register the UE based on the private user identifier;

[0331] The second registration request is generated by the AMF entity in the following manner:

[0332] In response to the first registration request sent by the UE, a first authentication generation request is sent to the AUSF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier;

[0333] After receiving the second authentication data sent by the AUSF entity, an authentication request is sent to the UE;

[0334] Upon receiving the authentication response from the UE, if it is determined that the authentication response was successful, the second registration request is sent to the IMS.

[0335] In some optional implementations, UE registration is performed based on the private user identifier, including:

[0336] The PCSCF entity forwards the second registration request to the ICSCF entity;

[0337] The second registration request is forwarded to the SSCCF entity through the ICSCF entity;

[0338] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and then determines the IMS registration result.

[0339] In some optional implementations, after determining the IMS registration result, the following steps are also included:

[0340] The IMS registration result is sent to the ICSCF entity through the SSCCF entity;

[0341] The IMS registration result is sent to the PCSCF entity through the ICSCF entity;

[0342] The PCSCF entity sends the IMS registration result to the AMF entity; wherein the IMS registration result is used by the AMF entity to send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and a public identifier.

[0343] Some optional implementations also include:

[0344] The PCSCF entity receives the second deregistration request sent by the AMF entity and forwards the second deregistration request to the ICSCF entity; wherein the second deregistration request includes the private user identifier; wherein the second deregistration request is triggered by the AMF entity in response to the first deregistration request sent by the UE; the first deregistration request includes information instructing IMS deregistration and the private user identifier;

[0345] The ICSCF entity forwards the second deregistration request to the SSCCF entity;

[0346] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and determines the IMS registration result.

[0347] In some optional implementations, after determining the IMS deregistration result, the following steps are also included:

[0348] The IMS deregistration result is sent to the ICSCF entity through the SSCCF entity;

[0349] The IMS deregistration result is sent to the PCSCF entity through the ICSCF entity;

[0350] The PCSCF entity sends the IMS deregistration result to the AMF entity; wherein the IMS deregistration result is used by the AMF entity to send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0351] Figures 14-16 For details on the specific implementation of the embodiments, please refer to the implementation of the above-described interaction method; repeated details will not be repeated here.

[0352] like Figure 17 As shown, based on and Figure 14 The present application provides a first fusion registration device 1700, which is based on the same inventive concept as the registration method shown, and is applied to AMF entities. The device includes:

[0353] The first sending module 1701 is configured to send a first authentication generation request to the AUSF entity in response to a first registration request sent by the UE; wherein the first registration request includes information indicating IMS registration and a private user identifier;

[0354] The first receiving module 1702 is used to receive the second authentication data sent by the AUSF entity;

[0355] The first sending module 1701 is also used to send an authentication request to the UE;

[0356] The first sending module 1701 is further configured to, after the first receiving module 1702 receives the authentication response from the UE, if it is determined that the authentication response is successfully authenticated, send a second registration request carrying the private user identifier to the IMS.

[0357] In some optional implementations, after responding to the first registration request sent by the UE, the first sending module 1701 is further configured to:

[0358] Determine whether the first registration request contains information representing security protection for the user terminal;

[0359] The first transmitting module 1701 is specifically used for:

[0360] Send an authentication request carrying information representing the security protection server to the UE.

[0361] In some optional implementations, after the first sending module 1701 sends a second registration request carrying the private user identifier to the IMS, the first receiving module 1702 is also used to receive the IMS registration result sent by the IMS.

[0362] The first sending module 1701 is further configured to send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and a public identifier.

[0363] In some alternative implementations, a first deregistration module 1703 is also included, for:

[0364] In response to the first deregistration request sent by the UE, if it is determined that the authentication of the first deregistration request is successful, the session is released through the UPF entity; wherein, the first deregistration request includes information instructing IMS to deregister and the private user identifier;

[0365] Send a second deregistration request carrying the private user identifier to the IMS.

[0366] In some alternative implementations, the first deregistration module 1703 is further configured to:

[0367] Receive the IMS deregistration result sent by the IMS;

[0368] Send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0369] like Figure 18 As shown, based on and Figure 15 The present application provides a second fusion registration device 1800, which is based on the same inventive concept as the registration method shown, and is applied to a UE. The device includes:

[0370] The second sending module 1801 is used to send a first registration request to the AMF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier; the first registration request is used by the AMF entity to send a first authentication generation request to the AUSF entity;

[0371] The second receiving module 1802 is used to receive the authentication request sent by the AMF entity;

[0372] The second sending module 1801 is further configured to send an authentication response to the AMF entity; wherein, the authentication response is used by the AMF entity to send a second registration request carrying the private user identifier to the IMS after determining that the authentication response is successful.

[0373] In some optional implementations, if the first registration request contains information representing the security protection client, then the authentication request contains information representing the security protection server.

[0374] In some optional implementations, after the second sending module 1801 sends an authentication response to the AMF entity, the second receiving module 1802 is further configured to:

[0375] Receive a registration acceptance message sent by the AMF entity; wherein the registration acceptance message includes an IMS registration result and a public identifier; the IMS registration result is sent by the IMS to the AMF entity.

[0376] In some alternative implementations, a second deregistration module 1803 is also included, for:

[0377] A first deregistration request carrying information instructing the IMS to deregister and the private user identifier is sent to the AMF entity; wherein, if the AMF entity determines that the authentication of the first deregistration request is successful, the session is released through the UPF entity; and a second deregistration request carrying the private user identifier is sent to the IMS; the second deregistration request is used by the IMS to deregister the UE based on the private user identifier.

[0378] In some alternative implementations, the second deregistration module 1803 is further configured to:

[0379] Receive a deregistration acceptance message sent by the AMF entity; wherein the deregistration acceptance message contains a deregistration result; the deregistration result is sent by the IMS to the AMF entity.

[0380] like Figure 19 As shown, based on and Figure 16 The present application provides a third type of fusion registration device 1900, which is based on the same inventive concept as the registration method shown, and is applied to IMS. The device includes:

[0381] The third receiving module 1901 is used to receive a second registration request sent by an AMF entity; wherein the second registration request contains a private user identifier;

[0382] IMS registration module 1902 is used to register the UE based on the private user identifier;

[0383] The second registration request is generated by the AMF entity in the following manner:

[0384] In response to the first registration request sent by the UE, a first authentication generation request is sent to the AUSF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier;

[0385] After receiving the second authentication data sent by the AUSF entity, an authentication request is sent to the UE;

[0386] Upon receiving the authentication response from the UE, if it is determined that the authentication response was successful, the second registration request is sent to the IMS.

[0387] In some optional implementations, the IMS registration module 1902 is specifically used for:

[0388] The PCSCF entity forwards the second registration request to the ICSCF entity;

[0389] The second registration request is forwarded to the SSCCF entity through the ICSCF entity;

[0390] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and then determines the IMS registration result.

[0391] In some optional implementations, the IMS registration module 1902 is also used for:

[0392] The IMS registration result is sent to the ICSCF entity through the SSCCF entity;

[0393] The IMS registration result is sent to the PCSCF entity through the ICSCF entity;

[0394] The PCSCF entity sends the IMS registration result to the AMF entity; wherein the IMS registration result is used by the AMF entity to send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and a public identifier.

[0395] In some alternative implementations, an IMS deregistration module 1903 is also included, for:

[0396] The PCSCF entity receives the second deregistration request sent by the AMF entity and forwards the second deregistration request to the ICSCF entity; wherein the second deregistration request includes the private user identifier; wherein the second deregistration request is triggered by the AMF entity in response to the first deregistration request sent by the UE; the first deregistration request includes information instructing IMS deregistration and the private user identifier;

[0397] The ICSCF entity forwards the second deregistration request to the SSCCF entity;

[0398] The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and determines the IMS registration result.

[0399] In some optional implementations, after determining the IMS deregistration result, the IMS deregistration module 1903 is further configured to:

[0400] The IMS deregistration result is sent to the ICSCF entity through the SSCCF entity;

[0401] The IMS deregistration result is sent to the PCSCF entity through the ICSCF entity;

[0402] The PCSCF entity sends the IMS deregistration result to the AMF entity; wherein the IMS deregistration result is used by the AMF entity to send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

[0403] Figures 17-19 For details on the specific implementation of the embodiments, please refer to the implementation of the above-described interaction method; repeated details will not be repeated here.

[0404] Based on the same technical concept, this application also provides an AMF entity 2000, such as... Figure 20 As shown, it includes at least one bus 2003 and a memory 2002 connected to at least one processor 2001. In this embodiment, the specific connection medium between the bus 2003 and the memory 2002 is not limited. Figure 20 Taking the connection between bus 2003 and memory 2002 via bus 2003 as an example. Buses can be divided into path buses, data buses, control buses, etc. For ease of illustration, Figure 20 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0405] The bus 2003 serves as the control center of the first satellite, connecting various parts of the satellite via various interfaces and lines. It performs data processing by running or executing instructions stored in the memory 2002 and accessing data stored in the memory 2002. Optionally, the bus 2003 may include one or more processing units. The bus 2003 may integrate an application processor 2001 and a modem processor 2001. The application processor 2001 primarily handles the operating system, user interface, and applications, while the modem processor 2001 primarily handles issuing instructions. It is understood that the modem processor 2001 may not be integrated into the bus 2003. In some embodiments, the bus 2003 and the memory 2002 may be implemented on the same chip; in other embodiments, they may be implemented on separate chips.

[0406] The bus 2003 can be a general-purpose processor, such as a central processing unit (CPU), digital signal processor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the registration method embodiments can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0407] Memory 2002, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. Memory 2002 may include at least one type of storage medium, such as flash memory, hard disk, multimedia card, card-type memory, random access memory (RAM), static random access memory (SRAM), programmable read-only memory (PROM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic storage, magnetic disk, optical disk, etc. Memory 2002 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited thereto. The memory 2002 in the embodiments of this application may also be a circuit or any other device capable of implementing storage functions for storing program instructions and / or data.

[0408] In this embodiment, the memory 2002 stores a computer program, which, when executed by the bus 2003, causes the bus 2003 to perform the steps of the registration method corresponding to the AMF entity.

[0409] Based on the same technical concept, this application also provides a UE, including at least one processor and at least one memory, wherein the memory stores a computer program, and when the program is executed by the processor, the processor performs the steps of the registration method corresponding to the UE described above.

[0410] Based on the same technical concept, this application also provides an IMS, including at least one processor and at least one memory, wherein the memory stores a computer program, and when the program is executed by the processor, the processor performs the steps of the registration method corresponding to the above-mentioned IMS.

[0411] Based on the same technical concept, embodiments of this application also provide a computer-readable storage medium storing a computer program executable by a processor, which, when run on the processor, causes the processor to perform the steps of the above-described registration method.

[0412] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0413] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0414] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0415] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0416] Although preferred embodiments of this application have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of this application.

[0417] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A registration method, characterized in that, Applied to the Authentication Management Function (AMF) entity, the method includes: In response to a first registration request sent by a user equipment (UE), a first authentication generation request is sent to the authentication service function (AUSF) entity; wherein, the first registration request includes information indicating registration of the network interconnection protocol multimedia subsystem (IMS) and a private user identifier; After receiving the second authentication data sent by the AUSF entity, an authentication request is sent to the UE; Upon receiving the authentication response from the UE, if it is determined that the authentication response was successful, a second registration request carrying the private user identifier is sent to the IMS.

2. The method of claim 1, wherein, Following the first registration request sent by the UE, the following is also included: Determine whether the first registration request contains information representing security protection for the user terminal; If the first registration request contains information representing the security protection of the user terminal, then an authentication request is sent to the UE, including: Send an authentication request carrying information representing the security protection server to the UE.

3. The method of claim 1, wherein, After sending a second registration request carrying the private user identifier to IMS, the process further includes: Receive the IMS registration result sent by the IMS; Send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and the public identifier.

4. The method of claim 1, wherein, Also includes: In response to the first deregistration request sent by the UE, if it is determined that the authentication of the first deregistration request is successful, the session is released through the User Plane Function (UPF) entity; wherein, the first deregistration request includes information instructing IMS to deregister and the private user identifier; Send a second deregistration request carrying the private user identifier to the IMS.

5. The method of claim 4, wherein, Also includes: Receive the IMS deregistration result sent by the IMS; Send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

6. A registration method characterized by comprising: Applied to a UE, the method includes: Send a first registration request to the AMF entity; wherein the first registration request includes information indicating IMS registration and a private user identifier; the first registration request is used by the AMF entity to send a first authentication generation request to the AUSF entity; Receive the authentication request sent by the AMF entity; Send an authentication response to the AMF entity; wherein, the authentication response is used by the AMF entity to send a second registration request carrying the private user identifier to the IMS after determining that the authentication response is successful.

7. The method of claim 6, wherein, If the first registration request contains information representing the security protection of the user terminal, then the authentication request contains information representing the security protection of the server terminal.

8. The method of claim 6, wherein, After sending the authentication response to the AMF entity, the process also includes: Receive a registration acceptance message sent by the AMF entity; wherein the registration acceptance message includes an IMS registration result and a public identifier; the IMS registration result is sent by the IMS to the AMF entity.

9. The method of claim 6, wherein, Also includes: A first deregistration request is sent to the AMF entity; wherein the first deregistration request includes information instructing the IMS to deregister and the private user identifier; the first deregistration request is used by the AMF entity to release the session through the UPF entity if the authentication of the first deregistration request is successful; and a second deregistration request carrying the private user identifier is sent to the IMS; the second deregistration request is used by the IMS to deregister the UE based on the private user identifier.

10. The method of claim 9, wherein, Also includes: Receive a deregistration acceptance message sent by the AMF entity; wherein the deregistration acceptance message contains a deregistration result; the deregistration result is sent by the IMS to the AMF entity.

11. A registration method characterized by comprising: Applied to IMS, the method includes: Receive a second registration request sent by an AMF entity; wherein the second registration request contains a private user identifier; Register the UE based on the private user identifier; The second registration request is generated by the AMF entity in the following manner: In response to the first registration request sent by the UE, a first authentication generation request is sent to the AUSF entity; wherein, the first registration request includes information indicating IMS registration and a private user identifier; After receiving the second authentication data sent by the AUSF entity, an authentication request is sent to the UE; Upon receiving the authentication response from the UE, if it is determined that the authentication response was successful, the second registration request is sent to the IMS.

12. The method of claim 11, wherein, Registering the UE based on the private user identifier includes: The second registration request is forwarded to the query call session control function ICSCF entity by the proxy call session control function PCSCF entity. The second registration request is forwarded to the Service Call Session Control Function (SCSCF) entity by the ICSCF entity; The SSCCF entity queries the Home Subscriber Server (HSS) and the Unified Data Management (UDM) entity to determine whether the private user identifier exists and to confirm the IMS registration result.

13. The method as described in claim 12, characterized in that, After confirming the IMS registration result, the following is also included: The IMS registration result is sent to the ICSCF entity through the SSCCF entity; The IMS registration result is sent to the PCSCF entity through the ICSCF entity; The PCSCF entity sends the IMS registration result to the AMF entity; wherein the IMS registration result is used by the AMF entity to send a registration acceptance message to the UE; wherein the registration acceptance message includes the IMS registration result and a public identifier.

14. The method as described in claim 11, characterized in that, Also includes: The PCSCF entity receives the second deregistration request sent by the AMF entity and forwards the second deregistration request to the ICSCF entity; wherein the second deregistration request includes the private user identifier; wherein the second deregistration request is triggered by the AMF entity in response to the first deregistration request sent by the UE; the first deregistration request includes information instructing IMS deregistration and the private user identifier; The ICSCF entity forwards the second deregistration request to the SSCCF entity; The SSCCF entity queries the HSS and UDM entities to see if the private user identifier exists, and determines the IMS registration result.

15. The method of claim 14, wherein, After confirming the IMS registration result, the following is also included: The IMS deregistration result is sent to the ICSCF entity through the SSCCF entity; The IMS deregistration result is sent to the PCSCF entity through the ICSCF entity; The PCSCF entity sends the IMS deregistration result to the AMF entity; wherein the IMS deregistration result is used by the AMF entity to send a deregistration acceptance message to the UE; wherein the deregistration acceptance message contains the IMS registration result.

16. An AMF entity, characterized by It includes at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform any of the registration methods described in 1 to 5.

17. An AMF entity, characterized by It includes at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform any of the registration methods described in 6 to 10.

18. An IMS, characterized by It includes at least one processor and at least one memory, wherein the memory stores a computer program that, when executed by the processor, causes the processor to perform any of the registration methods described in 11 to 15.

Images