Methods, architectures, apparatuses, and systems for user equipment (UE) to UE relay discovery using mobile ad hoc networks.

By configuring the relay service code (RSC) for the WTRU, UE-to-UE relay discovery and connection are achieved, solving the problem of low efficiency in UE-to-UE relay discovery in 5G ProSe technology and improving the coverage and communication capabilities of the wireless network.

CN123125955APending Publication Date: 2026-11-17INTERDIGITAL PATENT HOLDINGS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580025881.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-04-04
Filing Date
2025-04-03
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing 5G ProSe technology suffers from inefficiency and limited coverage in relay discovery and communication between user equipment (UE), especially in wireless networks where it is difficult to effectively discover and establish UE-to-UE relay connections.

Method used

By configuring a Relay Service Code (RSC) for the Radio Transmit/Receive Unit (WTRU), mobile ad hoc network relay services between WTRUs are implemented, including receiving and sending relay request and response messages to discover and select flooded multipoint relays (MPRs), and using the RSC to establish UE-to-UE relay connections.

Benefits of technology

It improves the efficiency and coverage of relay discovery between UEs, enhances the communication capabilities of the wireless network, supports multi-hop relay connections, and improves the flexibility and reliability of the network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125955A_ABST
    Figure CN123125955A_ABST
Patent Text Reader

Abstract

This describes the processes, methods, architectures, apparatuses, systems, devices, and computer program products for User Equipment (UE) to UE relay discovery in a Mobile Ad Hoc Network (MANET). One method may include: a WTRU to WTRU relay joining the MANET based on a configured Relay Service Code (RSC); receiving a first relay request message from a first WTRU to discover a second WTRU; sending a second relay request message to one or more WTRUs in the vicinity of the WTRU to WTRU relay; sending information associated with the first relay request message to other WTRU to WTRU relays within one hop of the WTRU to WTRU relay; receiving a first relay response message from the second WTRU; and sending the second relay response message to the first WTRU.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications This application claims the benefit of U.S. Provisional Patent Application No. 63 / 574440, filed April 4, 2024. The contents of the earlier application are incorporated herein by reference in their entirety. Technical Field

[0002] The example embodiments described in this disclosure generally relate to the fields of communications, software, and coding, including, for example, methods, architectures, apparatuses, and systems related to user equipment (UE) to UE relay discovery. Background Technology

[0003] 5G New Radio (NR) ProSe enables communication between user equipment or devices within a certain proximity range. 5G ProSe defines several features and / or procedures, such as 5G ProSe direct discovery, 5G ProSe direct communication, 5G ProSe UE-to-Network Relay, and 5G ProSe UE-to-UE Relay. Summary of the Invention

[0004] One embodiment may be directed to a Wireless Transmit / Receive Unit (WTRU), which may be or can act as a WTRU-WTRU relay. The WTRU may include circuitry, including any one of a processor and a transceiver. The WTRU and / or circuitry may be configured to receive configuration information indicating a Relay Service Code (RSC) associated with a Mobile Ad Hoc Network (MANR), to join or connect to the MANR based on the Relay Service Code (RSC), and to receive a first relay request message from a first WTRU to discover a second WTRU. The first relay request message includes any one of user information associated with the first WTRU, user information associated with the second WTRU, and the Relay Service Code (RSC). The WTRU-WTRU relay is selected as a flooding multipoint relay (MPR). The WTRU and / or circuitry may be configured to transmit a second relay request message intended for delivery to any WTRU within the vicinity of the WTRU-WTRU relay and / or to other WTRU-WTRU relays within one hop of the WTRU-WTRU relay. The second relay request message includes a forwarding instruction associated with the mobile ad hoc network and any one of the following: user information associated with the first WTRU, user information associated with the second WTRU, user information associated with a WTRU-to-WTRU relay, and / or a relay service code (RSC). The WTRU and / or circuit can be configured to receive a first relay response message, which includes any one of the following: user information associated with the first WTRU, user information associated with the second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with the WTRU-to-WTRU relay from which the relay response message is received, and / or a relay service code (RSC). The WTRU and / or circuit can be configured to send a second relay response message to the first WTRU. The second relay response message includes any one of the following: user information associated with the first WTRU, user information associated with the second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with the WTRU-to-WTRU relay from which the relay response message is received, and / or a relay service code (RSC).

[0005] One embodiment relates to a method implemented by a Wireless Transmit / Receive Unit (WTRU) that can be or may act as a WTRU-WTRU relay. The method may include receiving configuration information indicating a Relay Service Code (RSC) associated with a Mobile Ad Hoc Network (MANR), joining or connecting to the MANR based on the RSC, and receiving a first relay request message from a first WTRU to discover a second WTRU. The first relay request message includes any one of user information associated with the first WTRU, user information associated with the second WTRU, and the Relay Service Code (RSC). The WTRU-WTRU relay may be selected as a flooding multipoint relay (MPR). The method includes sending a second relay request message intended for delivery to any WTRU within the vicinity of the WTRU-WTRU relay and / or other WTRU-WTRU relays within one hop of the WTRU-WTRU relay. The second relay request message includes a forwarding instruction associated with a mobile ad hoc network and any one of the following: user information associated with a first WTRU, user information associated with a second WTRU, user information associated with a WTRU-to-WTRU relay, and / or a relay service code (RSC). The method includes receiving a first relay response message, which includes any one of the following: user information associated with a first WTRU, user information associated with a second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with a WTRU-to-WTRU relay from which the relay response message was received, and / or a relay service code (RSC). The method includes sending a second relay response message to the first WTRU. The second relay response message includes any one of the following: user information associated with a first WTRU, user information associated with a second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with a WTRU-to-WTRU relay from which the relay response message was received, and / or a relay service code (RSC). Attached Figure Description

[0006] A more detailed understanding can be obtained by referring to the following detailed description, which is given by way of example in conjunction with the accompanying drawings. Similar to the detailed description, the figures in these drawings are illustrative. Therefore, the figures (FIGs.) and detailed description should not be considered limiting, and other equally valid examples are possible and likely. Furthermore, similar reference numerals (“ref.”) in the figures indicate similar elements, and wherein: Figure 1A This is a system diagram illustrating an example communication system; Figure 1B The illustration can be found Figure 1AThe diagram illustrates a system diagram of an example wireless transmit / receive unit (WTRU) used within a communication system. Figure 1C The illustration can be found Figure 1A The diagram illustrates a system diagram of an example radio access network (RAN) and an example core network (CN) used within a communication system. Figure 1D The illustration can be found Figure 1A The diagram shows another example RAN and another example CN used in the communication system. Figure 2 This is a signaling diagram of a UE-to-UE relay discovery process according to some embodiments; Figure 3 This is a signaling diagram of a UE-to-UE relay discovery process according to some embodiments; and Figure 4 An example flowchart of a method according to some embodiments is illustrated. Detailed Implementation

[0007] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the 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, processes, components, and circuits have not been described in detail so as not to obscure the following description. Furthermore, embodiments and examples not specifically described herein may be practiced in place of, or in combination with, the embodiments and other examples expressly, implicitly, and / or inherently described, disclosed, or otherwise provided herein (collectively, the “Provided”). Although various embodiments are described and / or claimed herein (where apparatuses, systems, devices, etc., and / or any elements thereof perform operations, processes, algorithms, functions, etc., and / or any part thereof), it should be understood that any embodiment described and / or claimed herein assumes that any apparatus, system, device, etc., and / or any element thereof is configured to perform any operation, process, algorithm, function, etc., and / or any part thereof.

[0008] The methods, apparatus, and systems provided herein are well-suited for communications involving both wired and wireless networks. Regarding... Figure 1A-1D An overview of various types of wireless devices and infrastructures is provided, wherein various elements of the network may: utilize, perform, be arranged in accordance with, and / or be adapted to, and / or be configured for use with the methods, apparatuses and systems provided herein.

[0009] Figure 1AThis is a system diagram illustrating an example communication system 100, in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system providing content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access this content through the sharing of system resources (including wireless bandwidth). For example, the communication system 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) Discrete Fourier Transform (DFT) Extended OFDM (ZTUW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0010] like Figure 1A As shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, radio access networks (RANs) 104 / 113, core networks (CNs) 106 / 115, public switched telephone networks (PSTNs) 108, the Internet 110, and other networks 112. However, it will be understood 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. As examples, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include / or be user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or Mi-Fi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. WTRUs 102a, 102b, 102c, and 102d, or any other WTRU mentioned or described herein, may be interchangeably referred to as a UE.

[0011] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly interface with at least one of WTRUs 102a, 102b, 102c, and 102d, for example, to facilitate access to one or more communication networks, such as CN106 / 115, Internet 110, and / or Network 112. As an example, base stations 114a and 114b can be any of the following: base transceiver station (BTS), node B (NB), evolved node B (eNB), home node B (HNB), home evolved node B (HeNB), g node B (gNB), NR node B (NR NB), site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b can include any number of interconnected base stations and / or network elements.

[0012] Base station 114a may be part of RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies (which may be referred to as cells (not shown)). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may vary over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In one embodiment, 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 can be used to transmit and / or receive signals in a desired spatial direction.

[0013] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Any suitable radio access technology (RAT) can be used to establish air interface 116.

[0014] More specifically, as noted above, communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies (such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA)), which can use wideband CDMA (WCDMA) to establish air interface 116. 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).

[0015] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as evolved UMTS terrestrial radio access (E-UTRA), which can use Long Term Evolution (LTE) and / or Advanced LTE (LTE-A) and / or Advanced LTE Pro (LTE-A Pro) to establish air interface 116.

[0016] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use New Radio (NR) to establish air interface 116.

[0017] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for instance, use a dual connectivity (DC) principle to implement both LTE and NR radio access together. Therefore, the air interface utilized by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0018] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSMEDGE (GERAN), etc.

[0019] Figure 1A Base station 114b can be, for example, a wireless router, a home node B, a home evolution node B, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in local areas such as commercial locations, homes, vehicles, campuses, industrial facilities, air corridors (e.g., for drone use), roads, etc. In one embodiment, base station 114b and WTRU102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRU102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In one embodiment, base station 114b and WTRU102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.) to establish any of small cells, picocells, or femtocells. Figure 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN106 / 115.

[0020] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data can have different Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions such as user authentication. Although not explicitly stated... Figure 1AAs shown, but to be understood, RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs employing the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which can utilize NR radio technology, CN 106 / 115 can also communicate with another RAN (not shown) employing any of GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or Wi-Fi radio technologies.

[0021] CN 106 / 115 may also act as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 114 or a different RAT.

[0022] Some or all of the WTRUs 102a, 102b, 102c, and 102d in communication system 100 may include multi-mode capability (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers for communicating with different wireless networks via different wireless links). For example, Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a, which can employ cellular-based radio technology, and with base station 114b, which can employ IEEE 802 radio technology.

[0023] Figure 1B This is a system diagram illustrating the example WTRU 102. (Example:) Figure 1B As shown, 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 supply 134, a Global Positioning System (GPS) chipset 136, and / or other components / peripherals 138, etc. It will be understood that, while remaining consistent with the embodiments, WTRU 102 may include any sub-combination of the foregoing components.

[0024] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal encoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, which may be coupled to transmitting / receiving element 122. Although Figure 1B The processor 118 and transceiver 120 are depicted as separate components, but it will be understood that the processor 118 and transceiver 120 may be integrated together, for example, in an electronic package or chip.

[0025] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In one embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF signals and optical signals. It will be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0026] Although the transmitting / receiving element 122 is in Figure 1B While depicted as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. For example, WTRU 102 may employ MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0027] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As noted above, WTRU 102 can have multi-mode capability. Thus, for example, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via various RATs such as NR and IEEE 802.11.

[0028] The processor 118 of WTRU 102 can be coupled to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and can receive user input data therefrom. The processor 118 can also output user data to the speaker / microphone 124, keypad 126, and / or display / touchpad 128. Furthermore, the processor 118 can access information from any type of suitable memory (such as non-removable memory 130 and / or removable memory 132) and can store data in any type of suitable memory (such as non-removable memory 130 and / or removable memory 132). 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. Removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital storage (SD) card, etc. In other embodiments, processor 118 may access information from memory that is not physically located on WTRU 102 (such as on a server or home computer (not shown)) and may store data in that memory.

[0029] The processor 118 may receive power from the power supply 134 and may be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 may be any suitable device for powering the WTRU 102. For example, the power supply 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, etc.

[0030] The processor 118 may also be coupled to a GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) about the current location of the WTRU 102. Attached to or replacing the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via air interface 116 and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that, while remaining consistent with the embodiments, the WTRU 102 may acquire location information using any suitable location determination method.

[0031] Processor 118 may be further coupled to other components / peripherals 138, which may include one or more software and / or hardware modules / units providing additional features, functions, and / or wired or wireless connectivity. For example, component / peripheral 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (e.g., for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Component / peripheral 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0032] WTRU 102 may include a full-duplex radio for which some or all of the transmissions and receptions (e.g., associated with specific subframes for both 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 for reducing and / or substantially eliminating self-interference via hardware (e.g., a choke) or via signal processing (e.g., a separate processor (not shown) or via processor 118). In one embodiment, WTRU 102 may include a half-duplex radio for which some or all of the transmissions and receptions (e.g., associated with specific subframes for either uplink (e.g., for transmission) or downlink (e.g., for reception)) may be concurrent and / or simultaneous.

[0033] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to one embodiment. As noted above, RAN 104 can use E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 can also communicate with CN 106.

[0034] RAN 104 may include evolved Nodes B 160a, 160b, and 160c, but it will be understood that RAN 104 may include any number of evolved Nodes B while remaining consistent with the embodiments. Each evolved Node B 160a, 160b, and 160c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, evolved Nodes B 160a, 160b, and 160c may implement MIMO technology. Therefore, evolved Node B 160a may, for example, use multiple antennas to transmit radio signals to and receive radio signals from WTRU 102a.

[0035] Each of the evolved Nodes B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in the uplink (UL) and / or downlink (DL), etc. Figure 1C As shown, evolution nodes B160a, 160b, and 160c can communicate with each other via the X2 interface.

[0036] Figure 1C The CN 106 shown 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 is depicted as part of the CN 106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0037] The MME 162 can connect to each of the evolved nodes B 160a, 160b, and 160c in RAN 104 via the S1 interface and can act as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, and so on. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies such as GSM and / or WCDMA.

[0038] The SGW 164 can connect to each of the evolved Nodes B 160a, 160b, and 160c in RAN104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions such as anchoring the user plane during inter-evolved Node B handovers, triggering paging when DL data is available for WTRUs 102a, 102b, and 102c, and managing and storing the context of WTRUs 102a, 102b, and 102c.

[0039] SGW 164 can be connected to PGW 166, which can provide WTRU 102a, 102b, 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0040] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to circuit-switched networks (such as PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional land-line communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 106 and PSTN 108, or can communicate with such an IP gateway. Furthermore, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0041] Despite WTRU in Figure 1A-1D While described as a wireless terminal, it is envisioned that, in some representative embodiments, such a terminal may (e.g., temporarily or permanently) use a wired communication interface with a communication network.

[0042] In a representative embodiment, the other network 112 may be a WLAN.

[0043] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can have an access or interface to a distribution system (DS) or another type of wired / wireless network that carries traffic to and / or out of the BSS. Traffic originating outside the BSS and destined for a STA can reach and be delivered to the STA via the AP. Traffic originating from a STA and destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP; for example, a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. Peer-to-peer traffic can be sent between a source STA and a destination STA (e.g., directly between them) using Direct Link Establishment (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using the Standalone BSS (IBSS) mode can function without access points (APs), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as an "ad-hoc" communication mode in this document.

[0044] When operating in 802.11ac infrastructure mode or a similar mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a 20 MHz bandwidth) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, each STA (including the AP) can listen on the primary channel. If the primary channel is listened to / detected and / or determined to be busy by a particular STA, that STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0045] High-throughput (HT) STAs can communicate using a 40 MHz wide channel, for example, by combining a primary 20 MHz channel with adjacent or non-adjacent 20 MHz channels to form a 40 MHz wide channel.

[0046] Very High Throughput (VHT) STAs can support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. 40 MHz and / or 80 MHz channels can be formed by combining consecutive 20 MHz channels. A 160 MHz channel can be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels (this can be referred to as an 80+80 configuration). For the 80+80 configuration, after channel coding, data can be split into two streams by a segment parser. Each stream can be processed individually using Inverse Fast Fourier Transform (IFFT) and time-domain processing. These streams can be mapped to two 80 MHz channels, and data can be transmitted via a transmitting STA. At the receiver of the receiving STA, the operations described above for the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC) layer, entities, etc.

[0047] 802.11af and 802.11ah support operating modes below 1 GHz. Compared to those used in 802.11n and 802.11ac, 802.11af and 802.11ah reduce channel operating bandwidth and carrier. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV white space (TVWS) spectrum, while 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11ah may support instrument-type control / machine-type communication (MTC), such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities, including supporting (e.g., only supporting) certain bandwidths and / or limited bandwidths. MTC devices may include batteries with a battery life above a threshold (e.g., to maintain a very long battery life).

[0048] WLAN systems that can support multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah include a channel that can be designated as the primary channel. The primary channel can have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel can be set and / or limited by STAs supporting the minimum bandwidth operating mode from all STAs operating in the BSS. In the 802.11ah example, for STAs supporting (e.g., only supporting) the 1 MHz mode (e.g., MTC type devices), the primary channel can be 1 MHz wide, 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 Sense and / or Network Allocation Vector (NAV) settings can depend on the status of the primary channel. If the primary channel is busy, for example, because an STA (which only supports the 1 MHz operating mode) is transmitting to the AP, the entire available band can be considered busy even if most of the band remains idle and potentially available.

[0049] In the United States, the available frequency band for 802.11ah is 902 MHz to 928 MHz. In South Korea, the available frequency band is 917.5 MHz to 923.5 MHz. In Japan, the available frequency band is 916.5 MHz to 927.5 MHz. The total available bandwidth for 802.11ah is 6 MHz to 26 MHz, depending on the country code.

[0050] Figure 1D This is a system diagram illustrating RAN 113 and CN 115 according to one embodiment. As noted above, RAN 113 may employ NR radio technology to communicate with WTRU 102a, 102b, 102c via air interface 116. RAN 113 may also communicate with CN 115.

[0051] RAN 113 may include gNBs 180a, 180b, and 180c, but it will be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, and 180c may include one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from WTRUs 102a, 102b, and 102c. Therefore, gNB 180a may, for example, use multiple antennas to transmit and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c can implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers (not shown) to WTRU 102a. A subset of these component carriers can be on unlicensed spectrum, while the remaining component carriers can be on licensed spectrum. In one embodiment, gNBs 180a, 180b, and 180c can implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a can receive cooperative transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0052] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with a scalable set of parameters. For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary depending on different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of various or scalable lengths (e.g., including different numbers of OFDM symbols and / or continuously varying absolute time lengths).

[0053] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without also accessing other RANs (e.g., evolved Node Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c use one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, while also communicating / connecting with another RAN (such as evolved Node B 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate substantially simultaneously with one or more gNBs 180a, 180b, and 180c and one or more evolved Node B 160a, 160b, and 160c. In a non-standalone configuration, evolved Node B 160a, 160b, and 160c can serve as mobility anchors for WTRUs 102a, 102b, and 102c, and gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0054] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network slicing support, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB180a, 180b, and 180c can communicate with each other via the Xn interface.

[0055] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and at least one Data Network (DN) 185a, 185b. Although each of the foregoing elements is depicted as part of the CN 115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0056] AMF 182a and 182b can connect to one or more of gNB180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different Protocol Data Unit (PDU) sessions with different requirements), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, etc. AMF 182a and 182b can use network slicing, for example, to customize CN support for WTRU102a, 102b, and 102c based on the type of service utilized by WTRU102a, 102b, and 102c. For example, different network slices can 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, etc. AMF 162 can provide control plane functions for switching between RAN 113 and other RANs (not shown) that employ other radio technologies such as LTE, LTE-A, LTE-APro and / or non-3GPP access technologies such as Wi-Fi).

[0057] SMF 183a and 183b can connect to AMF182a and 182b in CN 115 via the N11 interface. SMF 183a and 183b can also connect to UPF184a and 184b in CN 115 via the N4 interface. SMF 183a and 183b can select and control UPF184a and 184b, and configure the routing of services through UPF184a and 184b. SMF183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0058] UPF 184a and 184b can be connected via the N3 interface to one or more of gNB180a, 180b, and 180c in RAN 113. This provides WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110), for example, to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can perform other functions such as routing and forwarding packets, implementing user plane policies, supporting multihomed PDU sessions, handling user plane QoS, caching downlink packets, and providing mobility anchoring.

[0059] CN 115 can facilitate communication with other networks. For example, CN 115 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that acts as an interface between CN 115 and PSTN 108, or may communicate with such an IP gateway. Furthermore, CN 115 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c may be connected to DNs 185a and 185b via UPF 184a and 184b through the N3 interface to UPFs 184a and 184b and the N6 interface between UPFs 184a and 184b and local data networks (DNs) 185a and 185b.

[0060] Given Figure 1A-1D as well as Figure 1A-1D The corresponding descriptions, relating to any one or more of the functions described herein, can be performed by one or more emulation components / devices (not shown): WTRU102a-102d, base station 114a-114b, evolved Node B 160a-160c, MME 162, SGW164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other component(s) / device(s) described herein. An emulation device can be one or more devices configured to mimic one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0061] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices can perform one or more or all functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. The one or more simulation devices can perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices can be directly coupled to another device for testing purposes and / or can use over-the-air wireless communication to perform tests.

[0062] The one or more emulation devices can perform one or more (including all) functions without being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices can be used in test scenarios within a test laboratory and / or non-deployed (e.g., testing) wired and / or wireless communication networks to perform testing of one or more components. The one or more emulation devices can be test rigs. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) can be used by the emulation devices to transmit and / or receive data.

[0063] The embodiments disclosed herein are representative and do not limit the applicability of the apparatus, processes, functions, and / or methods to any particular wireless technology, any particular communication technology, or other technology. The term "network" in this disclosure may generally refer to one or more base stations or gNBs or other network entities, which may be associated with one or more Transmit / Receive Points (TRPs), or any other node in a radio access network.

[0064] Note that in all the example embodiments described herein, the terms “base station,” “serving base station,” “RAN,” “RAN node,” “access network,” “NG-RAN,” “gNodeB,” and / or “gNB” may be used interchangeably to refer to any network element, such as a network element that acts as a serving base station, for example. It should be understood that the embodiments described herein are not limited to gNBs and are applicable to any other type of base station.

[0065] 5G ProSe defines several features and procedures, such as 5G ProSe direct discovery, 5G ProSe direct communication, 5G ProSe UE-to-Network relay, and 5G ProSe UE-to-UE relay.

[0066] 5G ProSe UE-to-UE relay enables indirect communication between two End UEs. Thus, a 5GProSe UE-to-UE relay can refer to a UE with 5GProSe capability that provides connectivity between 5G ProSe End UEs. Note that an End UE can refer to a 5GProSe-capable UE that can connect to one or more other 5G ProSe-capable UEs via a 5G ProSe UE-to-UE relay. For UE-to-UE relay, 5G ProSe UE-to-UE relay discovery and 5G ProSe communication via UE-to-UE relay are defined.

[0067] For 5G ProSe UE-to-UE relay discovery, both Model A and Model B discovery are supported. Model A uses a single discovery protocol message (announcement). Model B uses two discovery protocol messages (request and response).

[0068] During 5G ProSe UE-to-UE relay discovery, information about the two End UEs is shared between them to identify the discovering End UE and the discovered End UE. However, this information is protected between the two End UEs and is transparent to UE-to-UE relay. Therefore, UE-to-UE relay cannot obtain or identify the End UE's information, nor can it use this information for route discovery, other signaling messages, or other purposes.

[0069] 5G ProSe communication via UE-to-UE relay is possible using Layer 2 or Layer 3 UE-to-UE relay. For both Layer 2 and Layer 3 UE-to-UE relay, 5G ProSe communication settings with a discovery process are defined. Furthermore, discovery integrated into the PC5 unicast link establishment process is also defined.

[0070] Using a Layer 2 UE-to-UE relay, an end-to-end PC5 link is established between End UEs. PC5-S messages can then be exchanged between End UEs.

[0071] Using a Layer 3 UE-to-UE relay, each End UE establishes a PC5 link with the relay, and the relay forwards messages to the End UE. PC5-S messages are exchanged between the End UE and the relay.

[0072] When using a Layer 3 UE-to-UE trunk, and employing an Internet Protocol (IP)-based data connection, after establishing a PC5 link with the trunk, each End UE can be assigned an IP address by the trunk using a Dynamic Host Configuration Protocol (DHCP) mechanism, or each End UE can assign its own IP address using a link-local IP address allocation mechanism and notify the trunk of that address. The choice between DHCP and link-local IP address allocation can be determined during the establishment of the secure connection between the End UE and the UE-to-UE trunk.

[0073] Proposals in 3GPP are under discussion to investigate potential enhancements to support multi-hop UE-to-Network (U2N) and UE-to-UE (U2U) relays in Rel-19 (e.g., see 3GPP TR 23.700-03 v0.2.0 Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS); Phase 3 (Release 19)). Multi-hop U2N relays enable remote UEs to discover and communicate with U2N relays via one or more U2U relays. Multi-hop U2U relays enable end UEs to discover and communicate with each other via more than one U2U relay. Multi-hop capability can be important for mission-critical communications (e.g., emergency responders) and often requires enhanced coverage (e.g., indoors).

[0074] The IETF developed technologies to support mobile ad hoc networks (MANETs). Each router in a MANET can discover other routers by exchanging HELLO messages, and each router can determine its 1-hop and 2-hop neighbors based on the exchanged HELLO messages (see, for example, RFC 6130, Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)). Each router can store a list of its 1-hop and 2-hop neighbors, allowing the MANET routing protocol to utilize this information.

[0075] MANET routing is based on the Optimized Link-State Routing (OLSR) protocol (see, for example, RFC 7181, The Optimized Link-State Routing Protocol Version 2). Each router periodically exchanges its topology information with other routers in the network. Each router can select two sets of Multi-Point Relays (MPRs), each set being a group of neighboring routers covering all 2-hop neighbor routers it is connected to. These two sets are the "Flooding MPR" and the "Route MPR," used to implement flood reduction and topology reduction, respectively. Flood reduction is achieved by flooding control traffic across the network using hop-by-hop forwarding, but routers only need to forward control traffic received first directly from one of the routers that has selected it as a flooding MPR. Topology reduction is achieved by assigning special responsibilities to routers selected as route MPRs when declaring link-state information. Routers not selected as route MPRs are not required to send any link-state information.

[0076] To support multi-hop ProSe UE-to-UE relays, relays supporting multi-hop ProSe UE-to-UE relay functionality (e.g., each relay) can form a co-located MANET router function, connecting to adjacent MANET routers and establishing a mobile ad hoc network defined in the MANET (e.g., see RFC 5444, Generalized Mobile Ad Hoc Network (MANET) Packet / Message Format). 5G ProSe communication can be used for communication between two UE-to-UE relays acting as MANET routers, and all MANET messages exchanged between UE-to-UE relays can be considered data services on the PC5 user plane interface.

[0077] Supporting discovery and PC5 connection establishment between two End UEs via one or more UE-to-UE relays is a primary function of multi-hop UE-to-UE relays. Therefore, it is expected that multi-hop UE-to-UE relays with MANETs will also support discovery and PC5 connection establishment between two End UEs via UE-to-UE relays with MANETs. Furthermore, the security level implemented by 5G ProSe UE-to-UE relays should be maintained in multi-hop UE-to-UE relays, including those with MANETs.

[0078] Therefore, it is desirable to address at least the following issues while maintaining compatibility with UE-to-UE relay security requirements: how an End UE discovers one or more other End UEs in a MANET-based UE-to-UE relay network, and / or how a UE-to-UE relay in a MANET can forward signaling messages from one End UE to another. Thus, in addition to addressing other issues not explicitly stated above, some example embodiments described herein can resolve at least the issues mentioned above.

[0079] As will be discussed in more detail below, some example embodiments can be applied to UE-to-UE (U2U) relay discovery using a MANET topology. In one embodiment, a U2U relay may be configured with a Relay Service Code (RSC) for MANET (e.g., it may receive configuration information indicating the RSC for MANET) and may join a MANET-based U2U relay network based on the RSC. After joining the MANET, the U2U relay may share (or provide) routing information to the ProSe layer within the MANET, for example, enabling the U2U relay discovery and PC5 connection establishment processes to use the routing information to forward messages to the appropriate U2U relay. According to one embodiment, when a U2U relay request message is sent, the U2U relay may update the user information of the U2U relay acting as the first-hop relay of the discovering End UE with its own user information, for example, enabling the discovering End UE and the discovered End UE to recognize the routing information (i.e., the user information of the first-hop relay of the discovering End UE and the user information of the first-hop relay of the discovered End UE). When (for example, only if) MANET_forwarding_indication is included in a U2U relay request message, a U2U relay may decide to use the received U2U relay request message to send a U2U relay request message to an End UE in its vicinity. When sending a U2U relay request message, a U2U relay supporting flooding MPR may include MANET_forwarding_indication in the U2U relay request message to be sent, for example, so that the U2U relay of the next hop of flooding MPR can use the U2U relay request message from the U2U relay supporting flooding MPR.

[0080] As will be discussed in more detail below, some example embodiments can be used for UE-to-UE (U2U) relay discovery with one or more dedicated signaling messages used to exchange discovery information between U2U relays. In one embodiment, a U2U relay may be configured with an RSC for MANET and may join a MANET-based U2U relay network based on the RSC. When sending a U2U relay request message, the U2U relay may update the user information of the U2U relay that is the first-hop relay of the discovering EndUE with its own user information, for example, so that the discovering EndUE and the discovered EndUE can recognize routing information (i.e., the user information of the first-hop relay of the discovering EndUE and the user information of the first-hop relay of the discovered EndUE). If the U2U relay receiving the U2U relay request message is either from the discovering End UE or a U2U relay operating as a flooding MPR, one or more signaling messages may be sent to the U2U relay to share (or provide) information associated with the request message sent from the End UE (e.g., this information may include RSC, user information of the discovering End UE, etc.) and user information of the U2U relay acting as the first-hop relay of the discovering End UE. Upon receiving a signaling message from the End UE that includes information associated with the request message, the U2U relay may send a U2U relay request message that will be received (or intended to be received by) an End UE in the vicinity.

[0081] As described above, some example embodiments may involve or include UE-to-UE relay discovery using MANET topology information. For example, one embodiment may include UE-to-UE relay discovery using Model B, which uses request and response messages between the discovering End UE and the discovered End UE via multi-hop UE-to-UE relay forming a MANET-based UE-to-UE relay network.

[0082] In some embodiments, it can be assumed that UE-to-UE trunks supporting MANET router functionality and one or more common trunk service codes (RSCs) can form a MANET-based UE-to-UE trunk network and can store routing information for service exchange with other UE-to-UE trunks in the same MANET.

[0083] In another example, after registration and authorization of a UE-to-UE relay with MANET capability, the RSC of the MANET-based U2U relay network can be pre-configured or configured during parameter provision.

[0084] When a U2U trunk receives an RSC for a MANET-based U2U trunk, the U2U trunk can attempt to discover other U2U trunks that support the same RSC and can establish one or more PC5 connections with the discovered U2U trunks, for example, allowing the U2U trunk to attempt to join a MANET-based U2U trunk network.

[0085] Routing information can include information about how a U2U trunk connects to another U2U trunk via other U2U trunks, based on information exchanged via MANET technology.

[0086] Once joined to a MANET, routing information can be shared or otherwise provided when it is available within that MANET. For example, routing information can be shared at the ProSe layer, allowing 5G ProSe UE-to-UE discovery and PC5 connection setup procedures to use the routing information to forward messages to the appropriate U2U trunk.

[0087] In one embodiment, an End UE may send a U2U relay request message to discover another End UE with (e.g., an indication) an RSC that supports multi-hop U2U relay service. When (or subsequently) a U2U relay request message is received from an End UE, the U2U relay may send a U2U relay request message to be received by End UEs and other U2U relays in the vicinity. The U2U relay request message from a U2U relay may include or indicate the U2U relay's user information (as the first-hop relay of the discovering End UE) and MANET_forwarding_indication to instruct other U2U relays to forward the message to End UEs in the vicinity.

[0088] In one embodiment, a U2U relay request message from a U2U relay may include or indicate user information that the U2U relay is the first-hop relay for the discovering End UE and also the first-hop relay for the discovering End UE.

[0089] In one embodiment, upon receiving a U2U relay request message with MANET_forwarding_indication, the receiving U2U relay may send a U2U relay request message to be received by (or intended to be received by) an End UE in the vicinity of (the receiving U2U relay). If the received U2U relay request message does not include user information of the U2U relay (as the first-hop relay of the discovered End UE), the user information of the sending U2U relay (as the first-hop relay of the discovered End UE) may be added, appended, or otherwise included or indicated in the message. If the received U2U relay request message includes user information of the U2U relay (as the first-hop relay of the discovered End UE), the sending U2U relay may change / replace the user information in the message with its own user information (as the first-hop relay of the discovered End UE). If a U2U relay receives a U2U relay request message without MANET_forwarding_indication, it can discard the received message because the message is intended for reception by the End UE, not by the U2U relay itself. If a U2U relay operating as a flooding MPR in a MANET receives a U2U relay request message with MANET_forwarding_indication, it can send a U2U relay request message with MANET_forwarding_indication, which will be received by the End UE in the vicinity and one or more other U2U relays in the next hop.

[0090] In one embodiment, if the discovering End UE receives a U2U relay request message with or without MANET_forwarding_indication, it can send a response message to the U2U relay based on the user information of the U2U relay that is the first-hop relay UE of the discovering End UE.

[0091] According to one embodiment, when a response message is received from the discovered End UE, the U2U relay can send the response message to the next hop U2U relay based on the user information of the U2U relay (as the first-hop relay of the discovered End UE) and the routing information to the U2U relay (as the first-hop relay of the discovered End UE).

[0092] Figure 2 The diagram illustrates an example signaling diagram of a UE-to-UE relay discovery process using MANET_forwarding_indication according to one embodiment. Figure 2In the example, in step 200a, the End UE and the U2U trunk are authorized to use the multi-hop U2U trunk service and may be provided with parameters for the discovery and / or selection of the End UE via the U2U trunk and for establishing one or more PC5 connections via the multi-hop U2U trunk. In step 200b, a U2U trunk capable of implementing MANET router functionality may join a MANET-based U2U trunk network. By exchanging information with other MANET routers, the U2U trunk (e.g., each U2U trunk) may store routing information for communication with other U2U trunks capable of implementing MANET router functionality in the same MANET-based U2U trunk network. In step 200c, the U2U trunk (e.g., each U2U trunk) may share the routing information at the ProSe layer in the MANET-based U2U trunk network, for example, making it available for use during the ProSe U2U trunk discovery and PC5 connection establishment process.

[0093] exist Figure 2 In the example, in step 201, the S-End UE (e.g., the source End UE or the discovering End UE) may send a U2U relay request message to discover another End UE. The U2U relay request message may include user information of the S-End UE, user information of the T-End UE (e.g., the target End UE or the discovering End UE), and / or an RSC that supports multi-hop U2U relay services.

[0094] like Figure 2 As shown in the example, in step 202, when the U2U relay ( Figure 2 In the example, when U2U relay_1 receives a U2U relay request message from an S-End UE, the U2U relay can send the U2U relay request message to one or more End UEs in the vicinity and other U2U relays (here, U2U relay_2 and U2U relay_3) in a 1-hop connection based on routing information. The U2U relay request message may include user information of the S-End UE (e.g., the source End UE or the discoverer End UE), user information of the T-End UE (e.g., the target End UE or the discoverer End UE), user information of U2U relay_1, RSC, and / or MANET_forwarding_indication.

[0095] exist Figure 2 In the example, in step 203a, when the U2U relay ( Figure 2In the example, when U2U relay_2 receives a U2U relay request message from U2U relay_1, the U2U relay can send the U2U relay request message to the End UEs in the vicinity. The U2U relay request message may include user information for the S-End UE (e.g., the source End UE or the discoverer End UE), user information for the T-End UE (e.g., the target End UE or the discoverer End UE), user information for U2U relay_1, user information for U2U relay_2, and / or RSC. In this example, the request message does not include MANET_forwarding_indication because U2U relay_2 was not selected as a flooding MPR by U2U relay_1, and the request message is for (e.g., only for) End UEs in the vicinity, not for other U2U relays.

[0096] like Figure 2 As shown in the example, in step 203b, when the U2U relay ( Figure 2 In the example, when U2U relay_3 receives a U2U relay request message from U2U relay_1, the U2U relay can send a U2U relay request message for End UEs in the vicinity and other U2U relays in the 1-hop connection. The U2U relay request message may include user information for the S-End UE (e.g., the source End UE or the discoverer End UE), user information for the T-End UE (e.g., the target End UE or the discoverer End UE), user information for U2U relay_1, user information for U2U relay_3, RSC, and / or MANET_forwarding_indication. In this example, the request message includes MANET_forwarding_indication because U2U relay_3 is selected by U2U relay_1 as the flooding MPR, and the request message is for End UEs in the vicinity and other U2U relays in the 1-hop connection.

[0097] exist Figure 2 In the example, in step 204, when the U2U relay ( Figure 2In the example, when U2U relay_4 receives a U2U relay request message including MANET_forwarding_indication from U2U relay_3, the U2U relay can send a U2U relay request message for an End UE in the vicinity. The U2U relay request message may include user information for the S-End UE (e.g., the source End UE or the discoverer End UE), user information for the T-End UE (e.g., the target End UE or the discoverer End UE), user information for U2U relay_1, user information for U2U relay_4, and / or RSC. In this example, the request message does not include MANET_forwarding_indication because U2U relay_4 was not selected by U2U relay_3 as a flooding MPR, and the request message is for (e.g., only for) End UEs in the vicinity, not for other U2U relays.

[0098] In one embodiment, when a U2U relay (e.g., Figure 2 In the example, when U2U relays_1, U2U relay_2, U2U relay_3, and U2U relay_4 receive a U2U relay request message without MANET_forwarding_indication from other U2U relays, the U2U relays can discard the received message because the message is intended to be received by the End UE, not by the U2U relay.

[0099] exist Figure 2 In the example, in step 205, when the T-End UE receives a U2U relay request message from the S-End UE via a U2U relay for discovering the T-End UE, the T-End UE can select a U2U relay from among the multiple U2U relays that sent the U2U relay request message from the S-End UE (e.g., in...). Figure 2 In the example, the T-End UE selects a U2U relay (4), for example, based on the link quality of the received messages. In one embodiment, the T-End UE can connect to the selected U2U relay (e.g., Figure 2 In the example, U2U relay_4 sends a U2U relay response message, which may include user information of the S-EndUE (e.g., the source EndUE or the discoverer EndUE), user information of the T-EndUE (e.g., the target EndUE or the discoverer EndUE), user information of U2U relay_1, user information of U2U relay_4, and / or RSC.

[0100] like Figure 2As shown in the example, in step 206, when a U2U relay response message is received from the T-End UE, U2U relay_4 can send a response message to U2U relay_1 based on routing information to establish a connection between U2U relay_4 and U2U relay_1. This response message may include user information of the S-End UE (e.g., the source End UE or the discoverer End UE), user information of the T-End UE (e.g., the target End UE or the discoverer End UE), user information of U2U relay_1, user information of U2U relay_4, and / or RSC.

[0101] exist Figure 2 In the example, in step 207, when a U2U relay response message is received from the T-End UE via another U2U relay, U2U relay_1 can send a response message to the S-End UE. This response message may include user information of the S-End UE (e.g., the source End UE or the discovering End UE), user information of the T-End UE (e.g., the target End UE or the discovering End UE), user information of U2U relay_1, user information of U2U relay_4, and / or RSC. After receiving the U2U relay response message, the S-End UE can store the user information of U2U relay_1, the user information of U2U relay_4, and the user information of the T-End UE, indicating the appropriate (e.g., suitable) U2U relay in the path of communication with the T-End UE via the U2U relay.

[0102] As described above, some example embodiments may target or include UE-to-UE relay discovery, which has one or more dedicated signaling messages for exchanging discovery information between UE-to-UE relays. For example, one embodiment may involve UE-to-UE relay discovery utilizing Model B, which uses request and response messages between the discovering End UE and the discovered End UE via a multi-hop UE-to-UE relay, including information about sharing request messages between UE-to-UE relays.

[0103] In some embodiments, it can be assumed that UE-to-UE trunks supporting MANET router capabilities and the same RSC can form a MANET-based UE-to-UE trunk network and can store routing information for service exchange with other UE-to-UE trunks on the same MANET. The routing information may include information about how a U2U trunk connects to another U2U trunk via other U2U trunks, derived from information exchanged via MANET technology.

[0104] In one embodiment, an End UE may send a U2U relay request message to discover another End UE with an RSC that supports multi-hop U2U relay services.

[0105] According to one embodiment, when a U2U relay request message is received from an End UE (or subsequently), the U2U relay may forward or send the U2U relay request message, which includes or indicates user information of the U2U relay (as the first-hop relay of the discovering End UE), to End UEs in the vicinity. The U2U relay may send one or more messages, including information related to the request message, to other U2U relays in the 1-hop connection.

[0106] In one embodiment, when a request message is received from a U2U relay (or after it is received), the receiving U2U relay can send a U2U relay request message to the End UE in the vicinity. The message includes the user information of the discovering End UE, the user information of the discovered End UE, the user information of the U2U relay (as the first-hop relay of the discovering End UE), and its user information (as the first-hop relay of the discovered End UE).

[0107] According to one embodiment, if a U2U relay operating as a flooding MPR at a MANET receives information about a request message from another U2U relay, it can send one or more messages, including the information about the request message, to other U2U relays within the 1-hop connection.

[0108] In one embodiment, if the discovered End UE receives a U2U relay request message from the U2U relay, it can send a response message to the U2U relay based on the user information of the U2U relay that is the first-hop relay of the discovered End UE.

[0109] According to one embodiment, when a response message is received from the discovered End UE (or after the response message is received), the U2U relay can send the response message to the U2U relay using routing information based on the user information of the U2U relay (which is the first-hop relay of the discovered End UE).

[0110] Figure 3 The diagram illustrates an example signaling diagram of the UE-to-UE relay discovery process using MANET messages, according to some example embodiments. Figure 3In the example 300a, End UEs and U2U trunks are authorized to use multi-hop U2U trunk services and can be provided with parameters for the discovery and / or selection of End UEs via U2U trunks and for establishing one or more PC5 connections via multi-hop U2U trunks. In 300b, U2U trunks capable of implementing MANET router functionality can join a MANET-based U2U trunk network. By exchanging information with other MANET routers, U2U trunks (e.g., each U2U trunk) can store routing information for communication with other MANET-based U2U trunks in the same MANET-based U2U trunk network capable of implementing MANET router functionality.

[0111] like Figure 3 As shown in the example, in step 301, an S-End UE (e.g., the source End UE or the discovering End UE) can send a U2U relay request message to discover another End UE. The U2U relay request message may include user information of the S-End UE, user information of the T-End UE (e.g., the target End UE or the discovering End UE), and / or an RSC that supports multi-hop U2U relay services.

[0112] exist Figure 3 In the example 302, when U2U relay ( Figure 3 When U2U Relay_1 in the example receives a U2U Relay Request message from an S-End UE, it can send U2U Relay Request messages to one or more End UEs in the vicinity. The U2U Relay Request message may include user information of the S-End UE (e.g., the source End UE or the discoverer End UE), user information of the T-End UE (e.g., the target End UE or the discoverer End UE), user information of U2U Relay_1, and / or RSC.

[0113] like Figure 3 As shown in the example, in 303, U2U relay_1 can connect to a U2U relay at a 1-hop connection (e.g., Figure 3 The U2U relay_2 and U2U relay_3 send messages (e.g., new MANET messages) to share information from a request message from the S-End UE. This message may include user information for the S-End UE (source End UE or discoverer End UE), user information for the T-End UE (target End UE or discoverer End UE), user information for the U2U relay_1, and / or RSC.

[0114] exist Figure 3In the example 304a, when a U2U relay (e.g., U2U relay_2) receives a signaling message from U2U relay_1 containing information for sharing a request message from an End UE, it can send a U2U relay request message for one or more End UEs in the vicinity. The U2U relay request message may include user information for the S-End UE (source End UE or discoverer End UE), user information for the T-End UE (target End UE or discoverer End UE), user information for U2U relay_1, user information for U2U relay_2, and / or RSC.

[0115] like Figure 3 As shown in the example, in 304b, when a U2U relay (e.g., U2U relay_3) receives a signaling message from U2U relay_1 for sharing an information request message from an End UE (or after receiving it), it can send a U2U relay request message for one or more End UEs in the vicinity. The U2U relay request message may include user information of the S-End UE (source End UE or discoverer End UE), user information of the T-End UE (target End UE or discoverer End UE), user information of U2U relay_1, user information of U2U relay_3, and / or RSC.

[0116] exist Figure 3 In the example at 305, when U2U relay_3 is selected as the flooding MPR by U2U relay_1, U2U relay_3 can forward a message from U2U relay_1 (e.g., a MANET message) for sharing information from a request message from the End UE to other U2U relays within the 1-hop connection. This signaling message may include user information for the S-End UE (source End UE or discoverer End UE), user information for the T-End UE (target End UE or discoverer End UE), user information for U2U relay_1, and / or RSC.

[0117] like Figure 3 As shown in the example, in 306, when a U2U relay (e.g., U2U relay_4) receives a signaling message from U2U relay_3 containing information for sharing a request message from an End UE, it can send a U2U relay request message for an End UE in the vicinity. The U2U relay request message may include user information for the S-End UE (source End UE or discoverer End UE), user information for the T-End UE (target End UE or discoverer End UE), user information for U2U relay_1, user information for U2U relay_4, and / or RSC.

[0118] exist Figure 3 In the example 307, when the T-End UE receives a U2U relay request message via a U2U relay to discover the T-End UE from the S-End UE, it can select a U2U relay from among the multiple U2U relays that sent the U2U relay request message from the S-End UE (e.g., Figure 3 In the example, the T-End UE selects U2U relay_4, for example, based on the link quality of the received messages. The T-End UE can send a U2U relay response message to the selected U2U relay (e.g., U2U relay_4), which includes user information of the S-End UE (source End UE or discoverer End UE), user information of the T-End UE (target End UE or discoverer End UE), user information of U2U relay_1, user information of U2U relay_4, and / or RSC.

[0119] like Figure 3 As shown in the example, in step 308, when a U2U relay response message is received from the T-End UE, U2U relay_4 can send a response message to U2U relay_1 based on routing information to establish a connection between U2U relay_4 and U2U relay_1. This response message may include user information of the S-End UE (source End UE or discoverer End UE), user information of the T-End UE (target End UE or discoverer End UE), user information of U2U relay_1, user information of U2U relay_4, and / or RSC.

[0120] exist Figure 3 In the example, at 309, when a U2U relay response message is received from a T-End UE via another U2U relay (or after receiving it), U2U relay_1 can send a response message to the S-End UE. This response message may include user information for the S-End UE (source End UE or discoverer End UE), user information for the T-End UE (target End UE or discoverer End UE), user information for U2U relay_1, user information for U2U relay_4, and / or RSC. Upon receiving the U2U relay response message, the S-End UE can store the user information for U2U relay_1, U2U relay_4, and the T-End UE, indicating the appropriate U2U relay in the path for communication with the T-End UE via the U2U relay.

[0121] Some example embodiments may involve or include U2U relay discovery using Model A for sharing End UEs in proximity. In one embodiment, a U2U relay may send an announcement message having (e.g., indicating or including) a list of direct discovery sets including user information of End UEs, based on information received from other U2U relays. According to one embodiment, when including a list of direct discovery sets received from other U2U relays, the user information of the U2U relay may be included to indicate that End UEs in the direct discovery set are in the proximity range of the U2U relay. In one embodiment, when receiving an announcement message from a U2U relay, the source End UE may store the U2U relay information along with the list of direct discovery sets. According to one embodiment, when sending a Direct Communication Request (DCR) to a target End UE, the U2U relay may include the user information of the U2U relay received in an announcement message or response message for Model B discovery.

[0122] Some example embodiments may involve or include an initial connection establishment process with a MANET-based U2U relay network. In one embodiment, when the S-End UE sends a DCR message for communication with the T-End UE, it may include a process for routing the DCR message to the first U2U relay of the T-End UE via a U2U relay (as the U2U relay at the discovering UE, for example, Figure 3 User information of U2U relay 1) and the second U2U relay (as the U2U relay at the discovered UE, for example, Figure 3 User information of U2U relay_4. According to one embodiment, when a DCR message is received from the S-End UE, U2U relay_1 can forward the DCR to U2U relay_4 based on routing information. In one embodiment, when the T-End UE sends a Direct Communication Acceptance (DCA) message as a response to a DCR from the S-End UE, it can include user information of both U2U relay_1 and U2U relay_4, which can be used to route the DCA message to the S-End UE via the U2U relay. According to one embodiment, when a DCA message is received from the T-End UE, U2U relay_4 can forward the DCA to U2U relay_1 based on routing information.

[0123] Figure 4 An example flowchart of a method 400 for or relating to relay discovery in a mobile ad hoc network (MANET) according to some embodiments is shown. Figure 4 Example method 400 and the disclosure appended herein may include, may be based on, or may be a combination of various embodiments or elements discussed in detail above.

[0124] For ease of explanation and simplicity, for example, Figure 4Examples can be found in the text above. Figure 1A-1D Describe the architecture or system described. However, Figure 4 The example method 400 described herein can also be implemented using different architectures. According to some embodiments, Figure 4 Method 400 can be executed or implemented by the UE or WTRU, such as the WTRU 102 described above or Figure 2-3 The example shows a WTRU (i.e., a U2U relay).

[0125] It should be noted that, Figure 4 Method 400 may include further steps, processes, or details, as discussed in detail elsewhere in this disclosure. Figure 4 Method 400 can be modified to include any steps, processes, elements, and / or details shown and / or discussed above or below. For example, it has already been discussed in detail above. Figure 4 Additional details regarding information, parameters, messages, signaling, configuration, etc., as described in the document.

[0126] In addition, it should be noted that it is possible to [do something related to] Figure 4 The methods and / or blocks may be modified to include, or be replaced by, any or one of the processes, elements, or blocks discussed elsewhere herein. Therefore, those skilled in the art will understand that Figure 4 It is provided as an example, and modifications to it are possible, while remaining within the scope of certain example embodiments.

[0127] like Figure 4 As illustrated in the example, method 400 may include receiving configuration information at 410 indicating a relay service code (RSC) associated with a mobile ad hoc network. At 420, method 400 may include joining or connecting to the mobile ad hoc network based on the relay service code (RSC). Method 400 may include, at 430, receiving a first relay request message from a first WTRU to discover a second WTRU. The first relay request message may include any one or more of user information associated with the first WTRU, user information associated with the second WTRU, and / or the relay service code (RSC). In some embodiments, the WTRU-to-WTRU relay performing method 400 may be selected as a flooded multipoint relay (MPR).

[0128] exist Figure 4In one example, the method may include sending a second relay request message at 440, the second relay request message being intended for delivery to any one of the WTRUs in the vicinity of the WTRU-WTRU relay and / or other WTRU-WTRU relays within one hop of the WTRU-WTRU relay. The second relay request message may include a forwarding indication associated with the mobile ad hoc network and any one or more of the following: user information associated with the first WTRU, user information associated with the second WTRU, user information associated with the WTRU-WTRU relay, and / or relay service code (RSC).

[0129] like Figure 4 As shown in the example, method 400 may include receiving a first relay response message at 450. The first relay response message may include any one or more of the following: user information associated with a first WTRU, user information associated with a second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with the WTRU-to-WTRU relay from which the relay response message was received, and / or relay service code (RSC).

[0130] exist Figure 4 In one example, method 400 may include sending a second relay response message to the first WTRU at 460. The second relay response message may include any one or more of the following: user information associated with the first WTRU, user information associated with the second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with the WTRU-to-WTRU relay from which the relay response message was received, and / or relay service code (RSC).

[0131] In an embodiment, if the first relay request message does not include user information associated with another WTRU-to-WTRU relay, method 400 may include adding the user information associated with the WTRU-to-WTRU relay to the second relay request message.

[0132] In one embodiment, if the first relay request message includes user information associated with another WTRU-to-WTRU relay, the method may include replacing the user information associated with the other WTRU-to-WTRU relay in a second relay request message with the user information associated with the WTRU-to-WTRU relay.

[0133] In one embodiment, if the WTRU-to-WTRU relay is a flooded multipoint relay (MPR), the first relay request message may include a forwarding indication associated with the mobile ad hoc network to instruct the WTRU-to-WTRU relay to send the second relay request message to any one or more WTRUs in the vicinity of the WTRU-to-WTRU relay and / or other WTRU-to-WTRU relays within one hop of the WTRU-to-WTRU relay.

[0134] In one embodiment, if the first relay request message includes a forwarding indication associated with a mobile ad hoc network, then the forwarding indication associated with the mobile ad hoc network may be included in the second relay request message.

[0135] In one embodiment, if the first relay request message does not include a forwarding indication associated with a mobile ad hoc network, then method 400 may include discarding the first relay request message.

[0136] In one embodiment, method 400 may include providing routing information associated with a WTRU-to-WTRU relay in a mobile ad hoc network. The routing information may include information indicating how other WTRU-to-WTRU relays can connect to the WTRU-to-WTRU relay.

[0137] In one embodiment, the first WTRU may be a source WTRU, a discoverer WTRU, or another WTRU-to-WTRU relay. In one embodiment, the second WTRU may be a target WTRU, a discoverer WTRU, or a discovered WTRU.

[0138] Some example embodiments may include a relay discovery method using MANET topology information, which may be implemented in a Wireless Transmit / Receive Unit (WTRU) to WTRU relay. In some embodiments, the method may include one or more steps performed by or associated with a UE-to-UE relay, as discussed elsewhere herein, such as regarding Figure 2 and / or Figure 3 As described or shown. For example, the WTRU-to-WTRU relay implementing this method may be or may include one or more of U2U relay_1, U2U relay_2, U2U relay_3 and / or U2U relay_4. It should also be understood that one or more of the steps in this method may be optional, may be omitted, and / or may be performed in a different order.

[0139] In one embodiment, the method may include receiving configuration information indicating a relay service code (RSC) associated with a Mobile Ad Hoc Network (MANET), and joining the MANET based on the relay service code (RSC). The method may include receiving a first relay request message from a first WTRU to discover a second WTRU. The first relay request message may include or indicate any one of user information associated with the first WTRU, user information associated with the second WTRU, and / or the relay service code (RSC). In some examples, the first WTRU may be a source WTRU, a discovering WTRU, or another WTRU-to-WTRU relay. In some examples, the second WTRU may be a target WTRU, a discovered WTRU, or a discovered WTRU.

[0140] In one embodiment, the method may include sending a second relay request message intended for any one and / or another WTRU-WTRU relay within the vicinity of the WTRU-WTRU relay, such other WTRU-WTRU relays being, for example, within one hop (or next hop) of the WTRU-WTRU relay. The second relay request message may include or indicate any one of the following: user information associated with a first WTRU, user information associated with a second WTRU, user information associated with one or more WTRU-WTRU relays, and / or relay service code (RSC).

[0141] In one embodiment, the method may include receiving a first relay response message, the first relay response message including or indicating any one of the following: user information associated with a first WTRU, user information associated with a second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with a WTRU-to-WTRU relay from which the relay response message was received, and / or relay service code (RSC).

[0142] In one embodiment, the method may include sending a second relay response message to a first WTRU. For example, the second relay response message may include or indicate any one of the following: user information associated with the first WTRU, user information associated with the second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with the WTRU-to-WTRU relay from which the relay response message was received, and / or relay service code (RSC).

[0143] In one embodiment, if the first relay request message does not include user information associated with another WTRU-to-WTRU relay, the method may include adding (or otherwise including, indicating, or incorporating) the user information associated with the WTRU-to-WTRU relay to the second relay request message.

[0144] In one embodiment, where the first relay request message includes user information associated with another WTRU-to-WTRU relay (e.g., a second, third, and / or fourth WTRU-to-WTRU relay), the method may include replacing the user information associated with the other WTRU-to-WTRU relay in the second relay request message with the user information associated with the WTRU-to-WTRU relay.

[0145] In one embodiment, when a WTRU-to-WTRU relay is selected as a flooded multipoint relay (MPR), the first relay request message may further include or indicate a forwarding indication associated with the mobile ad hoc network (e.g., MANET_forwarding_indication).

[0146] In one embodiment, where the first relay request message includes or indicates a forwarding indication associated with a mobile ad hoc network (e.g., MANET_forwarding_indication), the method may include incorporating or including the forwarding indication associated with the mobile ad hoc network into a second relay request message.

[0147] In one embodiment, if the first relay request message does not include a forwarding indication associated with a mobile ad hoc network (e.g., MANET_forwarding_indication), the method may include discarding the first relay request message.

[0148] In one embodiment, the method may include providing routing information associated with a WTRU-to-WTRU relay within / to a mobile ad hoc network (e.g., other WTRUs associated with a MANET share routing information associated with a WTRU-to-WTRU relay). For example, the routing information may include or indicate information that suggests how other WTRU-to-WTRU relays can connect to the WTRU-to-WTRU relay.

[0149] Some example embodiments may include a method for relay discovery using dedicated signaling messages for exchanging discovery information between WTRU-WTRU relays, a method that can be implemented in a Radio Transmit / Receive Unit (WTRU) to WTRU relay. In some embodiments, the method may include one or more steps performed by or associated with a UE-to-UE relay, as discussed elsewhere herein, such as regarding Figure 2 and / or Figure 3As described or shown. For example, the WTRU-to-WTRU relay implementing this method may be or may include one or more of U2U relay_1, U2U relay_2, U2U relay_3 and / or U2U relay_4. It should also be understood that one or more of the steps in this method may be optional, may be omitted, and / or may be performed in a different order.

[0150] In one embodiment, the method may include joining a Mobile Ad Hoc Network (MANET) based on a configured Relay Service Code (RSC). According to some embodiments, a WTRU-to-WTRU relay may be a flooded multipoint relay (MPR).

[0151] In one embodiment, the method may include receiving first information from a first WTRU indicative of a first relay request message to discover a second WTRU. In some examples, the first relay request message may include or indicate any information associated with the first WTRU, user information associated with the second WTRU, and / or the relay service code (RSC). In some examples, the first WTRU may be a source WTRU, a discovering WTRU, or another WTRU-to-WTRU relay. In some examples, the second WTRU may be a target WTRU, a discovered WTRU, or a discovered WTRU.

[0152] In one embodiment, the method may include sending second information indicating a second relay request message to one or more WTRUs in the vicinity of a WTRU-to-WTRU relay. According to some examples, the second relay request message may include or indicate any one of the following: user information associated with a first WTRU, user information associated with a second WTRU, user information associated with a WTRU-to-WTRU relay, and / or relay service code (RSC).

[0153] In one embodiment, the method may include sending third information to other WTRU-WTRU relays within one hop of the WTRU-WTRU relay, the third information indicating information associated with the first relay request message. According to some examples, the third information may include or indicate any information such as user information associated with the first WTRU, user information associated with the second WTRU, user information associated with the WTRU-WTRU relay, and / or relay service code (RSC).

[0154] In one embodiment, the method may include receiving a first relay response message from a second WTRU based on user information associated with the WTRU-to-WTRU relay. According to some examples, the first relay response message may include or indicate any information from the user information associated with the first WTRU, the user information associated with the second WTRU, the user information associated with the WTRU-to-WTRU relay, the user information associated with at least one WTRU-to-WTRU relay from which the relay response message was received, and / or any information in the relay service code (RSC).

[0155] In one embodiment, the method may include sending a second relay response message to a first WTRU. According to some examples, the second relay response message may include or indicate any one of the following: user information associated with the first WTRU, user information associated with the second WTRU, user information associated with a WTRU-to-WTRU relay, user information associated with at least one WTRU-to-WTRU relay from which the relay response message was received, and / or relay service code (RSC).

[0156] While features and elements have been provided above in specific combinations, those skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. This disclosure is not limited to the specific embodiments described herein, which are intended as illustrative of various aspects. Many modifications and variations can be made without departing from its spirit and scope, as will be apparent to those skilled in the art. Unless expressly provided so, no element, action, or instruction used in the description of this application should be construed as essential or indispensable to the invention. Based on the foregoing description, functionally equivalent methods and apparatuses within the scope of this disclosure, other than those listed herein, will be apparent to those skilled in the art. These modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only by the terminology of the appended claims and the full scope of their equivalents. It should be understood that this disclosure is not limited to any particular method or system.

[0157] In some of the example embodiments described herein, the information (e.g., configuration) may be described as being received by the WTRU from the network, for example, via system information or via any kind of protocol message. Although not explicitly mentioned throughout the embodiments described herein, the same information (e.g., configuration) may be pre-configured in the WTRU (e.g., via any kind of pre-configuration method, such as, for example, via factory settings) so that the information (e.g., configuration) can be used by the WTRU without being received from the network.

[0158] Any feature, variation, or embodiment of the method is compatible with apparatus including a mechanism for processing the disclosed method, such as apparatus including a processor configured for processing the disclosed method, a computer program product including program code instructions, and a non-transitory computer-readable storage medium storing program instructions.

[0159] For simplicity, the foregoing embodiments have been discussed in terms of terminology and structure relating to devices with infrared functionality (i.e., infrared transmitters and receivers). However, the embodiments discussed are not limited to these systems, but can be applied to other systems that use other forms of electromagnetic waves or non-electromagnetic waves (such as sound waves).

[0160] It should also 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 "image" may mean any of a snapshot, a single image, and / or multiple images displayed on a time basis. As another example, when referred to herein, the term "user equipment" and its abbreviation "UE," the term "remote," and / or the term "head-mounted display" or its abbreviation "HMD" may mean or include (i) a wireless transmitting and / or receiving unit (WTRU); (ii) any of several embodiments of a WTRU; (iii) a device having wireless and / or wired (e.g., tetherable) capabilities configured with some or all of the structure and functions of a WTRU; (iii) a device having wireless and / or wired capabilities configured with fewer than all the structure and functions of a WTRU; or (iv) the like. Figure 1A-1D Details of an example WTRU that may represent any WTRU described herein are provided. As another example, the various disclosed embodiments herein are described above and below as utilizing a head-mounted display. Those skilled in the art will recognize that devices other than head-mounted displays can be utilized, and some or all of this disclosure and the various disclosed embodiments can be modified accordingly without excessive experimentation. Examples of such other devices may include drones or other devices configured to stream information to provide an adaptive, realistic experience.

[0161] Furthermore, the methods described herein can be implemented in computer programs, 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 via a wired or wireless connection) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, 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 optical discs (DVDs)). The processor associated with the software can be used to implement a radio frequency transceiver for a WTRU, UE, terminal, base station, RNC, or any host computer.

[0162] Variations of the methods, apparatus, and systems provided above are possible without departing from the scope of the invention. Given the various embodiments that can be applied, it should be understood that the illustrated embodiments are merely examples and should not be construed as limiting the scope of the following claims. For example, embodiments provided herein include handheld devices that may include or be used with any suitable voltage source (such as a battery) that provides any suitable voltage.

[0163] Furthermore, in the embodiments provided above, references to processing platforms, computing systems, controllers, and other devices including processors are mentioned. These devices may include at least one central processing unit (“CPU”) and memory. In accordance with the practice of those skilled in the art of computer programming, references to symbolic representations of actions and operations or instructions can be executed by various CPUs and memories. Such actions and operations or instructions may be referred to as “executed,” “computer-executed,” or “CPU-executed.”

[0164] Those skilled in the art will understand that the actions and symbols representing operations or instructions include the CPU's manipulation of electrical signals. The electrical system represents data bits, which can lead to the final transformation or reduction of electrical signals and the retention of data bits at memory locations in the memory system, thereby reconfiguring or otherwise altering the CPU's operation and performing other signal processing. The memory location holding the data bits is a physical location having specific electrical, magnetic, optical, or organic properties corresponding to or representing the data bits. It should be understood that the embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided methods.

[0165] Data bits can also be stored on a computer-readable medium, including disks, optical disks, and any other CPU-readable volatile (e.g., random access memory (“RAM”) or non-volatile (e.g., read-only memory (“ROM”) mass storage system. The computer-readable medium can include cooperative or interconnected computer-readable media that are uniquely present on the processing system or distributed across multiple interconnected processing systems, which can be local or remote relative to the processing system. It should be understood that the embodiments are not limited to the memory described above, and other platforms and memories can support the provided methods.

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

[0167] There is little difference between hardware and software implementations of various aspects of the system. The use of hardware or software typically (but not always, as the choice between hardware and software can become important in certain contexts) represents a design choice that weighs cost against efficiency. Various media (e.g., hardware, software, and / or firmware) may exist to implement the processes and / or systems and / or other technologies described herein, and the preferred media can vary depending on the context in which the processes and / or systems and / or other technologies are deployed. For example, if the implementer determines that speed and accuracy are most important, the implementer may choose a media that is primarily hardware and / or firmware. If flexibility is most important, the implementer may choose a primarily software implementation. Alternatively, the implementer may choose some combination of hardware, software, and / or firmware.

[0168] The foregoing detailed description has illustrated various embodiments of the device and / or process using block diagrams, flowcharts, and / or examples. Where such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, those skilled in the art will understand that each function and / or operation within such block diagrams, flowcharts, or examples can be implemented individually and / or collectively by a wide range of hardware, software, firmware, or virtually any combination thereof. In embodiments, several portions of the subject matter described herein can be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integration formats. However, those skilled in the art will recognize that some aspects of the embodiments disclosed herein can be equivalently implemented in an integrated circuit, in whole or in part, as one or more computer programs (e.g., one or more programs running on one or more computer systems), one or more programs running on one or more processors (e.g., one or more programs running on one or more microprocessors), firmware, or virtually any combination thereof, and that designing circuits and / or writing code for software and / or firmware according to this disclosure will be entirely within the technical scope of those skilled in the art. Furthermore, those skilled in the art will understand that the mechanisms of the subject matter described herein can be distributed as a program product in various forms, and that the illustrative embodiments of the subject matter described herein are applicable regardless of the specific type of signal-bearing medium used to actually perform such distribution. Examples of signal-bearing media include, but are not limited to, the following: recordable media (such as floppy disks, hard disks, CDs, DVDs, digital magnetic tapes, computer memory, etc.); and transmission media (such as digital and / or analog communication media (e.g., fiber optic cables, waveguides, wired communication links, wireless communication links, etc.)).

[0169] Those skilled in the art will recognize that it is common practice in the art to describe devices and / or processes in the manner set forth herein, and subsequently to use engineering practice 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 can be integrated into a data processing system through a reasonable amount of experimentation. Those skilled in the art will recognize that a typical data processing system generally includes one or more of the following: a system unit enclosure; a video display device; memory, such as volatile and non-volatile memory; a processor, such as a microprocessor and a digital signal processor; computing entities, such as an operating system, drivers, a graphical user interface, and applications; one or more interactive devices, such as a touchpad or screen; and / or a control system, including feedback loops and control motors (e.g., feedback for sensing position and / or speed, control motors for moving and / or adjusting components and / or quantities). A typical data processing system can be implemented using any suitable commercially available components, such as those commonly found in data computing / communication and / or network computing / communication systems.

[0170] The subjects described herein are sometimes illustrated with different components included within or connected to different other components. It should be understood that such depicted architectures are merely examples, and many other architectures can in fact achieve the same functionality. Conceptually, any arrangement of components achieving the same function is effectively “associated” so that the desired function can be achieved. Therefore, any two components combined herein to achieve a particular function can be considered “associated” with each other so that the desired function can be achieved, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired function. Specific examples of operably coupled components include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or logically interact and / or logically interact.

[0171] Regarding virtually any plural and / or singular terms used herein, those skilled in the art can appropriately convert them from plural to singular and / or from singular to plural depending on the context and / or application. For clarity, various singular / plural permutations may be explicitly listed herein.

[0172] Those skilled in the art will understand that, in general, the terminology used herein, and especially in the appended claims (e.g., the body of the appended claims), is intended to be “open-ended” (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will further understand that if it is intended to specify a particular number of introduced claim subjects, such intention will be explicitly stated in the claims, and if no such subject is present, such intention will not exist. For example, the term “single” or similar language may be used where only one item is anticipated. To aid understanding, the appended claims and / or the description herein may include the use of the introductory phrases “at least one” and “one or more” to introduce claim subjects. However, the use of such phrases should not be construed as implying that any particular claim including such introduced claim subject matter is limited to including only one embodiment of such claim subject matter by the indefinite article “a” or “an”, even when the same claim includes the introductory phrase “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” or “an” should be interpreted as meaning “at least one” or “one or more”). The same applies to the use of definite articles for introducing claim subject matter. Furthermore, even when a specific number of introduced claim subject matter is explicitly stated, those skilled in the art will recognize that such a statement should be interpreted as meaning at least the stated number (e.g., in the absence of other modifiers, a bare statement of “two subject matter” means at least two subject matter, or two or more subject matter). Furthermore, in instances where the convention of "at least one of A, B, and C" is used, generally speaking, this construction implies that a person skilled in the art will understand that the convention (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having both A and B, having both A and C, having both B and C, and / or having both A, B, and C). In instances where the convention of "at least one of A, B, or C" is used, generally speaking, this construction implies that a person skilled in the art will understand that the convention (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having both A and B, having both A and C, having both B and C, and / or having both A, B, and C). A person skilled in the art will further understand that, in fact, any separate words and / or phrases presenting two or more alternative terms, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one term, any one of the terms, or both terms.For example, the phrase “A or B” will be understood to include the possibility of “A” or “B” or “A and B”. Furthermore, as used herein, the term “any one of…” followed by a list of multiple items and / or multiple item categories is intended to include items and / or item categories individually or in combination with other items and / or other item categories, “any one of…”, “any combination of…”, “any multiple of…”, and / or “any combination of multiples of…”. Furthermore, as used herein, the term “set” is intended to include any number of items, including zero. Furthermore, as used herein, the term “quantity” is intended to include any quantity, including zero. And, as used herein, the term “many” is intended to be synonymous with “multiple”.

[0173] Furthermore, in the case of the description of features or aspects of this disclosure in accordance with the Markush Group, those skilled in the art will recognize that this disclosure is therefore also described in accordance with any individual member of the Markush Group or a subgroup of its members.

[0174] As those skilled in the art will understand, for any and all purposes (such as for providing a written description), all scopes disclosed herein also encompass any and all possible subscopes and combinations thereof. Any listed scope can be readily identified as sufficiently descriptive and such that the same scope can be divided into at least two equal halves, thirds, quarters, fifths, tenths, etc. As a non-limiting example, each scope discussed herein can be readily divided into a lower third, a middle third, and an upper third, etc. As those skilled in the art will also understand, all language such as “at most,” “at least,” “greater than,” “less than,” etc., includes the referenced number and refers to a scope that can subsequently be divided into subscopes as discussed above. Finally, as those skilled in the art will understand, a scope includes each individual member. Thus, for example, a group having 1 to 3 cells refers to a group having 1, 2, or 3 cells. Similarly, a group having 1 to 5 cells refers to a group having 1, 2, 3, 4, or 5 cells, and so on.

[0175] Furthermore, unless otherwise stated, the claims should not be construed as being limited to the order or elements provided. Additionally, the use of the term "means for..." in any claim is intended to invoke the claim format of 35 USC §112, ¶ 6 or means plus function, and any claim without the term "means for..." is not intended to be so.

[0176] Although various embodiments have been described based on the communication system, it is anticipated that the system can be implemented in software on a microprocessor / general-purpose computer (not shown). In some embodiments, the functionality of one or more of the various components can be implemented in software that controls the general-purpose computer.

[0177] Furthermore, although some exemplary embodiments have been illustrated and described herein, the invention is not intended to be limited to the details shown. Rather, various modifications and variations can be made with respect to the details shown within the scope of the claims and their equivalents without departing from the spirit or scope of the invention.

Claims

1. A method implemented in a wireless transmit / receive unit (WTRU) to WTRU relay, the method comprising: Receive configuration information indicating the Relay Service Code (RSC) associated with the mobile ad hoc network; Connect to the mobile ad hoc network based on the relay service code (RSC); A first relay request message is received from a first WTRU to discover a second WTRU, wherein the first relay request message includes any one of a first user information associated with the first WTRU, a second user information associated with the second WTRU, and the relay service code (RSC), wherein the WTRU-to-WTRU relay is selected as a flooded multipoint relay (MPR). Send a second relay request message, the second relay request message being intended to be sent to any of the WTRUs in the vicinity of the WTRU-WTRU relay and any of the other WTRU-WTRU relays within one hop of the WTRU-WTRU relay, wherein the second relay request message includes a forwarding indication associated with the mobile ad hoc network and any of the following: first user information associated with the first WTRU, second user information associated with the second WTRU, third user information associated with the WTRU-WTRU relay, and the relay service code (RSC); Receive a first relay response message, the first relay response message including any one of the following: first user information associated with the first WTRU, second user information associated with the second WTRU, third user information associated with the WTRU-to-WTRU relay, fourth user information associated with the WTRU-to-WTRU relay from which the relay response message was received, and the relay service code (RSC); and Send a second relay response message to the first WTRU, wherein the second relay response message includes any one of the following: first user information associated with the first WTRU, second user information associated with the second WTRU, third user information associated with the WTRU-WTRU relay, fourth user information associated with the WTRU-WTRU relay from which the relay response message was received, and the relay service code (RSC).

2. The method according to claim 1, wherein, If the first relay request message does not include user information associated with another WTRU-to-WTRU relay, the method includes adding the third user information associated with the WTRU-to-WTRU relay to the second relay request message.

3. The method according to claim 1, wherein, If the first relay request message includes user information associated with another WTRU-to-WTRU relay, the method includes replacing the user information associated with the other WTRU-to-WTRU relay in the second relay request message with third user information associated with the WTRU-to-WTRU relay.

4. The method according to any one of claims 1-3, wherein, In the case that the WTRU-to-WTRU relay is a flooded multipoint relay (MPR), the first relay request message also includes a forwarding indication associated with the mobile ad hoc network to instruct the WTRU-to-WTRU relay to send the second relay request message to any of the WTRUs in the vicinity of the WTRU-to-WTRU relay and any of the other WTRU-to-WTRU relays within one hop of the WTRU-to-WTRU relay.

5. The method according to any one of claims 1-4, wherein, If the first relay request message includes a forwarding indication associated with the mobile ad hoc network, the method includes including a forwarding indication associated with the mobile ad hoc network in the second relay request message.

6. The method according to any one of claims 1-4, wherein, If the first relay request message does not include a forwarding indication associated with the mobile ad hoc network, the method includes discarding the first relay request message.

7. The method according to any one of claims 1-6, comprising providing routing information associated with the WTRU-WTRU relay in the mobile ad hoc network.

8. The method according to claim 7, wherein, The routing information includes information indicating how other WTRU-WTRU relays can connect to the WTRU-WTRU relay.

9. The method according to any one of claims 1-8, wherein the first WTRU includes a source WTRU, a discoverer WTRU, or another WTRU-to-WTRU relay, and wherein the second WTRU includes a target WTRU, a discoverer WTRU, or a discovered WTRU.

10. A Wireless Transmit / Receive Unit (WTRU) to WTRU relay, comprising: The circuit, including any one of a processor, memory, transmitter, and receiver, is configured to: Receive configuration information indicating the Relay Service Code (RSC) associated with the mobile ad hoc network; Connect to the mobile ad hoc network based on the relay service code (RSC); A first relay request message is received from a first WTRU to discover a second WTRU, wherein the first relay request message includes any one of a first user information associated with the first WTRU, a second user information associated with the second WTRU, and the relay service code (RSC), wherein the WTRU-to-WTRU relay is selected as a flooded multipoint relay (MPR). Send a second relay request message, the second relay request message being intended to be sent to any of the WTRUs in the vicinity of the WTRU-WTRU relay and any of the other WTRU-WTRU relays within one hop of the WTRU-WTRU relay, wherein the second relay request message includes a forwarding indication associated with the mobile ad hoc network, and any of the following: first user information associated with the first WTRU, second user information associated with the second WTRU, third user information associated with the WTRU-WTRU relay, and any of the relay service codes (RSCs); Receive a first relay response message, the first relay response message including any one of the following: first user information associated with the first WTRU, second user information associated with the second WTRU, third user information associated with the WTRU-to-WTRU relay, fourth user information associated with the WTRU-to-WTRU relay from which the relay response message was received, and the relay service code (RSC); and Send a second relay response message to the first WTRU, wherein the second relay response message includes any one of the following: first user information associated with the first WTRU, second user information associated with the second WTRU, third user information associated with the WTRU-WTRU relay, fourth user information associated with the WTRU-WTRU relay from which the relay response message was received, and the relay service code (RSC).

11. The WTRU of claim 10, configured to: add third user information associated with the WTRU-WTRU relay to the second relay request message if the first relay request message does not include user information associated with another WTRU-WTRU relay.

12. The WTRU of claim 10, configured to: in the case that the first relay request message includes user information associated with another WTRU-to-WTRU relay, replace the user information associated with the other WTRU-to-WTRU relay in the second relay request message with third user information associated with the WTRU-to-WTRU relay.

13. The WTRU according to any one of claims 10-12, wherein, In the case that the WTRU-to-WTRU relay is a flooded multipoint relay (MPR), the first relay request message also includes a forwarding indication associated with the mobile ad hoc network, indicating that the WTRU-to-WTRU relay should send the second relay request message to any of the WTRUs in the vicinity of the WTRU-to-WTRU relay and any of the other WTRU-to-WTRU relays within one hop of the WTRU-to-WTRU relay.

14. The WTRU according to any one of claims 10-13, configured to include a forwarding indication associated with the mobile ad hoc network in the second relay request message, provided that the first relay request message includes a forwarding indication associated with the mobile ad hoc network.

15. The WTRU according to any one of claims 10-13, configured to discard the first relay request message if the first relay request message does not include a forwarding indication associated with the mobile ad hoc network.

16. The WTRU according to any one of claims 10-15, configured to: provide routing information associated with the WTRU-WTRU relay in the mobile ad hoc network.

17. The WTRU of claim 16, wherein the routing information includes information indicating how other WTRU-WTRU relays connect to the WTRU-WTRU relay.

18. The WTRU according to any one of claims 10-17, wherein the first WTRU includes a source WTRU, a discoverer WTRU, or another WTRU-to-WTRU relay, and wherein the second WTRU includes a target WTRU, a discoverer WTRU, or a discovered WTRU.