WO2025212921A1 - Methods, architectures, apparatuses and systems for role authorization in a wireless network environment - Google Patents

Abstract

Procedures, methods, apparatuses, systems, and computer program products are provided for handling a role authorization request from a wireless transmit/receive unit (WTRU) roaming in a visited network. The role involves security or privacy considerations. In an example, a first policy control function (PCF) in the WTRU's home network handles the request by obtaining a visited network privacy policy from a second PCF in the visited network and combining the home network privacy policy with the visited network privacy policy to generate a combined network privacy policy. The first PCF then determines whether to authorize the role authorization request by applying the combined network privacy policy to the request. The role is assigned to the WTRU by a key management function in the home network which provides any cryptographic keys required to provide security or privacy for the role to the WTRU.

Description

METHODS, ARCHITECTURES, APPARATUSES AND SYSTEMS FOR ROLE AUTHORIZATION IN A WIRELESS NETWORK ENVIRONMENT

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefit of U.S. Provisional Application No. 63/574,727, filed in the U.S. Patent and Trademark Office on April 4, 2024, which is hereby incorporated by reference herein in its entirety.

TECHNICAL FIELD

[0002] The present disclosure is generally directed to the fields of communications, software and encoding/decoding, including, for example, to methods, architectures, apparatuses, systems related to role authorization in a wireless network environment.

BACKGROUND

[0003] A wireless transmit/receive unit associated with both a home network and a serving network may request to perform a particular role within a wireless network environment. When a wireless transmit/receive unit requests authorization to assume a particular role from a serving network, the home network performs the role authorization without taking into account or even having knowledge of the serving network.

SUMMARY

[0004] In accordance with certain representative embodiments of the present disclosure, when a wireless transmit/receive unit (WTRU) requests to authorize performing a particular role within a wireless network, a wireless network entity may determine a combined network privacy policy. Such a combined network privacy policy may accommodate for the privacy laws, regulations, or policies specified by both a home network associated with the WTRU and a serving network. As a result, the risk of introducing a security issue with respect to the serving network is reduced.

[0005] In accordance with certain representative embodiments of the present disclosure, methods and systems are provided for role authorization within a wireless network. A method may be performed by a wireless network entity, and such a method includes receiving a role authorization request including an indication of one or more roles requested by a WTRU. The method further includes determining a response to the role authorization request by applying a combined network privacy policy to the role authorization request such that the combined network privacy policy is determined based on a serving network privacy policy and a privacy policy of a home network of the WTRU. The method also includes sending the response including an indication of a role authorized for the WTRU.

[0006] In certain representative embodiments, the method further includes requesting the serving network privacy policy, receiving the serving network privacy policy, and combining the received serving network privacy policy with the privacy policy of the home network to obtain the combined network privacy policy.

[0007] In certain representative embodiments, the combined network privacy policy is determined by resolving any conflict between the serving network privacy policy and the privacy policy of the home network of the WTRU in favor of the serving network privacy policy or the privacy policy of the home network.

[0008] In certain representative embodiments, the method further includes receiving subscription and authorization parameters from a unified data management function associated with the home network of the WTRU. When determining the response to the role authorization request, the method further includes applying the received subscription and authorization parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more detailed understanding may be had from the detailed description below, given by way of example in conjunction with drawings appended hereto. Figures in such drawings, like the detailed description, are examples. As such, the Figures (FIGs.) and the detailed description are not to be considered limiting, and other equally effective examples are possible and likely. Furthermore, like reference numerals ("ref.") in the FIGs. indicate like elements, and wherein: [0010] FIG. 1A is a system diagram illustrating an example communications system, in accordance with certain embodiments;

[0011] FIG. IB is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1 A, in accordance with certain embodiments;

[0012] FIG. 1C 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, in accordance with certain embodiments;

[0013] FIG. ID 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. 1 A, in accordance with certain embodiments;

[0014] FIG. 2 is a signaling diagram illustrating the first part of a process for handling a role authorization request from a WTRU, in accordance with certain embodiments; [0015] FIG. 3 is a signaling diagram illustrating the second part of a process for handling a role authorization request from a WTRU, in accordance with certain embodiments;

[0016] FIG. 4 is a signaling diagram illustrating an alternative second part of a process for handling a role authorization request from a WTRU, in accordance with certain embodiments; and [0017] FIG. 5 is a flowchart of illustrative steps for role authorization in a wireless network, in accordance with certain embodiments.

DETAILED DESCRIPTION

[0018] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of embodiments and/or examples disclosed herein. However, it will be understood that such embodiments and examples may be practiced without some or all of the specific details set forth herein. In other instances, well-known methods, procedures, components and circuits have not been described in detail, so as not to obscure the following description. Further, embodiments and examples not specifically described herein may be practiced in lieu of, or in combination with, the embodiments and other examples described, disclosed or otherwise provided explicitly, implicitly and/or inherently (collectively "provided") herein. Although various embodiments are described and/or claimed herein in which an apparatus, system, device, etc. and/or any element thereof carries out an operation, process, algorithm, function, etc. and/or any portion thereof, it is to be understood that any embodiments described and/or claimed herein assume that any apparatus, system, device, etc. and/or any element thereof is configured to carry out any operation, process, algorithm, function, etc. and/or any portion thereof.

[0019] Example Communications System

[0020] The methods, apparatuses and systems provided herein are well-suited for communications involving both wired and wireless networks. An overview of various types of wireless devices and infrastructure is provided with respect to FIGs. 1A-1D, where various elements of the network may utilize, perform, be arranged in accordance with and/or be adapted and/or configured for the methods, apparatuses and systems provided herein.

[0021] FIG. 1A is a system 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 (ZT) unique-word (UW) discreet Fourier transform (DFT) spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block- filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0022] As shown in FIG. 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104/113, a core network (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 (or be) 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.

[0023] 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, e.g., to facilitate access to one or more communication networks, such as the CN 106/115, the Internet 110, and/or the networks 112. By way of example, the base stations 114a, 114b may be any of a base transceiver station (BTS), a Node-B (NB), an eNode-B (eNB), a Home Node-B (HNB), a Home eNode-B (HeNB), a gNode-B (gNB), a NR Node-B (NR NB), 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.

[0024] 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 an embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each or any sector of the cell. For example, beamforming may be used to transmit and/or receive signals in desired spatial directions.

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

[0026] 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 116 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 Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

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

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

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

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (Wi-Fi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0031] 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 an 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 an 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 any of a small cell, picocell or femtocell. As shown in FIG. 1 A, 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.

[0032] 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. 1 A, 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 an NR radio technology, the CN 106/115 may also be in communication with another RAN (not shown) employing any of a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technology. [0033] 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 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/114 or a different RAT.

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

[0035] FIG. IB is a system diagram illustrating an example WTRU 102. As shown in FIG. IB, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/mi crophone 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 elements/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.

[0036] 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. IB 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, e.g., in an electronic package or chip. [0037] 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 an 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 an 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.

[0038] Although the transmit/receive element 122 is depicted in FIG. IB as a single element, the WTRU 102 may include any number of transmit/receive elements 122. For example, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0039] 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 IEEE 802.11, for example.

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

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

[0042] 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 location-determination method while remaining consistent with an embodiment.

[0043] The processor 118 may further be coupled to other elements/peripherals 138, which may include one or more software and/or hardware modules/units that provide additional features, functionality and/or wired or wireless connectivity. For example, the elements/peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (e.g., 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 elements/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.

[0044] 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 uplink (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 uplink (e.g., for transmission) or the downlink (e.g., for reception)).

[0045] FIG. 1C 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, and 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0046] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0047] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink (UL) and/or downlink (DL), and the like. As shown in FIG. 1C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface. [0048] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any one of these elements may be owned and/or operated by an entity other than the CN operator.

[0049] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI 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.

[0050] The SGW 164 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via the SI 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.

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

[0053] Although the WTRU is described in FIGs. 1A-1D 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. [0054] In representative embodiments, the other network 112 may be a WLAN.

[0055] 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 into and/or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and/or referred to as peer-to-peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.1 le DLS or an 802.1 Iz tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) 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.

[0056] When using the 802.1 lac 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.

[0057] 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 nonadj acent 20 MHz channel to form a 40 MHz wide channel.

[0058] Very high throughput (VHT) STAs may support 20 MHz, 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 a medium access control (MAC) layer, entity, etc.

[0059] Sub 1 GHz modes of operation are supported by 802.11af and 802.1 lah. The channel operating bandwidths, and carriers, are reduced in 802.1 laf and 802.1 lah relative to those used in

802.1 In, and 802.1 lac. 802.1 laf supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV white space (TVWS) spectrum, and 802.1 lah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment,

802.1 lah may support meter type control/machine-type communications (MTC), 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).

[0060] WLAN systems, which may support multiple channels, and channel bandwidths, such as

802.1 In, 802.1 lac, 802.1 laf, and 802.1 lah, 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.1 lah, 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.

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

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

[0063] 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 an embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 180b may utilize beamforming to transmit signals to and/or receive signals from the WTRUs 102a, 102b, 102c. 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).

[0064] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, 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., including a varying number of OFDM symbols and/or lasting varying lengths of absolute time).

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

[0066] 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 functions (UPFs) 184a, 184b, routing of control plane information towards access and mobility management functions (AMFs) 182a, 182b, and the like. As shown in FIG. ID, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0067] The CN 115 shown in FIG. ID may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one session management function (SMF) 183 a, 183b, and at least one Data Network (DN) 185a, 185b. The CN 115 may further include a Policy Control Function (PCF) 186, a Unified Data Management (UDM) service 187 and a Security and Key Management Function (SKMF) 188.

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

[0069] 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 protocol data unit (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, e.g., 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 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.

[0070] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an Nl 1 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, Ethernet-based, and the like.

[0071] 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, e.g., 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 multihomed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0072] The PCF 186 may be connected to an AMF 182a, 182b via an N15 interface, and may be connected to an SMF 183a, 183b by an N7 interface. The Policy Control Function (PCF) may provide policies which control the operation of the CN 115. The use of policies may provide the operator of the CN 115 with a mechanism for managing the operation of the network. A policy may be applied to each of a number of instances of a network function in the network. Any update to the policy may be made at the Policy Control Function and the updated policy may then be applied to each of the number of instances of a network function in the network.

[0073] The UDM 187 may be connected to an AMF 182a, 182b via an N8 interface, and may be connected to an SMF 183a, 183b by an N10 interface. The UDM service may provide other functions in the network, or functions in another network (e.g., a remote wireless network operated by a different network operator), with an interface to a subscriber database storing data relating to each subscriber to the service provided by the RAN 113 and the CN 115.

[0074] The SKMF 188 may provide security and key management functions for one or more services involving security requirements (e.g., privacy-sensitive services such as ranging based services, sidelink positioning services, proximity-based services, and sensing network functions and the like). The SKMF 118 may comprise one or both of a SideLink Positioning Key Management Function (SLPKMF) and a 5G ProSe Key Management Function (PKMF).

[0075] 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 an 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.

[0076] In view of FIGs. 1 A-1D, and the corresponding description of FIGs. 1 A-1D, one or more, or all, of the functions described herein with regard to any of: WTRUs 102a-d, base stations 114a- b, eNode-Bs 160a-c, MME 162, SGW 164, PGW 166, gNBs 180a-c, AMFs 182a-b, UPFs 184a- b, SMFs 183a-b, DNs 185a-b, PCF 186, UDM 187, SKMF 188 and/or any other element(s)/device(s) described herein, may be performed by one or more emulation elements/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.

[0077] 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 performing testing using over-the-air wireless communications. [0078] 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 test 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.

[0079] Furthermore, it will be understood that a wireless network may include any suitable components and devices, including, for example, any of one or more base stations, one or more TRPs, one or more gNBs, one or more WTRUs, or any combination thereof. It will be further understood that a component or device that is part of the wireless network can be referred to as communicating with the wireless network when it is communicating with any one or more other components or devices of the wireless network. For example, reference to a WTRU, which is part of the wireless network, transmitting or receiving signals to or from the wireless network refers to the WTRU transmitting or receiving signals, respectively, to or from any other component or device (e.g., another WTRU) of the wireless network.

[0080] It will be further understood that a wireless network entity may be in reference to one or more suitable network functions that are part of a core network (e.g., AMF 182a-182b, SMF 183a- 183b, and UPF 184a-184b). The functionality provided by a wireless network entity may be a combination of one or more (partial) functionalities provided by various network functions.

[0081] Overview

[0082] Agreements between wireless network operators may enable subscribers to use the communications services provided by a first network (i.e., a home network) or to use communication services provided by a second network (i.e., a visited or serving network). In some cases, the home network and visited network may be in different countries. If any WTRU 102a, 102b, 102c is receiving service from a visited network, the WTRU is said to be "roaming." In a scenario where any WTRU 102a, 102b, 102c is roaming, the visited network may contact UDM 187 (and, in some examples, PCF 186) in the home network to, for example, ensure that the subscriber is a genuine subscriber to the home network and has paid the operator of the home network a fee for receiving roaming service in the visited network.

[0083] Both the home network and the visited network may have the architecture illustrated in FIG. ID. Services made available to roaming WTRU 102a, 102b, 102c may include services involving security requirements (e.g. privacy-sensitive services) as mentioned above. [0084] One example of a service involving security requirements is integrated sensing.

[0085] Integrated Sensing

[0086] Use cases and potential requirements for enhancement of a communications system to provide sensing services may address different target verticals or applications (e.g., autonomous/assisted driving, vehicle-to-everything (V2X), unmanned aerial vehicles (UAVs), three dimensional (3D) maps, smart cities, smart homes, factories, healthcare, or maritime sector). [0087] Integrated sensing may include a process of collecting sensing measurement data - which may be data collected about radio/wireless signals impacted (e.g., reflected, refracted, diffracted) by an object or environment of interest - for sensing purposes and deriving sensing results from processing sensing measurement data. The area defined for sensing may be referred to as the sensing service area location, which may be an area or location whether with or without obstacles, for which the communications system can provide sensing service with a certain quality.

[0088] One of the use cases for integrated sensing may be object detection (e.g., pedestrian or animal intrusion detection on a highway or intruder detection in the surroundings of a smart home). [0089] In these scenarios, a base station or WTRU may detect the intrusion on the sensing area of a base station by itself or by collaboration between a WTRU and a base station. The sensing measurement may be transferred to the network and further processed into the sensing result.

[0090] Another example use case for integrated sensing is transparent sensing. In transparent sensing, sensing data may be captured by a WTRU and communicated so that the communications system is aware of the sensing information.

[0091] In this scenario, a user terminal may acquire sense signals from many 3GPP and non- 3GPP devices. The communications network may determine various available sensing services by processing collated sensing data.

Sensing Network Functions (Sensing NF)

[0092] To enable integrated sensing, network functions collectively called sensing NFs may be provided. Sensing network functions may include an Integrated Sensing Assistance NF (ISANF) and a Sensing Operation Management Function (SOMF). An ISANF and SOMF may be logical entities and may be collocated with other entities (e.g., ISANF may be collocated with a Network Exposure Function (NEF)). ISANF and SOMF both may be collocated with an NEF. An SOMF may be collocated with AMF. An SOMF may be collocated with an RAN.

[0093] The ISANF may oversee interaction with an Application Function (AF) providing sensing services. The ISANF may understand the service request from the AF and may derive the corresponding requested sensing mechanism. Based on the sensing mechanism, the ISANF may forward the request to the relevant NFs within 5GC that serve the region of interest or requested entities (e.g., WTRUs). When the AF is a 3rd party application and is not a trusted 5GS entity, the AF and ISANF may communicate through an NEF.

[0094] The SOMF may handle the coordination of sensing operations between a base station (BS) and WTRUs. Based on information received from the AMF in the requested sensing region, a BSs and WTRUs’ list, and requested sensing mechanism with QoS requirement, the SOMF may derive coordination information for a sensing operation. For example, the SOMF may decide the role for a sensing operation such as being designed as a sender(s) of sensing signal(s), receiver(s) of sensing signal(s), entity to collect the sensing measurement data, or entity to calculate sensing result. For example, the SOMF may determine the sensing period and the waveform of the sensing signal and request BS(s) or sender(s) resource assignment for sending the sensing signal at the sensing period.

[0095] Another example of a service involving security requirements is ranging based services and SideLink (SL) positioning.

[0096] Ranging Based Services and Sidelink Positioning

[0097] The SideLink Positioning Key Management Function (SLPKMF) is a logical function handling network-related operations required for the generation and provisioning of security materials used for ranging/SL positioning services. The SLPKMF has similar functionalities of that to a 5G Prose Key Management Function (PKMF). The SLPKMF may be a standalone entity or collocated with 5G PKMF. In addition to the functionalities supported by 5G PKMF, the SLPKMF may support the at least one of the following functions: key management for secure unicast direct link establishment between WTRUs for ranging/SL positioning services provided by the network; WTRU role authorization via the UDM; or key management for the protection of SideLink Positioning Protocol (SLPP) signalling broadcast/groupcast.

[0098] The address of SLPKMF may be preconfigured on the WTRU or provisioned by the PCF to the WTRU.

[0099] In the case of other services such as integrated sensing or D2D communication, similar functionalities may be performed by the SKMF.

[0100] Yet another example of a service involving security requirements is Proximity based Services (ProSe).

[0101] Proximity based Services (ProSe)

[0102] In some examples of ProSe services, the network may authorize a role of a WTRU seeking to claim a role before a ProSe capable WTRU claims its role to the peer WTRU(s) in a discovery message. The WTRU role authorization may be performed by an SKMF through discovery key request/response messages during the security procedure for ranging/SL positioning discovery. The authorization information used to check whether the WTRU is allowed to act as the claimed role in a ranging/SL positioning service may only based on the WTRU subscription data.

[0103] In some examples where the WTRU is roaming, the WTRU role authorization in the SL positioning procedure or sensing procedure may be performed by SKMF 188 in the home network purely based on the WTRU subscription data in UDM 187 without any inputs from the serving network (herein also interchangeably referred to as a visited network). The details, scope, and basis for the WTRU role authorization decision made by the home network take no account of the serving network. This may cause a security risk to the serving network due to several reasons. For example, there may be different privacy laws or privacy regulations between the two networks (i.e., the home network versus the visited network). In another example, the serving network may have strict security controls over certain roles such as the role of the SL positioning/ sensing server WTRU. Assigning such a role may potentially cause severe security damages if the WTRU is not scrutinized.

[0104] For the integrated sensing and D2D communication, WTRU role authorization by the SKMF in the home network face the same problem, namely how serving network security and privacy requirements are to be met.

[0105] In the case of integrated sensing, the WTRU may request authorization from the SKMF for roles to be performed in the serving network. Such roles may include a sensing transmitter role, sensing receiver role, or sensing server WTRU role that is capable calculating a sensing result.

[0106] In summary, a problem arises in relation to enforcing serving network privacy laws, regulations, or privacy policies when the WTRU role for procedures (e.g., SideLink, sensing, or D2D communication) are assigned by the SKMF in the home network taking into consideration additional info from the WTRU subscription data in UDM 187.

[0107] The authorized role for a procedure involving security requirements (e.g., positioning and sensing) may be assigned in an authorization token by the SKMF upon authorization being requested. The SKMF may determine a response to the authorization request based on the authorization information obtained from both the serving network and the home network in addition to the user privacy profile obtained from the UDM from the home network. The serving network role authorization information may include at least one of the operator’s privacy policy, associated privacy laws or regulations that control the privacy in the serving network, or the WTRU’s capability requirement from the serving network. If the requested role(s) are authorized, the SKMF may assign the role(s) along with contextual parameters to the WTRU. The parameters sent back to the requester may be digitally signed. The contextual parameters may specify conditions that may change or modify WTRU role(s) such as location validity, time and duration validity, and other limitations or restrictions.

[0108] The discovery request may indicate other requirements for authorization such as the expected duration of the role authorization, location where the role is performed, or the network identifier (e.g., visited public land mobile network (VPLMN)).

[0109] In the case of integrated sensing, the WTRU may request authorization from the SKMF for sensing role(s) to be performed in the serving network (e.g., a sensing transmitter role, a sensing receiver role, or a sensing server WTRU role that is capable calculating a sensing result).

[0110] If the role(s) are not authorized based on the serving network policy, a wireless network entity may reject the request or assign role(s) recommended by the serving network. FIG. 2 illustrates an example of a first part of a role authorization process in some representative embodiments. In the representative embodiments, operations may be performed by a PCF in the home network (hPCF), a PCF in the visited network (vPCF), or any suitable wireless network entity. The SKMF and UDM/Unified Data Repository (UDR) seen in FIG. 2 may be included in the home CN. In some embodiments, the hPCF and UDM may be combined into a UDR function. [0111] At 202, SKMF 214 (which may be the same as SKMF 188) may receive a role assignment request from WTRU 212 (which may be the same as any of suitable WTRUs 102a-102d) such that WTRU 212 intends, by acting as the requested role(s), to participate in procedures requiring security considerations (e.g., the SL positioning process, integrated sensing, or D2D communication). The request may indicate the scope of the role(s) such as information related to how long the role needs to be authorized for, location area, serving network, duration, starting time, or any other suitable information.

[0112] At 204, SKMF 214 may determine the current location, serving network, or other required WTRU role determination information for the requested role(s) by WTRU 212. If the current serving network that WTRU 212 is visiting is different from the requested serving network for the role(s), SKMF 212 may reject the request with a reason code.

[0113] At 206, SKMF 212 may request the security and privacy policies from hPCF 218 (which may be the same as PCF 186). The request may include at least one of the requested role(s), WTRU identification, or requested scope(s) that include the serving network identifier (e.g., VPLMN identification).

[0114] At 208, hPCF 218 may contact vPCF 220 to solicit the serving network inputs for the role(s) requested by WTRU 212 that will be acting in the serving network. The request may include all the information from SKMF 214 and other information that may be added by hPCF 218. hPCF 218 may add policy information associated with the home network, such as privacy policies, privacy laws, privacy regulations and operator’s policies from the home network.

[0115] At 210, the serving network (or visited network) may authorize the requested role(s) and any associated scope(s) based on at least one of the information in the request from hPCF 218, the local security policy, privacy laws, privacy regulations, the operator’s policy, or serving network capabilities.

[0116] With respect to FIG. 3, if 210 is successful, vPCF 220 may send the authorized roles(s) and any associated scope(s) to hPCF 218. The response may include privacy policies formulated based on at least one of the serving network requirements, an operator’s policy, privacy laws, or privacy regulations. The response message may also include other parameters such as proposed or recommended role(s) in addition to or instead of requested role(s) of WTRU 212. The serving network may propose alternative or additional role(s) for WTRU 212. The response message may also include contextual parameters. The contextual parameters may include at least one of the day of the year, time of the day, location (e.g., topographical coordinates and elevation), or weather conditions at the location.

[0117] At 304, once hPCF 218 receives the response from vPCF 220, hPCF 218 may resolve any conflicts in the privacy policies between the serving network and the home network. hPCF 218 may formulate combined privacy policies and role(s) recommended for WTRU 212.

[0118] At 306 and at 308, SKMF 214 may retrieve a privacy profile that includes the subscription parameters and other authorization parameters from UDM/UDR 222 (which may be the same as UDM 187) that may be required to authorize the request for the role(s) assignment from WTRU 212.

[0119] At 310, SKMF 214 may determine the requested role and privacy requirement(s) for the role for WTRU 212 based on the combined policy from at least one of both the serving and home network, user privacy profile received from UDM/UDR 222, or other authorization information. If the requested role(s) along with the contextual parameters are authorized, SKMF 214 may assign the role(s) with the associated contextual parameters to WTRU 212. The role(s) and contextual parameters sent back to the requester (e.g., WTRU 212) may be digitally signed.

[0120] The combined policies may contain conditions that will be used by SKMF 214 in deciding the role assignment and scopes of the role(s). For example, conditions may include one or more of a valid network, valid time constraint, valid location, valid area, valid duration, privacy-related restriction (e.g., such that entities may be able to expose WTRU 212 privacy information) for WTRU 212. [0121] If the role(s) is not authorized, the communications network may reject the request or assign a role(s) that is recommended by the serving network.

[0122] At 312, SKMF 214 sends the authorized role(s) in authorization token back to the role requesting WTRU (e.g., WTRU 212). The parameters sent back to the requester will be digitally signed by SKMF 214, and the token consumer may validate the digital signature.

[0123] In some representative embodiments, in a variation to the signaling seen in FIG. 2 and FIG. 3, the request at 204 to vPCF 220 may be sent directly from the SKMF 214 without going through hPCF 218. vPCF 220 may then respond to the SKMF 214 with the information formulated by vPCF 220. SKMF 214 may obtain the policy from hPCF 218 as seen at 206 and at 304. In this case, SKMF 214 may resolve any conflicts between hPCF 218 and vPCF 220. SKMF 214 may use the combined policies for the decision of the WTRU role authorization.

[0124] In some representative embodiments, as an alternative, vPCF 220 may receive inputs from hPCF 218 and resolve any conflicts before combining inputs from both vPCF 220 and hPCF 218 that will be used for the final call on the role assignment.

[0125] In some representative embodiments (e.g., after any operation following 304), if SKMF 214 receives an update to information that is used for the role decision at 310, SKMF 214 may perform the role decision based on the updated information. SKMF 214 may send an update of the authorized role(s) in authorization tokens back to the role-requesting WTRU. The parameters sent back to the requester may be digitally signed by SKMF 214 and may be validated by the token consumer.

[0126] In some representative embodiments, when WTRU 212 registers itself in the visited network (serving network), vPCF 220 may provide the policy related information to hPCF 218 which in turn could provide the policy related information to SKMF 214. As such, a future role assignment may be performed by SKMF 214 without requiring interactions with vPCF 220 and thereby reduce the signaling required at the time of handling the role authentication request. The exchange of information from vPCF 220 to hPCF 218 may be linked with other triggers.

[0127] FIG. 4 illustrates alternative signaling which may be adopted instead of the signaling illustrated in FIG. 3 in some representative embodiments. In such embodiments, hPCF 218 may request at least one of the WTRU’s privacy policy, user consent conditions, or authorization information from UDM/UDR 222 instead of SKMF 214 requesting that information from the UDM/UDR 222. In such a case, hPCF 218 may retrieve the privacy profile that includes the subscription parameters and other authorization parameters from UDM/UDR 222 that are needed to authorize the request for the role(s) assignment of WTRU 212 (shown at 404 and at 406 in FIG. 4. After hPCF 218 receives the information from UDM/UDR 222, hPCF 218 may resolve any conflicts between the serving network and the home network. hPCF 218 may formulate the combined role policy, before, in some representative embodiments, sending the combined role policy to the SKMF 214 at 408 along with any information that may be required by SKMF 214. [0128] FIG. 5 is a flowchart of illustrative operations for role authorization in a wireless network, in accordance with certain embodiments. Flowchart 500 outlines, for example, the operations for how one or more serving network privacy laws, regulations, or privacy policies may be enforced when a role for a WTRU (e.g., SL positioning, sensing, D2D communication) is assigned by the SKMF of a home network while also accounting for additional information (e.g., WTRU subscription data) from a UDM.

[0129] At 502, a wireless network entity (e.g., an SKMF) receives a role authorization request that includes an indication of one or more roles requested by a WTRU.

[0130] In certain representative embodiments, the role authorization request further includes an indication of a scope of the role authorization request. In such representative embodiments, the indication of the scope of the role authorization request includes one or more of a time period for which the role authorization request is sought, a geographical area for which the role authorization request is sought, or a serving network for which the role authorization request is sought.

[0131] In certain representative embodiments, the role authorization request further includes an indication of a serving network for which the role authorization request is sought.

[0132] At 504, the wireless network entity determines a response to the role authorization request by applying a combined network privacy policy to the role authorization request such that the combined network privacy policy is determined based on a serving network privacy policy and a privacy policy of a home network of the WTRU.

[0133] In certain representative embodiments, the wireless network entity is further configured to request the serving network privacy policy (e.g., from a different network entity), receive the serving network privacy policy, and combine the received serving network privacy policy with the privacy policy of the home network to obtain the combined network privacy policy.

[0134] In certain representative embodiments, the combined network privacy policy is determined by resolving any conflict between the serving network privacy policy and the privacy policy of the home network of the WTRU in favor of the serving network privacy policy or the privacy policy of the home network.

[0135] In certain representative embodiments, the wireless network entity further receives subscription and authorization parameters from a unified data management function associated with the home network of the WTRU. When determining the response to the role authorization request, the wireless network entity is further configured to apply the received subscription and authorization parameters.

[0136] At 506, the wireless network sends the response including an indication of a role authorized for the WTRU.

[0137] In certain representative embodiments, the role authorization request is a first role authorization request. In such representative embodiments, the wireless network entity further compares a serving network with a serving network for which a second role authorization request is sought. In response to the comparison finding that the serving network is different than the serving network for which the second role authorization request is sought, the wireless network entity further rejects the second role authorization request.

[0138] In certain representative embodiments, the role authorized for the WTRU is different than the role requested by the WTRU.

[0139] In certain representative embodiments, the wireless network entity is further configured to apply a digital signature or other integrity protection to at least one of the indications of the role authorized for the WTRU or an indication of a scope the role authorized. The response to the role authorization request includes at least one of an applied digital signature or integrity protection. [0140] Although features and elements are provided above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. The present disclosure is not to be limited in terms of the particular embodiments described in this application, which are intended as illustrations of various aspects. Many modifications and variations may be made without departing from its spirit and scope, as will be apparent to those skilled in the art. No element, act, or instruction used in the description of the present application should be construed as critical or essential to the invention unless explicitly provided as such. Functionally equivalent methods and apparatuses within the scope of the disclosure, in addition to those enumerated herein, will be apparent to those skilled in the art from the foregoing descriptions. Such modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled. It is to be understood that this disclosure is not limited to particular methods or systems.

[0141] The foregoing embodiments are discussed, for simplicity, with regard to the terminology and structure of wireless communication capable devices, (e.g., radio wave emitters and receivers). However, the embodiments discussed are not limited to these systems but may be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves such as acoustic waves.

[0142] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used herein, the term "video" or the term "imagery" may mean any of a snapshot, single image and/or multiple images displayed over a time basis. As another example, when referred to herein, the terms "user equipment" and its abbreviation "UE", the term "remote" and/or the terms "head mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmit and/or receive unit (WTRU); (ii) any of a number of embodiments of a WTRU; (iii) a wireless-capable and/or wired-capable (e.g., tetherable) device configured with, inter alia, some or all structures and functionality of a WTRU; (iii) a wireless-capable and/or wired-capable device configured with less than all structures and functionality of a WTRU; or (iv) the like. Details of an example WTRU, which may be representative of any WTRU recited herein, are provided herein with respect to FIGs. 1 A-1D. As another example, various disclosed embodiments herein supra and infra are described as utilizing a head mounted display. Those skilled in the art will recognize that a device other than the head mounted display may be utilized and some or all of the disclosure and various disclosed embodiments can be modified accordingly without undue experimentation. Examples of such other device may include a drone or other device configured to stream information for providing the adapted reality experience.

[0143] In addition, the methods provided herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and 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 internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

[0144] Variations of the method, apparatus and system provided above are possible without departing from the scope of the invention. In view of the wide variety of embodiments that can be applied, it should be understood that the illustrated embodiments are examples only and should not be taken as limiting the scope of the following claims. For instance, the embodiments provided herein include handheld devices, which may include or be utilized with any appropriate voltage source, such as a battery and the like, providing any appropriate voltage.

[0145] Moreover, in the embodiments provided above, processing platforms, computing systems, controllers, and other devices that include processors are noted. These devices may include at least one Central Processing Unit ("CPU") and memory. In accordance with the practices of persons skilled in the art of computer programming, reference to acts and symbolic representations of operations or instructions may be performed by the various CPUs and memories. Such acts and operations or instructions may be referred to as being "executed," "computer executed" or "CPU executed."

[0146] One of ordinary skill in the art will appreciate that the acts and symbolically represented operations or instructions include the manipulation of electrical signals by the CPU. An electrical system represents data bits that can cause a resulting transformation or reduction of the electrical signals and the maintenance of data bits at memory locations in a memory system to thereby reconfigure or otherwise alter the CPU's operation, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to or representative of the data bits. It should be understood that the embodiments are not limited to the above-mentioned platforms or CPUs and that other platforms and CPUs may support the provided methods.

[0147] The data bits may also be maintained on a computer readable medium including magnetic disks, optical disks, and any other volatile (e.g., Random Access Memory (RAM)) or non-volatile (e.g., Read-Only Memory (ROM)) mass storage system readable by the CPU. The computer readable medium may include cooperating or interconnected computer readable medium, which exist exclusively on the processing system or are distributed among multiple interconnected processing systems that may be local or remote to the processing system. It should be understood that the embodiments are not limited to the above-mentioned memories and that other platforms and memories may support the provided methods.

[0148] In an illustrative embodiment, any of the operations, processes, etc. described herein may be implemented as computer-readable instructions stored on a computer-readable medium. The computer-readable instructions may be executed by a processor of a mobile unit, a network element, and/or any other computing device.

[0149] There is little distinction left between hardware and software implementations of aspects of systems. The use of hardware or software is generally (but not always, in that in certain contexts the choice between hardware and software may become significant) a design choice representing cost versus efficiency tradeoffs. There may be various vehicles by which processes and/or systems and/or other technologies described herein may be affected (e.g., hardware, software, and/or firmware), and the preferred vehicle may vary with the context in which the processes and/or systems and/or other technologies are deployed. For example, if an implementer determines that speed and accuracy are paramount, the implementer may opt for a mainly hardware and/or firmware vehicle. If flexibility is paramount, the implementer may opt for a mainly software implementation. Alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.

[0150] The foregoing detailed description has set forth various embodiments of the devices and/or processes via the use of block diagrams, flowcharts, and/or examples. Insofar as such block diagrams, flowcharts, and/or examples include one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, or examples may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or virtually any combination thereof. In an embodiment, several portions of the subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), and/or other integrated formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or as virtually any combination thereof, and that designing the circuitry and/or writing the code for the software and or firmware would be well within the skill of one of skill in the art in light of this disclosure. In addition, those skilled in the art will appreciate that the mechanisms of the subj ect matter described herein may be distributed as a program product in a variety of forms, and that an illustrative embodiment of the subject matter described herein applies regardless of the particular type of signal bearing medium used to actually carry out the distribution. Examples of a signal bearing medium include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a CD, a DVD, a digital tape, a computer memory, etc., and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.).

[0151] Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in the fashion set forth herein, and thereafter use engineering practices to integrate such described devices and/or processes into data processing systems. That is, at least a portion of the devices and/or processes described herein may be integrated into a data processing system via a reasonable amount of experimentation. Those having skill in the art will recognize that a typical data processing system may generally include one or more of a system unit housing, a video display device, a memory such as volatile and non-volatile memory, processors such as microprocessors and digital signal processors, computational entities such as operating systems, drivers, graphical user interfaces, and applications programs, one or more interaction devices, such as a touch pad or screen, and/or control systems including feedback loops and control motors (e.g., feedback for sensing position and/or velocity, control motors for moving and/or adjusting components and/or quantities). A typical data processing system may be implemented utilizing any suitable commercially available components, such as those typically found in data computing/communication and/or network computing/communication systems.

[0152] The herein described subject matter sometimes illustrates different components included within, or connected with, different other components. It is to be understood that such depicted architectures are merely examples, and that in fact many other architectures may be implemented which achieve the same functionality. In a conceptual sense, any arrangement of components to achieve the same functionality is effectively "associated" such that the desired functionality may be achieved. Hence, any two components herein combined to achieve a particular functionality may be seen as "associated with" each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated may also be viewed as being "operably connected", or "operably coupled", to each other to achieve the desired functionality, and any two components capable of being so associated may also be viewed as being "operably couplable" to each other to achieve the desired functionality. Specific examples of operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

[0153] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.

[0154] It will be understood by those within the art that, in general, terms used herein, and especially in the appended claims (e.g., bodies of the appended claims) are generally intended as "open" terms (e.g., the term "including" should be interpreted as "including but not limited to," the term "having" should be interpreted as "having at least," the term "includes" should be interpreted as "includes but is not limited to," etc.). It will be further understood by those within the art that if a specific number of an introduced claim recitation is intended, such an intent will be explicitly recited in the claim, and in the absence of such recitation no such intent is present. For example, where only one item is intended, the term "single" or similar language may be used. As an aid to understanding, the following appended claims and/or the descriptions herein may include usage of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be construed to imply that the introduction of a claim recitation by the indefinite articles "a" or "an" limits any particular claim including such introduced claim recitation to embodiments including only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and indefinite articles such as "a" or "an" (e.g., "a" and/or "an" should be interpreted to mean "at least one" or "one or more"). The same holds true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim recitation is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted to mean at least the recited number (e.g., the bare recitation of "two recitations," without other modifiers, means at least two recitations, or two or more recitations). Furthermore, in those instances where a convention analogous to "at least one of A, B, and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, and C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to "at least one of A, B, or C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B, or C" would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). It will be further understood by those within the art that virtually any disjunctive word and/or phrase presenting two or more alternative terms, whether in the description, claims, or drawings, should be understood to contemplate the possibilities of including one of the terms, either of the terms, or both terms. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B." Further, the terms "any of followed by a listing of a plurality of items and/or a plurality of categories of items, as used herein, are intended to include "any of," "any combination of," "any multiple of," and/or "any combination of multiples of the items and/or the categories of items, individually or in conjunction with other items and/or other categories of items. Moreover, as used herein, the term "set" is intended to include any number of items, including zero. Additionally, as used herein, the term "number" is intended to include any number, including zero. And the term "multiple", as used herein, is intended to be synonymous with "a plurality".

[0155] In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0156] As will be understood by one skilled in the art, for any and all purposes, such as in terms of providing a written description, all ranges disclosed herein also encompass any and all possible subranges and combinations of subranges thereof. Any listed range can be easily recognized as sufficiently describing and enabling the same range being broken down into at least equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each range discussed herein may be readily broken down into a lower third, middle third and upper third, etc. As will also be understood by one skilled in the art all language such as "up to," "at least," "greater than," "less than," and the like includes the number recited and refers to ranges which can be subsequently broken down into subranges as discussed above. Finally, as will be understood by one skilled in the art, a range includes each individual member. Thus, for example, a group having 1-3 cells refers to groups having 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers to groups having 1, 2, 3, 4, or 5 cells, and so forth.

[0157] Moreover, the claims should not be read as limited to the provided order or elements unless stated to that effect. In addition, use of the terms "means for" in any claim is intended to invoke 35 U.S.C. §112, 6 or means-plus-function claim format, and any claim without the terms "means for" is not so intended.

Claims

CLAIMS What is claimed is:

1. A method for role authorization in a wireless network environment, comprising: receiving a role authorization request comprising an indication of one or more roles requested by a wireless transmit/receive unit (WTRU); determining a response to the role authorization request by applying a combined network privacy policy to the role authorization request, wherein the combined network privacy policy is determined based on a serving network privacy policy and a privacy policy of a home network of the WTRU; and sending the response comprising an indication of a role authorized for the WTRU.

2. The method of claim 1, further comprising: requesting the serving network privacy policy; receiving the serving network privacy policy; and combining the received serving network privacy policy with the privacy policy of the home network to obtain the combined network privacy policy.

3. The method of any of claims 1-2, wherein the combined network privacy policy is determined by resolving any conflict between the serving network privacy policy and the privacy policy of the home network of the WTRU in favor of the serving network privacy policy or the privacy policy of the home network.

4. The method of any of claims 1-3, wherein the role authorization request further comprises an indication of a scope of the role authorization request.

5. The method of claim 4, wherein the indication of the scope of the role authorization request comprises one or more of a time period for which the role authorization request is sought, a geographical area for which the role authorization request is sought, or a serving network for which the role authorization request is sought.

6. The method of any of claims 1-5, wherein the role authorization request further comprises an indication of a serving network for which the role authorization request is sought.

7. The method of any of claims 1-6, wherein the role authorization request is a first role authorization request, the method further comprising: comparing a serving network with a serving network for which a second role authorization request is sought; and in response to the comparison finding that the serving network is different than the serving network for which the second role authorization request is sought, rejecting the second role authorization request.

8. The method of any of claims 1-7, further comprising: receiving subscription and authorization parameters from a unified data management function associated with the home network of the WTRU, and wherein determining the response to the role authorization request further comprises applying the received subscription and authorization parameters.

9. The method of any of claims 1-8, wherein the role authorized for the WTRU is different than the role requested by the WTRU.

10. The method of any of claims 1-9, further comprising: applying a digital signature or other integrity protection to at least one of the indication of the role authorized for the WTRU or an indication of a scope the role authorized, wherein the response to the role authorization request includes at least one of an applied digital signature or integrity protection.

11. A wireless network entity of a core network (CN) configured to authorize a role for a wireless transmit/receive unit (WTRU), the wireless network entity comprising at least one processor and configured to: receive a role authorization request comprising an indication of one or more roles requested by the WTRU; determine a response to the role authorization request by applying a combined network privacy policy to the role authorization request, wherein the combined network privacy policy is determined based on a serving network privacy policy and a privacy policy of a home network of the WTRU; and send the response comprising an indication of a role authorized for the WTRU.

12. The wireless network entity of claim 11, further configured to: request the serving network privacy policy; receive the serving network privacy policy; and combine the received serving network privacy policy with the privacy policy of the home network to obtain the combined network privacy policy.

13. The wireless network entity of any of claims 11-12, wherein the combined network privacy policy is determined by resolving any conflict between the serving network privacy policy and the privacy policy of the home network of the WTRU in favor of the serving network privacy policy or the privacy policy of the home network.

14. The wireless network entity of any of claims 11-13, wherein the role authorization request further comprises an indication of a scope of the role authorization request.

15. The wireless network entity of claim 14, wherein the indication of the scope of the role authorization request comprises one or more of a time period for which the role authorization request is sought, a geographical area for which the role authorization request is sought, or a serving network for which the role authorization request is sought.

16. The wireless network entity of any of claims 11-15, wherein the role authorization request further comprises an indication of a serving network for which the role authorization request is sought.

17. The wireless network entity of any of claims 11-16, wherein the role authorization request is a first role authorization request, the wireless network entity further configured to: compare a serving network with a serving network for which a second role authorization request is sought; and in response to the comparison finding that the serving network is different than the serving network for which the second role authorization request is sought, reject the second role authorization request.

18. The wireless network entity of any of claims 11-17, further configured to: receive subscription and authorization parameters from a unified data management function associated with the home network of the WTRU, and, when determining the response to the role authorization request, the wireless network entity is further configured to apply the received subscription and authorization parameters.

19. The wireless network entity of any of claims 11-18, wherein the role authorized for the WTRU is different than the role requested by the WTRU.

20. The wireless network entity of any of claims 11-19, further configured to: apply a digital signature or other integrity protection to at least one of the indication of the role authorized for the WTRU or an indication of a scope the role authorized, wherein the response to the role authorization request includes at least one of an applied digital signature or integrity protection.