Determining the Authentication Type

By deriving authentication methods from the UE's NAI and not relying solely on SUPI, the authentication process for non-5G capable UEs is modified to prevent registration failures, enabling successful 5G network access via non-3GPP networks.

JP7594031B2Active Publication Date: 2024-12-03LENOVO (SINGAPORE) PTE LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2022574681
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-06-03
Publication Date
2024-12-03
Estimated Expiration
2040-06-03

AI Technical Summary

Technical Problem

Special types of UEs that do not support 5G NAS protocols over non-3GPP access networks face registration failures due to the current method of selecting authentication methods based solely on the UE's SUPI, which may force the use of unsupported authentication methods like 5G-AKA.

Method used

The proposed solution involves modifying the authentication process by using the NAI provided by the UE to derive or indicate the appropriate authentication method, such as EAP-AKA', and ensuring that the UDM selects the correct authentication method based on the UE's capabilities, rather than relying solely on SUPI.

Benefits of technology

This approach allows non-5G capable UEs to successfully register with a 5G network via non-3GPP access by selecting the appropriate authentication method, preventing registration failures and ensuring seamless connectivity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007594031000001
    Figure 0007594031000001
  • Figure 0007594031000002
    Figure 0007594031000002
  • Figure 0007594031000003
    Figure 0007594031000003
Patent Text Reader

Abstract

[0003] Apparatuses, methods, and systems for selecting an authentication type within a 5G network are disclosed. One apparatus 600 includes a processor 605 and a network interface 640 that receives 805 a first message requesting registration of a remote unit with a mobile communications network, where the remote unit is connected to a non-3GPP access network and the remote unit does not support the NAS protocol. A processor 650 determines 810 an authentication request type for the remote unit, where the authentication request type is not based on the NAS protocol. The processor 605 creates 815 a NAS registration message on behalf of the remote unit and sends 820 a second message to an access management function within the mobile communications network, where the second message includes the NAS registration message and the determined authentication request type.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The subject matter disclosed herein generally relates to determining an authentication type for a remote unit operating in a non-3GPP access network. [Background technology]

[0002] The following abbreviations and acronyms are defined herein, at least some of which will be referred to within the description that follows.

[0003] 3rd Generation Partnership Project ("3GPP"), 5th Generation Core Network ("5GC"), Access and Mobility Management Function ("AMF"), Access Point Name ("APN"), Access Stratum ("AS"), Access Network Information ("ANI"), Application Programming Interface ("API"), Authentication Server Function ("AUSF"), Data Network Name ("DNN"), Downlink ("DL"), Enhanced Mobile Broadband ("eMBB"), Evolved Node B ("eNB"), Evolved Packet Core ("EPC"), Evolved UMTS Terrestrial Radio Access Network ("E-UTRAN"), Home Subscriber Server ("HSS"), International Mobile Subscriber Identity ("IMSI"), IP Multimedia Subsystem ("IMS", aka "IP Multimedia Core Network Subsystem"), Internet Protocol ("IP"), Long Term Evolution ("LTE"), LTE Advanced ("LTE-A"), Medium Access Control ("MAC"), Mobile Country Code ("MCC"), Mobile Network Code ("MNC"), Mobile Network Operator ("MNO"), Mobility Management Entity ("MME"), Non-Access Stratum ("NAS"), Narrowband ("NB"), Network Function ("NF"), Network Access Identifier ("NAI"), Next Generation (e.g., 5G) Node B ("gNB"), Next Generation Application Protocol ("NGAP"), Next Generation Radio Access Network ("NG-RAN"), New Radio ("NR"), Non-5G capable over WLAN ("N5CW"),"Non-5G-capable-over-WLAN"), Policy Control Function ("PCF"), Packet Data Network ("PDN"), Packet Data Unit ("PDU"), PDN Gateway ("PGW"), Public Land Mobile Network ("PLMN"), Quality of Service ("QoS"), Radio Access Network ("RAN"), Radio Access Technology ("RAT"), Radio Resource Control ("RRC"), Receive ("Rx"), Security Mode Control ("SMC"), Single Network Slice Selection Assistance Information ("S-NSSAI"), Serving Gateway ("SGW"), Session Management Function ("SMF"), Subscription Concealment Identifier ("SUCI"), Subscription Persistent Identifier ("SUPI"), Transmit Control Protocol ("TCP"), Transmission ("Tx"), Trusted Non-3GPP Access Network ("TNAN"), Trusted Non-3GPP Access Point ("TNAP"), Trusted Non-3GPP Gateway Function ("TNGF"), Unified Data Management ("UDM"), User Entity / Equipment (Mobile Terminal) ("UE"), Uplink ("UL"), User Plane ("UP"), Universal Mobile Telecommunications System ("UMTS"), User Datagram Protocol ("UDP"), User Location Information ("ULI"), Wireless Local Area Network ("WLAN"), and Worldwide Interoperability for Microwave Access ("WiMAX").

[0004] In certain embodiments, a UE may access a 5G Core ("5GC") network via a gateway function in a trusted non-3GPP access network ("TNAN"). However, a special type of UE cannot support 5G NAS protocols over non-3GPP access. Summary of the Invention [Means for solving the problem]

[0005] One method of a first network function, e.g., AMF, for selecting an authentication type in a 5G network includes receiving a registration request message from a remote unit (i.e., UE) and receiving subscription search information, where the registration request message includes an external subscriber identifier of the UE, and the subscription search information is different from the UE identifier. The method includes sending a first request for subscription data search to a network function in the mobile communication network using the subscription search information, and receiving a response message from the network function including the UE subscription data, where the subscription search information indicates that the subscription data is stored in a subscription owner external to the mobile communication network.

[0006] One method of a second network function, e.g., TWIF, for selecting an authentication type in a 5G network includes receiving a registration request message from a remote unit (i.e., UE) and receiving subscription search information, where the registration request message includes an external subscriber identifier of the UE, and the subscription search information is different from the UE identifier. The method includes sending a first request for subscription data search to a network function in the mobile communication network using the subscription search information, and receiving a response message from the network function including the UE subscription data, where the subscription search information indicates that the subscription data is stored in a subscription owner external to the mobile communication network.

[0007] One method of a third network function, e.g., a UDM, for selecting an authentication type in a 5G network includes receiving a first request from an AUSF in a mobile communications network to provide authentication data to a remote unit, the request indicating an authentication request type. The third method includes selecting a first authentication method using the authentication request type and subscription data of the remote unit, and responding to the first request by transmitting an authentication vector, the response also indicating the first authentication method.

[0008] A more detailed description of the embodiments briefly described above will now be given with reference to specific embodiments illustrated in the accompanying drawings, in which: Figure 1 is a schematic diagram of a method for manufacturing a semiconductor device according to the present invention; Figure 2 is a schematic diagram of a semiconductor device according to the present invention; [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 illustrates an embodiment of a wireless communication system for selecting an authentication type in a 5G network. [Figure 2A] FIG. 1 is a signal flow diagram illustrating an embodiment of a procedure to enable a UE that does not support 5G NAS via non-3GPP access to register with a 5G network via a trusted non-3GPP access network using a selected authentication type. [Figure 2B] FIG. 2B illustrates the continuation of the procedure shown in FIG. 2A. [Figure 2C] FIG. 2C illustrates the continuation of the procedure shown in FIG. 2B. [Figure 2D] FIG. 2D shows a continuation of the procedure shown in FIG. 2C. [Diagram 3] FIG. 1 is a block diagram illustrating an embodiment of a user equipment device that supports selection of authentication types in a 5G network. [Figure 4]FIG. 1 is a block diagram illustrating an embodiment of a network equipment device that supports authentication type selection in a 5G network. [Diagram 5] FIG. 1 is a flow chart diagram illustrating one embodiment of a first method for selecting an authentication type in a 5G network. [Figure 6] FIG. 1 is a flow chart diagram illustrating one embodiment of a second method for selecting an authentication type in a 5G network. [Figure 7] FIG. 11 is a flow chart diagram illustrating one embodiment of a third method for selecting an authentication type in a 5G network. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.) or an embodiment combining software and hardware aspects.

[0011] For example, the disclosed embodiments may be implemented as hardware circuits including custom very large scale integrated ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code which may be organized as, for example, objects, procedures, or functions.

[0012] Furthermore, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-transitory, and / or non-transmitting. The storage devices may not embody signals. In certain embodiments, the storage devices employ only signals to access the code.

[0013] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device that stores the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micro-mechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0014] More detailed examples of storage devices (a non-exhaustive list) include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disk read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0015] "One embodiment," "an embodiment," or similar language throughout this specification means that a particular feature, structure, or characteristic described with respect to this embodiment is included in at least one embodiment. Thus, all occurrences of the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification mean "one or more, but not all embodiments," although they may, but do not necessarily, refer to the same embodiment, unless otherwise specified. The terms "including," "comprising," "having," and variations thereof mean "including, but not limited to," unless otherwise specified. An enumerated list of items does not imply that any or all of the items are mutually exclusive, unless otherwise specified. The terms "a," "an," and "the" also refer to "one or more," unless otherwise specified.

[0016] As used herein, a list involving "and / or" includes any one item in the list or a combination of items in the list. For example, a list of A, B and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B and C. As used herein, a list using the term "one or more of" includes any one item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B and C. As used herein, a list using the term "one of" includes only any one item in the list. For example, "one of A, B and C" includes only A, only B, or only C, and excludes the combination of A, B and C. As used herein, "a member selected from the group consisting of A, B, and C" includes only one of A, B, or C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C, and combinations thereof" includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0017] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other cases, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0018] Aspects of the embodiments are described below with reference to schematic flow diagrams and / or schematic block diagrams of methods, apparatus, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow diagrams and / or schematic block diagrams, and combinations of blocks in the schematic flow diagrams and / or schematic block diagrams, may be implemented as code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to generate a machine such that the instructions, which execute via a processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the schematic flow diagrams and / or schematic block diagrams.

[0019] Code may be stored within the storage device that may instruct a computer, other programmable data processing device, or other device to function in a particular manner, such that the instructions stored within the storage device produce an article of manufacture that includes instructions that implement the functions / acts specified in the schematic flow chart illustrations and / or schematic block diagrams.

[0020] The code may be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device such that the code executing on the computer or other programmable apparatus generates a computer-implemented process to provide a process for implementing the functions / operations specified in the schematic flow chart illustrations and / or schematic block diagrams.

[0021] The schematic flow chart diagrams and / or schematic block diagrams of the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the schematic flow chart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing a specified logical function(s).

[0022] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may be executed in the reverse order, depending on the functionality involved. Other steps and methods may be devised that are equivalent in function, logic, or effect to one or more blocks of the illustrated figures, or portions thereof.

[0023] Descriptions of elements in each figure may refer to elements in the preceding figure. Like numbers refer to like elements in all figures, including alternative embodiments of like elements.

[0024] A method, apparatus, and system for selecting an authentication type in a 5G network are disclosed. A UE may access a 5G Core ("5GC") network via a trusted non-3GPP gateway function ("TNGF") in a trusted non-3GPP access network ("TNAN"). The 3GPP specification requires that all UEs that can access a 5G PLMN must support two authentication methods: EAP-AKA' and 5G-AKA.

[0025] When a UE attempts to access a 5G PLMN, during a primary authentication procedure, the UDM in the Home PLMN selects an authentication method (either EAP-AKA' or 5G-AKA) for this UE based on the UE Subscription Persistent Identity (SUPI). However, choosing an authentication method based only on the SUPI is not feasible for special UE types, i.e., UEs that (a) behave as normal 5G UEs when using 3GPP access, and (b) behave as non-5G capable devices when using WLAN access.

[0026] This special UE type may register to the 5G Core (5GC) network either via a 3GPP access network (e.g., NG-RAN or E-UTRAN) or via a non-3GPP access network (e.g., WLAN), but this UE type applies different capabilities. Via a 3GPP access network, this type of UE applies the 5G NAS protocol, and this type of UE requests 5G registration by sending a NAS registration request message. Via a non-3GPP access network, this special type of UE does not support the 5G NAS protocol, and this special type of UE requests 5G registration by initiating an EAP authentication procedure with a special NAI. The NAI is in the format<username@realm> Note that the special NAI may have the username portion and / or an indicator in the realm portion of the NAI, in which case the NAS registration request is made by a trusted WLAN interworking function ("TWIF") on behalf of the UE.

[0027] For the special UE type mentioned above, it is clear that the UDM should not select the 5G-AKA authentication method when the UE type attempts to register via non-3GPP access, because this authentication method is based on the 5G NAS protocol, but the UE does not support the 5G NAS protocol. Therefore, the 5G primary authentication procedure should be extended so that the UDM may select the EAP-AKA' authentication method in this case. Selecting the authentication method based only on the UE's SUPI (as currently specified) may cause the UE to select an unsupported authentication method (i.e., 5G-AKA), which would result in registration failure via non-3GPP access.

[0028] To clarify that this special type of UE is non-5G capable (i.e., cannot use 5G NAS protocols) when it communicates with 5GC via a WLAN access network, this special type of UE is also referred to as a non-5G capable over WLAN ("N5CW") device. However, it should be noted that when an N5CW device communicates with 5GC via a 3GPP access network, the device may be 5G capable. Thus, the same device may have two "personalities": when the device communicates with 5GC via a 3GPP access network, the device may be a normal 5G UE, and when the device communicates with 5GC via a non-3GPP access network, the device may be an N5CW device. Each "personality" is associated with a different authentication capability over 3GPP and non-3GPP access, which is the cause of the problem presented above.

[0029] FIG. 1 illustrates a wireless communication system 100 for selecting an authentication type in a 5G network, according to an embodiment of the present disclosure. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, at least one trusted non-3GPP access network ("TNAN") 130, and a mobile core network 140 in a PLMN. The TNAN 130 may be comprised of at least one base unit 121. The remote unit 105 may communicate with the TNAN 130 using a non-3GPP communication link 113 according to a radio access technology deployed by the TNAN 130. Although a specific number of remote units 105, base units 121, TNAN 130, and mobile core network 140 are illustrated in FIG. 1, one skilled in the art will recognize that any number of remote units 105, base units 121, TNAN 130, and mobile core network 140 may be included in the wireless communication system 100.

[0030] In one implementation, the wireless communication system 100 complies with the 5G system specified in the 3GPP specifications. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication network, such as LTE / EPC (referred to as "4G") or WiMAX, among other networks. This disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0031] In one embodiment, the remote unit 105 may include a computing device, such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smartphone, a smart television (e.g., a television connected to the Internet), a smart appliance (e.g., an appliance connected to the Internet), a set-top box, a gaming console, a security system (including security cameras), a vehicle mounted computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device, such as a smart watch, a fitness band, an optical head mounted display, etc. Additionally, the remote unit 105 may be referred to as a UE, a subscriber unit, a mobile, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a user terminal, a wireless transmit / receive unit ("WTRU"), a device, or by other terms used in the art.

[0032] The remote units 105 may communicate directly with one or more of the base units 121 within the TNAN 130 via uplink ("UL") and downlink ("DL") communication signals. Additionally, the UL and DL communication signals may be carried over communication link 113. Note that the TNAN 130 is an intermediate network that provides the remote units 105 with access to the mobile core network 140.

[0033] The base unit 121 may serve several remote units 105 within a serving area, e.g., within a cell or cell sector, via the communication link 113. The base unit 121 may directly communicate with one or more of the remote units 105 via communication signals. In general, the base unit 121 transmits DL communication signals to serve the remote units 105 in the time, frequency, and / or spatial domains. Furthermore, the DL communication signals may be carried via the communication link 113. The communication link 113 may be any suitable carrier in a licensed or unlicensed radio spectrum. The communication link 113 facilitates communication between one or more of the remote units 105 and / or one or more of the base units 121.

[0034] As described above, the TNAN 130 supports a secure signaling interface and interworking with the 5G core network. The TNAN includes at least one TNGF; in the illustrated embodiment, the TNAN 130 includes a first TNGF ("TNGF-1") 125 and a second TNGF ("TNGF-2") 127. In certain embodiments, the TNAN 130 supports a Tn interface between the TNGFs within the TNAN 130.

[0035] The base units 121 may be distributed across a geographic region. In certain embodiments, the base units 121 may be referred to as trusted non-3GPP access points ("TNAPs"), access terminals, access points, bases, base stations, relay nodes, devices, or any other terminology used in the art. The base units 121 are generally part of a radio access network ("RAN"), such as a TNAN 130, which may include one or more controllers communicatively coupled to one or more corresponding base units 121. These and other elements of a radio access network are not shown, but are generally well known by those skilled in the art. The base units 121 connect to a mobile core network 140 via the TNAN 130.

[0036] In some embodiments, the remote unit 105 communicates with an application server (or other communication peer) via a network connection with the mobile core network 140. For example, an application in the remote unit 105 (e.g., a web browser, a media client, a telephony / VoIP application) may trigger the remote unit 105 to establish a PDU session (or other data connection) with the mobile core network 140 using the TNAN 130. To establish a PDU session, the remote unit 105 must register with the mobile core network.

[0037] In one embodiment, the mobile core network 140 is a 5G Core ("5GC") or Evolved Packet Core ("EPC") that may be coupled to data networks (such as the Internet and private data networks, among other data networks). The remote units 105 may have a subscription or other account with the mobile core network 140. This disclosure is not limited to any particular wireless communications system architecture or protocol implementation.

[0038] The mobile core network 140 includes several network functions ("NFs"). As shown, the mobile core network 140 includes at least one user plane function ("UPF") 141. The mobile core network 140 also includes multiple control plane functions, including, but not limited to, an access and mobility management function ("AMF") 143, a session management function ("SMF") 145, an authentication server function ("AUSF") 146, a policy control function ("PCF") 147, and a unified data management function ("UDM") 149. In certain embodiments, the mobile core network 140 may include a network repository function ("NRF") (used by various NFs to discover and communicate with each other via APIs), or other NFs defined for the 5G core.

[0039] The remote unit 105 may request registration to a mobile core network 140 (e.g., 5GC) either via a 3GPP access 120 (e.g., NG-RAN or E-UTRAN) or via a non-3GPP access 130 (e.g., WLAN). The interworking function 135 makes a NAS registration request on behalf of a remote unit 105 that does not support the 5G-NAS protocol over a non-3GPP access network 130, e.g., as specified in TS 23.502, Chapter 4.12b. In various implementations, the interworking function 135 is an embodiment of a trusted WLAN interworking function ("TWIF").

[0040] The UDM 149 is an integrated data management function that selects an authentication method and creates the applicable authentication data whenever the remote unit 105 must be authenticated (e.g., during a registration procedure). The AUSF 146 is an authentication server function that receives the selected authentication method and authentication data from the UDM 149 and authenticates the remote unit 105.

[0041] In various embodiments, the mobile core network 140 supports different types of mobile data connections and different types of network slices, with each mobile data connection utilizing a particular network slice. Each network slice includes a set of CP and UP network functions, with each network slice optimized for a special type of service or traffic class. For ease of explanation, the different network slices are not shown in FIG. 1, but their support is assumed. In one example, each network slice instance includes instances of the SMF 145 and the UPF 141, but the various network slices share the AMF 143, the PCF 147, and the UDM / UDR 149. In another example, each network slice instance includes instances of the AMF 143, the SMF 145, and the UPF 141. Although a particular number and type of network functions are shown in FIG. 1, one skilled in the art will recognize that any number and type of network functions may be included within the mobile core network 140.

[0042] As discussed above, for remote units 105 that do not support the 5G-NAS protocol over non-3GPP access networks 130, selecting an authentication method based solely on the UE's SUPI (as currently specified) may result in selection of an unsupported authentication method for the UE (i.e., 5G-AKA), which would result in a registration failure over the non-3GPP access. Thus, as described in more detail below, the behavior of the interworking function 135 and / or the mobile core network 140 is modified to avoid selecting an unsupported authentication method.

[0043] 2A-2D show the signaling flows that apply when a UE that does not support 5G NAS via non-3GPP access 130 requests registration for 5GC (within 5G PLMN 215) via a WLAN access network (e.g., trusted non-3GPP access network 210). To clarify that this type of UE is non-5G capable (i.e., cannot use 5G NAS protocols) when it communicates with 5GC via a WLAN access network, this type of UE is also referred to as a non-5G capable over WLAN ("N5CW") device 205. However, it should be noted that when the N5CW device 205 communicates with 5GC via a 3GPP access network 120, it may be 5G capable. Thus, the same device may have two "personalities": the same device may be a normal 5G UE when it communicates with 5GC via a 3GPP access network 120, and may be an N5CW device when it communicates with 5GC via a non-3GPP access network 130. Each "personality" is associated with different authentication capabilities over 3GPP and non-3GPP accesses, which is the source of the problems presented above.

[0044] The procedure 200 involves an N5CW device 205 (i.e., an embodiment of the remote unit 105), a TNAN 210 (i.e., an embodiment of the non-3GPP access network 130), a TWIF 213 (i.e., an embodiment of the interworking function 135), 5GC NFs in the 5G PLMN 215, specifically, an AMF 217 (i.e., an embodiment of the AMF 143), an AUSF 218 (i.e., an embodiment of the AUSF 146), and a UDM 219 (i.e., an embodiment of the UDM / UDR 149).

[0045] The procedure 200 modifies the procedure specified in TS 23.502vl6.4.0, chapter 4.12b.2, with some new extensions aimed at helping the UDM 219 select the correct authentication method (i.e., EAP-AKA') when the N5CW device 205 attempts to register to a 5GC (in the 5G PLMN 215) via a non-3GPP access (i.e., the TNAN 210). Note again that without these extensions, the UDM 219 would select an authentication method based only on the SUPI of the N5CW device 205 and thus may select 5G-AKA, which is not supported by the N5CW device 205. In the most typical cases, the trusted non-3GPP access network 210 is a WLAN access network conforming to the IEEE 802.11 specification.

[0046] 2A, the procedure 200 begins at step 1, where the N5CW device 205 discovers a WLAN access network (i.e., TNAN 210) that advertises support for 5G connectivity to one or more PLMNs for devices that do not support 5G NAS protocols. Because this WLAN access network supports N2 / N3 connectivity with each of these PLMNs, the WLAN access network is referred to as a "trusted" WLAN access network.

[0047] The N5CW device 205 determines to connect to one of these PLMNs (i.e., 5G PLMN 215) via the discovered TNAN 210 and establishes a layer 2 (L2) connection (see messaging 221) with a trusted non-3GPP access point ("TNAP") 211 within the discovered TNAN 210. In the case of an IEEE 802.11 WLAN, this L2 connection corresponds to an IEEE 802.11 association.

[0048] In step 2, the EAP procedure begins. An EAP packet is encapsulated in an L2 packet, for example an IEEE 802.11 / 802.1x packet, between the N5CW device 205 and the TNAN 210. The TNAP 211 requests the identity of the N5CW device 205 (see messaging 223), and the N5CW device 205 responds with an L2 packet including an NAI. The NAI provided by the N5CW device 205 indicates that it is providing “5G connectivity without NAS” for a particular PLMN, i.e., NAI=“6 <suci>@nai.5gc-nn.mnc <mnc>.mcc <mcc>.3gppnetwork.org". Note that the prefix "6" is a special digit that indicates the capability of the N5CW device, as described in more detail below. The MNC, MCC are the identification of a particular 5G PLMN 215, and the "5gc-nn" designation indicates that there is no 5G connectivity with any NAS. The SUCI is a subscription concealment identifier that identifies the subscription within the 5G PLMN 210 and enables identity privacy, i.e., does not disclose the actual subscription identity to intermediate functions. In various embodiments, the SUCI is based on the subscription persistent identity of the N5CW device 205, such as the SUPI and / or IMSI.

[0049] The NAI provided by the N5CW device 205 selects a TWIF 213 that provides 5G connectivity to the indicated 5G PLMN 215 and triggers the TNAP 211 to send an AAA request to the selected TWIF 213 (see messaging 227). Between the TNAP 211 and the selected TWIF 213, each EAP packet is encapsulated in an AAA message.

[0050] In step 3, after receiving the AAA request in step 2c, the TWIF 213 creates a NAS-REGISTRATION REQUEST message on behalf of the N5CW device 205 (see block 229) and selects an AMF 217 in the indicated PLMN for forwarding the NAS-REGISTRATION REQUEST over the N2 interface (see block 231). In some embodiments, the TWIF 213 derives an authentication request type for the NAS-REGISTRATION REQUEST (block 233), as shown in option A. In other embodiments, the AMF 217 derives an authentication request type (block 239), as shown in option B.

[0051] In step A1 (part of option A), TWIF 213 derives an authentication request type based on the received NAI (see block 235). The authentication request type indicates the authentication method requested for this N5CW device 205, for example, TWIF 213 knows that N5CW device 205 cannot support 5G-AKA, so the authentication request type is set to EAP-AKA'. In certain embodiments, TWIF 213 may always set the authentication request type to EAP-AKA'. Alternatively, TWIF 213 may use the previous digits in the NAI to determine whether the authentication request type is EAP-AKA'. <suci>may be utilized to determine the authentication method preferred by the N5CW device 205. This digit may be set to "6" for EAP-AKA', "0" for EAP-AKA, "1" for EAP-SIM, etc. However, in other network implementations, different prefixes may be used to indicate different candidate authentication methods.

[0052] In step A2 (also part of Option A), the TWIF 213 forwards the created NAS-Registration Request message to the selected AMF 217 (see messaging 237), where the created NAS-Registration Request message is sent within an N2 message that also includes an authentication-request-type parameter (i.e., authentication-request-type=EAP-AKA').

[0053] Continuing in FIG. 2B, in step B1 (part of option B), alternatively, instead of steps A1-A2, TWIF 213 does not derive an authentication request type but forwards the created NAS registration request message to the selected AMF 217 in an N2 message that does not include an authentication request type (see messaging 241).

[0054] In step B2 (also part of option B), in this alternative, the AMF 217 generates an authentication request type and, for example, always sets it to EAP-AKA' (see block 243). Since the AMF 217 does not know about the NAI provided by the N5CW device 205, the AMF 217: <suci>Note that the digits before the 5G-AKA and EAP-AKA' authentication methods cannot be used to determine the authentication method preferred by the N5CW device 205. However, this is not an issue when the PLMN supports only the 5G-AKA and EAP-AKA' authentication methods.

[0055] It is important to note that the AMF 217 generates the authentication request type only when the AMF 217 receives a NAS registration request message from the TWIF 213. When the AMF 217 receives a NAS registration request message from another radio access function (e.g., gNB, N3IWF, TNGF, W-AGF), the AMF 217 does not derive the authentication request type.

[0056] In step 4a, the AMF 217 decides to authenticate the device requesting registration and sends a Nausf_UEAuthentication_Authenticate Request message to the AUSF 218 (see messaging 245). However, this message also includes the authentication request type received from the TWIF 213 in step A2 or derived by the AMF 217 in step B2.

[0057] In step 4b, before the AUSF 218 initiates the authentication procedure with the N5CW device 205, the AUSF 218 requests the UDM 219 to select an authentication method and provide authentication data (also called authentication vector) (see messaging 247). As shown, in the Nudm_UEAuthentication_Get Request message, the AUSF 218 also includes the Authentication Request Type received by the AMF 217 according to option A or derived by the AMF 217 according to option B.

[0058] In step 5, the UDM 219 uses the received Authentication Request Type to select an authentication method (see block 249). The UDM 219 may use the subscription data corresponding to the received subscriber identity (i.e., SUCI) to determine whether the authentication method in the received Authentication Request Type is permitted by the subscription data. In the illustrated embodiment, it is assumed that the requested EAP-AKA' method is permitted for the N5CW device 205.

[0059] In step 6, if the authentication method in the received Authentication Request Type is allowed by the subscription data, the UDM 219 selects this authentication method and provides (a) the selected authentication method (in the Authentication Type element) and (b) the authentication vector required for this authentication method to the AUSF 218 (see messaging 251). The AUSF 218 then starts the EAP authentication procedure according to the selected authentication method, e.g., if EAP-AKA' is selected, the AUSF 218 creates an EAP / AKA challenge packet. The AUSF 218 sends a response to the AMF 217 including the created EAP packet in an EAP payload (see messaging 253).

[0060] Continuing with FIG. 2C, in step 7, the EAP packet created by the AUSF 218 is forwarded to the N5CW device 205 via the AMF 217, the TWIF 213, and the TNAP 211 (see messaging 255).

[0061] In step 8, the N5CW device 205 sends a response EAP packet (see messaging 257) that is forwarded to the AUSF 218 via the TNAP 211, the TWIF 213, and the AMF 217. Further EAP packets may be exchanged between the UE and the AUSF 218 as in steps 7 and 8.

[0062] In step 9, after the authentication is successfully completed, the AUSF218 sends (again as an EAP payload) an EAP success packet, K SEAF A message containing the key and the unobscured subscriber identity (i.e., SUPI) of the N5CW device 205 is sent to the AMF 217 (see messaging 259).

[0063] In step 10a, AUSF 218 additionally indicates to UDM 219 that authentication was successfully completed by sending a Nudm_UEAuthentication_ResultConfirmation Request message (see messaging 261). In step 10b, UDM 219 responds with a Nudm_UEAuthentication_ResultConfirmation Response message (see messaging 263).

[0064] In step 11, the AMF 217 SEAF A TWIF key is created from the key (see block 265).

[0065] In step 12a, the AMF 217 initiates a normal security mode control (SMC) procedure (see messaging 267). In step 12b, the TWIF 213 responds (see messaging 269) on behalf of the N5CW device 205. This SMC procedure is performed between the TWIF 213 and the AMF 217 because the N5CW device 205 does not support 5G NAS.

[0066] In step 13, the AMF 217 sends an N2 Initial UE Context Setup Request message to the TWIF 213 (see messaging 271) to create a secure communication channel with the N5CW device 205. This message includes the TWIF key and triggers the TWIF 213 to send an EAP-Success message to the N5CW device 205 and send the TNAP key to the TNAP 211 (see messaging 273, 275). The TNAP 211 uses the TNAP key to secure the air interface communication between the N5CW device 205 and the TNAP 211. Note that the N5CW 205 derives a copy of the TNAP key for use in securing the air interface.

[0067] In step 14a, security is established between the N5CW device 205 and the TNAP 211 (see messaging 277) and the N5CW device 205 is successfully connected to the WLAN. In step 14b, the N5CW device 205 receives IP configuration data including an IP address (e.g., using a DHCP procedure) (see messaging 279). A Layer 2 (L2) or Layer 3 (L3) connection is established between the TNAP 211 and the TWIF 213, which is further used to tunnel all traffic of the N5CW device 205 to / from the TWIF 213 (see messaging 281).

[0068] In steps 15a-15b, the TWIF 213 responds to the AMF 217 with an N2 Initial UE Context Response message (see messaging 283) which triggers the AMF 217 to complete the registration procedure by sending a NAS Registration Accept to the TWIF 213 (see messaging 285). After this step, the TWIF 213 may request a PDU Session on behalf of the N5CW device 205, for example, as described in TS 23.502vl6.4.0, chapter 4.12b.2, to route all data of the N5CW device 205 within the 5G PLMN 215 via 5GC.

[0069] 3 illustrates an embodiment of a user equipment device 300 according to an embodiment of the disclosure. The user equipment device 300 may be an embodiment of a remote unit 105 and / or a UE 205. Additionally, the user equipment device 300 may include a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325. In some embodiments, the input device 315 and the output device 320 are combined into a single device, such as a touch screen. In certain embodiments, the user equipment device 300 does not include any input device 315 and / or output device 320.

[0070] As shown, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. Here, the transceiver 325 communicates with a mobile core network (e.g., 3GC) via an access network. In addition, the transceiver 325 may support at least one network interface 340. Here, the at least one network interface 340 facilitates communication with the TNGF (e.g., using an "NWt" interface). In addition, the at least one network interface 340 may include interfaces used to communicate with the AMF, SMF, and / or UPF.

[0071] The processor 305, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 305 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processing unit ("GPU"), auxiliary processing unit, field programmable gate array ("FPGA"), or similar programmable controller. In some embodiments, the processor 305 executes instructions stored in the memory 310 to perform the methods and routines described herein. The processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.

[0072] In various embodiments, the processor 305 controls the user equipment device 300 to implement the UE behaviors described above.

[0073] Memory 310, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 310 is a volatile computer storage medium. For example, memory 310 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 310 includes a non-volatile computer storage medium. For example, memory 310 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 310 includes both volatile and non-volatile computer storage media.

[0074] In some embodiments, memory 310 stores data related to the selection of an authentication type in a 5G network, e.g., stores authentication parameters, security keys, device / entity identifiers, IP addresses, etc. In particular embodiments, memory 310 also stores program code and associated data, such as an operating system ("OS") or other controller algorithms that run on user equipment device 300 and one or more software applications.

[0075] The input device 315, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 315 may be integrated with an output device 320, such as, for example, a touch screen or similar touch-sensitive display. In some embodiments, the input device 315 includes a touch screen, such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 315 includes two or more different devices, such as a keyboard and a touch panel.

[0076] The output device 320, in one embodiment, may include any known electronically controllable display or display device. The output device 320 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, the output device 320 includes an electronic display capable of outputting visual data to a user. For example, the output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 320 may include a wearable display, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, the output device 320 may be a component of a smartphone, a personal digital assistant, a television, a tablet computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0077] In certain embodiments, the output device 320 includes one or more speakers for generating sound. For example, the output device 320 may generate an audible alert or notification (e.g., a beep or chime). In some embodiments, the output device 320 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of the output device 320 may be integrated with the input device 315. For example, the input device 315 and the output device 320 may form a touch screen or similar touch-sensitive display. In other embodiments, all or a portion of the output device 320 may be located near the input device 315.

[0078] As discussed above, the transceiver 325 communicates with one or more network functions of a mobile communications network via one or more access networks. The transceiver 325 operates under the control of the processor 305 to transmit messages, data, and other signals, and also to receive messages, data, and other signals. For example, the processor 305 may selectively activate the transceiver (or portions thereof) at particular times to transmit and receive messages.

[0079] The transceiver 325 may include one or more transmitters 330 and one or more receivers 335. Although only one transmitter 330 and one receiver 335 are shown, the user equipment device 300 may have any suitable number of transmitters 330 and receivers 335. Furthermore, the transmitters 330 and receivers 335 may be any suitable type of transmitter and receiver. In one embodiment, the transceiver 325 includes a first transmitter / receiver pair used to communicate with a mobile communications network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communications network over an unlicensed radio spectrum.

[0080] In certain embodiments, a first transmitter / receiver pair used to communicate with a mobile communications network over a licensed radio spectrum and a second transmitter / receiver pair used to communicate with a mobile communications network over an unlicensed radio spectrum may be combined into a single transceiver unit, e.g., a single chip that implements functionality for use with both licensed and unlicensed radio spectrum. In some embodiments, the first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, a particular transceiver 325, transmitter 330, and receiver 335 may be implemented as physically separate components that access common hardware and / or software resources, such as, for example, a network interface 340.

[0081] In various embodiments, one or more transmitters 330 and / or one or more receivers 335 may be implemented and / or integrated within a single hardware component, such as a multi-transceiver chip, a system-on-chip, an ASIC, or other type of hardware component. In particular embodiments, one or more transmitters 330 and / or one or more receivers 335 may be implemented and / or integrated within a multi-chip module. In some embodiments, other components, such as a network interface 340 or other hardware components / circuits, may be integrated into a single chip with any number of transmitters 330 and / or receivers 335. In such embodiments, the transmitters 330 and receivers 335 may be logically configured as a transceiver 325 using another common control signal, or as modular transmitters 330 and receivers 335 implemented within the same hardware chip or multi-chip module.

[0082] FIG. 4 illustrates an embodiment of a network equipment device 400 according to an embodiment of the present disclosure. In some embodiments, the network equipment device 400 may be an embodiment of a TNGF (i.e., TNGF1 and / or TNGF2). In other embodiments, the network equipment device 400 may be an embodiment of an AMF. Furthermore, the network equipment device 400 may include a processor 405, a memory 410, an input device 415, an output device 420, and a transceiver 425. In some embodiments, the input device 415 and the output device 420 are combined in a single device, such as a touch screen. In certain embodiments, the network equipment device 400 does not include any input device 415 and / or output device 420.

[0083] As shown, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435, where the transceiver 425 communicates with one or more remote units. In addition, the transceiver 425 may support at least one network interface 440, such as the NWt, N2, and N3 interfaces shown in FIG. 1. In some embodiments, the transceiver 425 supports a first interface for communicating with a RAN node, a second interface for communicating with one or more network functions within a mobile core network (e.g., 4GC), and a third interface for communicating with a remote unit (e.g., UE).

[0084] The processor 405, in one embodiment, may include any known controller capable of executing computer-readable instructions and / or performing logical operations. For example, the processor 405 may be a microcontroller, microprocessor, central processing unit ("CPU"), graphics processing unit ("GPU"), auxiliary processing unit, field programmable gate array ("FPGA"), or similar programmable controller. In some embodiments, the processor 405 executes instructions stored in the memory 410 to perform the methods and routines described herein. The processor 405 is communicatively coupled to the memory 410, the input device 415, the output device 420, and the first transceiver 425.

[0085] In various embodiments, the processor 405 controls the network equipment device 400 to implement the AMF behavior described above. In some embodiments, via the network interface 440, the processor 405 receives a first message from an interworking function in a non-3GPP access network (i.e., a TWIF), the first message requesting 5G registration to a mobile communications network on behalf of a remote unit (i.e., an N5CW device) that does not support the NAS protocol.

[0086] The processor 405 is responsible for determining a required authentication method for the remote unit, where the required authentication method is not based on a NAS protocol, and forwarding the required authentication method to a data management function (i.e., UDM) via an AUSF in the mobile communications network, where the required authentication method is applied by the data management function to select an authentication method for the remote unit, where the selected authentication method is not based on a NAS protocol. The processor 405 initiates a security mode control procedure with the interworking function in response to successful authentication completion by the remote unit using the selected authentication method.

[0087] In some embodiments, the first message is an NGAP message including a NAS registration request message and an authentication type parameter, and determining the requested authentication method includes parsing the first message for the authentication type parameter. In some embodiments, determining the requested authentication method includes selecting a pre-configured authentication method type (i.e., EAP-AKA') whenever the first message is received. In some embodiments, the request message includes the requested authentication method, and the authentication request message indicates that the remote unit should be authenticated using an authentication method that is based on the requested authentication method.

[0088] In various embodiments, the processor 405 controls the network equipment device 400 to implement the TWIF behavior described above. In some embodiments, via the network interface 440, the processor 405 receives a first message requesting to register a remote unit with a mobile communication network, the remote unit is connected to a non-3GPP access network, and the remote unit does not support a NAS protocol (i.e., the remote unit is an N5CW device). The processor 405 determines an authentication request type for the remote unit, the authentication request type is not based on the NAS protocol. The processor 405 creates a NAS registration message on behalf of the remote unit and sends a second message to an access management function in the mobile communication network, the second message including the NAS registration message and the determined authentication request type.

[0089] In some embodiments, the first message includes an NAI indicating that the remote unit does not support the NAS protocol, and determining the authentication request type includes selecting an authentication request type based on the NAI. In certain embodiments, a portion of the NAI indicates a preferred authentication method for the remote unit, and determining the authentication request type is based on the preferred authentication method for the remote unit. In some embodiments, the device is configured with a default authentication method type to use whenever the first message is received.

[0090] In various embodiments, the processor 405 controls the network equipment device 400 to implement the UDM behavior described above. In some embodiments, via the network interface 440, the processor 405 receives a first request from an AUSF in a mobile communication network to provide authentication data to a remote unit (i.e., an N5CW device), the request indicating an authentication request type. The processor 405 selects a first authentication method using the authentication request type and subscription data of the remote unit, and responds to the first request by transmitting an authentication vector, the response also indicating the first authentication method.

[0091] In some embodiments, selecting the first authentication method includes determining whether the authentication request type is permitted by the subscription data. In some embodiments, the first request includes the SUCI of the remote unit, and the processor 405 decodes the SUCI to retrieve the subscription data of the remote unit.

[0092] Memory 410, in one embodiment, is a computer-readable storage medium. In some embodiments, memory 410 includes volatile computer storage media. For example, memory 410 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 410 includes non-volatile computer storage media. For example, memory 410 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 410 includes both volatile and non-volatile computer storage media.

[0093] In some embodiments, memory 410 stores data related to the selection of authentication types in a 5G network, e.g., security keys, IP addresses, UE context, etc. In particular embodiments, memory 410 also stores program code and associated data, such as an operating system ("OS") or other controller algorithms that run on network equipment device 400 and one or more software applications.

[0094] The input device 415, in one embodiment, may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. In some embodiments, the input device 415 may be integrated with an output device 420, such as, for example, a touch screen or similar touch-sensitive display. In some embodiments, the input device 415 includes a touch screen, such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, the input device 415 includes two or more different devices, such as a keyboard and a touch panel.

[0095] The output device 420, in one embodiment, may include any known electronically controllable display or display device. The output device 420 may be designed to output visual, auditory, and / or tactile signals. In some embodiments, the output device 420 includes an electronic display capable of outputting visual data to a user. For example, the output device 420 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, the output device 420 may include a wearable display, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, the output device 420 may be a component of a smartphone, a personal digital assistant, a television, a tablet computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0096] In certain embodiments, output device 420 includes one or more speakers for generating sound. For example, output device 420 may generate an audible alert or notification (e.g., a beep or chime). In some embodiments, output device 420 includes one or more haptic devices for generating vibration, movement, or other haptic feedback. In some embodiments, all or a portion of output device 420 may be integrated with input device 415. For example, input device 415 and output device 420 may form a touchscreen or similar touch-sensitive display. In other embodiments, all or a portion of output device 420 may be located near input device 415.

[0097] As discussed above, the transceiver 425 may communicate with one or more interworking functions that provide access to one or more remote units and / or one or more PLMNs. The transceiver 425 may also communicate with one or more network functions (e.g., within the mobile core network 140). The transceiver 425 operates under the control of the processor 405 to transmit messages, data, and other signals, and also to receive messages, data, and other signals. For example, the processor 405 may selectively activate the transceiver (or portions thereof) at particular times to transmit and receive messages.

[0098] The transceiver 425 may include one or more transmitters 430 and one or more receivers 435. In particular embodiments, the one or more transmitters 430 and / or the one or more receivers 435 may share transceiver hardware and / or circuitry. For example, the one or more transmitters 430 and / or the one or more receivers 435 may share antennas, antenna tuners, amplifiers, filters, oscillators, mixers, modulators / demodulators, power supplies, etc. In one embodiment, the transceiver 425 implements multiple logical transceivers using different communication protocols or protocol stacks while using common physical hardware.

[0099] 5 illustrates one embodiment of a method 500 for selecting an authentication type in a 5G network in accordance with an embodiment of the disclosure. In various embodiments, method 500 is performed by an access and mobility management function, such as AMF 143, AMF 217, and / or network equipment device 400 described above. In some embodiments, method 500 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0100] The method 500 begins by receiving 505 a first message from an interworking function in a non-3GPP access network (i.e., the TWIF), the first message requesting 5G registration with the mobile communications network on behalf of a remote unit that does not support the NAS protocol.

[0101] The method 500 includes determining 510 a required authentication method for the remote unit, where the required authentication method is not based on a NAS protocol.

[0102] The method 500 includes forwarding 515 the requested authentication method to a data management function (i.e., UDM) via an AUSF in the mobile communications network, where the requested authentication method is applied by the data management function to select an authentication method for the remote unit, and the selected authentication method is not based on a NAS protocol.

[0103] Method 500 includes initiating an SMC procedure with the interworking function 520 in response to successful authentication completion by the remote unit using the selected authentication method. Method 500 then ends.

[0104] 6 illustrates one embodiment of a method 600 for selecting an authentication type in a 5G network in accordance with an embodiment of the disclosure. In various embodiments, method 600 is performed by an interworking function, such as interworking function 135, TWIF 213, and / or network equipment device 400, described above. In some embodiments, method 600 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0105] The method 600 begins by receiving 605 a first message requesting to register a remote unit with a mobile communications network, the remote unit being connected to a non-3GPP access network, and the remote unit not supporting the NAS protocol. The method 600 includes a step 610 of determining an authentication request type for the remote unit, the authentication request type not based on the NAS protocol. The method 600 includes a step 615 of creating a NAS registration message on behalf of the remote unit. The method 600 includes a step 620 of sending a second message to an access management function in the mobile communications network, the second message including the NAS registration message and the determined authentication request type. The method 600 ends.

[0106] 7 illustrates one embodiment of a method 700 for selecting an authentication type in a 5G network in accordance with an embodiment of the disclosure. In various embodiments, method 700 is performed by a subscription and user data manager, such as UDM / UDR 149, UDM 219, and / or network equipment device 400, as described above. In some embodiments, method 700 is performed by a processor, such as a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, etc.

[0107] The method 700 begins by receiving 705 a first request from an AUSF in a mobile communications network to provide authentication data to a remote unit, the request indicating an authentication request type. The method 700 includes a step 710 of selecting a first authentication method using the authentication request type and subscription data of the remote unit. The method 700 includes a step 715 of responding to the first request by sending an authentication vector, the response also indicating the first authentication method. The method 700 ends.

[0108] Disclosed herein is a first apparatus for selecting an authentication type in a 5G network according to an embodiment of the present disclosure. The first apparatus may be implemented by an access and mobility management function, such as the AMF 143, the AMF 217, and / or the network equipment device 400. The first apparatus includes a processor and a network interface for receiving a first message from an interworking function in a non-3GPP access network (i.e., TWIF), where the first message requests 5G registration to a mobile communication network on behalf of a remote unit that does not support a NAS protocol. The processor determines a requested authentication method for the remote unit, where the requested authentication method is not based on a NAS protocol, and forwards the requested authentication method to a data management function (i.e., UDM) via an AUSF of the mobile communication network. Wherein, the requested authentication method is applied by the data management function to select an authentication method for the remote unit, where the selected authentication method is not based on a NAS protocol. The processor initiates a security mode control procedure with the interworking function in response to successful authentication completion by the remote unit using the selected authentication method.

[0109] In some embodiments, the first message is an NGAP message including a NAS registration request message and an authentication type parameter, and determining the requested authentication method includes parsing the first message for the authentication type parameter. In some embodiments, determining the requested authentication method includes selecting a pre-configured authentication method type (i.e., EAP-AKA') whenever the first message is received. In some embodiments, the request message includes the requested authentication method, and the authentication request message indicates that the remote unit should be authenticated using an authentication method that is based on the requested authentication method.

[0110] Disclosed herein is a first method for selecting an authentication type in a 5G network according to an embodiment of the present disclosure. The first method may be implemented by an access and mobility management function, such as the AMF 143, the AMF 217, and / or the network equipment device 400. The first method includes receiving a first message from an interworking function in a non-3GPP access network (i.e., TWIF), where the first message requests 5G registration to a mobile communication network on behalf of a remote unit that does not support a NAS protocol. The first method includes determining a requested authentication method for the remote unit, where the requested authentication method is not based on a NAS protocol, and forwarding the requested authentication method to a data management function (i.e., UDM) via an AUSF in the mobile communication network. Wherein the requested authentication method is applied by the data management function to select an authentication method for the remote unit, where the selected authentication method is not based on a NAS protocol. The first method includes initiating a security mode control procedure with the interworking function in response to successful authentication completion by the remote unit using the selected authentication method.

[0111] In some embodiments, the first message is an NGAP message including a NAS registration request message and an authentication type parameter, and determining the requested authentication method includes parsing the first message for the authentication type parameter. In some embodiments, determining the requested authentication method includes selecting a pre-configured authentication method type (i.e., EAP-AKA') whenever the first message is received. In some embodiments, forwarding the requested authentication method includes sending an authentication request message including the requested authentication method to the AUSF, the authentication request message indicating that the remote unit should be authenticated using an authentication method based on the requested authentication method.

[0112] Disclosed herein is a second apparatus for selecting an authentication type in a 5G network according to an embodiment of the present disclosure. The second apparatus may be implemented by an interworking function, such as the interworking function 135, the TWIF 213, and / or the network equipment device 400. The second apparatus includes a processor and a network interface that receives a first message requesting to register a remote unit in a mobile communication network, where the remote unit is connected to a non-3GPP access network, and the remote unit does not support a NAS protocol. The processor determines an authentication request type for the remote unit, where the authentication request type is not based on the NAS protocol. The processor creates a NAS registration message on behalf of the remote unit and sends a second message to an access management function in the mobile communication network, where the second message includes the NAS registration message and the determined authentication request type.

[0113] In some embodiments, the first message includes an NAI indicating that the remote unit does not support the NAS protocol, and determining the authentication request type includes selecting an authentication request type based on the NAI. In particular embodiments, a portion of the NAI indicates a preferred authentication method for the remote unit, and determining the authentication request type is based on the preferred authentication method for the remote unit. In some embodiments, the device is configured with a default authentication method type to use whenever the first message is received.

[0114] Disclosed herein is a second method for selecting an authentication type in a 5G network according to an embodiment of the present disclosure. The second method may be implemented by an interworking function, such as the interworking function 135, the TWIF 213, and / or the network equipment device 400. The second method includes receiving a first message requesting registration of a remote unit in a mobile communication network, where the remote unit is connected to a non-3GPP access network and the remote unit does not support a NAS protocol. The second method includes determining an authentication request type for the remote unit and creating a NAS registration message on behalf of the remote unit, where the authentication request type is not based on the NAS protocol. The second method includes sending a second message to an access management function in the mobile communication network, where the second message includes the NAS registration message and the determined authentication request type.

[0115] In some embodiments, the first message includes an NAI indicating that the remote unit does not support a NAS protocol, and determining the authentication request type includes selecting an authentication request type based on the NAI. In certain embodiments, a portion of the NAI indicates a preferred authentication method for the remote unit, and determining the authentication request type is based on the preferred authentication method for the remote unit. In some embodiments, the second method includes receiving a configuration of a default authentication method type to be used whenever the first message is received.

[0116] Disclosed herein is a third apparatus for selecting an authentication type in a 5G network according to an embodiment of the present disclosure. The third apparatus may be implemented by a subscription and user data manager, such as a UDM / UDR 149, a UDM 219, and / or a network equipment device 400. The third apparatus includes a processor and a network interface for receiving a first request from an AUSF in a mobile communication network to provide authentication data to a remote unit, the request indicating an authentication request type. The processor selects a first authentication method using the authentication request type and the subscription data of the remote unit, and responds to the first request by sending an authentication vector, the response also indicating the first authentication method.

[0117] In some embodiments, selecting the first authentication method includes determining whether the authentication request type is permitted by the subscription data. In some embodiments, the first request includes a SUCI of the remote unit, and the processor decodes the SUCI to retrieve the subscription data of the remote unit.

[0118] Disclosed herein is a third method for selecting an authentication type in a 5G network according to an embodiment of the present disclosure. The third method may be implemented by a subscription and user data manager, such as a UDM / UDR 149, a UDM 219, and / or a network equipment device 400. The third method includes receiving a first request from an AUSF in a mobile communication network to provide authentication data to a remote unit, the request indicating an authentication request type. The third method includes selecting a first authentication method using the authentication request type and the subscription data of the remote unit, and responding to the first request by sending an authentication vector, the response also indicating the first authentication method.

[0119] In some embodiments, selecting the first authentication method includes determining whether the authentication request type is permitted by the subscription data. In some embodiments, the first request includes a SUCI of the remote unit, and the method further includes decrypting the SUCI to retrieve the subscription data of the remote unit.

[0120] The embodiments may be embodied in other specific forms. The described embodiments are to be considered in all respects as merely illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0121] 100 Wireless communication system 105 Remote Unit 113 Non-3GPP communication links, communication links 120 3GPP Access 121 Base Unit 125 The first TNGF ("TNGF-1") 127 The second TNGF ("TNGF-2") 130 Trusted Non-3GPP Access Network ("TNAN"), Non-3GPP Access 135 Interworking Function 140 Mobile Core Network 141 User Plane Function ("UPF") 143 Access and Mobility Management Function ("AMF") 145 Session Management Facility ("SMF") 146 Authentication Server Function ("AUSF") 147 Policy Control Function ("PCF") 149 Integrated Data Management Function ("UDM"), UDR 205 N5CW Device, UE 210 TNAN 211 Trusted Non-3GPP Access Point (TNAP) 213 TWIF 215 PLMNs, 5G PLMNs 217 AMF 218 AUSF 219 UDM 221 Messaging 223 Messaging 227 Messaging 229 Block 231 Block 233 Block 235 Block 237 Messaging 239 Block 241 Messaging 243 Block 245 Messaging 247 Messaging 249 Block 251 Messaging 253 Messaging 255 Messaging 257 Messaging 259 Messaging 261 Messaging 263 Messaging 265 blocks 267 Messaging 269 ​​Messaging 271 Messaging 273 Messaging 275 Messaging 277 Messaging 279 Messaging 281 Messaging 283 Messaging 285 Messaging 300 User equipment device 305 Processor 310 Memory 315 Input Devices 320 Output Device 325 Transceiver 330 Transmitter 335 Receiver 340 Network Interface 400 Network Equipment 405 Processor 410 Memory 415 Input Devices 420 output device 425 Transceiver, First Transceiver 430 Transmitter 435 Receiver 440 Network Interface 500 ways 600 ways 700 methods< / suci> < / suci> < / mcc> < / mnc> < / suci>

Claims

1. 1. An apparatus in a mobile communications network, comprising: a network interface configured to receive a first message from an interworking function in a non-3GPP access network, the first message requesting 5G registration with the mobile communications network on behalf of a remote unit that does not support a non-access stratum ("NAS") protocol; and 1. A processor comprising: determining a required authentication method for the remote unit, the required authentication method being not based on the NAS protocol; forwarding the requested authentication method to a Data Management Function via an Authentication Server Function ("AUSF") in the mobile communications network, the requested authentication method being applied by the Data Management Function to select an authentication method for the remote unit, the selected authentication method being not based on the NAS protocol; initiating a security mode control procedure with said interworking function in response to said remote unit successfully completing authentication using said selected authentication method; The processor and An apparatus comprising:

2. 2. The apparatus of claim 1, wherein the first message is a Next Generation Application Protocol ("NGAP") message including a NAS Registration Request message and an authentication type parameter, and wherein determining the requested authentication method includes parsing the first message for the authentication type parameter.

3. The apparatus of claim 1 , wherein the determining the required authentication method includes selecting a preconfigured authentication method type whenever the first message is received.

4. 2. The apparatus of claim 1, wherein the apparatus sends an authentication request message to the AUSF including the requested authentication method, the authentication request message indicating that the remote unit should be authenticated using an authentication method based on the requested authentication method.

5. receiving a first message from an interworking function in a non-3GPP access network, the first message requesting 5G registration with a mobile communications network on behalf of a remote unit that does not support a Non-Access Stratum ("NAS") protocol; determining a required authentication method for the remote unit, the required authentication method not being based on the NAS protocol; forwarding the requested authentication method to a Data Management Function via an Authentication Server Function ("AUSF") in the mobile communications network, where the requested authentication method is applied by the Data Management Function to select an authentication method for the remote unit, and where the selected authentication method is not based on the NAS protocol; initiating a security mode control procedure with said interworking function in response to said remote unit successfully completing authentication using said selected authentication method; A method comprising:

6. 6. The method of claim 5, wherein the first message is a Next Generation Application Protocol ("NGAP") message including a NAS Registration Request message and an authentication type parameter, and wherein determining the requested authentication method includes parsing the first message for an authentication type parameter.

7. 6. The method of claim 5, wherein the step of determining the required authentication method comprises the step of selecting a preconfigured authentication method type whenever the first message is received.

8. 6. The method of claim 5, wherein the step of forwarding the requested authentication method comprises the step of sending an authentication request message to the AUSF including the requested authentication method, the authentication request message indicating that the remote unit should be authenticated using an authentication method based on the requested authentication method.

9. 1. An apparatus in a mobile communications network, comprising: a network interface for receiving a first message requesting registration of a remote unit with the mobile communications network, the remote unit being connected to a non-3GPP access network and the remote unit not supporting a non-access stratum ("NAS") protocol; and 1. A processor comprising: determining an authentication request type for the remote unit, the authentication request type not based on the NAS protocol; generating a NAS registration message on behalf of the remote unit; sending a second message to an access management function in the mobile communications network, the second message including the NAS registration message and the determined authentication request type; A processor that performs Equipped with the first message includes a network access identifier ("NAI") indicating that the remote unit does not support the NAS protocol, and determining the authentication request type includes selecting an authentication request type based on the NAI. Device.

10. 10. The apparatus of claim 9, wherein a portion of the NAI indicates a preferred authentication method of the remote unit, and wherein the determining of the authentication request type is based on the preferred authentication method of the remote unit.

11. 10. The apparatus of claim 9, wherein the apparatus is configured with a default authentication method type to use whenever the first message is received.

12. receiving a first message requesting registration of a remote unit with a mobile communications network, the remote unit being connected to a non-3GPP access network and the remote unit not supporting a non-access stratum ("NAS") protocol; determining an authentication request type for the remote unit, the authentication request type not being based on the NAS protocol; creating a NAS registration message on behalf of the remote unit; sending a second message to an access management function in the mobile communication network, the second message including the NAS registration message and the determined authentication request type; Including, The first message includes a Network Access Identifier ("NAI") indicating that the remote unit does not support the NAS protocol, and the determining the authentication request type includes selecting an authentication request type based on the NAI. method.

13. 13. The method of claim 12, wherein a portion of the NAI indicates a preferred authentication method of the remote unit, and wherein the determining of the authentication request type is based on the preferred authentication method of the remote unit.

14. 13. The method of claim 12, further comprising the step of receiving a configuration of a default authentication method type to be used whenever the first message is received.

15. 1. An apparatus in a mobile communications network, comprising: a network interface that receives a first request from an Authentication Server Function ("AUSF") in the mobile communications network to provide authentication data to a remote unit, the request indicating an authentication request type; 1. A processor comprising: selecting a first authentication method using the authentication request type and subscription data of the remote unit; responding to the first request by transmitting an authentication vector, the response also indicating the first authentication method; A processor that performs An apparatus comprising:

16. 16. The apparatus of claim 15, wherein the selecting the first authentication method includes determining whether the authentication request type is permitted by the subscription data.

17. 16. The apparatus of claim 15, wherein the first request includes a subscription ciphering identifier ("SUCI") of the remote unit, and the processor decodes the SUCI to retrieve the subscription data of the remote unit.

18. receiving a first request from an Authentication Server Function ("AUSF") in a mobile communications network to provide authentication data to a remote unit, said request indicating an authentication request type; selecting a first authentication method using the authentication request type and subscription data of the remote unit; responding to the first request by transmitting an authentication vector, the response also indicating the first authentication method; A method comprising:

19. 20. The method of claim 18, wherein the step of selecting the first authentication method includes determining whether the authentication request type is permitted by the subscription data.

20. 20. The method of claim 18, wherein the first request includes a subscription concealment identifier ("SUCI") of the remote unit, the method further comprising the step of decrypting the SUCI to retrieve the subscription data of the remote unit.

Citation Information

Patent Citations

  • A method to authenticate with a mobile communication network

    US20190335330A1

  • Handling failure of non-3GPP access to 5GCN not being allowed

    WO2020006515A1