Associating a human user with a subscription

Abstract

Systems and methods are described herein for associating a human user with a subscription. User identities may be managed. User identities may be linked and / or unlinked with subscriptions. An identified user may be authenticated to use a subscription. A device (e.g., wireless transmit / receive unit (WTRU)) may detect whether a network slice is enabled (e.g., allowed) to be accessed by a user. A WTRU's protocol data unit (PDU) sessions may be configured to be associated with a user of the WTRU. Associating a PDU session with a user may enable a network to configure quality of service (QoS) treatment for the PDU session (e.g., such that it is based on the level of service that may be provided to the user).

Description

ASSOCIATING A HUMAN USER WITH A SUBSCRIPTIONCROSS-REFERENCE TO RELATED APPLICATOINS

[0001] The application claims the benefit of U.S. Provisional Application 63 / 553,829, filed February 15, 2024, the contents of which are incorporated by reference in their entirety herein.BACKGROUND

[0002] Mobile communications using wireless communication continue to evolve. A fifth generation may be referred to as 5G. A previous (legacy) generation of mobile communication may be, for example, fourth generation (4G) long term evolution (LTE).SUMMARY

[0003] Systems and methods are described herein for associating a human user with a subscription. User identities may be managed. User identities may be linked and / or unlinked with subscriptions. An identified user may be authenticated to use a subscription. A device (e.g., wireless transmit / receive unit (WTRU)) may detect whether a network slice is enabled (e.g., allowed) to be accessed by a user. A WTRU’s protocol data unit (PDU) sessions may be configured to be associated with a user of the WTRU. Associating a PDU session with a user may enable a network to configure quality of service (QoS) treatment for the PDU session (e.g., such that it is based on the level of service that may be provided to the user).

[0004] A first network entity (e.g., policy control function (PCF) network entity) may associated a human user with a subscription. The first network entity may receive (e.g., from a second network entity, e.g., a session management function (SMF) network entity) a first message. The first message may indicate a user identity associated with a PDU session. The first network entity may determine a QoS parameter (e.g., a first default value associated with a QoS identifier (QI), a second default value associated with an allocation and retention priority (ARP), a priority level associated with QI, etc.) based on the user identity and a data network name (DNN)Zsingle network slice selection assistance information (S-NSSAI) combination associated with the PDU session. For example, the first network entity may send a second message to a user data management (UDM) network entity. The second message may request the QoSparameter associated with the DNN / S-NSSAI combination associated with the PDU session. The first network entity may receive a third message that indicates the QoS parameter associated with the DNN / S- NSSAI combination associated with the PDU session. The first network entity may determine a policy and charging control (PCC) rule, for example, based on the QoS parameter. The determined PCC rule may be associated with the PDU session. The first network entity may send the PCC rule to the second network entity.

[0005] Details associated with a user identify may be described. In examples, the user identifier may be used to identify traffic (e.g., associated with a WTRU). The WTRU may be associated with the user. The user identifier may be associated with a user profile. The user profile may be associated with (e.g., include) a (e.g., at least) a first DNN / S-NSSAI combination and a first default QoS parameter. The first default parameter may be associated with the first DNN / S-NSSAI combination. The first DNN / S-NSSAI combination may be the DNN / S-NSSAI combination associated with the PDU session. The determined QoS parameter may be the first default QoS parameter associated with the first DNN / S-NSSAI combination. In examples, the user identity may include one or more of a domain identifier (e.g., associated with a domain) or a local identifier (e.g., indicating a user in the domain). The domain may be associated with a mobile network operator (MNO). The user identity may include an application function identifier. The application function identifier may indicate an application function network entity. The application function network entity may be associated with one or more of linking a user to a first subscription, unlinking the user from a second subscription, storing information in a user profile, reading information from the user profile, authenticating a user, etc.BRIEF DESCRIPTION OF THE DRAWINGS

[0006] FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.

[0007] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0008] FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.

[0009] FIG. 1 D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0010] FIG. 2 illustrates an example registration to begin the association of a User to a subscription.

[0011] FIG. 3 illustrates an example registration to begin the association of a User to a subscription.

[0012] FIG. 4 illustrates an example of a PDU Session Establishment when a User Identity is associated with a subscription.

[0013] FIG. 5 illustrates an example PDU Session Modification if a User Identity is authenticated to be associated with a subscription.

[0014] FIG. 6 illustrates an example of exposure of User Profile information.DETAILED DESCRIPTION

[0015] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0016] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a ON 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will 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 may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c, and 102d may be interchangeably referred to as a UE.

[0017] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the I nternet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B (eNB), a Home Node B, a Home eNode B, a gNode B (gNB), a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0018] The base station 114a may be part of the RAN 104 / 113, 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), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e. , one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0019] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0020] More specifically, as noted above, the communications 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, and the like. For example, the base station 114a in the RAN 104 / 113 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0021] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0022] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using New Radio (NR).

[0023] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[0024] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, 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), and the like.

[0025] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 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 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0026] The RAN 104 / 113 may be in communication with the CN 106 / 115, 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. The data may have varying quality of service (QoS)requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 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. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0027] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide 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), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0028] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0029] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the 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 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0030] 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 in association with a DSP core, a controller, a microcontroller, Application SpecificIntegrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. 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. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0031] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0032] Although the transmit / receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one 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 116.

[0033] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and I EEE 802.11 , for example.

[0034] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), 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 other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0035] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the 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 (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0036] 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 over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.

[0037] The processor 118 may further 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 an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0038] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WRTU 102 may include a half-duplex radio for which transmissionand reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

[0039] FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0040] 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 one 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 / or receive wireless signals from, the WTRU 102a.

[0041] Each of the eNode-Bs 160a, 160b, 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 UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0042] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements is depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0043] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, 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, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0044] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0045] The SGW 164 may be connected to the PGW 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.

[0046] The CN 106 may facilitate communications with other networks. For example, the CN 106 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 CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0047] Although the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0048] In representative embodiments, the other network 112 may be a WLAN.

[0049] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to- peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.

[0050] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with theAP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0051] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0052] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0053] Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0054] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices)that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0055] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0056] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the CN 115.

[0057] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0058] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0059] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0060] Each of the gNBs 180a, 180b, 180c 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 UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0061] The CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0062] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access,services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0063] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.

[0064] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, 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. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0065] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0066] In view of Figures 1 A-1 D, and the corresponding description of Figures 1 A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0067] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, one or more emulation devices mayperform one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may performing testing using over- the-air wireless communications.

[0068] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network to implement testing of one or more components. The one or more emulation devices may be testing equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0069] Systems and methods are described herein for associating a human user with a subscription. User identities may be managed. User identities may be linked and / or unlinked with subscriptions. An identified user may be authenticated to use a subscription. A device (e.g., wireless transmit / receive unit (WTRU)) may detect whether a network slice is enabled (e.g., allowed) to be accessed by a user. A WTRU’s protocol data unit (PDU) sessions may be configured to be associated with a user of the WTRU. Associating a PDU session with a user may enable a network to configure quality of service (QoS) treatment for the PDU session (e.g., such that it is based on the level of service that may be provided to the user).

[0070] A first network entity (e.g., policy control function (PCF) network entity) may associate a human user with a subscription. The first network entity may receive (e.g., from a second network entity, e.g., a session management function (SMF) network entity) a first message. The first message may indicate a user identity associated with a PDU session. The first network entity may determine a QoS parameter (e.g., a first default value associated with a QoS identifier (QI), a second default value associated with an allocation and retention priority (ARP), a priority level associated with QI, etc.) based on the user identity and a data network name (DNN)Zsingle network slice selection assistance information (S-NSSAI) combination associated with the PDU session. For example, the first network entity may send a second message to a user data management (UDM) network entity. The second message may request the QoS parameter associated with the DNN / S-NSSAI combination associated with the PDU session. The first network entity may receive a third message that indicates the QoS parameter associated with the DNN / S- NSSAI combination associated with the PDU session. The first network entity may determine a policy andcharging control (PCC) rule, for example, based on the QoS parameter. The determined PCC rule may be associated with the PDU session. The first network entity may send the PCC rule to the second network entity.

[0071] Details associated with a user identify may be described. In examples, the user identifier may be used to identify traffic (e.g., associated with a WTRU). The WTRU may be associated with the user. The user identifier may be associated with a user profile. The user profile may be associated with (e.g., include) a (e.g., at least) a first DNN / S-NSSAI combination and a first default QoS parameter. The first default parameter may be associated with the first DNN / S-NSSAI combination. The first DNN / S-NSSAI combination may be the DNN / S-NSSAI combination associated with the PDU session. The determined QoS parameter may be the first default QoS parameter associated with the first DNN / S-NSSAI combination. In examples, the user identity may include one or more of a domain identifier (e.g., associated with a domain) or a local identifier (e.g., indicating a user in the domain). The domain may be associated with a mobile network operator (MNO). The user identity may include an application function identifier. The application function identifier may indicate an application function network entity. The application function network entity may be associated with one or more of linking a user to a first subscription, unlinking the user from a second subscription, storing information in a user profile, reading information from the user profile, authenticating a user, etc.

[0072] A network entity (e.g., policy control function (PCF) network entity or a session management function (SMF) network entity) may associate a human user with a subscription. A first network entity may receive a first message (e.g., registration request). The first message (e.g., registration request) may indicate a user identity associated with a wireless transmit / receive unit (WTRU). The first network entity may determine whether the user identity is linked to a subscription. The first network entity may (e.g., based on the determination of whether the user identity is associated with the subscription) send a registration response. The registration response may include an indication that the user may be allowed to access a set of slices associated with the subscription. The registration response may include a rejected indication that the user is not allowed to access a slice that is associated with a single network slice selection assistance information (S-NSSAI). The first network entity may determine whether the user identity has been authenticated (e.g., receive an indication that the user identity has been authenticated). The first network entity may send a message to a second network entity associated with serving a PDU session. The message may indicate the user identity (e.g., so a session management function may know which QoS rules to apply).

[0073] Access and mobility function (AMF) actions may be performed. AMF actions may be related to configuring a WTRU’s connection to a system (e.g., 5G System) for a user (e.g., for a specific user.

[0074] An AMF may perform one or more of the following.

[0075] A registration request may be received (e.g., as shown with respect to FIG. 3 at 1). The registration request may include a user identity.

[0076] A procedure may be performed to check if the user identity is linked to the WTRU’s subscription (e.g., as shown with respect to FIG. 3 at 3).

[0077] A registration response may be sent (e.g., as shown with respect to FIG. 3 at 5). The registration response may include an indication. The indication may, for example, indicate that the user identity is linked to the WTRU’s subscription. The registration response may include information, for example, such as rejected network slice selection assistance information (NSSAI). The rejected NSSAI may include a (e.g., at least one) single NSSAI (S-NSSAI) and / or an indication that indicates user access for a slice associated with the S-NSSAI (e.g., indication that indicates the user is not allowed to access a slice that is associated with the S-NSSAI).

[0078] An authentication procedure may be initiated (e.g., as shown with respect to FIG. 3 at 6), for example, by sending a message (e.g., non-access stratum mobility management (NAS-MM) message) to the WTRU. The message (e.g., NAS-MM message) may include an identity request message (e.g., extensible authentication protocol (EAP) Identity Request message) and the user identity.

[0079] An authentication procedure may be initiated by the AMF (e.g., as shown with respect to FIG. 3 at 6), for example, the AMF may initiate the procedure by sending a message (e.g., NAS-MM) message to the WTRU. The message (e.g., NAS-MM message) may include an identity request message (e.g., EAP Identity Request message) and the user identity.

[0080] An indication may be received (e.g., from the AMF by the WTRU), for example, as part of the authentication procedure. For example, the indication may indicate that the user identity has been authenticated. In examples, the indication may be received (e.g., from the AMF by the WTRU) after the authentication procedure. The WTRU may initiate a registration request (e.g., a new Registration Request) to the AMF, for example, if the indication indicates that the user identity was not authenticated. The Registration Request may include a different user identity or may refrain from including a user identity (e.g., may include no user identity).

[0081] A message may be sent (e.g., as shown with respect to FIG. 5 at 1) to a network entity (e.g., an SMF or PCF) that is serving a PDU Session. The message may include the user identity, for example, so that the network entity (e.g., SMF or PCF) knows what QoS Rules to apply.

[0082] A subscription (e.g., 3GPP Subscription) may be identified, for example, by a subscription permanent identifier (SUPI). A SUPI may be a subscription identifier. The SUPI may be stored in a WTRU(e.g., the SIM card of a WTRU). A subscription may refrain from identifying (e.g., not identify) a user. For example, a system may not be aware of the human who is using a WTRU (e.g., a smartphone).

[0083] A system may be unable to identify the human user of a subscription. The system may not be aware of the identity of the user (e.g., human) who is using a WTRU to send and receive traffic.

[0084] The mobile network operator may be unable to customize the service experience based on the human user of a WTRU. Service customization may be subscription-based (e.g., only be subscriptionbased).

[0085] A system may be unable to form an Allowed NSSAI, for example, that is based on the identity of the user of a WTRU.

[0086] A system may be unable to configure QoS Rules, for example, based on the identity of the user of a WTRU.

[0087] A core network may (e.g., be enabled to) manage user identities. User identities may be linked and unlinked with subscriptions. An identified user may be authenticated to use a subscription.

[0088] The WTRU may detect whether a network slice may be accessed (e.g., is allowed to be accessed) by a user. A WTRU’s PDU Sessions may (e.g., be configured to) be associated with the user of the WTRU. The network (e.g., session management function (SMF) or policy control function (PCF)) may configure the QoS Treatment for the PDU Session (e.g., such that it is based on the level of service that should be provided to the user), for example, by associating the PDU Session with a user.

[0089] A user identifier may include (e.g., be made up of) a domain identifier (e.g., component) and / or a local identifier (e.g., component).

[0090] A user profile may be stored in the user data repository (UDR). The user profile may include (e.g., hold) information, for example, about which subscriptions the user is linked to and / or default QoS parameters for the user’s traffic.

[0091] The user may be linked and unlinked to subscriptions, for example, based on requests from the AF (e.g., via the NEF). Being linked may include that the user profile stores an indication that the user is allowed to use a subscription.

[0092] The WTRU may provide the user identifier, for example, during a registration procedure. Whether the user identifier is linked to the subscription may be checked (e.g., by the AMF). The AMF may allow (e.g., only allow) slices that the WTRU is subscribed to and / or the user is authorized to access.

[0093] The user may be authenticated, for example, after registration.

[0094] Once a user is authenticated, the user identifier may be provided (e.g., by the AMF) to the network entity (e.g., SMFs or PCFs) that serve a (e.g., any) PDU Session(s) of the WTRU. The user’sdefault QoS parameters may be obtained (e.g., by the SMF or PCF), for example, from the user profile for the DNN / S-NSSAI combination. The user’s Default QoS parameters may be considered (e.g., by the SMF), for example, if (e.g., when) creating the QoS Rules, QoS Profile, and N4 Rules.

[0095] During PDU Session Establishment, the user identifier may be provided (e.g., by the AMF) to the network entity (e.g., SMF or PCF). The user’s Default QoS parameters may be obtained (e.g., by the SMF or PCF) from the User Profile for the DNN / S-NSSAI combination. The user’s Default QoS parameters may be considered (e.g., by the SMF or PCF), for example, if (e.g., when) creating the QoS Rules, QoS Profile, and N4 Rules.

[0096] A procedure (e.g., similar to the Network Slice-Specific Authentication and Authorization) may include authenticating and / or authorizing the human user of a WTRU.

[0097] The User Profile may be included in (e.g., part of a) network function (e.g., the UDR) in the home network of the operator that manages the user identifier. The network function may allow the NEF to invoke APIs to read and subscribe to information from the user profile. For example, the User Profile may be stored in the UDR. The User profile may be accessed via the UDM.

[0098] Details associated with a format of the user identity may be provided herein.

[0099] The User Identity may include one or more of the following: a Domain Identifier which may identify a domain that is under the control of a Mobile Network Operator (MNO); a Local Identifier which may identify the user within the domain (e.g., the local identifier may be managed by the Mobile Network Operator); an Application Function identifier that may identify an AF; etc. The AF may (e.g., be allowed to) link a user to a subscription, unlink a user from a subscription, store information in the user’s profile, read information from the user’s profile, and / or authenticate the user. For example, the AF may be the authentication, authorization, and accounting server (AAA-S).

[0100] Details associated with the User Profile may be provided herein.

[0101] The User Profile may be stored in the UDR. The User Profile may be initially created via operations and management (O&M) provisioning. A User Profile may include one or more of the following: a User Identifier; 0 or more SUPIs which may identify the subscriptions to which the User Profile is linked; DNN / S-NSSAI combinations that the user may be authorized to access; default QoS parameters for each DNN / S-NSSAI combination the user is authorized to access (e.g., default values for the 5QI and the ARP and optionally, the 5QI Priority Level); etc.

[0102] The content of the user identity profile may be updated.

[0103] User Profile information may be updated in the UDR, for example, by the UDM. The UDM may update the User Profile information by invoking a service (e.g., Nudr_DM_Update service) and / or using a user identifier as a data key.

[0104] The UDM may support a service operation (e.g., Nudm_UserldentityProfile(UIP)_Modify service operation). Consumers of the Nudm_UIP_Modify service operation may include the AF and NEF. The AF, AMF, and NEF may invoke the Nudm_UIP_Modify service operation to write content in the user profile.

[0105] A request to link or unlink a User Identity and a SUPI may be issued, for example, by an AF or NEF (e.g., by invoking the Nudm_UIP_Modify service operation). The UDM may authorize the request. The SUPI may be stored in the User Identity Profile, for example, if the request is authorized. The UDM may authorize the request, for example, based on local configuration information and operator policy.

[0106] The Content of the User Identity Profile may be accessed and / or read.

[0107] User Profile information may be read in the UDR, for example, by the UDM. The UDM may read the User Profile information by invoking a service (e.g., Nudr_DM_Query service) and / or using a user identifier as a data key.

[0108] The UDM may support a service operation (e.g., Nudm_Userl dentityProfile(UI P)_Get service operation). Consumers of the Nudm_UIP_Get service operation may include the AF, AMF, and NEF. The AF, AMF, and NEF may invoke the Nudm_UIP_Get service operation to read the content of the user profile.

[0109] A request to read information from a User Identity Profile may be issued, for example, by an AF, AMF, or NEF (e.g., by invoking the Nudm_UIP_Get service operation). The UDM may authorize the request. If the request is authorized, the UDM may provide information from the User Identity Profile. The UDM may authorize the request, for example, based on local configuration and operator policy.

[0110] This request (e.g., to read information) may be invoked to check if a User Identifier is linked to a SUPI.

[0111] Details associated with linking and unlinking, associating a user with a WTRU’s registration, and associating a user with a WTRU’s PDU Sessions may be described herein.

[0112] Linking and unlinking may be performed.

[0113] FIG. 2 shows an example of how an AF may request that a subscription and user identity be linked or unlinked. For example, FIG. 2 may illustrate an example of registration to associate (e.g., begin the association of) a user to a subscription.

[0114] As shown in FIG. 2 at 1, a link request may be sent (e.g., the AF may send a Link Request to the NEF). The request may include one or more of a User Identifier, a subscription identifier (e.g., a SUPI or External ID), and / or an indication of whether the request may be to link or unlink.

[0115] As shown in FIG. 2 at 2, the link or unlink request may be sent, for example, to the UDM (e.g., NEF may invoke the Nudm_UIP_Modify service operation to send the link or unlink request to the UDM). The UDM may form the identifier link (e.g., by updating the User Profile to include the SUPI), for example, if the UDM authorizes the request to link. If the UDM authorizes the request to unlink, then the UDM may delete the identifier link, for example, by updating the User Profile to remove the SUPI. The UDM may respond to the service invocation, for example, by indicating that the link or unlink request was successful.

[0116] As shown in FIG. 2 at 3, an indication of whether the link or unlink request was successful may be sent (e.g., the NEF may respond to the AF, for example, with an indication of whether the link or unlink request was successful).

[0117] Registration may be performed.

[0118] FIG. 3 shows an example of how the WTRU may indicate the identity of its user to the network. The WTRU may be triggered to perform this procedure (e.g., trigger the Registration Message and include a user identity in the registration message), for example, based on a request from an application on the WTRU. The application may include a graphical user interface (GUI) that allows the human user to enter the user identifier and a credential that is associated with the user identifier (e.g., a password). The Application may provide the user identifier to the WTRU (e.g., via an AT Command). The WTRU may send a message (e.g., EAP messages) that is associated with authenticating the user identifier to the application. The application may send messages (e.g., EAP messages) that are associated with authenticating the user identifier to the application to the WTRU. The exchange of the EAP messages between the WTRU and WTRU Application may be for authentication of the user identifier. The exchange of EAP messages between the WTRU and Application may be performed, for example, via an API or AT Command.

[0119] FIG. 3 illustrates an example of registration to begin the association of a user to a subscription.

[0120] As shown in FIG. 3 at 1, the WTRU may send a Registration Request to the AMF (e.g., similar to that of a general registration procedure). The Registration Request may include a User Identifier.

[0121] As shown in FIG. 3 at 2, actions associated with a General Registration procedure may be executed.

[0122] As shown in FIG. 3 at 3, the AMF may invoke a service operation (e.g., an Nudm_UIP_Get service operation). The service invocation may include the SUPI of the WTRU and the User Identity. The response from the UDM may indicate whether (e.g., if) the User Identity is linked to the SUPI. Theresponse from the UDM may include the S-NSSAI(s) that the user is authorized to access, for example, if the User Identity is linked to the SUPI. The AMF may allow (e.g., only allow) slices, for example, if the user is authorized to access the slice. If the Requested NSSAI included slices that the user is not allowed to access, then the AMF may include these slices in the Rejected NSSAI and send the Rejected NSSAI in the Registration Accept message. The rejection cause value(s) in the Rejected NSSAI may indicate that connection to the slice was rejected because the user is not allowed to access the slice.

[0123] As shown in FIG. 3 at 4 actions associated with the General Registration procedure may be performed / executed.

[0124] As shown in FIG. 3 at 5, the AMF may send a Registration Accept message to the WTRU (e.g., similar to actions performed in the General Registration). The Registration Accept message may indicate if the User Identity is linked to the SUPI. At this point, the User Identity may not be (e.g., yet be) authenticated. If the AMF determines that the User Identity is not linked to the subscription, the AMF may send the registration accept message and may include an indication that the user is not linked to the subscription (e.g., and refrain from performing actions (e.g., skip actions) associated with 6 as shown in FIG. 3).

[0125] As shown in FIG. 3 at 6, the User Identifier may be authenticated. As part of the authentication procedure, the WTRU may be notified if the user was authenticated or not. If the WTRU is not authenticated, an action (e.g., number of actions) may be performed based the lack of authentication. In examples, a WTRU may send a different (e.g., new) Registration Request (e.g., to request slices that are not authorized for the user).

[0126] In examples, the Registration Request may include multiple user identifiers. This may be useful in a scenario where multiple users are simultaneously using a WTRU, for example, in a gaming scenario. The registration response may indicate whether each user identifier from the registration request is allowed use the WTRU’s subscription. In this scenario, the AMF may trigger authentication (e.g., EAP authentication procedures) to authenticate a (e.g., each) user.

[0127] In examples, the network may send the WTRU a list of user identities that are linked to the WTRU’s subscription. Sending the WTRU such a list may enable the WTRU to check if the user identity is in the list before the WTRU includes the user identifier in the Registration Request. The network may send, and the WTRU may receive the list in a Registration Accept message or a WTRU Configuration Update command.

[0128] PDU Session Establishment may be performed.

[0129] FIG. 4 shows an example of how user identity information may be used by the network in a PDU session establishment procedure.

[0130] FIG. 4 illustrates an example of PDU session establishment when a user identity may be already associated with a subscription.

[0131] As shown in FIG. 4 at 1 actions associated with WTRU requested PDU session establishment may be performed.

[0132] As shown in FIG. 4 at 2, the AMF may invoke Nsmf_PDUSession_CreateSMContext (e.g., with respect to actions associated with a WTRU Requested PDU Session Establishment procedure). The AMF may send the user identifier to the network entity (e.g., SMF or PCF), for example, if there is already a user identifier linked to the WTRU’s subscription.

[0133] As shown in FIG. 4 at 3, the SMF may query the UDM / UDR. The Default QoS parameters may be obtained (e.g., by the SMF) from the User Profile for the DNN / S-NSSAI combination. The user’s Default QoS parameters may be considered (e.g., by the SMF), for example, if (e.g., when) creating the QoS Rules, QoS Profile, and N4 Rules.

[0134] In examples, the SMF may provide the user identifier to the PCF (e.g., similar to that of 2 in FIG. 4) that serves the PDU Session. The PCF may then provide PCC rules (e.g., new PCC Rules) to the SMF. The PCF may obtain the Default QoS parameters for the User from the User Profile for the DNN / S-NSSAI combination (e.g., similar to that of 3 in FIG. 4). The PCF may use the Default QoS Rules to derive PCC rules (e.g., new PCC Rules) for the PDU and then provide the PCC rules (e.g., new PCC Rules) to the SMF. The SMF may use the PCC Rules to derive (e.g., new) QoS Rules, QoS Profile, and N4 Rules for the PDU Session.

[0135] As shown in FIG. 4 at 4, actions associated with the WTRU requested PDU session establishment procedure may be performed.

[0136] PDU session modification may be performed.

[0137] FIG. 5 shows an example of how the user identity information may be used by the network in a PDU session modification procedure. This procedure may be initiated, for example, if (e.g., when) a user is authenticated and authorized to use a subscription (e.g., so that existing PDU Sessions may be reconfigured to consider the identity of the user of the WTRU).

[0138] FIG. 5 illustrates an example PDU Session Modification if a User Identity may be authenticated to be associated with a subscription.

[0139] As shown in FIG. 5 at 1, the first network entity (e.g., AMF or SMF) may notify a second network entity (e.g., SMF or PCF) that the WTRU’s registration is not associated with a User Identifier (e.g., invoke Nsmf_PDUSession_UpdateSMContext to notify the SMF / PCF that the WTRU’s registration is notassociated with a User Identifier), for example, if (e.g., when) a user had been authenticated and is using the WTRU’s subscription.

[0140] As shown in FIG. 5 at 2, the second network entity (e.g., SMF or PCF) may query the UDM / UDR. The Default QoS parameters may be obtained from the User Profile for the DNN / S-NSSAI combination. The second network entity (e.g., SMF or PCF) may consider the user’s Default QoS parameters if (e.g., when) creating the QoS Rules, QoS Profile, and N4 Rules.

[0141] As shown in FIG. 5 at 3, actions associated with network requested PDU session modification may be performed.

[0142] Details related to authenticating and authorizing a user may be provided herein.

[0143] To authenticate the human user of a WTRU subscription, a Network Slice-Specific Authentication and Authorization procedure may be used (e.g., reused) using one or more of the following changes.

[0144] The network entity (e.g., AMF or SMF) may be triggered to perform the procedure, for example, if (e.g., when) it receives a request from the user to use the subscription and the network entity (e.g., AMF or SMF) has verified that the user is linked to the subscription.

[0145] If the network entity (e.g., AMF or SMF) is triggered to perform the procedure and the network entity (e.g., AMF or SMF) is not able to communicate with the AAA-S, the network entity (e.g., AMF or SMF) may send a message (e.g., NAS MM Transport message) to the WTRU and / or indicate that the User Identity cannot be authenticated. In examples, a network entity (e.g., AMF or SMF) may not be able to communicate with the AAA-S. An example roaming scenario may include where the network entity (e.g., AMF or SMF) is not able to communicate with the AAA-S of the domain that manages the user identifier.

[0146] A user identity may be used in the procedure instead of S-NSSAI.

[0147] An AAA-P or an AAA-S may be selected (e.g., based on the domain that manages the User Identity), for example, instead of selecting an AAA-P or an AAA-S based on the S-NSSAI.

[0148] The network entity (e.g., AMF or SMF) may store the result in the User Profile, for example, if (e.g., when) the authentication and authorization procedure is complete. The result may then be exposed from the user profile.

[0149] The network may determine the domain that manages the User Identity based on the domain field of the user identity.

[0150] Once authenticated and authorized, it may be assumed that the specific user identifier is associated with the WTRU’s traffic (e.g., all of the WTRU's traffic) during the time that specific user identifier is active with the WTRU's subscription. User specific policies (e.g., QoS settings) can then be taken into account by the system (e.g., 5GS) in order to provide service differentiation. Completion of thisprocedure may cause the network entity (e.g., AMF or SMF) to trigger PDU Session Modification procedure(s).

[0151] Details related to the exposure of User Profile information may be provided herein.

[0152] FIG. 6 illustrates an example of exposing user profile information. It may be assumed that theUser Profile information is read in the UDR by the UDM. The UDM may invoke a service (e.g., the Nudr_DM_Query service) and use a user identifier as a data key.

[0153] The UDM may support an Nudm_Userl dentityProfile(UI P)_Get service operation. In examples, the NEF may be a consumer of the Nudm_UIP_Get service operation.

[0154] A request to read information from a User Identity Profile may be issued (e.g., by the NEF), for example, by invoking a service operation (e.g., the Nudm_UIP_Get service operation). The UDM may authorize the request. The UDM may provide information from the User Identity Profile, for example, if the request is authorized. The UDM may authorize the request, for example, based on local configuration information and / or operator policy.

[0155] FIG. 6 illustrates an example of exposure of User Profile information.

[0156] As shown in FIG. 6 at 1, the AF may send a request to read information from a User Profile to the NEF. The request may include the User Identifier, an AF identifier, a data key, and / or the like. The NEF may check (e.g., based on local configuration) if the AF is authorized to read the user profile (e.g., whether the AF is authorized to read the user profile of users that are in the domain of the provided user identifier). If the AF is not authorized, actions may be skipped (e.g., actions as show at 2 in FIG. 6 may be skipped), and an error response may be returned (e.g., as shown in FIG.6 at 3).

[0157] The Data Key may indicate if the AF wants to obtain a list of subscription(s) that are linked to the user identifier or read what subscription the user is currently authorized to use.

[0158] The network may determine the domain that manages the User Identity, for example, based on the domain field of the user identity.

[0159] As shown in FIG. 6 at 2, the NEF may invoke a service operation (e.g., an Nudm_UIP_GET service operation) to read information from the user profile. The user identity and data key may be provided in the service invocation. The UDM / UDR may send a response to the NEF with the requested information.

[0160] As shown in FIG. 6 at 3, the NEF may respond to the AF with the requested information.

[0161] Details associated with associating a human user with a subscription are described herein and may include one or more of the following. The WTRU may provide the user identifier during registration. The WTRU may provide and / or receive the user identifier in the NAS MM Transport messages that carry the EAP messages. An AMF may read information from the User Profile by invoking a UDM Service. AnAMF may trigger the authentication procedure. An AMF may send a NAS MM Transport message with an EAP ID Request and the user identity. An AMF may receive a NAS MM Transport message with an EAP ID Response and the user identity. An AMF may store the result of the authentication and authorization procedure in the User Profile. A UDM may authorize requests from an AF to (un)link a user to a subscription. A UDM may receive a request from the NEF to read user profile information and may send a response. An UDR may store user profiles. An NEF may process requests from the AF to (un)link a user to a subscription. An NEF may receive a request from the AF to read user profile information and may send a response. An NEF may check that the AF is authorized to read the user profile. An NEF may send a request from the UDM / / UDR to read user profile information and may receive a response. An SMF may receive a user identifier from the AMF for a PDU Session. An SMF may read the user’s Default QoS parameters from the UDM / UDR. An AF may send a request to the NEF to read user profile information and may receive a response. An NSSAAF may select a AAA-P or a AAA-S based on the User Identity.

[0162] Although features and elements described above are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without other features and elements.

[0163] Although the implementations described herein may consider 3GPP specific protocols, it is understood that the implementations described herein are not restricted to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

[0164] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and / or wireless connections) and / or computer-readable storage media. Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

Claims

CLAIMSWhat Is Claimed Is1 . A first network entity, the first network entity comprising, a processor configured to: receive, from a second network entity, a first message indicating a user identity associated with a protocol data unit (PDU) session; determine a quality of service (QoS) parameter based on the user identity and a data network name (DNN)Zsingle network slice selection assistance information (S-NSSAI) combination associated with the PDU session; determine a policy and charging control (PCC) rule based on the QoS parameter, wherein the determined PCC rule is associated with the PDU session; and send the PCC rule to the second network entity.

2. The first network entity of claim 1 , wherein the first network entity is policy control function (PCF) network entity, and wherein the second network entity is a session management function (SMF) network entity.

3. The first network entity of claim 1 or 2, wherein the processor is further configured to: send a second message to a user data management (UDM) network entity, wherein the second message requests the QoS parameter associated with the DNN / S-NSSAI combination and with the user identity associated with the PDU session; and receive a third message, wherein the third message indicates the QoS parameter associated with the DNN / S-NSSAI combination and the user identity associated with the PDU session.

4. The first network entity of any of claims 1 to 3, wherein the user identity is used to identify traffic associated with a wireless transmit / receive unit (WTRU), wherein the WTRU is associated with the user.

5. The first network entity of any of claims 1 to 4, wherein the user identity is associated with a user profile, wherein the user profile is associated with at least a first DNN / S-NSSAI combination and a firstdefault QoS parameter, wherein the first default QoS parameter is associated with the first DNN / S-NSSAI combination.

6. The first network entity of claim 5, wherein the DNN / S-NSSAI combination associated with the PDU session is the first DNN / S-NSSAI combination, and wherein the QoS parameter determined based on the user identity and the DNN / S-NSSAI combination is the first default QoS parameter.

7. The first network entity of claim 5 or 6, wherein the first default QoS parameter is at least one of a first default value associated with a QoS identifier (QI), a second default value associated with an allocation and retention priority (ARP), or a priority level associated with QI.

8. The first network entity of any of claims 1 to 7, wherein the user identity comprises at least one of a domain identifier or a local identifier, wherein the domain identifier is associated with a domain, wherein the local identifier indicates a user in the domain, and wherein the domain is associated with a mobile network operator.

9. The first network entity of any of claims 1 to 8, wherein the user identity comprises an application function identifier that indicates an application function network entity, wherein the application function network entity is associated with at least one of linking a user to a first subscription, unlinking the user from a second subscription, storing information in a user profile, reading information from the user profile, or authenticating a user.

10. A method comprising: receiving, from a network entity, a first message indicating a user identity associated with a protocol data unit (PDU) session; determining a quality of service (QoS) parameter based on the user identity and a data network name (DNN)Zsingle network slice selection assistance information (S-NSSAI) combination associated with the PDU session; determining a policy and charging control (PCC) rule based on the QoS parameter, wherein the determined PCC rule is associated with the PDU session; and sending the PCC rule to the network entity.11 . The method of claim 10, wherein the method is performed by a policy control function (PCF) network entity, and wherein the network entity is a session management function (SMF) network entity.

12. The method of claim 10 or 11 , wherein the method further comprises: sending a second message to a user data management (UDM) network entity, wherein the second message requests the QoS parameter associated with the DNN / S-NSSAI combination and with the user identity associated with the PDU session; and receiving a third message, wherein the third message indicates the QoS parameter associated with the DNN / S-NSSAI combination and the user identity associated with the PDU session.

13. The method of any of claims 10 to 12, wherein the user identity is used to identify traffic associated with a wireless transmit / receive unit (WTRU), wherein the WTRU is associated with the user.

14. The method of any of claims 10 to 13, wherein the user identity is associated with a user profile, wherein the user profile is associated with at least a first DNN / S-NSSAI combination and a first default QoS parameter, wherein the first default QoS parameter is associated with the first DNN / S-NSSAI combination.

15. The method of claim 14, wherein the DNN / S-NSSAI combination associated with the PDU session is the first DNN / S-NSSAI combination, and wherein the QoS parameter determined based on the user identity and the DNN / S-NSSAI combination is the first default QoS parameter.

16. The method of claim 14 or 15, wherein the first default QoS parameter is at least one of a first default value associated with a QoS identifier (QI), a second default value associated with an allocation and retention priority (ARP), or a priority level associated with QI.

17. The method of any of claims 10 to 16, wherein the user identity comprises at least one of a domain identifier or a local identifier, wherein the domain identifier is associated with a domain, wherein the local identifier indicates a user in the domain, and wherein the domain is associated with a mobile network operator.

18. The method of any of claims 10 to 17, wherein the user identity comprises an application function identifier that indicates an application function network entity, wherein the application function networkentity is associated with at least one of linking a user to a first subscription, unlinking the user from a second subscription, storing information in a user profile, reading information from the user profile, or authenticating a user.

Images