Methods for user identifier activation and authentication

Abstract

Disclosed herein are systems, methods, and instrumentalities associated with methods for user identifier activation and authentication. A wireless transmit / receive unit (WTRU) may include a processor. The WTRU may send a first request message. The first request message may include a request to a first network node to suspend usage of a first user identification (UID) or use a second UID. The WTRU may receive a first response message. The first response message may indicate that the first UID is suspended. The WTRU may send a second request message to the first network node. The second request message may include a request to use the first UID. The WTRU may receive a second response message from the first network node. The second response message may indicate a data connection resumption acceptance for the first UID. The WTRU may allow the sending of traffic over a plurality of resumed protocol data unit (PDU) sessions.

Description

METHODS FOR USER IDENTIFIER ACTIVATION AND AUTHENTICATIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The application claims the benefit of U.S. Patent Application Number 63 / 574,514, filed April 4, 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, for example, may be fourth generation (4G) long term evolution (LTE).SUMMARY

[0003] Disclosed herein are systems, methods, and instrumentalities associated with methods for user identifier activation and authentication. A wireless transmit / receive unit (WTRU) may include a processor. The WTRU may send a first request message. The first request message may include a request to a first network node to suspend usage of a first user identification (UID) or use a second UID. The WTRU may receive a first response message. The first response message may indicate that the first UID is suspended. The WTRU may send a second request message to the first network node. The second request message may include a request to use the first UID. The WTRU may receive a second response message from the first network node. The second response message may indicate a data connection resumption acceptance for the first UID. The WTRU may allow the sending of traffic over a plurality of resumed protocol data unit (PDU) sessions.

[0004] In examples, the first response message may include a plurality of suspended PDU sessions. The device may refrain from sending traffic over the plurality of suspended PDU sessions.

[0005] A first network node may include a processor. The first network node may determine a first user identification (UID) associated with a wireless transmit / receive unit (WTRU). The first network node may receive a first request message from the WTRU. The first request message may include a request to use a second UID from a second network node or suspend usage of the first UID. The first network node may send a first message to a second network node. The first message may indicate to suspend traffic forwarding on a plurality of protocol data unit (PDU) sessions for the first UID. The first message may include a suspension duration. The first network node may send a second message to a third network node. The second message may indicate that the first UID is suspended. The first network node mayreceive a second request message from the WTRU. The second request message may include a request by the WTRU to use the first UID. The first network node may determine that the first UID usage is suspended based on a UID state in a user profile. The first network node may send a third message to the second network node. The third message may indicate to resume traffic on the plurality of PDU sessions for the first UID. The first network node may send a fourth message to the third network node. The fourth message may indicate that usage of the first UID is resumed. The first network node may send a fifth message to the WTRU. The fifth message may indicate a data connection resumption acceptance for the first UID.

[0006] A first network node may include a processor. The first network node may receive a first request message from a second network node. The first request message may include a request to suspend traffic forwarding for a plurality of protocol data unit (PDU) sessions for a first user identification (UID), a plurality of PDU session identifications (I D(s)), and a suspension duration. The first network node may configure a third network node to not allow data traffic for the plurality of PDU sessions. The first network node may send a first response. The first response may confirm the suspension of the plurality of PDU sessions. The first network node may receive a first message from the second network node. The first message may indicate to resume traffic on the plurality of PDU sessions for the first UID providing the plurality of PDU session IDs. The first network node may configure the third network node to allow data traffic for the plurality of PDU sessions. The first network node may reset the suspension duration. The first network node may send a second response to the second network node. The second response may confirm the resumption of the plurality of PDU sessions or initiate a release of the plurality of PDU sessions if the suspension duration elapses.

[0007] A wireless transmit / receive unit (WTRU) may include a processor configured to send a first request message to a first network node, where the first request message may indicate a request to suspend usage of a first user identification (UID) or a request to use a second UID. Upon receiving a first response message from the first network node indicating that the first UID is suspended, the WTRU may send a second request message to the first network node, requesting usage of the first UID. The WTRU may receive a second response message from the first network node indicating a data connection resumption acceptance for the first UID and, based on this acceptance, may send a data message using a resumed protocol data unit (PDU) session. In examples, the first response message may identify multiple suspended PDU sessions associated with the first UID. If the WTRU determines that a second data message is intended for a suspended PDU session among the plurality, the WTRU may prevent that second data message from being sent until that PDU session is resumed. In examples, the WTRU may receive an authentication and authorization request from the first network node, where the authenticationand authorization request indicates that the WTRU may perform an authorization procedure based on the second DID.

[0008] A first network node may comprise a processor configured to receive a message from the WTRU requesting usage of a first UID. The first network node may determine that usage of the first UID is suspended according to a UID state associated with a user profile. The first network node may identify a second network node associated with the first UID. The first network node may send a message to the second network node requesting the resumption of traffic on a PDU session associated with the first UID. The first network node may send a message to the WTRU indicating data connection resumption acceptance for the first UID. That message may indicate the PDU session(s) associated with the first UID. In examples, the first network node may determine that the WTRU’s first UID and second UID may be tied to a subscription. The first network node may receive a message from the WTRU requesting suspension of the first UID (or requesting to use the second UID) and, in response, may send instructions to the second network node to suspend traffic forwarding on the relevant PDU session. In example, the first network node may notify the third network node that the first UID is suspended.

[0009] A first network node may be configured to receive a message from a second network node requesting the resumption of traffic on a PDU session associated with the first UID. This first network node may determine a suspension duration for the PDU session and then send a message to a third network node requesting that data traffic for the PDU session be resumed. The first network node may send a message to the second network node to indicate whether the PDU session has been resumed or whether the PDU session may be released if the suspension duration has elapsed. The first network node may receive messages from the second network node requesting that traffic forwarding be suspended for the PDU session, along with the applicable suspension duration, and may forward a suspension request to the third network node. The first network node may further send a message to the WTRU indicating that the PDU session has been suspended.BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

[0014] FIG. 2 is a flow diagram illustrating UID (re)activation during a Registration Procedure (authentication outside Registration).

[0015] FIG. 3 is a flow diagram illustrating UID (re)activation during a Registration Procedure (authentication inside Registration).

[0016] FIG. 4 is a flow diagram illustrating an example of a procedure for user (re)activation where SMF may act as an authenticator toward an AAA server.

[0017] FIG. 5 is a flow diagram illustrating the suspension of the UID during a Registration Procedure (authentication inside registration).

[0018] FIG. 6 is a flow diagram illustrating the resumption of the UID during a Registration Procedure (e.g., authentication inside registration).

[0019] FIG. 7 is a flow diagram illustrating the UID activity states, which may illustrate the activation state model.DETAILED DESCRIPTION

[0020] FIG. 1 A 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.

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

[0022] 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, a Home Node B, a Home eNode B, a 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.

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

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

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

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

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

[0028] 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., a eNB and a gNB).

[0029] 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 forMobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0058] 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, and802.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).

[0059] WLAN systems, which may support multiple channels, and channel bandwidths, such as802.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.

[0060] 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 for802.11 ah is 6 MHz to 26 MHz depending on the country code.

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

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

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

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

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

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

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

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

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

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

[0071] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-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.

[0072] 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, the one or more emulation devices may perform the 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 in order 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 perform testing using over-the-air wireless communications.

[0073] 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 in order 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.

[0074] Reference to a timer herein may refer to a time, a time period, a tracking of time, a tracking of a period of time, a combination thereof, and / or the like. Reference to a timer expiration herein may refer to determining that the time has occurred or that the period of time has expired.

[0075] A wireless transmit / receive unit (WTRU) may include a processor configured to send a first request message to a first network node, where the first request message may indicate a request to suspend usage of a first user identification (III D) or a request to use a second III D. Upon receiving a first response message from the first network node indicating that the first UID is suspended, the WTRU may send a second request message to the first network node, requesting usage of the first UID. The WTRU may receive a second response message from the first network node indicating a data connection resumption acceptance for the first UID and, based on this acceptance, may send a data message using a resumed protocol data unit (PDU) session. In examples, the first response message may identify multiple suspended PDU sessions associated with the first UID. If the WTRU determines that a second data message is intended for a suspended PDU session among the plurality, the WTRU may prevent that second data message from being sent until that PDU session is resumed. In examples, the WTRU may receive an authentication and authorization request from the first network node, where the authentication and authorization request indicates that the WTRU may perform an authorization procedure based on the second UID.

[0076] A first network node may comprise a processor configured to receive a message from the WTRU requesting usage of a first UID. The first network node may determine that usage of the first UID is suspended according to a UID state associated with a user profile. The first network node may identify a second network node associated with the first UID. The first network node may send a message to the second network node requesting the resumption of traffic on a PDU session associated with the first UID. The first network node may send a message to the WTRU indicating data connection resumption acceptance for the first UID. That message may indicate the PDU session(s) associated with the first UID. In examples, the first network node may determine that the WTRU’s first UID and second UID may be tied to a subscription. The first network node may receive a message from the WTRU requesting suspension of the first UID (or requesting to use the second UID) and, in response, may send instructions to the second network node to suspend traffic forwarding on the relevant PDU session. In example, the first network node may notify the third network node that the first UID is suspended.

[0077] A first network node may be configured to receive a message from a second network node requesting the resumption of traffic on a PDU session associated with the first UID. This first network node may determine a suspension duration for the PDU session and then send a message to a third network node requesting that data traffic for the PDU session be resumed. The first network node may send a message to the second network node to indicate whether the PDU session has been resumed or whether the PDU session may be released if the suspension duration has elapsed. The first network node may receive messages from the second network node requesting that traffic forwarding be suspended for thePDU session, along with the applicable suspension duration, and may forward a suspension request to the third network node. The first network node may further send a message to the WTRU indicating that the PDU session has been suspended.

[0078] User identification (ID) activation with fast re-authorization may be provided. An authenticator may perform an authentication and / or authorization procedure with a wireless transmit / receive unit (WTRU) requesting to use a user ID (UID). The authenticator may perform a fast re-authorization of the UID following a subsequent request from the WTRU to use the UID (e.g., following a swap of UIDs on the WTRU, or suspension of the UID).

[0079] An authenticator with access and mobility function (AMF) or session management function (SMF) behavior may be provided. The authenticator may initiate authentication and authorization of a UID (e.g., during registration, protocol data unit (PDU) session). The authenticator may receive authentication and authorization validity scope information (e.g., access type, time, time of day, location, public land mobile networks (PLMNs), etc.) from an authentication server (e.g., authentication server function (AUSF) or authentication, authorization, and accounting (AAA) server). The authenticator may store authorization information in a user profile (e.g., user data management (UDM) or user data repository (UDR)) of a UID. The authenticator may send authorization validity scope information to the WTRU. The authenticator may receive a request by the WTRU to use the UID (e.g., after the WTRU switched usage to an alternate UID or to use the UID over a different access network). The authenticator may check whether there is a valid authentication and authorization result in the user profile (UDM / UDR) for the UID before triggering the authentication procedure. The authenticator may authorize the WTRU to use the UID without authentication based on the condition of finding a valid authentication and authorization result in the user profile (e.g., in UDM / UDR) and based on determining that the validity scope information is valid (e.g., authentication validity timer not expired). The authenticator may refresh authentication and authorization result information (e.g., in the UDM / UDR) for a UID when an authentication validity timer expires or upon request from the authentication server.

[0080] WTRU behavior may be provided. The WTRU may receive a configuration of authorization for UID usage from a policy control function (PCF) or an application function (AF). The configuration may indicate per UID a validity scope, such as the context of where or when the WTRU is authorized to use a particular UID (e.g., geographical location area(s), list of authorized PLMNs or indication of whether roaming is allowed, access type, etc.). The WTRU may send a first request to use a UID conditional on authorization configuration. The WTRU may receive authorization data, including validity scope information associated with the UID following a successful authentication and authorization of the UID, overriding any existing authorization configuration (validity scope) associated with the UID. The WTRU may send asecond request to use the Ul D (e.g., after WTRU switches usage to another III D or over a different access network) conditional on authorization configuration. The WTRU may receive authorization to use the UID without performing an authentication and authorization procedure of the UID.

[0081] UID usage suspension and resumption may be provided. The AMF may initiate the suspension and resumption of traffic for the PDU sessions used by a UID upon a request by the WTRU to suspend the UID or to use another UID when a UID may be currently active in the WTRU or the network (e.g., following authentication and authorization as described above).

[0082] AMF behavior may be provided. The AMF may receive a request from the WTRU to use another UID and / or to suspend usage of the UID. The AMF may proceed with authentication and authorization for the other (e.g., alternate) UID. The AMF may mark the UID as suspended in the user profile of the UID profile. The AMF may send a message to the SMF(s) serving the UID to suspend traffic forwarding on the PDU sessions for the UID. The message may include a suspension timer. The AMF may send a message to the application function (AF) or authentication, authorization, and accounting (AAA) server indicating that usage of the UID is suspended. The AMF may send a response to the WTRU including an indication of suspension of the UID. The indication may include the list of IDs of the suspended PDU sessions. The AMF may receive a request by the WTRU to use or resume usage of the UID (e.g., after suspension, the WTRU may switch usage to another UID, which may be an alternate UID). The AMF may determine that the UID usage is suspended based on a UID state in the user profile. The AMF may send a message to the SMF(s) serving the UID to resume traffic on the PDU sessions for the UID. The AMF may send a message to the AF / AAA server indicating that usage of the UID is resumed. The AMF may send a response to the WTRU including an indication of data connection resumption acceptance for the UID. The indication may include the list of IDs for the resumed PDU sessions. The WTRU may resume sending traffic over the resumed PDU sessions.

[0083] WTRU behavior may be provided. The WTRU may send a request to an AMF to use another UID (e.g., an alternate UID) and / or to suspend usage of the UID. The WTRU may receive a response that includes an indication of suspension of the UID. The indication may include the list of IDs of the suspended PDU sessions. The WTRU may refrain from sending traffic over PDU sessions marked as suspended. The WTRU may send a request to an AMF to use or resume usage of the UID. The WTRU may receive a response including an indication of data connection resumption acceptance for the UID. The indication may include the list of IDs for the resumed PDU sessions. The WTRU may allow the sending of traffic over the resumed PDU sessions.

[0084] SMF behavior may be provided. The SMF may receive a request message from an AMF to suspend traffic forwarding for one or more PDU sessions for the UID, providing the PDU session I D(s) anda suspension timer. The SMF may configure the user plane function (UPF) or radio access network (RAN) to not allow data traffic for the PDU session(s), including canceling or updating any user plane inactivity timer running in the UPF. The SMF may start the suspension timer and send a response confirming the suspension of the PDU session. The SMF may receive a message from AMF to resume traffic on the PDU sessions for the UID providing the PDU session ID. The SMF may configure UPF / RAN to allow data traffic for the PDU session(s), including provisioning or updating a user plane inactivity timer in the UPF. The SMF may clear the suspension timer and send a response to the AMF confirming the resumption of the PDU session(s) or initiating the release of the PDU session(s) if the suspension timer expires (e.g., before it may be resumed by the AMF).

[0085] UIDs authentication architecture in a system, such as the fifth generation (5G) System (5GS), may be provided. Examples provided herein may provide enhancements to support the usage of UIDs in a system, such as the 5G system. In examples, such enhancements may allow operators to utilize userspecific identities to provide a service delivery tailored based on the user identity. In an example, a user identity may be that of a human using a WTRU, an application running on the WTRU, or a device behind a WTRU gateway.

[0086] Service level parameters (e.g., requirements) related to user profiles and user identity may be provided. Architecture assumptions may provide that a (e.g., only one) UID may be active at a time for a given subscription and that the UID may be linked to the subscription under operator control (e.g., via API) prior to access. UID state changes, such as explicit UID state changes, may be enabled and / or triggered by an AMF or SMF to notify the network exposure function (NEF), without specifying or describing other possible actions (e.g., release of resources or authentication) needed for UID swapping. The release of resources used by a first user upon the network receiving a request to use a second UID may be initiated. A request to use a PDU session for a second UID may be rejected if the PDU session is already used by a first user.

[0087] Secondary authentication procedures may be provided. A secondary authentication procedure may be where a WTRU may be authenticated by a third-party authentication server via intermediate functions in a core network, such as the 5GC (e.g., SMF, AMF, NEF). These procedures may be referred to as PDU session secondary authentication and authorization (A&A) and / or network slice-specific authentication and authorization (NSSAA). The WTRU may use a user identity and credentials during an authentication and authorization (A&A) procedure before being granted access to the network resources (e.g., PDU session, network slice, data network (DN), etc.).

[0088] UID switching capability may be provided. In examples, rejecting a WTRU request to change UIDs may not be preferred where alternating or changing of a UID occurs frequently (e.g., a human userswitching between a personal and professional user profile on the WTRU and / or multiple human users actively sharing a WTRU). When alternating or changing of UID may occur frequently, access to data connectivity may be denied or unnecessarily delayed for usage of another (e.g., alternate) UID while being locked to the UID currently active. Allowing the WTRU to switch (e.g., efficiently, seamlessly) active UID (implicitly or explicitly) may be preferable for the user experience.

[0089] Authentication and authorization signaling overhead for UID activation may be repetitive, for example. Mechanisms for UID activation (e.g., during registration or PDU session establishment) may request (e.g., require) a systematic authentication run between the WTRU and the network / third party. As this activation may be triggered while changing or alternating between UIDs on the WTRU, reactivating a UID may trigger redundant authentication run(s). In examples, if the WTRU requests usage of the same UID, the WTRU may trigger another authentication run. In these examples, the repetitive and redundant authentication runs may be prevented in order to avoid unnecessary signaling overhead and (e.g., excessive) delay for the end user to access (back) the service.

[0090] Session management signaling overhead for UID activation may incur delay for the end user. Mechanisms may propose to release the network resources (PDU session) for the UID being swapped out for another UID. Switching between UIDs may request (e.g., require) reestablishment of PDU sessions before the WTRU may resume data communication. In examples, the frequent release and reestablishment of PDU sessions may be prevented to avoid unnecessary signaling overhead and delay for the end user to access (back) the service for the UID that was initially swapped out.

[0091] Examples may enable activation of a UID in a matter to allow fast and efficient network and data connection access while switching usage of UIDs and / or connecting via one or more access networks for that UID.

[0092] Examples described herein may utilize a system, such as 5GS or 6GS, to enable a fast reauthorization without re-authentication of a UID and data connection resumption of a UID linked.

[0093] In examples, a human user may be allowed to activate usage of a UID while swapping user profiles (e.g., personal vs. business) or connecting via a different and / or additional access network (e.g., WiFi), with quicker resumption of data connectivity than when activating the UID the first time.

[0094] In examples, the operator may be allowed to minimize signaling overhead that may be caused by authentication and session management signaling when a UID is being temporarily deactivated (e.g., suspended) and then reactivated or while accessing via a different and / or an (e.g., only) additional access network (e.g., WiFi).

[0095] Ul D activation with fast re-authorization may be provided. FIG. 2 and FIG. 3 illustrate an example procedure for User (re)activation where an AMF acts as an authenticator toward an AAA server where the UID authentication takes place, respectively, outside and inside the registration procedure.

[0096] FIG. 2 illustrates UID (re)activation during a registration procedure (authentication outside registration).

[0097] At 0, the UID may be linked to a WTRU subscription in the UDM / UDR. The WTRU may be configured with an authorization configuration for UID usage (e.g., by a PCF, AF). The configuration indicates per UID the context where / when the WTRU may be authorized to use a particular UID (e.g., list of authorized PLMNs or indication of whether roaming is allowed, authorized radio access type, authorization validity information (time and location), etc.).

[0098] At 1 , the WTRU may send a registration request message, including the UID to be activated. The WTRU may check the configuration to verify if the WTRU is allowed to use the UID. For example, if usage of the UID may not be allowed while roaming or accessing a particular PLMN or a particular access network type, the WTRU may refrain from activating the UID.

[0099] At 2, the AMF may retrieve the subscription data linked to the UID from UDM / UDR to check whether the WTRU may be authorized to use the UID. The AMF may determine whether to initiate UID authentication and authorization based on authorization data retrieved from UDM / UDR. A valid authorization may be available from a previous activation (e.g., the UID was swapped out by the WTRU to use another UID (e.g., an alternate UID) or if the WTRU is requesting to use the UID via an additional access network).

[0100] At 3, if no valid authorization may be found, the AMF sends a registration accept with an indication that authentication and authorization of UID may be pending, and the AMF may skip initiation at 4. If a valid authorization is found, the authorization result information may be included in the message. The WTRU may refrain from requesting a network service (e.g., PDU session, SMS, etc.) regardless of the access network, while the UID authentication and authorization may be pending at 4.

[0101] At 4, the AMF may initiate the authentication and authorization of UID with AAA-server (AAA-S) via a UID authentication function (UIAAF). UIAAF may be collocated with a network slice authentication and authorization function (NSAAF). Multiple messages (e.g., extensible authentication protocol (EAP)) may be exchanged between the WTRU and AAA via AMF / UIAAF. The AMF may receive from the AAA an A&A result that may include a UID authorization data including validity scope information (e.g., access type, time, time of day, location, PLMNs, etc.).

[0102] At 5, the AMF may update UDM / UDR with authorization data and may indicate an active state for the UID.

[0103] At 6, the AMF may update the WTRU in a WTRU configuration update (UCU) procedure, providing the UID authorization data and an indication of successful activation of the DID. The WTRU may override existing authorization data associated with the UID (e.g., at 6 or at 3 if authorization without authentication was performed). The WTRU may request to use a network service (e.g., PDU session, SMS over NAS) based on the UID authorization data.

[0104] FIG. 3 illustrates UID (re)activation during a registration procedure (authentication inside Registration). The procedure in FIG. 3 may be similar to the procedure described in FIG. 2 with several differences. For example, at 2, the AMF may initiate the authentication and authorization at 3 before sending the result in the registration accept message. The AMF may not need to update the WTRU with a UCU procedure as the authentication and authorization result may be provided directly at 5 as part of the registration procedure.

[0105] FIG. 4 illustrates an example of a procedure for user (re)activation where SMF may act as an authenticator towards an AAA server. FIG. 4 illustrates the UID (re)activation during a PDU session establishment procedure.

[0106] At 0, the UID may be linked to a WTRU subscription in the UDM / UDR. The WTRU may be configured with an authorization configuration for UID usage (e.g., by a PCF, AF). The configuration may indicate per UID the context where / when the WTRU is authorized to use a particular UID (e.g., S-NSSAI, DNN, via a WTRU to Network relay, location, time of day, etc.). For example, a UID may be allowed to use S-NSSAIs or DNNs that are a subset of the S-NSSAIs or DNNs in a WTRU subscription.

[0107] At 1 , the WTRU may send a PDU session establishment request message, including the UID to be activated. The WTRU may check the configuration to verify if the WTRU is allowed to use the UID. For example, if usage of the UID is not allowed for a given S-NSSAI or DNN, the WTRU may refrain from activating the UID.

[0108] At 2, the SMF may retrieve the subscription data linked to the UID from UDM / UDR to check whether the WTRU may be authorized to use the UID. The SMF may determine whether to initiate UID authentication and authorization based on authorization data retrieved from UDM / UDR. A valid authorization may be available from a previous activation (e.g., the UID was successfully authorized to use another PDU session).

[0109] At 3, if no valid authorization may be found, the SMF may initiate the A&A of the UID with the AAA via a UPF or NEF. Multiple messages (e.g., EAP) are exchanged between the WTRU and AAA via SMF. The SMF may receive from the AAA an A&A result that may include authorization data, including validity scope information (e.g., location, time, time of day, etc.). If a valid authorization may be found, the A&A of the UID at 3 and the update of the UDM / UDR at 4 may be skipped.

[0110] At 4, the SMF may update the UDM / UDR with authorization data and indicate an active state for the UID.

[0111] At 5, the SMF may send a PDU session establishment accept message to the WTRU providing authorization data (described above). The WTRU may start exchanging traffic over the PDU session according to the authorization data.

[0112] UID usage may be suspended and resumed. FIG. 5 and FIG. 6 illustrate examples of procedures respectively for user suspension and resumption, performed during a registration procedure. Traffic over the PDU sessions for the UID may be suspended implicitly when the WTRU may request usage of an alternate UID while the UID is active. The UID may also be suspended when the WTRU sends an explicit request to suspend the UID (e.g., to fall back to the default subscription settings, without a particular UID active). Traffic over the PDU sessions for the UID, (e.g., the suspended UID), may be allowed to resume when the WTRU may send a subsequent request to resume usage of the UID. UID activity state model (active, suspended, inactive, etc.) details may be provided. In examples, using a different procedure (e.g., service request, PDU Session modification) procedure or messages, may be provided, including activation / suspension of an included list of PDU sessions in the messages.

[0113] FIG. 5 illustrates the suspension of the UID during a registration procedure (authentication inside registration).

[0114] At 0, UID1 and UID2 may be linked to the WTRU subscription. UID1 may be active (e.g., as shown in FIG. 2-4). UID2 may be inactive.

[0115] At 1 , the WTRU may send a registration request message including UID2 to be activated (e.g., instead of UID1). The WTRU may send a registration request message including an explicit indication to suspend UID1 or no indication and no UID to suspend UID (for example, to use the default subscription settings, not linked to a particular UID).

[0116] At 2, the AMF may retrieve the authorization data from UDM / UDR (e.g., user profile) and may check whether UID2 is authorized (e.g., linked with the WTRU subscription). AMF may determine that UID1 is active and UID2 is inactive based on data retrieved from UDM / UDR and / or UID activity information stored in the WTRU context. AMF may initiate a switch of active user as follows.

[0117] At 3, the AMF may initiate the UID authentication and authorization for UID2. If a valid authorization for UID2 was retrieved at 2, the initiation of the UID A&A for UID2 at 3 may be skipped.

[0118] At 4, the AMF may send a request to the one or more SMF serving PDU session(s) for UID1 providing the SMF context ID, UID1 , and an indication that the PDU session(s) may be suspended, including a suspension timer. For a PDU session (e.g., each PDU session), an SMF (e.g., each SMF) mayconfigure the UPF to not allow traffic for the PDU session, including canceling or updating any user plane inactivity timer running in the UPF. The SMF may start the suspension timer for the UID PDU session(s).

[0119] At 5, the AMF may send a message to the AAA to provide the UID1 and an indication that UID1 may be suspended. For example, a third-party AAA or AF may subscribe to be notified of user activity status via NEF, which may be triggered whenever the UID status may be updated in the UDM / UDR (e.g., at 6). The AMF may include in the same or separate message an indication that UID2 is active.

[0120] At 6, the AMF may send a message to the UDM / UDR providing the UID1 and an indication that UID1 may be suspended. The AMF may include, in the same or separate message, an indication that UID2 is active. If UID2 was requested at 1 , the A&A for the UID may be provided. If UID2 authorization fails at 2 or 3, the AMF may send a registration reject to the WTRU. Two options are available regarding UID1 activity status if UID2 authorization fails. If the AMF decides to retain UID1 as active or suspend UID1 , then AMF may skip or proceed with 4-6, respectively. The decision to suspend or retain UID1 as active if UID2 authorization fails may be based on operator policy. If suspended, the WTRU may resume UID1 usage as illustrated below.

[0121] FIG. 6 illustrates the resumption of the UID during a registration procedure (e.g., authentication inside registration).

[0122] At 0, UID1 and UID2 may be linked to the WTRU subscription. UID1 may be suspended, and UID2 may be active (e.g., FIG. 5).

[0123] At 1 , the WTRU may send a registration request message including UID1 to resume usage of UID1.

[0124] At 2, the AMF may retrieve the authorization data from UDM / UDR. The AMF may determine that UID1 is suspended and UID2 is active based on data retrieved from UDM / UDR and / or UID activity information stored in the WTRU context. The AMF may initiate a switch of active user as follows.

[0125] At 3, the AMF may send a request to the one or more SMF serving PDU session(s) for UID2, providing the SMF context ID, UID2, and an indication that the PDU session(s) may be suspended as described above.

[0126] At 4, the AMF may send a message to the AAA to provide the UID2 and an indication that UID2 may be suspended. The AMF may send a message to the UDM / UDR providing the UID2 and an indication that UID2 may be suspended. The AMF may send a request to the one or more SMF serving PDU session(s) for UID1 providing the SMF context ID, UID1 , and an indication that the PDU session(s) may be activated. For a PDU session (e.g., each PDU session), an SMF (e.g., each SMF) may configure the UPF to request traffic to be allowed for the PDU session which may include provisioning or updating a userplane inactivity timer in the UPF. The SMF also may clear the suspension timer. The SMF may initiate the release of the PDU session(s) if the suspension timer expires (before it is resumed by AMF).

[0127] The AMF may send a message to the AAA providing the UID1 and an indication that UID1 may be active.

[0128] The AMF may send a message to the UDM / UDR providing the UID1 and an indication that UID1 may be active.

[0129] Service request procedure based suspension and resumption of the UID may be provided. WTRU initiated service request procedure may be defined to suspend and resume UID. The WTRU may trigger a service request procedure to suspend the active UID. The service request message may include a second UID (e.g., an alternate UID), which the WTRU may activate. During this procedure, traffic over the PDU sessions for a UID may be suspended when the WTRU may request usage of an alternate second UID in the service request message.

[0130] The WTRU may include an indication of the selective activation of PDU sessions for the UID to be activated in the service request message. The WTRU may include an indication of the selective suspension of PDU sessions for the UID to be suspended. The list of PDU sessions (e.g., respectively, to be activated or suspended) may comprise all or a subset of the PDU sessions of the UID. The list of PDU sessions to be activated (e.g., respectively suspended) may belong to the associated UID to be activated (e.g., respectively suspended). The AMF may verify that a list (e.g., each list) of PDU session (e.g., respectively to be activated or suspended) may belong to the associated UID (e.g., respectively to be activated or suspended). For example, the AMF may reject the request if the list of PDU session to be activated (e.g., respectively suspended) may include the PDU session ID associated with a different UID than the UID to be activated (e.g., respectively suspended).

[0131] The network (e.g., the AMF) may send the service accept message to indicate to the WTRU that the alternate UID has been activated and the UID has been suspended. The information about the activated (e.g., respectively suspended) PDU sessions may be sent to the WTRU in the service accept message. At 2-5, as described in FIG. 6, execution may also occur on the network side after the network receives the service request message from the WTRU. If the list of PDU sessions to be suspended (respectively activated) in the service request message may be a subset of the PDU sessions of the UID to be suspended (respectively activated), the AMF may request that one or more SMF serving PDU session(s) for the UID to release the remaining PDU sessions of the UID to be suspended (respectively activated).

[0132] In an example, the WTRU may use other types of NAS control plane signaling messages instead of the registration or service request messages for UID activation / suspension (e.g., UL NAS transportmessage with a container containing information about activating / suspending a UID and associated PDU sessions, a PDU Session Modification message indicating a activation or suspension of the UID and the associated PDU Session).

[0133] UID activation management states may be provided. The following UID activation states may be used in the WTRU and the network (e.g., AMF, UDM / User Profile).

[0134] The UID inactive state may be provided. The WTRU and network may set the UID in an inactive state when the UID is not authenticated or authorized. The UID inactive state may be provided when the WTRU is not allowed to access or use network resources for that UID. The UID inactive state may be provided when the WTRU has no PDU sessions established for that UID.

[0135] The UID active state may be provided. The WTRU and network may set the UID in an active state when the UID is authenticated and authorized. The UID active state may be provided when the WTRU is allowed to access and use network resources for that UID. The UID active state may be provided when the WTRU may have PDU sessions established and active for that UID.

[0136] The UID suspended state may be provided. The UID suspended state may be provided when the UID is authenticated and authorized. The UID suspended state may be provided when the WTRU is not allowed to access and use network resources for that UID. The UID suspended state may be provided when the WTRU may have PDU sessions established and suspended for that UID.

[0137] FIG. 7 illustrates the UID activity states, which may illustrate the activation state model. FIG. 7 illustrates the UID activity states. In the inactive state, the WTRU and network may transition the UID state into the active state following a successful A&A procedure for the UID when requested by the WTRU. The activation event may correspond to the WTRU receiving one or more of the following messages: registration or service accept, PDU session establishment / modification accept, WTRU configuration update wherein the network (e.g., AMF or SMF) indicates successful activation of the UID and the like.

[0138] In the inactive state, the UID may remain in the inactive state if the authentication fails for the UID when requested by the WTRU. The activation reject event may correspond to the WTRU receiving a message (e.g., registration or service reject, PDU session establishment / modification reject wherein the network indicates unsuccessful activation of the UID).

[0139] In the active state, the WTRU and network may transition the UID state into the inactive state following an unsuccessful re-authentication and authorization procedure for the UID, a WTRU deregistration procedure, or revocation of UID authorization. The deactivation event may correspond to the WTRU receiving a message (e.g., NAS transport with re-authentication failure indication, PDU session release command, WTRU configuration update, or deregistration message, etc.) wherein the network (e.g., AMF or SMF) indicates deactivation of the UID.

[0140] In the active state, the Ul D may remain in the active state if a re-authentication triggered by the network (AMF or SMF) or an authentication server (e.g., AUSF or AAA server) may be successful. The activation update event may correspond to the WTRU receiving a message (e.g., PDU session modification accept, WTRU configuration update, etc.) wherein the network (e.g., AMF or SMF) may indicate a successful activation update of the UID.

[0141] In the active state, the WTRU and network may transition the UID state into the suspended state implicitly following a successful re-authentication and authorization procedure for a different UID or explicitly upon an explicit WTRU request to suspend usage of the UID. The suspend event may correspond to the WTRU receiving a message (e.g., Registration or Service Accept, PDU session establishment / modification accept, WTRU configuration update, etc.) wherein the network (AMF or SMF) may indicate successful activation for a different UID or the WTRU sending a request (e.g., registration, PDU session modification, etc.) to explicitly suspend usage of the UID.

[0142] In the suspended state, the WTRU and network may transition the UID state into the inactive state following an unsuccessful re-authentication and authorization procedure for the UID, a WTRU deregistration procedure, or revocation of UID authorization. The deactivation event may correspond to the WTRU receiving a message (e.g., PDU session release command, WTRU configuration update, deregistration message, etc.) wherein the network (AMF or SMF) indicates the deactivation of the UID.

[0143] In the suspended state, the WTRU and network may transition the UID state into the active state when requested by the WTRU. The resume event may correspond to the WTRU receiving a message (e.g., registration or service accept, PDU session establishment / modification accept, WTRU configuration update, etc.) wherein the network (AMF or SMF) indicates successful resumption of usage of the UID.

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

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

[0146] 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:1 . A wireless transmit / receive unit (WTRU) comprising: a processor, the processor configured to: send a first request message to a first network node, wherein the first request message indicates at least one of a request to suspend usage of a first user identification (UID), or a request to use a second UID; receive a first response message, wherein the first response message indicates that the first UID is suspended; send a second request message to the first network node, wherein the second request message indicates a request to use the first UID; receive a second response message from the first network node, wherein the second response message indicates a data connection resumption acceptance for the first UID; and send a data message using a resumed protocol data unit (PDU) session based on the data connection resumption acceptance for the first UID.

2. The WTRU of claim 1 , wherein the first response message indicates a plurality of suspended PDU sessions, wherein the suspended PDU sessions are associated with the first UID, and wherein the first UID and the second UID are associated with a subscription.

3. The WTRU of any one of claims 2 to 3, wherein the data message is a first data message, and wherein the processor is further configured to: determine a second data message is associated with a suspended PDU session from the plurality of the suspended PDU sessions; and prevent the second data message from being sent using the suspended PDU session.

4. The WTRU of any one of claims 2 to 4, wherein the processor is further configured to: receive an authorization request message from the first network node, wherein the authorization request message indicates a request for the WTRU to perform an authorization procedure based on the second UID.

5. A first network node, the first network node comprising: a processor, the processor configured to: receive a first message from a wireless transmit / receive unit (WTRU), wherein the first message indicates a request to use the first user identification (Ul D); determine that the first UID usage is suspended based on a UID state, wherein the UID state is associated with a user profile; determine a second network node associated with the first UID; send a second message to the second network node, wherein the second message indicates a request to resume traffic on a protocol data unit (PDU) session associated with the first UID; send a third message to the third network node, wherein the third message indicates that usage of the first UID is resumed; and send a fourth message to the WTRU, wherein the fourth message indicates a data connection resumption acceptance for the first UID.

6. The first network node of claim 5, wherein the fourth message further indicates the PDU session associated with the first UID.

7. The first network node of any one of claims 5 to 6, wherein the processor is further configured to determine a first UID associated with the WTRU, wherein the first UID is associated with a subscription, and wherein the second UID is associated with the subscription.

9. The first network node of any one of claims 5 to 7, wherein the processor is further configured to: receive a fifth message from the WTRU wherein the fifth message indicates at least one of a request to suspend usage of the first UID, or a request to use a second UID; and send a sixth message to the second network node, wherein the second message indicates a request to suspend traffic forwarding on the PDU session associated with the first UID.

10. The first network node of any one of claims 5 to 9, wherein the processor is further configured to send a seventh message to a third network node, wherein the second message indicates that the first UID is suspended.

11. A first network node, the first network node comprising: a processor, the processor configured to: receive a first message from a second network node, wherein the first message indicates a request to resume traffic on a protocol data unit (PDU) session associated with the first user identification (UID); determine a suspension duration associated with the PDU session; send a second message to a third network node, wherein the second message indicates a request for the third network node to resume data traffic for the PDU session; and send a third message to the second network node, wherein the third message indicates at least one of a resumption of the PDU session or a request to release the PDU session if the suspension duration has elapsed.

12. The first network node of claim 11 , wherein the processor is further configured to receive a fifth message from the second network node, wherein the fifth message indicates a request to suspend traffic forwarding for the PDU session and the suspension duration.

13. The first network node of any one of claims 11 to 12, wherein the processor is further configured to send a sixth message to the third network node, wherein the sixth message indicates a request for the third network node to suspend data traffic associated with the PDU session.

14. The first network node of any one of claims 11 to 13, wherein the processor is further configured to send a seventh message to the WTRU, wherein the seventh message indicates that the PDU session has been suspended.

Images