Relay communication support

Abstract

A method is provided in one embodiment of the disclosure. The method can include the steps of: sending a request message related to a UE context to a DU of a base station; and receiving a response message related to the UE context from the DU.

Description

Technical Field

[0001] This specification relates to a type of radio communication. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a technology for achieving high-speed packet communication. Many proposals have been put forward for LTE goals, including those aimed at reducing costs for users and providers, improving service quality, and expanding and increasing coverage and system capacity. 3GPP LTE requires lower cost per bit, increased service availability, flexible use of frequency bands, a simple architecture, open interfaces, and appropriate power consumption in terminals as higher-level requirements.

[0003] Work has begun within the International Telecommunication Union (ITU) and 3GPP to develop requirements and specifications for New Radio (NR) systems. 3GPP must identify and develop the technical components necessary for the successful standardization of the new RAT, meeting both pressing market demands and the longer-term requirements outlined in the ITU Radiocommunication Sector (ITU-R) International Mobile Telecommunications (IMT)-2020 process. Furthermore, NR should be able to utilize any frequency band within at least up to 130 GHz, and these bands should be available for wireless communication even in the more distant future.

[0004] The goal of NR is to address all use cases, requirements, and deployment scenarios with a single technology framework, including enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable and low-latency communications (URLLC). NR should inherently be backward compatible.

[0005] Based on current technology, there is no solution that supports relay communication between terminals. Summary of the Invention

[0006] Technical solution

[0007] According to embodiments of this disclosure, a method is provided. The method may include sending a request message related to a UE context to a DU (Distributed Utility Unit) of a base station; and receiving a response message related to a UE context from the DU.

[0008] According to an embodiment, an apparatus for implementing the method is provided.

[0009] According to embodiments of this disclosure, a method is provided. The method may include sending a request message related to a UE context from a CU of a base station; and sending a response message related to a UE context to the CU.

[0010] According to an embodiment, an apparatus for implementing the method is provided. Attached Figure Description

[0011] Figure 1 An example of a communication system that applies the implementation of this disclosure is shown.

[0012] Figure 2 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0013] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0014] Figure 4 An example of a 5G system architecture applying the implementation of this disclosure is shown.

[0015] Figure 5 This is an example of a U2U remote UE connection establishment process according to an embodiment of the present disclosure.

[0016] Figure 6 This is an example of a process for supporting U2U relay operation according to an embodiment of this disclosure.

[0017] Figure 7 An example of a process according to an embodiment of this disclosure is shown. Detailed Implementation

[0018] The following technologies, devices, and systems can be applied to a variety of wireless multiple access systems. Examples of multiple access systems include Code Division Multiple Access (CDMA) systems, Frequency Division Multiple Access (FDMA) systems, Time Division Multiple Access (TDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single-Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Multi-Carrier Frequency Division Multiple Access (MC-FDMA) systems. CDMA can be implemented using radio technologies such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented using radio technologies such as Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), or Enhanced Data Rate GSM Evolution (EDGE). OFDMA can be implemented using radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, or Evolved UTRA (E-UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). The 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is part of the Evolved UMTS (E-UMTS) using E-UTRA. 3GPP LTE employs OFDMA in the downlink (DL) and SC-FDMA in the uplink (UL). The evolution of 3GPP LTE includes LTE-Advanced (LTE-A), LTE-A Pro, and / or 5G New Radio (NR).

[0019] For ease of description, the implementation of this disclosure is primarily described with respect to 3GPP-based wireless communication systems. However, the technical features of this disclosure are not limited thereto. For example, although the following detailed description is based on mobile communication systems corresponding to 3GPP-based wireless communication systems, the aspects of this disclosure that are not limited to 3GPP-based wireless communication systems are applicable to other mobile communication systems.

[0020] For any terms and techniques used in this disclosure that are not specifically described in this disclosure, please refer to wireless communication standards documents published prior to this disclosure.

[0021] In this disclosure, "A or B" can mean "A only", "B only", or "both A and B". In other words, "A or B" in this disclosure can be interpreted as "A and / or B". For example, "A, B or C" in this disclosure can mean "A only", "B only", "C only", or "any combination of A, B and C".

[0022] In this disclosure, a forward slash ( / ) or a comma (,) can mean "and / or". For example, "A / B" can mean "A and / or B". Therefore, "A / B" can mean "A only", "B only", or "both A and B". For example, "A, B, C" can mean "A, B, or C".

[0023] In this disclosure, "at least one of A and B" can mean "only A", "only B" or "both A and B". Furthermore, the expressions "at least one of A or B" or "at least one of A and / or B" in this disclosure can be interpreted as the same as "at least one of A and B".

[0024] Additionally, in this disclosure, "at least one of A, B, and C" may mean "only A," "only B," "only C," or "any combination of A, B, and C." Furthermore, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C."

[0025] Furthermore, the brackets used in this disclosure may mean "for example". Specifically, when it is shown as "Control Information (PDCCH)", "PDCCH" can be cited as an example of "Control Information". In other words, "Control Information" in this disclosure is not limited to "PDCCH", and "PDCCH" can be cited as an example of "Control Information". In addition, even when shown as "Control Information (i.e., PDCCH)", "PDCCH" can be cited as an example of "Control Information".

[0026] The technical features described individually in one of the accompanying drawings of this disclosure can be implemented individually or simultaneously.

[0027] Although not limited thereto, the various descriptions, functions, processes, suggestions, methods and / or operation flowcharts disclosed herein can be applied to various fields that require wireless communication and / or connectivity between devices (e.g., 5G).

[0028] In the following description, this disclosure will be described in more detail with reference to the accompanying drawings. Unless otherwise stated, the same reference numerals in the following drawings and / or description may refer to the same and / or corresponding hardware blocks, software blocks and / or functional blocks.

[0029] Figure 1 An example of a communication system that applies the implementation of this disclosure is shown.

[0030] Figure 1 The 5G use cases shown are merely illustrative, and the technical features of this disclosure can be applied to... Figure 1 Other 5G use cases not shown.

[0031] The three main requirement categories for 5G include (1) Enhanced Mobile Broadband (eMBB), (2) Massive Machine Type Communications (mMTC), and (3) Ultra Reliable and Low Latency Communications (URLLC).

[0032] Reference Figure 1 The communication system 1 includes wireless devices 100a to 100f, a base station (BS) 200, and a network 300. Although Figure 1 An example of a 5G network as a network of communication system 1 is shown, but the implementation of this disclosure is not limited to 5G systems and can be applied to future communication systems other than 5G systems.

[0033] BS 200 and network 300 can be implemented as wireless devices, and a particular wireless device can operate as a BS / network node relative to other wireless devices.

[0034] Wireless devices 100a to 100f represent devices that perform communication using radio access technology (RAT) (e.g., 5G NR or LTE) and may be referred to as communication / radio / 5G devices. Wireless devices may include (but are not limited to) robots 100a, vehicles 100b-1 and 100b-2, extended reality (XR) devices 100c, handheld devices 100d, home appliances 100e, Internet of Things (IoT) devices 100f, and artificial intelligence (AI) devices / servers 400. For example, vehicles may include vehicles with wireless communication capabilities, autonomous vehicles, and vehicles capable of performing communication between vehicles. Vehicles may include unmanned aerial vehicles (UAVs) (e.g., drones). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices and may be implemented in the form of head-mounted displays (HMDs), head-up displays (HUDs) installed in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Handheld devices may include smartphones, smart tablets, wearable devices (e.g., smartwatches or smart glasses), and computers (e.g., laptops). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters.

[0035] In this disclosure, wireless devices 100a to 100f may be referred to as user equipment (UE). UE may include, for example, cellular phones, smartphones, laptop computers, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigation systems, tablet PCs, tablet PCs, ultrabooks, vehicles, vehicles with autonomous driving capabilities, connected cars, UAVs, AI modules, robots, AR devices, VR devices, MR devices, holographic devices, public safety devices, MTC devices, IoT devices, medical devices, FinTech devices (or financial devices), security devices, weather / environment devices, devices related to 5G services, or devices related to the Fourth Industrial Revolution.

[0036] Wireless devices 100a to 100f can connect to network 300 via BS 200. AI technology can be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f can connect to AI server 400 via network 300. Network 300 can be configured using 3G, 4G (e.g., LTE), 5G (e.g., NR), and super 5G networks. Although wireless devices 100a to 100f can communicate with each other via BS 200 / network 300, wireless devices 100a to 100f can also perform direct communication (e.g., sidelink communication) without going through BS 200 / network 300. For example, vehicles 100b-1 and 100b-2 can perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). IoT devices (e.g., sensors) can perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100a to 100f.

[0037] Wireless communication / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f and / or between wireless devices 100a to 100f and BS 200 and / or between BS 200. In this document, wireless communication / connections can be established via various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication (or device-to-device (D2D) communication) 150b, and inter-base station communication 150c (e.g., relay, integrated access and backhaul (IAB)). Wireless devices 100a to 100f and BS 200 / wireless devices 100a to 100f can send / receive radio signals to / from each other via wireless communication / connections 150a, 150b, and 150c. For example, wireless communication / connections 150a, 150b, and 150c can send / receive signals via various physical channels. Therefore, at least a portion of various configuration information configuration processes, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and resource allocation processes for transmitting / receiving radio signals can be performed based on various proposals of this disclosure.

[0038] NR supports multiple parameter sets (and / or multiple subcarrier spacings (SCS)) to support a variety of 5G services. For example, if the SCS is 15 kHz, wide-area coverage can be supported in traditional cellular bands, and if the SCS is 30 kHz / 60 kHz, dense urban areas, lower latency, and wider carrier bandwidth can be supported. If the SCS is 60 kHz or higher, bandwidths greater than 24.25 GHz can be supported to overcome phase noise.

[0039] NR bands can be defined as two types of frequency ranges: frequency range 1 (FR1) and frequency range 2 (FR2). The numerical values ​​of the frequency ranges can be varied. For example, the two types (FR1 and FR2) of frequency ranges can be shown in Table 1 below. For ease of explanation, in the frequency ranges used in NR systems, FR1 can represent "below 6 GHz range," FR2 can represent "above 6 GHz range," and can be referred to as millimeter wave (mmW).

[0040] [Table 1]

[0041] As mentioned above, the frequency range of the NR system can be varied. For example, FR1 can include a frequency band from 410MHz to 7125MHz, as shown in Table 2 below. That is, FR1 can include a frequency band of 6GHz (or 5850MHz, 5900MHz, 5925MHz, etc.) or higher. For example, the frequencies of 6GHz (or 5850MHz, 5900MHz, 5925MHz, etc.) or higher included in FR1 can include unlicensed frequency bands. Unlicensed frequency bands can be used for various purposes, such as for vehicle communications (e.g., autonomous driving).

[0042] [Table 2]

[0043] Here, the radio communication technologies implemented in the wireless devices of this disclosure may include narrowband IoT (NB-IoT) technologies for low-power communication, as well as LTE, NR, and 6G. For example, NB-IoT technology may be an example of low-power wide-area network (LPWAN) technology, implemented in specifications such as LTE Cat NB1 and / or LTE Cat NB2, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may communicate based on LTE-M technology. For example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as enhanced MTC (eMTC). For example, LTE-M technology may be implemented in at least one of various specifications such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-bandwidth limited (non-BL), 5) LTE-MTC, 6) LTE machine-type communication, and / or 7) LTE M, and may not be limited to the names mentioned above. Additionally and / or alternatively, the radio communication technologies implemented in the wireless devices of this disclosure may include at least one of ZigBee, Bluetooth, and / or LPWAN, which take into account low-power communication, and may not be limited to the names mentioned above. For example, ZigBee technology may generate personal area networks (PANs) associated with low-power / low-power digital communication based on various specifications such as IEEE 802.15.4, and may be referred to by various names.

[0044] Figure 2 An example of a wireless device that applies an implementation of the present disclosure is shown.

[0045] exist Figure 2 In this context, the first wireless device 100 and / or the second wireless device 200 can be implemented in various forms depending on the use case / service. For example, {the first wireless device 100 and the second wireless device 200} can correspond to... Figure 1 At least one of {wireless devices 100a to 100f and BS 200}, {wireless devices 100a to 100f and wireless devices 100a to 100f} and / or {BS 200 and BS 200}. The first wireless device 100 and / or the second wireless device 200 may be configured from various elements, devices / components and / or modules.

[0046] The first wireless device 100 may include at least one transceiver (e.g., transceiver 106), at least one processing chip (e.g., processing chip 101), and / or one or more antennas 108.

[0047] The processing chip 101 may include at least one processor (e.g., processor 102) and at least one memory (e.g., memory 104). Additionally and / or alternatively, the memory 104 may be located outside the processing chip 101.

[0048] Processor 102 can control memory 104 and / or transceiver 106, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 102 can process information in memory 104 to generate first information / signal, and then transmit a radio signal including the first information / signal via transceiver 106. Processor 102 can receive a radio signal including a second information / signal via transceiver 106, and then store the information obtained by processing the second information / signal in memory 104.

[0049] Memory 104 may be operatively connected to processor 102. Memory 104 may store various types of information and / or instructions. Memory 104 may store firmware and / or software code 105 that implements code, commands, and / or command sets, which, when executed by processor 102, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 105 may implement instructions that, when executed by processor 102, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 105 may control processor 102 to execute one or more protocols. For example, firmware and / or software code 105 may control processor 102 to execute one or more layers of a radio interface protocol.

[0050] In this document, processor 102 and memory 104 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 106 may be connected to processor 102 and transmit and / or receive radio signals via one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. Transceiver 106 may be used interchangeably with radio frequency (RF) units. In this disclosure, first wireless device 100 may represent a communication modem / circuit / chip.

[0051] The second wireless device 200 may include at least one transceiver (e.g., transceiver 206), at least one processing chip (e.g., processing chip 201), and / or one or more antennas 208.

[0052] The processing chip 201 may include at least one processor (e.g., processor 202) and at least one memory (e.g., memory 204). Additionally and / or alternatively, the memory 204 may be located outside the processing chip 201.

[0053] Processor 202 can control memory 204 and / or transceiver 206, and can be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts described in this disclosure. For example, processor 202 can process information in memory 204 to generate third information / signal, and then transmit a radio signal including the third information / signal via transceiver 206. Processor 202 can receive a radio signal including a fourth information / signal via transceiver 106, and then store the information obtained by processing the fourth information / signal in memory 204.

[0054] Memory 204 may be operatively connected to processor 202. Memory 204 may store various types of information and / or instructions. Memory 204 may store firmware and / or software code 205 that implements code, commands, and / or command sets, which, when executed by processor 202, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 205 may implement instructions that, when executed by processor 202, execute the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. For example, firmware and / or software code 205 may control processor 202 to execute one or more protocols. For example, firmware and / or software code 205 may control processor 202 to execute one or more layers of a radio interface protocol.

[0055] In this document, processor 202 and memory 204 may be part of a communication modem / circuit / chip designed to implement RAT (e.g., LTE or NR). Transceiver 206 may be connected to processor 202 and transmit and / or receive radio signals via one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. Transceiver 206 may be used interchangeably with an RF unit. In this disclosure, second wireless device 200 may represent a communication modem / circuit / chip.

[0056] The hardware elements of wireless devices 100 and 200 will be described in more detail below. One or more protocol layers can be implemented by (but are not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 can implement one or more layers (e.g., functional layers such as the Physical (PHY) layer, Medium Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Service Data Adaptation Protocol (SDAP) layer). One or more processors 102 and 202 can generate one or more Protocol Data Units (PDUs), one or more Service Data Units (SDUs), messages, control information, data, or information in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. One or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure, and provide the generated signals to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive signals (e.g., baseband signals) from one or more transceivers 106 and 206, and acquire PDUs, SDUs, messages, control information, data, or information, in accordance with the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure.

[0057] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field-programmable gate arrays (FPGAs) may be included in one or more processors 102 and 202. For example, one or more processors 102 and 202 may be configured by a set of communication control processors, application processors (APs), electronic control units (ECUs), central processing units (CPUs), graphics processing units (GPUs), and memory control processors. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories 104 and 204 may be configured with random access memory (RAM), dynamic RAM (DRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EPROM), flash memory, volatile memory, non-volatile memory, hard disk drive, registers, buffer memory, computer-readable storage media, and / or combinations thereof. One or more memories 104 and 204 may be located internally and / or externally to one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0058] One or more transceivers 106 and 206 can transmit user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure to one or more other devices. One or more transceivers 106 and 206 can receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure from one or more other devices. For example, one or more transceivers 106 and 206 can be connected to one or more processors 102 and 202 and transmit and receive radio signals. For example, one or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to transmit user data, control information, or radio signals to one or more other devices. One or more processors 102 and 202 can perform control to enable one or more transceivers 106 and 206 to receive user data, control information, or radio signals from one or more other devices.

[0059] One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208. Additionally and / or alternatively, one or more transceivers 106 and 206 may include one or more antennas 108 and 208. One or more transceivers 106 and 206 may be adapted to transmit and receive user data, control information, and / or radio signals / channels mentioned in the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein via one or more antennas 108 and 208. In this disclosure, one or more antennas 108 and 208 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0060] One or more transceivers 106 and 206 can convert received user data, control information, radio signals / channels, etc., from RF band signals into baseband signals so that the received user data, control information, radio signals / channels, etc., can be processed by one or more processors 102 and 202. One or more transceivers 106 and 206 can also convert user data, control information, radio signals / channels, etc., processed by one or more processors 102 and 202 from baseband signals into RF band signals. For this purpose, one or more transceivers 106 and 206 may include (analog) oscillators and / or filters. For example, one or more transceivers 106 and 206, under the control of one or more processors 102 and 202, can up-convert OFDM baseband signals to OFDM signals using their (analog) oscillators and / or filters, and transmit the up-converted OFDM signals at the carrier frequency. One or more transceivers 106 and 206 can receive OFDM signals at a carrier frequency and, under the control of one or more processors 102 and 202, downconvert the OFDM signals to OFDM baseband signals via their (analog) oscillators and / or filters.

[0061] although Figure 2 Not shown, but wireless devices 100 and 200 may also include additional components. Additional component 140 may be configured differently depending on the type of wireless devices 100 and 200. For example, additional component 140 may include at least one of a power unit / battery, input / output (I / O) devices (e.g., audio I / O ports, video I / O ports), drive devices, and computing devices. Additional component 140 may be coupled to one or more processors 102 and 202 via various technologies such as wired or wireless connections.

[0062] In the implementation of this disclosure, the UE can operate as a transmitting device in the uplink (UL) and as a receiving device in the downlink (DL). In the implementation of this disclosure, the BS can operate as a receiving device in the UL and as a transmitting device in the DL. Hereinafter, for ease of description, it is primarily assumed that the first wireless device 100 acts as the UE and the second wireless device 200 acts as the BS. For example, a processor 102 connected to, installed on, or started in the first wireless device 100 can be adapted to perform UE operations according to the implementation of this disclosure, or to control the transceiver 106 to perform UE operations according to the implementation of this disclosure. A processor 202 connected to, installed on, or started in the second wireless device 200 can be adapted to perform BS operations according to the implementation of this disclosure, or to control the transceiver 206 to perform BS operations according to the implementation of this disclosure.

[0063] In this disclosure, BS is also referred to as Node B (NB), eNodeB (eNB), or gNB.

[0064] Figure 3 An example of a UE that applies the implementation of this disclosure is shown.

[0065] Reference Figure 3 UE 100 can correspond to Figure 2 The first wireless device 100.

[0066] The UE 100 includes a processor 102, a memory 104, a transceiver 106, one or more antennas 108, a power management module 141, a battery 142, a display 143, a keyboard 144, a subscriber identification module (SIM) card 145, a speaker 146, and a microphone 147.

[0067] Processor 102 may be adapted to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. Processor 102 may be adapted to control one or more other components of UE 100 to implement the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed in this disclosure. A layer of the radio interface protocol may be implemented in processor 102. Processor 102 may include an ASIC, other chipsets, logic circuits, and / or data processing devices. Processor 102 may be an application processor. Processor 102 may include at least one of a DSP, CPU, GPU, and modem (modulator and demodulator). Examples of processor 102 may be found in the SNAPDRAGON™ series processors manufactured by Qualcomm®, the EXYNOS™ series processors manufactured by Samsung®, the A-series processors manufactured by Apple®, the HELIO™ series processors manufactured by MediaTek®, the ATOM™ series processors manufactured by Intel®, or corresponding next-generation processors.

[0068] Memory 104 is operatively coupled to processor 102 and stores various information for operating processor 102. Memory 104 may include ROM, RAM, flash memory, memory card, storage medium, and / or other storage devices. When the implementation is software-based, the techniques described herein can be implemented using modules (e.g., processes, functions, etc.) that perform the descriptions, functions, processes, suggestions, methods, and / or operation flowcharts disclosed herein. Modules may be stored in memory 104 and executed by processor 102. Memory 104 may be implemented within or outside processor 102, in which case those memories may be communicatively coupled to processor 102 via various means known in the art.

[0069] Transceiver 106 is operatively coupled to processor 102 and transmits and / or receives radio signals. Transceiver 106 includes a transmitter and a receiver. Transceiver 106 may include baseband circuitry for processing radio frequency signals. Transceiver 106 controls one or more antennas 108 to transmit and / or receive radio signals.

[0070] The power management module 141 manages the power of the processor 102 and / or transceiver 106. The battery 142 supplies power to the power management module 141.

[0071] Display 143 outputs the results processed by processor 102. Keyboard 144 receives input that will be used by processor 102. Keyboard 144 can be displayed on display 143.

[0072] The SIM 145 is an integrated circuit designed to securely store the International Mobile Subscriber Identity (IMSI) number and its associated keys. The IMSI number and its associated keys are used to identify and authenticate subscribers on mobile devices such as mobile phones and computers. It can also store contact information associated with many SIM cards.

[0073] Speaker 146 outputs sound-related results processed by processor 102. Microphone 147 receives sound-related input to be used by processor 102.

[0074] Figure 4 An example of a 5G system architecture applying the implementation of this disclosure is shown.

[0075] The 5G system (5GS) architecture includes the following network functions (NFs).

[0076] - Authentication Server Function (AUSF)

[0077] - Access and Mobility Management Function (AMF)

[0078] - Data networks (DN), such as carrier services, internet access, or third-party services.

[0079] - Unstructured Data Storage Function (UDSF)

[0080] - Network Exposure Function (NEF)

[0081] - Intermediate NEF (I-NEF)

[0082] - Network Repository Function (NRF)

[0083] - Network Slice Selection Function (NSSF)

[0084] - Policy Control Function (PCF)

[0085] - Session Management Function (SMF)

[0086] - Unified Data Management (UDM)

[0087] - Unified Data Repository (UDR)

[0088] - User Plane Function (UPF)

[0089] - UE Radio Capability Management Function (UCMF)

[0090] - Application Functionality (AF)

[0091] - User Equipment (UE)

[0092] - (Radio) Access Network ((R)AN)

[0093] - 5G-Device Identifier Register (5G-EIR)

[0094] - Network Data Analysis Function (NWDAF)

[0095] - Billing Function (CHF)

[0096] In addition, the following network functions can be considered.

[0097] - Non-3GPP Interoperability Function (N3IWF)

[0098] - Trusted Non-3GPP Gateway Function (TNGF)

[0099] - Wired Access Gateway Function (W-AGF)

[0100] Figure 4 The architecture of a 5G system in a non-roaming scenario is depicted, using reference point representations to show how various network functions interact with each other.

[0101] exist Figure 4 For clarity of the point-to-point graph, UDSF, NEF, and NRF are not depicted. However, all depicted network functions can interact with UDSF, UDR, NEF, and NRF as needed.

[0102] For clarity, Figure 4 The document does not depict the UDR or its connections to other NFs (e.g., PCFs). For clarity, Figure 4 The NWDAF and its connections with other NFs (e.g., PCF) are not described.

[0103] The 5G system architecture includes the following reference points: - N1: Reference point between UE and AMF.

[0104] - N2: Reference point between (R)AN and AMF.

[0105] - N3: Reference point between (R)AN and UPF.

[0106] - N4: Reference point between SMF and UPF.

[0107] - N6: Reference point between UPF and data network.

[0108] - N9: Reference point between the two UPFs.

[0109] The reference points below illustrate the interactions that exist between NF services in NF.

[0110] - N5: Reference point between PCF and AF.

[0111] - N7: Reference point between SMF and PCF.

[0112] - N8: Reference point between UDM and AMF.

[0113] - N10: Reference point between UDM and SMF.

[0114] - N11: Reference point between AMF and SMF.

[0115] - N12: Reference point between AMF and AUSF.

[0116] - N13: Reference point between UDM and AUSF.

[0117] - N14: Reference point between the two AMFs.

[0118] - N15: Reference point between PCF and AMF in non-roaming scenarios, and reference point between PCF and AMF in the surveyed network in roaming scenarios.

[0119] - N16: A reference point between two SMFs (between an SMF in the visited network and an SMF in the home network in a roaming situation).

[0120] - N22: Reference point between AMF and NSSF.

[0121] In some cases, several NFs may need to be associated with each other to serve the UE.

[0122] A solution is needed to support signaling and data transmission between a U2U remote UE and a peer U2U remote UE via a U2U relay UE. For example, the following needs to be discussed.

[0123] A mechanism needs to be discussed to support single-hop Layer 2 and Layer 3 UE-to-UE relay (i.e., source UE -> relay UE -> destination UE) for unicast.

[0124] For Layer 2 and Layer 3 relays, relay discovery and (re)selection can be discussed first. In addition, signaling support for relay and remote UE authorization needs to be discussed.

[0125] Layer 2 relay-specific components may include, for example, UE-to-UE relay adaptation layer design, control plane procedures, and QoS handling (if required).

[0126] For reference, for relays, it is worth considering supporting compatibility with two or more hops (e.g., forward compatibility) in subsequent versions.

[0127] For reference, a remote UE can connect to only one relay UE for a specified target UE at a specified time.

[0128] Reference Figure 5 This example describes the connection establishment process for an L2 U2U remote UE.

[0129] The following figures were created to illustrate specific examples of this disclosure. Specific names of devices or signals / messages / fields described in the figures are presented by way of example, and therefore the technical features of this disclosure are not limited to the specific names used in the following figures.

[0130] Figure 5 This is an example of a U2U remote UE connection establishment process according to an embodiment of the present disclosure.

[0131] Reference Figure 5 Examples are provided to illustrate control plane procedures used in L2 U2U relays.

[0132] L2 U2U remote UEs need to establish an end-to-end SL-SRB (signaling radio bearer) / DRB (data radio bearer) with their peer L2 U2U remote UEs before transmitting data in the user plane.

[0133] For reference, in this disclosure, sidelink or SL is an example of inter-terminal communication, and the scope of this disclosure is not limited to the term sidelink or SL. For example, in this disclosure, any other term related to inter-terminal communication may be used instead of sidelink or SL.

[0134] Figure 5 The higher-layer connection establishment procedure shown in the example can be applied to L2 U2U relay UEs and L2 U2U remote UEs: 1. It can perform the discovery process.

[0135] For example, L2 U2U remote UEs, L2 U2U relay UEs, and peer L2 U2U remote UEs perform discovery procedures or integrated discovery procedures.

[0136] 2a. An L2 U2U remote UE can establish a PC5 connection with an L2 U2U trunk UE. For example, an L2 U2U remote UE can establish / modify a PC5-RRC connection with a selected L2 U2U trunk UE (as specified in TS 23.304 V18.0.0).

[0137] 2a. An L2 U2U trunk UE can establish a PC5 connection with a peer L2 remote trunk UE. For example, an L2 U2U trunk UE can establish / modify a PC5-RRC connection with a peer L2 U2U remote UE (e.g., as specified in TS 23.304 V18.0.0).

[0138] 3. A U2U relay UE can assign local IDs to both the U2U remote UE and its peer U2U remote UE via an RRC reconfiguration message (e.g., RRCReconfigurationSidelink). For example, an L2 U2U relay UE may assign two local IDs, which can be delivered to each L2 U2U remote UE via the RRCReconfigurationSidelink message. One local ID may identify the L2U2U remote UE, and the other local ID may identify the peer L2 U2U remote UE. When delivering the local IDs, the L2 IDs of the peer L2 U2U remote UEs can also be delivered to the U2U remote UEs to establish an association (e.g., association) between the local IDs and the L2 IDs of the peer L2 U2U remote UEs.

[0139] 4. End-to-end PC5 connection establishment can be performed. For example, an L2 U2U remote UE can establish an end-to-end PC5-RRC connection with a peer L2 U2U remote UE via an L2 U2U trunk UE. For end-to-end connection establishment, fixed indices (i.e., 0 / 1 / 2 / 3) are defined for end-to-end SL-SRB 0 / 1 / 2 / 3 respectively, and a specified PC5 trunk RLC channel is configured in each hop. Sidelink UE capabilities can be exchanged between L2 U2U remote UEs via PC5-RRC (e.g., SL-SRB3) messages.

[0140] 5. The L2 U2U remote UE can send end-to-end QoS related information to the relay UE. The L2 U2U remote UE can send all QoS profiles for end-to-end QoS flows to the L2 U2U relay UE via PC5-RRC.

[0141] 6. L2 U2U relay UEs can perform QoS splitting only for PDBs.

[0142] 7. U2U relays can send information related to split QoS to remote UEs.

[0143] For example, an L2 U2U relay UE can send a split QoS value (i.e., PDB) to an L2 U2U remote UE via a PC5-RRC message.

[0144] 8. End-to-end RRC reconfiguration related to inter-terminal communication can be performed. For example, the serving gNB of an L2 U2U remote UE can derive the PDCP and SDAP configuration for the end-to-end SL-DRB and provide a portion of the reception-related configuration to the peer L2 U2U remote UE using the end-to-end RRCReconfigurationSidelink message. The end-to-end bearer ID used for SL-SRB and SL-DRB can be used as input for L2 U2U relay encryption and decryption in PDCP.

[0145] 9a. RRC reconfiguration related to inter-terminal communication can be performed. For example, the serving gNB or L2 U2U remote UE can deduce the first-hop configuration for SL-DRB (e.g., PC5 relay RLC channel configuration) and use hop-by-hop RRCReconfigurationSidelink messages to provide the L2 U2U relay UE with the reception-related configuration at the first hop (i.e., the Rx performed by the relay UE).

[0146] 9b. RRC reconfiguration related to inter-terminal communication can be performed. For example, the serving gNB or L2 U2U relay UE of an L2 U2U relay UE derives a second-hop configuration for each SL-DRB (e.g., PC5 relay RLC channel configuration) and provides the peer L2 U2U remote UE with the configuration related to the reception of data packets at the second hop (i.e., the Rx of the peer remote UE) using a hop-by-hop RRCReconfigurationSidelink message.

[0147] For reference, Figure 5 In the example, the first hop can involve between a U2U remote UE and a U2U relay UE, and the second hop can involve between a U2U relay UE and a peer U2U remote UE.

[0148] 10. L2 U2U remote UEs and peer L2 U2U remote UEs can send and receive data through L2 U2U relay UEs.

[0149] Reference Figure 5 The examples provided can lead to the problems of the prior art in the following examples.

[0150] Reference Figure 5For example, a U2U remote UE or U2U relay UE in the RRC_CONNECTED state can be allocated / configured from the serving base station for the configuration information of the PC5 relay RLC channel between a U2U remote UE and a U2U relay UE, or between peer-to-peer U2U remote UEs and U2U relay UEs. The base station can be split into gNB-CU and gNB-DU. In this case, the configuration information for the PC5 relay RLC channel needs to be allocated / configured by the gNB-DU. Therefore, an F1AP signaling is required whereby the gNB-CU requests the gNB-DU to allocate / configure the PC5 relay RLC channel configuration for U2U relay operations.

[0151] Furthermore, in order for the gNB-DU to allocate / configure PC5 relay RLC channel configuration for U2U relay operations, the gNB-CU needs to allocate / configure the PC5 relay RLC channel QoS and deliver the PC5 relay RLC channel QoS to the gNB-DU. In conventional U2N relay operations, the base station splits the QoS for each hop (i.e., Uu / PC5 relay RLC channel) based on the QoS information for DRB received from the 5GC. However, unlike conventional U2N relay operations, in U2U relay operations, after the U2U relay UE performs QoS splitting for each hop (i.e., first / second PC5 relay RLC channel) for SL-DRB, the U2U remote UE or U2U relay UE notifies each base station of the split QoS information for the first hop (i.e., between the U2U remote UE and the U2U relay UE) or the second hop (i.e., between the peer U2U remote UE and the U2U relay UE). Therefore, based on such operations, it is necessary to allocate / configure the PC5 trunk RLC channel configuration in which gNB-CU and / or gNB-DU are configured.

[0152] In addition, it is necessary for the gNB-CU to notify the gNB-DU of the operation of the target connected to each PC5 unicast link.

[0153] Therefore, this specification discloses a solution to address the problems of the prior art as described above. For example, for signaling and data transmission between U2U remote UEs via U2U relay UEs, the base station can allocate / configure PC5 relay RLC channel information.

[0154] According to the disclosure in this specification, for signaling and data transmission between a U2U remote UE and a peer U2U remote UE via a U2U relay UE, the base station can allocate / configure PC5 relay RLC channel information.

[0155] For example, a U2U remote UE or U2U relay UE in the RRC_CONNECTED state can notify the serving base station of QoS information for end-to-end (E2E) SL-DRB and split QoS information for each hop. Then, the gNB-CU can allocate and / or configure U2U PC5 relay RLC channel QoS information for PC5 relay RLC channel configuration. The gNB-CU can notify the gNB-DU of this U2U PC5 relay RLC channel QoS information. The gNB-DU can allocate / configure PC5 relay RLC channel configuration based on this U2U PC5 relay RLC channel QoS information. Furthermore, the gNB-CU can send the L2 ID of the peer U2U remote UE or the L2 ID of the U2U relay UE to the gNB-DU to notify the gNB-DU of the target being connected to each PC5 unicast link.

[0156] In this specification, user equipment (UE) and terminals are described interchangeably.

[0157] Furthermore, in this manual, UE-UE relay, ProSe UE-UE relay, relay, relay UE, UE-UE relay, 5G ProSe UE-UE relay, 5G ProSe UE-UE relay, U2U relay, U2U relay UE, etc. can be used interchangeably.

[0158] Furthermore, in this manual, remote UE, 5G remote UE, 5G ProSe remote UE, U2U remote UE, etc. can be used interchangeably.

[0159] Furthermore, in this specification, a UE that is not a UE-to-UE relay may be referred to as a remote UE, or may be referred to as a UE.

[0160] In this specification, a relay located on the path between a remote UE and a peer remote UE in order to provide connection services to a remote UE is referred to as a U2U relay.

[0161] In the following text, this specification will primarily describe the proposed contents. Descriptions relating to prior art will be omitted. For ProSe-related operations and procedures, as well as relay communication, references will be made to TS 23.304 V18.0.0, TS24.554 V18.0.0, TS 33.536 V17.0.0, TS 33.503 V18.0.0, TS 38.300 V17.0.0, TS38.401 V17.0.0, TS 38.331 V17.0.0, TS 38.351 V17.0.0, etc.

[0162] The scheme for supporting UE-to-UE relay as disclosed in this specification may consist of a combination of one or more of the following operations / configurations / steps.

[0163] For some messages (e.g., sidelink messages) related to inter-terminal communication between the remote UE and the relay UE described in the various examples of the disclosure in this specification, new messages can be defined and used. Furthermore, for some RRC messages between the NG-RAN and the terminal described below, new RRC messages can be defined and used.

[0164] In the following process, some steps can be performed simultaneously / in parallel, or in reverse order.

[0165] The names of the instructions, parameter information, and information described below are examples, and the scope of the disclosure in this specification is not limited to the names described below. For example, the names of the instructions, parameter information, and information described in this disclosure may be interpreted as being replaced with other names for the proposed process / purpose / scheme.

[0166] 1. A first example of the disclosure in this specification

[0167] The first example of the disclosure in this specification includes an example of a scheme for supporting relay communication between terminals.

[0168] In the first example of the disclosure in this specification, it is assumed that the serving base station of the U2U remote UE (e.g., gNB#1) is different from the serving base station of the U2U relay UE (e.g., gNB#2). However, this is merely an example, and the scope of the disclosure in this specification is not limited to this situation. For example, the content described in the first example of the disclosure in this specification can also be applied when the serving base station of the U2U remote UE is the same as the serving base station of the U2U relay UE.

[0169] The following figures were created to illustrate specific examples of this disclosure. Specific names of devices or signals / messages / fields described in the figures are presented by way of example, and therefore the technical features of this disclosure are not limited to the specific names used in the following figures.

[0170] Figure 6 This is an example of a process for supporting U2U relay operation according to an embodiment of this disclosure.

[0171] Reference Figure 6 The example, based on the F1 interface, illustrates a procedure that supports U2U relay operations.

[0172] Reference Figure 6The examples illustrate a U2U remote UE, a U2U relay UE, and a peer U2U remote UE. A U2U relay UE can relay communication between a U2U remote UE and a peer U2U remote UE.

[0173] gNB#1 can be a base station serving a U2U remote UE. gNB#2 can be a base station serving a U2U relay UE. Although Figure 6 Examples include cases where gNB#1 and gNB#2 are different, but this is just an example, and the two base stations can be the same base station.

[0174] gNB#1 can include gNB-DU#1 and gNB-CU#1.

[0175] Step 1: Can be executed Figure 5 Steps 1 to 7 in the example.

[0176] For example, in order to perform inter-terminal communication (e.g., sidelink communication) between a U2U relay UE and a peer U2U remote UE, the U2U remote UE can perform... Figure 5 Steps 1 to 7 in the example. For Figure 5 Steps 1 through 7 in the example can also be found in steps 1 through 7 of Clause 16.12.7 of TS38.300 V18.0.0.

[0177] Step 2: The U2U remote UE can send information to gNB#1. For example, the U2U remote UE can send a message to gNB#1 requesting configuration related to communication between the U2U remote UE and its peer U2U remote UE. For reference, the SidelinkInformationNR message is merely an example in the following text, and the disclosure of this specification is not limited to this name for the scope of the message sent in Step 2.

[0178] For example, when the U2U remote UE is in the RRC_CONNECTED state, such as Figure 5 In steps 8 to 9a (for example, see also steps 8 to 9a of Clause 16.12.7 of TS 38.300 V18.0.0), the U2U remote UE can send a message to gNB#1. For example, the U2U remote UE can send a SidelinkInformationNR message to gNB#1 to allow the SDAP configuration, the PDCP configuration for the end-to-end (E2E) SL-DRB for the peer U2U remote UE, and the first-hop configuration of the E2E SL-DRB (e.g., PC5 trunk RLC channel configuration, etc.) to be assigned / configured from gNB#1.

[0179] For example, a U2U remote UE can include QoS information related to the E2E SL-DRB and split QoS value information (e.g., packet delay budget) configured / assigned by the U2U relay UE for the first hop (i.e., between the U2U remote UE and the U2U relay UE) in the SidelinkInformationNR message. For existing input parameters included by the U2U remote UE in the SidelinkInformationNR message, refer to TS 38.331 V18.0.0.

[0180] Step 3: gNB-CU#1 can send a UE CONTEXT MODIFICATION REQUEST message to gNB-DU#1.

[0181] For example, based on the QoS information received in step 2, gNB-CU#1 can allocate / configure U2U PC5 Relay RLC channel QoS information for the first-hop configuration of the E2E SL-DRB (e.g., PC5 Relay RLC channel configuration, etc.). gNB-CU#1 can send a UE CONTEXT MODIFICATIONREQUEST message including this U2U PC5 Relay RLC channel QoS information to gNB-DU#1. Therefore, gNB-CU#1 can request gNB-DU#1 to allocate / configure the first-hop configuration of the E2E SL-DRB (e.g., PC5 Relay RLC channel configuration, etc.).

[0182] Furthermore, to notify gNB-DU#1 which U2U relay UE the first-hop PC5 unicast link of the E2E SL-DRB is connected to, gNB-CU#1 can send the ID associated with the U2U relay UE (e.g., L2 ID). For example, gNB-CU#1 can send a UE CONTEXT MODIFICATION REQUEST message to gNB-DU#1 that includes the ID associated with the U2U relay UE (e.g., L2 ID) and U2U PC5 relay RLC channel QoS information. For example, to notify gNB-DU#1 which peer U2U remote UE the E2E SL-DRB's E2EPC5 unicast link is connected to, gNB-CU#1 can send the L2 ID of the peer U2U remote UE in the UE CONTEXT MODIFICATION REQUEST message. For example, by sending the ID associated with the U2U relay UE (e.g., L2 ID), gNB-CU#1 can notify which peer (e.g., relay UE) the remote UE's first link (or first hop) is connected to. For example, by sending the L2 ID of the peer U2U remote UE, gNB-CU#1 can notify which peer (e.g., peer U2U remote UE) the entire link, including the first hop and the second hop, is connected to.

[0183] For reference, when gNB-CU#1 receives information from the U2U remote UE in step 2, gNB-CU#1 may send a UE context modification request message to gNB-DU#1, including the ID associated with the U2U relay UE (e.g., L2 ID) and / or the ID associated with the peer U2U remote UE (e.g., L2 ID). In this case, the ID associated with the U2U relay UE (e.g., L2 ID) may be referred to as the peer UE ID.

[0184] For reference, when gNB-CU#1 receives information from the U2U relay UE in step 2 (or step 7 described later), gNB-CU#1 may send a UE context modification request message to gNB-DU#1 including the ID (e.g., L2 ID) associated with the peer U2U remote UE and / or the L2 ID of the U2U remote UE. In this case, the ID (e.g., L2 ID) associated with the peer U2U remote UE may be referred to as the peer UE ID.

[0185] The gNB-DU#1 can implicitly identify, based on the L2 ID of the U2U relay UE, the L2 ID of the peer U2U remote UE, or the QoS information of the U2U PC5 relay RLC channel, that the currently allocated / configured PC5 relay RLC channel is for U2U relay operation, rather than U2N relay operation. Alternatively, the gNB-CU can send a UE CONTEXTMODIFICATION REQUEST message, including a separate indication, to the gNB-DU to explicitly notify that the currently allocated / configured PC5 relay RLC channel is for U2U relay operation, rather than U2N relay operation.

[0186] Step 4: gNB-DU#1 can send a UE CONTEXT MODIFICATION RESPONSE message to gNB-CU#1. This UE CONTEXT MODIFICATION RESPONSE message may include an RRC container (e.g., sl-RLC-ChannelToAddModList).

[0187] For example, based on the information received in step 3, gNB-DU#1 can allocate / configure the first-hop configuration of the E2E SL-DRB (e.g., PC5 relay RLC channel configuration, etc.). gNB-DU#1 can deliver the first-hop configuration of the E2E SL-DRB to gNB-CU#1 via an RRC container (e.g., sl-RLC-ChannelToAddModList).

[0188] Step 5: gNB#1 and U2U remote UEs can perform the RRC reconfiguration process.

[0189] For example, gNB-CU#1 can directly assign / configure SDAP and PDCP configurations for end-to-end (E2E) SL-DRB with peer U2U remote UEs. For example, gNB-CU#1 can deliver the information received in step 4 and the information assigned / configured by gNB-CU#1 in step 5 to the U2U remote UE through the RRC reconfiguration process.

[0190] Step 6: U2U remote UE can perform RRC reconfiguration related to inter-terminal communication.

[0191] For example, such as Figure 5In step 9a (for example, see also step 9a of clause 16.12.7 of TS 38.300 V18.0.0), the U2U remote UE may perform the following operations. For example, based on the information received in step 5, after configuring the PC5 trunk RLC channel for the first hop, the U2U remote UE may perform an RRC reconfiguration sidelink procedure to request the U2U trunk UE to also configure the same PC5 trunk RLC channel for the first hop.

[0192] Step 7: When the U2U relay UE is in the RRC_CONNECTED state, the U2U relay UE can perform steps 2 to 5 with gNB#2. For example, as Figure 5 In step 9b (e.g., refer to step 9b of clause 16.12.7 in TS 38.300 V18.0.0), in order to be assigned / configured the second-hop configuration of the E2E SL-DRB from gNB#2 (i.e., PC5 trunk RLC channel configuration, etc.), the U2U trunk UE can perform with gNB#2 Figure 6 The process from step 2 to step 5.

[0193] For example, a U2U relay UE can send a step 2 message (e.g., a SidelinkInformationNR message) to gNB#2. The U2U relay UE can include in this message split QoS value information (e.g., SL-QoS-Profile) configured / assigned by the U2U relay UE for the second hop (e.g., between a peer U2U remote UE and a U2U relay UE). Based on this, gNB-CU#2 configures / assigns U2U PC5 relay RLC channel QoS information for the second-hop configuration of the E2E SL-DRB (e.g., PC5 relay RLC channel configuration, etc.), and gNB-CU#2 can deliver a UECONTEXT MODIFICATION REQUEST message including this U2U PC5 relay RLC channel QoS information to gNB-DU#2. Through this, gNB-CU#2 can request the allocation / configuration of the second-hop configuration (e.g., PC5 relay RLC channel configuration, etc.) for the E2E SL-DRB from gNB-DU#2. Furthermore, to notify gNB-DU#2 which peer U2U remote UE the second-hop PC5 unicast link of the E2E SL-DRB is connected to, gNB-CU#2 can send the L2 ID of the peer U2U remote UE to gNB-DU#2 along with the UE CONTEXT MODIFICATION REQUEST message. For example, gNB-CU#2 can send a UE CONTEXT MODIFICATION REQUEST message to gNB-DU#2 that includes the ID (e.g., L2 ID) associated with the peer U2U remote UE and QoS information for the U2U PC5 relay RLC channel. gNB-CU#2 can also send the L2 ID of the U2U remote UE to gNB-DU#2 along with the message to notify gNB-DU#2 which U2U remote UE the E2E PC5 unicast link of the E2E SL-DRB is connected to.

[0194] Step 8: U2U relay UEs can perform RRC reconfiguration related to inter-terminal communication with peer U2U remote UEs.

[0195] For example, such as Figure 5 In step 9b (e.g., referring to step 9b of clause 16.12.7 in TS 38.300 V18.0.0), the U2U relay UE can configure the PC5 relay RLC channel for the second hop based on information received from gNB-CU#2. The U2U relay UE can perform an RRC reconfiguration sidelink procedure to request that the peer U2U remote UE also configure the same PC5 relay RLC channel for the second hop.

[0196] Step 9: U2U remote UEs and peer U2U remote UEs can exchange data through U2U relay UEs.

[0197] 2. A second example of the disclosure in this specification.

[0198] The second example of the disclosure in this specification illustrates an example of applying the first example of the disclosure in this specification.

[0199] A feature is being discussed that supports 5G ProSe UE-to-UE (U2U) relay operation to provide connectivity between U2U remote UEs. In this feature, a U2U remote UE can communicate with a peer U2U remote UE that is not reachable within sidelink coverage.

[0200] The serving gNB can provide per-hop configuration for SL-DRB (e.g., PC5 trunk RLC channel configuration) to UEs in RRC_CONNECTED (e.g., L2 U2U remote UEs or L2 U2U trunk UEs). The PC5 RLC channel ID IE can also be used for U2U trunk operations. This IE is assigned by the gNB-CU and can be sent to the gNB-DU along with QoS information.

[0201] However, in U2U trunk operations, since the QoS parameters for the PC5 trunk RLC channel are derived from the E2E QoS used for SL-DRB, the gNB-DU can provide the PC5 QoS parameter IE instead of the QoS flow-level QoS parameter IE. That is, in U2U trunk operations, the U2U remote UE and the peer U2U remote UE can negotiate the end-to-end QoS for service transmission between the U2U remote UEs. The gNB can determine the QoS parameters for the PC5 RLC channel based on the split QoS values ​​of the U2U remote UE or the U2U trunk UE.

[0202] Therefore, new features need to be introduced to support U2U relay operations.

[0203] For example, definitions for L2 U2U remote UEs and L2 U2U relay UEs can be added. U2U abbreviations can be added. Descriptions of U2U relay operations can be added. For UE CONTEXT MODIFICATION REQUEST, UE CONTEXTMODIFICATION RESPONSE, UE CONTEXT MODIFICATION REQUIRED, and UE CONTEXTMODIFICATION CONFIRM messages, peer-to-peer U2U UE ID IEs can be added. U2U PC5 RLC channel QoS IEs can be added to PC5 RLC channel QoS information IEs. Uu RLC channels can be changed to "Uu relay RLC channels".

[0204] The following describes an example of applying the disclosure of this specification to the UE context establishment request procedure.

[0205] Successful operations of the UE context establishment request process may include: the gNB-CU sending a UE CONTEXTSETUP REQUEST message to the gNB-DU, and the gNB-DU sending a UE CONTEXT SETUP RESPONSE message to the gNB-CU.

[0206] The gNB-CU initiates this procedure by sending a UE CONTEXT SETUP REQUEST message to the gNB-DU. When the gNB-DU successfully establishes the UE context, it replies to the gNB-CU with a UE CONTEXT SETUP RESPONSE. If the logical F1 connection associated with the UE does not exist, it is established as part of this procedure. Except for UEs configured with RACH-based SDT and BWP-specific ServingCellMO, the gNB-CU can send the UE to the RRC_CONNECTED state by performing RRC reconfiguration or RRC connection recovery as described in TS 38.331 V18.0.0.

[0207] If an index for the RAT / Frequency Selection Priority IE is available at the gNB-CU, the RAT / Frequency Selection Priority IE used for that index should be included in the UE CONTEXT SETUP REQUEST. The gNB-DU can then use it for RRM purposes.

[0208] In the UE CONTEXT SETUP RESPONSE message, the gNB-DU shall report the results of all requested DRB, SRB, BH RLC channels, Uu trunk RLC channels, PC5 trunk RLC channels, and SL DRB to the gNB-CU in the following manner: The gNB-DU can report the results of all requested DRB, SRB, BH RLC channels, Uu trunk RLC channels, PC5 trunk RLC channels, and SL DRB to the gNB-CU in the following manner: - The list of successfully established Uu relay RLC channels should be included in the Uu RLC channel establishment list (IE); - The list of Uu relay RLC channels that failed to be established should be included in the Uu RLC channel establishment failure list (IE); - The list of successfully established PC5 relay RLC channels should be included in the PC5 RLC channel establishment list (IE). - The list of PC5 relay RLC channels that failed to be established should be included in the PC5 RLC channel establishment failure list (IE). If the replication indication IE in the SL DRB pending establishment list is included in the UE context establishment request message, then gNB-DU generates two PC5 RLC configurations for the indicated SL DRB, if supported.

[0209] When gNB-DU reports a configuration failure for DRB, SRB, SL DRB, BH RLC channel, Uu trunk RLC channel, and PC5 trunk RLC channel, the reason value should be accurate enough for gNB-CU to know the reason for the configuration failure.

[0210] The following describes examples of how the disclosure of this specification is applied to a UE context modification procedure initiated by the gNB-CU.

[0211] The purpose of the UE context modification procedure is to modify, modify, and release established UE contexts, such as the configuration, modification, and release of radio resources or sidelink resources. Additionally, this procedure is used to command the gNB-DU to cease data transmission to the UE for mobility purposes. This procedure utilizes UE-related signaling.

[0212] Successful operations may include the gNB-CU sending a UE context modification request message to the gNB-DU, and the gNB-DU sending a UE context modification response message to the gNB-CU.

[0213] The UE context modification request message is initiated by gNB-CU.

[0214] If the Uu RLC channel pending establishment list IE is included in the UE context modification request message, then gNB-DU, if supported, will operate as specified in TS 38.401 V17.0.0.

[0215] If the Uu RLC channel to be modified list IE is included in the UE context modification request message, then gNB-DU, if supported, will operate as specified in TS 38.401 V17.0.0.

[0216] If the Uu RLC channel release list IE is included in the UE context modification request message, then gNB-DU releases the Uu relay RLC channel in that list if supported.

[0217] If the PC5 RLC channel pending establishment list IE is included in the UE context modification request message, the gNB-DU, if supported, operates as specified in TS 38.401 V17.0.0. The gNB-DU generates PC5 trunk RLC channel configurations for L2 U2N remote UEs, U2N trunk UEs, U2U remote UEs, or U2U trunk UEs. If the F1AP-ID is associated with a U2N trunk UE, the PC5 RLC channel pending establishment item IE should include the remote UE local ID, and correspondingly, the PC5 RLC channel establishment item IE and PC5 RLC channel establishment failure item IE in the UE context modification response message include this remote UE local ID. If the F1AP-ID is associated with a U2U remote UE or U2U trunk UE, the PC5 RLC channel pending establishment item IE should include the peer U2U UE ID IE, and correspondingly, the PC5 RLC channel establishment item IE and PC5 RLC channel establishment failure item IE in the UE context modification response message should include this peer U2U UE ID IE.

[0218] If the PC5 RLC channel to be modified list IE is included in the UE context modification request message, the gNB-DU, if supported, operates as specified in TS 38.401 V17.0.0. The gNB-DU generates PC5 trunk RLC channel configurations for L2 U2N remote UEs, U2N trunk UEs, U2U remote UEs, or U2U trunk UEs. If the F1AP-ID is associated with a U2N trunk UE, the PC5 RLC channel to be modified item IE includes the remote UE local ID IE, and correspondingly, the PC5 RLC channel modification item IE and PC5 RLC channel modification failure item IE in the UE context modification response message include this remote UE local ID IE. If the F1AP-ID is associated with a U2U remote UE or U2U trunk UE, the PC5 RLC channel to be modified item IE includes the peer U2U UE ID IE, and correspondingly, the PC5 RLC channel modification item IE and PC5 RLC channel modification failure item IE in the UE context modification response message include this peer U2U UE ID IE.

[0219] If the PC5 RLC channel release list IE is included in the UE context modification request message, the gNB-DU releases the PC5 trunk RLC channels in that list, if supported. If the F1AP-ID is associated with a U2N trunk UE, the PC5 RLC channel release item IE includes the remote UE local ID IE. If the F1AP-ID is associated with a U2U remote UE or a U2U trunk UE, the PC5 RLC channel release item IE includes the peer U2U UE ID IE.

[0220] The following describes examples of how the disclosure of this specification is applied to the procedures required for UE context modification initiated by gNB-DU.

[0221] The purpose of the procedures required for UE context modification is to modify an established UE context, such as modifying and releasing radio bearer resources, radio bearer resources used for inter-terminal communication (e.g., sidelinks), or conditional handover, conditional PSCell addition, conditional PSCell change, or candidate cells in subsequent CPACs. This procedure uses UE-associated signaling.

[0222] A successful operation includes the gNB-DU sending the UE context modification required message to the gNB-CU, and the gNB-CU sending the UE context modification confirmation message to the gNB-DU.

[0223] The message required for F1AP UE context modification is initiated by gNB-DU.

[0224] The gNB-CU reports the successful update of the UE context in the UE context modification confirmation message.

[0225] If the PC5 RLC channel required modification list IE or the PC5 RLC channel required release list IE is included in the UE context modification required message, and the F1AP-ID is associated with a U2N relay UE, then the PC5 RLC channel required modification list IE or the PC5 RLC channel required release list should include the remote UE local ID, and accordingly, the PC5 RLC channel modification item IE in the UE context modification confirmation message includes the remote UE local ID IE. If the F1AP-ID is associated with a U2U remote UE or a U2U relay UE, then the PC5 RLC channel required modification list IE or the PC5 RLC channel required release list includes the peer U2U UE ID IE, and accordingly, the PC5 RLC channel modification item IE in the UE context modification confirmation message may include the peer U2U UE ID IE.

[0226] In the following text, examples of information elements (IEs) included in a UE context modification request message are described with reference to Table 3.

[0227] The UE context modification request message is sent by the gNB-CU to inform the gNB-DU of the UE context information change. The UE context modification request message is sent from the gNB-CU to the gNB-DU.

[0228] [Table 3]

[0229] Table 3 provides examples of Internet Explorers (IEs) relevant to the disclosures in this specification. For IEs not shown in Table 3, please refer to 3GPP TS38.473 V18.0.0 S9.2.2.7.

[0230] For example, the gNB-CU can send a UE context modification request message to the gNB-DU. The UE context modification request message may include the message type, the gNB-CU UE F1AP ID, the gNB-DU UE F1AP ID, and a PC5 channel pending list. For example, the PC5 channel pending list may include PC5 RLC channel pending items (IEs). For example, a PC5 RLC channel pending item (IE) may include the PC5 RLC channel ID, the remote UE local ID, PC5 RLC channel QoS information, and the peer U2U UE ID. The PC5 RLC channel QoS information may include the U2U PC5 RLC channel QoS.

[0231] For reference, maxnoofPC5RLCChannels is the maximum number of PC5 trunk RLC channels allowed per remote UE or trunk UE for L2 U2N trunking or L2 U2U trunking, and the maximum value is 512.

[0232] The following describes examples of information elements (IEs) included in the UE context modification response message, with reference to Table 4.

[0233] A UE context modification response message is sent by the gNB-DU to acknowledge the modification of the UE context. This message is sent from the gNB-DU to the gNB-CU.

[0234] [Table 4]

[0235] For example, based on the examples in Table 4, the gNB-DU can send a UE context modification response message to the gNB-CU. The UE context modification response message may include the message type, gNB-CU UE F1AP ID, gNB-DU UE F1AP ID, DU-CU RRC information, and a PC5 RLC channel establishment list. For example, the PC5 RLC channel establishment list may include the PC5 RLC channel ID, the remote UE local ID, and the peer U2U UE ID.

[0236] The following describes examples of information elements (IEs) included in the UE context modification request message, with reference to Table 5. The UE context modification request message is sent by the gNB-DU to request modification of the UE context. The message can be sent from the gNB-DU to the gNB-CU.

[0237] [Table 5]

[0238] For example, based on the examples in Table 5, the gNB-DU can send a CONTEXTMODIFICATION REQUIRED message to the gNB-CU. The CONTEXTMODIFICATION REQUIRED message may include the message type, gNB-CU UEF1AP ID, gNB-DU UE F1AP ID, DU-CU RRC information, and a list of required modifications for the PC5 RLC channel. The list of required modifications for the PC5 RLC channel may include the PC5 RLC channel ID, the remote UE local ID, and the peer U2U UE ID.

[0239] The following sections describe examples of information elements (IEs) included in the UE context modification confirmation message, with reference to Table 6. The UE context modification confirmation message is sent by the gNB-CU to notify the gNB-DU of a successful modification. This message can be sent from the gNB-CU to the gNB-DU.

[0240] [Table 6]

[0241] For example, based on the examples in Table 6, the gNB-CU can send a UE context modification confirmation message (UECONTEXT MODIFICATION CONFIRM) to the gNB-DU. The UE context modification confirmation message may include the message type, the gNB-CU UEF1AP ID, the gNB-DU UE F1AP ID, and a PC5 RLC channel modification list. The PC5 RLC channel modification list may include the PC5 RLC channel ID, the remote UE local ID, and the peer U2U UE ID.

[0242] In the following text, examples of PC5 QoS parameters are described with reference to the examples in Table 7.

[0243] [Table 7]

[0244] The IE definitions related to PC5 QoS parameters, as shown in the examples in Table 7, define the QoS to be applied to SLDRB or PC5 RLC channels used for L2 U2U trunking.

[0245] For reference, maxnoofPC5QoSFlows represents the maximum number of PC5 QoS flows allowed for a UE for inter-terminal communication (e.g., NR sidelink communication), and the maximum value is 2048.

[0246] The dynamic PQI descriptors in the examples in Table 7 can be described as in the examples in Table 8.

[0247] [Table 8]

[0248] The dynamic PQI descriptor IE indicates the QoS characteristics of a non-standardized or non-pre-configured PQI used for inter-terminal communication.

[0249] For reference, if the PC5 QoS stream bit rate IE exists in the PC5 QoS parameter IE, then the ifGBRflow IE should also exist.

[0250] The PC5 RLC Channel ID IE uniquely identifies the PC5 trunk RLC channel used for L2 U2N remote UEs, L2 U2N trunk UEs, L2 U2U remote UEs, and L2 U2U trunk UEs. The existence of the PC5 RLC Channel ID IE is M (mandatory), and the IE type can be INTEGER (1..512,...).

[0251] In the following text, refer to Figure 7 Examples are provided to describe the process of implementing the present disclosure.

[0252] The following figures were created to illustrate specific examples of this disclosure. Specific names of devices or signals / messages / fields described in the figures are presented by way of example, and therefore the technical features of this disclosure are not limited to the specific names used in the following figures.

[0253] Figure 7 An example of a process according to an embodiment of this disclosure is shown.

[0254] For reference only. Figure 7 The process shown is merely an example, and the scope of this disclosure is not limited thereto. Figure 7 Example limitations.

[0255] For example, regarding Figure 7 Example, Figures 1 to 6 The operations described in the examples can also be applied. For example, even if the operations, content, etc., are not directly in... Figure 7 The operations and content described in the examples described in this disclosure can also be applied.

[0256] DU and CU can be included in one NG-RAN. DU can be referred to as gNB-DU, and CU can be referred to as gNB-CU.

[0257] Before or after performing step (S701), the CU can receive messages related to inter-terminal communication from the U2U remote UE or the U2U relay UE. For example, messages related to inter-terminal communication may be sidelink information messages. For example, messages related to inter-terminal communication may include QoS profiles.

[0258] For example, the CU can determine QoS information related to the PC5 RLC channel on the first or second hop based on the QoS profile.

[0259] In step S701, the CU can send a request message to the DU.

[0260] For example, the CU can send a request message related to the user equipment (UE) context to the distributed unit (DU) of the base station.

[0261] For example, the request message may include QoS information related to the PC5 RLC channel and the peer-to-peer (U2U) UEID. For example, if the request message is related to a U2U remote UE or a U2U relay UE, the peer-to-peer U2U UE ID may be included in the request message.

[0262] For example, when a CU receives messages related to inter-terminal communication from a U2U remote UE, the peer UE ID can be associated with the ID of the U2U relay UE.

[0263] For example, when a CU receives a message related to inter-terminal communication from a U2U relay UE, the peer UE ID can be associated with the ID of the peer remote UE.

[0264] For example, a request message related to the UE context could be a UE context establishment request message or a UE context modification request message.

[0265] In step S702, DU can send a response message to CU.

[0266] For example, the CU can receive response messages related to the UE context from the DU.

[0267] As described in the various examples of this disclosure, U2U relay can be effectively supported based on this disclosure.

[0268] For example, it can support F1 UE context management functions.

[0269] As an example, the following description applies to L2 U2U trunks: The F1 UE context management function is used for PC5 trunk RLC channel management for L2 U2U remote UEs and L2 U2U trunk UEs, specifically the establishment, modification, and release of PC5 trunk RLC channel resources. The establishment of a PC5 trunk RLC channel is triggered by the gNB-CU. Based on the resource reservation information and QoS information provided to the gNB-DU, the gNB-DU accepts or rejects the establishment or modification request. For example, the gNB-CU can send a message to the gNB-DU requesting the establishment or modification of a PC5 trunk RLC channel. Then, based on the resource reservation information and QoS information provided to the gNB-DU, the gNB-DU can accept or reject the establishment or modification requested by the gNB-CU. Modification of the PC5 trunk RLC channel can be triggered by either the gNB-CU or the gNB-DU.

[0270] - The gNB-CU can determine the QoS of the PC5 Relay RLC channel in the first or second hop of the end-to-end inter-terminal communication (e.g., side link) radio bearer based on the QoS profile received from the L2 U2U remote UE or L2 U2U relay UE, and provide QoS information to the gNB-DU.

[0271] For example, the gNB-CU can send a UE context establishment request message to the gNB-DU. The UE context establishment request message may include a list of PC5 RLC channels to be established. This list may include U2U RLC channel QoS, peer UE ID, etc.

[0272] For example, the gNB-CU can send a UE context modification request message to the gNB-DU. The UE context modification request message may include a list of PC5 RLC channels to be established. This list may include U2U RLC channel QoS, peer UE ID, etc.

[0273] When the gNB-CU UE F1AP ID and / or gNB-DU UE F1AP ID are associated with an L2 U2U remote UE or an L2 U2U trunk UE, the peer UE ID can be included in the UE context establishment request message and / or UE context modification request message.

[0274] According to the implementation method disclosed in this specification, gNB-CU can allocate / configure PC5 relay RLC channel QoS information between U2U remote UE and U2U relay UE or between peer U2U remote UE and U2U relay UE, and notify gNB-DU of the PC5 relay RLC channel QoS information.

[0275] According to the implementation of the disclosure in this specification, the gNB-CU can notify the gNB-DU of information about the target to which the PC5 trunk RLC channel between a U2U remote UE and a U2U relay UE or between a peer U2U remote UE and a U2U relay UE is to be connected (e.g., the L2 ID for the U2U relay UE or the peer U2U remote UE).

[0276] This instruction manual can have various effects.

[0277] For example, based on the disclosure in this specification, U2U relay scenarios can be effectively supported. For instance, in a U2U relay scenario, the base station can be divided into gNB-CU and gNB-DU. In this case, gNB-DU can allocate / configure a PC5 relay RLC channel and provide that PC5 relay RLC channel according to the request of a U2U remote UE or a U2U relay UE. Therefore, signaling and / or data can be effectively exchanged between U2U remote UEs. Based on the destination L2 ID provided by gNB-CU, it is possible to prevent two PC5 relay RLC channels with the same PC5 RLC channel ID from being configured to different destinations (e.g., a U2U relay UE or a peer-to-peer U2U remote UE).

[0278] The effects that can be obtained from the specific examples of this disclosure are not limited to those listed above. For example, a person skilled in the art can understand or infer various technical effects from this disclosure. Therefore, the specific effects of this disclosure are not limited to those expressly set forth herein, but may include various effects that can be understood or inferred from the technical features of this disclosure.

[0279] For reference, the operation of the terminal (e.g., UE, remote UE, relay UE) described in this specification can be achieved through the above... Figures 1 to 4 This is achieved through a device. For example, the terminal (e.g., UE, remote UE, relay UE) can be... Figure 2 The first device 100 or the second device 200. For example, the operation of the terminal (e.g., UE, remote UE, relay UE) described herein can be processed by one or more processors 102 or 202. The operation of the terminal described herein can be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable code) executable by one or more processors 102 or 202. One or more processors 102 or 202 control one or more memories 104 or 204 and one or more transceivers 105 or 206, and can perform the operation of the terminal (e.g., UE, remote UE, relay UE) described herein by executing the instructions / programs stored in one or more memories 104 or 204.

[0280] Furthermore, instructions for performing operations of the terminal (e.g., UE, remote UE, relay UE) described in this disclosure may be stored in a non-volatile computer-readable storage medium on which such instructions are recorded. The storage medium may include one or more memories 104 or 204. The instructions recorded in the storage medium may be executed by one or more processors 102 or 202 to perform operations of the terminal (e.g., UE, remote UE, relay UE) described in this disclosure.

[0281] For reference, the operation of network nodes (e.g., AMF, SMF, UPF, PCF, NEF, UDM, DN, etc.) or base stations (e.g., NG-RAN, gNB, gNB-DU, gNB-CU, DU, CU, CU-UP, CU-CP, etc.) described herein can be described as follows. Figures 1 to 3 This is achieved through devices. For example, a network node or base station could be... Figure 2 First device 100 or Figure 2 The second device 200. For example, the operation of the network node or base station described herein can be processed by one or more processors 102 or 202. The operation of the terminal described herein can be stored in one or more memories 104 or 204 in the form of instructions / programs (e.g., instructions, executable code) executable by one or more processors 102 or 202. One or more processors 102 or 202 can perform the operation of the network node or base station described herein by controlling one or more memories 104 or 204 and one or more transceivers 106 or 206 and executing the instructions / programs stored in one or more memories 104 or 204.

[0282] Additionally, instructions for performing the operations of the network node or base station described in this disclosure may be stored in a non-volatile (or non-transitory) computer-readable storage medium. The storage medium may include one or more memories 104 or 204. Furthermore, the instructions recorded in the storage medium are executed by one or more processors 102 or 202 to perform the operations of the network node or base station.

[0283] Preferred embodiments have been described above by way of example; however, the present disclosure of this specification is not limited to such specific embodiments, and therefore modifications, alterations or improvements may be made.

[0284] In the exemplary system described above, the method is described as a series of steps or blocks based on the flowchart, but is not limited to the order of the described steps. Some steps may occur in a different order or simultaneously with other steps as described above. Furthermore, those skilled in the art will understand that the steps shown in the flowchart are not exclusive and may include other steps, or one or more steps of the flowchart may be deleted without affecting the scope of the claims.

[0285] The claims described herein can be combined in various ways. For example, the technical features of the method claims of this specification can be combined and implemented as a device, and the technical features of the device claims of this specification can be combined and implemented as a method. Furthermore, the technical features of the method claims and the device claims of this specification can be combined and implemented as a device, and the technical features of the method claims and the device claims of this specification can be combined and implemented as a method.

Claims

1. A method comprising the following steps: Send a request message related to the user equipment (UE) context to the distributed unit (DU) of the base station; as well as Receive a response message related to the UE context from the DU. The request message includes Quality of Service (QoS) information and peer UE ID related to the PC5 Radio Link Control (RLC) channel.

2. The method according to claim 1, further comprising the following steps: Receive messages related to inter-terminal communication from UE to UE U2U remote UE or U2U relay UE.

3. The method according to claim 2, in, The messages related to inter-terminal communication include QoS configuration files.

4. The method according to claim 3, further comprising the following step: Based on the QoS profile, determine the QoS information associated with the PC5 RLC channel on the first hop or the second hop.

5. The method according to any one of claims 1 to 4, in, Since the request message is related to a U2U remote UE or a U2U relay UE, the peer UE ID is included in the request message.

6. The method according to claim 5, in, Based on messages related to inter-terminal communication received from the U2U remote UE, the peer UE ID is associated with the ID of the U2U relay UE.

7. The method according to claim 5, in, Based on messages related to inter-terminal communication received from the U2U relay UE, the peer UE ID is associated with the ID of the peer remote UE.

8. The method according to any one of claims 1 to 6, in, The request message related to the UE context is either a UE context establishment request message or a UE context modification request message.

9. An apparatus, the apparatus comprising: One or more transceivers; One or more processors; as well as One or more memories, which store instructions and are operatively connected to one or more processors. The operations performed based on the instructions being executed by the one or more processors include: the method according to any one of claims 1 to 8.

10. A method comprising the following steps: Send a request message related to the user equipment (UE) context from the base station's control unit (CU); as well as Send a response message related to the UE context to the CU. The request message includes Quality of Service (QoS) information and peer UE ID related to the PC5 Radio Link Control (RLC) channel.

11. The method according to claim 10, in, The QoS information is determined based on a QoS profile included in messages related to inter-terminal communication received by the CU of the base station from the UE to the UE U2U remote UE or U2U relay UE.

12. The method according to claim 10 or 11, in, Since the request message is related to a U2U remote UE or a U2U relay UE, the peer UE ID is included in the request message.

13. The method according to any one of claims 10 to 12, in, The request message related to the UE context is either a UE context establishment request message or a UE context modification request message.

14. An apparatus, the apparatus comprising: One or more transceivers; One or more processors; as well as One or more memories, which store instructions and are operatively connected to one or more processors. The operations performed based on the instructions being executed by the one or more processors include: the method according to any one of claims 10 or 13.

Images