WO2025208008A1 - Associating a human user with a subscription - Google Patents

Abstract

Systems and methods are described herein for associating a human user with a subscription. A human user may be identified. The human user may be associated with a wireless transmit/receive unit (WTRU). The human user may be associated with the WTRU's traffic. Authentication and authorization associated with the human user may be triggered and/or performed. The human user may be authenticated and authorized. Network entities (e.g., access management function, session management function, etc.) may be informed about the human user association. Traffic sessions may be adjusted based on user identity profile information. The network entities may be informed if (e.g., when) the human user logs in or logs out.

Description

ASSOCIATING A HUMAN USER WITH A SUBSCRIPTION

CROSS-REFERENCE TO RELATED APPLICATOINS

[0001] The application claims the benefit of U.S. Provisional Application 63/571 ,527, filed March 29, 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. A human user may be identified. The human user may be associated with a wireless transmit/receive unit (WTRU). The human user may be associated with the WTRU’s traffic. Authentication and authorization associated with the human user may be triggered and/or performed. The human user may be authenticated and authorized. Network entities (e.g., access management function, session management function, etc.) may be informed about the human user association. Traffic sessions may be adjusted based on user identity profile information. The network entities may be informed if (e.g., when) the human user logs in or logs out.

[0004] A first network entity (e.g., access management function) may receive a first message that indicates that a user identity is associated with a WTRU. The first network entity may obtain user information associated with user access. The user information may be associated with a user profile. The user information may include a list of identifiers (e.g., list of data network name/single network slice selection assistance information (DNN/S-NSSAI) combinations) that the user is allowed to access. The list may indicate access permissions associated with the user identity. The first network entity may send (e.g., to at least a second network entity) a second message, for example, that may include the user identity and/or an indication that indicates that the user identity is associated with successful authentication and authorization. The second message may indicate a list associated with user access. [0005] A first network entity may receive a message that indicates a user identity is to be associated with a protocol data unit (PDU) session that the first network entity serves. The first network entity may invoke a service operation associated with updating the status of the user identity. The status of the user identity may be updated to indicate that the user identity has been successfully authenticated and authorized. The first network entity may send an indication to a second network entity that indicates that the user identity has been successfully authenticated and authorized.

[0006] A first network entity may receive a user identifier. The first network entity may receive an indication that indicates that a user associated with the user identifier was successfully authenticated and associated with data traffic. The first network entity may obtain user identity profile information associated with the user. The user identity profile information may indicate access information. The first network entity may send a message to a WTRU. The message may indicate a rule associated with the user profile. The rule may be a quality of service rule.

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0008] 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.

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

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

[0011] FIG. 2 illustrates an example of a network identifying a human user of the WTRU logging in and associating WTRU traffic with the active human user.

[0012] FIG. 3 illustrates an example of when the human user logs out of the WTRU, handling, and transfer of the information from the WTRU to various network functions.

DETAILED DESCRIPTION

[0013] 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.

[0014] 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.

[0015] 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.

[0016] 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.

[0017] 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).

[0018] 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).

[0019] 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).

[0020] 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).

[0021] 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).

[0022] 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.

[0023] 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.

[0024] 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.

[0025] 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.

[0026] 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.

[0027] 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.

[0028] 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 Specific Integrated 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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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).

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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 transmission and 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)).

[0037] 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.

[0038] 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. [0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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. [0046] In representative embodiments, the other network 112 may be a WLAN.

[0047] 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.

[0048] 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 the AP. 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.

[0049] 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.

[0050] 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).

[0051] 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).

[0052] 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.

[0053] 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.

[0054] 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 [0055] 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).

[0056] 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).

[0057] 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. [0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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 may perform 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.

[0066] 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. [0067] Systems and methods are described herein for associating a human user with a subscription. A human user may be identified. The human user may be associated with a wireless transmit/receive unit (WTRU). The human user may be associated with the WTRU’s traffic. Authentication and authorization associated with the human user may be triggered and/or performed. The human user may be authenticated and authorized. Network entities (e.g., access management function, session management function, etc.) may be informed about the human user association. Traffic sessions may be adjusted based on user identity profile information. The network entities may be informed if (e.g., when) the human user logs in or logs out.

[0068] A first network entity (e.g., access management function) may receive a first message that indicates that a user identity is associated with a WTRU. The first network entity may obtain user information associated with user access. The user information may be associated with a user profile. The user information may include a list of identifiers (e.g., list of data network name/single network slice selection assistance information (DNN/S-NSSAI) combinations) that the user is allowed to access. The list may indicate access permissions associated with the user identity. The first network entity may send (e.g., to at least a second network entity) a second message, for example, that may include the user identity and/or an indication that indicates that the user identity is associated with successful authentication and authorization. The second message may indicate a list associated with user access.

[0069] A first network entity may receive a message that indicates a user identity is to be associated with a protocol data unit (PDU) session that the first network entity serves. The first network entity may invoke a service operation associated with updating the status of the user identity. The status of the user identity may be updated to indicate that the user identity has been successfully authenticated and authorized. The first network entity may send an indication to a second network entity that indicates that the user identity has been successfully authenticated and authorized.

[0070] A first network entity may receive a user identifier. The first network entity may receive an indication that indicates that a user associated with the user identifier was successfully authenticated and associated with data traffic. The first network entity may obtain user identity profile information associated with the user. The user identity profile information may indicate access information. The first network entity may send a message to a WTRU. The message may indicate a rule associated with the user profile. The rule may be a quality of service rule.

[0071] Access and mobility function (AMF) actions may be performed. For example, AMF actions may be performed based on successful authentication of a human user of the WTRU.

[0072] The AMF may (e.g., be enabled) to tell a session management function (SMF) if the SMF may release the PDU Session (e.g., because the user is not allowed to access the data network name/single network slice selection assistance information (DNN/S-NSSAI)) or tell the user identity to the SMF, for example, so that the SMF may obtain user settings (e.g., the user-specific settings).

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

[0074] The AMF may receive a message, for example, that indicates that a user identity is associated with the WTRU. The message may include the user identity (e.g., user identity associated with a user profile). The message may be received (e.g., from a session management entity or a user data management entity), for example, based on one or more of the following. FIG. 2 illustrates an example of a human user of a WTRU logging in. As shown at 7b in FIG. 2, the AMF may be informed (e.g., by the UDM NudmJJI P_Notification service operation) about a change in user identity profile status (e.g., the user identifier is successfully authenticated and authorized). As shown in FIG. 2 at 8, the AMF may receive a message (e.g., message transfer, e.g., the N1 N2MessageTransfer) from a first SMF about the successful authentication and authorization of the human user of the WTRU (e.g., which may provide the user identifier, Authentication and Authorization status, other user identity profile information, etc.) along with a container (e.g., the N1 SM container) which may contain a PDU Session Establishment accept message.

[0075] As shown at 10 in FIG. 2, the AMF may check the user identity profile (e.g., user profile). The AMF may obtain a list of DNN/S-NSSAI combinations that the user is allowed to access (e.g., authorized to access).

[0076] As shown at 10 in FIG. 2, the AMF may provide the user identifier and/or a successful authentication and authorization status to SMF(s) (e.g., all the SMFs, for example, a second SMF (e.g., based on a determination that the second SMF is associated with the WTRU traffic) which may be associated with the WTRU traffic (e.g., the SMFs that serve PDU Sessions of the WTRU). The message to the SMF(s) (e.g., first SMF and/or second SMFs) may indicate whether or not the user is allowed to access the DNN/S-NSSAI combination of the PDU Session that is served by the SMF(s) (e.g., first and/or second second SMFs).

[0077] SMF (e.g., first SMF) actions may be performed, for example, based on successful authentication of the human user of the WTRU.

[0078] As shown at 4, 5, and 6 in FIG. 2, the SMF may receive a message that indicates that a user identity be associated with a PDU Session that the SMF serves. The SMF may participate in a procedure to authenticate the user. The SMF may determine that the user has been authenticated.

[0079] As shown at 7a in FIG. 2, the SMF may invoke a service operation (e.g., UDM Nudm_UIP_Modify service operation) to update the status of the user identifier as being successfully authenticated and authorized with the UDM. [0080] As shown at 8 in FIG. 2, the SMF may inform the AMF (e.g., via the N1 N2MessageTransfer) about the successful authentication and authorization of the human user of the WTRU (e.g., and provide the user identifier, Authentication and Authorization status, other user identity profile information, etc.) and/or a container (e.g., the N1 SM container) containing the PDU Session Establishment accept message.

[0081] SMF (e.g., second SMF) actions may be performed, for example, at successful authentication of the human user of the WTRU.

[0082] An SMF may perform one or more of the following.

[0083] As shown at 10 in FIG. 2, the SMF may receive a user identifier and/or an indication that the user was successfully authenticated and associated with the WTRU traffic.

[0084] As shown at 11 in FIG. 2, the SMF may obtain information from the user identity profile. The information may indicate if the user is allowed to access the DNN/S-NSSAI combination of the PDU Session that the SMF serves.The information may indicate QoS Settings for the WTRU.

[0085] As shown at 12 in FIG. 2, the SMF may send a PDU Session Modification Command message to the WTRU (e.g., based on the information in the user profile indicating that the user is allowed to access the DNN/S-NSSAI combination). The message may include QoS Rule(s). The QoS rules may be based on the QoS information from the user profile.

[0086] As shown at 13 in FIG. 2, the SMF may send a PDU Session Release message to the WTRU (e.g., based on the information in the user profile indicating that the user is not allowed to access the DNN/S-NSSAI combination). The message may include a cause code. The WTRU may use the cause code to take appropriate action e.g., re-establish the PDU session with a different DNN/S-NSSAI combination, etc.

[0087] User Identifiers may be used (e.g., in a 5G System)

[0088] The usage of user identifiers may be supported (e.g., in the 5G system).

[0089] Operators may (e.g., be allowed to) utilize user-specific identities in a network (e.g., in the 3GPP network), for example, to provide a service delivery tailored based on the user identity. A user identity may be that of a human using a WTRU or an application running on the WTRU or a device behind a WTRU gateway.

[0090] Service level parameters, requirements, and/or definitions related to User Profiles and User Identity may be specified.

[0091] Secondary authentication (e.g., 3GPP secondary authentication) may be performed, for example, by a third party. [0092] Secondary authentication may include where a WTRU is authenticated by a third party authentication server, for example, via intermediate functions in the 5GC (e.g., SMF, AMF, NEF). Seconday authentication may include one or more of the following: PDU Session Secondary authentication and authorization (A&A), network slice-specific authentication and authorization (NSSAA), and/or uncrewed aerial vehicles (UAV) uncrewed aerial system service supplier (USS) authentication and authorization (UUAA). The WTRU may use a user identity and/or credential (e.g., non 3GPP user identity and credentials) during an authentication and authorization procedure, for example, before being granted access to the network resources (e.g., PDU Session, network slice, DN).

[0093] There may be no way to identify the human user of a subscription in a system (e.g., in a 5G system). The system (e.g., 5G system) may not be aware of the identity of the user (e.g., human) who is using a WTRU to send and receive traffic. The identity of the user may be provided to the network during PDU Session Establishment. For example, the secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session feature may be used to request the user identification and authenticate the user.

[0094] The user identity may be known (e.g., only be known) in the context of a (e.g., single) PDU Session, for example, if a user is authenticated during PDU Session Establishment. The SMF that serves the PDU may (e.g., be able to) consider the user identity and information from the user identity profile, for example, if (e.g., when) providing service to the WTRU. For example, the SMF that serves the PDU Session may (e.g., be able to) use information from the User Identity Profile, for example, to configure the QoS Rules for the PDU Session. Such an approach may refrain from providing a means for the user identity to be known by the network functions (e.g., SMFs) that serve other PDU Sessions that the WTRU may have established or may establish. This approach may refrain from associating the user identifier with some or all of the WTRU’s traffic.

[0095] The Secondary authentication/authorization (e.g., by a DN-AAA server during the establishment of a PDU Session feature) may be used to authenticate a user. A user may be authenticated within a first PDU Session. The other PDU Session(s) (e.g., a second PDU session, third PDU session, etc.) of the WTRU may (e.g., be configured to) consider the identity of the user if (e.g., when) providing service to the WTRU. The network function entities (e.g., SMFs, 5G NFs) which may be serving the WTRU may be informed about the active human user/user identifier of the WTRU. Traffic (e.g., ongoing traffic sessions) may be adjusted, for example, based on the user identity profile information (e.g., stored in the UDM/user data repository (UDR)). 5G NFs may be informed about a log out event, for example, if (e.g., once) the human user logs out,. The information associated with the log out event may be considered. For example, the information associated with the log out event may trigger an adjustment of traffic (e.g., the ongoing traffic) associated with the WTRU. This may result in some ongoing PDU session being modified or released as per the user identity profile information.

[0096] Conditions and/or pre-conditions may be used (e.g., assumed) for one or more of the following. Some of the pre-conditions (e.g., not all of the following pre-conditions) may be considered (e.g., are necessary) for application in a communications system.

[0097] A User Identifier may include a Domain Identifier (e.g., component) and/or a Local Identifier (e.g., component).

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

[0099] A user may be linked and/or unlinked to subscriptions, for example, based on requests from the AF (e.g., via the NEF). Linked may mean that the user profile stores an indication that the user may use (e.g., may be allowed to use) a subscription.

[0100] A user profile may store an indication which indicates the authentication and authorization status of the user identifier (e.g., if user identity is already authenticated and authorized or a that (e.g., a fresh) authentication and authorization is required).

[0101] A WTRU may be provisioned with information (e.g., a DNN / S-NSSAI combination) that may be used for authenticating users. For example, the WTRU may receive a WTRU route selection policy (URSP) Rule. The traffic descriptor of the URSP Rule may indicate user identity authentication. The URSP Rule may trigger the WTRU to send a PDU Session Establishment Request, for example, if (e.g., when) application layer activity triggers user authentication. The PDU Session Establishment Request may include the DNN / S-NSSAI combination that may be used for authenticating users, for example, if (e.g., when) application layer activity triggers user authentication.

[0102] The SMF of the PDU Session may provide the AMF the user identifier. The SMF of the PDU session may provide the AMF the user identifier, for example, if (e.g., once) a user is authenticated within a PDU Session. The AMF may provide the user identifier to the SMF(s) that serve a PDU session (e.g., any PDU Session(s)) associated with the WTRU. The SMF(s) may obtain the user’s QoS parameters from the User Profile. A (e.g., each) SMF may be associated with a PDU Session that is associated with a certain DNN/S-NSSAI combination. The SMF may obtain the QoS parameters for the associated DNN / S-NSSAI combination. The SMF may consider the user’s QoS parameters in (e.g., when) creating the QoS Rules, QoS Profile, and/or N4 Rules for the PDU Session.

[0103] A human user of the WTRU may log in. [0104] FIG. 2 illustrates an example of a network identifying a human user of the WTRU logging in and associating WTRU traffic with the active human user.

[0105] As shown at 1 in FIG. 2, the WTRU may be successfully registered with the network (e.g., 5G network). The WTRU may receive configuration information, for example, indicating (e.g., configured with) the DNN/S-NSSAI combination (e.g., special DNN/S-NSSAI combination). The DNN/S-NSSAI combination may be used by the network for authenticating the users, e.g., human users linked with the subscription (e.g., 5G subscription) associated with the WTRU. For example, this may be achieved by configuring the WTRU with a rule/condition (e.g., URSP Rule) that includes a Traffic Descriptor that indicates user authentication. The route selection descriptor (RSD) of the URSP Rule may include the special DNN/S- NSSAI combination.

[0106] As shown at 2 in FIG. 2, the human user of the WTRU may log into the WTRU, for example, as per the configured rules (e.g., a URSP rule that includes a traffic descriptor indicating user authentication and RSD of the URSP rule may include special DNN/S-NSSAI combination for authenticating the human user of the WTRU). The WTRU may trigger PDU session establishment with a provisioned DNN/S-NSSAI toward the network (e.g., 5G network). The WTRU may provide the user identifier associated with the human user of the WTRU to the network.

[0107] The WTRU may trigger a PDU session modification (e.g., to associate the existing session with the user identifier associated with the human user of the WTRU), for example, by providing the user identifier to the network (e.g., if the PDU session with the same DNN/S-NSSAI combination already exists). [0108] As shown at 3 in FIG. 2, the AMF may select an SMF.

[0109] As shown at 4 in FIG. 2, the AMF may invoke a service operation (e.g.,

Nsmf_PDUSession_CreateSMContext), for example, with respect to a WTRU Requested PDU Session Establishment procedure. The AMF may send the user identifier to the SMF, for example, if there is (e.g., already) a user identifier linked to the WTRU’s subscription. This user identifier may identify the human user of the WTRU.

[0110] As shown at 5a/5b in FIG. 2, the SMF may query the UDM/UDR. The SMF may obtain one or more of the following: a user identity profile, a security flag indicating whether authentication is used (e.g., needed) for the user identifier or the user identifier is already successfully authenticated, security details for the authentication process, the Default QoS parameters from the User Profile for the DNN / S-NSSAI combination, and/or the like. The security details may include an indication about the security (e.g., security method) used (e.g., to be used) for authenticating the user identifier (e.g., which could be either set to secondary authentication or authentication via AUSF/UDM). [0111] As shown at 6 in FIG. 2, the authentication procedure may be triggered (e.g., as per the security flag and security details associated with 5a/b in FIG. 2). The user identifier may be successfully authenticated and authorized, for example, using either the secondary authentication or via AUSF/UDM based authentication procedure.

[0112] As shown at 7a/b in FIG. 2, the SMF may invoke a service operation (e.g., UDM Nudm_UIP_Modify service operation), for example, to update the status of the user identifier as being successfully authenticated and authorized. The UDM may invoke the service operation (e.g., NudmJJI P_Notification service operation) to inform the subscribed AMF about a change in user identity profile status (e.g., the user identifier is successfully authenticated and authorized).

[0113] As shown at 8 in FIG. 2, the SMF may inform the AMF (e.g., via the N1 N2MessageTransfer) about the successful authentication and authorization of the human user of the WTRU (e.g., and may provide the user identifier, Authentication and Authorization status, other user identity profile information, etc.) along with the N1 SM container containing the PDU Session Establishment accept message.

[0114] In examples, the actions shown at 8 in FIG. 2 may be an alternative to the actions shown at 7b in FIG. 2.

[0115] As shown at 9 in FIG. 2, the AMF may provide a message (e.g., the PDU Session Establishment accept message) to the WTRU (e.g., via the NAS DL transport received from the SMF via N1 SM container). The network may (e.g., decide to) keep the PDU session (e.g., special PDU session) alive while the human user is actively associated with the WTRU, e.g., to periodically re-authenticate the human user of the WTRU. The network may (e.g., decide to) use this PDU session (e.g., exclusively) for authenticating the human users of the WTRU (e.g., no other user plane traffic is generated for the PDU session).

[0116] As shown at 10 in FIG. 2, the AMF may provide the user identifier along with a successful authentication and authorization status to (e.g., all) the SMFs which are associated with the WTRU’s traffic. The AMF may provide the user identifier to the SMF(s) that serve other established PDU Sessions of the WTRU. The AMF may check the user identity profile and obtain a list of DNN/S-NSSAI combinations that the user is allowed to access (e.g., optionally), for example, before notifying the SMF. The notification that is sent to a (e.g., each) SMF may include an indication of whether or not the user is allowed to access the DNN/S-NSSAI combination of the PDU Session that is served by the SMF.

[0117] As shown at 11 a/b in FIG. 2, the SMF(s) may query the UDM/UDR. The SMF may obtain information from a user identity profile. For example, the QoS parameters corresponding to the user identifier (e.g., Human user of the WTRU) may be provided by the UDM/UDR to the SMF. The SMF may provide the DNN/S-NSSAI that is associated with the PDU Session that the SMF serves (e.g., so that the UDM/UDR knows that QoS Parameters to provide). [0118] As shown at 12 in FIG. 2, the SMF may use (e.g., consider) the user’s QoS parameters to update one or more of the following: the QoS Rules, QoS Profile, and/or N4 Rules of the existing ongoing PDU sessions. This may cause the SMF to trigger a PDU Session modification provided to deliver the QoS Rules to the WTRU, the QoS Profile to RAN, and/or N4 Rules to the UPF.

[0119] As shown at 13 in FIG. 2, the SMF may receive the associated user identifier and/or user identity profile information (e.g., from the UDM/UDR). Accordingly, the SMF may not be allowed to access (e.g., not authorized) a particular DNN/S-NSSAI combination and may (e.g., have to) release the PDU session with the WTRU (e.g., cause code provided to the WTRU). The WTRU may use the cause code to take appropriate action, e.g., re-establish the PDU session with different DNN/S-NSSAI combination(s). For example, the UDM/UDR may indicate to the SMF that the user is not permitted to access the DNN/S- NSSAI combination. This indication may trigger the SMF to initiate a PDU Session Release procedure. The PDU Session Release message that the SMF sends to the WTRU may include a cause code that indicates that the user is not permitted to access the DNN/S-NSSAI combination. Reception of the PDU Session Release message with the cause code may trigger the WTRU to display a message in a GUI indicating that access to a network (e.g., DNN/S-NSSAI combination) is not permitted.

[0120] Updating PDU Sessions may be triggered (e.g., using alternative triggers).

[0121] The Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session feature may be used to authenticate a user. As shown in FIG. 2, the WTRU may receive a message (e.g., a PDU Session Establishment or PDU Session Modification Command) that indicates that the user has been successfully authenticated. Receiving a message that indicates that the user has been successfully authenticated may trigger the WTRU to send a Registration Request to the network. The Registration Request may trigger the AMF to check what user identifier is authenticated to use the WTRU’s subscription. The AMF may trigger the actions at 10 as shown in FIG. 2, for example, if (e.g., when) the AMF receives an indication from the UDM/UDR that a user is authenticated and authorized to use the WTRU’s subscription. The action(s) at 10 in FIG. 2 may be associated with reconfiguring the WTRU’s other PDU Sessions to account for user specific settings such as user specific QoS parameters. The Registration Request message from the WTRU may have the effect of triggering the network to reconfigure the WTRU’s PDU Sessions to account for the user specific QoS Settings.

[0122] A human user of the WTRU may log out.

[0123] FIG. 3 illustrates an example of when the human user logs out of the WTRU, handling, and transfer of the information from the WTRU to various network functions. [0124] As shown at 1 in FIG. 3, an active PDU session may be ongoing with a DNN/S-NSSAI combination (e.g., special DNN/S-NSSAI combination), which may be configured for authenticating the users of the WTRU.

[0125] As shown at 2 in FIG. 3, the human user of a WTRU may trigger the WTRU to indicate to the network that the user may not be associated with the WTRU. For example, the human user of the WTRU may use a GUI to indicate that the human user is logging out. The indication may cause the WTRU to send a PDU Session Release request to the network for the PDU Session that is associated with user authentication. For example, the URSP Rule that includes a traffic descriptor that indicates user authentication may be used by the WTRU to select the correct PDU Session. The PDU Session Release request may include a “user log out” indication.

[0126] An inactivity by the human user of the WTRU may be detected by the network functions (e.g., SMF). An inactivity by the human user of the WTRU may result (e.g., lead) to the release of the PDU session with DNN/S-NSSAI combination (e.g., special DNN/S-NSSAI combination). The inactivity may be handled similarly to a human user logging out of the WTRU. For example, the human user may be using multiple PDU Sessions simultaneously. In that scenario, the AMF may be notified by an SMF about the inactivity detected for the PDU Session. The AMF may track whether the human is active or inactive across (e.g., all) the PDU Sessions for the user, for example, based on notifications from the serving SMF(s). The AMF may mark a PDU Session as inactive based on an SMF notification. The AMF may determine that the user is inactive, for example, if (e.g., when) the PDU sessions (e.g., all the PDU Sessions) are marked as inactive. Based on that determination, the AMF may trigger the release of the PDU Sessions for the user.

[0127] As shown at 3 in FIG. 3, the AMF may invoke a service operation (e.g., Nsmf_PDUSession_UpdateSMContext). The AMF may provide the indication about a human user of the WTRU logging out (e.g., “log-out”).

[0128] As shown at 4 in FIG. 3, the SMF may invoke a service operation (e.g., UDM Nudm_UIP_Modify service operation) to update the status of the user identifier as being logged out. The user may be considered to be implicitly logged out of the WTRU, and the SMF may be triggered to send a message to either release or modify the PDU session(s) (e.g., as shown at 5 in FIG. 3), for example, if the SMF determines to release the PDU Session (e.g., for any reason, e.g., based on a request from the AMF, PCF, or UPF). The AMF may request that a PDU Session be released or modified based on a change of WTRU location. The PCF may request that a PDU Session be released due to a change of WTRU policies.

[0129] As shown at 5 in FIG. 3, as the human user of the WTRU has logged out, the QoS parameters and other QoS settings for the ongoing PDU sessions may be impacted, for example, which may result in PDU sessions being modified or released. [0130] As shown in FIG. 2, the SMFs that serve the other PDU Sessions of the WTRU may be notified about the user’s status. FIG. 2 illustrates examples where the other SMFs may be notified that the user is associated with the WTRU. Similar (e.g., same) procedures may be used to notify the other SMFs that the user is no longer associated with the WTRU.

[0131] 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.

[0132] 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.

[0133] 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

CLAIMS What Is Claimed Is

1 . A first network entity, the first network entity comprising, a processor configured to: receive a first message that indicates that a user identity is associated with a wireless transmit/receive unit (WTRU); obtain user information associated with user access based on the user identity, wherein the user information is associated with a user profile, and wherein the user information comprises a list of identifiers that the user is allowed to access; send, to at least a second network entity, a second message comprising the user identity and an indication, wherein the indication indicates that the user identity is associated with a successful authentication and authorization status and associated with an identifier from the list.

2. The first network entity of claim 1 , wherein the first message is received from a third network entity, and wherein the first message further indicates a change in user identity profile status.

3. The first network entity of claim 2, wherein the change in user identity profile status indicates successful authentication and authorization associated with the user identity.

4. The first network entity of claim 2 or 3, wherein the third network entity is one of a session management function entity or a user data management entity.

5. The first network entity of any of claims 1 to 4, wherein the first message further indicates at least one of a user identifier, an authentication and authorization status, or user identity profile information.

6. The first network entity of any of claims 1 to 5, wherein the first network entity is an access management function entity, wherein the second network entity is a session management function entity, and wherein the session management function entity is associated with WTRU data traffic and the identifier from the list.

7. The first network entity of any of claims 1 to 6, wherein the second network entity is a first session management function, wherein the first session management function is associated with WTRU data traffic, and wherein the processor is further configured to: determine that a second session management function is associated with the WTRU data traffic; and send to the second session management function, based on the determination that the second session management function is associated with the WTRU data traffic, the user identity and a second indication, wherein the second indication indicates that the user identity is associated with a successful authentication and authorization status and associated with a second DNN/S-NSSAI combination from the list.

8. The first network entity of any of claims 1 to 7, wherein the list of identifiers is a list of DNN/S- NSSAI combinations that the user is allowed to access.

9. A method performed by a first network entity, the method comprising: receiving a first message that indicates that a user identity is associated with a wireless transmit/receive unit (WTRU); obtaining user information associated with user access based on the user identity, wherein the user information is associated with a user profile, and wherein the user information comprises a list of identifiers that the user is allowed to access; sending, to at least a second network entity, a second message comprising the user identity and an indication, wherein the indication indicates that the user identity is associated with a successful authentication and authorization status and associated with an identifier from the list.

10. The method of claim 9, wherein the first message is received from a third network entity, and wherein the first message further indicates a change in user identity profile status.

11 . The method of claim 10, wherein the change in user identity profile status indicates successful authentication and authorization associated with the user identity.

12. The method of claim 10 or 11 , wherein the third network entity is one of a session management function entity or a user data management entity.

13. The method of any of claims 10 to 12, wherein the first message further indicates at least one of a user identifier, an authentication and authorization status, or user identity profile information.

14. The method of any of claims 10 to 13, wherein the first network entity is an access management function entity, wherein the second network entity is a session management function entity, and wherein the session management function entity is associated with WTRU data traffic and the identifier from the list.

15. The method of any of claims 10 to 14, wherein the second network entity is a first session management function, wherein the first session management function is associated with WTRU data traffic, and wherein the method further comprises: determining that a second session management function is associated with the WTRU data traffic; and sending to the second session management function, based on the determination that the second session management function is associated with the WTRU data traffic, the user identity and a second indication, wherein the second indication indicates that the user identity is associated with a successful authentication and authorization status and associated with a second DNN/S-NSSAI combination from the list.

16. The method of any of claims 10 to 15, wherein the list of identifiers is a list of DNN/S-NSSAI combinations that the user is allowed to access.