Methods for external authentication and authorization
Through indicator interaction between wireless terminals and network entities, using protocols such as EAP, PAP or CHAP, the problem of external authentication and authorization compatibility between EPS and 5G systems is solved, and the secure and compatible transfer of network connections is achieved.
Patent Information
- Application Number
- CN202180089655.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-01-14
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2041-01-14
AI Technical Summary
Existing Evolution Packet Systems (EPS) do not support external authentication and authorization methods based on Extensible Authentication Protocol (EAP), resulting in authentication and authorization compatibility issues when transferring network connections between EPS and 5G systems.
By sending indicators between wireless terminals and network entities, identify supported external authentication and authorization methods and use EAP, Password Authentication Protocol (PAP) or Challenge Handshake Authentication Protocol (CHAP) to ensure that, if necessary, The smooth transfer of protocol data unit sessions between different networks.
Support for EAP-based external authentication and authorization methods between EPS and 5G systems is realized, ensuring the security and compatibility of network connections, and solving the limitations of authentication and authorization methods in the prior art.
Smart Images

Figure CN116686333B_ABST
Abstract
Description
Technical Field
[0001] This document relates generally to wireless communications and specifically to external authentication and authorization. Background Art
[0002] In the Evolved Packet System (EPS), if external authentication and authorization is required during the Packet Data Network (PDN) connection establishment process, the Password Authentication Protocol (PAP) and the Challenge Handshake Authentication Protocol (CHAP) are used as external authentication and authorization methods. In addition, EPS does not support external authentication and authorization based on the Extensible Authentication Protocol (EAP) for PDN connections.
[0003] In the 5G system (5GS), in addition to PAP and CHAP, if external authentication and authorization are required during the Protocol Data Unit (PDU) session establishment process, EAP is used as an external authentication and authorization method.
[0004] From a security perspective, PAP is an outdated protocol. CHAP provides stronger security than PAP. Compared with PAP and CHAP, EAP is the most recommended external authentication and authorization method. In 5GS, PAP and / or CHAP are still used for user equipment (UE) using some legacy applications.
[0005] Interworking with the Evolved Packet Core (EPC) refers to the mobility process between the 5G Core Network (5GC) and the EPC / E-UTRAN (Evolved Universal Terrestrial Radio Access Network). If the UE: 1) transfers a PDU session that has been authenticated and authorized by an external data network (DN) to EPS by using EAP in 5GS, and 2) re-authentication is required, the UE requires EPS to support EAP-based external authentication and authorization methods for mapping access point names (APNs) to DN names (DN Names, DNNs).
[0006] If the UE wants to transfer a PDN connection session that has been authenticated and authorized by an external DN to the 5GS through EAP in EPS, the UE requires the 5GS to support EAP-based external authentication and authorization for mapping the APN.
[0007] From the above, it can be seen that how to support EAP-based external authentication and authorization in EPS becomes an issue that needs to be discussed. Summary of the invention
[0008] This document relates to methods, systems, and devices for external authentication and authorization, and more specifically, to methods, systems, and devices for supporting EAP-based external authentication and authorization in EPS.
[0009] The present disclosure relates to a wireless communication method used in a network entity, the method comprising:
[0010] receiving an indicator from the wireless terminal, the indicator being associated with a capability to support at least one method of interacting with an external network to authenticate and / or authorize the external network for a packet data connection, and
[0011] A procedure is performed based on the indicator, wherein the procedure is associated with establishing a packet data network connection in the second network.
[0012] Various embodiments may preferably implement the following features:
[0013] Preferably, at least one method comprises at least one of the following:
[0014] Extensible Authentication Protocol,
[0015] Password Authentication Protocol, or
[0016] Challenge-Handshake Authentication Protocol.
[0017] Preferably, the process is associated with transferring a protocol data unit session of the wireless terminal from a first network to a second network as a packet data network connection, wherein the protocol data unit session is established with an external server using a first external authentication and / or authorization method.
[0018] Preferably, the first network is associated with a 5G system and the second network is associated with an Evolved Packet System.
[0019] Preferably, performing the process based on the indicator comprises determining whether to allocate an Evolved Packet System bearer identifier to the quality of service flow of the protocol data unit session based on the indicator.
[0020] Preferably, determining whether to allocate an evolved packet system bearer identifier to the quality of service flow of the protocol data unit session based on the indicator includes: when the indicator indicates that the wireless terminal supports the first external authentication and / or authorization method, allocating the evolved packet system bearer identifier to the quality of service flow of the protocol data unit session.
[0021] Preferably, determining whether to allocate an Evolved Packet System bearer identifier to a quality of service flow of a protocol data unit session based on the indicator comprises:
[0022] When at least one condition is met, not allocating an Evolved Packet System bearer identifier to a quality of service flow of a protocol data unit session,
[0023] Wherein, at least one condition includes at least one of the following:
[0024] the second network does not support the first external authentication and / or authorization method,
[0025] The indicator indicates that the wireless terminal does not support the first external authentication and / or authorization method, or
[0026] The access point name corresponding to the data network name of the protocol data unit session requires a second external authentication and / or authorization method that is different from the first external authentication and / or authorization method.
[0027] Preferably, the second network supports the first external authentication and / or authorization method, and the indicator indicates that the wireless terminal supports the first external authentication and / or authorization method,
[0028] The indicator-based execution process includes:
[0029] performing an external authentication and / or authorization process between the wireless terminal and the external server using a first external authentication and / or authorization method,
[0030] sending an indicator to the wireless terminal indicating that an external authentication and / or authorization process is being performed during the process, and
[0031] An external authentication and / or authorization process is performed between the wireless terminal and the external server.
[0032] Preferably, executing the process based on the indicator includes:
[0033] When at least one condition is met, sending a cause value indicating a process failure to the wireless terminal,
[0034] Wherein, at least one condition includes at least one of the following:
[0035] the second network does not support the first external authentication and / or authorization method,
[0036] The indicator indicates that the wireless terminal does not support the first external authentication and / or authorization method, or
[0037] The access point name corresponding to the data network name of the protocol data unit session requires a second external authentication and / or authorization method that is different from the first external authentication and / or authorization method.
[0038] Preferably, the second network supports the Extensible Authentication Protocol, and the indicator indicates that the wireless terminal supports the Extensible Authentication Protocol,
[0039] The indicator-based execution process includes:
[0040] Performing an external authentication and / or authorization process between the wireless terminal and an external server using the Extensible Authentication Protocol,
[0041] sending an indicator to the wireless terminal indicating that an external authentication and / or authorization process is being performed during the process, and
[0042] An external authentication and / or authorization process is performed between the wireless terminal and the external server.
[0043] The present disclosure relates to a wireless communication method used in a wireless terminal, the method comprising:
[0044] sending an indicator to a network entity, the indicator being associated with a capability to support at least one method of interacting with an external network to authenticate and / or authorize the external network for a packet data connection, and
[0045] A procedure is performed based on the indicator, wherein the procedure is associated with establishing a packet data network connection in the second network.
[0046] Various embodiments may preferably implement the following features:
[0047] Preferably, at least one method comprises:
[0048] Extensible Authentication Protocol,
[0049] Password Authentication Protocol, or
[0050] Challenge-Handshake Authentication Protocol.
[0051] Preferably, the process is associated with transferring a protocol data unit session of the wireless terminal from a first network to a second network as a packet data network connection, wherein the protocol data unit session is established with an external server using a first external authentication and / or authorization method.
[0052] Preferably, the first network is associated with a 5G system and the second network is associated with an Evolved Packet System.
[0053] Preferably, the second network supports the first external authentication and / or authorization method, and the indicator indicates that the wireless terminal supports the first external authentication and / or authorization method,
[0054] The indicator-based execution process includes:
[0055] receiving an indicator from a network entity, the indicator indicating that an external authentication and / or authorization procedure is being performed using a first external authentication and / or authorization method during the procedure, and
[0056] Perform external authentication and / or authorization procedures with network entities and external servers.
[0057] Preferably, executing the process based on the indicator includes:
[0058] receiving a cause value indicating a procedure failure from a network entity when at least one condition is satisfied,
[0059] Wherein, at least one condition includes at least one of the following:
[0060] the second network does not support the first external authentication and / or authorization method,
[0061] The indicator indicates that the wireless terminal does not support the first external authentication and / or authorization method, or
[0062] The access point name corresponding to the data network name of the protocol data unit session requires a second external authentication and / or authorization method that is different from the first external authentication and / or authorization method.
[0063] Preferably, the second network supports the Extensible Authentication Protocol, and the indicator indicates that the wireless terminal supports the Extensible Authentication Protocol,
[0064] The indicator-based execution process includes:
[0065] receiving an indicator from a network entity indicating that an external authentication and / or authorization procedure is being performed using the Extensible Authentication Protocol during the procedure, and
[0066] Perform external authentication and / or authorization procedures with network entities and external servers.
[0067] The present disclosure relates to a wireless communication method used in a network entity, the method comprising:
[0068] performing a process of transferring a protocol data unit session of the wireless terminal from a first network to a second network as a packet data network connection, and
[0069] When the indicator is not received, performing at least one step during the process,
[0070] The indicator is associated with a capability of supporting at least one method of interacting with an external network to perform authentication and / or authorization of the external network for a packet data connection.
[0071] Various embodiments may preferably implement the following features:
[0072] Preferably, at least one method comprises at least one of the following:
[0073] Extensible Authentication Protocol,
[0074] Password Authentication Protocol, or
[0075] Challenge-Handshake Authentication Protocol.
[0076] Preferably, the first network is associated with a 5G system and the second network is associated with an Evolved Packet System.
[0077] Preferably, at least one step comprises at least one of the following:
[0078] not allocating an EPS bearer identifier to a quality of service flow for a packet data unit session, or
[0079] A cause value indicating a failure of the procedure is sent to the wireless terminal.
[0080] The present disclosure relates to a network entity. The network entity includes:
[0081] a communication unit configured to receive an indicator from a wireless terminal, the indicator being associated with a capability to support at least one method of interacting with an external network for authenticating and / or authorizing the external network for a packet data connection, and
[0082] A processor is configured to perform a process based on the indicator, wherein the process is associated with establishing a packet data network connection in a second network.
[0083] Various embodiments may preferably implement the following features:
[0084] Preferably, the processor is further configured to execute any of the above wireless communication methods.
[0085] The present disclosure relates to a wireless terminal. The wireless terminal comprises:
[0086] a communication unit configured to send an indicator to a network entity, the indicator being associated with a capability to support at least one method of interacting with an external network for authentication and / or authorization of the external network for a packet data connection, and
[0087] A processor is configured to perform a process based on the indicator, wherein the process is associated with establishing a packet data network connection in a second network.
[0088] Various embodiments may preferably implement the following features:
[0089] Preferably, the processor is further configured to execute any of the above wireless communication methods.
[0090] The present disclosure relates to a network entity. The network entity includes:
[0091] a communication unit, and
[0092] Processor, configured as:
[0093] performing a process of transferring a protocol data unit session of the wireless terminal from a first network to a second network as a packet data network connection, and
[0094] When the communication unit does not receive the indicator, at least one step is performed during the process.
[0095] Various embodiments may preferably implement the following features:
[0096] Preferably, the processor is further configured to execute any of the above wireless communication methods.
[0097] The present disclosure relates to a computer program product, including a computer-readable program medium code stored therein, and when the computer-readable program medium code is executed by a processor, the processor executes a wireless communication method of any one of the above methods.
[0098] The exemplary embodiments disclosed herein are intended to provide features that will become apparent by reference to the following description in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example and not limitation, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications may be made to the disclosed embodiments without departing from the scope of this disclosure.
[0099] Therefore, the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. In addition, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be rearranged without departing from the scope of the present disclosure. Therefore, it will be understood by those of ordinary skill in the art that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present disclosure is not limited to the specific order or hierarchy presented. BRIEF DESCRIPTION OF THE DRAWINGS
[0100] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims.
[0101] Figure 1 A schematic diagram of a security process according to an embodiment of the present disclosure is shown.
[0102] Figure 2 A schematic diagram of a security process according to an embodiment of the present disclosure is shown.
[0103] Figure 3 A schematic diagram showing a network structure according to an embodiment of the present disclosure is shown.
[0104] Figure 4 A schematic diagram showing a process of processing a protocol data unit session into a packet data network connection according to an embodiment of the present disclosure is shown.
[0105] Figure 5 A schematic diagram showing a process of processing a protocol data unit session into a packet data network connection according to an embodiment of the present disclosure is shown.
[0106] Figure 6 A schematic diagram of an initial attachment process for establishing a PDN connection according to an embodiment of the present disclosure is shown.
[0107] Figure 7 A flow chart illustrating a process according to an embodiment of the present disclosure is shown.
[0108] Figure 8 A flow chart illustrating a process according to an embodiment of the present disclosure is shown.
[0109] Fig. 9 A flow chart illustrating a process according to an embodiment of the present disclosure is shown.
[0110] Fig.10 An example of a schematic diagram of a wireless terminal according to an embodiment of the present disclosure is shown.
[0111] Fig.11 An example of a schematic diagram of a wireless network node according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0112] Figure 1 The process between the UE and the external data network via the 5G network according to an embodiment of the present disclosure is shown.
[0113] As specified in 3rd Generation Partner Project (3GPP) TS 33.501, the EAP framework specified in Request For Comment (RFC) 3748 shall be used for authentication between the UE and the Data Network-AAA (DN-AAA) server in the external data network. In addition, the Session Management Function (SMF) will play the role of the EAP Authenticator. In non-roaming scenarios, the SMF will play the role of the EAP Authenticator. In the Local Break Out scenario, the Visitor SMF (V-SMF) of the visited network will play the role of the EAP Authenticator. The EAP Authenticator will rely on the external DN-AAA server to authenticate and authorize the request from the UE to establish a PDU session.
[0114] Between the UE and the SMF, the EAP messages will be sent in Session Management (SM) Non-Access Stratum (NAS) messages. As specified in 3GPP TS 23.502, at the Access and Mobility Management Function (AMF), the SM NAS messages are received over interface N1 and transmitted to the SMF over interface N11 using the Nsmf_PDUSession_CreateSMContext service operation or the Nsmf_PDUSession_Update SMContext service operation. The SMF, which plays the role of EAP authenticator, communicates with the external DN-AAA server via interfaces N4 and N6 via the User Plane Function (UPF).
[0115] The SMF invokes the Namf_Communication_N1N2MessageTransfer service operation to transmit the N1 NAS message containing the EAP message to the UE via the AMF.
[0116] Figure 2 A schematic diagram showing a security process between a UE and an external data network via a 3G / 4G network according to an embodiment of the present disclosure is shown.
[0117] Specifically, when the Gateway General Packet Radio Service (GPRS) Support Node (GGSN) receives a Create Packet Data Protocol (PDP) Context Request message for a given Access Point Name (APN), the GGSN will immediately send a Create PDP Context Response back to the Serving GPRS Support Node (SGSN). After the PPP link is established, the authentication phase may begin. During the authentication phase, the GGSN sends a RADIUS Access Request to the AAA server. The AAA server authenticates and authorizes the user. If the RADIUS server is also responsible for Internet Protocol (IP) address allocation, the AAA server should return the allocated IP address or IP Version 6 (IPv6) prefix (if the user has been authenticated) in the Access Accept message.
[0118] If the user is not authenticated, the GGSN will send a delete PDP context request to the SGSN.
[0119] Even if the GGSN is not involved in the user authentication (for example, for PPP, no authentication may be chosen), the GGSN may send a RADIUS Accounting Request Start message to the AAA server. The message contains parameters (e.g., a tuple including a user id and an IP address or an IPv6 prefix) that are used by the application server (e.g., a WAP gateway) to identify the user. The message also indicates to the AAA server that a user session has been started and the Quality of Service (QoS) parameters associated with the session.
[0120] If some external application requires RADIUS Accounting Request (Start) information before processing user packets, the selected APN (GGSN) can be configured so that the GGSN discards user data before receiving the Accounting Response (Start) from the AAA server. If no Accounting Response (Start) is received, the GGSN can delete the PDP context. The authentication and accounting servers can be configured separately for each APN.
[0121] When the GGSN receives the Delete PDP Context Request message and provides the previously sent RADIUS Accounting Request Start message, the GGSN will send a RADIUS Accounting Request Stop message to the AAA server indicating that the particular user session is terminated. The GGSN will immediately send a Delete PDP Context Response without waiting for the Accounting Response Stop message from the AAA server.
[0122] An Accounting Request On message and an Accounting Request Off message may be sent from the GGSN to the AAA server to ensure correct synchronization of session information in the GGSN and the AAA server.
[0123] The GGSN may send an Accounting Request Open message to the AAA server to indicate that a restart has occurred. The AAA server may then release the associated resources.
[0124] Before the scheduled restart, the GGSN may send an Accounting Request Close message to the AAA server, and then the AAA server may release the associated resources.
[0125] If an Access-Challenge is sent to the GGSN when using the PPP PDP type, the GGSN shall process it through PPP CHAP, provided that PPP CHAP is the selected authentication protocol. In RFC 2865, if CHAP authentication is not selected, authentication will fail.
[0126] Figure 3 A schematic diagram showing a network structure according to an embodiment of the present disclosure is shown. Figure 3 The network architecture shown is able to interwork with EPC, i.e., perform mobility procedures between 5GC and EPC / E-UTRAN.
[0127] During the E-UTRAN initial attach procedure, a UE supporting simultaneous 5GC NAS and EPC NAS shall indicate in the UE network capabilities that it supports 5G NAS as described in clause 5.11.3 of 3GPP TS 23.401.
[0128] During registration to 5GC, a UE supporting both 5GC NAS and EPC NAS shall indicate that it supports EPC NAS. This indication can be used to prioritize PGW-C+SMF (PDN Gateway Control Plane Function plus SMF) for UE supporting both EPC NAS and 5GC NAS.
[0129] A network that supports interworking with the EPC may support an interworking procedure using interface N26 or an interworking procedure not using interface N26. The interworking procedure using N26 supports providing IP address continuity to the UE regarding inter-system mobility, which supports both 5GC NAS and EPC NAS and operates in single registration mode. A network that supports an interworking procedure not using N26 will support a procedure to provide IP address continuity for inter-system mobility to UEs operating in both single registration mode and dual registration mode. In such a network, during the initial registration in the 5GC, the AMF will provide the UE with an indication that interworking without N26 is supported, or the MME may optionally provide an indication that the attachment procedure in the EPC as defined in TS 23.401 supports interworking without N26.
[0130] If the network does not support interworking with EPC, the network shall not indicate to the UE that "interworking without N26" is supported.
[0131] For intercommunication without using N26 interface:
[0132] -If the PDU session supports interworking, when SMF registers to HSS+UDM, PGW-C+SMF stores the PGW-C+SMF FQDN (Fully Qualified Domain Name) to SMF context in the Home Subscriber Server + Unified Data Management (HSS+UDM).
[0133] -For APN, HSS+UDM will select one from the stored PGW-C+SMF FQDN based on the operator's policy.
[0134] For intercommunication using N26 interface:
[0135] - For DNN, the AMF determines the PDU Session associated with the 3GPP access only in one PGW-C+SMF that supports EPS interworking via the EBI allocation procedure as described in clause 4.11.1.4.1 of 3GPP TS 23.502.
[0136] - If the network supports EPS interworking with non-3GPP access connected to 5GC, the AMF serving the 3GPP access informs the UDM to store the association between the DNN and the PGW-C+SMF FQDN supporting EPS interworking as an inter-system continuity context to avoid the MME receiving inconsistent PGW-C+SMF FQDN from the AMF and HSS+UDM.
[0137] - If the PGW-C+SMF and DNN association changes due to the AMF selecting another PGW-C+SMF for EPS interworking with the same DNN, the AMF updates the inter-system continuity context.
[0138] - If the PGW-C+SMF FQDN and associated APN exist in the inter-system continuity context, the HSS+UDM provides the PGW-C+SMF FQDN and associated APN to the MME.
[0139] Embodiment 1:
[0140] Figure 4 The process of processing a PDU session as a PDN connection according to an embodiment of the present disclosure is shown. In this embodiment, the UE has registered with the 5GC and established a PDU session that has been authenticated and authorized by an external authentication server (e.g., an EAP server). Next, the UE moves to an area with only eNB coverage, so a handover to a shared EPS is performed. In this article, it is assumed that the mobility from 5GS to EPS is performed using the N26 interface.
[0141] In step 1, the UE registers with the 5GS. Alternatively or in addition, the UE may provide an indicator of external authentication and authorization capabilities in the EPS to the network (e.g. AMF).
[0142] In step 2a, the UE sends a NAS message to the AMF, wherein the NAS message includes at least one of a PDU session establishment request or an indicator of an external authentication and authorization capability in the EPS. The capability is associated with a method for supporting packet data connection authentication / authorization signaling for interacting with an external DN to transmit the external DN. In one embodiment, the method includes:
[0143] -Extensible Authentication Protocol (EAP).
[0144] The AMF selects an appropriate SMF+PGW-C node that can support the external authentication and authorization methods in EPS indicated by the UE.
[0145] In step 2b, a PDU session is established with external authentication and authorization.
[0146] In step 3, based on the indicator of external authentication and authorization capabilities in EPS provided by the UE, the SMF+PGW-C determines whether the EPS bearer ID should be assigned to the QoS flow in the PDU session authenticated and authorized by the DN-AAA server. If the external authentication and authorization method used by the PDU session in EPS is not supported or allowed, the SMF+PGW-C determines not to allocate an EBI. Otherwise, the SMF+PGW-C allocates an EBI to the PDU session. In this embodiment, the external authentication and authorization capability indicator in EPS provided by the UE indicates that the UE supports the external authentication and authorization method used by the PDU session in EPS.
[0147] In step 4, SMF+PGW-C invokes Namf_Communication_EBIAssignment request to AMF. If AMF successfully allocates EBI, AMF responds with the allocated EBI. Otherwise, AMF responds with the reason indicating the failure of EBI allocation.
[0148] In step 5, a switching process from 5GS to EPS based on the N26 interface is performed.
[0149] In steps 6 to 10, after transferring the PDU session to the EPS as a PDN connection, the DN-AAA server may initiate an EAP re-authentication procedure to the UE.
[0150] Embodiment 2:
[0151] Figure 5 The process of processing a PDU session as a PDN connection according to an embodiment of the present disclosure is shown. In this embodiment, the UE has registered with the 5GC and established a PDU session that has been authenticated and authorized by an external authentication server (e.g., an EAP server). Then, the UE moves to an area with only eNB coverage and performs a handover to a shared EPS. In this article, it is assumed that the mobility from 5GS to EPS is not performed using the N26 interface.
[0152] In steps 1 to 5, the UE registers in 5GS and establishes a PDU session, and the external DN has authenticated and authorized the PDU session based on EAP. The UE initiates a TAU request to move to EPS. The MME determines that the old node is the AMF based on the UE's GUTI mapped from the 5G-GUTI, and the MME is configured to support 5GS-EPS interworking without the N26 procedure. The MME sends a TAU reject (message) to the UE, and the UE initiates an initial attachment procedure to the EPS.
[0153] In step 6, if the UE wants to transfer the PDN connection to the EPS and keep the same IP address / prefix, the UE performs the UE Requested PDN Connection procedure as specified and sets the request type to "Handover" in step 1 of the procedure, where the amendment is recorded in clause 4.11.2.4.2. The UE provides the APN and the PDU Session ID corresponding to the PDU session that the UE wants to transfer to the EPS. The UE may also provide an indicator of external authentication and authorization capabilities in the EPS. The capability refers to the method supported for interacting with the external DN to transmit signaling for packet data connection authentication / authorization by the external DN, including but not limited to:
[0154] -Extensible Authentication Protocol (EAP).
[0155] In addition, the UE may include an identifier of the external EAP authentication in the PDN connection request.
[0156] Scenario A:
[0157] if:
[0158] The PDU session ID corresponding to the PDU session is established in 5GS through EAP-based external authentication and authorization;
[0159] EPS supports or allows external authentication and authorization based on EAP; and
[0160] The UE indicates support for external authentication and authorization based on EAP.
[0161] Then SMF+PGW-C accepts the PDN connection request.
[0162] In step 8 to step 12 of case A, if the SMF+PGW-C receives an identifier for external EAP authentication in the PDN connection request, the SMF+PGW-C will proceed with external authentication and authorization between the UE and the DN-AAA server. The UE receives an indicator in the EAP authentication request and / or the PDN connection response. The indicator is configured to indicate to the UE that external authentication and authorization for PDN connection establishment is being performed / proceding and / or is required / required. In this case, the UE does not consider the PDN connection establishment to be complete.
[0163] In step 513a and step 514a, the UE and the network perform further procedures to complete the external authentication and authorization procedures. When receiving EAP-Success, the UE considers that the PDN connection is successfully established.
[0164] Case B:
[0165] The PDU Session ID corresponding to the PDU Session is established in 5GS through external authentication and authorization based on EAP, but:
[0166] a) EPS supports or allows external authentication and authorization based on EAP;
[0167] b) The UE does not indicate support for external authentication and authorization based on EAP;
[0168] c) the UE does not provide an indicator regarding external authentication and authorization capabilities in the EPS; or
[0169] d) The mapping of DNN to APN requires different external authentication methods in EPS.
[0170] SMF+PGW-C rejects the PDN connection request (i.e., steps 8 to 10 in case B). In one embodiment, SMF+PGW-C rejects the PDN connection request, and the cause value indicates:
[0171] 1) For a) or b) or c), requiring external authentication is not supported, or
[0172] 2), for d), external authentication is required.
[0173] Embodiment three:
[0174] In this embodiment, during the establishment of the PDN connection, the EPS network supports multiple authentication / authorization methods (such as EAP-based authentication, PAP authentication, and CHAP authentication, etc.) of the external authentication server. The initial attachment process for establishing the PDN connection is as follows: Figure 6 shown.
[0175] In step 1a and step 1b, the UE initiates the attach procedure and includes its external authentication and authorization capabilities for PDN connection establishment in the attach request. This capability refers to the method of supporting the signaling for interacting with the external DN to transmit packet data connection authentication / authorization by the external DN, including but not limited to:
[0176] Extensible Authentication Protocol (EAP).
[0177] The UE may also include an identity for external authentication in the attach request.
[0178] In steps 2 to 4, authentication and NAS security establishment are performed to activate integrity protection and NAS encryption.
[0179] In steps 5 to 7, the MME determines to establish a PDN connection that needs to be authenticated and authorized by an external authentication server based on EAP, and selects an appropriate SGW to send a create session request to the Serving Gateway (SGW). The SGW selects an appropriate PDN Gateway (PGW) and sends a corresponding create session request to the PGW. If provided by the UE in steps 1a and 1b, the PGW initiates an authentication request to the external authentication server and includes an identifier for external authentication.
[0180] In steps 8 to 11, the external authentication server sends an authentication request to the PGW via a Diameter message including an EAP-Request. The EAP-Request message is transmitted from the PGW to the MME via a GPRS Tunneling Protocol Control (GTP-C) message together with an indicator. The indicator is configured to indicate to the UE that external authentication and authorization for PDN connection establishment is currently being performed / in progress and / or needs to be performed / required. The UE receives the EAP request and indicator in the NAS message sent by the MME. The UE does not consider the PDN connection establishment to be completed.
[0181] In step 12 to step 27, the UE and the network perform procedures to complete the external authentication and authorization procedures. When the UE receives the EAP-Success (message), it is considered that the PDN connection is successfully established.
[0182] Figure 7 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. Figure 7 The process shown may be used in a network entity (e.g., PGW-C+SMF and / or MME and / or AMF) and comprises the following steps:
[0183] Step 701: Receive an indicator from a wireless terminal, the indicator being associated with a capability to support at least one method of interacting with an external network to authenticate and / or authorize the external network for a packet data connection.
[0184] Step 702: Perform a process based on the indicator, wherein the process is associated with establishing a packet data network connection in the second network.
[0185] exist Figure 7 In the present disclosure, a wireless terminal (e.g., a UE) may provide an indicator to a network entity. The indicator is associated with a capability of supporting at least one method of interacting with an external network (e.g., an external DN, a DN-AAA server, or an external authentication server) to authenticate / authorize a packet data connection (e.g., a PDU session or a PDN connection) to an external network. Based on the indicator, the network entity performs a process associated with establishing a PDN connection in a second network (e.g., EPS). In the present disclosure, authentication / authorization may be equivalent to authentication and / or authorization. In an embodiment, the capability is associated with the wireless terminal and / or the second network. That is, the indicator may indicate at least one of the following:
[0186] the wireless terminal supports at least one method of interacting with an external network to perform authentication / authorization of the external network for a packet data connection,
[0187] A capability to support at least one method of interacting with an external network to perform authentication / authorization of the external network for a packet data connection in the second network, or
[0188] the wireless terminal supports at least one method of interacting with an external network to perform authentication / authorization of the external network for a packet data connection in the second network,
[0189] In one embodiment, at least one method includes at least one of the following:
[0190] EAP,
[0191] PAP, or
[0192] CHAP.
[0193] In one embodiment, the process is associated with connecting a wireless terminal's PDU session as a PDN connection (eg, Figure 4 or Figure 5 The process shown in FIG. 1 is associated with transferring from a first network (e.g., 5GS) to a second network. In this embodiment, the PDU session is established with an external server (e.g., an external network) by using a first external authentication / authorization method. For example, the first external authentication / authorization method is EAP, and is not limited herein.
[0194] In one embodiment, the first network is associated with 5GS and the second network is associated with EPS.
[0195] In one embodiment, the process performed by the network entity based on the indicator includes:
[0196] A determination is made based on the indicator whether to allocate an EBI for the QoS flow of the PDU session.
[0197] In one embodiment, when the indicator indicates that the wireless terminal supports the first external authentication / authorization method, the network entity may (determine) allocate an EBI for the QoS flow of the PDU session.
[0198] In one embodiment, the network entity may (determine) not to allocate an EBI for the QoS flow of the PDU session when at least one condition is met. The at least one condition includes at least one of the following:
[0199] 1) the second network does not support the first external authentication and / or authorization method,
[0200] 2) an indicator indicating that the wireless terminal does not support the first external authentication and / or authorization method, or
[0201] 3) The APN of the DNN corresponding to the protocol data unit session requires a second external authentication and / or authorization method that is different from the first external authentication and / or authorization method.
[0202] It should be noted that, in condition 1), the first external authentication / authorization method may refer to any external authentication / authorization method supported by the first network but not supported by the second network. Similarly, in condition 2), the first external authentication / authorization method may refer to any external authentication / authorization method supported by the first network but not supported by the wireless terminal. In all conditions 1), 2) and 3), the first external authentication / authorization method may be an EAP-based external authentication / authorization method, and is not limited in this document.
[0203] In one embodiment, the second network supports a first external authentication and / or authorization method, and the indicator indicates that the wireless terminal supports the first external authentication and / or authorization method. In this embodiment, the process performed by the network entity based on the indicator includes:
[0204] performing (e.g., initiating, starting, beginning) an external authentication / authorization process between the wireless terminal and the external server using a first external authentication / authorization method,
[0205] sending an indicator to the wireless terminal indicating that an external authentication / authorization process is being performed during the process, and
[0206] An external authentication and / or authorization process is performed (eg, completed) between the wireless terminal and the external server.
[0207] In one embodiment, the process performed by the network entity based on the indicator includes:
[0208] When at least one condition is met, a cause value indicating a process failure is sent to the wireless terminal (e.g., Figure 5 In this embodiment, at least one condition includes at least one of the following:
[0209] 1) the second network does not support the first external authentication and / or authorization method,
[0210] 2) an indicator indicating that the wireless terminal does not support the first external authentication and / or authorization method, or
[0211] 3) The access point name corresponding to the data network name of the protocol data unit session requires a second external authentication and / or authorization method that is different from the first external authentication and / or authorization method.
[0212] It should be noted that, in condition 1), the first external authentication / authorization method may refer to any external authentication / authorization method supported by the first network but not supported by the second network. Similarly, in condition 2), the first external authentication / authorization method may refer to any external authentication / authorization method supported by the first network but not supported by the wireless terminal. In all conditions 1), 2) and 3), the first external authentication / authorization method may be an EAP-based external authentication / authorization method, and is not limited in this document.
[0213] In one embodiment, the second network supports EAP, and the indicator indicates that the wireless terminal supports EAP. In this embodiment, the process performed by the network entity based on the indicator includes:
[0214] Performing an external authentication and / or authorization process between the wireless terminal and an external server using the Extensible Authentication Protocol,
[0215] sending an indicator to the wireless terminal indicating that an external authentication and / or authorization process is being performed during the process, and
[0216] Perform external authentication and / or authorization procedures (e.g. Figure 6 ).
[0217] Figure 8 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. Figure 8 The process shown may be used for a wireless terminal (e.g., UE) and includes the following steps:
[0218] Step 801: Send an indicator to a network entity, the indicator being associated with a capability of supporting at least one method of interacting with an external network to perform authentication and / or authorization of the external network for a packet data connection.
[0219] Step 802: Perform a process based on the indicator, wherein the process is associated with establishing a packet data network connection in the second network.
[0220] exist Figure 8 In the embodiment, the wireless terminal sends (e.g., provides) an indicator to a network entity (e.g., PGW-C+SMF and / or AMF and / or MME), wherein the indicator is associated with a capability of supporting at least one method of interacting with an external network (e.g., an external DN, DN-AAA, or an external authentication server) to authenticate / authorize the external network for a packet data connection. Based on the indicator, the network entity performs a process associated with establishing a PDN connection in a second network (e.g., EPS). In an embodiment, the capability is associated with the wireless terminal and / or the second network. That is, the indicator may indicate at least one of the following:
[0221] the wireless terminal supports at least one method of interacting with an external network to perform authentication / authorization of the external network for a packet data connection,
[0222] A capability to support at least one method of interacting with an external network to perform authentication / authorization of the external network for a packet data connection in the second network, or
[0223] The wireless terminal supports the capability of interacting with the external network to perform at least one method of authentication / authorization of the external network for the packet data connection in the second network.
[0224] In one embodiment, at least one method includes:
[0225] EAP,
[0226] PAP, or
[0227] CHAP.
[0228] In one embodiment, the process is associated with transferring a PDU session of the wireless terminal as a PDN connection from a first network (e.g., 5GS) to a second network (e.g., EPS). In this embodiment, the PDU session is established with an external server (e.g., an external network) using a first external authentication and / or authorization method.
[0229] In one embodiment (e.g. Figure 4 or Figure 5 ), the second network supports the first external authentication / authorization method, and the indicator indicates that the wireless terminal supports the first external authentication and / or authorization method. Under this condition, the process performed by the wireless terminal based on the indicator includes:
[0230] receiving an indicator from the network entity indicating that an external authentication / authorization procedure is being performed using a first external authentication / authorization method during the procedure, and
[0231] An external authentication / authorization process is performed with network entities and external servers (eg, external networks).
[0232] In one embodiment, the process performed by the wireless terminal based on the indicator includes receiving a cause value indicating a process failure from a network entity when at least one condition is met. The at least one condition may include at least one of the following:
[0233] 1) the first external authentication and / or authorization method is not supported in the second network,
[0234] 2) an indicator indicating that the wireless terminal does not support the first external authentication and / or authorization method, or
[0235] 3) The access point name corresponding to the data network name of the protocol data unit session requires a second external authentication and / or authorization method that is different from the first external authentication and / or authorization method.
[0236] It should be noted that, in condition 1), the first external authentication / authorization method may refer to any external authentication / authorization method supported by the first network but not supported by the second network. Similarly, in condition 2), the first external authentication / authorization method may refer to any external authentication / authorization method supported by the first network but not supported by the wireless terminal. In all conditions 1), 2) and 3), the first external authentication / authorization method may be an EAP-based external authentication / authorization method, and is not limited in this document.
[0237] In one embodiment (e.g. Figure 6 ), the second network supports EAP, and the indicator indicates that the wireless terminal supports EAP. Under this condition, the process performed by the wireless terminal based on the indicator includes:
[0238] receiving an indicator from the network entity indicating that an external authentication / authorization procedure is being performed using a first external authentication / authorization method during the procedure, and
[0239] An external authentication / authorization process is performed (eg, completed) with the network entity and an external server (eg, an external network).
[0240] Fig. 9 A flow chart illustrating a process according to an embodiment of the present disclosure is shown. Fig. 9 The process shown may be used in a network entity (e.g., PGW-C+SMF and / or AMF and / or MME) and comprises the following steps:
[0241] Step 901: Execute a process of transferring a protocol data unit session of a wireless terminal from a first network to a second network as a packet data network connection.
[0242] Step 902: When no indicator is received, performing at least one step during the process.
[0243] exist Fig. 9 In the process, the network entity performs a process of transferring a PDU session of a wireless terminal (e.g., UE) from a first network (e.g., 5GS) to a second network (e.g., EPS) as a PDN connection. In this embodiment, the network entity does not receive an indicator from the wireless terminal, etc. The indicator indicates the ability to support at least one method of interacting with an external network (e.g., an external DN, DN-AAA, or an external authentication server) to authenticate / authorize the packet data connection to the external network. In such a case, the network entity performs at least one step in the process.
[0244] In an embodiment, the capability is associated with the wireless terminal and / or the second network. That is, the indicator may indicate at least one of the following:
[0245] the wireless terminal supports at least one method of interacting with an external network to perform authentication / authorization of the external network for a packet data connection,
[0246] A capability to support at least one method of interacting with an external network to perform authentication / authorization of the external network for a packet data connection in the second network, or
[0247] The wireless terminal supports the ability to interact with an external network to perform at least one method of authentication / authorization of the external network for a packet data connection in a second network. In one embodiment, the at least one method includes at least one of the following:
[0248] EAP,
[0249] PAP, or
[0250] CHAP.
[0251] In one embodiment, the first network is associated with 5GS and the second network is associated with EPS.
[0252] In one embodiment, at least one step includes:
[0253] not allocating an Evolved Packet System Bearer Identifier to a Quality of Service flow for a packet data unit session, and / or
[0254] A cause value indicating a failure of the procedure is sent to the wireless terminal.
[0255] Fig.10A schematic diagram of a wireless terminal 100 according to an embodiment of the present disclosure is provided. The wireless terminal 100 may be a user equipment (UE), a mobile phone, a laptop, a tablet computer, an e-book, or a portable computer system, and is not limited herein. The wireless terminal 100 may include a processor 1000 such as a microprocessor or an application specific integrated circuit (ASIC), a storage unit 1010, and a communication unit 1020. The storage unit 1010 may be any data storage device that stores a program code 1012 accessed and executed by the processor 1000. Embodiments of the storage unit 1012 include, but are not limited to, a subscriber identity module (SIM), a read-only memory (ROM), a flash memory, a random access memory (RAM), a hard disk, and an optical data storage device. The communication unit 1020 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 1000. In one embodiment, the communication unit 1020 communicates with the user via a communication device. Fig.10 At least one antenna 1022 is shown for transmitting and receiving signals.
[0256] In one embodiment, the storage unit 1010 and the program code 1012 may be omitted, and the processor 1000 may include a storage unit storing the program code.
[0257] The processor 1000 may implement any one of the steps of the exemplary embodiments on the wireless terminal 100 , for example, by executing the program code 1012 .
[0258] The communication unit 1020 may be a transceiver. Alternatively or in addition, the communication unit 1020 may be combined with a transmitting unit and a receiving unit configured to respectively transmit signals to a wireless communication node and receive signals from a wireless network node (eg, a base station).
[0259] Fig.11A schematic diagram of a radio network node 110 according to an embodiment of the present disclosure is provided. The radio network node 110 may be a satellite, a base station (BS), a network entity, a mobility management entity (MME), a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a radio access network (RAN), a next generation RAN (NG-RAN), a data network, a core network or a radio network controller (RNC), and is not limited herein. In addition, the radio network node 110 may include (execute) at least one network function, such as an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), an application function (AF), etc. It should be noted that the radio network node 110 may include Figure 3 The network entities and / or network functions shown (e.g., performing any of their functions). For example, the radio network node 110 may be a PGW-C+SMF. The radio network node 110 may include a processor 1100 such as a microprocessor or an ASIC, a storage unit 1110, and a communication unit 1120. The storage unit 1110 may be any data storage device that stores program code 1112 accessed and executed by the processor 1100. Examples of the storage unit 1112 include, but are not limited to, a SIM, a ROM, a flash memory, a RAM, a hard disk, and an optical data storage device. The communication unit 1120 may be a transceiver and is used to send and receive signals (e.g., messages or packets) according to the processing results of the processor 1100. In one example, the communication unit 1120 communicates via Fig.11 At least one antenna 1122 is shown for transmitting and receiving signals.
[0260] In one embodiment, the storage unit 1110 and the program code 1112 may be omitted. The processor 1100 may include a storage unit storing program code.
[0261] The processor 1100 may implement any steps described in the exemplary embodiments on the radio network node 110 , for example, by executing the program code 1112 .
[0262] The communication unit 1120 may be a transceiver. Alternatively or additionally, the communication unit 1120 may be configured in combination as a transmitting unit and a receiving unit that transmit and receive signals to and from a wireless terminal (eg, a user equipment), respectively.
[0263] Although various embodiments of the present disclosure have been described above, it should be understood that they are presented only by way of example, and not by way of limitation. Similarly, various figures may depict exemplary architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the exemplary features and functions of the present disclosure. However, these technicians will understand that the present disclosure is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as will be understood by those of ordinary skill in the art, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the exemplary embodiments described above.
[0264] It should also be understood that any reference to an element by names such as "first," "second," etc., as used herein, does not generally limit the number or order of these elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, reference to a first element and a second element does not mean that only two elements can be used, or that the first element must precede the second element in some manner.
[0265] In addition, those skilled in the art will appreciate that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0266] The skilled person will further understand that any of the various illustrative logical blocks, units, processors, components, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of both), firmware, various forms of programs or design codes including instructions (which, for convenience, may be referred to herein as "software" or "software units"), or any combination of these technologies.
[0267] In order to clearly illustrate this interchangeability of hardware, firmware and software, it has been generally described above according to the functions of various illustrative components, blocks, units, circuits and steps. Whether such functions are implemented as hardware, firmware or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the entire system. The technician can implement the described functions in various ways for each specific application, but this implementation decision will not lead to deviation from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc. can be configured to perform one or more functions described herein. The terms "configured to" or "configured for" used herein with respect to a specific operation or function refer to a processor, device, component, circuit, structure, machine, unit, etc., which is physically constructed, programmed and / or arranged to perform a specific operation or function.
[0268] In addition, the technician will understand that the various illustrative logic blocks, units, devices, components and circuits described herein can be implemented in an integrated circuit (IC) or performed by an IC, which may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device or any combination thereof. The logic blocks, units and circuits may also include antennas and / or transceivers to communicate with various components within a network or device. The general-purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other suitable configuration for performing the functions described herein. If implemented in software, these functions may be stored in a computer-readable medium as one or more instructions or codes. Therefore, the steps of the method or algorithm disclosed herein may be implemented as software stored in a computer-readable medium.
[0269] Computer-readable media include computer storage media and communication media, including any medium capable of transferring a computer program or code from one place to another. Storage media can be any available medium that a computer can access. As an example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and can be accessed by a computer.
[0270] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various units are described as discrete units; however, it is obvious to those of ordinary skill in the art that two or more units can be combined to form a single unit that performs the associated functions according to the embodiments of the present disclosure.
[0271] In addition, in the embodiments of the present disclosure, a memory or other storage device and a communication component may be used. It should be understood that, for the sake of clarity, the above description has described the embodiments of the present disclosure with reference to different functional units and processors. However, it is apparent that any suitable functional distribution may be used between different functional units, processing logic elements or domains without departing from the present disclosure. For example, a function illustrated as being performed by a separate processing logic element or controller may be performed by the same processing logic element or controller. Therefore, a reference to a specific functional unit is merely a reference to a suitable component for providing the described function, rather than indicating a strict logical or physical structure or organization.
[0272] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be consistent with the broadest scope consistent with the novel features and principles disclosed herein, as described in the following claims.
Claims
1. A wireless communication method used in a network entity, the method comprising: receiving an indicator from a wireless terminal registered in a first network and having established a protocol data unit (PDU) session in the first network, the indicator being associated with a capability to support at least one method of interacting with an external network for authentication and / or authorization of the external network for a packet data connection, Sending an Extensible Authentication Protocol (EAP) authentication request to the wireless terminal, and performing a process based on the EAP authentication request, wherein the process is associated with establishing a packet data network connection in the second network, The first network is associated with a 5G system and the second network is associated with an evolved packet system.
2. The wireless communication method according to claim 1, wherein: The at least one method comprises at least one of the following: Extensible Authentication Protocol EAP.
3. The wireless communication method according to claim 1, wherein: The first network is associated with a 5G system and the second network is associated with an evolved packet system.
4. The wireless communication method according to claim 1, wherein: The indicator is received in a create session request message.
5. A wireless communication method used in a wireless terminal, the method comprising: Before sending the indicator to the network entity, registering in a first network and establishing a protocol data unit (PDU) session in the first network, sending an indicator to a network entity, the indicator being associated with a capability to support at least one method of interacting with an external network for authentication and / or authorization of the external network for a packet data connection, receiving an Extensible Authentication Protocol (EAP) authentication request from the network entity, and performing a process based on the EAP authentication request, wherein the process is associated with establishing a packet data network connection in the second network, The first network is associated with a 5G system and the second network is associated with an evolved packet system.
6. The wireless communication method according to claim 5, wherein: The at least one method comprises: Extensible Authentication Protocol EAP.
7. The wireless communication method according to claim 5, wherein: The indicator is sent in an Attach Request message or a PDN Connection Request message.
8. A network entity, comprising a processor and a storage unit, wherein the processor is configured to read a program code from the storage unit and execute: receiving an indicator from a wireless terminal registered in a first network and having established a protocol data unit (PDU) session in the first network, the indicator being associated with a capability to support at least one method of interacting with an external network for authentication and / or authorization of the external network for a packet data connection, Sending an Extensible Authentication Protocol (EAP) authentication request to the wireless terminal, and Based on the EAP authentication request execution process, wherein: The process is associated with establishing a packet data network connection in a second network, The first network is associated with a 5G system and the second network is associated with an evolved packet system.
9. The network entity according to claim 8, wherein: The at least one method comprises at least one of the following: Extensible Authentication Protocol EAP.
10. The network entity according to claim 8, wherein: The first network is associated with a 5G system and the second network is associated with an evolved packet system.
11. The network entity of claim 8, wherein the indicator is received in a create session request message.
12. A wireless terminal comprising a processor and a storage unit, wherein the processor is configured to read a program code from the storage unit and execute: sending an indicator to a network entity, the indicator being associated with a capability to support at least one method of interacting with an external network for authentication and / or authorization of the external network for a packet data connection, receiving an Extensible Authentication Protocol (EAP) authentication request from the network entity, registering in a first network and establishing a PDU session in the first network before sending the indicator to the network entity, and Based on the EAP authentication request execution process, wherein: The process is associated with establishing a packet data network connection in a second network, The first network is associated with a 5G system and the second network is associated with an evolved packet system.
13. The wireless terminal according to claim 12, wherein: The at least one method comprises: Extensible Authentication Protocol EAP.
14. The wireless terminal according to claim 12, wherein: The indicator is sent in an Attach Request message or a PDN Connection Request message.
