Communication method and related equipment
By assisting the secondary authentication between the data network and user equipment in the core network, and storing the authentication results and restrictions, the problem of insufficient secondary authentication management in the existing technology is solved, and the security and effectiveness of business operations are improved. .
Patent Information
- Application Number
- CN201980099050.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-08-15
- Publication Date
- 2024-11-29
- Estimated Expiration
- 2039-08-15
AI Technical Summary
The lack of effective secondary authentication result management in the prior art has led to defects in the security and effectiveness of business operations based on secondary authentication.
After the first-level authentication between the core network and the user equipment is successfully carried out, the network functional entity assists the secondary authentication between the data network and the user equipment, and stores the authentication results and restrictions of the secondary authentication to reasonably limit the secondary authentication The use of the company improves its management efficiency and security.
By introducing the restrictions on secondary authentication, the security and effectiveness of service operation of secondary authentication are improved, unauthorized access is avoided, network resource utilization is optimized, and service requirements for limited-time access and restricted conditions are supported.
Smart Images

Figure CN114223232B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communications, and specifically to a communication method, user equipment, core network equipment, data network equipment, and computer-readable media. Background Art
[0002] The 3rd Generation Partnership Project (3GPP) has proposed the concept of network slicing in, for example, 5G (fifth generation) networks. Network slicing can be simply understood as cutting the operator's physical network into multiple virtual end-to-end networks. Each virtual network, including the devices, access, transmission and core networks within the network, is logically independent, and any failure in a virtual network will not affect other virtual networks. At present, various scenarios have put forward different requirements for the 3GPP ecosystem, such as billing, policy, security, mobility and other requirements. 3GPP emphasizes that network slices do not affect each other. For example, a sudden large number of meter reading services should not affect normal mobile broadband services. In order to meet the diverse needs and isolation between slices, relatively independent management and operation and maintenance between services are required, and tailored business functions and analysis capabilities are provided. Instances of different types of services can be deployed on different network slices, and different instances of the same service type can also be deployed on different network slices.
[0003] A slice in a 5G network is a virtual private network, which is composed of a set of network functions and subnetworks. Many network slices can be deployed in an operator network, and each slice can have different performance to meet the needs of different applications and different vertical industries. Operators can "tailor-make" a slice according to the needs of different vertical industry customers. Operators can also allow some industry customers to enjoy greater autonomy, such as being able to participate in some management and control functions of the slice. Slice-level authentication is a network control function that can be participated in by industry customers, that is, to authenticate and authorize the end user (User) to access the slice. Generally speaking, the authentication of user terminals (or user equipment or terminals, etc.) to access the core network is called primary authentication; in addition, slice-level authentication (abbreviated as "slice authentication") is also called "secondary authentication", which is the authentication between the data network and the end user.
[0004] Traditional technologies currently lack effective management of secondary authentication results, resulting in defects in the security and effectiveness of business operations based on secondary authentication. Summary of the invention
[0005] Embodiments of the present application provide a communication method and related devices.
[0006] A first aspect of an embodiment of the present application provides a communication method, which may include: after a first-level authentication between a core network and a user device is successful, if a second-level authentication is required between a data network and the user device, a network function entity in the core network (such as an access and mobility management function (AMF, Access and Mobility Management Function), etc.) assists the data network and the user device in performing the second-level authentication; the network function entity obtains an authentication result of the second-level authentication and a restriction condition of the second-level authentication from the data network; the network function entity stores the obtained authentication result of the second-level authentication and the restriction condition of the second-level authentication in the core network (for example, it can be stored in the AMF or UDM in the core network, etc.).
[0007] Among them, the secondary authentication mentioned in the embodiments of the present application is essentially the authentication between the data network and the user using the user device, and the user device can represent the user using this user device to a certain extent, so it can also be called "secondary authentication between the data network and the user device", of course, in some cases it can also be called "secondary authentication between the data network and the user using the user device" or "secondary authentication between the data network and the user". Among them, in the description of the embodiments of the present application, these terms have the same meaning and can be used interchangeably. Similar "secondary authentication of user devices" and "secondary authentication of users" can be used interchangeably, and so on.
[0008] In addition, the user terminal, user equipment, terminal and terminal equipment mentioned in the embodiments of the present application have the same meaning and can be used interchangeably.
[0009] It can be seen that in the above example scheme, by introducing the restriction conditions of the secondary authentication, it becomes possible for the authentication results of the secondary authentication to be used reasonably and restrictively, laying the foundation for the effective management of the authentication results of the secondary authentication, which in turn is conducive to improving the security and effectiveness of business operations based on the secondary authentication.
[0010] In some possible implementations, the restriction conditions of the secondary authentication may include, for example, the validity period of the authentication result of the secondary authentication and / or the authorization level of the secondary authentication.
[0011] In some possible implementations, the authentication result of the secondary authentication is stored in binding with the authentication result of the primary authentication (the authentication result of the secondary authentication is stored in binding with the authentication result of the primary authentication, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the authentication result of the primary authentication) or stored independently; or the authentication result of the secondary authentication is stored in binding with the user device context (the authentication result of the secondary authentication is stored in binding with the user device context, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the user device context) or stored independently, or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the user device context, or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the primary authentication.
[0012] In some possible implementations, the network function entity in the core network assisting the data network and the user equipment in performing secondary authentication includes: when it is determined that the initiation condition for the secondary authentication of the user equipment is met, the network function entity in the core network assisting the data network and the user equipment in performing secondary authentication. When it is determined that the initiation condition for the secondary authentication of the user equipment is not met, the core network rejects the secondary authentication request of the user equipment or directly determines that the secondary authentication between the data network and the user equipment is unsuccessful.
[0013] In some possible implementations, the method may also include: the network function entity obtains the accompanying information of the secondary authentication from the data network, and the network function entity stores the obtained accompanying information of the secondary authentication to the core network, and the accompanying information can be used to determine the initiation conditions of the next secondary authentication of the user device or other user devices.
[0014] For example, the initiation conditions of the secondary authentication may be determined by the accompanying information of one or several secondary authentications that have been performed for the current UE or other UEs that have been stored before. For example, when the operator network performs secondary authentication for other UEs (secondary authentication for S-NSSAI), the initiation conditions of the secondary authentication are used to assist the AMF in determining whether to continue the secondary authentication process or directly determine that the secondary authentication has failed. Similarly, if the secondary authentication fails, the reason for the authentication failure can be provided to the core network, and the reason for the authentication failure can be used as the accompanying information of this secondary authentication, which is used by the AMF to assist in determining whether this user or other users meet the secondary authentication (for S-NSSAI) conditions next time. For example, AAA-S successfully completes the authentication authorization for the user, but the DN network capacity or the number of users that can be supported reaches the upper limit, AAA-S can notify the operator network that the DN is temporarily running in "full load mode" and will not accept more secondary authentications temporarily. At this time, AAA-S can also send a timer, which is used to limit the specific duration of "temporary". After receiving the timer, AMF stores it in the core network (such as AMF, UDM). The next time other UE applies for secondary authentication, the secondary authentication application can be directly rejected to avoid unnecessary signaling interaction between the operator's core network and DN.
[0015] In some possible implementations, the method further includes: the network function entity sending the acquired authentication result of the secondary authentication and the restriction condition of the secondary authentication to the user equipment. The user equipment may receive and store the authentication result of the secondary authentication and the restriction condition of the secondary authentication.
[0016] In some possible implementations, the method further includes: when the network function entity receives an update request from the data network for requesting to update the secondary authentication restriction condition, updating the secondary authentication restriction condition stored in the core network according to the update request. Further, when the network function entity receives an update request from the data network for requesting to update the secondary authentication restriction condition, the network function entity may also send the update request to a user device, and after receiving the update request, the user device updates the secondary authentication restriction condition stored in the user device according to the update request.
[0017] A second aspect of an embodiment of the present application provides a network function entity in a core network, which may include: an assisting unit, for assisting the data network in performing secondary authentication with the user device after a primary authentication between the core network and the user device is successful, if secondary authentication is required between the data network and the user device.
[0018] An acquisition unit is used for the network function entity to acquire the authentication result of the secondary authentication and the restriction condition of the secondary authentication from the data network.
[0019] A storage unit is used to store the acquired authentication result of the secondary authentication and the restriction condition of the secondary authentication in the core network (for example, it can be stored in the AMF or UDM in the core network, etc.).
[0020] It can be seen that in the above example scheme, by introducing the restriction conditions of the secondary authentication, it becomes possible for the authentication results of the secondary authentication to be used reasonably and restrictively, laying the foundation for the effective management of the authentication results of the secondary authentication, which in turn is conducive to improving the security and effectiveness of business operations based on the secondary authentication.
[0021] In some possible implementations, the restriction condition of the secondary authentication may include, for example, the validity period of the authentication result of the secondary authentication and / or the authorization level of the secondary authentication.
[0022] In some possible implementations, the storage unit stores the authentication result of the secondary authentication in a bound manner with the authentication result of the primary authentication (the authentication result of the secondary authentication is stored in a bound manner with the authentication result of the primary authentication, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the authentication result of the primary authentication) or stores it independently; or the storage unit stores the authentication result of the secondary authentication in a bound manner with the user device context (the authentication result of the secondary authentication is stored in a bound manner with the user device context, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the user device context) or stores it independently. Or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the user device context. Or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the primary authentication.
[0023] In some possible implementations, the assisting unit assisting the data network with performing secondary authentication with the user equipment includes: assisting the data network with performing secondary authentication with the user equipment when it is determined that the initiation condition for the secondary authentication of the user equipment is met. In addition, when it is determined that the initiation condition for the secondary authentication of the user equipment is not met, the secondary authentication request of the user equipment may be rejected or the secondary authentication between the data network and the user equipment may be directly determined to be unsuccessful.
[0024] In some possible implementations, the acquisition unit is further configured to: acquire accompanying information of the secondary authentication from the data network.
[0025] The storage unit is further used to store the acquired accompanying information of the secondary authentication in the core network, and the accompanying information can be used to determine the initiation condition of the next secondary authentication of the user equipment or other user equipment.
[0026] In some possible implementations, the network function entity in the core network further includes a notification unit, configured to send the acquired authentication result of the secondary authentication and the restriction condition of the secondary authentication to the user equipment. The user equipment may receive and store the authentication result of the secondary authentication and the restriction condition of the secondary authentication.
[0027] In some possible implementations, the network functional entity in the core network also includes an update unit, which is used to update the secondary authentication restriction conditions stored in the core network according to the update request when an update request for requesting to update the secondary authentication restriction conditions is received from the data network.
[0028] Further, the notification unit may also be used to, when the network function entity receives an update request from the data network for requesting to update the secondary authentication restriction condition, send the update request to the user equipment. After receiving the update request, the user equipment may update the secondary authentication restriction condition stored in the user equipment according to the update request.
[0029] A third aspect of an embodiment of the present application provides another communication method, including: an authentication server in a data network performs secondary authentication with a user device with the assistance of a core network; and sends the authentication result of the secondary authentication and the restriction conditions of the secondary authentication to the core network, and the authentication result of the secondary authentication and the restriction conditions of the secondary authentication can be stored by the core network.
[0030] In some possible implementations, the restriction condition of the secondary authentication may include, for example, the validity period of the authentication result of the secondary authentication and / or the authorization level of the secondary authentication.
[0031] In some possible implementations, the method may further include: the authentication server sends additional information of the secondary authentication to the core network, the additional information can be stored by the core network, and the additional information can be used to determine the initiation conditions for the next secondary authentication of the user device or other user devices.
[0032] In some possible implementations, the method further includes: the authentication server sending an update request to the core network for requesting an update of the secondary authentication restriction condition, wherein the update request is used to trigger the core network to update the stored secondary authentication restriction condition.
[0033] A fourth aspect of an embodiment of the present application provides another authentication server in a data network, including:
[0034] A secondary authentication unit, used to perform secondary authentication with the user equipment with the assistance of the core network (such as AMF);
[0035] An interaction unit is used to send the authentication result of the secondary authentication and the restriction conditions of the secondary authentication to the core network (such as AMF), wherein the authentication result of the secondary authentication and the restriction conditions of the secondary authentication can be stored by the core network.
[0036] In some possible implementations, the restriction condition of the secondary authentication may include, for example, the validity period of the authentication result of the secondary authentication and / or the authorization level of the secondary authentication.
[0037] In some possible implementations, the interaction unit is further configured to: send the secondary authentication supplementary information to the core network. The supplementary information can be stored by the core network, and the supplementary information can be used to determine the initiation condition of the next secondary authentication of the user equipment or other user equipment.
[0038] In some possible implementations, the interaction unit is further used to: send an update request to the core network for requesting to update the secondary authentication restriction condition, wherein the update request is used to trigger the core network to update the stored secondary authentication restriction condition.
[0039] A fifth aspect of an embodiment of the present application provides a communication method, comprising: after a primary authentication between a core network and a user device is successful, if a secondary authentication is required between the user device and a data network, the user device performs secondary authentication with the data network with the assistance of the core network. The user device receives the authentication result of the secondary authentication and the restriction condition of the secondary authentication sent by the core network. The user device stores the received authentication result of the secondary authentication and the restriction condition of the secondary authentication.
[0040] In some possible implementations, when the authentication result of the secondary authentication is authentication failure and the restriction condition of the secondary authentication is the validity period of the authentication result, the method further includes: the user device re-initiating the secondary authentication with the data network after determining that the validity period of the authentication result has expired; and the user device suspending the initiation of the secondary authentication with the data network before determining that the validity period of the authentication result has expired.
[0041] A sixth aspect of an embodiment of the present application provides a user equipment, including:
[0042] The authentication unit is used to perform secondary authentication between the core network and the user equipment with the assistance of the core network if secondary authentication is required between the user equipment and the data network after the primary authentication between the core network and the user equipment is successful.
[0043] An interaction unit is used to receive the authentication result of the secondary authentication and the restriction condition of the secondary authentication sent by the core network.
[0044] The storage unit is used to store the received authentication result of the secondary authentication and the restriction condition of the secondary authentication.
[0045] In some possible implementations, the authentication unit is further used to, when the authentication result of the secondary authentication is authentication failure and the restriction condition of the secondary authentication is the validity period of the authentication result, after determining that the validity period of the authentication result has expired, re-initiate the secondary authentication with the data network; and before determining that the validity period of the authentication result has expired, suspend the initiation of the secondary authentication with the data network.
[0046] In some possible implementations, the interaction unit is further used to: receive the secondary authentication incidental information sent by the core network; if it is determined that the initiation condition of the secondary authentication of the user equipment is met, initiate the secondary authentication with the data network again; if it is determined that the initiation condition of the secondary authentication of the user equipment is not met, suspend the initiation of the secondary authentication with the data network. The incidental information is used to determine the initiation condition of the next secondary authentication of the user equipment.
[0047] A seventh aspect of an embodiment of the present application provides a communication device, characterized in that the communication device includes a coupled processor and a memory; wherein the processor is used to call a computer program stored in the memory to complete part or all of the steps of any one of the methods provided in the embodiments of the present application.
[0048] Among them, the communication device can be, for example, a user equipment, an authentication server in a data network, or a network function entity in a core network (such as AMF, etc.).
[0049] An eighth aspect of an embodiment of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it can complete part or all of the steps of any one of the methods provided in the embodiments of the present application.
[0050] In the ninth aspect, an embodiment of the present application also provides a computer program product of instructions, which, when executed on a computer device, enables the computer device to execute part or all of the steps of any method executed by any device provided in the embodiment of the present application. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] Figure 1 It is a schematic diagram of a network architecture provided in an embodiment of the present application.
[0052] Figure 2-A It is a schematic diagram of a secondary authentication provided in an embodiment of the present application.
[0053] Figure 2-B It is a schematic diagram of an authentication process provided in an embodiment of the present application.
[0054] Figure 3 It is a flowchart of a secondary authentication provided in an embodiment of the present application.
[0055] Figure 4 It is a flow chart of a communication method provided in an embodiment of the present application.
[0056] Figure 5 It is a flow chart of a communication method provided in an embodiment of the present application.
[0057] Figure 6 It is a flow chart of another communication method provided in an embodiment of the present application.
[0058] Figure 7 It is a flow chart of another communication method provided in an embodiment of the present application.
[0059] Figure 8 It is a structural diagram of a user equipment provided in an embodiment of the present application.
[0060] Fig. 9 It is a structural diagram of an authentication server provided in an embodiment of the present application.
[0061] Fig.10 It is a structural diagram of a network function entity of a core network provided in an embodiment of the present application.
[0062] Fig.11 It is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0063] The terms "including" and "having" and any variations thereof in the specification and claims of the present application and the above-mentioned drawings are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. In addition, the terms "first", "second", "third" and "fourth" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order.
[0064] The following is an introduction to the relevant network architecture.
[0065] See also Figure 1 , Figure 1 This is a schematic diagram of a 5G network architecture exemplified by an embodiment of the present application. The 5G network splits some network functional entities of the 4G network (such as the Mobility Management Entity (MME) and so on) and defines an architecture based on a service-oriented architecture. Figure 1 In the network architecture shown, the functions similar to those of the MME in the 4G network are divided into access and mobility management function (AMF, Access and Mobility Management Function) and session management function (SMF, Session Management Function) and so on.
[0066] Some other related network functions / entities are introduced below.
[0067] A user terminal (also called user equipment (UE) or terminal device or terminal, etc.) accesses a data network (DN) by accessing an operator network, and then uses services on the DN provided by the operator or a third party.
[0068] Access and Mobility Management Function (AMF) is a control plane network function in 3GPP network, which is mainly responsible for access control and mobility management of UE access to operator network. Among them, Security Anchor Function (SEAF) can be deployed in AMF, or SEAF may also be deployed in another device different from AMF. Figure 1 In the figure, SEAF is deployed in AMF as an example.
[0069] The Session Management Function (SMF) is a control plane network function in the 3GPP network. The SMF is mainly responsible for managing the UE's Packet Data Unit (PDU) session. A PDU session is a channel for transmitting PDUs. UEs can send PDUs to and from DNs through PDU sessions. SMF is responsible for the establishment, maintenance, and deletion of PDU sessions.
[0070] Data Network (DN) is also called Packet Data Network (PDN), which is usually located outside the 3GPP network. The 3GPP network can access multiple DNs, and a variety of services provided by operators or third parties can be deployed on the DN. For example, a DN is a private network of a smart factory. The sensors installed in the workshop of the smart factory play the role of UE, and the control server of the sensor is deployed in the DN. The UE communicates with the control server. After obtaining the instructions of the control server, the UE can pass the collected data to the control server according to the instructions. For another example, the DN is an internal office network of a company, and the terminals used by the company's employees can play the role of UE, and this UE can access the company's internal information and other resources.
[0071] Among them, the Unified Data Management (UDM) network function is a control plane network function in the 3GPP network. UDM is mainly responsible for storing the subscription data, credentials and persistent identity (SUPI) of the subscribers in the 3GPP network. These data can be used for authentication and authorization of UE access to the operator's 3GPP network.
[0072] The Authentication Server Function (AUSF) is also a control plane network function in the 3GPP network. AUSF is mainly used for primary authentication (i.e., authentication between the 3GPP network and the terminal of the contracted user).
[0073] Among them, the Network Exposure Function (NEF) is also a control plane network function in the 3GPP network. NEF is mainly responsible for opening the external interface of the 3GPP network to third parties in a secure manner. When network functions such as SMF need to communicate with third-party network functions, NEF can be used as a communication relay.
[0074] Among them, the network storage function (NRF, Network Repository Function) is also a control plane network function in the 3GPP network. It is mainly responsible for storing the configuration service profile of the accessible network function (NF) and providing network function discovery services for other network functions.
[0075] The User Plane Function (UPF) is the gateway for communication between the 3GPP network and the DN.
[0076] The Policy Control Function (PCF) is a control plane function in the 3GPP network, which is used to provide the SMF with the PDU session policy. The policy may include billing, Quality of Service (QoS), authorization-related policies, etc.
[0077] The access network (AN) is a sub-network of the 3GPP network. To access the 3GPP network, the UE must first pass through the AN. In the wireless access scenario, the AN is also called the radio access network (RAN), so the two terms RAN and AN are often used interchangeably without distinction.
[0078] 3GPP network refers to a network that complies with 3GPP standards. Figure 1 The parts other than UE and DN can be regarded as 3GPP networks. 3GPP networks are not limited to 5G networks defined by 3GPP, but can also include 2G, 3G, and 4G networks. Usually 3GPP networks are operated by operators. Figure 1 In the illustrated architecture, N1, N2, N3, N4, N6, etc. respectively represent reference points between related network functions, and Nausf, Namf, etc. respectively represent service-oriented interfaces of related network functions.
[0079] The mobility management network function in the embodiment of the present application may be Figure 1 The AMF shown may also be other network functions with the above-mentioned AMF functions in future communication systems. Alternatively, the mobility management network function in the present application may also be the MME in long term evolution (LTE).
[0080] For the convenience of explanation, the embodiments of the present application are mainly described by taking the mobility management network function as AMF as an example. And user terminals, user equipment, terminal devices or terminals can be collectively referred to as UE. That is, unless otherwise specified, the AMF described later in the embodiments of the present application can be replaced with the mobility management network function, and the UE can be replaced with the user terminal, user equipment, terminal device or terminal.
[0081] Figure 1 The network architecture shown in the figure (such as the 5G network architecture) adopts a service-based architecture and a universal interface. The traditional network element functions are split into several self-contained, self-managed, and reusable network function service modules based on the network function virtualization (NFV) technology. By flexibly defining a set of service modules, customized network function reconstruction can be achieved, and the business process is composed of a unified service call interface. Figure 1 The network architecture diagram shown in the figure can be understood as a service-based 5G network architecture diagram in a non-roaming scenario. In this architecture, different network functions are combined in an orderly manner according to the needs of specific scenarios, which can realize the customization of network capabilities and services, thereby deploying dedicated networks for different services and realizing 5G network slicing. Network slicing technology can enable operators to respond to customer needs more flexibly and quickly, and support flexible allocation of network resources.
[0082] Network slicing, in simple terms, is to cut the operator's physical network into multiple virtual end-to-end networks. Each virtual network, including the equipment, access, transmission and core network within the network, is logically independent. A failure in any virtual network will not affect other virtual networks.
[0083] At present, various scenarios have put forward different requirements for the 3rd Generation Partnership Project (3GPP) ecosystem, such as billing, policy, security, mobility and other requirements. 3GPP emphasizes that network slices should not affect each other. For example, a sudden large number of meter reading services should not affect normal mobile broadband services. Among them, in order to meet the diverse needs and isolation between slices, relatively independent management and operation and maintenance of services are required, and tailored business functions and analysis capabilities are provided. Instances of different types of services can be deployed on different network slices, and different instances of the same service type can also be deployed on different network slices.
[0084] A slice in a 5G network is a virtual private network consisting of a set of network functions and subnetworks. Figure 1 The subnetwork RAN 140, AMF network function 137, SMF network function 138, UPF network function 139, etc. can form a slice. Figure 1Only one of each network function is schematically drawn, but in actual network deployment, there can be multiple (for example, several, dozens or hundreds, or even more) of each network function or subnetwork. Many network slices can be deployed in the operator network, and each slice can have different performance to meet the needs of different applications and different vertical industries. Operators can "tailor-make" a slice according to the needs of customers in different vertical industries. In addition, operators can also allow some industry customers to enjoy greater autonomy and participate in some management and control functions of the slices. Among them, slice-level authentication is a network control function in which industry customers participate, that is, to authenticate and authorize user equipment to access the slice. The embodiment of this application may be referred to as "slice authentication".
[0085] by Figure 1 For example, when the core network CN deploys network slices, if UE 110 needs to access a certain network slice, UE 110 can provide the requested network slice to the core network. For example, the network slice requested by UE 110 can be represented by a requested network slice set, or the requested network slice can also be represented by requested network slice selection assistance information (requested NSSAI, requested network slice selection assistance information). The network slice set includes one or more network slices. Requested NSSAI is represented by one or more single network slice selection assistance information (S-NSSAI, single network slice selection assistance information), each S-NSSAI is used to identify a network slice type, it can also be understood that S-NSSAI is used to identify the network slice, or it can be understood that S-NSSAI is the identification information of the network slice.
[0086] For ease of understanding, in the following description, the embodiments of the present application do not make a strict distinction between "network slice" and "S-NSSAI", and the two can be used interchangeably. The "network slice" in the embodiments of the present application can also be called "slice" or "network slice instance", which have the same meaning and are explained here uniformly, and will not be repeated in the following text.
[0087] After UE 110 sends a registration request to the network, the core network network function (such as AMF network function 137 or NSSF network function) makes a comprehensive judgment based on the subscription data of UE 110, the requested NSSAI of UE 110, the roaming agreement, and the local configuration, and then selects a set of network slices allowed to be accessed for UE 110. Among them, the set of network slices allowed to be accessed can be represented by an allowed NSSAI, and the S-NSSAI contained in the allowed NSSAI is the S-NSSAI allowed to be accessed by the current operator network.
[0088] Before being allowed to access the network or network slice, UE 110 will perform two-way authentication with the network and / or network slice and obtain authorization from the network and / or network slice. Currently, in the 5G standard, the network authentication and authorization of UE 110 are performed directly by the operator network. This type of authentication and authorization method is called primary authentication.
[0089] With the development of vertical industries and the Internet of Things, it can be foreseen that data networks DN 120 outside the operator network (such as DNs serving vertical industries) also have authentication and authorization requirements for UE 110 accessing the DN 120. For example, a commercial company provides a gaming platform and provides gaming services to gamers through the operator network. On the one hand, since the UE 110 used by the player accesses the gaming platform through the operator network, the operator network needs to authenticate and authorize the UE 110, i.e., primary authentication. Gamers are customers of commercial companies, and the commercial company also needs to authenticate and authorize the gamers. If this authentication is based on network slicing, or authentication is based on slices, then this authentication can be called slice authentication or slice-specific authentication or secondary authentication.
[0090] It should be noted that in the embodiments of the present application, the secondary authentication may also be referred to as secondary authentication for slices, or slice authentication, or identity authentication for users (users using UE 110), which means, for example: secondary authentication performed between UE 110 (or users using the UE 110) and a third-party network, and the authentication result will determine whether the operator network authorizes the UE to access the corresponding slice. It should also be understood that the method applied to the secondary authentication in the embodiments of the present application is also applicable to scenarios such as session-based secondary authentication or slice-based secondary authentication, which will not be described in detail here.
[0091] Among them, the secondary authentication mentioned in the embodiment of the present application is essentially the authentication between the data network and the user using the user device. Since the user device can represent the user to a certain extent, it can also be called "secondary authentication between the data network and the user device". Of course, in some cases it can also be called "secondary authentication between the data network and the user using the user device". In the embodiment of the present application, these two terms have the same meaning and can be used interchangeably. Similar "secondary authentication of user devices" and "secondary authentication of users" can be used interchangeably, and so on.
[0092] Figure 2-A Examples of primary authentication and slice authentication methods are shown.
[0093] Specifically, Figure 2-A The authentication process between the UE and the network includes a primary authentication process and a secondary authentication process, wherein the primary authentication process is the authentication process between the UE and the operator network, and the secondary authentication process is the authentication process between the UE or a user using the UE and a third-party network.
[0094] In the embodiment of the present application, the description of "a secondary authentication process between a UE and a third-party network" can be understood as a secondary authentication process between a user using the UE and the third-party network. Figure 2-A As shown, exemplarily, the first-level authentication process is the authentication process between UE 210 and core network CN 230, and the second-level authentication process is the authentication process between the user using UE 210 and data network DN 220. Both the first-level authentication process and the second-level authentication process can be understood as part of the registration process of UE 110. For the convenience of understanding and description, in the embodiment of the present application, the authentication device in DN 220 is an authentication, authorization and accounting (AAA) server as an example for explanation. The AAA server can be represented as AAA-S (AAA server), and the AAA proxy function (AAA-F, AAA-proxy function) 238 can be located in the core network CN 230 to forward the message sent by the core network to AAA-S. AAA-F is an optional implementation, and the embodiment of the present application does not limit it. It should be further explained that AAA-S is usually deployed on the DN side outside the 3GPP network, but DN220 or AAA-S221 can also be deployed inside the 3GPP network, and the embodiment of the present application does not limit it.
[0095] refer to Figure 2-B , the main steps of the UE 210 registration process may be as follows:
[0096] 201. The UE sends a registration request to the network for requesting access to the network, wherein the registration request carries the identity information of the UE. Exemplarily, the UE 210 may send an access request carrying the identity information of the UE 210 to the AMF network function entity 237 in the core network CN 230, wherein the identity information may be, for example, encrypted identity information SUCI or temporary identity information such as a globally unique temporary identifier (GUTI).
[0097] The network determines whether to initiate a first-level authentication between the network and the UE according to the identity information of the UE carried in the registration request sent by the UE. Exemplarily, the AMF network function entity 237 may forward the encrypted identity information SUCI received from the UE 210 to the UDM network function entity 234, and the UDM network function entity 234 decrypts the SUCI to restore the real identity information SUPI of the UE 210, and then returns the SUPI to the AMF network function entity 237. The AMF network function entity 237 initiates a first-level authentication process between the network and the UE 210 according to the real identity SUPI of the UE 210.
[0098] After the first level authentication between the UE and the network is successful, the network can authorize the UE to allow it to access the operator network. Specifically, after the first level authentication is successful, the AMF network function entity 237 authorizes the UE 210 to access the operator network.
[0099] After step 201, the primary authentication process between the UE and the network can be considered completed. On the other hand, if the UE sends temporary identity information GUTI in step 201, then in step 201, the AMF checks the validity of the GUTI on the network side. If it is valid, it indicates that the previous primary authentication is still valid and there is no need to perform primary authentication.
[0100] 202. The network determines whether the UE needs further secondary authentication. Exemplarily, the AMF network function entity 237 determines whether the slice to which the UE 210 applies for access needs further slice authentication (i.e., secondary authentication) based on the information of the AMF network function entity 237 or the UDM network function entity 234.
[0101] 203. If the UE needs to perform secondary authentication, the network can, for example, trigger a secondary authentication process between the UE and the data network DN. Exemplarily, when the UE 210 needs to perform secondary authentication, the AMF network function entity 237 triggers a secondary authentication process between the UE 210 and the DN 220.
[0102] The embodiment of the present application takes the slice authentication as an example of secondary authentication. This slice authentication process can be based on the extensible authentication protocol (FAP) standard formulated by the standard organization-internet engineering task force (IETF) as the basic authentication mechanism. The EAP mechanism has great flexibility and can support dozens of specific EAP authentication methods.
[0103] It should be understood that the UE mentioned in the embodiments of the present application needs to perform secondary authentication, which can be understood as a user using the UE needs to perform secondary authentication. Taking the secondary authentication as slice authentication as an example, UE 210 needs to perform secondary authentication, which can be understood as a user using UE 210 needs to perform secondary authentication.
[0104] 203. UE 210 and the data network complete the secondary authentication through multiple rounds of signaling interaction, and the data network notifies the operator network of the secondary authentication result. The operator network continues to execute other processes based on the secondary authentication result, such as continuing to execute the remaining registration process, terminating the registration process or other related processes, which are not listed here one by one.
[0105] Exemplarily, taking slice authentication as an example, when a user using UE 210 performs secondary authentication with DN 220, multiple rounds of signaling interactions are required to complete the slice authentication, wherein DN 220 can obtain the user identity information signed between UE 110 and DN 220, that is, the identity information of a user using UE 210 mentioned above. For the convenience of description, the user identity information is referred to as DN user identity (DUI) in the embodiment of the present application, and in some embodiments, the user identity information may also be referred to as user ID. The user ID used for secondary authentication is the contract information between the terminal device and the external network other than the operator network, and the operator network may not have this information.
[0106] by Figure 2-AAs shown in the figure, for example, UE 210 sends DUI to AMF 237 in the core network CN 230, and AMF 237 can forward DUI to the authentication device in DN 220 (such as AAA-S 221 shown in the figure). After the secondary authentication is successful, the authentication device in DN220 notifies AMF 237 of the secondary authentication result. It should be noted that in some embodiments, DUI is placed in a message container and sent to AMF, and AMF directly forwards the container to DN, which is the so-called "transparent transmission". In this case, AMF does not parse the DUI in the container, that is, AMF does not know the user's DUI. In addition, in some embodiments, DUI can be forwarded from AMF network function entity 237 to the authentication device in DN 220 through AAA-F 238. At this point, the primary authentication process and the secondary authentication process between UE 210 and the network are completed, and the operator network can also continue other registration processes of UE 210.
[0107] As mentioned above, the secondary authentication process between UE data networks can be based on the EAP authentication mechanism, where the EAP authentication mechanism can support dozens of specific EAP authentication methods. Different UEs can support different or the same EAP authentication methods for the same data network; the same UE can support different or the same EAP authentication methods for different data networks. Different data networks can support different or the same EAP authentication methods.
[0108] For a UE, the supported EAP authentication methods may be one or more; for a data network, the supported EAP authentication methods may be one or more. When the secondary authentication is performed between the UE and the data network, the EAP authentication method supported by both the UE and the data network will be used. It should be understood that in the embodiments of the present application, the EAP authentication method supported by the data network can also be understood as the EAP authentication method supported by the authentication device in the data network. The two expressions have the same meaning and are not strictly distinguished in the embodiments of the present application.
[0109] In order to understand the process of secondary authentication (such as slice authentication) in more detail, the above 203 is further elaborated through a schematic diagram of the signaling interaction process before and after the secondary authentication. Figure 3 Part of the secondary authentication process between the UE and the AAA-S in the data network is schematically shown. It should be understood that the secondary authentication process between the UE and the data network (including AAA-S) also includes other steps such as establishing a connection between the network and AAA-S and details of the EAP authentication process. In order to simplify the description, detailed examples are not given here.
[0110] See also Figure 3 , Figure 3An example is given to illustrate a partial process of a secondary authentication.
[0111] 301. When AMF determines that UE needs to perform secondary authentication and initiates secondary authentication, AMF sends a NAS message to UE that can be used to initiate secondary authentication. At this time, UE has completed primary authentication with the core network, so the NAS message sent by AMF to UE is encrypted and integrity protected. This NAS message includes EAP ID Request information, requesting the user ID (DUI mentioned in step 206) required for secondary authentication from UE.
[0112] 302. The UE replies with a NAS response message to the AMF. The replied NAS response message carries EAP ID Response information, which is used to send the user ID information (DUI) requested in step 301.
[0113] It should be noted that step 301 and step 302 are optional steps, because not all EAP authentication processes need to use DUI or need to send DUI through EAP processes. It should be further noted that in addition to EAP information, NAS messages can also include other relevant information, such as S-NSSAI, etc., which are not limited here.
[0114] 303.AMF sends an EAP authentication request to AAA-S, where the EAP authentication request carries the DUI information (if steps 301 and 302 are executed). Optionally, the EAP authentication request is forwarded by network functions such as AUSF and / or AAA-P. It should be noted that it is not limited here whether the message is forwarded by these network functions or the message carried by the forwarded information and the message type. Optionally, the message sent by AMF to AAA-S may also include other relevant information, such as GPSI, which is not limited here.
[0115] 304. AAA-S sends an EAP authentication response to AMF. Similar to step 303, optionally, it is forwarded by network functions such as AUSF and / or AAA-P. Similarly, the message carried by the forwarded information and the message type, as well as other related information sent, such as GPSI, are not limited here.
[0116] 305. The UE continues to send the information required for EAP authentication to the AMF. Similar to step 303, this information is carried by the encrypted and integrity protected NAS message. This NAS message may also carry other relevant information.
[0117] 306.AMF sends the information required for EAP authentication to AAA-S. Similar to step 304, the forwarding network function, bearer message and other related information are not limited.
[0118] It should be noted that information interaction similar to steps 305-306 may be performed multiple times. The number of interactions depends on factors such as the EAP method used and whether retransmission is required, which is not limited here.
[0119] 307. Based on the above information exchange, AAA-S can obtain / determine the result of EAP authentication, that is, whether the authentication is successful or failed. AAA-S sends the authentication result to AMF to complete the EAP authentication process in the secondary authentication. The sending method is similar to step 304 and will not be repeated here.
[0120] In the above-mentioned secondary authentication method, after the secondary authentication is successful, there is no clear definition of the conditions for the use of the secondary authentication. For example, there is no definition of the validity period of the secondary authentication. This will pose a potential risk to network security and / or network operation efficiency. For example,
[0121] On the one hand, the results of the second-level authentication are not limited to a validity period, and the network can determine the results of the second-level authentication as "permanently valid". For example, the result of a successful second-level authentication will only become invalid after the user ID (DUI) or terminal ID (SUPI) is revoked by the DN (AAA-S) or the operator network respectively.
[0122] On the other hand, if the result of the secondary authentication is stored in the network (such as AMF) as the security context of the terminal, it means that the result of the secondary authentication is bound to the result of the primary authentication. When the primary authentication fails or the UE context fails, the result of the slice authentication will also fail.
[0123] On the other hand, if the result of the secondary authentication is stored in the network (such as AMF) as the context of the terminal, it means that the result of the secondary authentication is bound to the registration status of the terminal in the network. As long as the context of the terminal exists, the result of the slice authentication will be valid for a long time, and in this case, it cannot be shown that different S-NSSAI may have different secondary authentication validity periods.
[0124] In addition, there are no other restrictions on the results of the second-level authentication. For example, there is no restriction on the level of "allowed access" (similar to the "platinum", "gold", "silver" and other authorization levels in commercial services or games). For example, there is no specific restriction on whether "allowed access" is valid in different modes, such as whether access will be restricted when the network needs overload protection.
[0125] The above technical issues may have different negative impacts on the network. For example:
[0126] Because the revocation event of the user / terminal ID is an abnormal behavior processing event, under normal circumstances, after the second-level authentication is successful, it is equivalent to a "permanent" authorization. This long-term authentication authorization can greatly increase the security risks of unauthorized users accessing the slice. For example, if there is no binding relationship between the user and the terminal, after the attacker obtains the user name information, he can use the legitimate terminal to access the slice without authentication (assuming that the user has passed the second-level authentication). On the other hand, if the user and the terminal have a binding relationship, the attacker can steal the SIM card on other legitimate terminals (SIM card misappropriation, loss, theft and cloning, etc.), pass the first-level authentication first, and then directly access the slice without the second-level authentication. This is because the terminal has passed the second-level authentication and is valid for a long time. If the second-level authentication is time-limited, this risk will be greatly reduced. On the other hand, the second-level authentication without time limit makes it impossible for the network to effectively provide time-limited access services. If the process of first authentication and then revocation is used to complete time-limited access, it will cause abuse of the revocation process and increase network resource consumption. When the number of users increases, this waste of network resources will increase significantly.
[0127] If the result of the secondary authentication is bound to the result of the primary authentication by default to implicitly limit the timeliness of the secondary authentication, other problems may arise. First, this may cause difficulties in setting the validity period of the primary authentication security context: on the one hand, if the validity period of the primary authentication is set too long, it will bring greater security risks to the security context of the primary authentication. Generally, the longer the validity period of the security context, the longer the time left for potential attackers to attack, that is, the lower the security. Furthermore, if the UE context is retained in the AMF for a longer time, the storage capacity requirements of the AMF will also be higher. Therefore, usually the UE context and the UE security context are set by the operator based on its own network conditions and security comprehensive considerations, and a reasonable validity period is set. On the other hand, if the validity period of the primary authentication is set too short, frequent slice authentication will result. Because the UE will support multiple slice authentications, the time point for sending slice authentication requests is not fixed. For example, when a slice authentication request occurs near the first-level authentication or when the (security) context is about to expire, the result of the slice authentication will quickly expire, resulting in repeated and unnecessary slice authentication. In particular, slice authentication based on the EAP mechanism requires multiple rounds and a long chain of network interactions (from the terminal to the operator network and then transferred to the external DN), resulting in a significant waste of network resources. When the network needs to support: a) single UE multi-user scenario; b) single user using multiple UE scenarios, the problem is more serious and it is impossible to effectively support various application scenarios in terms of resources.
[0128] If the result of the secondary authentication and the validity of the UE context are used to implicitly limit the timeliness of the secondary authentication, the problem depends on the validity period of the UE context. If it is too long, there will be similar security risks and / or high requirements for storage resources. If it is too short, there will be a problem of frequent secondary authentication. Furthermore, since the UE supports secondary authentication of multiple S-NSSAIs, different S-NSSAIs can have different authentication authorization validity periods. This method cannot achieve differentiated validity periods (UE context as a unified validity period).
[0129] The results of the secondary certification have no other restrictions, making it difficult to effectively provide various application services and to effectively support network operation and resource allocation optimization.
[0130] The following discusses how to increase the mechanism of limiting conditions for secondary authentication. For example, increase the validity period of secondary authentication, optimize the process and storage for validity period, and add other limiting conditions, such as level, mode, etc. For example, the storage method of secondary authentication results, whether it is bound to the UE security context, and whether an independent user-level (security) context is established. The limiting conditions of authentication results include, but are not limited to: validity period, authentication authorization level, authentication authorization operation mode, etc.
[0131] The following is further illustrated by some specific embodiments.
[0132] See also Figure 4 , Figure 4 A flow chart of a communication method provided in an embodiment of the present application.
[0133] 401. Level 1 authentication is performed between the core network and the user equipment.
[0134] 402. After the first-level authentication between the core network and the user equipment is successful, if the second-level authentication is required between the data network and the user equipment, the network function entity (such as AMF, etc.) in the core network assists the data network and the user equipment in performing the second-level authentication.
[0135] Among them, the secondary authentication mentioned in the embodiments of the present application is essentially the authentication between the data network and the user using the user device, and the user device can represent the user using this user device to a certain extent, so it can also be called "secondary authentication between the data network and the user device", of course, in some cases it can also be called "secondary authentication between the data network and the user using the user device" or "secondary authentication between the data network and the user". Among them, in the description of the embodiments of the present application, these terms have the same meaning and can be used interchangeably. Similar "secondary authentication of user devices" and "secondary authentication of users" can be used interchangeably, and so on.
[0136] In addition, the user terminal, user equipment, terminal and terminal equipment mentioned in the embodiments of the present application have the same meaning and can be used interchangeably.
[0137] 403. A secondary authentication is performed between the data network and the user equipment, and the authentication server in the data network sends the authentication result of the secondary authentication and the restriction conditions of the secondary authentication to the core network.
[0138] In some possible implementations, the restriction conditions of the secondary authentication may include, for example, the validity period of the authentication result of the secondary authentication and / or the authorization level of the secondary authentication.
[0139] 404. After the network functional entity obtains the authentication result of the secondary authentication and the restriction conditions of the secondary authentication from the data network, the network functional entity stores the obtained authentication result of the secondary authentication and the restriction conditions of the secondary authentication in the core network (for example, it can be stored in the AMF or UDM in the core network, etc.).
[0140] 405. The network function entity sends the obtained authentication result of the secondary authentication and the restriction condition of the secondary authentication to the user equipment. The user equipment may receive and store the authentication result of the secondary authentication and the restriction condition of the secondary authentication.
[0141] It can be seen that in the above example scheme, by introducing the restriction conditions of the secondary authentication, it becomes possible for the authentication results of the secondary authentication to be used reasonably and restrictively, laying the foundation for the effective management of the authentication results of the secondary authentication, which in turn is conducive to improving the security and effectiveness of business operations based on the secondary authentication.
[0142] In some possible implementations, the authentication result of the secondary authentication is stored in binding with the authentication result of the primary authentication (the authentication result of the secondary authentication is stored in binding with the authentication result of the primary authentication, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the authentication result of the primary authentication) or stored independently; or the authentication result of the secondary authentication is stored in binding with the user device context (the authentication result of the secondary authentication is stored in binding with the user device context, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the user device context) or stored independently, or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the user device context, or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the primary authentication.
[0143] In some possible implementations, the network function entity in the core network assisting the data network and the user equipment in performing secondary authentication includes: when it is determined that the initiation condition for the secondary authentication of the user equipment is met, the network function entity in the core network assisting the data network and the user equipment in performing secondary authentication. When it is determined that the initiation condition for the secondary authentication of the user equipment is not met, the core network rejects the secondary authentication request of the user equipment or directly determines that the secondary authentication between the data network and the user equipment is unsuccessful.
[0144] In some possible implementations, the method may also include: the network function entity obtains the accompanying information of the secondary authentication from the data network, and the network function entity stores the obtained accompanying information of the secondary authentication to the core network, and the accompanying information can be used to determine the initiation conditions of the next secondary authentication of the user device or other user devices.
[0145] For example, the initiation conditions of the secondary authentication may be determined by the accompanying information of one or several secondary authentications that have been performed for the current UE or other UEs that have been stored before. For example, when the operator network performs secondary authentication for other UEs (secondary authentication for S-NSSAI), the initiation conditions of the secondary authentication are used to assist the AMF in determining whether to continue the secondary authentication process or directly determine that the secondary authentication has failed. Similarly, if the secondary authentication fails, the reason for the authentication failure can be provided to the core network, and the reason for the authentication failure can be used as the accompanying information of this secondary authentication, which is used by the AMF to assist in determining whether this user or other users meet the secondary authentication (for S-NSSAI) conditions next time. For example, AAA-S successfully completes the authentication authorization for the user, but the DN network capacity or the number of users that can be supported reaches the upper limit, AAA-S can notify the operator network that the DN is temporarily running in "full load mode" and will not accept more secondary authentications temporarily. At this time, AAA-S can also send a timer, which is used to limit the specific duration of "temporary". After receiving the timer, AMF stores it in the core network (such as AMF, UDM). The next time other UE applies for secondary authentication, the secondary authentication application can be directly rejected to avoid unnecessary signaling interaction between the operator's core network and DN.
[0146] In some possible implementations, when the authentication result of the secondary authentication is authentication failure and the restriction condition of the secondary authentication is the validity period of the authentication result, the method further includes: the user device re-initiating the secondary authentication with the data network after determining that the validity period of the authentication result has expired; and the user device suspending the initiation of the secondary authentication with the data network before determining that the validity period of the authentication result has expired.
[0147] In some possible implementations, the method further includes: when the network function entity receives an update request from the data network for requesting to update the secondary authentication restriction condition, updating the secondary authentication restriction condition stored in the core network according to the update request. Further, when the network function entity receives an update request from the data network for requesting to update the secondary authentication restriction condition, the network function entity may also send the update request to a user device, and after receiving the update request, the user device updates the secondary authentication restriction condition stored in the user device according to the update request.
[0148] See also Figure 5 , Figure 5 A flow chart of a communication method provided in an embodiment of the present application. Figure 5 In the embodiment shown by way of example, a validity period restriction condition is added for the secondary authentication, wherein the storage location of the secondary authentication restriction condition and the authentication result in the core network may be AMF and / or UDM (or may also be stored in other network functions).
[0149] like Figure 5 For example, a communication method may include:
[0150] 501. A first-level authentication is performed between the UE and the core network, and a security context for the first-level authentication is established.
[0151] For example, the first-level authentication establishes NAS security, and the subsequent NAS signaling interactions between the UE and the network can be encrypted and integrity protected.
[0152] 502.AMF determines whether the UE (the user using the UE) needs to perform secondary authentication.
[0153] Among them, the judgment method may include: querying AMF local storage or querying UDM storage.
[0154] After the query, it is determined whether the UE or / and the user has already undergone secondary authentication, and the result of the successful secondary authentication is still valid. The indication of validity can be a period, and it is valid within this period. The indication of validity can also be a timer. When the timer does not point to 0, the secondary authentication is still valid. When the timer points to 0, the secondary authentication is invalid. The present invention does not limit the method of indicating the validity period.
[0155] 503. If there is no valid secondary authentication, it is determined that secondary authentication is required between the UE and the data network, and the AMF assists the UE and AAA-S in performing secondary authentication.
[0156] The secondary certification process is similar Figure 3The example process of steps 302-307 is not repeated here, and reference can be made to the above example description.
[0157] Before AMF initiates the secondary authentication between UE and AAA-S, it can further determine whether the initiation conditions of the secondary authentication are met. Of course, the initiation conditions can also be assumed to be met, which is equivalent to no initiation conditions. AMF initiates the secondary authentication between UE and AAA-S only when the initiation conditions of the secondary authentication are met.
[0158] For example, the initiation conditions of the secondary authentication may be determined by the accompanying information of one or several secondary authentications that have been performed for the current UE or other UEs that have been stored before. For example, when the operator network performs secondary authentication for other UEs (secondary authentication for S-NSSAI), the initiation conditions of the secondary authentication are used to assist the AMF in determining whether to continue the secondary authentication process or directly determine that the secondary authentication has failed. Similarly, if the secondary authentication fails, the reason for the authentication failure can be provided to the core network, and the reason for the authentication failure can be used as the accompanying information of this secondary authentication, which is used by the AMF to assist in determining whether this user or other users meet the secondary authentication (for S-NSSAI) conditions next time. For example, AAA-S successfully completes the authentication authorization for the user, but the DN network capacity or the number of users that can be supported reaches the upper limit, AAA-S can notify the operator network that the DN is temporarily running in "full load mode" and will not accept more secondary authentications temporarily. At this time, AAA-S can also send a timer, which is used to limit the specific duration of "temporary". After receiving the timer, AMF stores it in the core network (such as AMF, UDM). The next time other UE applies for secondary authentication, the secondary authentication application can be directly rejected to avoid unnecessary signaling interaction between the operator's core network and DN.
[0159] 504. If the secondary authentication is successful, AAA-S can set the validity period of the secondary authentication (and can also set the additional information of the secondary authentication), and send the validity period and the successful authentication result to the core network (such as AMF).
[0160] The validity period may be bound to the S-NSSAI, that is, the validity period of the secondary authentication may be different for different S-NSSAIs. The validity period may also be bound to the UE or / and user, and different UEs or / and users may have different validity periods for the secondary authentication of the same S-NSSAI.
[0161] 505. After receiving the authentication result message from AAA-S, the core network (such as AMF) stores the authentication result and validity period (and may also store accompanying information).
[0162] It should be noted that different storage methods and storage locations may affect the validity period of the authentication result. The main possible storage methods are: 1) binding the security context of the first-level authentication; 2) binding the UE context (independent of other contexts); 3) defining an independent "user" context (independent of the UE context).
[0163] The storage method and storage location have the following optional implementations:
[0164] 1) The secondary authentication result is bound to the primary authentication result (or the security context after the primary authentication) and stored, that is, when the security context of the primary authentication fails, the secondary authentication result automatically fails. This storage method may cause potential problems of repeated secondary authentication. This is because a UE usually supports secondary authentication of multiple S-NSSAIs. When the UE applies to access a certain S-NSSAI, if the previous primary authentication is still valid (or has a security context), the primary authentication will no longer be performed, and only the secondary authentication for the S-NSSAI will be performed. At this time, if the primary authentication is valid but there is not much time left in the validity period, the validity of the successful secondary authentication will become invalid with the failure of the primary authentication, wasting the secondary authentication. On the other hand, if you try to modify the validity period of the primary authentication based on the secondary authentication result / validity period, other problems will arise. On the one hand, the validity period of the primary authentication may be significantly extended according to the secondary authentication result, and setting an overly long validity period poses a risk to the security of the primary authentication security context. On the other hand, the secondary authentication is usually controlled by the external network, while the primary authentication is controlled by the operator. The method of increasing the validity of the primary authentication through the secondary authentication may lead to the risk of the external network controlling the primary authentication.
[0165] 2) The secondary authentication result is bound to the UE context for storage, that is, when the UE context expires, the secondary authentication result will also automatically expire. When this method is used, the independence of the validity period of the secondary authentication result needs to be guaranteed, that is, the result / validity period of the secondary authentication will not be invalidated due to the invalidation of other contexts. Since a UE will support the secondary authentication of multiple S-NSSAIs, the validity periods of the secondary authentication will be very different, which may cause the UE context to be valid for a long time due to the existence of the secondary authentication, occupying storage resources. Therefore, this storage method needs to reasonably set the validity period of its UE context according to the specific situation. If it is too short, the actual validity period of the secondary authentication will also be shortened, and re-authentication is required. If it is set too long, it will occupy too many storage resources. On the other hand, different S-NSSAIs may be processed by different AMFs. Furthermore, the same S-NSSAI may also be processed by different AMFs at different times (such as AMF relocation, traffic control, etc.). In this case, the result / validity period of the secondary authentication can be more effectively stored centrally, such as stored in the UDM, and the AMF can access and query the UDM to obtain information such as the secondary authentication result / validity period.
[0166] 3) Define a new independent user context, which can be independent of the UE context. This is a flexible storage method that decouples the user of slice authentication and the terminal UE that carries it. The "user" here refers to the user who performs secondary authentication, and the result / validity period of slice authentication can be naturally decoupled from the UE context. At the same time, this method can more effectively support application scenarios where multiple users use the same UE and the same user uses multiple UEs. The former means that multiple users use the same terminal to access the network at different times for secondary authentication. Although the same terminal uses the same primary authentication, each secondary authentication is independent of each other due to different users. The latter means that a user can use different terminals to access the slice (secondary authentication) at different times. As long as the slice authentication is valid, the user does not have to perform slice authentication again.
[0167] 506. The core network sends the secondary authentication result and / or validity period to the UE. The UE may store the received secondary authentication result and / or validity period.
[0168] This embodiment introduces a validity period restriction condition for secondary authentication, which is conducive to effectively restricting the secondary authentication result, thereby helping to reduce the security risk of unauthorized access to slices, and effectively supporting time-limited access and restricted access slice services. It is also conducive to avoiding unnecessary multiple slice authentications and improving network resource utilization. It is conducive to effectively supporting application scenarios of single UE with multiple users and single user with multiple UEs.
[0169] See also Figure 6 , Figure 6 A flowchart of another communication method provided in an embodiment of the present application. Figure 5 In the embodiment shown by way of example, a restriction condition of the authorization level is added for the secondary authentication, wherein the restriction condition of the secondary authentication and the storage location of the authentication result in the core network may be AMF and / or UDM (or may also be stored in other network functions).
[0170] like Figure 6 By way of example, another communication method may include:
[0171] 601. A first-level authentication is performed between the UE and the core network, and a security context for the first-level authentication is established.
[0172] For example, the first-level authentication establishes NAS security, and the subsequent NAS signaling interactions between the UE and the network can be encrypted and integrity protected.
[0173] 602.AMF determines whether the UE (the user using the UE) needs to perform secondary authentication.
[0174] Among them, the stored secondary authentication authorization status can be checked, such as whether secondary authentication is required, whether secondary authentication is within the validity period, etc.
[0175] 603. If there is no valid secondary authentication, it is determined that secondary authentication is required between the UE and the data network, and the AMF assists the UE and AAA-S in performing secondary authentication.
[0176] The secondary certification process is similar Figure 3 The example process of steps 302-307 is not repeated here, and reference can be made to the above example description.
[0177] Among them, AMF can send a secondary authentication request to AAA-S, and the secondary authentication request can carry a recommended secondary authentication authorization level, for example.
[0178] 604. If the secondary authentication is successful, AAA-S sets the authorization level of this secondary authentication (and can also set the additional information of the secondary authentication), and sends the authorization level and the authentication result of successful authentication to the core network (such as AMF).
[0179] It should be noted that regardless of whether the secondary authentication request sent by AMF to AAA-S carries the authorization level, AAA-S can perform the action of setting the authorization level according to DN policy, etc.
[0180] 605. After receiving the authentication result message from AAA-S, the core network (such as AMF) stores the authentication result and validity period (and may also store accompanying information).
[0181] Among them, the considerations of storage method and storage location can refer to Figure 4 The examples given are examples.
[0182] It should be noted that, on the one hand, if different levels use different S-NSSAIs, the AMF may allocate "allowed S-NSSAI" according to the authorization level, and send the allowed S-NSSAI without sending the authorization level in step 606. On the other hand, if different levels use the same S-NSSAI, the AMF sends both the allowed S-NSSAI and the authorization level in step 606.
[0183] Among them, the authorization level of the second-level authentication is similar to the authorization levels of "platinum", "gold", "silver", etc. in commercial services or games. Different authorization levels may have different privileges. The higher the authorization level, the higher the privileges it may enjoy.
[0184] It should be further explained that the incidental information in this embodiment includes some auxiliary information. When the operator network performs secondary authentication for other terminals (secondary authentication for the S-NSSAI), the incidental information can assist the network in determining whether to continue the secondary authentication process or directly determine that the secondary authentication has failed. Similarly, if the secondary authentication fails, the reason for the authentication failure can be provided to the network, wherein the reason for the authentication failure can be used as auxiliary information for the network to perform secondary authentication (for the S-NSSAI) for the user / terminal or other users / terminals next time for auxiliary judgment.
[0185] 606. The core network sends the secondary authentication result to the UE. The UE may store the received secondary authentication result. In this step, whether the core network sends the authorization level to the UE may follow the judgment in the example of step 605.
[0186] This embodiment introduces restrictions on the authorization level for secondary authentication, which is conducive to effectively restricting secondary authentication, thereby helping to reduce the security risks of unauthorized access to slices, and effectively supporting time-limited access and restricted access slice services. It is also conducive to avoiding unnecessary multiple slice authentications and improving network resource utilization. It is conducive to effectively supporting application scenarios of single UE with multiple users and single user with multiple UEs.
[0187] See also Figure 7 , Figure 7 A flowchart of another communication method provided in an embodiment of the present application.
[0188] Figure 7The example embodiment is a restriction condition update process for secondary authentication. AAA-S stores the secondary authentication result and restriction conditions (validity period or authorization level, etc.) of each user based on previous authentication records. It is assumed that AAA-S needs to modify the restriction conditions of the previous secondary authentication of a user (such as changing the validity period, authorization level, etc.) according to the change of contract data or according to the policy of DN / AAA-S.
[0189] 701. AAA-S sends an update request to the core network, wherein the update request includes a user ID, a terminal ID (such as GPSI) and an authority value to be updated, where the updated authority value is, for example, a new validity period or an updated authorization level (such as changing a silver user to a gold user).
[0190] Optionally, the update request may also carry information such as the S-NSSAI of the user / terminal (if the information can be obtained by AAA-S).
[0191] 702. After receiving the update request, the core network (such as AMF) can update the restrictions of the locally stored secondary authentication.
[0192] In addition, AMF may also send an update request to UDM. Optionally, if AMF knows that other AMFs also store restrictions on secondary authentication, AMF may also directly forward the update request to other relevant AMFs, thereby triggering the update of restrictions on secondary authentication stored in other AMFs.
[0193] Correspondingly, UDM also updates the secondary authentication restriction accordingly. Optionally, UDM can also continue to forward the update request to other AMFs that store the secondary authentication restriction, thereby triggering other AMFs to also update the stored secondary authentication restriction.
[0194] 703. The network (such as AMF) sends an update request to the UE, and the UE updates the restrictions of the secondary authentication stored locally based on the update request.
[0195] It should be noted that steps 702 and 703 may be performed in any order, for example, step 703 may be performed first and then step 702.
[0196] The embodiment of the present application is mainly aimed at secondary authentication or slice authentication, and is also applicable to session-based secondary authentication scenarios, etc. I will not go into details here. The embodiment of the present application introduces restriction conditions for secondary authentication, which is conducive to effectively restricting the secondary authentication results, reducing the security risks of unauthorized access to slices, and effectively supporting time-limited access and access slice services with restricted conditions. It is conducive to avoiding unnecessary multiple slice authentications and improving network resource utilization. It is conducive to more effectively supporting application scenarios of single UE with multiple users and single user with multiple UEs.
[0197] The embodiments of the present application may be backward compatible, that is, if no restrictive conditions are sent, it is equivalent to unrestricted access, or it may be implicitly indicated based on the storage characteristics of the secondary authentication result.
[0198] See also Figure 8 , an embodiment of the present application provides a user equipment 800, including:
[0199] The authentication unit 810 is used to perform the secondary authentication between the user equipment and the data network with the assistance of the core network after the primary authentication between the core network and the user equipment is successful, if the secondary authentication is still required between the user equipment and the data network.
[0200] The interaction unit 820 is used to receive the authentication result of the secondary authentication and the restriction condition of the secondary authentication sent by the core network.
[0201] The storage unit 830 is used to store the received authentication result of the secondary authentication and the restriction condition of the secondary authentication.
[0202] In some possible implementations, the authentication unit 810 is further used to, when the authentication result of the secondary authentication is authentication failure and the restriction condition of the secondary authentication is the validity period of the authentication result, after determining that the validity period of the authentication result has expired, re-initiate the secondary authentication with the data network; and before determining that the validity period of the authentication result has expired, suspend the initiation of the secondary authentication with the data network.
[0203] In some possible implementations, the interaction unit 820 is further configured to: receive the secondary authentication incidental information sent by the core network; if it is determined that the initiation condition for the secondary authentication of the user equipment is met, initiate the secondary authentication with the data network again; if it is determined that the initiation condition for the secondary authentication of the user equipment is not met, suspend the initiation of the secondary authentication with the data network. The incidental information is used to determine the initiation condition for the next secondary authentication of the user equipment.
[0204] Among them, the various modules of the user equipment 800 can cooperate to execute part or all of the steps of each method executed by the UE in the above method embodiments.
[0205] See also Fig. 9 The embodiment of the present application provides an authentication server 900 in a data network, including:
[0206] The secondary authentication unit 910 is used to perform secondary authentication with the user equipment with the assistance of the core network (such as AMF).
[0207] The interaction unit 920 is used to send the authentication result of the secondary authentication and the restriction conditions of the secondary authentication to the core network (such as AMF), wherein the authentication result of the secondary authentication and the restriction conditions of the secondary authentication can be stored by the core network.
[0208] In some possible implementations, the restriction condition of the secondary authentication may include, for example, the validity period of the authentication result of the secondary authentication and / or the authorization level of the secondary authentication.
[0209] In some possible implementations, the interaction unit 920 is further configured to: send the secondary authentication supplementary information to the core network. The supplementary information can be stored by the core network and can be used to determine the initiation condition of the next secondary authentication of the user equipment or other user equipment.
[0210] In some possible implementations, the interaction unit 920 is further used to: send an update request to the core network for requesting to update the secondary authentication restriction condition, wherein the update request is used to trigger the core network to update the stored secondary authentication restriction condition.
[0211] The various modules of the authentication server 900 may cooperate to execute part or all of the steps of the various methods executed by the authentication server in the above method embodiments.
[0212] See also Fig.10 The embodiment of the present application provides a network function entity 1000 in a core network, which may include:
[0213] The assisting unit 1010 is used to assist the data network in performing the secondary authentication with the user equipment after the primary authentication between the core network and the user equipment is successful, if the secondary authentication is still required between the data network and the user equipment.
[0214] The acquisition unit 1020 is used for the network function entity to obtain the authentication result of the secondary authentication and the restriction condition of the secondary authentication from the data network.
[0215] The storage unit 1030 is used to store the acquired authentication result of the secondary authentication and the restriction condition of the secondary authentication in the core network (for example, it can be stored in the AMF or UDM in the core network, etc.).
[0216] It can be seen that in the above example scheme, by introducing the restriction conditions of the secondary authentication, it becomes possible for the authentication results of the secondary authentication to be used reasonably and restrictively, laying the foundation for the effective management of the authentication results of the secondary authentication, which in turn is conducive to improving the security and effectiveness of business operations based on the secondary authentication.
[0217] In some possible implementations, the restriction condition of the secondary authentication may include, for example, the validity period of the authentication result of the secondary authentication and / or the authorization level of the secondary authentication.
[0218] In some possible implementations, the storage unit 1030 stores the authentication result of the secondary authentication in a bound manner with the authentication result of the primary authentication (the authentication result of the secondary authentication is stored in a bound manner with the authentication result of the primary authentication, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the authentication result of the primary authentication) or stores it independently; or the storage unit stores the authentication result of the secondary authentication in a bound manner with the user device context (the authentication result of the secondary authentication is stored in a bound manner with the user device context, which may indicate that the validity period of the authentication result of the secondary authentication is the same as or has a corresponding relationship with the user device context) or stores it independently. Or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the user device context. Or the validity period of the secondary authentication is equal to or not equal to (greater than or less than) the validity period of the primary authentication.
[0219] In some possible implementations, the assisting unit 1010 assisting the data network with performing secondary authentication with the user equipment includes: assisting the data network with performing secondary authentication with the user equipment when it is determined that the initiation condition for the secondary authentication of the user equipment is met. In addition, when it is determined that the initiation condition for the secondary authentication of the user equipment is not met, the secondary authentication request of the user equipment may be rejected or the secondary authentication between the data network and the user equipment may be directly determined to be unsuccessful.
[0220] In some possible implementations, the acquisition unit 1020 is further configured to: acquire the accompanying information of the secondary authentication from the data network.
[0221] The storage unit is further used to store the acquired accompanying information of the secondary authentication in the core network, and the accompanying information can be used to determine the initiation condition of the next secondary authentication of the user equipment or other user equipment.
[0222] In some possible implementations, the network function entity in the core network further includes a notification unit 1040, configured to send the acquired authentication result of the secondary authentication and the restriction condition of the secondary authentication to the user equipment. The user equipment may receive and store the authentication result of the secondary authentication and the restriction condition of the secondary authentication.
[0223] In some possible implementations, the network functional entity in the core network also includes an update unit 1050, which is used to update the secondary authentication restriction conditions stored in the core network according to the update request when an update request for requesting to update the secondary authentication restriction conditions is received from the data network.
[0224] Further, the notification unit 1040 may also be used to send the update request to the user equipment when the network function entity receives the update request from the data network for requesting to update the secondary authentication restriction condition. After receiving the update request, the user equipment may update the secondary authentication restriction condition stored in the user equipment according to the update request.
[0225] Among them, the various modules of the network function entity 1000 can cooperate to execute part or all of the steps of each method performed by the AMF in the above method embodiment.
[0226] See also Fig.11 , an embodiment of the present application further provides a communication device 1100, the communication device comprising a coupled processor 1110 and a memory 1120; wherein the processor is used to call a program stored in the memory to complete part or all of the steps of any method performed by any device provided in the embodiment of the present application. For example, when the processor executes part or all of the steps executed by the UE in the above method embodiment, the communication device 1100 is the UE. When the processor executes part or all of the steps executed by the AMF in the above method embodiment, the communication device 1100 is the AMF. When the processor executes part or all of the steps executed by the authentication server AAA-S in the above method embodiment, the communication device 1100 is the authentication server in the data network. And so on.
[0227] Among them, the processor 1110 is used to call the computer program stored in the memory 1120, and then complete part or all of the steps of any method performed by devices such as UE, AMF or AAA-S in the embodiments of the present application.
[0228] Among them, the processor 1110 is also called a central processing unit (CPU). In a specific application, the components of the communication device are coupled together, for example, through a bus system. Among them, the bus system may include a power bus, a control bus, and a status signal bus in addition to a data bus. However, for the sake of clarity, various buses are marked as bus system 1130 in the figure. Among them, the method disclosed in the above-mentioned embodiment of the present application can be applied to the processor 1110, or implemented by the processor 1110. The processor 1110 may be an integrated circuit chip with signal processing capabilities. In some implementation processes, some or all of the steps of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 1110. The processor 1110 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a ready-made programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The processor 1110 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor 1110 may be a microprocessor or the processor may also be any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory or a register. The storage medium is located in the memory 1120, for example, the processor 1110 can read the information in the memory 1120, and complete some or all of the steps of the above method in combination with its hardware.
[0229] In addition, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is executed by related hardware to complete the execution of any one of the methods provided in the embodiment of the present invention.
[0230] In addition, an embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is enabled to execute any one of the methods provided in the embodiments of the present invention.
[0231] In the above embodiments, the description of each embodiment has its own emphasis, and for the parts not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0232] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, some steps may be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily required by the present application.
[0233] In the several embodiments provided in the present application, it should be understood that the disclosed device can be implemented in other ways. For example, the device embodiments described above are only schematic, such as the division of the above-mentioned units, which is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical or other forms.
[0234] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0235] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-accessible storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, wherein the computer software product is stored in a computer-readable storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc., specifically a processor in a computer device) to perform all or part of the steps of the above-mentioned methods of various embodiments of the present application. Among them, the aforementioned storage medium may include: U disk, mobile hard disk, magnetic disk, optical disk, read-only memory (ROM) or random access memory (RAM) and other media that can store program codes.
[0236] As described above, the above embodiments are only used to illustrate the technical solutions of the present application rather than to limit it. Although the present application has been described in detail with reference to the aforementioned embodiments, a person skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims
1. A communication method, characterized in that: include: After the primary authentication between the core network and the user equipment is successful, if the data network and the user equipment need to perform secondary authentication, the network function entity in the core network assists the data network and the user equipment in performing secondary authentication, and the network function entity is the access and mobility management function AMF; The network function entity obtains the authentication result of the secondary authentication and the restriction condition of the secondary authentication from the data network; The network function entity stores the acquired authentication result of the secondary authentication and the restriction condition of the secondary authentication in the core network; The restriction condition of the secondary authentication includes the authorization level of the secondary authentication, and users of different authorization levels have different privileges; in, The data network is a network located outside the 3GPP network, and the core network is located in the 3GPP network.
2. The method according to claim 1, characterized in that The restriction conditions of the secondary authentication also include the validity period of the authentication result of the secondary authentication.
3. The method according to claim 2, characterized in that: The authentication result of the secondary authentication is stored in conjunction with or independently of the authentication result of the primary authentication; or the authentication result of the secondary authentication is stored in conjunction with or independently of the user device context, or the validity period of the secondary authentication is not equal to the validity period of the user device context, or the validity period of the secondary authentication is not equal to the validity period of the primary authentication.
4. The method according to any one of claims 1 to 3, characterized in that: The authentication result of the secondary authentication and the restriction condition of the secondary authentication are stored in a unified data management network function UDM in the core network.
5. The method according to claim 4, characterized in that The network function entity in the core network assists the data network and the user equipment in performing secondary authentication, including: when it is determined that the initiation conditions for the secondary authentication of the user equipment are met, the network function entity in the core network assists the data network and the user equipment in performing secondary authentication.
6. The method according to claim 5, characterized in that: The method also includes: the network function entity obtains the accompanying information of the secondary authentication from the data network, and the network function entity stores the obtained accompanying information of the secondary authentication in the unified data management network function UDM in the core network, and the accompanying information can be used to determine the initiation conditions of the next secondary authentication of the user equipment or other user equipment.
7. The method according to claim 5, characterized in that The method further includes: the network function entity sending the acquired authentication result of the secondary authentication and the restriction condition of the secondary authentication to the user equipment.
8. The method according to claim 4, characterized in that The method also includes: when the network function entity receives an update request from the data network for requesting to update the secondary authentication restriction condition, updating the secondary authentication restriction condition stored in the unified data management network function UDM in the core network according to the update request.
9. The method according to claim 5, characterized in that The method also includes: when the network function entity receives an update request from the data network for requesting to update the secondary authentication restriction condition, updating the secondary authentication restriction condition stored in the unified data management network function UDM in the core network according to the update request.
10. A communication method, characterized in that: include: The authentication server in the data network performs secondary authentication with the user equipment with the assistance of the core network; Sending the authentication result of the secondary authentication and the restriction condition of the secondary authentication to the access and mobility management function AMF in the core network, where the authentication result of the secondary authentication and the restriction condition of the secondary authentication can be used by the core network; The restriction condition of the secondary authentication includes the authorization level of the secondary authentication, and users of different authorization levels have different privileges; The data network is a network outside the 3GPP network, and the core network is located in the 3GPP network.
11. The method according to claim 10, characterized in that The authentication result of the secondary authentication and the restriction condition of the secondary authentication are stored in a unified data management network function UDM in the core network; The method also includes: the authentication server sending an update request to the core network for requesting to update the secondary authentication restriction condition, wherein the update request is used to trigger the core network to update the secondary authentication restriction condition stored in a unified data management network function UDM.
12. The method according to any one of claims 10 to 11, characterized in that: The restriction conditions of the secondary authentication also include the validity period of the authentication result of the secondary authentication.
13. A communication method, characterized in that: include: After the primary authentication between the core network and the user equipment is successful, if the secondary authentication is still required between the user equipment and the data network, the user equipment performs the secondary authentication with the data network with the assistance of the core network; The user equipment receives the authentication result of the secondary authentication and the restriction condition of the secondary authentication sent by the access and mobility management function AMF in the core network; The user equipment stores the received authentication result of the secondary authentication and the restriction condition of the secondary authentication, wherein the authentication result of the secondary authentication and the restriction condition of the secondary authentication are from the data network; The restriction condition of the secondary authentication includes the authorization level of the secondary authentication, and users of different authorization levels have different privileges; The data network is a network outside the 3GPP network, and the core network is located in the 3GPP network.
14. The method according to claim 13, characterized in that In the case where the authentication result of the secondary authentication is authentication failure and the restriction condition of the secondary authentication is the validity period of the authentication result, the method further includes: the user equipment re-initiating the secondary authentication with the data network after determining that the validity period of the authentication result has expired; and the user equipment suspending the initiation of the secondary authentication with the data network before determining that the validity period of the authentication result has expired.
15. The method according to claim 13, characterized in that The method also includes: the user equipment receives the accompanying information of the secondary authentication sent by the core network; the user equipment again initiates the secondary authentication with the data network when it is determined that the initiation condition of the secondary authentication of the user equipment is met; the user equipment suspends the initiation of the secondary authentication with the data network when it is determined that the initiation condition of the secondary authentication of the user equipment is not met, wherein the accompanying information is used to determine the initiation condition of the next secondary authentication of the user equipment.
16. The method according to any one of claims 13 to 15, characterized in that: The restriction conditions of the secondary authentication also include the validity period of the authentication result of the secondary authentication.
17. A communication device, characterized in that: The communication device includes a coupled processor and memory; The processor is used to call the computer program stored in the memory to complete the method described in any one of claims 1 to 16.
18. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it can implement the method according to any one of claims 1 to 16.
