[go: up one dir, main page]

WO2025208008A1 - Association d'un utilisateur humain à un abonnement - Google Patents

Association d'un utilisateur humain à un abonnement

Info

Publication number
WO2025208008A1
WO2025208008A1 PCT/US2025/021978 US2025021978W WO2025208008A1 WO 2025208008 A1 WO2025208008 A1 WO 2025208008A1 US 2025021978 W US2025021978 W US 2025021978W WO 2025208008 A1 WO2025208008 A1 WO 2025208008A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
wtru
network entity
user identity
management function
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2025/021978
Other languages
English (en)
Inventor
Anuj Sethi
Michael Starsinic
Debashish Purkayastha
Samir Ferdi
Saad Ahmad
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025208008A1 publication Critical patent/WO2025208008A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent

Definitions

  • a human user may be identified.
  • the human user may be associated with a wireless transmit/receive unit (WTRU).
  • WTRU wireless transmit/receive unit
  • 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.
  • 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.
  • the second message may indicate a list associated with user access.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • 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.
  • DC dual connectivity
  • 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).
  • 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.
  • QoS quality of service
  • 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.
  • 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).
  • 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.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • 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.
  • GPS global positioning system
  • 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.
  • 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.
  • 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.
  • the WTRU 102 may have multi-mode capabilities.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • location information e.g., longitude and latitude
  • 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.
  • 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.
  • 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.
  • FM frequency modulated
  • 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.
  • 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.
  • 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).
  • 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)).
  • 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)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • 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.
  • 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.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • 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.
  • 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.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • 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.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • 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).
  • 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.
  • 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.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in in 802.11 systems.
  • 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.
  • 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.
  • 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.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting 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).
  • MAC Medium Access Control
  • 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
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 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).
  • 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.
  • 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.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • 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).
  • TTIs subframe or transmission time intervals
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • 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.
  • 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.
  • 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.
  • 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.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • 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.
  • SMF Session Management Function
  • 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.
  • 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.
  • 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.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • 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.
  • radio technologies such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • 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.
  • 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.
  • the CN 115 may facilitate communications with other networks.
  • 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.
  • IMS IP multimedia subsystem
  • 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.
  • 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.
  • DN local Data Network
  • 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.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • WTRU wireless transmit/receive unit
  • 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.
  • 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.
  • a first network entity 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.
  • 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.
  • 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.
  • Access and mobility function (AMF) actions may be performed.
  • AMF actions may be performed based on successful authentication of a human user of the WTRU.
  • 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).
  • SMF session management function
  • DNN/S-NSSAI data network name/single network slice selection assistance information
  • An AMF may perform one or more of the following.
  • 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.
  • 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).
  • UDM NudmJJI P_Notification service operation e.g., the user identifier is successfully authenticated and authorized.
  • 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.
  • a message e.g., message transfer, e.g., the N1 N2MessageTransfer
  • a container e.g., the N1 SM container
  • PDU Session Establishment accept message e.g., the N1 SM container
  • 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).
  • the message to the SMF(s) 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).
  • SMF e.g., first SMF
  • WTRU Wireless Fidelity
  • 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.
  • 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.
  • a service operation e.g., UDM Nudm_UIP_Modify service operation
  • 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.
  • SMF e.g., second SMF actions may be performed, for example, at successful authentication of the human user of the WTRU.
  • An SMF may perform one or more of the following.
  • the SMF may receive a user identifier and/or an indication that the user was successfully authenticated and associated with the WTRU traffic.
  • 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.
  • 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.
  • 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.
  • User Identifiers may be used (e.g., in a 5G System)
  • the usage of user identifiers may be supported (e.g., in the 5G system).
  • 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.
  • Service level parameters, requirements, and/or definitions related to User Profiles and User Identity may be specified.
  • Secondary authentication may be performed, for example, by a third party.
  • 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).
  • A&A PDU Session Secondary authentication and authorization
  • NSSAA network slice-specific authentication and authorization
  • UAV uncrewed aerial vehicles
  • USS uncrewed aerial system service supplier
  • the system may not be aware of the identity of the user (e.g., human) who is using a WTRU to send and receive traffic.
  • the identity of the user may be provided to the network during PDU Session Establishment.
  • 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.
  • 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.
  • 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.
  • SMFs network functions
  • 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.
  • 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.
  • 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.
  • a User Identifier may include a Domain Identifier (e.g., component) and/or a Local Identifier (e.g., component).
  • a Domain Identifier e.g., component
  • a Local Identifier e.g., component
  • 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.
  • 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.
  • 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).
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • a PDU session modification e.g., to associate the existing session with the user identifier associated with the human user of the WTRU
  • the network e.g., if the PDU session with the same DNN/S-NSSAI combination already exists.
  • the AMF may invoke a service operation (e.g.,
  • 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.
  • 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).
  • 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).
  • 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.
  • the AMF e.g., via the N1 N2MessageTransfer
  • 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.
  • the actions shown at 8 in FIG. 2 may be an alternative to the actions shown at 7b 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).
  • 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.
  • the SMF(s) may query the UDM/UDR.
  • the SMF may obtain information from a user identity profile.
  • the QoS parameters corresponding to the user identifier e.g., Human user of the WTRU
  • 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).
  • 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).
  • 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.
  • 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.
  • Updating PDU Sessions may be triggered (e.g., using alternative triggers).
  • the Secondary authentication/authorization by a DN-AAA server during the establishment of a PDU Session feature may be used to authenticate a user.
  • 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.
  • 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.
  • a human user of the WTRU may log out.
  • 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.
  • 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.
  • DNN/S-NSSAI combination e.g., special DNN/S-NSSAI combination
  • 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.
  • 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.
  • 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.
  • 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.
  • the human user may be using multiple PDU Sessions simultaneously.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes et des procédés pour associer un utilisateur humain à un abonnement. Un utilisateur humain peut être identifié. L'utilisateur humain peut être associé à une unité d'émission et de réception sans fil (WTRU). L'utilisateur humain peut être associé au trafic de la WTRU. L'authentification et l'autorisation associées à l'utilisateur humain peuvent être déclenchées et/ou effectuées. L'utilisateur humain peut être authentifié et autorisé. Des entités de réseau (par exemple, une fonction de gestion d'accès, une fonction de gestion de session, etc.) peuvent être informées concernant l'association d'utilisateurs humains. Des sessions de trafic peuvent être ajustées sur la base d'informations de profil d'identité d'utilisateur. Les entités de réseau peuvent être informées si (par exemple, lorsque) l'utilisateur humain se connecte ou se déconnecte.
PCT/US2025/021978 2024-03-29 2025-03-28 Association d'un utilisateur humain à un abonnement Pending WO2025208008A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202463571527P 2024-03-29 2024-03-29
US63/571,527 2024-03-29

Publications (1)

Publication Number Publication Date
WO2025208008A1 true WO2025208008A1 (fr) 2025-10-02

Family

ID=95477452

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2025/021978 Pending WO2025208008A1 (fr) 2024-03-29 2025-03-28 Association d'un utilisateur humain à un abonnement

Country Status (1)

Country Link
WO (1) WO2025208008A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021069067A1 (fr) * 2019-10-09 2021-04-15 Lenovo (Singapore) Pte. Ltd. Accès à un réseau de communication mobile à l'aide d'un identifiant d'utilisateur
US20230139780A1 (en) * 2018-08-13 2023-05-04 Lenovo (Singapore) Pte. Ltd. Network slice authentication

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230139780A1 (en) * 2018-08-13 2023-05-04 Lenovo (Singapore) Pte. Ltd. Network slice authentication
WO2021069067A1 (fr) * 2019-10-09 2021-04-15 Lenovo (Singapore) Pte. Ltd. Accès à un réseau de communication mobile à l'aide d'un identifiant d'utilisateur

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on User Identities and Authentication Architecture (Release 19)", 8 March 2024 (2024-03-08), XP052615966, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG2_Arch/Latest_SA2_Specs/Latest_draft_S2_Specs/23700-32-020.zip> [retrieved on 20240308] *

Similar Documents

Publication Publication Date Title
US12302237B2 (en) Network slice reselection
US20220369363A1 (en) Authentication and authorization to access a network by an unmanned aerial vehicle
US12401993B2 (en) Security and privacy support for direct wireless communications
US20240340766A1 (en) Wtru-to-network relay associated with mint
EP4197169A1 (fr) Support de services de diffusion/multidiffusion pour relais de réseau
US20250184857A1 (en) Route selection in a wireless communication system
US20250168638A1 (en) Personal internet of things network connectivity
EP4501063A1 (fr) Authentification et autorisation secondaires de session pdu et spécifiques à une tranche au moyen d&#39;un relais wtru-à-réseau de l3
EP4413695A1 (fr) Contrôle d&#39;accès à un réseau de locaux d&#39;abonné
WO2025208008A1 (fr) Association d&#39;un utilisateur humain à un abonnement
WO2025207558A1 (fr) Activation d&#39;envoi de sms sur nas à utilisateur humain sur la base de l&#39;identité de l&#39;utilisateur
WO2025240798A1 (fr) Mécanismes de gestion de transitions d&#39;état d&#39;utilisateur
WO2025175210A1 (fr) Association d&#39;un utilisateur humain à un abonnement
WO2025213073A1 (fr) Procédés d&#39;activation et d&#39;authentification d&#39;identifiant d&#39;utilisateur
WO2025075956A1 (fr) Procédés et appareil pour gérer une communication indirecte par l&#39;intermédiaire de passerelles dans des réseaux personnels de l&#39;internet des objets (ido)
WO2025240851A1 (fr) Procédés pour activer des services de messages courts sur ip pour un utilisateur
WO2025155494A1 (fr) Procédés et mécanismes d&#39;application de qos dans réseau local
WO2024233918A1 (fr) Support pour pcc dynamique avec sa prose
WO2024238267A1 (fr) Autorisation d&#39;un consommateur lors de la résolution d&#39;une adresse ip
WO2025212849A1 (fr) Procédés et appareils de gestion d&#39;unité de données de protocole pour dispositifs aptes à une double orientation
WO2025212905A1 (fr) Identification d&#39;un profil d&#39;utilisateur et connexion à celui-ci
EP4544832A1 (fr) Contrôle d&#39;accès à un réseau d&#39;hébergement et gestion de congestion
WO2024233913A1 (fr) Authentification secondaire de services de proximité pendant l&#39;établissement/modification d&#39;une session pdu de relais
WO2024177919A1 (fr) Procédés d&#39;autorisation ue/ac/eec dans des services de groupe fournis par eas commun à l&#39;aide d&#39;un serveur de groupe
WO2023081364A1 (fr) Établissement, modification et révocation de communications c2 directes

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25720549

Country of ref document: EP

Kind code of ref document: A1