Identity layer for IoT devices
By introducing 3UIANF into the 5G core network, the problem of the inability to identify and authenticate IoT device users in the existing technology has been solved, effective identity management and service policy application for IoT device users has been realized, and network security and management capabilities have been enhanced.
Patent Information
- Application Number
- CN202411037174.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2018-05-18
- Filing Date
- 2019-05-17
- Publication Date
- 2024-11-15
AI Technical Summary
The existing 3GPP system cannot effectively identify and authenticate users using IoT devices, especially when the device is shared by multiple users, resulting in the inability to apply value-added services unique to different users, such as parental control.
By introducing the 3GPP user identity authentication network function (3UIANF), user identity information is used to authenticate, support different user identity authentication, and identify users in the 5G core network, allowing users to separate identity authentication from the device to realize IoT devices User identity management.
It realizes effective identification and authentication of IoT device users, supports the application of service policies of different users, enhances network management and security, and ensures that the services of different users are correctly authorized and authenticated.
Smart Images

Figure CN118972846A_ABST
Abstract
Description
[0001] This application is a divisional application of the PCT application entering the Chinese national phase, with an international filing date of May 17, 2019, national application number 201980032922.1, and invention name “Identity Layer of IoT Devices”. Background Art
[0002] In 3GPP systems, the International Mobile Subscriber Identity (IMSI) is a subscription identifier. The IMSI consists of three fields: the Mobile Country Code (MCC), the Mobile Network Code (MNC), and the Mobile Subscriber Identification Number (MSIN). In 3GPP systems, the International Mobile Equipment Identity (IMEI) is a device identifier used to identify a given user equipment (UE). In IEEE 802 systems, the Medium Access Control (MAC) address is a device identifier used to identify a network interface controller. With respect to user identifiers, it is recognized herein that there is a lack of capabilities related to how different users can be authenticated over existing subscription authentications. Summary of the invention
[0003] In some examples, a user-centric authentication layer may be supported on top of existing subscription authentication so that different users can use the same user equipment (UE) with customized services, and different users of a device may be identified behind a gateway with a 3GPP subscription (in the absence of a device with a dedicated 3GPP subscription). Additionally, a user identifier may be linked to a subscription to access 3GPP services via non-3GPP access.
[0004] In an example, the UE receives a user identity and, in response to a triggering event, sends a request message to the network. The request message may include the user identity and session information to be associated with the user identity. The request message may also include a general registration request, a service request, a PDU session establishment request, a PDU modification request, or a PDU session release request. The request message may also include a list of users allowed to access the network via the UE. The UE may receive a response from the network, and the response may include an indication of whether the session information is allowed to be associated with the user identity. The user identity may be received via a graphical user interface of the UE or from a capillary device communicating with the UE or from an application running on the UE. Thus, the user identity may be an application, a capillary device communicating with the UE, or a human user of the UE. In some examples, the triggering event is a user identity being received by the UE. Other example triggering events include: when the UE transitions from a locked state to an unlocked state; when the UE receives data from a capillary device communicating with the UE; or when the UE receives a paging message or a non-access stratum (NAS) message. Such a paging message may include a user identity. For example, the UE may send a second message to the network, the second message indicating that the UE supports receiving a paging notification or a NAS notification including a user identity. In addition, the UE may receive broadcast information indicating that the network supports paging based on the user identity, and the UE may send a request message to the network based on the received broadcast information. Using the user identity, the UE may perform authentication on the network of the user associated with the user identity. In an example, the session information is protocol data unit (PDU) session information. In another example, the UE sends a second request message to the network to notify the network that the user identity is no longer associated with the UE. This second request message may be a registration request, or a message that may be sent in response to a paging notification or a NAS notification.
[0005] This summary is provided to introduce some concepts in a simplified form, which will be further described in the detailed description below. This summary is neither intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that address any or all disadvantages noted in any part of this disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0006] In order to promote a more robust understanding of the present application, reference is now made to the accompanying drawings, in which like elements are referenced with like reference numerals. These drawings should not be construed as limiting the present application, but are merely exemplary.
[0007] Figure 1 FIG. 2 is a call flow illustrating a 5G authentication process for a user equipment (UE).
[0008] Figure 2 It is a block diagram of the general Extensible Authentication Protocol (EAP) architecture.
[0009] Figure 3 Depicted is an example use case where a capillary device uses a user identity to access a 5G core network (5GC).
[0010] Figure 4 is a block diagram illustrating a 3GPP User Identity Authentication Network Function (3UIANF) in a 5GC according to an example embodiment.
[0011] Figure 5 is a call flow for user authentication with 3U I ANF using the control plane according to an example embodiment.
[0012] Figure 6 is a call flow for user authentication with 3U I ANF using user plane according to an example embodiment.
[0013] Figure 7 is a call flow illustrating an example registration process modified according to an example embodiment.
[0014] Figure 8 is a call flow illustrating a UE-triggered service request procedure that may be modified according to an example embodiment.
[0015] Fig. 9 is a call flow illustrating a UE-requested PDU session establishment procedure for non-roaming and roaming with local breakout that may be modified according to an example embodiment.
[0016] Fig.10 is an example UE graphical user interface for configuring a 3GPP user identity according to an example embodiment.
[0017] Fig.11A One embodiment of an example communication system is illustrated in which the methods and apparatus described and claimed herein may be implemented.
[0018] Fig. 11B is a block diagram of an example apparatus or device configured for wireless communication according to embodiments described herein.
[0019] Fig. 11C is a system diagram of an example radio access network (RAN) and core network according to an example embodiment.
[0020] Fig.11D is another system diagram of a RAN and a core network according to another embodiment.
[0021] Fig.11Eis another system diagram of a RAN and a core network according to another embodiment.
[0022] Fig.11F is a block diagram of an exemplary computing system 90 in which Fig.11A , 11C , 11D and 11E.
[0023] Fig.11G An embodiment of another example communication system is illustrated in which the methods and apparatus described and claimed herein may be implemented. DETAILED DESCRIPTION
[0024] First, as used herein, a capillary device refers to a device connected to a 3GPP network via a user equipment (UE) acting as a gateway or repeater. A capillary device may or may not have a subscriber identity module (SIM). For example, examples of capillary devices include wearable sensors and smart home devices (such as door locks and smart appliances). A user may refer to a person or device with an identity that can be separated from any subscription. As used herein, unless otherwise specified, subscriber and subscription may be used interchangeably without limitation.
[0025] Turning now to the protocol data unit (PDU) procedures, 5G registration, PDU establishment, and service request procedures can be used to activate, reactivate, and deactivate PDU sessions. Table 1 below shows example information about these procedures and the configuration update procedure.
[0026] Table 1. Registration, PDU creation, service request and configuration update process
[0027]
[0028]
[0029] 5G networks support a feature known as asynchronous type communication. When asynchronous type communication is enabled and the Policy Control Function (PCF), User Data Management (UDM), or Short Message Service – Service Center (SMS-SC) sends something to a given UE, the Access and Mobility Management Function (AMF) holds the message until the UE becomes CM-CONNECTED (instead of paging the UE).
[0030] Regarding authentication with the 5G Core Network (5GC), Figure 1 An example of 5G UE authentication is depicted. The AMF may invoke the Nausf_UEAuthentication_Authenticate procedure during UE registration to authenticate the UE using the UE's Subscription Permanent Identifier (SUPI) (e.g., IMSI).
[0031] A network slice may be identified using a single network slice selection assistance information (S-NSSAI). The S-NSSAI may consist of a slice / service type (SST) and a slice distinguisher (SD). NSSAI is a collection of S-NSSAIs. There are different types of NSSAI. The configured NSSAI is the NSSAI that a given UE is configured to use. The UE may have a different configured NSSAI in each PLMN. The configuration may include instructions for how to map the configured NSSAI to the NSSAI configured by the HPLMN. The UE provides the requested NSSAI to the network upon registration. The network may use the requested NSSAI to determine which network nodes should provide services to the UE and to determine which network slices the UE should be allowed to connect to. When registration is complete, the network provides the UE with the allowed NSSAI. The allowed NSSAI is a list of slices that the UE is allowed to access.
[0032] A PDU Session may be associated with an S-NSSAI and a Data Network Name (DNN). In the PDU Session Establishment Request sent to the network, the UE may provide a PDU Session Identifier (ID). The PDU Session ID is unique to each UE and is an identifier used to uniquely identify one of the PDU Sessions of the UE. The PDU Session ID may be stored in the User Data Management (UDM) to support handover between 3GPP and non-3GPP accesses when different PLMNs are used for both accesses.
[0033] UE Routing Selection Policy (URSP) is a policy that can be provided to the UE by the Policy Control Function (PCF) in the 5GC. The UE uses these policies to determine how to route outgoing services. In various examples, the service can be routed to an established PDU session, can be offloaded to a non-3GPP access outside the PDU session, or can trigger the establishment of a new PDU session. A given URSP may include an SSCMSP (SSC mode selection policy) used to map the service to a session and service continuity (SSC) mode. The URSP may include an NSSP (network slice selection policy) used to map the service to an S-NSSAI. The URSP may include a DNN selection policy used to map the service to a DN. The URSP may include an access network preference used to map the service to an access network type. A given UE may also have local preferences that can be used to determine how to treat the service. In some cases, local preferences take precedence over the URSP.
[0034] Turning now to the Extensible Authentication Protocol (EAP), EAP is a general authentication framework that can be used to implement a specific authentication method. EAP is a protocol that allows peers, authenticators, and authentication servers to negotiate which authentication method to use. The selected authentication method can then run inside the EAP protocol. EAP is defined in RFC 3748, which further describes the EAP packet format, procedures, and basic functions, such as the negotiation of the desired authentication mechanism. Figure 2 A block diagram showing the basic EAP architecture. EAP can use Radius or Diameter.
[0035] In some cases, it is not enough to describe the authentication mechanism as EAP, because there is some underlying authentication method. The IETF defines many EAP methods. For the purpose of example, it is assumed herein that the selected EAP method is EAP-AKA, which is based on UMTS-AKA and defined in RFC 4187, but it will be understood that other underlying authentication methods may be used. That is, according to various examples, embodiments may be implemented regardless of the selected EAP authentication method.
[0036] Turning now to the Protocol for Carrying Authentication for Network Access (PANA), EAP is designed as a link layer (layer 2) protocol, and PANA is a protocol that can be used to carry EAP messages over an IP network. Therefore, PANA can be a transport for EAP. PANA runs on top of the network (IP) layer. PANA is defined in RFC 5191. PANA allows dynamic service provider selection, supports various authentication methods, is suitable for roaming users, and is independent of link layer mechanisms.
[0037] In some cases, the 3GPP system or network is able to identify the device and the subscriber. For example, when the UE is attached to the network, the device (UE) can be identified by its permanent equipment identifier (PEI) (e.g., IMEI), and the subscriber associated with the UE can be identified by a subscription permanent identifier (SUPI) (e.g., IMSI). It is recognized herein that in some cases, the current 3GPP system cannot identify the user of the UE. It is also recognized herein that the 3GPP network treats each device based on the subscriber identity associated with the UE, so the network may not know who is using the UE. In some cases, for example, the UE can be shared by multiple users. In this example scenario, it is recognized herein that the 3GPP system cannot identify the person using the UE, and therefore different value-added services (e.g., parental control) cannot be applied when the UE is used by someone other than the subscriber (e.g., the subscriber's child).
[0038] It is also recognized herein that solving the technical problem of identifying a user can be valuable in the Internet of Things (IoT). For example, reference Figure 3 , a capillary device 302 such as a wearable device or a smart home appliance (without a SIM) may connect to a remote server 304 or relay to a core network 308 by using a UE 306 as a gateway. However, the user of the capillary device 302 may not be a subscriber associated with the UE 306. For example, a medical device 302 worn by a patient may connect to the Internet 308 using a friend's UE 306. When the UE 306 sends data to the network 308, the 3GPP system (e.g., the core network 308) may need to be able to authenticate and authorize the user identity associated with the capillary device 302, identify which traffic is coming from the capillary device 302, and apply different services / policies to the traffic coming from the capillary device 302 than to the traffic generated by applications hosted on the UE 306.
[0039] Among other technical problems, various embodiments described herein solve the Figure 3 Illustrated problem. For example, in the example, the core network (e.g., 3GPP 5GC) can identify a user. A user can refer to a person or device that has an identity that is separate (e.g., independent) from a subscription used to carry a service. In addition, if a UE is being used to send a service to a 5GC, the user can have an identity that is separate from the UE. Unless otherwise stated, user identity and 3GPP user identity can be used interchangeably in this document without limitation. In addition, unless otherwise stated, core network or 5GC can be used interchangeably in this document without limitation.
[0040] A 3GPP user identity may identify a user and a mobile network operator (MNO) associated with the user. The MNO may have a business relationship with the user. The MNO may be responsible for authenticating and authorizing user requests, and may be responsible for maintaining (one or more) information records associated with the user. The maintained information records are discussed further herein.
[0041] In the example, because the 3GPP user identity identifies at least two entities (the user and the MNO), it can have two parts. For example, its format can be: user-name@mno-name. The user-name can be an alphanumeric string that resolves to the user identity. The mno-name can be an alphanumeric string that resolves to the MNO identity. The MNO identity can consist of an MCC (Mobile Country Code) and an MCN (Mobile Network Code).
[0042] There can be different formats of 3GPP user identities. For example, an external format can be used on interfaces outside the 5GC, while an internal format can be used on interfaces inside the 5GC. When a message crosses the 5GC boundary, a parsing or conversion function at the edge of the 5GC can convert the 3GPP user identity between internal and external.
[0043] There may also be different types of 3GPP user identities. An example type of 3GPP user identity may identify a person. The person may then use this identity each time he or she accesses the 5GC, regardless of which device he or she uses to access the 5GC. For example, a 3GPP user identity may identify a child. When the child accesses the 5GC from his or her mother's UE, father's UE, or friend's UE, he or she may use the same 3GPP user identity.
[0044] Another type of 3GPP user identity can identify a non-3GPP device. For example, in some cases, a 3GPP user identity may be associated only with a specific non-3GPP device (e.g., a smart watch).
[0045] The format of the 3GPP user identity or the fields having the 3GPP user identity may identify what type of user (eg, user or device) the 3GPP user identity represents. Thus, in some examples, user and device may be used interchangeably herein.
[0046] The 3GPP user identity format may be further extended with a field (e.g., a third field) that identifies the device or subscription being used to access the system. For example, a user identity may have the following format: user-name.additional-field@mno-name. In this example, the additional-field identifies the device (e.g., PEI) or subscription (e.g., IMSI or external identifier) that the user is using to access the 3GPP system. The additional-field may be useful for situations where the user-name may be device- or subscription-specific. For example, a device or subscription may be configured to support certain user-names.
[0047] The 3GPP user identity format may be further extended with another field (e.g., a fourth field) that identifies the role of the user. As an example, the role of a user may be a standard user, a guest user, or an administrator user. A standard user may be a user that the MNO can identify. An administrator user may be a user that the MNO can identify but has additional privileges. For example, an administrator user may require a different level of authentication than users indicating other roles. An administrator user may be allowed access to special types of slices. For example, an administrator user is allowed access to slices with special network diagnostic capabilities. A guest user may be a user that the MNO cannot identify, but the device or subscription owner may be willing to host the guest user's business. For example, if the guest user's business comes from a UE with a SUPI, the subscription information associated with the SUPI may indicate that it is willing to sponsor business for the guest user or certain guest users.
[0048] There may also be internal and external 3GPP user identities. In the example, the internal 3GPP user identity is generally not exposed outside the 3GPP system, and the external 3GPP user identity will be used when accessing the system from the outside (for example, via a third-party application function (AF) or UE). A network function (NF) (such as an AMF, UDM / UDR, or a network exposure function (NEF)) can convert an external 3GPP user identity into an internal 3GPP user identity. The internal 3GPP user identity can be a type of SUPI. Although the examples described herein illustrate how to use NEF to interface between 5GC and a given AF, it will be understood that the examples are presented to facilitate the description of the disclosed subject matter and are not intended to limit the scope of the present disclosure. Other devices, systems, and configurations may be used to implement the embodiments disclosed herein, and all such embodiments are contemplated to be within the scope of the present disclosure. For example, an AAA proxy may be used as an interface between a given AF as an AAA server and a 5GC.
[0049] The 3GPP user identity format can be further extended with another field (e.g., a fifth field) that provides biometric data that has been captured by the UE. For example, the fifth field can indicate that the field includes a specific type of biometric data (e.g., an eye / retina scan result or a fingerprint scan result) and can also indicate the result (e.g., a number or value representing the eye / retina scan result or the fingerprint scan result). When this field is provided to the 5GC, it can be considered as part of the user identity. In the example, the 5GC will not recognize the user unless this field matches or is close to the expected value stored in the network for the user. Alternatively, the information in this field can be considered as a value separate from the user identity and can be used by the 5GC to authenticate and authorize the user.
[0050] Turning now to information that may be stored in the network, the Unified Data Repository (UDR) stores subscription data. In an example, the UDR is enhanced to also store user data. For example, a UDR query may require a data set identifier. The data set identifier identifies a subscription or key (e.g., SUPI / IMSI), and what data from the subscription record is expected in response to the query. The UDR may be enhanced to support (via 3GPP User Identity) identifying the data set identifier of the user and what data from the user record is expected in response to the query. The user record may include the information listed in Table 2, which is presented by way of example and without limitation.
[0051] The network functions in the 5GC can access the information in the user record by directly querying the UDR or querying the UDR via the UDM. In the example, the UDR and UDM services are updated to allow the network function to query the information associated with the user. Alternatively, in another example, the user record can be stored in a repository separate from the UDR and accessed directly from the repository or via a front-end interface such as the UDM.
[0052] Table 2: Example user record information
[0053]
[0054]
[0055] To support the 3GPP user identities described herein, the subscription record may be updated to include one or more of the following new fields, which are presented in the example manner of Table 3 without limitation:
[0056] Table 3: Example subscription record information
[0057]
[0058]
[0059] We now discuss example scenarios in which 3GPP user identities may be used. In one example, a 3GPP device initiates a direct network connection. The 3GPP user identity may be used to access a 5G network using a 3GPP device that has been provisioned with a SIM and associated user credentials. For example, a smartphone may allow different users (e.g., a parent and a child) to log into the device. The smartphone may then indicate the 3GPP user identity to the 5GC network so that the network may adjust the services applied based on the 3GPP user identity. For example, parental controls may be applied to a service when using a child's 3GPP user identity.
[0060] In another example, a non-3GPP device initiates a direct network connection. A 3GPP user identity may be used to allow a non-3GPP device that may not provide a SIM or associated subscriber credentials to directly access the 5GC. A non-3GPP device (e.g., a Wi-Fi camera or a Wi-Fi tablet) may be connected to the 5GC via a non-3GPP interworking function (N3IWF). The owner of a 3GPP user identity may be able to use the 3GPP user identity to connect to the network via any number of devices (e.g., different Wi-Fi tablets), or in other examples, the 3GPP user identity may be associated with only a single device (e.g., a Wi-Fi camera).
[0061] In another example, a non-3GPP device has an indirect connection. A 3GPP user identity may be used to allow a non-3GPP device that may not provide a SIM or associated subscriber credentials to indirectly access 5GC via a 3GPP device. In some cases, a non-3GPP device (e.g., a Bluetooth medical monitoring device) may not have a subscriber credential associated with it, but it may have a 3GPP user identity. A 3GPP device (e.g., a smart phone) may have provided a SIM and associated subscriber credentials. In an example, when a non-3GPP device is connected to a 3GPP device, the 5GC network is able to authenticate the 3GPP user identity presented by the non-3GPP device. When authenticating, the user may also provide (one or more) user credentials to the network. In various examples, when a 3GPP device sends and receives a service associated with a non-3GPP device, the network is able to identify whether the service is associated with a non-3GPP device or a 3GPP device.
[0062] Another example of a capillary device connected to the 5GC via a 3GPP device is where a vehicle (such as a taxi) has an embedded UE that acts as a gateway for the capillary device. When a passenger enters the taxi, a medical monitoring device (e.g., a capillary device) attached to the passenger can connect to the gateway using a protocol such as WiFi or Bluetooth to obtain a connection to the 5GC and send data to a remote server. The 3GPP user identity and associated credentials can be provided to the GW (e.g., UE) via application layer messaging over the WiFi or Bluetooth connection, or a GUI in the vehicle can allow the passenger to provide the device 3GPP user identity and associated credentials directly to the GW (e.g., UE).
[0063] In some cases, a user may use his 3GPP user identity to contact a device and obtain services or data from the device. For example, a person may be using his laptop with a broadband connection. This person may try to contact a camera connected to a 3GPP 5GC so that he can view the video stream provided by the camera. The user may present his 3GPP user identity to the 5GC to gain access to the camera. Alternatively, the user may use a network application (e.g., AF / AS) to access the camera and provide the 3GPP user identity and (one or more) user credentials to the camera. The camera (UE) may then authenticate the 3GPP user identity.
[0064] refer to Figure 4 According to an example embodiment, a new 3GPP user identity authentication network function (3UIANF) 402 may be included in the 5GC 400. The 3UIANF 402 may expose a user identity authentication service that allows a requester (e.g., another NF) to request authentication of a user. The 3UIANF 402 may support different styles of user identity authentication. In one example, the 3UIANF 402 supports a request for an authenticated 3GPP user identity from the UE 404 via control plane (e.g., NAS) signaling. In another example, the 3UIANF 402 supports a request for an authenticated 3GPP user identity from the UE 400 via user plane (e.g., PANA over UDP) messaging. In yet another example, the 3UIANF 402 supports a request for an authenticated 3GPP user identity from an application function (AF) 405. This request may come from an API exposed by the NEF 406 over the N33 reference point. It will be understood that the functionality of 3U IANF 402 may alternatively be part of an authentication server function (AUSF), or may be provided by one or more network functions. For example, 3U IANF 402 may alternatively be deployed as AF 405 and its interaction with other NFs (e.g., AMF 408) may be routed via NEF 406.
[0065] After the user authentication is complete, the user record in the UDR 410 may be updated to indicate that the 3GPP user identity has been authenticated. Furthermore, if applicable, the SUPI and PEI associated with the device using the 3GPP user identity are recorded in the user record of the UDR 410. Additionally, if applicable (e.g., if the 3GPP user identity is connecting via a device with a subscription), the user record associated with the SUPI is updated to indicate that the 3GPP user identity is currently associated with the subscription. In some cases, for example, the fact that the 3GPP user identity is currently associated with the subscription may be retrieved later by other network functions (NFs) when authorizing a service request and / or when other NFs need to determine how to contact the user for a service (such as an MT short message service (SMS)). When the user accesses the network using the UE, the network may choose to update the allowed NSSAI and / or allowed LADN of the UE. For example, in some cases, the UE may only be allowed to access information slices with parental control enabled, or the UE may not be allowed to access certain enterprise information slices.
[0066] If the UE has not been authenticated with 5GC prior to the process of authenticating the 3GPP user identity, the output of the authentication process may be used to derive NAS security keys. This may be the case, for example, when the UE is connected via an RLOS connection.
[0067] If the UE has already been authenticated with the 5GC before the process of authenticating the 3GPP user identity, then in an example, the output of the authentication process is not used to derive the NAS security keys. This may be the case, for example, when the UE has already registered with the network and only the 3GPP user identity is being authenticated.
[0068] Continue to refer Figure 4 The Nc interface may be used by the 3U IANF 402 to obtain a user record from the UDM / UDR 410. The Nb interface may be used to receive an authentication request initiated by the AF 405 from the NE 406. The Na interface may be used to receive an authentication request initiated by a user from the AMF 408. The Na interface may also be used to authenticate a user via control plane signaling. The N6 or Nd interface may be used to authenticate a user via user plane signaling.
[0069] In an example, the 3U IANF 402 may support authentication of a user identity via control plane signaling. This service may be similar to, but different from, the UE authentication service provided by the AUSF and described herein. For example, in addition to the SUPI, the input to the service may also include a 3GPP user identity. The input may include the PEI of the device hosting the 3GPP user identity. The 3U IANF 402 may retrieve necessary user record information (e.g., see Table 2) from the UDR 410 and confirm that the user is accessing the network 400 from an allowed access network name, allowed access type, allowed location, and not from a restricted location. If the authentication process is triggered by a request sent to the network by a device associated with a subscription, the request may include the SUPI (or PEI). The 3U IANF 402 may check whether the user information indicates that the 3GPP user identity is associated with the SUPI, or whether the subscription record associated with the SUPI (or PEI) indicates that it is associated with the 3GPP user identity.
[0070] Also refer to Figure 5 , shows an example of a user authentication process based on an example control plane. Figure 5 and 6 An example system 500 is shown that includes a UE 404, a requestor NF 502, a 3UIANF 402, and a UDM / UDR 410. It will be appreciated that the example system 500 is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of the present disclosure. Figure 5 and 6 In addition to or in lieu of systems such as those shown in Figure 5 and 6 Other devices, systems, and configurations may also be used to implement the embodiments disclosed herein, and all such embodiments are contemplated to be within the scope of the present disclosure. Figure 5 According to the example shown, a 3GPP user identity may be associated with a device that is making an initial connection to a 5GC network. The device may be a non-3GPP device that is making an initial registration request to the network, and the device does not have a SUPI. Instead, it makes an initial registration request with a 3GPP user identity.
[0071] Still reference Figure 5According to the example shown, at 1, the requester NF 502 starts the process of authenticating the user. Examples of initiating events include, but are not limited to: receiving a registration request including a 3GPP user identity; receiving a PDU session establishment, release or modification request including a 3GPP user identity; receiving a service request including a 3GPP user identity; and receiving an API request including a 3GPP user identity (e.g., NEF 406 receives an API request from AF). In the example, the requester 502 is AMF 408. At 2, the requester sends an authentication request to 3UIANF 402. The request may include a requester ID and a 3GPP user identity. The request may also include a SUPI and / or PEI associated with the UE 404 that initiated the request.
[0072] At 3, 3U IANF 402 obtains the necessary authentication information from UDM / UDR 410. The request to UDM / UDR 410 may include a 3GPP user identity. 3U IANF 402 may send the request to more than one UDM / UDR. For example, it may be necessary to obtain information based on a 3GPP user identity from one UDM / UDR and obtain information based on SUPI from another UDM / UDR. For example, 3U IANF 402 may need to check subscription information (associated with SUPI) to determine whether the subscriber allows user access, and 3U IANF may need to check user information (associated with 3GPP user identity) to obtain information necessary to authenticate the user. In some cases, 3U IANF 402 may instead query a third-party AF to authenticate and authorize the user. 3U IANF 402 may determine which third-party AF to query based on the information obtained from UDM / UDR 410. The request may be sent to the AF via the NEF. The identity may also be obtained from the UDM / UDR. At 4, the UDM(s) (eg, UDM / UDR 410) respond to the 3U IANF request(s).
[0073] Based on the authentication information obtained at 4, 3U IANF 402 selects an authentication method and performs user authentication. Depending on the authentication method, the user authentication process may involve different round trips between UE 404 and 3U IANF 402. For example, if the user is a non-human device, it may have the necessary logic and security credentials to rely on a credential-based authentication exchange with the core network. Alternatively, if the user is human, network authentication may be assumed to be implicit if the UE that the user is using is authenticated, and user authentication may be achieved by sending the user to a captive portal where the user can enter credential information. According to the example, at 6, 3U IANF 402 responds to requester 502 with an indication of the authentication result. 3U IANF 402 may provide the security key material used, which may be used by requester 502 to derive (one or more) other security keys.
[0074] 3U IANF 402 may also support authentication of user identity via user plane signaling. The user plane approach may be well suited for situations where the UE has registered with the network using its SUPI and is authenticating the user of the UE. The user plane approach may also be well suited for situations where the UE is allowed to attach to the network without authentication and be able to obtain a RLOS connection. The RLOS connection may then be used to communicate with the 3U IANF 402 and authenticate the user. The RLOS connection may be established via well-known DNN and / or S-NSSAI slices, which allows the UE to obtain an IP connection to the 3U IANF.
[0075] When the user plane method is used, the UE can send an authentication request to the AMF. The authentication request includes the 3GPP user identity. The AMF can call the 3UI ANF authentication service. In this example, the interaction between the 3UI ANF and the UE is not via NAS signaling. More specifically, the interaction with the UE will be via the user plane. The user plane interaction can consist of an authentication process carried in the EAP signaling over PANA. In this user plane scenario, the 3UI ANF 402 can be an EAP authenticator, the user can be an EAP peer, and the authentication server can be the UDM 410.
[0076] refer to Figure 6 , shows an example where a user can be authenticated via user plane signaling. The process shown can be initiated via control plane signaling. According to the example shown, at 1, an initiation event causes the requester NF 502 to start the process of authenticating the user, as described above with reference to Figure 5 At 2, the requester 502 sends an authentication request to the 3UIANF 402, as described above with reference to Figure 5At 3, 3UIANF 402 obtains the necessary authentication information from UDM / UDR 410, as described above with reference to Figure 5 At 4, (one or more) UDMs (e.g., UDM 410) respond to (one or more) 3UIANF 402 requests, as referenced Figure 5 At 5, based on the authentication information obtained at 4, 3UIANF 402 responds to the requestor 502 with an IP address and port number that the user can contact to perform authentication. In the example, instead of an IP address, an FQDN can be provided. This message can also indicate a preferred authentication method (e.g., EAP, AKA-based, PANA, etc.).
[0077] Still reference Figure 6 According to the example shown, at 6, the requester 502 forwards the information received at 5 to the user. In some cases, this request can be sent from the 3U IANF 402 to the user in a NAS message. For example, the request can be sent in a NAS notification or device trigger, which includes a 3GPP user identifier and a trigger purpose. The trigger purpose can specify a user-based action that the user should perform (e.g., refresh user login, user friend connection request, etc.). The message can include the 3GPP user identity and the IP address and port number provided at 5. If the initiating event (at 1) is the result of a user plane request from the UE, then in some examples, this message can be a user plane response. If the initiating event (at 1) is the result of an API request, then in some cases, this message can be sent to the API caller instead of the UE, and step 7 can occur between the API caller and the 3U IANF 402.
[0078] At 7, UE 404 and 3U IANF 402 perform user authentication. This process can be initiated by UE 404 sending a PANA client-initiated (PANA-Client-Initiation, PCI) message to 3U IANF 402. In the example, UE 404 sends a message to the IP address and port number provided at 6. When the authentication process is completed, (one or more) security keys that can be used for subsequent user plane messaging associated with the user can be derived. UE 404 can create a new PDU session, modify the PDU session, or send a service request before sending the PANA client-initiated (PCI) message. If other authentication messages are used, then in some cases, the message may be different from the PCI message. According to the example, at 8, a notification is sent to NF requester 502 to notify it of the completion (and success or failure) of user authentication.
[0079] The services of 3U IANF 402 may be exposed to third parties directly, via NEF 406, or via some other API exposure functionality. This may be useful when a 3GPP user identity is used to access third party services. NEF 406 may expose an API that allows a third party AF to request that the network authenticate the user on behalf of the AF. For example, NEF 406 may expose an API that allows the AF to provide a 3GPP user identity and request that the network authenticate the 3GPP user identity. The request may include a reference ID known to the user and the AF.
[0080] Can be modified Figure 6 The example depicted is such that the initiating event is a request from an API exposed function (e.g., NEF). In the example, the request may include a 3GPP user identity, an AF identifier, and a reference ID. In addition, the request may include an indication of the location of the device or UE that the 3GPP user identity is using to access the 5G system. It may also be modified Figure 6 Steps 2-5 of 3UIANF 402 enable AF to check whether it is authorized to communicate with the user. Figure 6 Steps 6 and / or 7 are modified to include a reference ID so that the user knows which AF initiated the authentication request and can therefore determine whether it wants to be authenticated. Figure 6 )When receiving the completion notification, the API exposure function can send a completion notification to AF.
[0081] Thus, as described above, a device (e.g., 3UI ANF 402) may receive an authentication request from a requester node, and the authentication request may include an identity associated with the requester node and a user identity associated with a user of a UE communicating with the requester node. In response to the authentication request, the device may obtain information associated with the user identity. Based on the information, the device may perform authentication of a user of a user equipment, wherein the user identity is independent of the device identity associated with the user equipment, thereby allowing the user to access the network after authentication. The user may be a capillary device communicating with the user equipment, so that the user identity identifies the capillary device. Alternatively, the user may be a first person, so that the user identity identifies the first person, and the device identity indicates a second person different from the first person. The authentication request may include at least one of a subscription permanent identifier of the user equipment or a permanent equipment identifier of the user equipment. Information associated with the user identity may be obtained from a unified data repository. For example, information associated with the user identity may be obtained from multiple unified data repositories. The information associated with the user identity obtained may indicate restrictions associated with network access, which are associated with at least one of the user's location, the user's equipment identifier, the access type, the data network, the network function, one or more network slices, or time. The obtained information may also include a preferred mechanism for authentication, or one or more credentials for authentication. In some examples, the obtained information associated with the user identity includes subscription information associated with a subscription of the user equipment, and the subscription information may indicate at least one of the following: one or more user identities associated with the subscription, one or more user identities allowed to access the network via the subscription, one or more user identities prohibited from accessing the network via the subscription, whether a guest user is allowed to access the network via the subscription, and one or more specific guest users allowed to access the network via the subscription.
[0082] As described above, the user identity may indicate a mobile network operator associated with the user, a user equipment with which the user communicates, or a subscription for network access. The user identity may be formatted according to an internal format that is different from the external format of the user identity used by the user equipment. In an example, in response to the user equipment sending an initial request to the network via a requestor node, an authentication request is received from the requestor node, and the initial request may include the user identity. In addition, the initial request may be, for example, one of the following: a registration request; a PDU session establishment, release, or modification request; a service request; or an API request. In an example, the requestor node includes access and mobility management functions. In addition, performing authentication of the user may include determining that the user equipment is authenticated and directing the user to a mandatory portal so that the user can enter credential information at the mandatory portal.
[0083] In some cases, performing authentication of the user includes sending an IP address and port number to the requester node for the user to contact. In another example, performing authentication of the user includes receiving a PCI message from the user at the IP address and port number to initiate authentication. The device can also derive one or more security keys for subsequent user plane messages associated with the user. In an example, performing authentication of the user includes sending a message indicating a preferred authentication method for authentication to the requester node. In another example, in response to the user equipment sending a user plane request to the network via the requester node, an authentication request is received from the requester node.
[0084] Described herein are example methods that a user may use to obtain services with a 3GPP user identity when accessing a network using a UE. Prior to using one of these methods, in some cases, the UE may receive broadcast information indicating that the network supports connection with a 3GPP user identity. Also described herein are methods for IoT devices (e.g., wearable devices and smart home devices) having 3GPP user identities associated therewith to connect to a UE (e.g., smart phones and gateways). The UE may then use the methods now described to allow the IoT devices to obtain network access / network services.
[0085] The device may display a GUI, such as example GUI 1000 (see Fig.10 ), the GUI allows the device owner to enter the names of people who are allowed to use the device. The device owner can also enter a 3GPP user identity associated with each user. It will be understood that, for example, when setting up a user's account, the network can identify the 3GPP user identity based on some previous registration of the 3GPP user identity. In addition, the device can allow the owner and user to configure biometric data associated with each user. For example, the device can be configured to recognize the fingerprint of each user via a fingerprint sensor, and can be configured to recognize the physical characteristics of each user via a camera. Each user can also have an alphanumeric password configured locally on the device. The user can enter or speak the alphanumeric password to identify him / herself when they unlock or begin to use the device. These techniques can be considered to unlock the device.
[0086] When a new user unlocks the device, the following actions of the UE may be triggered, presented in an exemplary manner but not limited to: a general registration process; a PDU session establishment, modification and / or release process; and a service request. During these processes, each NF may record the user identity in the CDR so that the appropriate charges may be charged to the subscriber and user when the CDR is processed in the billing domain. When a new user uses the UE to access the 5G network, the PCF may send a new policy to the UE to indicate how the traffic from the user should be treated.
[0087] Reference now Figure 7 There are multiple scenarios where a given UE can trigger a registration request. For example, an application-level activity that triggers registration can be when a user unlocks the UE, starts a specific application, or logs into a specific application. The user can be the same or a different user than the last user who unlocked the UE, used the application, or logged into the application. Figure 7 The general registration process is shown. Figure 7 Modifications to the general process according to various embodiments are discussed.
[0088] At 1, the UE sends a registration procedure to the AMF. The registration procedure may be caused or triggered when the user unlocks the device. The registration procedure includes various parameters such as: registration type, SUCI or 5G-GUTI or PEI, security parameters, requested NSSAI, [mapping of requested NSSAI], UE 5GC capabilities, PDU session state, list of PDU sessions to be activated, follow-up requirements, MICO mode preferences, requested DRX parameters. According to an example embodiment, a 3GPP user identity, an indication that the UE supports a user identity feature (and may also indicate that a user identity will be provided), and / or a parameter indicating a list of allowed users may be added to the message at 1 as an optional field. The 3GPP user identity in this example refers to the user identity of the user who unlocked the device. If the identity does not exist, the network may fall back to the default behavior and assume that the device user is a subscriber associated with the UE. Alternatively, this may be a list of users currently associated with the device. For example, the device may be a wall-mounted monitor, and multiple users may be in the room where the monitor is located. With respect to the list of allowed users, if registration is triggered in response to a page, the registration request message may identify a list of users currently associated with the device.
[0089] The Registration Type field allows the UE to indicate whether the UE wants to perform an initial registration, a mobility registration, an emergency registration, or a periodic registration update. In an example, the Registration Type field is updated or a new field is added to allow the UE to indicate whether the purpose of the registration is to add a new user association, remove a user association, or switch a user association. If the Registration Type field supports this indication, it can be enhanced so that it can be a bit field that allows the UE to indicate multiple registration reasons. Example registration reasons include emergency and new user, which may occur when a user unlocks the UE for an emergency phone call. The list of PDU sessions to be activated can be determined at least in part by the UE based on which user unlocked the UE. The UE can determine the requested NSSAI based at least in part on which user unlocked the phone. For example, a policy in the UE may indicate that certain users can only connect to slices that provide parental control services, or that only certain users are allowed to connect to specific enterprise slices.
[0090] If multiple users use the device simultaneously, the registration request may include multiple 3GPP user identities and multiple requested NSSAIs, where each requested NSSAI may be associated with a 3GPP user identity. Alternatively, the UE may provide a single NSSAI that is an aggregation of the NSSAIs associated with the 3GPP user identities in the request.
[0091] In some cases, the encoding of the PDU session status is enhanced to allow the UE to indicate the status of the PDU session for users other than the user(s) associated with this registration request. For example, the UE may indicate to the network that PDU sessions associated with other users should be released or maintained. Therefore, in some cases, this field is enhanced to indicate that a PDU session is suspended, paused or deleted.
[0092] The registration request at 1 may include an indication that the request is for RLOS network services and authentication with a 3GPP user identity. The registration request may include a PEI identifying the UE. In some examples, the PEI may be something other than an IMEI, such as a MAC address, for example.
[0093] The indication that the request is for RLOS network services and authentication with a 3GPP user identity may be part of the NSSAI provided by the UE to the network in a registration request. For example, the NSSAI name may indicate that the UE wishes to gain access to services that may be used to authenticate the device's 3GPP user identity.
[0094] In some examples, a separate list of PDU session identifiers for each user on the UE is maintained. In some cases, the format of the PDU session identifier can be enhanced to be a concatenation of a 3GPP user identifier and a numerical value indicating the PDU session, making the PDU session identifier a unique value for each user per UE.
[0095] When a registration request is sent, the request may include the user's PDU session identifier that was last used on a different UE. The request may also indicate which UE (e.g., PEI) or subscription (e.g., IMSI, GUTI, or external identifier) was last used to establish a PDU with the network. Alternatively, when a user establishes a PDU session, the network may provide a PDU session reference ID to the UE and the user so that when the user reconnects from the same or a different device, the user can use the reference ID to reestablish the connection. A PDU session establishment, registration, or service request may indicate that such a PDU session type that supports a reference ID is desired.
[0096] Still reference Figure 7, at 9, the (one or more) user identities provided at 1 may be authenticated as described above. Alternatively, according to an example, if the UE has not yet been authenticated, a 2-step authentication may be performed. In the example, the UE is authenticated, and if the UE authentication is successful, the user is then authenticated. If the UE is not authenticated, a registration rejection message may be notified to the UE and the user, the registration rejection message indicating the reason for rejecting the authentication.
[0097] At 12, the N5g-eir_EquipmentIdentityCheck_Get identity request service may be enhanced so that when the AMF checks the PEI, it may also indicate the 3GPP user identity(ies) that attempted to use the device associated with the PEI. The response from the EIR may indicate whether each user is allowed to use the device associated with the PEI.
[0098] As an alternative to checking access authorization as part of the authentication performed at 9, authorization may also be verified independently. The AMF may use the associated access type to check whether the user is accessing the UE. The AMF may also check whether the UE is on the associated SUPI(s) (or associated PEI list(s)) and in the associated location(s).
[0099] At 13, the AMF selects a UDM based on the SUPI. The UDM may select a UDR instance. In some examples, the AMF selects an additional UDM. Each 3GPP user identity may require the selection of a UDM. The UDM discovery function may accept a 3GPP user identity or a field within a 3GPP user identity as input to be used to determine the UDM. At 14, the AMF registers with the UDM using the Nudm_UECM_Registration service. In the example, this service allows the AMF to indicate which users are associated with the registration. In addition, the AMF may contact other UDMs to inform them that the user is using a UE reachable via the AMF. In some cases, when the AMF contacts a UDM located in a different PLMN, it will not notify the UDM of users that are not associated with a different PLMN. The updated Nudm_UECM_Registration service or a new service may be used to notify the UDM of users. At 14, the AMF may also need to contact (one or more) UDMs to inform them that (one or more) users are no longer reachable on the UE via the AMF. This may be performed using the updated Nudm_UECM_DeregistrationNotification service or a new service.
[0100] In some cases, network policy may dictate whether the UDM / UDR should indicate to the AMF whether a user is already connected via a different subscription or device, and whether to allow or disallow the user's connection when this occurs.
[0101] Still reference Figure 7 , at 15, the AMF may select a PCF. Currently, the PCF is selected based on the UE or PDU session. According to an example embodiment, the PCF may also be selected based on a 3GPP user identity. When the AMF discovers the PCF with the NRF, it may provide the NRF with a 3GPP user identity, which may be used to determine where policies associated with the user may be stored.
[0102] At 16, the AMF obtains the policy from the PCF by calling the Npcf_AMPolicyControlGet service. When the service is called, the service may be updated to allow the AMF to indicate the 3GPP user identity instead of the SUPI or in addition to the SUPI. Moreover, the PEI may be provided to the PCF. When the device associated with the user does not have a SUPI, the PEI may indicate which policies should be applied. At 17, the AMF calls the Namf_EventExposure_Subscribe service to subscribe to notifications about changes in policies associated with the UE. In the example, the AMF may provide a 3GPP user identity in order to subscribe to notifications about policy changes related to the user. At 18, the AMF calls the Nsmf_PDUSession_UpdateSMContext service with (one or more) SMFs to activate the PDU sessions in the "list of PDU sessions to be activated". According to the example, the service is enhanced to allow the AMF to indicate the 3GPP user identity instead of the SUPI or in addition to the SUPI. The AMF may also call the Nsmf_PDUSession_UpdateSMContext service with (one or more) SMFs to suspend or suspend a PDU session that is not associated with the user currently using the UE. Alternatively, in an example, a new service is created for suspending or terminating a PDU session.
[0103] Still reference Figure 7, at 22, the AMF responds to the UE with a Registration Accept message. The response indicates for each PDU session whether it is rejected. If the rejection is because the user is not allowed to access the network from the UE, or because there are already too many users connected to the network from the UE, the message indicates this to the UE in the cause value. If the registration is not allowed because some of the indicated (one or more) 3GPP user identities are not allowed to access the network, because some users are not allowed to access the network from the UE, because there are already too many users connected to the network from the UE and / or the user is not allowed to access the network with the subscription associated with the device, then these reasons are indicated to the UE.
[0104] Reference now Figure 8 There are various scenarios where a UE may trigger a service request. For example, an application-level activity that triggers a service request may be when a user unlocks the UE. The user may be the same or a different user than the last user that has unlocked the UE. A service request may be triggered by a NAS notification message. The NAS notification message may be enhanced to include a 3GPP user identity. By receiving the 3GPP user identity, the UE may know which user is associated with the (one or more) PDU sessions that need to be established in a subsequent service request. Figure 8 The general UE-triggered service request process is shown. Figure 8 Modifications to the general process according to various embodiments are discussed.
[0105] Here, the UE sends an N2 service request to the AMF. When the user unlocks the device, the service request may be caused or triggered. The service request may include the following parameters: a list of PDU sessions to be activated, a list of allowed PDU sessions, security parameters, and PDU session status. As an example but not as a limitation, the service request may also include a 3GPP user identity, a list of allowed users, a user flag, and a list of PDU sessions to be activated. The 3GPP user identity refers to the user identity of the user who unlocked the device. If it does not exist, then in the example, the network can fall back to the default behavior and assume that the device user is a subscriber associated with the UE. Alternatively, in another example, this may be a list of users currently associated with the device. For example, the device may be a wall-mounted monitor, and multiple users may be in the room where the monitor is located. With respect to the list of allowed users, if the service request is triggered in response to paging, the service request message may identify a list of users currently associated with the device. In the example, the purpose of the service request is to add a new user association, remove a user association, or switch a user association. When the flag indicates that the UE expects to switch users, the flag may be interpreted as an indication that PDU sessions associated with other users should be terminated. The UE may provide a list of PDU sessions to be activated for each allowed user. This may be useful, for example, when a service request is in response to a page. The network may have paged the UE because it knows that the user it needs to contact was recently associated with the UE. However, at the time of paging, a user may or may not be associated with the UE, or multiple users may be associated with the UE (e.g., in the smart TV example discussed earlier, in the case of a smart home control panel, etc.).
[0106] At 3, the request may trigger a process in which the user identity needs to be authenticated. When this is the case, the process described in this document may be used to authenticate the user identity. At 4, the AMF determines which SMF(s) are associated with the PDU session(s) to be activated and calls Nsmf_PDUSession_UpdateSMContext with each SMF to request service with an operation type set to "UP Activation". This message may include the following parameters: PDU Session ID, Operation Type, UE Location Information, Access Type. In various examples, by way of example and not limitation, this message may also include:
[0107] · 3GPP User Identity: This is the user identity indicated by the UE.
[0108] • List of allowed users: This is the list of allowed users indicated by the UE.
[0109] User Identity: This is the user identity indicated by the UE.
[0110] If provided by the UE, the AMF may provide a list of the list of PDU Sessions to be activated per allowed user.
[0111] The AMF may determine to release some PDU sessions. For example, if the UE indicates that the request is a request to switch a user associated with the UE, then the AMF may decide to release the PDU sessions associated with other users. Similarly, if the request indicates that the request is to remove a user, then the AMF may decide to release the PDU sessions associated with the removed user. The AMF determines which SMF(s) are associated with the PDU session(s) to be released and calls Nsmf_PDUSession_UpdateSMContext with each SMF to request the service with the "Operation Type" set to "UP Deactivate". This message already includes the following parameters: PDU Session ID, Operation Type, UE Location Information, Access Type. In various examples, the message may also include a cause value indicating that the session is being deactivated because the user is no longer associated with the UE.
[0112] If the message from the UE is triggered in response to paging, and the user for which the UE is being paged is not in the list of allowed users provided by the UE and / or the PDU session for which the UE is being paged is not in the list of allowed PDU sessions, then the AMF informs the SMF that the user plane for the PDU session cannot be reactivated. The notification to the SMF may include an indication that the user is no longer associated with the UE. If the AMF knows which UE the user is associated with, then the AMF may provide this information to the SMF so that the SMF can attempt to page the user at another UE.
[0113] In some examples, a separate list of PDU session identifiers for each user on the UE is maintained. In another example, the format of the PDU session identifier can be optionally updated to be a concatenation of a 3GPP user identifier and a numerical value indicating the PDU session, making the PDU session identifier a unique value per user per UE. If a user is making a service request from a UE and the user is not yet associated with the UE, the AMF may update the user's record and / or the subscriber's record to record the fact that the user is reachable at the UE.
[0114] Still reference Figure 8, at 11, the SMF responds to the AMF. The response may include the following parameters: PDU Session ID, (one or more) QFI, (one or more) QoS profiles, CN N3 tunnel information, S-NSSAI, User Plane Security Enforcement, and reason. Based on local policies obtained from the PCF or subscriber or user policies, the SMF may indicate whether a PDU session not associated with the user should be deactivated. At 13, the AMF responds to the UE (via the RAN). If the response indicates that the PDU session is rejected and if the rejection is because the user is not allowed to access the network from the UE, or because there are already too many users connected to the network from the UE, the message may indicate this to the UE in the cause value.
[0115] Reference now Fig. 9 There are various descriptions in which the UE may trigger a PDU session establishment request. For example, the application-level activity that triggers the service request may be when the user unlocks the UE, starts a specific application, or logs into a specific application. The user may be the same or different user as the last user who has unlocked the UE, used the application, or logged into the application. Fig. 9 The general UE-requested PDU session establishment process is shown. Fig. 9 Modifications to the general procedure according to various embodiments in which different users may use the same UE are discussed.
[0116] At 1, the UE sends a PDU session establishment request to the AMF. The request may be caused or triggered when the user unlocks the device. The PDU session establishment request may include the following parameters:
[0117] (One or more) S-NSSAI, DNN, PDU Session ID, Request Type, Old PDU Session ID, N1 SM container (PDU Session Establishment Request). The message may also include a 3GPP User Identity, which is the user identity of the user whose application layer activity triggered the request. If it is not present, then in the example, the network can fall back to the default behavior and assume that the device user is the subscriber associated with the UE. Alternatively, in another example, the PDU Session ID or S-NSSAI may include or be associated with a 3GPP User Identity, thereby providing a PDU Session ID to identify which user the session is associated with. The request may trigger a process that requires authentication of the user identity. When this is the case, the user identity can be authenticated using the examples described herein.
[0118] At 2, the AMF selects the SMF. When the AMF discovers the SMF with the NRF, it can provide the NRF with a 3GPP user identity, which can be used to determine where policies associated with the user can be stored. At 3, the AMF calls the Nsmf_PDUSession_CreateSMContext or Nsmf_PDUSession_UpdateSMContext service. These services can be updated with the same updates described above for the Nsmf_PDUSession_UpdateSMContext service. At 4, the SMF registers itself as a service node associated with the UE. In the example, the Nudm_UECM_Registration service is updated so that the SMF can also provide a 3GPP user identity associated with the PDU session. In some cases, the SMF may need to notify at least two different UDMs that it is servicing a PDU session. For example, the SMF may need to notify one UDM associated with the UE subscription and one UDM associated with the user. At 7, the SMF performs PCF selection, which may be based on reference Figure 7 Step 15 described above is modified. At 8, the SMF performs UPF selection. When the SMF determines the UPF using the NRF, it can provide the NRF with a 3GPP user identity, which can be used to determine where the policies associated with the user can be stored. At 13, the AMF responds to the UE (via the RAN). If the response indicates that the PDU session is rejected, and the rejection is because the user is not allowed to access the network from the UE, or because there are already too many users connected to the network from the UE, then the message can indicate this to the UE in the cause value.
[0119] As discussed above, non-3GPP devices without subscription credentials can connect to the UE in order to access the 5G network. For example, the device can be a smart watch, tablet, health monitoring device, door lock, smart appliance, etc. The UE can be a smart phone, smart home control panel, gateway, etc. The connection between the device and the UE can be made using protocols such as Wi-Fi, PC5, Bluetooth, etc.
[0120] The device may use its connection to the UE to send a connection and authentication request to the UE. The connection and authentication request is a request to connect to the UE so that the UE can act as a relay between the 5G network and the device. The connection and authentication request includes a 3GPP user identity associated with the device. The request may also include a description of which network services the device wants to access (e.g., an NSSAI or a value to be mapped to the NSSAI by the UE). The request may also include a device identifier associated with the device (e.g., a MAC address).
[0121] If the device does not provide the UE with a 3GPP user identity, the UE may provide the GUI 1000 ( Fig.10 ), the GUI 1000 allows a person to enter a 3GPP user identity associated with a device. For example, when a device is paired with a UE (e.g., Bluetooth pairing), a person may be able to enter a 3GPP user identity associated with the UE. Thus, the UE will then know the association of the 3GPP user identity with the device and the associated device identifier (e.g., MAC address) of the device. The user interface 1000 may display a 3GPP user identity associated with the device. Fig.10 , but it will be appreciated that any number of GUIs and any GUI designs may be implemented as desired. It will be appreciated that the examples of user identity information shown are not exhaustive, and alternative or additional information may be displayed or configured as desired. It will also be appreciated that the GUI may provide the user with various information of interest to the user via various charts or alternative visual depictions.
[0122] Alternatively, the UE may query a third-party server for a list of 3GPP user identities based on the device's MAC address. For example, after a connection and authentication request, the UE may send a request to a third-party server (such as 5G-EIR) to find the assigned 3GPP user identity configured for this device.
[0123] Once a connection is established between the device and the UE, the UE can trigger the above reference Figure 7-9 One of the enhanced registration, service request or PDU session establishment processes described. The UE can use the above-mentioned example embodiments to authenticate the UE. In an alternative example, the 5GC can use a method based on deep packet inspection (DPI) to detect which flows to / from the UE are associated with the subscriber or each user. For example, the AMF or SMF can inform the UPF which (which) subscribers and users are associated with the UE. The UPF can then use the DPI function to analyze the business from the UE and determine which flows are associated with each user. For example, the UPF can obtain the DPI rules associated with each user. The DPI rules can describe which applications each user will run, which application identifiers each user can use, what time of day each user can use a specific application, and how each user will digitally sign the business. The DPI rules can also include biometric data associated with each user, for example, the biometric data can be as described above. The UE can then attach the biometric data to the business from the user, and the UPF can use the DPI to detect the biometric data and determine that the business is from the user.
[0124] In an example, the network may need to send MT data to the user. For example, the SMS may be addressed to a 3GPP user identity. In a first example use case, the user is last known to be reachable via a UE, and the UE has a subscription, such as a SUPI associated with it (e.g., IMSI). In a second example use case, the user is last known to be reachable via a device, and the device does not have a subscription, such as no SUPI associated with it (e.g., IMSI).
[0125] When a user needs to be paged in the first case, the network can learn which UE to page by performing a new process with UDM / UDR that allows the network to check the user's record and determine which UE the user was last associated with. The network can page the UE based on the UE's IMSI using existing procedures, but the paging message can be enhanced to include the 3GPP user identity described herein. The presence of the 3GPP user identity can indicate to the UE which user the paging is associated with. If the UE is connected via a non-3GPP network, the network can send a NAS notification including the 3GPP user identity to the device (instead of paging the device). If the user is no longer associated with the UE (for example, no longer logged in or no longer detected), the UE can respond with a service request or registration request indicating that the user is no longer associated with the UE. If the user exists, the UE can send a service request message to the AMF. The UE can know the PDU session state that only includes PDU sessions associated with the user being paged.
[0126] When the user needs to be paged in the second example use case, the network can know how to page by performing a new process with UDM / UDR, which allows the network to check the user's record and determine which UE the user was last associated with. The network (AMF or SMSF) can then initiate a process to page the user with a 3GPP user identity. The device can use the 3GPP user identity to determine the paging occasion. For example, all or part of the user-name field of the 3GPP user identity described herein can be used by the UE and the network to determine the paging occasion. The UE may have indicated in a previous registration message that it supports paging by user identity. The registration message response or broadcast indication from the network (for example, in the SIB) may have indicated to the UE that the network supports paging based on the 3GPP user identity. When the UE sees that its paging indicator is set, it can read the paging message and determine that its 3GPP user identity is in the paging message. In the example, if the device is connected via a non-3GPP network, the network can send a NAS notification including the 3GPP user identity to the device (instead of paging the device). The UE can then perform a service request and provide its 3GPP user identity to the network.
[0127] To avoid unnecessary paging, the UE may perform a registration update to inform the network that the user is no longer associated with the device or UE (e.g. logged in). By excluding the 3GPP user identity from the registration message, the device or UE may indicate to the network that the user is no longer associated with the device or UE. When the network receives notification that the user is no longer associated with the device or UE, the AMF may update the record of the user in the UDR to indicate that the user is no longer associated with the device.
[0128] In an example, the UE or modem platform may expose an API that allows an application to start an application flow or send data on an existing application flow. This type of API may allow the application to specify the port number on which it wants to send traffic, and specify the transport level protocol for the flow (i.e., UDP or TCP). According to an example embodiment, the API may be enhanced to include a 3GPP user identity, NSSAI (or S-NSSAI), and / or DNN. The application may specify its associated 3GPP user identity, which slice the application wants to connect to, and which data network. This may be configured in the application via a GUI. The application may provide this to the UE when the application makes an API call to create a traffic flow, or each time it sends traffic on a traffic flow. When the UE receives a request to initiate a traffic flow, it may trigger the UE to send a NAS request (such as a registration, service request message, or PDU session establishment request) to the network. Reference above Figure 7-9 Enhanced registration, PDU session establishment and service request messages are described, which include authentication and authorization of users.
[0129] Thus, as described above, the UE may receive a user identity and, in response to a triggering event, send a request message to the network. The request message may include the user identity and the session information to be associated with the user identity. The request message may also include a general registration request, a service request, a PDU session establishment request, a PDU modification request, or a PDU session release request. The request message may also include a list of users allowed to access the network via the UE. The UE may receive a response from the network, and the response may include an indication of whether the session information is allowed to be associated with the user identity. The user identity may be received via a graphical user interface of the UE or from a capillary device communicating with the UE or from an application running on the UE. Thus, the user identity may identify a human user of the UE, a capillary device communicating with the UE, or an application. In some examples, the triggering event is that the UE is receiving the user identity. Other example triggering events include: when the UE transitions from a locked state to an unlocked state; when the UE receives data from a capillary device communicating with the UE; or the UE receives a paging message or a non-access stratum (NAS) message. Such a paging message may include a user identity. For example, the UE may send a second message to the network, the second message indicating that the UE supports receiving a paging notification or a NAS notification including a user identity. In addition, the UE may receive broadcast information indicating that the network supports paging based on the user identity, and the UE may send a request message to the network based on the received broadcast information. Using the user identity, the UE may perform authentication with the network of the user associated with the user identity. In an example, the session information is protocol data unit (PDU) session information. In another example, the UE sends a second request message to the network to notify the network that the user identity is no longer associated with the UE. This second request message may be a registration request, or may be sent in response to a paging notification or a NAS notification.
[0130] Figure 4-10 The present invention and its related description illustrate various embodiments of methods and apparatus for authorizing a user (person or device) connected to a UE. In these figures, various steps or operations performed by one or more nodes, devices, functions, or networks are shown. It should be understood that the nodes, devices, functions, or networks shown in these figures may represent logical entities in a communication network and may be implemented in the form of software (e.g., computer executable instructions) stored in a memory of a node of such a network and executed on a processor thereof, such a network may include the following description Fig.11A , 11C -E or 11G. That is, it can be stored in a network node or device (such as Fig. 11B or a node or computer system shown in 11F) in the form of software (e.g., computer executable instructions) in a memory of Figure 5-9The computer executable instructions, when executed by the processor of the node, perform the steps shown in the figure. It should also be understood that any sending and receiving steps shown in these figures can be performed by the communication circuit system of the node (e.g., respectively) under the control of the processor of the node and the computer executable instructions (e.g., software) executed by it. Fig. 11B The circuit system 120 or Fig.11F Circuit system 97) executes. Figure 1-10 Any client, proxy or server device shown in any of the above may comprise a node of a communication system such as Fig.11A , 11C -E or the node shown in 11G.
[0131] The various techniques described herein can be implemented in conjunction with hardware, firmware, software or (when appropriate) a combination thereof. Such hardware, firmware and software can reside in a device located at each node of a communication network. The device can operate individually or in combination with each other to implement the method described herein. As used herein, the terms "device", "network device", "node", "equipment" and "network node" can be used interchangeably.
[0132] 3GPP has identified a variety of use cases that NR is expected to support, resulting in various user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, ultra-high broadband access indoors, broadband access in crowds, ubiquitous 50+Mbps, ultra-low-cost broadband access, in-vehicle mobile broadband), critical communications, massive machine-type communications, network operations (e.g., network slicing, routing, migration and interworking, energy saving), and enhanced vehicle-to-everything (eV2X) communications, where V2X communications can include any of vehicle-to-vehicle communications (V2V), vehicle-to-infrastructure communications (V2I), vehicle-to-network communications (V2N), vehicle-to-pedestrian communications (V2P), and communications between vehicles and other entities. Specific services and applications in these categories include, for example, surveillance and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, car ecalls, disaster alerts, real-time gaming, multi-person video calls, autonomous driving, augmented reality, tactile Internet, and virtual reality, among others. All of these use cases and others are contemplated herein.
[0133] Fig.11AAn embodiment of an example communication system 100 is illustrated in which the methods and apparatus described and claimed herein may be implemented. As shown, the example communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, and / or 102f (generally or collectively referred to as WTRUs 102), a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and a V2X server (or ProSe function and server) 113, although it should be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f may be any type of device or apparatus configured to operate and / or communicate in a wireless environment. Figures 11A-11E , but it should be understood that for the various use cases anticipated for 5G wireless communications, each WTRU may include or be implemented in any type of device or apparatus configured to send and / or receive wireless signals, including, by way of example only, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smart phone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronics product, a wearable device (such as a smart watch or smart clothing), a medical or e-health device, a robot, an industrial equipment, a drone, a vehicle (such as a car, truck, train or airplane, etc.).
[0134] The communication system 100 may also include a base station 114a and a base station 114b. The base station 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The base station 114b may be any type of device configured to wirelessly interface with at least one of the RRHs (remote radio heads) 118a, 118b, TRPs (transmit and receive points) 119a, 119b, and / or RSUs (roadside units) 120a, 120b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, other networks 112, and / or a V2X server (or ProSe function and server) 113. The RRH 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The TRP 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102d to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or other networks 112. The RSU 120a, 120b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102e or 102f to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, other networks 112, and / or a V2X server (or ProSe function and server) 113. For example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, etc. Although the base stations 114a, 114b are each depicted as a single element, it should be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.
[0135] The base station 114a may be part of the RAN 103 / 104 / 105, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114b may be part of the RAN 103b / 104b / 105b, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), a relay node, etc. The base station 114a may be configured to send and / or receive wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The base station 114b may be configured to send and / or receive wired and / or wireless signals within a specific geographic area, which may be referred to as a cell (not shown). The cell may be further divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may include three transceivers, for example, one transceiver for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple-output (MIMO) technology and may therefore use multiple transceivers for each sector of the cell.
[0136] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, centimeter wave (cmWave), millimeter wave (mmWave), etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).
[0137] The base station 114b may communicate with one or more of the RRHs 118a, 118b, the TRPs 119a, 119b, and / or the RSUs 120a, 120b via a wired or air interface 115b / 116b / 117b, where the wired or air interface 115b / 116b / 117b may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).
[0138] The RRHs 118a, 118b, TRPs 119a, 119b and / or RSUs 120a, 120b may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f via an air interface 115c / 116c / 117c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / 116c / 117c may be established using any suitable radio access technology (RAT).
[0139] The WTRUs 102a, 102b, 102c, 102d, 102e, and / or 102f may communicate with one another via an air interface 115d / 116d / 117d, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115d / 116d / 117d may be established using any suitable radio access technology (RAT).
[0140] More specifically, as described above, the communication system 100 may be a multiple-access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, TRPs 119a, 119b and RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish the air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. WCDMA may include communication protocols such as High Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High Speed Downlink Packet Access (HSDPA) and / or High Speed Uplink Packet Access (HSUPA).
[0141] In an embodiment, the base station 114a and the WTRU 102a, 102b, 102c or the RRH 118a, 118b, TRP 119a, 119b and RSU 120a, 120b and WTRU 102c, 102d in the RAN 103b / 104b / 105b may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may use Long Term Evolution (LTE) and / or LTE-Advance (LTE-A) to establish an air interface 115 / 116 / 117 or 115c / 116c / 117c, respectively. In the future, the air interface 115 / 116 / 117 may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and V2X technologies and interfaces (such as sidelink communications, etc.). 3GPP NR technologies include NR V2X technologies and interfaces (such as sidelink communications, etc.).
[0142] In an embodiment, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c or the RRHs 118a, 118b, the TRPs 119a, 119b and / or the RSUs 120a, 120b and the WTRUs 102c, 102d, 102e, 102f in the RAN 103b / 104b / 105b may implement a radio technology such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE), GSM EDGE(GERAN) etc.
[0143] For example, Fig.11AThe base station 114c in the example may be a wireless router, a Home Node B, a Home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business location, a home, a vehicle, a campus, etc. In an embodiment, the base station 114c and the WTRU 102e may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114c and the WTRU 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114c and the WTRU 102e may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or a femtocell. Fig.11A As shown in FIG, base station 114b may have a direct connection to the Internet 110. Therefore, base station 114c may not be required to access the Internet 110 via core network 106 / 107 / 109.
[0144] The RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b may be in communication with a core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions (such as user authentication).
[0145] Although not in Fig.11A 105b and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b, which may utilize an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) that employs a GSM radio technology.
[0146] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), the User Datagram Protocol (UDP), and the Internet Protocol (IP) (in the TCP / IP Internet protocol suite). The networks 112 may include wired communication networks or wireless communication networks owned and / or operated by other service providers. For example, the networks 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 and / or the RAN 103b / 104b / 105b or a different RAT.
[0147] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities. For example, the WTRUs 102a, 102b, 102c, 102d, and 102e may include multiple transceivers for communicating with different wireless networks via different wireless links. Fig.11A The WTRU 102e shown in FIG. 1 may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.
[0148] Fig. 11B 1 is a block diagram of an example apparatus or device (such as, for example, WTRU 102) configured for wireless communication according to the embodiments described herein. Fig. 11BAs shown in , the example WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicator 128, a non-removable memory 130, a removable memory 132, a power supply 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It should be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment. Moreover, embodiments contemplate that the base stations 114a and 114b and / or the nodes that the base stations 114a and 114b may represent (such as, but not limited to, a transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, and a proxy node, etc.) may include Fig. 11B and some or all of the elements described in this document.
[0149] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. Although Fig. 11B The processor 118 and transceiver 120 are depicted as separate components, but it will be appreciated that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.
[0150] The send / receive element 122 may be configured to send a signal to a base station (e.g., base station 114a) or receive a signal from a base station (e.g., base station 114a) via an air interface 115 / 116 / 117. For example, in an embodiment, the send / receive element 122 may be an antenna configured to send and / or receive an RF signal. In an embodiment, the send / receive element 122 may be a transmitter / detector configured to, for example, send and / or receive an IR, UV or visible light signal. In yet another embodiment, the send / receive element 122 may be configured to send and receive both an RF signal and an optical signal. It should be appreciated that the send / receive element 122 may be configured to send and / or receive any combination of wireless signals.
[0151] In addition, although the transmit / receive element 122 is Fig. 11B Although depicted as a single element in the figure, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.
[0152] The transceiver 120 may be configured to modulate signals to be transmitted by the transmit / receive element 122 and to demodulate signals received by the transmit / receive element 122. As described above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs (e.g., such as UTRA and IEEE 802.11).
[0153] The processor 118 of the WTRU 102 may be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad / indicator 128 (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit), and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicator 128. In addition, the processor 118 may access information from and store data in any type of suitable memory, such as a non-removable memory 130 and / or a removable memory 132. The non-removable memory 130 may include a random access memory (RAM), a read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In an embodiment, the processor 118 may access information from and store data in a memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).
[0154] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries, solar cells, fuel cells, etc.
[0155] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to or in lieu of the information from the GPS chipset 136, the WTRU 102 may receive location information from a base station (e.g., base stations 114a, 114b) over the air interface 115 / 116 / 117 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by any suitable location-determination method while remaining consistent with an embodiment.
[0156] The processor 118 may also be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may include various sensors such as an accelerometer, a biometric (e.g., fingerprint) sensor, an electronic compass, a satellite transceiver, a digital camera (for photos or videos), a universal serial bus (USB) port or other interconnect interface, a vibration device, a television transceiver, a hands-free headset, a Bluetooth modules, FM radio units, digital music players, media players, video game player modules, internet browsers, etc.
[0157] The WTRU 102 may be implemented in other devices or equipment, such as sensors, consumer electronics, wearable devices (such as smart watches or smart clothing), medical or e-health equipment, robots, industrial equipment, drones, vehicles (such as cars, trucks, trains or airplanes), etc. The WTRU 102 may be connected to other components, modules or systems of such devices or equipment via one or more interconnect interfaces (such as an interconnect interface that may include one of the peripheral devices 138).
[0158] Fig. 11C 1 is a system diagram of the RAN 103 and the core network 106 according to an embodiment. As described above, the RAN 103 may employ UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also communicate with the core network 106. Fig. 11CAs shown in FIG. 1 , the RAN 103 may include Node-Bs 140a, 140b, 140c, each of which may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also include RNCs 142a, 142b. It will be appreciated that the RAN 103 may include any number of Node-Bs and RNCs while remaining consistent with an embodiment.
[0159] like Fig. 11C As shown in , Node-B 140a, 140b can communicate with RNC 142a. In addition, Node-B 140c can communicate with RNC 142b. Node-B 140a, 140b, 140c can communicate with corresponding RNC 142a, 142b via Iub interface. RNC 142a, 142b can communicate with each other via Iur interface. Each of RNC 142a, 142b can be configured to control the corresponding Node-B 140a, 140b, 140c connected thereto. In addition, each of RNC 142a, 142b can be configured to perform or support other functions, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro diversity, security functions, data encryption, etc.
[0160] Fig. 11C The core network 106 shown in FIG. 1 may include a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. Although each of the foregoing elements is depicted as part of the core network 106, it should be appreciated that any of these elements may be owned and / or operated by an entity other than a core network operator.
[0161] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an IuCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
[0162] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an IuPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0163] As described above, core network 106 may also be connected to networks 112, which may include other wired or wireless networks owned and / or operated by other service providers.
[0164] Fig.11D 1 is a system diagram of the RAN 104 and the core network 107 according to an embodiment. As described above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.
[0165] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.
[0166] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, etc. Fig.11D As shown in FIG, eNode-Bs 160a, 160b, 160c may communicate with each other via an X2 interface.
[0167] Fig.11DThe core network 107 shown in FIG. 1 may include a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements is depicted as part of the core network 107, it should be appreciated that any of these elements may be owned and / or operated by an entity other than a core network operator.
[0168] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, etc. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.
[0169] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an S1 interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 may also perform other functions, such as anchoring the user plane during inter-eNode B handover, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing the context of the WTRUs 102a, 102b, 102c, and the like.
[0170] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
[0171] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core network 107 may include, or may be in communication with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and / or operated by other service providers.
[0172] Fig.11E 1 is a system diagram of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 117. As discussed further below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.
[0173] like Fig.11E As shown in the figure, the RAN 105 may include base stations 180a, 180b, 180c and an ASN gateway 182, but it should be appreciated that the RAN 105 may include any number of base stations and ASN gateways while remaining consistent with the embodiment. The base stations 180a, 180b, 180c may each be associated with a particular cell in the RAN 105 and may include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In an embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, the base station 180a, for example, may use multiple antennas to send wireless signals to the WTRU 102a and receive wireless signals from the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions, such as handover triggering, tunnel establishment, radio resource management, service classification, quality of service (QoS) policy enforcement, etc. The ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and the like.
[0174] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.
[0175] The communication link between each of the base stations 180a, 180b, and 180c may be defined as an R8 reference point, which includes protocols for facilitating WTRU handover and data transfer between the base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point. The R6 reference point may include protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.
[0176] like Fig.11E As shown in , the RAN 105 may be connected to a core network 109. The communication link between the RAN 105 and the core network 109 may be defined as an R3 reference point, which includes protocols for facilitating, for example, data transfer and mobility management capabilities. The core network 109 may include a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. While each of the foregoing elements is depicted as part of the core network 109, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the core network operator.
[0177] The MIP-HA may be responsible for IP address management and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. The MIP-HA 184 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, and 102c and IP-enabled devices. The AAA server 186 may be responsible for user authentication and supporting user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communication devices. In addition, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may include other wired or wireless networks that are owned and / or operated by other service providers.
[0178] Although not in Fig.11E 105 may be connected to other ASNs and the core network 109 may be connected to other core networks. The communication link between the RAN 105 and the other ASNs may be defined as an R4 reference point, which may include protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core networks may be defined as an R5 reference, which may include protocols for facilitating interworking between a home core network and a visited core network.
[0179] This article describes and Fig.11A , 11C The core network entities shown in 11D and 11E are identified by the names given to these entities in certain existing 3GPP specifications, but it should be recognized that in the future, these entities and functions may be identified by other names, and certain entities or functions may be combined in future specifications published by 3GPP (including future 3GPP NR specifications). Fig.11A , 11B The specific network entities and functionality described and illustrated in 11C, 11D, and 11E are provided by way of example only, and it should be understood that the subject matter disclosed and claimed herein may be implemented or realized in any similar communication system, whether currently defined or in the future.
[0180] Fig.11F is a block diagram of an exemplary computing system 90 in which Fig.11A , 11C, 11D and 11E, such as certain nodes or functional entities in the RAN 103 / 104 / 105, the core network 106 / 107 / 109, the PSTN 108, the Internet 110 or other networks 112. The computing system 90 may include a computer or a server and may be primarily controlled by computer-readable instructions, which may be in the form of software, wherever or in any manner such software is stored or accessed. Such computer-readable instructions may be executed within the processor 91 to enable the computing system 90 to operate. The processor 91 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor 91 may perform signal encoding, data processing, power control, input / output processing, and / or any other function that enables the computing system 90 to operate in a communication network. Coprocessor 81 is an optional processor distinct from main processor 91 that may perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatus disclosed herein.
[0181] In operation, processor 91 fetches, decodes and executes instructions and transfers information to and from other resources via the computing system's main data transfer path, system bus 80. Such a system bus connects components in computing system 90 and defines a medium for data exchange. System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the bus. An example of such a system bus 80 is a PCI (Peripheral Component Interconnect) bus.
[0182] The memory coupled to the system bus 80 includes a random access memory (RAM) 82 and a read-only memory (ROM) 93. Such memory includes a circuit system that allows information to be stored and retrieved. ROM 93 generally contains stored data that is not easily modified. The data stored in RAM 82 can be read or changed by a processor 91 or other hardware device. Access to RAM 82 and / or ROM 93 can be controlled by a memory controller 92. The memory controller 92 can provide an address translation function that converts a virtual address into a physical address when an instruction is executed. The memory controller 92 can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Therefore, a program running in the first mode can only access memory mapped by its own process virtual address space; unless memory sharing between processes has been set up, it cannot access memory within the virtual address space of another process.
[0183] In addition, the computing system 90 may include a peripheral device controller 83 that is responsible for transmitting instructions from the processor 91 to peripheral devices such as a printer 94 , a keyboard 84 , a mouse 95 , and a disk drive 85 .
[0184] The display 86 controlled by the display controller 96 is used to display the visual output generated by the computing system 90. Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display 86 may be implemented with a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch pad. The display controller 96 includes the electronic components required to generate the video signal sent to the display 86.
[0185] Additionally, computing system 90 may include communications circuitry such as, for example, a network adapter 97 that may be used to connect computing system 90 to an external communications network such as Fig.11A , 11B , RAN 103 / 104 / 105 of 11C, 11D and 11E, core network 106 / 107 / 109, PSTN 108, Internet 110 or other network 112) to enable computing system 90 to communicate with other nodes or functional entities of these networks. Alone or in combination with processor 91, the communication circuit system can be used to perform the sending and receiving steps of certain devices, nodes or functional entities described herein.
[0186] Fig.11GAn embodiment of an example communication system 111 is illustrated in which the methods and apparatus described and claimed herein may be implemented. As shown, the example communication system 111 may include wireless transmit / receive units (WTRUs) A, B, C, D, E, F, base stations, a V2X server, and RSUs A and B, but it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. One or several or all of the WTRUs A, B, C, D, E may be out of range of the network (e.g., outside of the cell coverage boundary shown by the dashed lines in the figure). WTRUs A, B, C form a V2X group, where WTRU A is the group leader and WTRUs B and C are group members. WTRUs A, B, C, D, E, F may communicate over a Uu interface or a sidelink (PC5) interface.
[0187] It should be understood that any or all of the devices, systems, methods, and processes described herein may be implemented in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium, which, when executed by a processor (such as processor 118 or 91), causes the processor to perform and / or implement the systems, methods, and processes described herein. Specifically, any step, operation, or function described herein may be implemented in the form of such computer executable instructions executed on a processor of a device or computing system configured for wireless and / or wired network communications. Computer-readable storage media include volatile and non-volatile, removable and non-removable media implemented in any non-transient (e.g., tangible or physical) method or technology for storing information, but such computer-readable storage media do not include signals. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassette, tape, magnetic disk storage or other magnetic storage device, or any other tangible or physical medium that can be used to store desired information and can be accessed by a computing system.
[0188] In describing the preferred embodiments of the subject matter of the present disclosure, as shown in the figures, specific terminology is employed for clarity. However, the claimed subject matter is not intended to be limited to the specific terminology so selected, and it should be understood that each specific element includes all technical equivalents that operate in a similar manner to achieve a similar purpose.
[0189] The following table includes a list of service-level technology-related acronyms that may appear in the above description. Unless otherwise specified, the acronyms used in this article refer to the corresponding terms listed below.
[0190] Table 3
[0191]
[0192]
[0193]
[0194] This written description uses examples to disclose the present invention, including the best mode, and also enables any person skilled in the art to practice the present invention, including making and using any device or system and performing any incorporated method. The patentable scope of the present invention is defined by the claims, and may include other examples that occur to those skilled in the art. If such other examples have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that do not differ substantially from the literal language of the claims, then they are intended to be within the scope of the claims.
Claims
1. An apparatus comprising a processor, a memory, and a communication circuit system, the apparatus being connected to a network via its communication circuit system, the apparatus further comprising computer executable instructions stored in the memory of the apparatus, the computer executable instructions, when executed by the processor of the apparatus, causing the apparatus to perform operations comprising: receiving an authentication request from a requestor node, the authentication request including an identity associated with the requestor node and a user identity associated with a user of a user equipment in communication with the requestor node; In response to the authentication request, obtaining information associated with the user identity; as well as Based on the information, authentication is performed on a user of the user equipment, wherein the user identity is independent of a device identity associated with the user equipment, so as to allow the user network access after authentication.
2. The apparatus of claim 1, wherein the user is a capillary device that communicates with the user equipment such that the user identity identifies the capillary device.
3. The apparatus of claim 1, wherein the user is a first person, such that the user identity identifies the first person, and the device identity indicates a second person different from the first person.
4. The apparatus of any one of claims 1 to 3, wherein the authentication request further comprises at least one of a subscription permanent identifier of the user equipment or a permanent equipment identifier of the user equipment.
5. An apparatus as claimed in any one of claims 1 to 4, wherein information associated with the user identity is obtained from a unified data repository.
6. The apparatus of any one of claims 1 to 5, wherein information associated with the user identity is obtained from a plurality of unified data repositories.
7. An apparatus as described in any one of claims 1 to 6, wherein the information obtained in association with the user identity indicates restrictions related to network access, and the restrictions are associated with at least one of the user's location, the user's equipment identifier, the access type, the data network, the network function, one or more network slices, or time.
8. The apparatus of any one of claims 1 to 7, wherein the obtained information further comprises a preferred mechanism for authentication or one or more credentials for authentication.
9. An apparatus as described in any one of claims 1 to 8, wherein the obtained information associated with the user identity includes subscription information associated with a subscription of the user equipment, and the subscription information indicates at least one of the following: one or more user identities associated with the subscription, one or more user identities allowed to access the network via the subscription, one or more user identities prohibited from accessing the network via the subscription, whether a guest user is allowed to access the network via the subscription, and one or more specific guest users allowed to access the network via the subscription.
10. The apparatus of any one of claims 1 to 9, wherein the user identity indicates a mobile network operator associated with the user.
11. An apparatus as claimed in any one of claims 1 to 10, wherein the user identity indicates user equipment with which the user communicates.
12. The apparatus of any one of claims 1 to 11, wherein the user identity identifies a subscription for network access.
13. An apparatus as claimed in any one of claims 1 to 12, wherein the user identity is formatted according to an internal format different from an external format of the user identity used by the user equipment.
14. An apparatus as claimed in any one of claims 1 to 13, wherein the authentication request is received from the supplicant node in response to the user equipment sending an initial request to the network via the supplicant node.
15. The apparatus of claim 14, wherein the initial request includes a user identity.
16. The apparatus of claim 15, wherein the initial request is one of: a registration request; a PDU session establishment, release, or modification request; a service request; or an API request.
17. The apparatus of any one of claims 1 to 16, wherein the requester node comprises an access and mobility management function.
18. The apparatus of any one of claims 1 to 17, wherein performing authentication of a user comprises: Determining that the user equipment has been authenticated; as well as Directing the user to a captive portal to enable the user to enter credential information at the captive portal.
19. The apparatus of claim 1, wherein performing authentication of a user comprises: Sends the IP address and port number to the requester node for the user to contact.
20. The apparatus of claim 19, wherein performing authentication of the user comprises: A PCI message is received from a user at the IP address and port number to initiate authentication.
21. The apparatus of claim 20, further comprising computer executable instructions stored in a memory of the apparatus, wherein when the computer executable instructions are executed by a processor of the apparatus, the apparatus performs the following operations: One or more security keys are derived for use in subsequent user plane messages associated with the user.
22. The apparatus of any one of claims 19 to 21, wherein performing authentication of a user comprises: A message is sent to the supplicant node indicating a preferred authentication method for authentication.
23. An apparatus as claimed in any one of claims 1 or 19 to 22, wherein the authentication request is received from the supplicant node in response to the user equipment sending a user plane request to the network via the supplicant node.
