[go: up one dir, main page]

WO2025075939A1 - Découverte de relais et améliorations de sécurité de communication - Google Patents

Découverte de relais et améliorations de sécurité de communication Download PDF

Info

Publication number
WO2025075939A1
WO2025075939A1 PCT/US2024/049367 US2024049367W WO2025075939A1 WO 2025075939 A1 WO2025075939 A1 WO 2025075939A1 US 2024049367 W US2024049367 W US 2024049367W WO 2025075939 A1 WO2025075939 A1 WO 2025075939A1
Authority
WO
WIPO (PCT)
Prior art keywords
wtru
discovery
protected
relay
solicitation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/US2024/049367
Other languages
English (en)
Inventor
Samir Ferdi
Taimoor ABBAS
Jung Je SON
Michelle Perras
Saad Ahmad
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital Patent Holdings Inc
Original Assignee
InterDigital Patent Holdings Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by InterDigital Patent Holdings Inc filed Critical InterDigital Patent Holdings Inc
Publication of WO2025075939A1 publication Critical patent/WO2025075939A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03Protecting confidentiality, e.g. by encryption
    • H04W12/037Protecting confidentiality, e.g. by encryption of the control plane, e.g. signalling traffic
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/005Discovery of network devices, e.g. terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/04Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • a fifth generation of mobile communication radio access technology may be referred to as 5G new radio (NR).
  • a previous (legacy) generation of mobile communication RAT may be, for example, fourth generation (4G) long-term evolution (LTE).
  • Wireless communication devices may establish communications with other devices and data networks, e.g., via an access network, such as a radio access network (RAN).
  • RAN radio access network
  • a device such as the first wireless transmit/receive unit (WTRU) may be in direct proximity to another device, such as the second WTRU.
  • the first WTRU may include a processor.
  • the first WTRU may be configured to perform one or more of the following.
  • the first WTRU may receive a first protected discovery solicitation message from the second WTRU.
  • the protected discovery solicitation message may be, or may include, a first protected direct discovery set.
  • the first protected direct discovery set may be, or may include, encrypted discoverer user information and discoveree user information.
  • the first WTRU may allocate a direct discovery solicitation Identification (ID) and/or may associate the direct discovery solicitation ID with a WTRU source Layer 2 (L2) ID.
  • the WTRU source L2 ID may be associated with the second WTRU.
  • the first WTRU may send another protected discovery solicitation message (e.g., a second protected discovery solicitation message) to another device, such as a third WTRU.
  • the second protected discovery solicitation message may be, or may include, the first protected direct discovery set and/or the direct discovery solicitation ID.
  • the first WTRU may receive a first protected discovery solicitation response message, from the third WTRU.
  • the first protected discovery solicitation response message may be, or may include, a second protected direct discovery set and/or the direct discovery solicitation ID.
  • the first WTRU may determine the WTRU source L2 ID associated with the discoverer WTRU, e.g., using the direct discovery solicitation ID.
  • the first WTRU may send a second protected discovery solicitation response message to the first WTRU.
  • the second protected discovery solicitation response message may be, or may include, the second protected direct discovery set.
  • the first WTRU described herein may be a UE-to-UE relay WTRU
  • the second WTRU may be a discoverer WTRU
  • the third WTRU may be a discoverer WTRU.
  • the second WTRU may be an end WTRU (e.g., a first end WTRU)
  • the third WTRU may be another end WTRU (e.g., a second WTRU).
  • the first WTRU, the second WTRU, and/or the third WTRU may be provisioned with a discovery parameter.
  • the discovery parameter may be, or may include, a discovery user confidentiality key (DUCK), a discovery user integrity key (DUIK), a discovery user scrambling key (DUSK), and/or timing information.
  • the discovery parameter may be associated with a relay service code (RSC) (e.g., a UE-to- Network (U2N) RSC).
  • RSC relay service code
  • a device such as the first WTRU, may be provided.
  • the first WTRU may include a processor.
  • the first WTRU may perform one or more of the following.
  • the first WTRU may receive a protected discovery solicitation message from the second WTRU.
  • the protected discovery solicitation message may include relay user information, a first protected direct discovery set including encrypted discoverer user information, discoveree user information, and/or a direct discovery solicitation ID.
  • the direct discovery solicitation ID may be associated with a relay source L2 ID.
  • the first WTRU may send a protected discovery solicitation response message to the second WTRU.
  • the protected discovery solicitation response message may include a second protected direct discovery set and/or the discovery solicitation ID.
  • a device such as the first WTRU, may be provided.
  • the first WTRU may be an intermediate relay WTRU.
  • the first WTRU may include a processor.
  • the processor may be programmed to perform one or more processes.
  • the first WTRU may receive a first protected discovery solicitation message from another device, such as a second relay WTRU.
  • the first protected discovery solicitation message may be, or may include, one or more of a Relay Service Code (RSC) indication, user information for the second relay WTRU, a first protected direct discovery set, and/or a direct discovery solicitation Identifier (ID).
  • the direct discovery solicitation ID may be associated with the source L2 ID of the second relay WTRU.
  • the first WTRU may send a second protected discovery solicitation message to the discoveree WTRU.
  • the second protected discovery solicitation message may be, or may include, the RSC, one or more of the user information for the first relay WTRU, the first protected direct discovery set, and/or the direct discovery solicitation ID.
  • the first WTRU may receive a protected discovery solicitation response message from the discoveree WTRU.
  • the protected discovery solicitation response message may include one or more of the RSC, a second protected direct discovery set, and/or the direct discovery solicitation ID.
  • the first WTRU may determine the source L2 ID of the second relay WTRU, e.g., using the direct discovery solicitation ID.
  • the first WTRU may send a second protected discovery solicitation response message to the second WTRU.
  • the second protected discovery solicitation response message may be, or may include, a second protected direct discovery set.
  • a device such as the first WTRU, may be provided.
  • the first WTRU may be a U2U relay.
  • the first WTRU may include a processor.
  • the processor may be programmed to perform one or more processes.
  • the first WTRU may receive a first protected discovery solicitation message from the remote WTRU.
  • the first protected discovery solicitation message may be, or may include, encrypted remote WTRU user information and WTRU-to-Network (U2N) relay user information within a first protected U2N discovery set.
  • U2N WTRU-to-Network
  • the first WTRU may allocate and/or associate the U2N relay discovery solicitation ID with a remote WTRU source L2 ID that is associated with the remote WTRU.
  • the first WTRU e.g., the U2U relay
  • the second protected discovery solicitation message may be, or may include, the first protected U2N discovery set and/or the U2N relay discovery solicitation ID.
  • the second relay WTRU may receive a first protected discovery solicitation response message.
  • the first protected discovery solicitation response message may include a second protected U2N discovery set and/or the U2N relay discovery solicitation ID.
  • the first WTRU may determine the remote WTRU source L2 ID associated with the remote WTRU, e.g., using the U2N relay discovery solicitation ID.
  • the first WTRU e.g., the U2U relay, may send a second protected discovery solicitation response message to the remote WTRU.
  • the second protected discovery solicitation response message may include the second protected U2N discovery set.
  • a device such as the first WTRU, may be provided.
  • the first WTRU may be a U2N relay.
  • the first WTRU may include a processor.
  • the processor may be programmed to perform one or more processes.
  • the first WTRU may receive a protected discovery solicitation message from a UE-to-UE (U2U) relay.
  • the protected discovery solicitation message may be, or may include, one or more of a U2U relay user information, a first protected U2N discovery set, and/or a U2N relay discovery solicitation ID.
  • the U2N relay discovery solicitation ID may be associated with a U2U relay source L2 ID.
  • the first WTRU may send a protected discovery solicitation response message to the U2U relay.
  • the protected discovery solicitation response message may include a second protected U2N discovery set and/or the U2N relay discovery solicitation ID.
  • a device such as the first WTRU, may be provided.
  • the first WTRU may be a U2N relay.
  • the first WTRU may include a processor.
  • the processor may be programmed to perform one or more processes.
  • the first WTRU may receive a first protected discovery solicitation message from a second U2U relay WTRU.
  • the first protected discovery solicitation message may include one or more of an RSC, a relay indication, U2U relay user information associated with the second U2U relay WTRU, a first protected U2N discovery set, and/or a U2N relay discovery solicitation ID.
  • the U2N relay discovery solicitation ID may be associated with the second U2U relay source L2 ID.
  • the first WTRU may send a second protected discovery solicitation message to a U2N relay WTRU.
  • the second protected discovery solicitation message may include one or more of the RSC, U2U relay user information related to the first U2U relay WTRU, the first protected U2N discovery set, and/or the U2N relay discovery solicitation ID.
  • the first WTRU may receive a protected discovery solicitation response message from the U2N relay WTRU.
  • the protected discovery solicitation response message may include one or more of a second protected U2N discovery set and/or the U2N relay discovery solicitation ID.
  • the first WTRU may determine the source L2 ID of the second U2U relay WTRU using the U2N relay discovery ID.
  • the first WTRU may send a second protected discovery solicitation response message to the second U2U relay WTRU.
  • the second protected discovery solicitation response message may include the second protected U2N discovery set.
  • FIG. 1 A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.
  • FIG. 1 B is a system diagram illustrating an example wireless transmit/receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • WTRU wireless transmit/receive unit
  • FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (ON) that may be used within the communications system illustrated in FIG. 1 A according to an embodiment.
  • RAN radio access network
  • ON core network
  • FIG. 1 D is a system diagram illustrating a further example RAN and a further example ON that may be used within the communications system illustrated in FIG. 1A according to an embodiment.
  • FIG. 2 illustrates an example UE-to-UE (U2U) relay discovery with a Model B using a solicitation identification (ID).
  • U2U UE-to-UE
  • FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented.
  • the communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users.
  • the communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth.
  • the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • ZT UW DTS-s OFDM zero-tail unique-word DFT-Spread OFDM
  • UW-OFDM unique word OFDM
  • FBMC filter bank multicarrier
  • the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104/113, a ON 106/115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and/or network elements.
  • WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment.
  • the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like.
  • UE user equipment
  • PDA personal digital assistant
  • HMD head-mounted display
  • a vehicle a drone
  • the communications systems 100 may also include a base station 114a and/or a base station 114b.
  • Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106/115, the I nternet 110, and/or the other networks 112.
  • the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.
  • 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.
  • BSC base station controller
  • RNC radio network controller
  • 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.
  • the cell associated with the base station 114a may be divided into three sectors.
  • the base station 114a may include three transceivers, i.e. , one for each sector of the cell.
  • the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell.
  • MIMO multiple-input multiple output
  • beamforming may be used to transmit and/or receive signals in desired spatial directions.
  • 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).
  • RAT radio access technology
  • 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.
  • 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 (DL) Packet Access (HSDPA) and/or High-Speed UL Packet Access (HSUPA).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-Advanced (LTE-A) and/or LTE-Advanced Pro (LTE-A Pro).
  • E-UTRA Evolved UMTS Terrestrial Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • LTE-A Pro LTE-Advanced Pro
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).
  • NR New Radio
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies.
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles.
  • DC dual connectivity
  • the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and/or transmissions sent to/from multiple types of base stations (e.g., an eNB and a gNB).
  • the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.
  • IEEE 802.11 i.e., Wireless Fidelity (WiFi)
  • IEEE 802.16 i.e., Worldwide Interoperability for Microwave Access (WiMAX)
  • CDMA2000, CDMA2000 1X, CDMA2000 EV-DO Code Division Multiple Access 2000
  • IS-95 Interim Standard 95
  • IS-856 Interim Standard 856
  • GSM Global System for
  • 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.
  • 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).
  • WLAN wireless local area network
  • 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).
  • the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell.
  • the base station 114b may have a direct connection to the Internet 110.
  • the base station 114b may not be required to access the Internet 110 via the CN 106/115.
  • the RAN 104/113 may be in communication with the CN 106/115, which may be any type of network configured to provide voice, data, applications, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d.
  • the data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like.
  • QoS quality of service
  • the CN 106/115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions, such as user authentication.
  • 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.
  • the CN 106/115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.
  • the CN 106/115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and/or the other networks 112.
  • the PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS).
  • POTS plain old telephone service
  • 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.
  • the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104/113 or a different RAT.
  • Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links).
  • the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.
  • FIG. 1 B is a system diagram illustrating an example WTRU 102.
  • the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and/or other peripherals 138, among others.
  • GPS global positioning system
  • the processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like.
  • the processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment.
  • the processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.
  • 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.
  • the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • 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.
  • the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.
  • the transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122.
  • the WTRU 102 may have multi-mode capabilities.
  • the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and I EEE 802.11 , for example.
  • the processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit).
  • the processor 118 may also output user data to the speaker/microphone 124, the keypad 126, and/or the display/touchpad 128.
  • the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and/or the removable memory 132.
  • the non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • SIM subscriber identity module
  • SD secure digital
  • 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).
  • the processor 118 may receive power from the power source 134 and may be configured to distribute and/or control the power to the other components in the WTRU 102.
  • the power source 134 may be any suitable device for powering the WTRU 102.
  • the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • dry cell batteries e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.
  • solar cells e.g., solar cells, fuel cells, and the like.
  • the processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102.
  • location information e.g., longitude and latitude
  • the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.
  • the processor 118 may further be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and/or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and/or Augmented Reality (VR/AR) device, an activity tracker, and the like.
  • FM frequency modulated
  • the peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • a gyroscope an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and/or a humidity sensor.
  • the WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and/or simultaneous.
  • the full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118).
  • the WRTU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).
  • FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment.
  • the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the RAN 104 may also be in communication with the CN 106.
  • the RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment.
  • the eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116.
  • the eNode-Bs 160a, 160b, 160c may implement MIMO technology.
  • the eNode-B 160a for example, may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.
  • the CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • MME mobility management entity
  • SGW serving gateway
  • PGW packet data network gateway
  • the MME 162 may be connected to each of the eNode-Bs 160a, 160b, 160c in the RAN 104 via an S1 interface and may serve as a control node.
  • 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.
  • the SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface.
  • the SGW 164 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c.
  • the SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.
  • the SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • packet-switched networks such as the Internet 110
  • the CN 106 may facilitate communications with other networks.
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.
  • the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily, or permanently) wired communication interfaces with the communication network.
  • the other network 112 may be a WLAN.
  • a WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP.
  • the AP may have an access or an interface to a Distribution System (DS) or another type of wired/wireless network that carries traffic in to and/or out of the BSS.
  • Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs.
  • Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations.
  • Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA.
  • the traffic between STAs within a BSS may be considered and/or referred to as peer-to- peer traffic.
  • the peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS).
  • the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS).
  • a WLAN using an Independent BSS (I BSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other.
  • the IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.
  • the AP may transmit a beacon on a fixed channel, such as a primary channel.
  • the primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling.
  • the primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP.
  • Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) may be implemented, for example in 802.11 systems.
  • the STAs e.g., every STA, including the AP, may sense the primary channel.
  • High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.
  • VHT STAs may support 20MHz, 40 MHz, 80 MHz, and/or 160 MHz wide channels.
  • the 40 MHz, and/or 80 MHz, channels may be formed by combining contiguous 20 MHz channels.
  • a 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration.
  • the data, after channel encoding may be passed through a segment parser that may divide the data into two streams.
  • Inverse Fast Fourier Transform (IFFT) processing, and time domain processing may be done on each stream separately.
  • IFFT Inverse Fast Fourier Transform
  • the streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA.
  • the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).
  • MAC Medium Access Control
  • Sub 1 GHz modes of operation are supported by 802.11af and 802.11 ah.
  • the channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and 802.11 ac.
  • 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum
  • 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum.
  • 802.11 ah may support Meter Type Control/Machine-Type Communications, such as MTC devices in a macro coverage area.
  • MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and/or limited bandwidths.
  • the MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).
  • WLAN systems which may support multiple channels, and channel bandwidths, such as 802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel.
  • the primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS.
  • the bandwidth of the primary channel may be set and/or limited by a STA, from among all STAs operating in a BSS, which supports the smallest bandwidth operating mode.
  • the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and/or other channel bandwidth operating modes.
  • Carrier sensing and/or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.
  • STAs e.g., MTC type devices
  • NAV Network Allocation Vector
  • the available frequency bands which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.
  • FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment.
  • 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.
  • 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.
  • the gNBs 180a, 180b, 180c may implement MIMO technology.
  • gNBs 180a, 108b may utilize beamforming to transmit signals to and/or receive signals from the gNBs 180a, 180b, 180c.
  • the gNB 180a may use multiple antennas to transmit wireless signals to, and/or receive wireless signals from, the WTRU 102a.
  • the gNBs 180a, 180b, 180c may implement carrier aggregation technology.
  • 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.
  • the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology.
  • WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and/or gNB 180c).
  • CoMP Coordinated Multi-Point
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and/or OFDM subcarrier spacing may vary for different transmissions, different cells, and/or different portions of the wireless transmission spectrum.
  • the WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and/or lasting varying lengths of absolute time).
  • TTIs subframe or transmission time intervals
  • 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.
  • 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).
  • WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point.
  • WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band.
  • WTRUs 102a, 102b, 102c may communicate with/connect to gNBs 180a, 180b, 180c while also communicating with/connecting to another RAN such as eNode-Bs 160a, 160b, 160c.
  • WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously.
  • eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and/or throughput for servicing WTRUs 102a, 102b, 102c.
  • Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and/or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.
  • UPF User Plane Function
  • AMF Access and Mobility Management Function
  • the CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and/or operated by an entity other than the CN operator.
  • SMF Session Management Function
  • the AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node.
  • the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like.
  • Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c.
  • different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and/or the like.
  • URLLC ultra-reliable low latency
  • eMBB enhanced massive mobile broadband
  • MTC machine type communication
  • the AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and/or non-3GPP access technologies such as WiFi.
  • the SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface.
  • the SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface.
  • the SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b.
  • the SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like.
  • a PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.
  • the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.
  • the UPF 184a, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.
  • the CN 115 may facilitate communications with other networks.
  • the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108.
  • IMS IP multimedia subsystem
  • the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and/or wireless networks that are owned and/or operated by other service providers.
  • the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.
  • DN local Data Network
  • one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and/or any other device(s) described herein, may be performed by one or more emulation devices (not shown).
  • the emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein.
  • the emulation devices may be used to test other devices and/or to simulate network and/or WTRU functions.
  • the emulation devices may be designed to implement one or more tests of other devices in a lab environment and/or in an operator network environment.
  • the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and/or deployed as part of a wired and/or wireless communication network in order to test other devices within the communication network.
  • the one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation device may be directly coupled to another device for purposes of testing and/or may perform testing using over-the-air wireless communications.
  • the one or more emulation devices may perform the one or more, including all, functions while not being implemented/deployed as part of a wired and/or wireless communication network.
  • the emulation devices may be utilized in a testing scenario in a testing laboratory and/or a non-deployed (e.g., testing) wired and/or wireless communication network in order to implement testing of one or more components.
  • the one or more emulation devices may be testing equipment. Direct RF coupling and/or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and/or receive data.
  • RF circuitry e.g., which may include one or more antennas
  • Reference to a timer herein may refer to a time, a time period, a tracking of time, a tracking of a period of time, a combination thereof, and/or the like.
  • Reference to a timer expiration herein may refer to determining that the time has occurred or that the period of time has expired.
  • a relay WTRU may be in direct proximity to a discoverer WTRU.
  • the relay WTRU may include a processor.
  • the processor may be configured to perform one or more of the following.
  • the relay WTRU may receive a first protected discovery solicitation message from the discoverer WTRU.
  • the first protected discovery solicitation message may include a first protected direct discovery set.
  • the first protected direct discovery set may include encrypted discoverer user information and discoveree user information.
  • the relay WTRU may allocate a direct discovery solicitation identification (ID) and may be associated the direct discovery solicitation ID with a discoverer source Layer 2 (L2) ID.
  • the WTRU source L2 ID may be associated with the second WTRU.
  • the relay WTRU may send a second protected discovery solicitation message to a relay WTRU.
  • the second protected discovery solicitation message may include the first protected direct discovery set and the direct discovery solicitation ID.
  • a first protected discovery solicitation response message may be received from the relay WTRU.
  • the first protected discovery solicitation response message may include a second protected direct discovery set and the direct discovery solicitation ID.
  • the relay WTRU may determine the discoverer source L2 ID associated with the discoverer WTRU using the direct discovery solicitation ID.
  • the relay WTRU may send a second protected discovery solicitation response message to the discoverer WTRU.
  • the second protected discovery solicitation response message may include the second protected direct discovery set.
  • the source L2 ID may be a first source L2 ID.
  • the allocation of the direct discovery solicitation ID by the processor may involve associating the direct discovery solicitation ID with a second source L2 ID.
  • the first WTRU may include a processor that is configured to perform one or more of the following.
  • the first WTRU may receive a protected discovery solicitation message from the second WTRU.
  • the protected discovery solicitation message may include relay user information, a direct discovery solicitation ID, and/or a first protected direct discovery set.
  • the first protected direct discovery set may include encrypted discoverer user information and/or encrypted discoveree user information.
  • the direct discovery solicitation ID may be associated with a relay source Layer 2 (L2) ID.
  • L2 relay source Layer 2
  • the first WTRU may send a protected discovery solicitation response message to the second WTRU.
  • the protected discovery solicitation response message may include a second protected direct discovery set and the discovery solicitation ID.
  • a first WTRU which may be an intermediate relay WTRU, may be provided.
  • the first WTRU may include a processor that is programmed to perform one or more processes.
  • the first WTRU may receive a first protected discovery solicitation message from a second relay WTRU.
  • the first protected discovery solicitation message may include one or more of a Relay Service Code indication, user information for the second relay WTRU, a first protected direct discovery set, and/or a direct discovery solicitation Identifier (ID).
  • the direct discovery solicitation ID may be associated with the source Layer 2 (L2) ID of the second relay WTRU.
  • the first WTRU may send a second protected discovery solicitation message to a discoveree WTRU.
  • the second protected discovery solicitation message may include the RSC, one or more of the user information for the first relay WTRU, the first protected direct discovery set, and/or the direct discovery solicitation ID.
  • the first WTRU may receive a protected discovery solicitation response message from the discoveree WTRU.
  • the protected discovery solicitation response message may include one or more of the RSC, a second protected direct discovery set, and/or the direct discovery solicitation ID.
  • the first WTRU may determine the source L2 ID of the second relay WTRU using the direct discovery solicitation ID.
  • the first WTRU may send a second protected discovery solicitation response message to the second WTRU.
  • the second protected discovery solicitation response message may include a second protected direct discovery set.
  • the second WTRU is provisioned with a Relay Service Code (RSC) with an associated indicator for multi-hop support.
  • RSC Relay Service Code
  • the first protected direct discovery set may be, or may include, encrypted discoverer user information and/or encrypted discoveree user information.
  • a first WTRU which may be a U2U relay, may be provided.
  • the first WTRU may include a processor that is configured to perform one or more processes.
  • the first WTRU may receive a first protected discovery solicitation message from the remote WTRU.
  • the first protected discovery solicitation message may include encrypted remote WTRU user information and/or WTRU-to-Network (U2N) relay user information within a first protected U2N discovery set.
  • the first WTRU may allocate the U2N relay discovery solicitation identification (ID) and associate the U2N relay discovery solicitation ID with a remote WTRU source Layer 2 (L2) ID that is associated with the remote WTRU.
  • ID U2N relay discovery solicitation identification
  • L2L2 ID remote WTRU source Layer 2
  • the first WTRU may send a second protected discovery solicitation message to a second relay WTRU.
  • the second protected discovery solicitation message may include the first protected U2N discovery set and/or the U2N relay discovery solicitation ID.
  • the first WTRU may receive a first protected discovery solicitation response message from the second relay WTRU.
  • the first protected discovery solicitation response message may include a second protected U2N discovery set and/or the U2N relay discovery solicitation ID.
  • the first WTRU may determine the remote WTRU source L2 ID associated with the remote WTRU using the U2N relay discovery solicitation ID.
  • the first WTRU may send a second protected discovery solicitation response message to the remote WTRU.
  • the second protected discovery solicitation response message may include the second protected U2N discovery set.
  • a first WTRU which may be a U2N relay, may be provided.
  • the first WTRU may include a processor that is configured to perform one or more processes.
  • the first WTRU may receive a protected discovery solicitation message from a UE-to-UE (U2U) relay.
  • the protected discovery solicitation message may include one or more of a U2U relay user information, a first protected U2N discovery set, and/or a U2N relay discovery solicitation identification (ID).
  • the first WTRU may associate the U2N relay discovery solicitation ID with a U2U relay source Layer 2 (L2) ID.
  • L2U U2U relay source Layer 2
  • the first WTRU may send a protected discovery solicitation response message to the U2U relay.
  • the protected discovery solicitation response message may include a second protected U2N discovery set and the U2N relay discovery solicitation ID.
  • the first protected U2N discovery set may include a U2N Relay Service Code (RSC), encrypted remote WTRU user information, and/or U2N relay user information.
  • RSS U2N Relay Service Code
  • a first WTRU which may be a U2U relay, may be provided.
  • the first WTRU may include a processor that is programmed to perform one or more processes.
  • the first WTRU may receive a first protected discovery solicitation message from a second U2U relay WTRU.
  • the first protected discovery solicitation message may include one or more of a U2U Relay Service Code (U2U_RSC), a relay indication, U2U relay user information associated with the second U2U relay WTRU, a first protected UE- to-Network (U2N) discovery set, and a U2N relay discovery solicitation identification (ID).
  • U2U_RSC U2U Relay Service Code
  • U2N first protected UE- to-Network
  • ID U2N relay discovery solicitation identification
  • the first WTRU may associate the U2N relay discovery solicitation ID with the second U2U relay source Layer 2 (L2) ID. Based on the relay indication and/or an indication for multi-hop support associated with the U2U_RSC, the first WTRU may send a second protected discovery solicitation message to a U2N relay WTRU.
  • the second protected discovery solicitation message may include one or more of the U2U relay user information related to the first U2U relay WTRU, the first protected U2N discovery set, and/or the U2N relay discovery solicitation ID.
  • the first WTRU may receive a protected discovery solicitation response message from the U2N relay WTRU.
  • the protected discovery solicitation response message may include one or more of a second protected U2N discovery set and the U2N relay discovery solicitation ID.
  • the first WTRU may determine the source L2 ID of the second U2U relay using the U2N relay discovery ID.
  • the first WTRU may send a second protected discovery solicitation response message to the second U2U relay WTRU.
  • the second protected discovery solicitation response message may include the second protected U2N discovery set.
  • the first U2U relay is provisioned with a U2U Relay Service Code (U2U_RSC) with an associated indication for multi-hop support.
  • U2U_RSC U2U Relay Service Code
  • the first protected UE-to-Network (U2N) discovery set may include one or more of U2N_RSC, encrypted remote WTRU user information, and/or U2N relay user information.
  • wireless transmit/receive unit WTRU
  • AUSF Authentication Server Function
  • DCR/DCA Direct Connection Request/Accept
  • DDNMF Direct Discovery Name Management Function
  • DUCK Discovery User Confidentiality Key
  • DUIK Discovery User Integrity Key
  • DUSK Discovery User Scrambling Key
  • KNRP Key NR Prose
  • KNRP Key NR Prose
  • MIC Key NR Prose
  • PCF Policy Control Function
  • PMF ProSe Key Management Function
  • PRUK Prose remote User Key
  • RSC Relay Service Code
  • U2N relay UE-to-Network Relay
  • U2N_RSC RSC offered by U2N relay
  • U2U_RSC UE-to-UE Relay
  • U2U_RSC User Plane PRUK
  • UTC Universal Time Coordinated
  • U2U relay Discovery Security Model B using a random discovery solicitation ID (e.g., Single and Multi-Hop) may be provided.
  • One or more U2U relays may employ a random solicitation ID associated with a discoverer WTRU upon receiving a discovery solicitation message. This may be done to determine which discoverer WTRU to send the discovery solicitation response message from a discoveree WTRU.
  • a U2U relay is in proximity (e.g., direct proximity) to a discoverer WTRU (e.g., either single-hop or multi-hop), the U2U relay may perform one or more procedures.
  • the U2U relay may receive a message, e.g., a protected discovery solicitation message, from the discoverer WTRU.
  • the protected discovery solicitation message may include a protected direct discovery set (e.g., a first protected direct discovery set).
  • a discovery solicitation ID (e.g., a direct discovery solicitation ID) may be allocated and may be associated with the source L2 ID of the discoverer.
  • a protected discovery solicitation message (e.g., a new protected discovery solicitation message) may be sent to a discoveree WTRU/U2U relay.
  • the protected discovery solicitation message (e.g., the new protected discovery solicitation message) may include the first protected direct discovery set and/or the direct discovery solicitation ID.
  • the source L2 ID of the discoverer WTRU may be located, e.g., using the direct discovery solicitation ID.
  • the protected discovery solicitation response message may be, or may include, a second protected direct discovery set and/or the direct discovery solicitation ID.
  • a protected discovery solicitation response message (e.g., a new protected discovery solicitation response message) may be sent to the discoverer WTRU.
  • the protected discovery solicitation response message (e.g., the new protected discovery solicitation response message) may include the second protected direct discovery set.
  • the discoveree WTRU may receive a protected discovery solicitation message from a U2U relay.
  • the message may include one or more of U2U relay user information, a first protected direct discovery set, and/or a direct discovery solicitation ID.
  • the discoveree WTRU may associate the direct discovery solicitation ID with the U2U relay source L2 ID and send a protected discovery solicitation response message (e.g., a new protected discovery solicitation response message) to the U2U relay.
  • the discovery solicitation response message may include a second protected direct discovery set and/or the discovery solicitation ID.
  • a U2U relay which may be an intermediate U2U relay, may be configured for use in a multi-hop scenario.
  • the U2U relay may be provisioned with an RSC with an associated indication for multi-hop support.
  • the U2U relay may receive a protected discovery solicitation message from a second U2U relay.
  • the message may include an RSC, a relay indication, a second U2U relay user information, a first protected direct discovery set, and/or a direct discovery solicitation ID.
  • the U2U relay may associate the direct discovery solicitation ID with the second U2U relay source L2 ID.
  • the U2U relay may send a protected discovery solicitation message (e.g., a new protected discovery solicitation message) to a discoveree WTRU.
  • the protected discovery solicitation message (e.g., the new protected discovery solicitation message) may include the RSC, one or more of its own U2U relay user information, the first protected direct discovery set, and/or the discovery solicitation ID (e.g., direct discovery solicitation ID).
  • the U2U relay may receive a protected discovery solicitation response message from the discoveree WTRU.
  • the protected discovery solicitation response message may include the RSC, one or more of a second protected direct discovery set, and/or the direct discovery solicitation ID.
  • the U2U relay may locate the source L2 ID of the U2U relay using the direct discovery solicitation ID.
  • the U2U relay may transmit a protected discovery solicitation response message (e.g., a new protected discovery solicitation response message) to the discoverer WTRU.
  • the protected discovery solicitation response message (e.g., the new protected discovery solicitation response message) may include the second protected direct discovery set.
  • U2N procedures for discovery and communication may be provided and may include security and privacy.
  • a U2N relay direct discovery using Model A or B may be supported.
  • the U2N relay may send one or more announcement discovery messages to be discovered by a remote WTRU in proximity.
  • the remote WTUR may act as a discoverer and may send a solicitation discovery message to which the U2N relay (e.g., discoveree) may reply with a corresponding response message.
  • One or more discovery security parameters may be associated with the U2N relay Service Code (RSC).
  • the one or more discovery security parameters may be provisioned in the remote WTRU and/or U2N relay.
  • the one or more discovery security parameters may be used to protect one or more discovery messages and/or some sensitive parameters in a DCR message (e.g., RSC).
  • the remote WTRU/relay may be provided with one or more security parameters, e.g., by a Direct Discovery Name Management Function (DDNMF), a Policy Control Function (PCF), and/or a ProSe Key Management Function (PKMF).
  • DDNMF Direct Discovery Name Management Function
  • PCF Policy Control Function
  • PKMF ProSe Key Management Function
  • U2N relay direct communication may support one or more User Plane (UP) and/or Control Plane (CP) based security mechanisms.
  • a root credential may be provisioned and/or generated.
  • the root credential may be called a ProSe remote User Key (PRUK).
  • a remote WTRU may establish a root credential (e.g., CP-PRUK) with a remote WTRU home public land mobile network (HPLMN) (e.g., authentication server function (AUSF)/ unified data management (UDM)/ prose anchor function (PAnF)/ and/or the like).
  • HPLMN public land mobile network
  • AUSF authentication server function
  • UDM unified data management
  • PAnF prose anchor function
  • a remote WTRU may establish a root credential during an authentication procedure (e.g., ProSe authentication procedure) as part of protocol establishment (e.g., PC5 link establishment) with the U2N relay.
  • the authentication may request that one or more credentials are stored in the remote WTRU universal integrated circuit card (UICC).
  • UICC universal integrated circuit card
  • a remote WTRU may be configured by its PKMF with a root credential (e.g., UP-PRUK).
  • UP-PRUK may also be generated as part of a link establishment (e.g., PC5 link establishment) with the U2N relay using a mechanism, such as a GBA-PUSH mechanism, using one or more credentials, e.g., which may be stored in the remote WTRU UICC.
  • the PRUK may be used to establish a link root key (e.g., a PC5 link root key) KNRP shared between the remote WTRU and the U2N relay.
  • the PRUK may be used to derive one or more sessions and/or security keys.
  • the remote WTRU may derive KNRP from the PRUK, e.g., while the U2N relay receives KNRP from the network (e.g., PKMF or AMF).
  • the network e.g., PKMF or AMF
  • the RSC and PRUK ID may be sent protected in the DCR for confidentiality and/or integrity as described herein.
  • the relay device e.g., the relay WTRU
  • a privacy protection mechanism may be used for a U2U relay if receiving a DCR from an end WTRU.
  • U2U relay discovery security may be provided.
  • U2U procedures for discovery and communication which may include security and privacy, may be provided.
  • Model A and B of discovery may be supported.
  • the UE-to-UE relay may send one or more U2U relay Announcement messages.
  • the one or more U2U relay announcement messages may include information about one or more end WTRUs (e.g., one or more end UEs, which may be known as direct discovery set and may include user information and/or ProSe service code) that were previously discovered or connected to the relay.
  • the UE-to-UE relay may retransmit the direct discovery set included in one or more U2U relay discovery solicitation and/or response messages.
  • One or more discovery messages may be protected using one or more key sets, such as two separate key sets.
  • a first key set may be associated with the RSC offered by the U2U relay and used to protect the U2U relay discovery message (e.g., Announcement, Solicitation, and/or the like).
  • a second key set may be associated with the ProSe service used by the one or more end WTRUs (e.g., the one or more end UEs).
  • One or more discovery messages and/or direct discovery sets may be protected for confidentiality, integrity, and/or against replay. Replay protection may be done based on a UTC time-based counter.
  • Multi-hop for U2N and U2U relay may be provided.
  • Multi-hop for U2N relay may enable a remote WTRU to discover and communicate with a U2N relay via one or more U2U relays.
  • Multi-hop U2U relay may enable one or more WTRUs (e.g., one or more end UEs) to discover and communicate with each other via more than one U2U relay.
  • the multi-hop capability may be useful for one or more mission-critical communications (e.g., first responders) and may enhance coverage (e.g., indoor).
  • mission-critical communications e.g., first responders
  • enhance coverage e.g., indoor
  • the user information ID of the discoverer end WTRU and discoveree end WTRU may be encrypted end-to-end, e.g., using a key set associated with a service (e.g., a ProSe service) inside a protected direct discovery set included on the one or more U2U relay discovery (e.g., solicitation and/or response) messages.
  • a service e.g., a ProSe service
  • a protected direct discovery set included on the one or more U2U relay discovery e.g., solicitation and/or response
  • the U2U relay may not be provisioned with the key set associated with the ProSe service and may not be able to decrypt the user information IDs inside the direct discovery set within the relay discovery message.
  • the U2U relay may (e.g., only) forward transparently the protected direct discovery set (e.g., with encrypted discoverer and/or discoveree User information) received in the discovery message.
  • the discoverer user information received relay discovery solicitation response message may be encrypted.
  • the Relay may be unable to determine to which discoverer WTRU to send the discovery solicitation response message. This may be addressed for Multi-hop U2U relay with model B discovery (e.g., 2 end UEs using 2 or more U2U relay for discovering each other).
  • the remote WTRU may play the role of a discoverer.
  • the U2N relay may play the role of a discoveree.
  • the U2N relay service (e.g., with its RSC) may be used instead of and/or in addition to a ProSe service.
  • Embodiments disclosed herein may provide for the U2U relay to be able to determine to which discoverer end WTRU to send a discovery solicitation response message upon receiving a discovery solicitation response message from a discoveree end WTRU.
  • Embodiments disclosed herein may secure and preserve the privacy of the discoverer/discoveree against unauthorized parties as per existing security requirements (e.g., maintain an end-to-end (E2E) direct discovery set confidentiality protection).
  • E2E end-to-end
  • Embodiments disclosed herein allow the support of multi-hop relaying scenarios (e.g., multi-hop between end-to-end WTRUs or between a remote WTRU and U2N relay).
  • multi-hop relaying scenarios e.g., multi-hop between end-to-end WTRUs or between a remote WTRU and U2N relay.
  • a U2U relay may use a discovery solicitation ID to forward the discovery solicitation response to an appropriate discoverer in a U2U relay discovery Model B procedure.
  • a principle of E2E security and confidentiality of the direct discovery set within the discovery message may be preserved.
  • a U2N relay may establish a secure DCR Security ID (DSID) with an authorized remote WTRU during the discovery procedure.
  • the U2N relay may locate one or more discovery security keys to decrypt the RSC and/or the PRUK ID in the DCR using the DSID included in the DCR.
  • the privacy of the RSC and/or the PRUK ID may be preserved and have negligible processing overhead on both the relay and the remote WTRU.
  • U2U relay Discovery Security Model B using a random discovery solicitation ID (e.g., single and/or multi-Hop) may be provided.
  • FIG. 2 illustrates an example U2U relay discovery with Model B using a solicitation ID.
  • One or more processes illustrated in FIG. 2 may or may not be performed (e.g., skipped).
  • a solicitation ID may be assigned to a discoverer upon receiving a protected discovery solicitation message.
  • the solicitation ID may be used to determine to which discoverer to send a protected discovery solicitation response message upon receiving such a message from a discoveree.
  • FIG. 2 may show a U2U relay discovery procedure in a single hop scenario.
  • the end WTRUs and U2U relay may be provisioned with one or more U2U relay discovery parameters, e.g., including the security material associated with the Relay Service Code (RSC).
  • the end WTRU e.g., the UEs
  • the end WTRU may be provisioned with the one or more discovery parameters, e.g., including the security material associated with the ProSe Service.
  • the discoverer may generate a discovery solicitation message.
  • the discovery solicitation message may include a protected direct discovery set (e.g., including the discoverer and/or the target discoveree user information).
  • the discoverer may protect the discovery solicitation message with the security material associated with RSC.
  • the discoverer may send the message to the U2U relay, e.g., using a self-assigned source L2 ID.
  • the U2U relay may verify the security of the message using the security material associated with RSC. If the check is successful (e.g., the security of the message has not been compromised), the U2U relay may allocate a direct discovery solicitation ID and may associate the direct discovery solicitation ID with the discoverer source L2 ID. The U2U relay may ensure that the direct discovery solicitation ID may be unique (e.g., locally unique and/or different from other ongoing solicitation discovery) to identify unambiguously the discoverer at the U2U relay.
  • the U2U relay may be used for the solicitation ID any of a random number, the source L2 ID of the discoverer, the Query Code (e.g., inside the direct discovery set) from discoverer, and/or a transformation function thereof (e.g., using a hash function).
  • the U2U relay may generate a discovery solicitation message (e.g., a new discovery solicitation message).
  • the discovery solicitation message may include the protected direct discovery set received from the discoverer and the direct discovery solicitation ID.
  • the U2U relay may protect the discovery solicitation message with the security material associated with RSC and send the message to the discoveree.
  • the U2U relay may associate the direct discovery solicitation ID with the U2U relay's source L2 ID used to send the discovery solicitation message over the next hop.
  • the U2U relay's source L2 ID used to send the discovery solicitation message may be derived using the direct discovery solicitation ID.
  • the discoveree may verify the security of the message using the security material associated with RSC. If the check is successful (e.g., the security of the message has not been compromised), the discoveree may verify the security of the included direct discovery set and may decrypt its content (e.g., the user information of the discoverer and discoveree). If the check is successful, the discoveree may check that the received discoverer user information matches its own configured user information. If there is a match, the discoveree may generate a discovery solicitation response message that includes a protected direct discovery set (e.g., the discoverer and/or the target discoveree user information) and the direct discovery solicitation ID. The discoveree may protect the discovery solicitation response message with the security material associated with RSC and send the message to the U2U relay.
  • a protected direct discovery set e.g., the discoverer and/or the target discoveree user information
  • the U2U relay may verify the security of the message using the security material associated with RSC. If the check is successful, the U2U relay may locate the discoverer source L2 ID based on the received direct discovery solicitation ID (e.g., based on the mapping established at 3 or 4 illustrated in FIG. 2 and/or as described herein). The U2U relay may generate a discovery solicitation response message (e.g., a new discovery solicitation response message) that includes the protected direct discovery set received from the discoveree. The U2U relay may protect the discovery solicitation response message with the security material associated with RSC and may send the message to the discoverer.
  • a discovery solicitation response message e.g., a new discovery solicitation response message
  • the behavior of the first U2U relay e.g., the direct U2U relay
  • the behavior of an intermediate U2U relay e.g., in the discovery path between the direct U2U relay and the discoveree
  • the U2U relays and the end WTRUs may be provisioned with an RSC with an associated indication for multi-hop support.
  • the discoverer may include a relay indication in a discovery solicitation message to indicate that the discoverer wishes to perform U2U relay discovery across more than one U2U relay.
  • An indication of the maximum number of hops allowed for the discovery may be included in the discovery message (e.g., the discovery solicitation message).
  • an indication may be configured as part of the authorization policy provisioned in the WTRUs and Relay (e.g., an indicator associated with the RSC).
  • An indication of the number of hops (e.g., current number of hops) may be included in the discovery solicitation message and used by the relay to verify whether to include a relay indication in the discovery solicitation message (e.g., to prevent further relaying).
  • the direct U2U relay may send the discovery message to the intermediate U2U relay.
  • the intermediate U2U relay (e.g., in addition to and/or instead of the discoveree) may receive and process the discovery message similarly to how it may be described herein for the direct U2U relay.
  • the U2U may decide to proceed with the multi-hop U2U relay discovery and associate the direct discovery solicitation ID with the direct U2U relay source L2 ID.
  • the discoveree WTRU may receive from the intermediate U2U relay (e.g., in addition to and/or instead of a direct Relay) the protected discovery solicitation message (e.g., the new protected discovery solicitation message), including intermediate U2U relay user information, the protected direct discovery set, and/or the direct discovery solicitation ID from the direct U2U relay.
  • the intermediate U2U relay may include a second direct discovery solicitation ID in the message.
  • the intermediate U2U may allocate the second direct discovery solicitation ID (e.g., to be locally unique) and associate the second direct discovery solicitation ID with one or more of the sources’ L2 ID and direct discovery solicitation ID of the direct U2U relay.
  • the intermediate U2U relay may receive a protected discovery solicitation response message from the discoveree WTRU.
  • the protected discovery solicitation response message may include a second protected direct discovery set, and/or the direct discovery solicitation ID.
  • the intermediate U2U relay may check the discovery solicitation response message security. If the security check is successful, the intermediate U2U relay may locate the source L2 ID of the direct U2U relay using direct discovery solicitation ID.
  • the direct U2U relay may receive a protected discovery solicitation response message from the intermediate U2U relay (e.g., in addition to and/or instead of the discoveree WTRU)
  • Examples of computer- readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as compact disc (CD)-ROM disks, and/or digital versatile disks (DVDs).
  • ROM read only memory
  • RAM random access memory
  • register cache memory
  • semiconductor memory devices magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and/or optical media such as compact disc (CD)-ROM disks, and/or digital versatile disks (DVDs).
  • CD compact disc
  • DVDs digital versatile disks
  • a processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and/or any host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes, des procédés et un appareil de découverte de relais et/ou d'améliorations de sécurité de communication. Une première unité d'émission/réception sans fil (WTRU) peut recevoir un premier message de sollicitation de découverte protégé en provenance de la seconde WTRU. Le premier message de sollicitation de découverte protégé peut comprendre un premier ensemble de découverte directe protégé. Le premier ensemble de découverte directe protégé peut comprendre des informations d'utilisateur d'élément de découverte et d'élément découvert chiffrées. La première WTRU peut attribuer une identification de sollicitation de découverte directe (ID) et associer l'ID de sollicitation de découverte directe à un ID de couche 2 (L2) de source de WTRU. La première WTRU peut envoyer un deuxième message de sollicitation de découverte protégé à une troisième WTRU. Le second message de sollicitation de découverte protégé peut comprendre le premier ensemble de découverte directe protégé et l'ID de sollicitation de découverte directe. La première WTRU peut recevoir un premier message de réponse de sollicitation de découverte protégé en provenance de la troisième WTRU et envoyer un second message de réponse de sollicitation de découverte protégé à la seconde WTRU.
PCT/US2024/049367 2023-10-05 2024-10-01 Découverte de relais et améliorations de sécurité de communication Pending WO2025075939A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202363542714P 2023-10-05 2023-10-05
US63/542,714 2023-10-05

Publications (1)

Publication Number Publication Date
WO2025075939A1 true WO2025075939A1 (fr) 2025-04-10

Family

ID=93214766

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/049367 Pending WO2025075939A1 (fr) 2023-10-05 2024-10-01 Découverte de relais et améliorations de sécurité de communication

Country Status (1)

Country Link
WO (1) WO2025075939A1 (fr)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security aspects of Proximity based Services (ProSe) in the 5G System (5GS) (Release 18)", 12 September 2023 (2023-09-12), XP052517288, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG3_Security/TSGS3_112_Goteborg/SA-101/33503-i00.docx> [retrieved on 20230912] *
JUNG JE SON ET AL: "[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects", vol. SA WG2, no. Chicago, US; 20231113 - 20231117, 3 November 2023 (2023-11-03), XP052538147, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160_Chicago_2023-11/Docs/S2-2312055.zip S2-2312055 LS_Response_relating_to_SecurityU2URelayDiscovery_toCT1SA3.docx> [retrieved on 20231103] *
JUNG JE SON ET AL: "Correction on 5G ProSe UE-to-UE relay discovery with security aspects", vol. SA WG2, no. Chicago, US; 20231113 - 20231117, 3 November 2023 (2023-11-03), XP052538148, Retrieved from the Internet <URL:https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_160_Chicago_2023-11/Docs/S2-2312056.zip S2-2312056 CRrelatingtoU2URelayDiscovery.docx> [retrieved on 20231103] *

Similar Documents

Publication Publication Date Title
US20240314534A1 (en) Discovery of internet of things network
US11159937B2 (en) Terminal requesting network slice capabilites from non-3GPP access network
EP3912373B1 (fr) Procédures permettant une communication en monodiffusion v2x sur une interface pc5
US20250350932A1 (en) Security and privacy support for direct wireless communications
EP4275286B1 (fr) Changement d&#39;identifiants de liaison pc5 entre la wtru et le relais wrtu-wrtu de couche 2
US20240340766A1 (en) Wtru-to-network relay associated with mint
US20250220425A1 (en) Pdu session secondary and slice-specific authentication and authorization using l3 wtru-to-network relay
WO2025029504A1 (fr) Procédés de découverte de relais wtru-réseau à sauts multiples au moyen d&#39;un ensemble de découverte de relais avec comptage de sauts
US20230254690A1 (en) U2n relay (up) pc5 link setup security when using gba push
US20250184857A1 (en) Route selection in a wireless communication system
US20250142334A1 (en) Customer premises network access control
US12212957B2 (en) Methods and apparatus for WTRU-to-WTRU relay discovery security and privacy
WO2025075939A1 (fr) Découverte de relais et améliorations de sécurité de communication
WO2025075941A1 (fr) Traitement de protection de message de dcr par un relais u2n à l&#39;aide d&#39;un id de sécurité de dcr
WO2024211895A1 (fr) Systèmes et procédés d&#39;établissement de sécurité entre une unité d&#39;émission-réception sans fil cible (wtru) et une wtru relais u2u
WO2024211891A1 (fr) Systèmes et procédés de détection d&#39;état de relais u2u sans découverte autonome
WO2024211885A1 (fr) Systèmes et procédés de détection d&#39;état de relais u2u pendant une découverte
WO2024211179A1 (fr) Planification d&#39;annonce de découverte de relais wtru à wtru
WO2025075782A1 (fr) Découverte et utilisation d&#39;un nœud intermédiaire pour les dispositifs ambiants
WO2025212905A1 (fr) Identification d&#39;un profil d&#39;utilisateur et connexion à celui-ci
WO2024026082A1 (fr) Procédé et appareil d&#39;activation de communication n3gpp entre une wtru distante et une wtru relais
WO2025072897A1 (fr) Demande de resélection de relais indiquant un support de relais à sauts multiples
WO2025175201A1 (fr) Procédés d&#39;authentification d&#39;utilisateur dans des systèmes sans fil associés à des utilisateurs derrière une passerelle rg ou passerelle
WO2024044186A1 (fr) Autorisation d&#39;unité de transmission/réception sans fil en itinérance pour des applications périphériques
WO2025019314A1 (fr) Négociation sur une puissance de batterie suffisante dans un ido

Legal Events

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

Ref document number: 24794544

Country of ref document: EP

Kind code of ref document: A1