Method, apparatus, and system for enabling indirect-to-direct path switching in Layer-3 (L3) user equipment (UE)-UE relays.

The implementation of path switching methods in Layer-3 UE-to-UE relays using DCR and DSM messages addresses inefficiencies in existing systems, enhancing network performance and resource utilization.

JP7953979B2Active Publication Date: 2026-11-19INTERDIGITAL PATENT HOLDINGS INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2024506934
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2021-08-06
Filing Date
2022-08-03
Publication Date
2026-11-19
Estimated Expiration
2042-08-03

AI Technical Summary

Technical Problem

Existing wireless communication systems face inefficiencies in switching between indirect and direct paths in Layer-3 UE-to-UE relays, leading to suboptimal performance and resource utilization.

Method used

Implementing methods, apparatuses, and systems for enabling seamless switching between indirect and direct paths in Layer-3 UE-to-UE relays, utilizing signaling mechanisms such as Direct Communication Request (DCR) and Direct Security Mode (DSM) messages to establish direct links and facilitate path switching.

Benefits of technology

Enhances communication efficiency by optimizing path selection in UE-to-UE relays, improving resource utilization and performance in wireless networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007953979000001
    Figure 0007953979000001
  • Figure 0007953979000002
    Figure 0007953979000002
  • Figure 0007953979000003
    Figure 0007953979000003
Patent Text Reader

Abstract

A method, an apparatus, and a system are disclosed. One method may be performed by a first wireless transmit / receive unit (WTRU) that has established an indirect link with a second WTRU. The method may include performing a discovery procedure and detecting that the second WTRU is directly reachable based on a result of the performed discovery procedure. The method may further include initiating establishment of the direct link, exchanging the indirect link to a direct link, and communicating with the second WTRU by the first WTRU using the established direct link after the exchange.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Provisional Patent Application No. 63 / 230334, filed on August 6, 2021. The content of this prior application is hereby incorporated by reference in its entirety into this specification.

[0002] (FIELD OF THE INVENTION) The embodiments disclosed herein relate generally to wireless communications, for example, to path switching between indirect and direct paths in Layer-3 UE-to-UE relay Switching or path switching between direct and indirect paths Switching methods, apparatuses, and systems for enabling the same. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] A more detailed understanding may be given from the following detailed description, by way of example, taken in conjunction with the accompanying drawings. The drawings in the description are exemplary embodiments. Accordingly, the drawings and detailed description are not to be regarded as limiting, and other equally effective embodiments are possible and are highly probable. Furthermore, like reference numerals in the drawings denote like elements. [Figure 1A] is a system diagram illustrating an exemplary communication system in which one or more disclosed embodiments may be implemented. [Figure 1B] is a system diagram illustrating an exemplary wireless transmit / receive unit (WTRU) that may be used within the communication system illustrated in FIG. 1A, in accordance with an embodiment. [Figure 1C] is a system diagram illustrating an exemplary radio access network (RAN) and an exemplary core network (CN) that may be used within the communication system illustrated in FIG. 1A, in accordance with an embodiment. [Figure 1D]This is a system diagram illustrating further representative RANs and further representative CNs that may be used in the communication system illustrated in Figure 1A according to one embodiment. [Figure 2] This diagram illustrates a typical UE-UE relay using IP routing. [Figure 3] This diagram illustrates a typical Layer 3-based UE-UE relay reselection. [Figure 4] For example, the diagram illustrates a typical indirect-to-direct route switching triggered during direct link establishment using a message. [Figure 5] For example, the diagram illustrates a typical indirect-to-direct path switching triggered after a direct link is established, using the PC5 signaling transmission message. [Figure 6] This figure illustrates a typical indirect-to-direct route switching triggered during direct link establishment using DSM (Direct Security Mode) command messages. [Figure 7] This diagram illustrates a typical direct-to-indirect route switching scenario. [Figure 8] This flowchart illustrates a typical method. [Figure 9] This flowchart illustrates a typical method. [Figure 10] This flowchart illustrates a typical method. [Modes for carrying out the invention]

[0004] Representative network for implementing the embodiment Figure 1A illustrates a typical communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, message transmission, and broadcast to multiple wireless users. The communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communication system 100 may use one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single-Carrier FDMA (SC-FDMA), Zero-Tail Unique-Word DFT-Spread OFDM (ZT UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtering OFDM, and Filter Bank Multi Carrier (FBMC).

[0005] As shown in Figure 1A, the communication system 100 may include radio transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, the Internet 110, and other networks 112, but it will be understood that the disclosed embodiments intend 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 radio environment. For example, WTRU102a, 102b, 102c, 102d, any of which may be referred to as “station” and / or “STA (Station)”, may be configured to transmit and / or receive radio signals and may include User Equipment (UE), mobile stations, fixed subscriber units or mobile subscriber units, subscriber-based units, radio paging, mobile phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, radio sensors, hotspots or Mi-Fi devices, Internet of Things devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., for remote surgery), industrial devices and applications (e.g., robots and / or other radio devices operating in industrial and / or automated processing chain contexts), consumer electronics devices, devices operating on commercial radio networks and / or industrial radio networks, etc. WTRU102a, 102b, 102c, and 102d can all be referred to as UE for compatibility purposes.

[0006] The communication system 100 may also include base stations 114a and / or base stations 114b. Each of the base stations 114a and 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, the Internet 110, and / or other networks 112. For example, base stations 114a and 114b may be base transceiver stations (BTS), Node-B, eNode B(end), home Node B(HNB), home eNode B(HeNB), gNB, NR Node B, site controller, access point (AP), wireless router, etc. Although base stations 114a and 114b are depicted as single elements, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0007] 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 a Base Station Controller (BSC), a Radio Network Controller (RNC), and relay nodes. 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 licensed spectra, unlicensed spectra, or a combination of licensed and unlicensed spectra. Cells may provide coverage for radio services to a specific geographic area, which may be relatively fixed or change over time. Cells may be further divided into cell sectors. For example, a 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, the base station 114a may use multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0008] Base stations 114a and 114b may communicate with one or more WTRUs 102a, 102b, 102c, and 102d via the air interface 116, which may be any suitable radio communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0009] More specifically, as described above, the communication system 100 may be a multiple access system and may use one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, 102c in RAN 104 / 113 may implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117. WCDMA may include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Advanced HSPA (HSPA+). HSPA may include High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

[0010] In one embodiment, base stations 114a and WTRUs 102a, 102b, and 102c may implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0011] In one embodiment, the base station 114a and WTRUs 102a, 102b, and 102c may implement radio technologies such as NR radio access, but the technology may also establish the air interface 116 using New Radio (NR).

[0012] In one embodiment, base station 114a and WTRU 102a, 102b, 102c may implement multiple radio access technologies. For example, base station 114a and WTRU 102a, 102b, 102c may implement LTE radio access and NR radio access together, for example, using the Dual Connectivity (DC) principle. Thus, the air interface utilized by WTRU 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions transmitted to and from multiple types of base stations (e.g., eNB and gNB).

[0013] In other embodiments, base stations 114a and WTRUs 102a, 102b, and 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wireless Fidelity, WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access, WiMAX), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), and GSM EDGE (GERAN).

[0014] The base station 114b in Figure 1A may be, for example, a wireless router, home Node B, home eNode B, or access point, and may utilize any suitable RAT to facilitate wireless connectivity in local areas such as offices, homes, vehicles, campuses, industrial facilities, aerial corridors (for use by drones), roads, etc. In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). In one embodiment, the base station 114b and WTRU 102c, 102d may implement wireless technologies such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, base stations 114b and WTRUs 102c, 102d may establish picocells or femtocells using cellular-based RATs (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR, etc.). As shown in Figure 1A, base station 114b may have a direct connection to the internet 110. Therefore, base station 114b may not need to access the internet 110 via CN 106 / 115.

[0015] RAN104 / 113 may communicate with CN106 / 115, which may be any type of network configured to provide voice, data, applications, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRU102a, 102b, 102c, and 102d. The data may have various Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, and mobility requirements. CN106 / 115 may provide call control, billing services, mobile location-based services, prepaid calls, internet connectivity, video distribution, etc., and / or perform high-level security functions such as user authentication. Although not shown in Figure 1A, it will be understood that RAN104 / 113 and / or CN106 / 115 may communicate directly or indirectly with other RANs using the same RAT as RAN104 / 113 or a different RAT. For example, in addition to being connected to RAN104 / 113 which may utilize NR radio technology, CN106 / 115 may also communicate with another RAN (not shown) using GSM, UMTS, CDMA2000, WiMAX, E-UTRA, or WiFi radio technology.

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

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

[0018] Figure 1B is a system diagram illustrating a representative WTRU 102. As shown in Figure 1B, the WTRU 102 may include, among other things, 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 peripherals 138. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0019] The processor 118 may be a general purpose processor, a dedicated processor, a conventional processor, a Digital Signal Processor (DSP), a plurality of 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, or the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While Figure 1B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0020] The transmit / receive element 122 may be configured to transmit a signal to or receive a signal from a base station (e.g., base station 114a) via the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In one embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF signals and optical signals. It will be understood that the transmit / receive element 122 may be configured to transmit and / or receive any combination of radio signals.

[0021] Although the transmit / receive element 122 is depicted as a single element in Figure 1B, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may utilize MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving radio signals via the air interface 116.

[0022] The transceiver 120 may be configured to modulate the signal transmitted by the transmit / receive element 122 and to demodulate the signal received by the transmit / receive element 122. As described above, the WTRU 102 may have multiple mode capabilities. Therefore, the transceiver 120 may include multiple transceivers to enable the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11.

[0023] The processor 118 of the WTRU102 may be connected to a speaker / microphone 124, a keypad 126, and / or a display / touchpad 128 (for example, a liquid crystal display (LCD) display unit or an organic light-emitting diode (OLED) display unit), from which it may receive user input data. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. The processor 118 may also access information from any type of suitable memory, such as non-removable memory 130 and / or removable memory 132, and store data in such memory. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a Subscriber Identity Module (SIM) card, a Memory Stick, a Secure Digital (SD) memory card, etc. In other embodiments, the processor 118 may access information from memory not physically located on the WTRU 102, such as on a server or home computer (not shown), and store data in such memory.

[0024] The processor 118 may receive power from the power supply 134, but may also 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 supplying power to 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.), a solar cell, a fuel cell, etc.

[0025] 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. In addition to or instead of the information from the GPS chipset 136, the WTRU 102 may determine its location based on receiving location information from base stations (e.g., base stations 114a, 114b) via the air interface 116 and / or based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU 102 may acquire location information by any preferred location determination method while maintaining consistency with one embodiment.

[0026] The processor 118 may be further connected to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functions, and / or wired or wireless connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photos and / or videos), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a Frequency Modulated (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, a virtual reality and / or augmented reality (VR / AR) device, an activity tracker, and the like. The peripheral device 138 may include one or more sensors, one or more of which may be a gyroscope, accelerometer, Hall effect sensor, magnetometer, compass sensor, proximity sensor, temperature sensor, time sensor, geolocation sensor, altimeter, light sensor, touch sensor, magnetometer, barometer, gesture sensor, biometric sensor, and / or humidity sensor.

[0027] The processor 118 of the WTRU102 may, in order to implement a typical embodiment disclosed herein, operately communicate with various peripheral devices 138, including, for example, one or more accelerometers, one or more gyroscopes, a USB port, other communication interfaces / ports, a display and / or other visual / audio indicators.

[0028] WTRU102 may include a full-duplex radio in which the transmission and reception of some or all of the signals (e.g., associated with specific subframes for both UL (Uplink, e.g., for transmission) and downlink (e.g., for reception) may be in parallel and / or simultaneous. The full-duplex radio may include an interference management unit for reducing and / or substantially eliminating self-interference either through hardware (e.g., chokes) or signal processing via a processor (e.g., via a separate processor (not shown) or processor 118). In one embodiment, WTRU102 may include a half-duplex radio for the transmission and reception of any of the signals (e.g., associated with specific subframes for either UL (e.g., for transmission) or downlink (e.g., for reception)).

[0029] Figure 1C is a system diagram illustrating RAN104 and CN106 according to one embodiment. As described above, RAN104 may communicate with WTRU102a, 102b, and 102c via the air interface 116 using E-UTRA wireless technology. RAN104 may also communicate with CN106.

[0030] RAN104 may include eNode B160a, 160b, and 160c, but it will be understood that RAN104 may include any number of eNode B while maintaining consistency with one embodiment. Each of eNode B160a, 160b, and 160c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, eNode B160a, 160b, and 160c may implement MIMO technology. Thus, eNode B160a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU102a.

[0031] Each of the eNode B160a, 160b, and 160c may be associated with a specific cell (not shown) and may be configured to handle wireless resource management decisions, handover decisions, user scheduling, etc., in UL and / or DL. As shown in Figure 1C, the eNode B160a, 160b, and 160c may communicate with each other via the X2 interface.

[0032] The CN106 shown in Figure 1C may include a Mobility Management Entity (MME) 162, a Serving Gateway (SGW) 164, and a Packet Data Network (PDN) Gateway (or PGW) 166. Although each of the aforementioned elements is depicted as part of CN106, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0033] MME162 may be connected to each of the eNode B160a, 160b, and 160c within RAN104 via the S1 interface and may function as a control node. For example, MME162 may perform roles such as authenticating users of WTRU102a, 102b, and 102c, activating / deactivating bearers, and selecting gateways for specific services during the initial attachment of WTRU102a, 102b, and 102c. MME162 may also provide control plane functions for exchange between RAN104 and other RANs (not shown) using GSM and / or other radio technologies such as WCDMA.

[0034] SGW164 may be connected to each of the eNode B160a, 160b, and 160c in RAN104 via the S1 interface. SGW164 may generally route and forward user data packets to and from WTRU102a, 102b, and 102c. SGW164 may also perform other functions during eNode B handovers, such as anchoring the user plane, triggering paging when DL data is available to WTRU102a, 102b, and 102c, and managing and remembering the context of WTRU102a, 102b, and 102c.

[0035] SGW164 may be connected to PGW166, which may provide WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices.

[0036] CN106 may facilitate communication with other networks. For example, CN106 may provide WTRU102a, 102b, and 102c with access to a circuit-switched network such as PSTN108 to facilitate communication between WTRU102a, 102b, and 102c and conventional terrestrial line communication devices. For example, CN106 may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between CN106 and PSTN108. Furthermore, CN106 may provide WTRU102a, 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.

[0037] Although the WTRU is described as a wireless terminal in Figures 1A to 1D, in certain representative embodiments, such a terminal is intended to be able to use a wired communication interface with a communication network (for example, temporarily or permanently).

[0038] In a typical embodiment, the other network 112 may be a WLAN.

[0039] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) of the BSS and one or more stations (STAs) associated with the AP. The AP may have access to or interfaces with another type of wired / wireless network that carries traffic entering and / or leaving the Distribution System (DS) or BSS. Traffic originating outside the BSS to the STA may reach and be delivered to the STA via the AP. Traffic originating from the STA to destinations outside the BSS may be sent to the AP and then delivered to their respective destinations. Traffic between STAs within the BSS may be transmitted, for example, via the AP; a source STA may send traffic to the AP, and the AP may deliver the traffic to the destination STA. Traffic between STAs within the BSS may be considered and / or referred to as same-layer traffic. Same-layer traffic may be transmitted between the source STA and the destination STA (for example, directly between them) via a Direct Link Setup (DLS). In certain representative embodiments, the DLS may be an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using Independent BSS (IBSS) mode may not have access points (APs), and STAs (e.g., all STAs) within or using IBSS may communicate directly with one another. The IBSS mode of communication may be referred to herein as the “ad hoc” communication mode.

[0040] When using the 802.11ac infrastructure operating mode or a similar operating mode, an AP may transmit beacons on a fixed channel, such as the primary channel. The primary channel may be of a fixed width (e.g., a 20 MHz bandwidth) or a width dynamically set via signal transmission. The primary channel may be the operating channel of the BSS and may be used by the STA to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example, in an 802.11 system. In the case of CSMA / CA, the STA, including the AP (e.g., all STAs), may sense the primary channel. If the primary channel is sensed / detected and / or determined to be operational by a particular STA, that particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0041] A high-throughput (HT) STA may use a 40 MHz wide channel for communication, which may be formed, for example, via a combination of a 20 MHz primary channel and adjacent or non-adjacent 20 MHz channels.

[0042] A very high throughput (VHT) STA may support channels with widths of 20 MHz, 40 MHz, 80 MHz, and / or 160 MHz. The 40 MHz and / or 80 MHz wide channels described above may be formed by combining multiple consecutive 20 MHz channels. A 160 MHz channel may be formed by combining eight consecutive 20 MHz channels, or by combining two non-consecutive 80 MHz channels, which may be referred to as an 80+80 configuration. In the case of an 80+80 configuration, after channel coding, the data may pass through a segment parser that can split the data into two streams. Inverse Fast Fourier Transform (IFFT) processing and time-domain processing may be performed separately for each stream. The streams may be mapped to two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of a receiving STA, the operation described above for the 80+80 configuration may be reversed, and the combined data may be transmitted to Medium Access Control (MAC).

[0043] Sub-1 GHz operating modes are supported by 802.11af and 802.11ah. Channel operating bandwidth and carrier are reduced in 802.11af and 802.11ah compared to those used in 802.11n and 802.11ac. 802.11af supports bandwidths of 5 MHz, 10 MHz, and 20 MHz in the TV White Space (TVWS) spectrum, while 802.11ah supports bandwidths of 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz using the non-TVWS spectrum. According to a typical embodiment, 802.11ah may support meter-type control / machine-type communications, such as MTC devices within a macro-notification range area. MTC devices may have specific features, including support for specific and / or limited bandwidths (e.g., support only for those bandwidths). MTC devices may include batteries with battery life exceeding a threshold (e.g., to maintain very long battery life).

[0044] A WLAN system capable of supporting multiple channels and channel bandwidths such as 802.11n, 802.11ac, 802.11af, and 802.11ah includes a channel that may be designated as the primary channel. The primary channel may have a bandwidth equal to the maximum common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by an STA from among all STAs operating in a BSS that support the minimum bandwidth operating mode. In embodiments of 802.11ah, the primary channel may be 1 MHz wide for an STA (e.g., an MTC-type device) that supports (e.g., only supports) 1 MHz mode, even if other STAs in the AP and BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the state of the primary channel. For example, if the primary channel is operational due to an STA (supporting only 1 MHz operating mode) transmitting to the AP, the entire available frequency band may be considered operational, even if a large portion of the frequency band remains idle and could be available.

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

[0046] Figure 1D is a system diagram illustrating RAN113 and CN115 according to an embodiment. As described above, RAN113 may communicate with WTRU102a, 102b, and 102c via air interface 116 using NR radio technology. RAN113 may also communicate with CN115.

[0047] RAN113 may include gNB180a, 180b, and 180c, but it will be understood that RAN113 may include any number of gNBs while maintaining consistency with the embodiment. Each of gNB180a, 180b, and 180c may include one or more transceivers for communicating with WTRU102a, 102b, and 102c via the air interface 116. In one embodiment, gNB180a, 180b, and 180c may implement MIMO technology. For example, gNB180a and 180b may use beamforming to transmit and / or receive signals to and from gNB180a, 180b, and 180c. Thus, gNB180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU102a. In one embodiment, gNB180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB180a may transmit multiple component carriers to WTRU102a (not shown). A subset of these component carriers may be on the unauthorized spectrum, and the remaining component carriers may be on the authorized spectrum. In one embodiment, gNB180a, 180b, and 180c may implement coordinated multi-point (CoMP) technology. For example, WTRU102a may receive coordinated transmissions from gNB180a and gNB180b (and / or gNB180c).

[0048] WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using transmits associated with an extensible numerology. For example, OFDM symbol intervals and / or OFDM subcarrier intervals may vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using subframes or transmission time intervals (TTIs) of varying or scalable lengths (e.g., containing varying numbers of OFDM symbols and / or having varying absolute time durations).

[0049] gNB180a, 180b, and 180c may be configured to communicate with WTRU102a, 102b, and 102c in standalone and / or non-standalone configurations. In a standalone configuration, WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c without accessing other RANs (e.g., eNode B160a, 160b, and 160c). In a standalone configuration, WTRU102a, 102b, and 102c may use one or more of gNB180a, 180b, and 180c as mobility anchor points. In a standalone configuration, WTRU102a, 102b, and 102c may communicate with gNB180a, 180b, and 180c using signals in unauthorized bands. In a non-standalone configuration, WTRU102a, 102b, and 102c may communicate with and connect to gNB180a, 180b, and 180c, while also communicating with and connecting to other RANs such as eNode B160a, 160b, and 160c. For example, WTRU102a, 102b, and 102c may implement a DC principle to communicate substantially simultaneously with one or more gNB180a, 180b, and 180c and one or more eNode B160a, 160b, and 160c. In a non-standalone configuration, eNode B160a, 160b, and 160c may function as mobility anchors for WTRU102a, 102b, and 102c, while gNB180a, 180b, and 180c may provide additional reach and / or throughput for servicing WTRU102a, 102b, and 102c.

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

[0051] The CN115 shown in Figure 1D may include at least one AMF182a, 182b, at least one UPF184a, 184b, at least one Session Management Function (SMF)183a, 183b, and optionally a Data Network (DN)185a, 185b. Although each of the aforementioned elements is illustrated as part of the CN115, it will be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0052] AMF182a, 182b may be connected via the N2 interface to one or more gNB180a, 180b, 180c in RAN113 and may function as control nodes. For example, AMF182a, 182b may play roles such as user authentication for WTRU102a, 102b, 102c, support for network slicing (e.g., processing different Protocol Data Unit (PDU) sessions with different requirements), selection of SMF183a, 183b for registration, management of registration areas, termination of Non-Access Stratum (NAS) signaling, and mobility management. Network slices may be used by AMF182a, 182b to customize CN support for WTRU102a, 102b, and 102c based on the type of service utilizing WTRU102a, 102b, and 102c. For example, different network slices may be established for different use cases, such as services relying on Ultra-Reliable Low Latency Communication (URLLC) access, services relying on Enhanced Mobile Broadband (eMBB) access, services for Machine Type Communication (MTC) access, and / or similar. AMF162 may provide control plane functionality for exchange between RAN113 and other RANs (not shown) using other radio technologies such as LTE, LTE-A, LTE-A Pro, and / or WiFi.

[0053] SMF183a and 183b may be connected to AMF182a and 182b in CN115 via the N11 interface. SMF183a and 183b may also be connected to UPF184a and 184b in CN115 via the N4 interface. SMF183a and 183b may select and control UPF184a and 184b, and configure routing for traffic passing through UPF184a and 184b. SMF183a and 183b may also perform other functions, such as managing and assigning UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types may be IP-based, non-IP-based, Ethernet-based, etc.

[0054] UPF184a and 184b may be connected via the N3 interface to one or more of the gNB180a, 180b, and 180c in RAN113, thereby providing WTRU102a, 102b, and 102c with access to a packet-switched network such as the Internet 110 to facilitate communication between WTRU102a, 102b, and 102c and IP-enabled devices. UPF184 and 184b may perform other functions such as routing and forwarding packets, enforcing user plane policies, supporting multiple home PDU sessions, handling user plane QoS, buffering downlink packets, and providing mobility anchoring.

[0055] CN115 may facilitate communication with other networks. For example, CN115 may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) that functions as an interface between CN115 and PSTN108. CN115 may also provide WTRU102a, 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, WTRU102a, 102b, and 102c may be connected to local data networks (DNs) 185a and 185b via UPF184a and 184b through an N3 interface to UPF184a and 184b, and an N6 interface between UPF184a and 184b and DN185a and 185b.

[0056] In view of Figures 1A to 1D and their corresponding descriptions, one or more of the functions described herein may be performed by one or more emulation devices (not shown) with respect to one or more of the WTRU102a-d, base stations 114a-b, eNodeB160a-c, MME162, SGW164, PGW166, gNB180a-c, AMF182a-ab, UPF 184a-b, SMF 183a-b, DN185a-b, and / or any other devices described herein. The emulation devices may be one or more devices configured to emulate one or more of the functions described herein. For example, emulation devices may be used to test other devices and / or simulate network and / or WTRU functions.

[0057] Emulation devices may be designed to implement one or more tests of other devices in a laboratory and / or operator network environment. For example, one or more emulation devices may perform one or more or all functions while fully or partially implemented and / or deployed as part of a wired and / or wireless network to test other devices in a communications network. One or more emulation devices may perform one or more or all functions while temporarily implemented / deployed as part of a wired and / or wireless network. Emulation devices may be directly coupled to another device for testing purposes and / or may perform tests using terrestrial radio communication.

[0058] One or more emulation devices may perform one or more functions, including all of the above, while not implemented / deployed as part of a wired and / or wireless communication network. For example, an emulation device may be used in a test laboratory test scenario, and / or in a wired and / or wireless communication network that is not deployed (e.g., for testing) to implement testing of one or more components. One or more emulation devices may also be test equipment. Direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation device to transmit and / or receive data.

[0059] In certain representative embodiments, the methods, apparatus, and systems are, for example, indirect-to-direct pathways. Switching For this purpose, it may be implemented. For example, the source UE may include indirect link information (e.g., information) in the first message (e.g., a Direct Communication Request (DCR) message and / or a Direct Security Mode (DSM) completion message) to establish a direct link and an indirect-to-direct path. SwitchingThe source UE may initiate the process. The source UE may detect that it has an indirect link with the target UE (e.g., currently has one) when it receives a second message (e.g., a Direct Communication Accept (DCA) message for establishing a direct link). The source UE may then initiate the indirect-to-direct route by sending a third message (e.g., an updated link change request message) in and / or via the direct link, along with the indirect link information. Switching The source UE may initiate the process. The source UE may detect that it has an indirect link with the target UE (e.g., currently has one) when it receives a first message (e.g., a DCR message) from the target UE. The source UE may, for example, in a fourth message (e.g., a DSM command message), initiate the process. switching By including information (for example, information), the indirect-direct pathway Switching You may start.

[0060] In certain representative embodiments, the methods, apparatus, and systems are, for example, direct-indirect pathways. Switching This may be implemented. For example, a first UE (e.g., UE1) may, for example, send a first message (e.g., a link change request message) within and / or on a direct link to the direct-indirect path. Switching (You may start) Indication (For example, (1) "direct-indirect" Indication (2) "keep-IP-addr" Indication , (3) threshold, and / or (4) “preparation” Indication You may include any of the following. route Switching This can be performed / completed immediately after the link change procedure is completed, or may be completed when a threshold is met or the link is lost (e.g., only once). The first UE (e.g., UE1) and / or the second UE (e.g., UE2) are indirectly linked to SwitchingAfterward, you may continue to monitor link quality on and / or via the direct link. If the direct link quality has improved, the path from the indirect link to the direct link may be monitored. Switching You may perform / complete this task.

[0061] In certain representative embodiments, the methods, apparatus, and systems are, for example, capable of Switching The following may be implemented: The first UE (e.g., UE1) and the second UE (e.g., UE2) may, during the discovery procedure and / or the link establishment procedure, determine the route. Switching It may also indicate whether it supports multiple paths and / or seamless continuity.

[0062] Typical procedure for L3 UE-UE relay that may handle IP traffic. Figure 2 illustrates a typical UE-UE relay using IP routing. For L3 UE-UE relays based on IP routing, any UE that wishes to use ProSe (proximity-based service) 5G UE-UE relays may need to establish a unicast single query L2 link (e.g., a PC5 unicast single query link) with the UE-UE relay. As part of the unicast single query L2 link establishment procedure, the ProSe 5G UE-UE relay can assign an IP address / prefix prefix to the UE and may store the association of the UE's user information (e.g., user information) and / or the assigned IP address / prefix prefix in one or more Domain Name Server / System (DNS) entries of the UE. The ProSe 5G UE-UE relay may also function as a DNS server.

[0063] As illustrated in the embodiment of Figure 2, in 2-1a and 2-1b, UE-1 and UE-2 may each be configured to use a UE-UE relay. In 2-1c, the UE-UE relay may be configured to operate as a UE-UE relay. Figure 2 illustrates an embodiment that includes announcement-based UE-UE relay discovery, where the UE-UE relay may announce its UE-UE relay capability to UE-1 and / or UE-2 in 2-2. In 2-3a and 2-3b, UE-1 and UE-2 may each send a direct communication request to the UE-UE relay. In 2-4a and 2-4b, UE-1 and UE-2 may perform security establishment with the UE-UE relay. In 2-5a and 2-5b, the UE-UE relay may send a direct communication acceptance message to UE-1 and / or UE-2.

[0064] In the embodiment shown in Figure 2, in 2-6, UE-1 may send a DNS query to the UE-UE relay. The DNS query may include target user information. In 2-7, the UE-UE relay may send a DNS response to UE-1 that may include an IP address and / or prefix. In 2-8a, UE-1 may send IP data including the target IP address and / or prefix to the UE-UE relay. In 2-8b, the UE-UE relay may forward the IP data including the target IP address and / or prefix to UE-2.

[0065] In some embodiments, the UE may obtain an IP address from an entity other than the relay. In this case, the UE may register its IP address with the relay, and / or the relay may store this association. When a first UE (e.g., a source UE) needs or should communicate with another UE (e.g., a target UE), or when a first UE needs or should discover a ProSe service via the ProSe 5G UE-UE relay, the first UE may send a DNS query to the ProSe 5G UE-UE relay via a unicast single query link that can (1) return the IP address / prefix prefix of the target UE or the ProSe service for the target UE (e.g., based on the target UE's user information), or (2) return a list of IP addresses / prefix prefixes of target UEs that support the ProSe service for the ProSe service. In the first scenario, the source UE may be aware of the target UE's user information, and / or the target UE may not be aware of the source UE's user information. In the second scenario, neither the source UE nor the target UE may be aware of the user information of their respective UEs.

[0066] The source UE may send IP data, or non-IP data encapsulated in IP, to the target UE via a unicast single-lookup L2 link to a UE-UE relay that returns the target UE's IP address / prefix prefix. The UE-UE relay may act as an IP router, but may forward packets to the corresponding unicast single-lookup L2 link toward the target UE. Each of the unicast single-lookup L2 links may be treated as an IP interface.

[0067] (For example, a path between two relays using an indirect-to-indirect link) Switching Typical procedures for Figure 3 illustrates a typical Layer-3 based UE-UE relay reselection. Referring to Figure 3, a UE-UE relay reselection with two L3 relays may be used. The source UE or target UE may initiate the relay reselection procedure, but the source UE and target UE may negotiate the UE-UE relay reselection using an existing relay connection. The link change procedure (e.g., via multiple messages such as request / accept / acknowledgment messages) involves the relay reselection negotiation and the IP address to be used with the selected relay. exchange It may be used for that purpose.

[0068] As illustrated in the embodiment of Figure 3, in 3-1 and 3-1a, the source UE and the target UE may establish a PC5 unicast single query link with relay 1. Similarly, in 3-2 and 3-2a, the source UE and the target UE may establish a PC5 unicast single query link with relay 2. In 3-3, traffic forwarding between the source UE and the target UE may be performed via relay 1. In 3-4, the source UE may decide to perform relay UE reselection, but in 3-5, relay reselection to be forwarded to the target UE Indication A link change request including and / or candidate RIDs may be sent to relay 1. Then, in steps 3-6, relay 1 performs relay reselection. Indication A link change request having a candidate RID may be forwarded to the target UE. In 3-7, the target UE may select a RID, but in 3-8, a relay reselection request should be forwarded to the source UE. Indication And / or a link change acceptance including the selected RID may be sent to Relay 1. Next, in 3-9, Relay 1 performs relay reselection. Indication The link change acceptance, including the selected RID, may be forwarded to the source UE. In 3-10, the source UE forwards the relay reselection to the target UE. IndicationA link change acknowledgment including the selected RID may be sent to Relay 1. In 3-11, Relay 1 may forward the link change acknowledgment to the target UE. In 3-12, the target UE and / or source UE may begin transmitting IP traffic through the selected RID (e.g., Relay 2 in the embodiment of Figure 3).

[0069] The Layer-3 UE-UE relay operation illustrated in Figures 2 and 3 involves relaying traffic between two terminal-equipped UEs via two PC5 unicast single-query links, and routing traffic from one indirect link via one relay to another via another. Switching To support and

[0070] Indirect-direct pathways Switching Typical procedures for Indirect communication (e.g., PC5 indirect communication using PC5 communication via a U2U relay) may be used when the source UE and target UE are not in close proximity to each other. Once a PC5 link is established via the relay, the source UE and / or target UE may communicate (e.g., exchange traffic). For example, while communicating via this indirect link, the source UE and target UE may move closer to each other, but allow the establishment of a direct PC5 unicast single query link (e.g., a PC5 link without a U2U relay). The UEs may be configured with a policy that prefers direct links over indirect links, for example, for efficiency reasons. In this case, the source UE and target UE may route traffic from the indirect link to a direct PC5 unicast single query link (e.g., for continuity of service, for example, a route). Switching (By executing this) SwitchableThe procedure and / or operation may be implemented as follows: In the case of an indirect link via an L3 relay, the source UE may know and / or determine the target UE user information (e.g., information), but the target UE may not know the source UE user information (e.g., information). If the corresponding UE IP address is learned via a DNS query specifying a ProSe service, it is also possible that neither the source UE nor the target UE knows or can determine the corresponding UE user information.

[0071] In certain representative embodiments, methods, systems, apparatus, procedures, and / or operations are configured such that a source UE (1) detects that its indirect isotopic UE is directly reachable, (2) establishes a direct link with the indirect isotopic UE, and / or (3) establishes an indirect-to-direct path. Switching Therefore, it may be implemented to associate direct links with existing indirect links on their side and on the corresponding UE side.

[0072] In certain representative embodiments, methods, systems, apparatus, procedures, and / or operations are indirect-to-direct pathways (which are transparent to the application layer, for example). Switching It may be implemented to support seamless continuity during this time. For example, to obtain seamless continuity, IP routing may be used so that UEs communicating via relay can communicate directly. Switch In such cases, it may be necessary to save or reuse those IP addresses.

[0073] In certain representative embodiments, methods, systems, apparatus, procedures, and / or operations are performed via indirect-to-direct pathways. Switching When performing this, the source UE may be implemented to ensure seamless continuity.

[0074] In certain representative embodiments, methods, systems, apparatus, procedures, and / or operations may be implemented to support the establishment of direct links in addition to indirect links, and / or to use direct and indirect links simultaneously and / or in parallel (e.g., for additional bandwidth) and / or per service type (e.g., using direct links for PC5 signal transmission and indirect links for traffic (e.g., data)), or to keep one as a backup link (e.g., using direct links for redundancy and switching back to indirect links if the direct links are lost or of poor link quality). Additional links may support, for example, two or more indirect links.

[0075] In certain representative embodiments, methods, systems, apparatus, procedures, and / or operations may be implemented for a source UE to associate additional routes (e.g., direct / indirect links) with existing routes (e.g., direct / indirect links) together with a corresponding UE (e.g., multiple routes may be supported for increased bandwidth, for traffic type-based routes, and / or for backup routes).

[0076] Direct-indirect routes Switching Typical procedures for In the case of direct communication (for example, via a PC5 link), the source UE and target UE may exchange traffic after the PC5 link is established. While communicating via this direct link, the source UE and target UE may move away from each other, but require / facilitate the establishment of an indirect PC5 link (e.g., a unicast single query link), such as a PC5 link via a U2U relay. In certain embodiments, direct-indirect routes are used. Switching This may not be implemented. In other embodiments, indirect-indirect paths Switching However, it may be implemented.

[0077] In certain representative embodiments, methods, systems, apparatus, procedures, and / or operations are used to determine which U2U relays a source UE can reach its counterpart UE, and / or to establish direct-indirect paths to this counterpart UE. Switching It may be implemented to adjust it.

[0078] Typical procedures for seamless continuity and IP address reuse Seamless continuity may be achieved by saving the IP addresses used for the link between two identical UEs (e.g., source UE and target UE) and their reuse on the new link. In this embodiment, the application layer is the route. Switching It is not necessary to be aware of, or it is acceptable not to be aware of. When the same IP address is reused in another indirect or direct link: (1) The IP address assigned by the relay (RID1) is route Switching (1) When used later with another relay (RID2), in a particular representative embodiment, an IP address assigned by relay RID1 may not be released while being used with the other relay RID2, and / or may not be assigned to or reallocated to another UE; (2) When an IP address assigned by relay (RID1) is also assigned to another UE by the other relay (RID2), in a particular representative embodiment, relay RID2 may determine to which UE traffic should or may be routed when the same IP address is associated with two different UEs; and / or (3) When an IP address assigned by relay (RID1) is also assigned to another UE by the other relay (RID2), in a particular representative embodiment, IP address duplication may be handled by relay RID1 and / or relay RID2.

[0079] The terms ProSe Application Layer ID, UE Application Layer ID, ProSe User Information, and UE User Information may be used interchangeably herein. The terms IP address (sometimes referred to as IP addr) and IP prefix may be used interchangeably herein; for example, whenever IP address is used herein, it may be replaced by an IP prefix. Indication The term "(keep IP address indication)" and "reuse" Indication The term "(reuse indication)" may be used interchangeably in this specification.

[0080] In the case of IP-based communication via L3 relay, multiple procedures may be implemented.

[0081] Indirect-direct pathways Switching Details of typical procedures for this purpose A source UE that knows / determines the user information of the target UE, and if the target UE does not know the source UE's user information, the source UE may learn / determine the target UE's IP address, for example, by sending a DNS query message to a relay (e.g., associated with an indirect route). The DNS query message may include the target UE's user information (e.g., received from the application layer). The relay may respond with a DNS response message containing the target UE's IP address. The source UE and the target UE may communicate via the relay.

[0082] In certain representative embodiments, for example, in the first example (Example 1), the source UE may detect that the target UE is directly reachable after the execution of the discovery procedure. For example, the source UE may include indirect link information in the message (e.g., in the DCR message or in the DSM completion message) the direct link establishment procedure and the indirect-to-direct path. SwitchingThe relay may be initiated. The indirect link information may include, in particular, any of the following: (1) one or more RIDs, (2) the IP address of the source UE via the relay, (3) the target IP address via the relay, (4) the App ID, and / or (5) the user information of the target UE.

[0083] In certain representative embodiments, for example, in a second example (Example 2), the source UE may not be aware of and / or determine that the target UE is directly reachable, and may broadcast a message (e.g., a DCR message). The source UE may detect that it has an indirect link with the current target UE when it receives a DCA message for direct link establishment, and this DCA message may contain and / or include user information of the target UE. The source UE may, for example, include / indicate indirect link information, and may use the direct link to send an update message (e.g., an updated link change request message) or a new request (e.g., a new link) via / using the direct link. switching By sending a request, the indirect-direct route Switching You may start.

[0084] In certain representative embodiments, for example, in a third example (Example 3), the source UE and target UE may not be aware of and / or determine that they are directly reachable, and the target UE may broadcast a message (e.g., a DCR message). The source UE may detect that it currently has an indirect link with the target UE when it receives a DCR message that may contain and / or have user information from the target UE. The source UE may, for example, in a message (e.g., a DSM command message), route switching By including information, the indirect-direct pathway Switching You may start.

[0085] For source and target UEs that do not know / have not determined the user information of those co-located UEs, the source UE may learn / determine the target UE's IP address, for example, by sending a DNS query message. The DNS query message may include a ProSe service, but the relay may respond with a DNS response message that includes the IP address. After and / or upon receiving a DNS query that includes a ProSe service, the relay may include the target UE's user information in addition to the target UE's IP address in the DNS response. After the source UE has received the target UE user information and / or IP address, the first, second, and third cases (cases 1 to 3) described above may be applied (for example, then completed).

[0086] Direct-indirect routes Switching Details of typical procedures for this purpose The source UE and target UE may negotiate which relays should be used for the indirect link. (1) Indirect-to-indirect path Switching Procedures, and / or (2) direct-indirect routes Switching For any of the procedures, a relay for indirect communication may be negotiated / selected, or may be required to be negotiated / selected. The IP address used via the selected relay is the route. Switching They may be replaced in the middle. In certain embodiments, the source UE and target UE may decide to retain / keep IP addresses used on and / or via the direct link for a direct link, but may reuse these IP addresses on and / or via the indirect link for an indirect link. In this embodiment, the IP address may or may need to be registered with the selected relay. Direct-indirect route Switching This may include any of the following: (1) Source UE changes the current direct communication to indirect communication. Switching May and / or imminent route Switching Is it alright to determine / decide to prepare for it? (2) Source UE is (i) direct-indirect Indication (ii) a list of candidate RIDs, and / or (iii) keep-IP-addr Indication (iv) The request is route Switching For example, if it is preparation for a route Switching If this is not done immediately, then "preparation" Indication , and / or (v) link quality threshold is specified / included in the request / Shown The request may include either a link change request or a new link request. switching (3) For example, a target UE receiving a request may send a relay (e.g., keep-IP-addr Indication If this is included, and the target UE agrees to reuse the target UE's IP address for the indirect link and / or the direct link through the indirect link, the target UE may register this IP address with the selected relay. Indication If specified / included and / or indicated, the target UE will not register the target UE's IP address with the selected relay at this point, and will not actually route it. Switching In the event that this is performed (for example, only in that case), for example, if a link quality threshold is provided, if it is met, or if the direct link is lost, is it permissible to determine / decide whether to register the IP address of the target UE? (4) The target UE is (for example, keep-IP-addr Indication Based on this, may a message (e.g., a link change acceptance message) be sent back containing either an IP address used in and / or via the direct link, or an IP address used with the selected relay (e.g., assigned by the selected relay), in order to reuse the target UE's IP address? (5) The source UE may register its IP address with the selected relay if the IP address from the direct link is reused on the indirect link (for the target UE, if a link change procedure is imminent). SwitchingWhen used in preparation for this, the source UE does not register its IP address with the relay at this point, and actually routes Switching When performing the following actions (for example, when a link quality threshold is provided on a link change request, when the link quality threshold is met, or when a direct link is lost), is it permissible to determine / decide whether to register the IP address of the source UE? (6) If the IP address used on the direct link is not reused, the source UE may, by the selected relay, send a message containing the source UE's IP address (e.g., a link change Ack acknowledgment message), and / or (7) The source UE and / or target UE, in particular, when traffic reaches the indirect link Switch This allows you to release the direct link.

[0087] route Switching For preparation, the route Switching This may be done immediately after the link change procedure is completed, or after the threshold is met, or after the link is lost (for example, only once). For example, source UE1 and / or target UE2 may monitor the link quality of the direct link and, if the threshold is met, the path Switching This may be triggered. In another embodiment, source UE1 and / or target UE2 may maintain a direct link and an indirect link. Switching After that, you may continue to monitor the link quality of the direct links. If the direct link quality has improved, you can change the path from indirect links to direct links without having to establish new direct links. Switching You may do so.

[0088] Typical procedures for supporting multiple paths Multiple paths may be used in parallel and / or simultaneously for additional bandwidth and / or one or more backup links. The source UE and target UE may negotiate / decide on the use of one or more additional and / or backup links. For example, at any time, the source UE and / or target UE may determine / decide to add a new link and / or remove an existing link to (1) change the bandwidth (increase / decrease the bandwidth of the communication), (2) for the transmission of one or more specific traffic, and / or (3) as a backup. With respect to indirect-to-indirect procedures, the addition of indirect or direct communication may be negotiated or may need to be negotiated. For example, the source UE may change an existing direct communication to an indirect communication. Switching You may judge / decide that this is the case.

[0089] Indirect-direct pathways Switching Representative actions for Figure 4 shows a typical indirect-to-direct pathway according to one embodiment. Switching This is a diagram illustrating this point. For example, the indirect-to-direct pathway. Switching This may be triggered during direct link establishment using a message (e.g., a DSM completion message). The source UE may know / determine the user information of the target UE, and the target UE may not know / determine the user information of the source UE. In the first embodiment, source UE1 may know / determine that target UE2 is directly reachable after the discovery procedure. From this indirect path to the direct path Switching (Example 1) may include any of the following:

[0090] In operation 4-0, source UE1 and target UE2 may have a relay and an established PC5 unicast single query link (indirect link). Source UE1 may know / determine user information of target UE2 (e.g., received from the application layer). Source UE1 and target UE2 may exchange IP traffic (e.g., user plane packets) via the relay. Target UE2 does not know / determine user information of source UE1.

[0091] In operation 4-1, source UE1 may discover that target UE2 is directly reachable during the discovery procedure (for example, source UE1 may send a message (e.g., a request message), receive a response message, and / or source UE1 may receive another message (e.g., an announcement message) from target UE2). The user information of target UE2 discovered during the discovery procedure is the same user information associated with the indirect link via the relay.

[0092] In operation 4-2, source UE1 may initiate the establishment of a PC5 direct link with target UE2 by sending a message (e.g., a DCR message) to target UE2 (e.g., specifying / providing user information for target UE2). The DCR message may be broadcast and / or sent to the L2 ID of target UE2, as discovered in operation 4-1.

[0093] In operation 4-3, the target UE2 may send a message (e.g., a DSM command message) to the source UE1. Since the target UE2 does not know the user information of the source UE1, at this point the target UE2 does not need to know, or does not know, that the source UE1 that sent the DCR message is the same UE that already has an indirect link.

[0094] In operation 4-4, source UE1 routes the DSM completion message. switchingBy including information, the indirect-direct pathway Switching You may start the route. switching Information, in particular, (1) "from indirect to direct" Indication (2) Indirect link information, and / or (3) "keep-IP-addr" Indication The indirect link information may include any of the following: (1) Relay identifier (RID), IP address of source UE1 via the relay, (2) IP address of target UE2 via the relay, (3) App ID, and / or (4) User information of target UE2. "keep-IP-addr" Indication (For example, may be transmitted as desired) may indicate, for example, that IP addresses used to exchange traffic over indirect links may be reused for direct links, with respect to similar seamless continuity, as disclosed herein. switching The information can be sent using the DSM Complete message, so the route switching Information may be transmitted with integrity and confidentiality protection, for example, via switching The information is not visible to any UE other than Target UE2, or integrity and confidentiality protections are intended to be enabled for this direct link, so it may not be tampered with by malicious third parties.

[0095] In operation 4-5, target UE2 is the path in the DSM completion message. switching Information may be received, and based on the received information, it may be verified that target UE2 has an ongoing indirect link with source UE1. If the ongoing link is discovered, target UE2 is found to be a path. Switching If accepted, Target UE2 will use the path received in operation 4-4. switching A response may be made by sending a DCA message containing information. For example, if target UE2 is a route Switching If you do not accept this and do not agree to reuse the IP address from the indirect link, Target UE2 will "keep-IP-addr" Indication Without, route switching Information may be included. In another example, if target UE2 is a path Switching If you do not accept the other option and instead accept establishing a PC5 direct unicast single query link, the DCA message will be routed. switching It may be transmitted without containing any information. In certain embodiments, the target UE2 is the path Switching If this is not accepted, target UE2 will route the DCA message. switching Information may be omitted or not included. If the target UE2 does not want / like / decide not to establish a direct link, the target UE2 will use a cause value (e.g., "path"). Switching A direct communication rejection message, which may include "Rejected," may be sent to source UE1.

[0096] In operation 4-6, source UE1 may receive a DCA message and / or verify whether the same IP address may or may not be reused. If the same IP address is reused, the IP address from the indirect link is associated with the direct link, and the IP address assignment procedure may be skipped. Otherwise, the IP address assignment procedure may be performed as usual. A direct PC5 unicast single query link may be established between source UE1 and target UE2 in addition to the existing indirect link via relay.

[0097] In operation 4-7, source UE1 and target UE2 redirect traffic from an indirect link to a direct link. Switching For example, source UE1 and target UE2 may send traffic via a direct link and receive traffic via a direct link.

[0098] Routes triggered using DCR messages Switching Typical procedure using Source UE1 uses a DCR message via operation 4-2 instead of a DSM completion message to route Switching This may be triggered. In this case, the path switchingThe information may also be transmitted using DCR messages. switching The information may be transmitted unprotected, for example, in plain text. Target UE2 is the path. Switching If accepted, target UE2 will use the same path with integrity protection in the DSM command message. switching The information may be resent. In certain embodiments, target UE2 converts the indirect link to a new direct link. Switching If you do not want to / do not like to, or do not decide to do so, the goal UE2 will be the path switching The response may be a DSM command message without any information. Alternatively, the target UE2 may provide a cause value (e.g., "path"), for example. Switching Direct link establishment may be refused by sending a message containing "Rejected" (for example, a DSM rejection message).

[0099] Capabilities and paths triggered using link change procedures exchanged using DCR / DCA messages. Switching Typical procedures for The capabilities may be swapped during the link establishment procedure. In this case, source UE1 will perform a link change procedure (or link change procedure) as described herein, for example, with respect to Figure 5 and operation 5-7. Switching Using the procedure, based on the capabilities of the equivalent UE (e.g., target UE2), the path Switching You may decide to trigger it.

[0100] Figure 5 shows a typical indirect-to-direct path, triggered after direct link establishment using, for example, a PC5 signal transmission message. Switching This is a diagram illustrating the concept.

[0101] Referring to Figure 5, Source UE1 may not recognize / determine that Target UE2 is directly reachable and may broadcast a DCR message. Indirect-to-Direct Path in Case 2 Switching In this case, one of the following actions may be performed. (1) In action 5-0, any of the actions related to Figure 4 (Example 1) may be performed. (2) In operation 5-1, source UE1 may broadcast a message (e.g., a DCR message) without specifying / determining user information for target UE2. Source UE1 may declare one or more supported ProSe services as shared. (3) In operation 5-2, the target UE2 may directly trigger the security mode procedure, for example, by sending a message (e.g., a DSM command message) as usual. The target UE2 may not know / determine the user information of source UE1 and / or the target UE2 may not detect or be able to detect the existence of an indirect link with source UE1. (4) In operation 5-3, source UE1 may complete the procedure by, for example, sending a completion message (e.g., a DSM completion message) as usual. (5) In operation 5-4, the target UE2 may complete direct link establishment, for example, by sending a DCA message, which may, for example, include or indicate the user information of the target UE2, as usual. (6) In operation 5-5, a direct link is established between source UE1 and target UE2. (7) In operation 5-6, upon receiving the DCA message, source UE1 may detect the direct reachability of target UE2, and / or source UE1 may already have an indirect link with source UE2 in addition to the newly established direct link. (8) In operation 5-7, source UE1 may send a message (e.g., a changed link change request message) or a request (e.g., a new link Switching By sending the request within and / or via the direct link, the route goes from indirect to direct. SwitchingThis may be initiated. This message or request may include indirect link information. Another message may be sent, which may include direct link information within and / or over the indirect link. These messages may also include route switching information, as described herein, for example, with respect to Figure 4 (Example 1) and operation 4-4. For example, source UE1 is route switching You may send a link change request message containing information. Target UE2 is the route Switching If accepted, Target UE2 may respond with a link change acceptance message. Target UE2 will then process the route. Switching It may accept, or may reject, the reuse of the IP address from the indirect link. Target UE2 can also, for example, send a link change rejection message to the route. Switching You may refuse this. "keep-IP-addr" Indication (For example, reuse Indication ) included and accepted (via a link change acceptance message), the direct link may be associated with the IP address used for the indirect link. In this case, a new IP address may not be assigned or will not be assigned after the completion of the direct link establishment procedure, and / or (9) Source UE1 and target UE2 may, in particular, send and / or receive traffic via direct links instead of using indirect links.

[0102] Figure 6 shows typical indirect-to-direct paths triggered during direct link establishment using DSM command messages. Switching This is a diagram illustrating the concept.

[0103] Referring to Figure 6, target UE2 may not recognize / determine that source UE1 is directly reachable and may broadcast a DCR message. (Example 3: Indirect-Direct Path) Switching In this case, one of the following actions may be performed. (1) In action 6-0, any of the actions related to Figure 4 (Example 1) may be performed. (2) In operation 6-1, the target UE2 may broadcast a message (e.g., a DCR message) without specifying / determining the user information of the target UE2. The target UE2 may declare one or more supported ProSe services as shared. (3) In operation 6-2, source UE1 may detect that it currently has an indirect link with target UE2 when it receives a message (e.g., a DCR message). The DCR message may, for example, contain user information of target UE2 as usual. Source UE1 may route the DSM command message, for example. switching By including information, the indirect-direct pathway Switching You may start the route. switching Information is disclosed, for example, with respect to Figure 4 (Example 1) and Operation 4-4. (4) In operation 6-3, target UE2 is the path in the DSM command message. switching Information may be received, and based on the received information, it may be verified that the target UE2 has an ongoing indirect link with source UE1 (e.g., actually has one). For example, if an ongoing link is discovered, the target UE2 may be found to have a path Switching If accepted, target UE2 will take an integrity-protected route, such as the one received in operation 6-2. switching You may respond by sending a message containing information (e.g., a DSM completion message). For example, if target UE2 is a route Switching If you do not accept the reuse of the IP address from the indirect link, Target UE2 will use "keep-IP-addr" or reuse Indication Without, route switching Information may be included. In another example, if target UE2 is a path Switching If you do not accept the other option and instead accept establishing a PC5 direct unicast single query link, the DSM completion message will be sent to the route. switchingIt may be transmitted without containing any information. In a further embodiment, if Target UE2 does not want / does not like / decides not to establish a direct link, Target UE2 may send a direct communication denial message to Source UE1, and route Switching A cause value indicating that the request was rejected (for example, "path") Switching It may include the "rejection" cause value. (5) In operation 6-4, source UE1 may send a DCA message to verify whether the same IP address is reused. If the IP address is reused, the IP address from the indirect link may be associated with the direct link. Otherwise, the IP address assignment procedure is performed normally, for example, after the link establishment procedure is completed. (6) In operation 6-5, in addition to the existing indirect link via relay, a direct PC5 unicast single query link may be established between source UE1 and target UE2, and / or (7) In operation 6-6, source UE1 and target UE2 move the traffic from the indirect link to the direct link. Switching (For example, source UE1 and / or target UE2 may send traffic directly to the link and / or receive traffic from the direct link.)

[0104] Direct-indirect routes Switching Typical procedures for Figure 7 shows a typical direct-indirect pathway. Switching This is a diagram illustrating the concept.

[0105] Referring to Figure 7, a typical direct-indirect pathway is shown. Switching This may include any of the following actions: (1) In operation 7-0, source UE1 may have a PC5 unicast single query link established with relay RID1. Target UE2 may have a PC5 unicast single query link established with relay RID1. Source UE1 and target UE2 may communicate directly via the PC5 unicast single query link. Source UE1 and target UE2 may be aware of each other's peer user information. (2) In operation 7-1, source UE1 directs traffic to target UE2 via an indirect link. Switching via, and / or indirect links Switching They may decide to do so (for example, they may make a decision). This decision / judgment may be based on a variety of factors, including, for example, any of the following: (1) direct link quality, (2) deterioration of direct link quality, and / or (3) policy in particular. (3) In operation 7-2, source UE1 sends a message (e.g., a link change request message) using the direct link, for example, via the direct-indirect path. Switching You may start it. The message is route for relay selection. switching Information may be included. Route switching Information is (1) "direct-indirect" Indication , (2) "keep-IP-addr" (reuse) Indication , (3) "Preparation" Indication (4) one or more thresholds (e.g., including a preparation threshold), and / or (5) a list of candidate RIDs, which may include any of these. "keep-IP-addr" Indication This may indicate that IP addresses used to exchange traffic over a direct link are reused for an indirect link, for example, as described herein with respect to seamless continuity. Indication is, route Switching A relay should be prepared (for example, a relay is selected), but the route SwitchingThis may indicate that it should not be performed immediately after the link change procedure is completed. One or more thresholds may be and may be specified for link quality. If this threshold is met, the path to the indirect link with the selected relay is closed. Switching This can be triggered. The thresholds may indicate, for example, a LOW threshold and / or a HIGH threshold. Link quality that does not meet (e.g., falls below) the LOW threshold indicates poor link quality using direct links and routes to indirect links. Switching It may also indicate that this should or will be done. Link quality that meets (e.g., exceeds) the HIGH threshold indicates good link quality using direct links and the path from indirect links to direct links. Switching It may also indicate that something should be done, could be done, or will be done. (4) In operation 7-3, target UE2 may select a relay based on the received list of candidate RIDs. For example, target UE2, Indication (For example, "keep-IP-addr" (for example, reuse) Indication Based on the reception of the signal, it may be determined whether the IP address used for the direct link is to be reused for the indirect link via the relay. (5) In operation 7-4, target UE2 may register its IP address with the selected relay (for example, if the IP address has not yet been registered). For example, such registration may occur if the IP address from the direct link is to be reused for the indirect link via the selected relay. At this point, target UE2 may determine / decide not to register its IP address and to complete the registration operation, route Switching It can wait for a trigger (for example, when a threshold is met or when the direct link is lost). (6) In operation 7-5, the target UE2 is on the path SwitchingIf accepted, Target UE2 may send a message (e.g., a link change acceptance message) to Source UE1 via the direct link. As described herein, and as shown in Figure 4 for example, Target UE2 may, Switching The destination UE2 may accept the request and refuse to reuse the IP address from the direct link. The destination UE2 may, for example, send a rejection message (e.g., a link change rejection message) to the route. Switching You may reject it. For example, "keep-IP-addr" (e.g., reuse). Indication If specified / included and accepted, the indirect link may be associated with the IP address used for the direct link. In this case, the new IP address may not be assigned, or should not be assigned, during and / or after the indirect link establishment procedure. As another embodiment, if the target UE2 does not accept reusing the IP address from the direct link, "keep-IP-addr" Indication This does not have to be specified / included in the link change acceptance message. Instead, the IP address of the target UE2 used for the selected relay may be specified / included in the link change acceptance message. (7) In operation 7-6, the determination / decision is to reuse the IP address from the direct link, and if the IP address of source UE1 has not yet been registered, source UE1 may register its IP address with the selected relay (e.g., one with RID) as received in operation 7-5. Source UE1 may at this point determine / decide not to register its source IP address, and to register the IP address of source UE1, route Switching It can wait for a trigger (for example, until a threshold is met or the direct link is lost). (8) In operation 7-7, source UE1 may send an acknowledgment message (e.g., link change Ack-acknowledgment message) to target UE2 via / using the direct link. This operation is used / necessary when source / target UE does not maintain / keep the same IP address from the direct link to the indirect link. In this case, the IP address of source UE1 recognized in the selected relay may be sent to target UE2 using this acknowledgment message. In certain embodiments, operations 7-4 and 7-7 may be replaced by one or more DNS queries from source UE1 and / or target UE2. The acknowledgment message (e.g., link change Ack-acknowledgment message) is (1) a "keep IP address" if agreed / negotiated. Indication (2) "keep IP addr" Indication However, if not specified / included in the acknowledgment message, the IP address of the source UE1 to be used with the selected relay (e.g., RID) may be provided and / or (3) preparations if specified in the request message, for example in operation 7-2. Indication It may include either and / or a threshold. (9) In operation 7-8, the route Switching Furthermore, source UE1 and target UE2 may, transparently to the application layer, send and / or receive traffic via indirect links instead of using direct links if the IP addresses from the direct links are reused. For example, routing Switching is "preparation" Indication However, if not specified / included in the acknowledgment message, it may be performed immediately after the link change procedure is completed. "Preparation" Indication If specified / included with a threshold, source UE1 and / or target UE2 may monitor the link quality of the direct link, and if the threshold is met (for example, if the link quality does not meet the LOW threshold so that data can be sent over the indirect link), the path SwitchingThis may be triggered. If a HIGH threshold is specified / included in the acknowledgment message, source UE1 and / or target UE2 will initiate the indirect link. Switching After this, you may continue to monitor the link quality of the direct link, and if the direct link quality improves, for example, if it reaches / meets the HIGH threshold, the path from the indirect link to the direct link may be monitored. Switching This may be done. Thresholds may be monitored in the ProSe layer based on measurements received from one or more lower layers. In certain embodiments, the ProSe layer may configure lower layers using thresholds (e.g., thresholds), and / or lower layers may notify the ProSe layer when the threshold is reached, and the route from direct link to indirect link, or vice versa. Switching This can be triggered. "Preparation" without a threshold. Indication If specified / included, source UE1 and target UE2 will have a direct link if the path is lost. Switching You may also trigger this. "Preparation" Indication If specified / included, source UE1 and / or target UE2 may periodically re-execute the link change procedure, and / or based on the current list of candidate RIDs for source UE1 and / or target UE2, route Switching You may choose a different relay for this purpose. (10) In operation 7-9, the direct link is from the indirect link to the direct link. Switching To enable reversal (for example, to enable faster resumption), it may be released or retained (for example, maintained). Direct links may be reused if a HIGH threshold is specified / included as described herein.

[0106] It should be noted that in certain embodiments, the diagrams illustrated in Figures 2 to 7, and / or the operations depicted therein, can be combined in any preferred manner.

[0107] Typical procedures for supporting multiple paths Multiple links may be used simultaneously between two corresponding UEs, for example, Source UE1 and Target UE2, and may be, for example, a direct PC5 link and an indirect PC5 link via relays, or two or more indirect links via two or more different relays. Source UE1 may indicate, for example, when sending a DCR message or a DSM completion message, which "type" of direct or indirect link it wants / prefers to establish. Target UE2 proposes / Indication You may accept, or, for example, another type or other corresponding Indication By sending the information, the determination / decision may be made in a different way.

[0108] New link type Indication (1) Traffic is transferred from an indirect link to a direct link via a relay. Switching In the case of "indirect-direct" Indication (2) Traffic is transferred from the direct link to the indirect link via a relay. Switching In the case of "direct-indirect" Indication (3) When a new direct link is associated with an existing indirect link (for example, by adding it), use the "direct + indirect" method. Indication , and / or (4) when a new indirect link is associated with an existing direct link (e.g., added), “indirect + direct” Indication It may include any of the following.

[0109] "Direct + indirect" Indication Or "indirect + direct" Indication For multi-path support with this new link, you may include another new “usage” field to specify the use of this new link. The new “usage” field value may indicate, for example, any of the following: (1) additional bandwidth, (2) signaling traffic (e.g., signaling traffic only), (3) data traffic (e.g., data traffic only), and / or (4) backup.

[0110] Representative procedures for seamless continuity Seamless continuity may be achieved by saving the IP addresses used for the link between two identical UEs and reusing them on the new link. In this case, the application layer is responsible for routing. Switching There is no need to be aware of this.

[0111] To support this reuse of IP addresses from one link to another, the UE manages its own IP addresses, i.e., instead of relaying. This means the UE establishes direct links and then uses the same IP addresses to communicate with them over indirect links. Switching To enable, or to still use the same IP address to establish an indirect link and then move to another indirect or direct link.

[0112] UE is to indirect links Switching In such cases, those IP addresses, along with the corresponding application ID and / or user information, may be registered with the relay. Registration may occur (1) during the indirect link establishment procedure, or (2) after the indirect link establishment. During link establishment, the UE may use a DSM completion message and include this IP address in the DSM completion message to indicate to the relay that the UE already has an IP address. For example, the IP address configuration IE may be set to a new value, e.g., "address allocation not needed". In this case, the relay provides its own IP address in a DCA message. No further IP allocation procedures are used, or may need to be performed after the link establishment. In certain embodiments, the UE may function as a DHCP server or IPv6 router and assign an IP address to the relay. In this case, the UE may reuse its own IP address or assign a new IP address to the relay. Switching Before that, if a link with the selected relay has already been established, the UE will SwitchThe relay may register the IP address used by the UE for the link to be changed. This may be done, for example, using a link change request message that includes the IP address to be registered. In this case, the relay may add an association between this IP address and the UE's user information and application ID (for example, in the relay's DNS entry).

[0113] Go to direct link Switching In this case, the first and second UEs will keep the "keep IP addr" (as described herein and shown, for example, in Figures 4 and 6) in the DSM completion / DCA message. Indication They may use the same IP address. The UEs may agree to reuse the same IP address. If the UEs agree, the IP address configuration information element (IE) and the link-local IPv6 address IE do not need to be specified in the DSM completion / DCA message. In certain embodiments, the IP address configuration IE may be set to a new value (e.g., "No address assignment required"). The first and second UEs may be provisioned in a pool of unique IP addresses (IPv4 prefix prefix and / or IPv6 prefix prefix) to prevent, for example, two or more UEs from registering the same IP address for relay.

[0114] route Switching Typical procedures for exchanging capabilities The first UE and / or the second UE (e.g., UE1 and / or UE2) are connected by (1) the path Switching (2) whether to support multiple routes and / or (3) seamless continuity on discovery messages, Show That's also good. For example, "path Switching Indicates "enabled (path switching enabled)". Indication However, this may be added to the request message. Indication However, it may be specified / used in the response message. For multiple path support Indicationand / or another for seamless continuity support Indication is, route Switching Indication In addition to, or instead of, support for, routes may be included and / or added. Switching Indication Support for this may be protected / verified within the discovery message by the first UE and / or second UE (e.g., UE1 and UE2) using discovery keys obtained from network functions and / or application functions (e.g., DDNMF / PKMF).

[0115] In certain embodiments, capabilities may be exchanged during the link establishment procedure, for example, a first UE (e.g., UE1) may send a message (e.g., a DCR message) containing its capabilities. A second UE (e.g., UE2) may, for example, replicate the capabilities of the first UE1 during the DSM using integrity protection to mitigate a potential man-in-the-middle (MiTM) attack. The second UE2 may send its own capabilities on another message (e.g., a DCA message).

[0116] In other embodiments, the first UE1 may include its capabilities in a message DCR message, and the relay may store the capabilities of the first UE (e.g., UE1) separately, for example. When the relay receives a DNS query message concerning the first UE1 (e.g., from a second UE2), the relay may respond with a response message (e.g., a DNS response message) which may include the capabilities of the first UE (e.g., UE1).

[0117] Typical steps for provisioning route SwitchingCapabilities may be enabled / disabled via provisioning. Multiple routes and seamless continuity support may be provisioned on the UE. The UE may receive provisioning information (e.g., from network entities), e.g., from the PCF, and the provisioning information may include information indicating, for example, one of the following: (1) indirect-to-direct routes Switching (2) Whether valid or invalid, direct-indirect routes Switching However, whether it is valid or invalid, (3) indirect-to-indirect routes Switching (4) Multiple path support is enabled or disabled, and / or (5) Seamless continuity is enabled or disabled.

[0118] Figure 8 is a flowchart illustrating a typical method (800) that can be implemented by a first WTRU that has established an indirect link with a second WTRU, according to several representative embodiments. For example, the first WTRU may establish an indirect link with the second WTRU via a relay. Referring to Figure 8, the typical method (800) may include, in (810), the first WTRU performing a discovery procedure. In (820), the first WTRU may detect, based on the results of the performed discovery procedure, that the second WTRU is directly reachable. For example, in one embodiment, the first WTRU may detect in (820) that the second WTRU may be directly reachable via a direct link (i.e., without a relay). In (830), the first WTRU may initiate the establishment of a direct link with the second WTRU. According to one embodiment, the direct link may be a PC5 direct link or a PC5 unicast single query link.

[0119] In the embodiment shown in Figure 8, at (840), the first WTRU moves from the indirect link to the direct link. Switching This may also be the case. According to one embodiment, from an indirect link to a direct link Switching(840) transmits a message containing or indicating indirect link information to the second WTRU, thereby establishing an indirect-to-direct route. Switching This may include initiating the process. The indirect link information may include one or more of the following: (1) one or more relay identifiers associated with the indirect link, (2) the IP address of the first WTRU, (3) the IP address of the second WTRU, (4) an application identifier, and / or (5) user information of the second WTRU. According to one embodiment, the user information of the second WTRU may include information used to uniquely identify a user for a particular application (e.g., a unique username). In certain embodiments, the message may be a Direct Communication Request (DCR) message or a Direct Security Mode (DSM) completion message. According to one embodiment, the message may include (1) route Switching Shows the type Indication , and / or (2) the IP addresses of the first WTRU and the second WTRU used for the indirect link are reused for the direct link, indicating a preference of the first WTRU. Indication Information containing one or more of the following may be included.

[0120] As illustrated in the embodiment of Figure 8, in (850), the first WTRU is Switching The first WTRU may communicate with the second WTRU via a later established direct link. In some embodiments, representative method (800) may further include the first WTRU receiving an acceptance message containing information confirming that the IP addresses of the first and second WTRUs, which are used for the indirect link, will be reused for the direct link. According to a particular embodiment, representative method (800) may include the first WTRU communicating with the direct link based on the fact that a trigger condition has been met. Switching Receiving information indicating whether or not it should be done, determining whether the trigger condition is met, and based on whether the trigger condition is met, switching from an indirect link to a direct link. Switching This may include triggering an event.

[0121] Figure 9 is a flowchart illustrating a typical method (900) that may be implemented by the first WTRU in several embodiments. Referring to Figure 9, the typical method (900) may include, in (910), the first WTRU broadcasting a message indicating a request for direct communication. In (920), the first WTRU may receive a response from the second WTRU to the broadcasted message. In (930), the first WTRU may determine that the second WTRU has an established indirect link with the first WTRU.

[0122] In one embodiment, receiving a response to a broadcasted message (920) may include receiving from a second WTRU an acceptance message indicating acceptance of direct communication with the first WTRU, and information associated with the second WTRU. According to one embodiment, determining that the second WTRU has an established indirect link with the first WTRU (930) may include determining that the received information associated with the second WTRU matches the information associated with the established indirect link with the second WTRU. In some embodiments, the broadcasted message may be a direct communication request (DCR) message, and the response to the broadcasted message may be a direct communication acceptance (DCA) message.

[0123] As further shown in the representative method (900) in Figure 9, in (940), the first WTRU provides a path for an indirect-to-direct link with the second WTRU. Switching They may initiate (950), in which the first WTRU moves from an indirect link to the second WTRU to a direct link to the second WTRU. Switching In some embodiments, the indirect link to the second WTRU is replaced with a direct link to the second WTRU. Switching(950) transmits one or more of the following to the second WTRU to establish an indirect-to-direct route: (1) an update message using an established indirect link, which includes information indicating direct link information, and / or (2) a request message using a direct link, which includes information indicating indirect link information. Switching This may include initiating the update. According to one embodiment, the update message may be a link change request message, and / or the request message may be a link Switching It may also be a request message. According to one embodiment, from an indirect link to a second WTRU to a direct link to a second WTRU Switching (950) is a link change request message or route Switching Within the request message, the route to the second WTRU is specified. Switching By transmitting information, indirect-direct pathways Switching This may include initiating it.

[0124] In (960), the representative method (900) is performed by the first WTRU, Switching This may include communicating with a second WTRU via a later established direct link.

[0125] Figure 10 is a flowchart illustrating a typical method (1000) that can be implemented by a first WTRU that has established a direct link with a second WTRU, according to several embodiments. Referring to Figure 10, the typical method (1000) is that in (1010), the first WTRU moves from a direct link to an indirect link. Switching This may include sending a link change message to the second WTRU that includes information indicating one or more candidate relays for the indirect link. In some embodiments, the information in the link change message may include (1) the type of link change, (2) whether the direct IP addresses of the first and second WTRUs are to be reused for the indirect link, and / or (3) whether the indirect link is immediately or triggered by the conditions being met. Switching You may further indicate one or more of the following: whether or not.

[0126] As further illustrated in the embodiment of Figure 10, in (1020), the typical method (1000) may include the first WTRU receiving an acceptance message from the second WTRU containing information indicating a selected relay from one or more candidate relays for the indirect link. The typical method (1000) may also include, in (1030), registering the IP address of the first WTRU with the selected relay.

[0127] In some embodiments, the information in the acceptance message is used for and to trigger the indirect link based on whether the trigger condition has been met. Switching The reuse of the direct IP addresses of the first and second WTRUs may be further described. According to one embodiment, registering the IP address of the first WTRU with the selected relay (1030) includes registering the same IP address of the first WTRU for the indirect link as the IP address of the first WTRU for the established direct link after the trigger condition is met.

[0128] In some embodiments, the information in the acceptance message includes the reuse of the direct IP addresses of the first and second WTRUs for the indirect link, and the immediate access to the indirect link. Switching This may be further illustrated. According to one embodiment, registering the IP address of the first WTRU with the selected relay (1030) includes registering the same IP address of the first WTRU for the indirect link as the IP address of the first WTRU for the established direct link in response to the receipt of an acceptance message.

[0129] Referring again to Figure 10, in (1040), the representative method (1000) may include the first WTRU sending a link change acknowledgment message to the second WTRU. In (1050), method (1000) is from a direct link to an indirect link Switching In (1060), SwitchingLater, this may include communicating with a second WTRU via an indirect link. In some embodiments, although not shown in the embodiment of Figure 10, a typical method (1000) is to move from communication with a second WTRU using a direct link to communication with a second WTRU using an indirect link. Switching This may include deciding whether or not to do so.

[0130] It should be noted that in certain embodiments, the flowcharts illustrated in Figures 8 to 10 and / or the operations depicted therein can be combined in any preferred manner.

[0131] The contents of each of the following references are incorporated herein by reference in their entirety: (1) 3GPP TR 23.752 v1.1.0, “Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS) (Release 17)”, (2) 3GPP TDoc S2-2006575, “KI#4, New Sol: Negotiated UE-to-UE Relay Reselection”, (3) 3GPP TDoc S2-2007736, “KI#4, Sol#50: Update to add more details to UE-to-UE Relay Re-selection”, and (4) 3GPP TDoc S3-202706, “Modification of KI for TR 33.847 - security for UE2UE Relay path switch”.

[0132] A system and method for processing data according to a typical embodiment may be executed by one or more processors that execute a sequence of instructions contained in a memory device. Such instructions may be read into the memory device from other computer-readable media, such as a secondary data storage device. By executing the sequence of instructions contained in the memory device, the processor operates, for example, as described above. In alternative embodiments, hardwired circuits may be used instead of, or in combination with, software instructions to implement the present invention. Such software may be executed on a processor remotely housed in a Robotic Assistance / Apparatus (RAA) and / or another mobile device. In the latter case, data may be transferred by wire or wirelessly between the RAA or other mobile device including sensors and a remote device including a processor that executes software performing scale estimation and compensation as described above. According to other typical embodiments, some of the processing described above with respect to localization may be performed in a device including sensors / cameras, and the remainder of the processing may be performed in a second device after receiving partially processed data from the device including sensors / cameras.

[0133] While the features and elements are described 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. The methods described herein may also be implemented in computer programs, software, or firmware embedded in computer-readable media for execution by a computer or processor. Examples of non-temporary 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 Disks (DVDs). A radio frequency transceiver may be implemented using a software-associated processor for use in a WTRU102, UE, terminal, base station, RNC, or any host computer.

[0134] Furthermore, the embodiments described above include other devices, including processing platforms, computing systems, controllers, and processors. These devices may include at least one central processing unit ("Central Processing Unit, CPU") and memory. According to the convention of those skilled in the art of computer programming, references to operations and symbolic representations of arithmetic or instructions may be performed by various CPUs and memories. Such operations and arithmetic or instructions may be referred to as "executed," "computer executed," or "CPU executed."

[0135] Those skilled in the art will understand that operations and symbolically represented arithmetic or instructions involve the manipulation of electrical signals by the CPU. The electrical system represents data bits that can cause a resulting transformation or reduction of electrical signals, maintains these data bits in memory locations in the memory system, thereby reconfiguring or altering the CPU's operations and other signal processing. The memory location where the data bits are maintained is a physical location having specific electrical, magnetic, optical, or organic properties that correspond to or represent the data bits. It should be understood that representative embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided method.

[0136] Data bits may also be maintained on computer-readable media, including magnetic disks, optical disks, and any other volatile (e.g., random access memory ("RAM")) or CPU-readable, non-volatile (e.g., read-only memory ("ROM")) mass storage systems. The computer-readable media may include cooperative or interconnected computer-readable media distributed among multiple interconnected processing systems, which may reside exclusively on a processing system or be local or remote to the processing system. It will be understood that representative embodiments are not limited to the memory described above, and other platforms and memories may support the methods described. It should be understood that the representative embodiments are not limited to the platforms or CPUs described above, and other platforms and CPUs may support the provided methods.

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

[0138] There is little distinction between hardware and software implementations of a system configuration. The use of hardware or software is generally a design choice involving a cost-effectiveness trade-off (though not always, in certain situations the choice between hardware and software can be significant). There may be various vehicles (e.g., hardware, software, and / or firmware) that may affect the processes and / or systems and / or other technologies described herein, but the preferred vehicle may 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 paramount, the implementer may primarily choose hardware and / or firmware vehicles. If flexibility is paramount, the implementer may primarily choose software implementations. Alternatively, the implementer may choose any combination of hardware, software, and / or firmware.

[0139] The detailed description above illustrates various embodiments of devices and / or processes through the use of block diagrams, flowcharts, and / or examples. Those skilled in the art will understand that, insofar as such block diagrams, flowcharts, and / or examples include one or more functions and / or operations, each function and / or operation in such block diagrams, flowcharts, or examples may be implemented individually and / or collectively by a wide range of hardware, software, firmware, or substantially any combination thereof. Suitable processors include, by example, general-purpose processors, dedicated processors, conventional processors, digital signal processors (DSPs), multiple microprocessors, one or more microprocessors associated with a DSP core, controllers, microcontrollers, application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), field-programmable gate array (FPGA) circuits, any other type of integrated circuit (IC), and / or state machines.

[0140] This disclosure is not limited in terms of the specific embodiments described herein, which are intended to be illustrative of various aspects. As will be apparent to those skilled in the art, many modifications and variations may be made without departing from the spirit and scope of the invention. No element, operation, or instruction used in this application should be construed as important or essential to the invention unless expressly presented as such. In addition to those enumerated herein, functionally equivalent methods and apparatus within the scope of this disclosure will be apparent to those skilled in the art from the foregoing description. Such modifications and variations are intended to fall within the scope of the appended claims. This disclosure is limited only by the terms of the appended claims, and together with the full scope of the equivalents to which such claims are entitled. It should be understood that this disclosure is not limited to any particular method or system.

[0141] It should also be understood that the terms used herein are for the purpose of describing only specific embodiments and are not intended to limit them. Where used herein, “station” and its abbreviation “STA,” “user equipment” and its abbreviation “UE” may mean (i) a radio transmit and / or receive unit (WTRU) such as the infrastructure described herein, (ii) any of several embodiments of a WTRU such as the infrastructure described herein, (iii) a radio-enabled and / or wired (e.g., tetherable) device configured to have some or all of the structure and functions of a WTRU such as the infrastructure described herein, (iii) a radio-enabled and / or wired device configured to have less than all of the structure and functions of a WTRU such as the infrastructure described herein, or (iv) other. Details of exemplary WTRUs that may represent any UE listed herein are provided below with respect to Figures 1A to 1D.

[0142] In certain representative embodiments, some parts of the subject matter described herein may be implemented via application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), and / or other integrated formats. However, it will be recognized by those skilled in the art that some aspects of the embodiments disclosed herein can be equivalently implemented in an integrated circuit as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, or substantially any combination thereof, and that designing circuits and / or writing software and / or firmware code is within the scope of the art of those skilled in the art in light of this disclosure. It will also be understood by those skilled in the art that the mechanisms of the subject matter described herein can be distributed as various forms of program products, and that the representative embodiments of the subject matter described herein apply regardless of the specific type of signal transmission medium used to actually carry out the distribution. Examples of signal transmission media include, but are not limited to, recordable media such as floppy disks, hard disk drives, CDs, DVDs, digital tapes, and computer memory, as well as transmitting media such as digital communication media and / or analog communication media (e.g., optical fiber cables, waveguides, wired communication links, wireless communication links, etc.).

[0143] The subject matter described herein may, in some cases, represent different components that are contained within or connected to other different components. It should be understood that such depicted architectures are merely examples, and in practice, many other architectures can be implemented to achieve the same function. Conceptually, any arrangement of components to achieve the same function is effectively “associated” in such a way that the desired function can be achieved. Therefore, any two components combined herein to achieve a particular function, regardless of architecture or intermediate components, can be seen as “associated with” each other in such a way that the desired function can be achieved. Similarly, any two components thus associated may be considered “operably connected” or “operably coupled” to each other in order to achieve the desired function, and any two components that can be associated in such a way may be considered “operably coupleable” to each other in order to achieve the desired function. Specific examples of components that can be operably connected include, but are not limited to, components that are physically matable and / or physically interactable, and / or wirelessly interactable and / or logically interactable.

[0144] With regard to the use of substantially any plural and / or singular terms herein, a person skilled in the art may convert from plural to singular and / or singular to plural as appropriate to the context and / or use. Various singular / plural rearrangements may be explicitly described herein for clarity.

[0145] In general, it will be understood by those skilled in the art that the terms used herein, and in particular in the appended claims (e.g., the body of the appended claims), are generally intended to be “open” terms (for example, the term “including” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” and the term “includes” should be interpreted as “includes but is not limited to”). Furthermore, if a particular number of descriptions of introduced claims are intended, such intent is explicitly stated in the claims, and if such statement is not present, such intent is not present, it will be understood by those skilled in the art. For example, if only one item is intended, the term “single” or similar wording may be used. For the sake of understanding, the following appended claims and / or descriptions of this specification may include the use of the introductory phrases “at least one” and “one or more” to introduce the details of the claims. However, the use of such phrases should not be interpreted as meaning that the introduction of a claim description with the indefinite article "a" or "an" limits any particular claim containing such introduced description to embodiments containing only one such description, even if the same claim contains the introductory phrase "one or more" or "at least one)" and an indefinite article such as "a" or "an" (for example, "a" and / or "an" should be interpreted as meaning "at least one" or "one or more"). The same applies to the use of definite articles used to introduce a claim description.Furthermore, even if a specific number of claims introduced is explicitly stated, it will be recognized by those skilled in the art that such statements should be interpreted as meaning at least the stated number (for example, the simple statement “two recitations” without other modifiers means at least two statements, or two or more statements). In addition, when a notation similar to “at least one of A, B, and C, etc.” is used, such a structure is generally intended to mean what those skilled in the art would understand (for example, “a system having at least one of A, B, and C” includes, but is not limited to, a system having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). Where expressions similar to "at least one of A, B, or C" are used, such structures are generally intended to mean what a person skilled in the art would understand (for example, "a system having at least one of A, B, or C" includes, but is not limited to, systems having only A, only B, only C, A and B together, A and C together, B and C together, and / or A, B, and C together). A person skilled in the art will further understand that substantially any disjunct words and / or phrases presenting two or more alternative terms in the specification, claims, or drawings should be understood as intending to include the possibility of including one of the terms, either of the terms, or both of the terms. For example, the phrase "A or B" should be understood to include the possibilities of "A" or "B" or "A and B".Furthermore, as used herein, the term “any of ~” followed by a list of multiple items and / or a list of categories of multiple items is intended to include any of, any combination of, any multiple of, and / or any combination of multiples of, items and / or categories of items, individually or in combination with other items and / or categories of other items. Furthermore, as used herein, the terms “set” or “group” are intended to include any number of items, including zero. In addition, as used herein, the term “number” is intended to include any number, including zero.

[0146] Where any feature or aspect of this disclosure is described from the perspective of the Markush group, a person skilled in the art will recognize that this disclosure also describes any individual component or subgroup of components of the Markush group.

[0147] As will be understood by those skilled in the art, for all purposes, including providing written descriptions, all scopes disclosed herein also encompass any possible sub-scopes and combinations of sub-scopes. Any enumerated scope can be readily recognized as fully explaining and enabling that the same scope can be broken down into at least equal 1 / 2, 1 / 3, 1 / 4, 1 / 5, 1 / 10, etc. In non-limiting embodiments, each scope considered herein may readily be broken down into a lower third, a middle third, an upper third, etc. Also, as will be understood by those skilled in the art, all words such as “up to,” “at least,” “greater than,” and “less than” include the number mentioned and mean a scope that can be further broken down into sub-scopes as considered above. Finally, as will be understood by those skilled in the art, a scope includes each individual element. 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.

[0148] Furthermore, claims should not be read as being limited to the order or elements provided unless specifically stated so. In any claim, the use of the term “means for” is intended to appeal to Section 112, paragraph 6 of the U.S. Patent Act or the means-plus-function claim format; no claim without the term “means for” is intended to appeal to the means for which it is used.

[0149] A radio frequency transceiver may be implemented using a software-related processor for use in a radio transmit / receive unit (WTRU), user equipment (UE), terminal, base station, mobility management entity (MME), or evolved packet core (EPC), or any host computer. The WTRU may be used in conjunction with hardware and / or software-implemented modules such as software-defined radio (SDR), and may also be implemented in other components such as cameras, video camera modules, video phones, speakerphones, vibration devices, speakers, microphones, television transceivers, hands-free headsets, keyboards, Bluetooth® modules, frequency modulation (FM) radio units, near-field communication (NFC) modules, liquid crystal display (LCD) display units, organic light-emitting diode (OLED) display units, digital music players, media players, video game player modules, internet browsers, and / or wireless local area network (WLAN) or ultra-wideband (UWB) modules.

[0150] Through this disclosure, those skilled in the art will understand that certain representative embodiments may be used in combination with alternative or other representative embodiments.

[0151] The methods described herein may be implemented in computer programs, software, or firmware that are incorporated as instructions into a computer-readable storage medium for execution by a computer or processor to perform the operations described above. Examples of non-temporary 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 multipurpose disks (DVDs). A radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer may be implemented using a processor associated with the software.

Claims

1. A method carried out by a first wireless transmission and reception unit (first WTRU), Steps to perform the discovery procedure, Based on the results of the discovery procedure performed, the step of detecting that the second WTRU is directly reachable, Following the established indirect link with the second WTRU, the step of initiating the establishment of a direct PC5 link with the second WTRU is: A step of switching from the indirect link to the PC5 direct link, wherein the switching from the indirect link to the PC5 direct link includes initiating an indirect-to-direct route switching, which includes sending a message containing indirect link information, wherein the indirect link information includes any of the following: (1) one or more relay identifiers associated with the indirect link, (2) the Internet Protocol address of the first WTRU, (3) the Internet Protocol address of the second WTRU, (4) an application identifier, and (5) user information of the second WTRU. The first WTRU, after the route switching, communicates with the second WTRU via the direct link to the PC 5, A method for providing this.

2. The method according to claim 1, wherein the message includes a direct communication request message or a direct security mode completion message.

3. The method according to claim 1, wherein the message includes information indicating a preference by the first WTRU that the Internet Protocol addresses of the first WTRU and the second WTRU used for the indirect link will be reused for the PC5 direct link.

4. The step of receiving an acceptance message, which includes information confirming that the Internet Protocol addresses of the first WTRU and the second WTRU used for the indirect link will be reused for the PC5 direct link, The method according to claim 3, further comprising:

5. The method according to claim 1, wherein the message includes information indicating the type of route switching.

6. The steps include receiving information indicating whether or not to switch to the PC5 direct link based on whether the trigger condition is met, A step of determining whether the trigger condition is met, Based on the fact that the trigger condition is met, the step of triggering the switching from the indirect link to the PC5 direct link, The method according to claim 1, further comprising:

7. The steps include sending a Domain Name System query message containing information indicating proximity-based services (ProSe) for indirect links, The steps include receiving a Domain Name System response message containing the Internet Protocol address and user information of the second WTRU, The method according to claim 1, further comprising:

8. A first wireless transmit / receive unit (first WTRU), Perform the discovery procedure, Based on the results of the discovery procedure performed, it is detected that the second WTRU is directly reachable. Following the establishment of the indirect link with the second WTRU, the establishment of a direct PC5 link with the second WTRU is initiated. Switching from the indirect link to the direct PC5 link, the switching from the indirect link to the direct PC5 link, includes initiating an indirect-to-direct route switching, which includes sending a message containing indirect link information, and the indirect link information is configured to include any of the following: (1) one or more relay identifiers associated with the indirect link, (2) the Internet Protocol address of the first WTRU, (3) the Internet Protocol address of the second WTRU, (4) an application identifier, and (5) user information of the second WTRU. Processor and After the aforementioned route switching, a transmitter / receiver configured to communicate with the second WTRU via the PC5 direct link, A first WTRU equipped with [a specific feature].

9. The first WTRU according to claim 8, wherein the message includes a direct communication request message or a direct security mode completion message.

10. The first WTRU according to claim 8, wherein the message includes information indicating a preference by the first WTRU, where the Internet Protocol addresses of the first WTRU and the second WTRU used for the indirect link will be reused for the PC5 direct link.

11. The transmitter / receiver is The first WTRU according to claim 10, configured to receive an acceptance message containing information confirming that the Internet Protocol addresses of the first WTRU and the second WTRU used for the indirect link are to be reused for the PC5 direct link.

12. The WTRU according to claim 8, wherein the message includes information indicating the type of route switching.

13. The transmitter / receiver is It is configured to receive information indicating whether or not to switch to the PC5 direct link based on whether the trigger condition is met. The aforementioned processor, Determine whether the aforementioned trigger condition is met. The first WTRU according to claim 8, configured to trigger the switching from the indirect link to the PC5 direct link based on whether the trigger condition is met.

14. The transmitter / receiver is Send a Domain Name System query message containing information indicating Proximity-Based Services (ProSe) for indirect links. The first WTRU according to claim 8, configured to receive a Domain Name System response message containing the Internet Protocol address and user information of the second WTRU.

Citation Information

Patent Citations

  • Method and apparatus for device-to-device (D2D) mobility in wireless systems

    JP2015521455A

  • Mobile communication system, user terminal, base station, and processor

    WO2014106936A1