Method for performing relay communication in wireless communication system, and apparatus therefor

Abstract

Disclosed are a method performed by a first relay user equipment (UE), according to various embodiments, and an apparatus therefor. Disclosed are the method and the apparatus therefor, the method comprising the steps of: transmitting, to a base station, a first message including type information of a first relay UE related to a multi-hop-based UE to network (U2N) relay; and receiving, from the base station, a second message including configuration information for configuring a radio link control (RLC) channel for the multi-hop-based U2N relay.

Description

Method for performing relay communication in a wireless communication system and device therefor

[0001] A method for performing multi-hop based relay communication in a wireless communication system and a device therefor are provided.

[0002] Wireless communication systems are multiple access systems that support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0003] Sidelink (SL) refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). SL is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0004] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0005] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive machine type communication (MTC), and ultra-reliable and low latency communication (URLLC) can be called new radio access technology (RAT) or new radio (NR). NR can also support vehicle-to-everything (V2X) communication.

[0006] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0007] In relation to V2X communication, in RATs prior to NR, methods for providing safety services based on V2X messages such as Basic Safety Message (BSM), Cooperative Awareness Message (CAM), and Decentralized Environmental Notification Message (DENM) were mainly discussed. V2X messages may include location information, dynamic information, attribute information, etc. For example, a terminal may transmit a CAM of a periodic message type and / or a DENM of an event triggered message type to another terminal.

[0008] For example, a CAM may include basic vehicle information such as dynamic vehicle status information, such as direction and speed, static vehicle data, such as dimensions, external lighting conditions, and route history. For example, a terminal may broadcast a CAM, and the latency of the CAM may be less than 100 ms. For example, in the event of an emergency, such as a vehicle breakdown or accident, a terminal may generate a DENM and transmit it to other terminals. For example, all vehicles within the transmission range of the terminal may receive the CAM and / or DENM. In this case, the DENM may have a higher priority than the CAM.

[0009] Since then, various V2X scenarios have been proposed in NR in relation to V2X communications. For example, various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, and remote driving.

[0010] For example, based on vehicle platooning, vehicles can dynamically form groups and move together. For example, to perform platoon operations based on vehicle platooning, vehicles in the group can receive periodic data from the lead vehicle. For example, vehicles in the group can use this periodic data to narrow or widen the gap between vehicles.

[0011] For example, based on improved driving, vehicles can become semi-autonomous or fully automated. For example, each vehicle can adjust its trajectories or maneuvers based on data acquired from local sensors of nearby vehicles and / or nearby logical entities. Furthermore, for example, each vehicle can share driving intentions with nearby vehicles.

[0012] For example, based on extended sensors, raw data, processed data, or live video data acquired through local sensors can be exchanged between vehicles, logical entities, pedestrian terminals, and / or V2X application servers. Thus, for example, a vehicle can perceive its environment better than it can perceive using its own sensors.

[0013] For example, based on remote driving, a remote driver or V2X application can operate or control the remote vehicle for people who cannot drive or for remote vehicles located in hazardous environments. For example, in cases where the route is predictable, such as public transportation, cloud computing-based driving can be utilized to operate or control the remote vehicle. Additionally, access to a cloud-based back-end service platform, for example, can be considered for remote driving.

[0014] Meanwhile, a method to specify service requirements for various V2X scenarios, such as vehicle platooning, enhanced driving, expanded sensors, and remote driving, is being discussed in NR-based V2X communication.

[0015] The technical problem to be achieved by the present invention is to provide a method for a relay UE to perform multi-hop based U2N relay communication more accurately and efficiently.

[0016] The technical challenges are not limited to the technical challenges mentioned above, and other technical challenges not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0017] A method according to one aspect by a first relay UE (user equipment) comprises the steps of transmitting a first message including type information of a first relay UE related to a multi-hop based U2N (UE to Network) relay to a base station; and receiving a second message including configuration information for setting up an RLC (Radio Link Control) channel for the multi-hop based U2N relay from the base station, wherein the type information may include information on a first relay type or a second relay type based on whether the first relay UE is directly connected to the base station.

[0018] Alternatively, based on the first relay UE performing the multi-hop based U2N relay through a Uu connection directly connected to the base station and a connection with another UE, the type information is characterized in that it includes information on the first relay type.

[0019] Alternatively, based on the first relay UE performing the multi-hop based U2N relay without direct connection with the base station, the type information is characterized in that it includes information on the second relay type.

[0020] Alternatively, based on the type information including information on the first relay type, the second message is characterized in that it includes configuration information for setting an RLC channel for a Uu connection that is a direct connection with the base station and an RLC channel for a connection with another UE.

[0021] Alternatively, based on the type information including information about the second relay type, the second message is characterized in that it includes the configuration information for setting a first RLC channel for a first connection with a remote UE and a second RLC channel for a second connection with a second relay UE.

[0022] Alternatively, the first message is characterized in that it is an RRCSetupRequest message, an RRCReestablishmentRequest message, or an RRCResumeRequest message requesting an RRC (Radio Resource Control) connection related to the multi-hop based U2N relay.

[0023] Alternatively, the first message is characterized in that it is a SUI (SidelinkUEInformationNR) message.

[0024] Alternatively, the RLC channel is characterized in that it is established based on an e2e (end-to-end) bearer associated with the multi-hop based U2N relay.

[0025] According to another aspect, a non-transitory computer-readable storage medium having recorded thereon instructions for performing the method by the first relay UE described above may be provided.

[0026] According to another aspect, a first relay UE performing the method described above may be provided.

[0027] According to another aspect, a processing device may be provided for controlling a first relay UE performing the method described above.

[0028] A method by a base station according to another aspect comprises the steps of: receiving a first message including type information related to a multi-hop based U2N (UE to Network) relay from a first relay UE (user equipment); and transmitting a second message including configuration information for setting up an RLC (Radio Link Control) channel for the multi-hop based U2N relay based on the type information, wherein the type information may include information on a first relay type or a second relay type determined based on whether the first relay UE is directly connected to the base station.

[0029] According to another aspect, a base station performing the above-described method may be provided.

[0030] According to one embodiment, a relay UE in a wireless communication system can perform multi-hop based U2N relay communication more accurately and efficiently.

[0031] The effects that can be obtained in various embodiments are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the description below.

[0032] The drawings attached to this specification are intended to provide an understanding of the present invention, illustrate various embodiments of the present invention, and together with the description of the specification serve to explain the principles of the present invention.

[0033] Figure 1 is a diagram for comparing and explaining V2X communication based on RAT before NR and V2X communication based on NR.

[0034] Figure 2 shows the structure of the LTE system.

[0035] Figure 3 shows the structure of the NR system.

[0036] Figure 4 shows the structure of a radio frame of NR.

[0037] Figure 5 shows the slot structure of an NR frame.

[0038] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to one embodiment of the present disclosure.

[0039] FIG. 7 illustrates an electromagnetic spectrum according to one embodiment of the present disclosure.

[0040] Figure 8 shows a radio protocol architecture for SL communication.

[0041] Figure 9 shows a terminal performing V2X or SL communication.

[0042] Figure 10 shows resource units for V2X or SL communication.

[0043] FIG. 11 illustrates an example of a BWP according to one embodiment of the present disclosure.

[0044] FIG. 12 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure.

[0045] Figure 13 is a diagram for explaining the control plane procedure of L2 U2N relay (UE-to-Network Relay).

[0046] Figure 14 is a diagram for explaining a method for performing multi-hop based U2N relay communication.

[0047] FIG. 15 is a diagram illustrating a method for a first relay UE to receive configuration information for multi-hop based U2N relay communication.

[0048] FIG. 16 is a diagram illustrating a method for a base station to provide configuration information for a multi-hop based U2N relay.

[0049] Figure 17 illustrates a communication system applied to the present invention.

[0050] Figure 18 illustrates a wireless device applicable to the present invention.

[0051] Figure 19 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service.

[0052] Figure 20 illustrates a vehicle or autonomous vehicle to which the present invention is applied.

[0053] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and multi-carrier frequency division multiple access (MC-FDMA).

[0054] Sidelink refers to a communication method that establishes a direct link between user equipment (UE), allowing voice or data to be exchanged directly between terminals without going through a base station (BS). Sidelink is being considered as a solution to address the burden on base stations due to rapidly increasing data traffic.

[0055] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-based objects through wired / wireless communication. V2X can be divided into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through the PC5 interface and / or Uu interface.

[0056] Meanwhile, as more and more communication devices demand greater communication capacity, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Accordingly, communication systems that consider services or terminals sensitive to reliability and latency are being discussed. Next-generation wireless access technologies that consider improved mobile broadband communication, massive MTC, and URLLC (Ultra-Reliable and Low Latency Communication) can be called new radio access technology (RAT) or new radio (NR). NR can also support V2X (vehicle-to-everything) communication.

[0057] The following technologies can be used in various wireless communication systems, such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented with wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented with wireless technologies such as GSM (global system for mobile communications) / GPRS (general packet radio service) / EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented with wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e, providing backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is a part of E-UMTS (evolved UMTS) that uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0058] 5G NR, the successor to LTE-A, is a new clean-slate mobile communications system featuring high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, from low-frequency bands below 1 GHz, mid-frequency bands between 1 GHz and 10 GHz, and high-frequency (millimeter wave) bands above 24 GHz.

[0059] For clarity, the description will focus on LTE-A or 5G NR, but the technical ideas of the embodiment(s) are not limited thereto.

[0060] Figure 2 illustrates the architecture of an applicable LTE system. This may be referred to as an Evolved-UMTS Terrestrial Radio Access Network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.

[0061] Referring to FIG. 2, the E-UTRAN includes a base station (20; BS) that provides a control plane and a user plane to a terminal (10). The terminal (10) may be fixed or mobile, and may be referred to by other terms such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, etc. The base station (20) refers to a fixed station that communicates with the terminal (10), and may be referred to by other terms such as an evolved-NodeB (eNB), a base transceiver system (BTS), an access point, etc.

[0062] Base stations (20) can be connected to each other via the X2 interface. The base station (20) is connected to an EPC (Evolved Packet Core, 30) via the S1 interface, more specifically, to an MME (Mobility Management Entity) via the S1-MME, and to an S-GW (Serving Gateway) via the S1-U.

[0063] The EPC (30) consists of an MME, an S-GW, and a P-GW (Packet Data Network-Gateway). The MME holds information about terminal access and capabilities, and this information is primarily used for terminal mobility management. The S-GW is a gateway with the E-UTRAN as its endpoint, and the P-GW is a gateway with the PDN as its endpoint.

[0064] The layers of the radio interface protocol between the terminal and the network can be divided into L1 (Layer 1), L2 (Layer 2), and L3 (Layer 3) based on the three lower layers of the Open System Interconnection (OSI) standard model, which is widely known in communication systems. Among these, the physical layer belonging to Layer 1 provides an information transfer service using a physical channel, and the RRC (Radio Resource Control) layer located in Layer 3 controls radio resources between the terminal and the network. To this end, the RRC layer exchanges RRC messages between the terminal and the base station.

[0065] Figure 3 shows the structure of the NR system.

[0066] Referring to FIG. 3, the NG-RAN may include a gNB and / or an eNB that provides user plane and control plane protocol termination to the UE. FIG. 7 illustrates a case where only a gNB is included. The gNB and eNB are connected to each other via an Xn interface. The gNB and eNB are connected to the 5th generation core network (5G Core Network: 5GC) via the NG interface. More specifically, the gNB is connected to the access and mobility management function (AMF) via the NG-C interface, and the gNB is connected to the user plane function (UPF) via the NG-U interface.

[0067] Figure 4 shows the structure of a radio frame of NR.

[0068] Referring to FIG. 4, radio frames can be used for uplink and downlink transmission in NR. A radio frame has a length of 10 ms and can be defined as two 5 ms half-frames (Half-Frames, HF). A half-frame can include five 1 ms sub-frames (Subframes, SF). A sub-frame can be divided into one or more slots, and the number of slots within a sub-frame can be determined by the Subcarrier Spacing (SCS). Each slot can include 12 or 14 OFDM (A) symbols depending on the cyclic prefix (CP).

[0069] When normal CP is used, each slot can contain 14 symbols. When extended CP is used, each slot can contain 12 symbols. Here, the symbols can include OFDM symbols (or CP-OFDM symbols), SC-FDMA (Single Carrier - FDMA) symbols (or DFT-s-OFDM (Discrete Fourier Transform-spread-OFDM) symbols).

[0070] Table 1 below shows the number of symbols per slot ((N)) depending on the SCS setting (u) when normal CP is used. slot symb ), number of slots per frame ((N frame,u slot ) and the number of slots per subframe ((N subframe,u slot ) is an example.

[0071] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 15KHz (u=0)1410130KHz (u=1)1420260KHz (u=2)14404120KHz (u=3)14808240KHz (u=4)1416016

[0072] Table 2 illustrates the number of symbols per slot, the number of slots per frame, and the number of slots per subframe according to SCS when extended CP is used.

[0073] SCS (15*2 u )N slot symb N frame,u slot N subframe,u slot 60KHz (u=2)12404

[0074] In an NR system, OFDM(A) numerology (e.g., SCS, CP length, etc.) may be set differently between multiple cells that are merged into a single terminal. Accordingly, the (absolute time) interval of a time resource (e.g., subframe, slot, or TTI) (conveniently referred to as TU (Time Unit)) consisting of the same number of symbols may be set differently between the merged cells.

[0075] In NR, multiple numerologies, or SCSs, can be supported to support various 5G services. For example, a 15 kHz SCS can support wide areas in traditional cellular bands, while a 30 kHz / 60 kHz SCS can support dense urban areas, lower latency, and wider carrier bandwidth. A 60 kHz or higher SCS can support bandwidths greater than 24.25 GHz to overcome phase noise.

[0076] The NR frequency band can be defined by two types of frequency ranges. The two types of frequency ranges can be FR1 and FR2. The numerical values ​​of the frequency ranges can be changed, and for example, the two types of frequency ranges can be as shown in Table 3 below. Among the frequency ranges used in the NR system, FR1 can mean the "sub 6 GHz range", and FR2 can mean the "above 6 GHz range" and can be called millimeter wave (mmW).

[0077] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1450MHz - 6000MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0078] As described above, the numerical value of the frequency range of the NR system can be changed. For example, FR1 may include a band from 410 MHz to 7125 MHz, as shown in Table 4 below. That is, FR1 may include a frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.). For example, the frequency band above 6 GHz (or 5850, 5900, 5925 MHz, etc.) included within FR1 may include an unlicensed band. The unlicensed band may be used for various purposes, such as for vehicular communications (e.g., autonomous driving).

[0079] Frequency Range designationCorresponding frequency rangeSubcarrier Spacing (SCS)FR1410MHz - 7125MHz15, 30, 60kHzFR224250MHz - 52600MHz60, 120, 240kHz

[0080] Figure 5 shows the slot structure of an NR frame.

[0081] Referring to Figure 5, a slot includes multiple symbols in the time domain. For example, in the case of a normal CP, one slot may include 14 symbols, but in the case of an extended CP, one slot may include 12 symbols. Alternatively, in the case of a normal CP, one slot may include 7 symbols, but in the case of an extended CP, one slot may include 6 symbols.

[0082] A carrier includes multiple subcarriers in the frequency domain. An RB (Resource Block) can be defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (Bandwidth Part) can be defined as multiple consecutive (P)RBs ((Physical) Resource Blocks) in the frequency domain, and can correspond to one numerology (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through activated BWPs. Each element can be referred to as a Resource Element (RE) in the resource grid, and one complex symbol can be mapped to it.

[0083] Meanwhile, the wireless interface between terminals or between terminals and a network may be composed of an L1 layer, an L2 layer, and an L3 layer. In various embodiments of the present disclosure, the L1 layer may refer to a physical layer. Furthermore, for example, the L2 layer may refer to at least one of a MAC layer, an RLC layer, a PDCP layer, and an SDAP layer. Furthermore, for example, the L3 layer may refer to an RRC layer.

[0084] FIG. 6 illustrates a communication structure that can be provided in a 6G system according to an embodiment of the present disclosure. The embodiment of FIG. 6 can be combined with various embodiments of the present disclosure.

[0085] New network characteristics in 6G may include:

[0086] - Satellite integrated network

[0087] - Connected Intelligence: Unlike previous generations of wireless communication systems, 6G is revolutionary, upgrading the wireless evolution from "connected objects" to "connected intelligence." AI can be applied at every stage of the communication process (or at every signal processing step, as described below).

[0088] - Seamless integration of wireless information and energy transfer

[0089] - Ubiquitous super 3D connectivity: Access to networks and core network functions of drones and very low Earth orbit satellites will create super 3D connectivity in 6G ubiquitous.

[0090] Some general requirements for the new network characteristics of 6G, such as the above, may be as follows:

[0091] - small cell networks

[0092] - Ultra-dense heterogeneous network

[0093] - High-capacity backhaul

[0094] - Radar technology integrated with mobile technology: High-precision localization (or location-based services) through communications is a key feature of 6G wireless communication systems. Therefore, radar systems will be integrated with 6G networks.

[0095] - Softwarization and virtualization

[0096] Below, the core implementation technologies of the 6G system are described.

[0097] - Artificial Intelligence: Incorporating AI into communications can streamline and improve real-time data transmission. AI can use numerous analytics to determine how complex target tasks should be performed. This means AI can increase efficiency and reduce processing delays. Time-consuming tasks such as handovers, network selection, and resource scheduling can be performed instantly using AI. AI can also play a crucial role in machine-to-machine (M2M), machine-to-human, and human-to-machine communications. Furthermore, AI can facilitate rapid communication in brain-computer interfaces (BCIs). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning.

[0098] - THz communication (terahertz communication): Data rates can be increased by increasing the bandwidth. This can be achieved by using sub-THz communication with wide bandwidths and applying advanced massive MIMO technology. THz waves, also known as sub-millimeter waves, typically refer to the frequency range between 0.1 THz and 10 THz, with corresponding wavelengths ranging from 0.03 mm to 3 mm. The 100 GHz to 300 GHz band (sub-THz band) is considered a key part of the THz spectrum for cellular communications. Adding the sub-THz band to the mmWave band will increase the capacity of 6G cellular communications. Among the defined THz bands, 300 GHz to 3 THz lies in the far infrared (IR) frequency band. While part of the optical band, the 300 GHz to 3 THz band lies at the boundary of the optical band, immediately following the RF band. Therefore, this 300 GHz to 3 THz band exhibits similarities to RF.

[0099] Figure 7 illustrates the electromagnetic spectrum according to one embodiment of the present disclosure. The embodiment of Figure 7 can be combined with various embodiments of the present disclosure. Key characteristics of THz communications include (i) a widely available bandwidth to support very high data rates, and (ii) high path loss at high frequencies (highly directional antennas are essential). The narrow beamwidth generated by the highly directional antenna reduces interference. The small wavelength of THz signals allows for a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array techniques to overcome range limitations.

[0100] - Large-scale MIMO technology

[0101] - Hologram beamforming (HBF)

[0102] - Optical wireless technology

[0103] - Free-space optical transmission backhaul network (FSO backhaul network)

[0104] - Quantum communication

[0105] - Cell-free communication

[0106] - Integration of wireless information and power transmission

[0107] - Integration of wireless communication and sensing

[0108] - Integrated access and backhaul network

[0109] - Big data analysis

[0110] - Reconfigurable intelligent surface

[0111] - metaverse

[0112] - Blockchain

[0113] Unmanned aerial vehicles (UAVs): UAVs, or drones, will be a key element in 6G wireless communications. In most cases, high-speed data wireless connectivity can be provided using UAV technology. Base stations (BSs) can be installed on UAVs to provide cellular connectivity. UAVs may offer specific capabilities not found in fixed BS infrastructure, such as easy deployment, robust line-of-sight links, and controlled mobility. During emergencies such as natural disasters, deploying terrestrial communications infrastructure is not economically feasible and sometimes cannot provide services in volatile environments. UAVs can easily handle these situations. UAVs will become a new paradigm in wireless communications. This technology facilitates three fundamental requirements for wireless networks: enhanced mobile broadband (eMBB), URLLC, and mMTC. UAVs can also support various purposes, such as enhancing network connectivity, fire detection, disaster emergency services, security and surveillance, pollution monitoring, parking monitoring, and accident monitoring. Therefore, UAV technology is recognized as one of the most important technologies for 6G communications.

[0114] - Autonomous driving (self-driving): V2X (vehicle to everything), a key element in building autonomous driving infrastructure, can be a technology that allows cars to communicate and share with various elements on the road for autonomous driving, such as vehicle-to-vehicle (V2V) and vehicle-to-infrastructure (V2I) wireless communication. Fast transmission speeds and low-latency technologies are essential to maximize autonomous driving performance and ensure high safety. Furthermore, in the future, autonomous driving will go beyond simply providing warnings or guidance messages to drivers and may require active intervention in vehicle operation and direct control of the vehicle in dangerous situations. To this end, the amount of information that needs to be transmitted and received may become enormous, so 6G is expected to maximize autonomous driving with faster transmission speeds and lower latency than 5G.

[0115] Figure 8 illustrates a radio protocol architecture for SL communication. Specifically, Figure 8 (a) illustrates a user plane protocol stack of NR, and Figure 8 (b) illustrates a control plane protocol stack of NR.

[0116] Below, the SL synchronization signal (Sidelink Synchronization Signal, SLSS) and synchronization information are described.

[0117] SLSS is an SL-specific sequence and may include a Primary Sidelink Synchronization Signal (PSSS) and a Secondary Sidelink Synchronization Signal (SSSS). The PSSS may be referred to as a Sidelink Primary Synchronization Signal (S-PSS), and the SSSS may be referred to as a Sidelink Secondary Synchronization Signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 Gold sequences may be used for the S-SSS. For example, a terminal may detect an initial signal and acquire synchronization using the S-PSS. For example, a terminal may acquire detailed synchronization and detect a synchronization signal ID using the S-PSS and the S-SSS.

[0118] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in NR V2X, for evaluating PSBCH performance, the payload size of PSBCH may be 56 bits, including a 24-bit CRC.

[0119] S-PSS, S-SSS and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in the frequency to discover the S-SSB in the carrier.

[0120] Meanwhile, in the NR SL system, multiple numerologies having different SCS and / or CP lengths may be supported. In this case, as the SCS increases, the length of the time resource for a transmitting terminal to transmit an S-SSB may become shorter. Accordingly, the coverage of the S-SSB may decrease. Therefore, in order to ensure the coverage of the S-SSB, the transmitting terminal may transmit one or more S-SSBs to a receiving terminal within one S-SSB transmission period according to the SCS. For example, the number of S-SSBs that the transmitting terminal transmits to the receiving terminal within one S-SSB transmission period may be pre-configured or configured for the transmitting terminal. For example, the S-SSB transmission period may be 160 ms. For example, an S-SSB transmission period of 160 ms may be supported for all SCSs.

[0121] For example, when the SCS is 15 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 30 kHz at FR1, the transmitting terminal can transmit one or two S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 60 kHz at FR1, the transmitting terminal can transmit one, two, or four S-SSBs to the receiving terminal within one S-SSB transmission period.

[0122] For example, when the SCS is 60 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, or 32 S-SSBs to the receiving terminal within one S-SSB transmission period. For example, when the SCS is 120 kHz at FR2, the transmitting terminal can transmit 1, 2, 4, 8, 16, 32, or 64 S-SSBs to the receiving terminal within one S-SSB transmission period.

[0123] Meanwhile, when the SCS is 60 kHz, two types of CP may be supported. In addition, the structure of the S-SSB transmitted by the transmitting terminal to the receiving terminal may be different depending on the CP type. For example, the CP type may be Normal CP (NCP) or Extended CP (ECP). Specifically, for example, when the CP type is NCP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 9 or 8. On the other hand, for example, when the CP type is ECP, the number of symbols to which the PSBCH is mapped within the S-SSB transmitted by the transmitting terminal may be 7 or 6. For example, the PSBCH may be mapped to the first symbol within the S-SSB transmitted by the transmitting terminal. For example, the receiving terminal receiving the S-SSB may perform an Automatic Gain Control (AGC) operation in the first symbol section of the S-SSB.

[0124] Figure 9 shows a terminal performing V2X or SL communication.

[0125] Referring to FIG. 9, the term "terminal" in V2X or SL communication may primarily refer to a user's terminal. However, if a network device such as a base station transmits and receives signals according to a communication method between terminals, the base station may also be considered a type of terminal. For example, terminal 1 may be a first device (100), and terminal 2 may be a second device (200).

[0126] For example, terminal 1 can select a resource unit corresponding to a specific resource within a resource pool, which represents a set of resources. Then, terminal 1 can transmit an SL signal using the resource unit. For example, terminal 2, which is a receiving terminal, can be configured with a resource pool in which terminal 1 can transmit a signal, and can detect a signal from terminal 1 within the resource pool.

[0127] Here, if terminal 1 is within the connection range of the base station, the base station can inform terminal 1 of the resource pool. On the other hand, if terminal 1 is outside the connection range of the base station, another terminal can inform terminal 1 of the resource pool, or terminal 1 can use a pre-configured resource pool.

[0128] In general, a resource pool can be composed of multiple resource units, and each terminal can select one or multiple resource units to use for its SL signal transmission.

[0129] Figure 10 shows resource units for V2X or SL communication.

[0130] Referring to Figure 10, the entire frequency resources of the resource pool can be divided into NF units, and the entire time resources of the resource pool can be divided into NT units. Therefore, a total of NF * NT resource units can be defined within the resource pool. Figure 10 illustrates an example where the resource pool repeats with a cycle of NT subframes.

[0131] As shown in Figure 10, a single resource unit (e.g., Unit #0) may appear periodically and repeatedly. Alternatively, to achieve diversity effects in the time or frequency dimensions, the index of the physical resource unit to which a single logical resource unit is mapped may change in a predetermined pattern over time. In this resource unit structure, a resource pool may refer to a set of resource units that a terminal wishing to transmit an SL signal can use for transmission.

[0132] Resource pools can be subdivided into several categories. For example, based on the content of the SL signal transmitted from each resource pool, resource pools can be categorized as follows:

[0133] (1) Scheduling Assignment (SA) may be a signal that includes information such as the location of resources used by a transmitting terminal for transmission of an SL data channel, MCS (Modulation and Coding Scheme) or MIMO (Multiple Input Multiple Output) transmission method required for demodulation of other data channels, and TA (Timing Advance). SA may also be transmitted multiplexed with SL data on the same resource unit, in which case the SA resource pool may mean a resource pool in which SA is multiplexed with SL data and transmitted. SA may also be called an SL control channel.

[0134] (2) The SL data channel (Physical Sidelink Shared Channel, PSSCH) may be a resource pool used by a transmitting terminal to transmit user data. If SA is multiplexed and transmitted together with SL data on the same resource unit, only the SL data channel excluding SA information may be transmitted from the resource pool for the SL data channel. In other words, the REs (Resource Elements) that were used to transmit SA information on individual resource units within the SA resource pool may still be used to transmit SL data in the resource pool of the SL data channel. For example, the transmitting terminal may transmit the PSSCH by mapping it to consecutive PRBs.

[0135] (3) A discovery channel may be a resource pool for transmitting terminals to transmit information such as their IDs. Through this, transmitting terminals can enable neighboring terminals to discover them.

[0136] Even if the content of the SL signal described above is the same, different resource pools may be used depending on the transmission and reception properties of the SL signal. For example, even if it is the same SL data channel or discovery message, it may be again divided into different resource pools depending on the transmission timing determination method of the SL signal (for example, whether it is transmitted at the time of reception of a synchronization reference signal or whether it is transmitted by applying a certain timing advance at the time of reception), the resource allocation method (for example, whether the base station designates transmission resources for individual signals to individual transmitting terminals or whether individual transmitting terminals independently select individual signal transmission resources within the resource pool), the signal format (for example, the number of symbols each SL signal occupies in one subframe or the number of subframes used for transmission of one SL signal), the signal strength from the base station, the transmission power strength of the SL terminal, etc.

[0137] FIG. 11 illustrates an example of a BWP according to an embodiment of the present disclosure. The embodiment of FIG. 11 can be combined with various embodiments of the present disclosure. In the embodiment of FIG. 11, it is assumed that there are three BWPs.

[0138] Referring to Figure 11, a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other. Furthermore, a PRB may be a numbered resource block within each BWP. Point A may indicate a common reference point for the resource block grid.

[0139] The BWP can be set by Point A, an offset from Point A (NstartBWP), and a bandwidth (NsizeBWP). For example, Point A can be an outer reference point of a PRB of a carrier where subcarrier 0 of all numerologies (e.g., all numerologies supported by the network on that carrier) are aligned. For example, the offset can be the PRB spacing between the lowest subcarrier in a given numerology and Point A. For example, the bandwidth can be the number of PRBs in a given numerology.

[0140] SLSS (Sidelink Synchronization Signal) is a SL (sidelink) specific sequence and may include PSSS (Primary Sidelink Synchronization Signal) and SSSS (Secondary Sidelink Synchronization Signal). The PSSS may be referred to as S-PSS (Sidelink Primary Synchronization Signal) and the SSSS may be referred to as S-SSS (Sidelink Secondary Synchronization Signal). For example, length-127 M-sequences may be used for S-PSS and length-127 Gold sequences may be used for S-SSS. For example, a terminal may detect an initial signal (signal detection) and obtain synchronization using S-PSS. For example, the terminal can obtain detailed synchronization using S-PSS and S-SSS and detect a synchronization signal ID.

[0141] PSBCH (Physical Sidelink Broadcast Channel) may be a (broadcast) channel that transmits basic (system) information that a terminal must know first before transmitting or receiving an SL signal. For example, the basic information may be information related to SLSS, duplex mode (DM), TDD UL / DL (Time Division Duplex Uplink / Downlink) configuration, resource pool-related information, type of application related to SLSS, subframe offset, broadcast information, etc. For example, in order to evaluate PSBCH performance, in NR V2X, the payload size of PSBCH may be 56 bits, including a 24-bit CRC (Cyclic Redundancy Check).

[0142] S-PSS, S-SSS and PSBCH may be included in a block format supporting periodic transmission (e.g., SL SS (Synchronization Signal) / PSBCH block, hereinafter referred to as S-SSB (Sidelink-Synchronization Signal Block)). The S-SSB may have the same numerology (i.e., SCS and CP length) as the PSCCH (Physical Sidelink Control Channel) / PSSCH (Physical Sidelink Shared Channel) in the carrier, and the transmission bandwidth may be within a (pre-)configured SL BWP (Sidelink BWP). For example, the bandwidth of the S-SSB may be 11 RBs (Resource Blocks). For example, the PSBCH may span 11 RBs. And, the frequency location of the S-SSB may be (pre-)configured. Therefore, the terminal does not need to perform hypothesis detection in the frequency to discover the S-SSB in the carrier.

[0143] FIG. 12 illustrates a procedure for a terminal to perform V2X or SL communication according to a resource allocation mode, according to one embodiment of the present disclosure. The embodiment of FIG. 12 may be combined with various embodiments of the present disclosure.

[0144] Referring to (a) of FIG. 12, in resource allocation mode 1, the base station may schedule SL resources to be used by the terminal for SL transmission. For example, in step S1200, the base station may transmit information related to SL resources and / or information related to UL resources to the first terminal. For example, the UL resources may include PUCCH resources and / or PUSCH resources. For example, the UL resources may be resources for reporting SL HARQ feedback to the base station.

[0145] For example, a first terminal may receive information related to a dynamic grant (DG) resource and / or information related to a configured grant (CG) resource from a base station. For example, a CG resource may include a CG type 1 resource or a CG type 2 resource. In this specification, a DG resource may be a resource that a base station configures / allocates to the first terminal via downlink control information (DCI). In this specification, a CG resource may be a (periodic) resource that a base station configures / allocates to the first terminal via DCI and / or an RRC message. For example, in the case of a CG type 1 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal. For example, in the case of a CG type 2 resource, the base station may transmit an RRC message including information related to the CG resource to the first terminal, and the base station may transmit a DCI related to activation or release of the CG resource to the first terminal.

[0146] In step S1510, the first terminal may transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to the second terminal based on the resource scheduling. In step S1220, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1230, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal. For example, HARQ feedback information (e.g., NACK information or ACK information) may be received from the second terminal via the PSFCH. In step S1240, the first terminal may transmit / report HARQ feedback information to the base station via a PUCCH or a PUSCH. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on the HARQ feedback information received from the second terminal. For example, the HARQ feedback information reported to the base station may be information generated by the first terminal based on a rule set in advance. For example, the DCI may be DCI for scheduling SL.

[0147] Referring to (b) of FIG. 12, in resource allocation mode 2, a terminal can determine an SL transmission resource within the SL resources set by the base station / network or within the preset SL resources. For example, the set SL resources or the preset SL resources may be a resource pool. For example, the terminal can autonomously select or schedule resources for SL transmission. For example, the terminal can perform SL communication by selecting a resource within the set resource pool. For example, the terminal can select a resource within a selection window by performing sensing and resource (re)selection procedures. For example, the sensing can be performed on a subchannel basis. For example, in step S1210, a first terminal that has selected a resource within the resource pool can transmit a PSCCH (e.g., Sidelink Control Information (SCI) or 1st-stage SCI) to a second terminal using the resource. In step S1220, the first terminal may transmit a PSSCH (e.g., 2nd-stage SCI, MAC PDU, data, etc.) related to the PSCCH to the second terminal. In step S1230, the first terminal may receive a PSFCH related to the PSCCH / PSSCH from the second terminal.

[0148] Referring to (a) or (b) of FIG. 12, for example, a first terminal may transmit an SCI to a second terminal on a PSCCH. Or, for example, the first terminal may transmit two consecutive SCIs (e.g., 2-stage SCIs) to the second terminal on the PSCCH and / or the PSSCH. In this case, the second terminal may decode the two consecutive SCIs (e.g., 2-stage SCIs) to receive the PSSCH from the first terminal. In this specification, an SCI transmitted on a PSCCH may be referred to as a 1st SCI, a 1st SCI, a 1st-stage SCI, or a 1st-stage SCI format, and an SCI transmitted on a PSSCH may be referred to as a 2nd SCI, a 2nd SCI, a 2nd-stage SCI, or a 2nd-stage SCI format.

[0149] Referring to (a) or (b) of FIG. 12, in step S1530, the first terminal may receive a PSFCH. For example, the first terminal and the second terminal may determine PSFCH resources, and the second terminal may use the PSFCH resources to transmit HARQ feedback to the first terminal.

[0150] Referring to (a) of FIG. 12, in step S1540, the first terminal may transmit SL HARQ feedback to the base station via PUCCH and / or PUSCH.

[0151] Figure 13 is a diagram for explaining the control plane procedure of L2 U2N relay (UE-to-Network Relay).

[0152] The PC5-RRC aspect PC5 unicast link establishment procedure of Rel-16 NR V2X can be reused to establish a secure unicast link for L2 U2N relay (layer 2 UE-to-Network relaying) between the remote UE and the relay UE before the remote UE establishes a Uu RRC connection with the network via the relay UE.

[0153] For both in-coverage and out-of-coverage scenarios, when a remote UE initiates the first RRC message to establish a connection with a gNB, the PC5 L2 configuration for transmissions between the remote UE and the U2N relay UE can be based on the RLC / MAC configuration defined in the standard. The establishment of Uu SRB1 / SRB2 and DRB of the remote UE follows the legacy Uu configuration procedure for the L2 U2N relay.

[0154] A given scenario (TS 38.300) describes the control plane procedures of an L2 U2N relay as follows:

[0155] In step S1300, the remote UE and the relay UE can perform a discovery procedure and establish a PC5-RRC connection in step S1301 based on the existing Rel-16 procedure.

[0156] In step S1302, the remote UE can transmit the first RRC message (i.e., RRCSetupRequest) to establish a connection with the gNB via the relay UE using the default L2 configuration of PC5. The gNB responds to the remote UE with an RRCSetup message (S1303). The RRCSetup delivery to the remote UE uses the default configuration of PC5. If the relay UE is not initiated in RRC_CONNECTED, it must perform its own connection establishment upon receiving the message for the default L2 configuration of PC5.

[0157] In step S1304, the gNB and the relay UE perform a relay channel setup procedure via Uu. Depending on the configuration of the gNB, the relay / remote UE establishes an RLC channel for relaying SRB1 to the remote UE via PC5. This step prepares the relay channel for SRB1.

[0158] In step S1305, a remote UE SRB1 message (e.g., an RRCSetupComplete message) is transmitted to the gNB via the relay UE using the SRB1 relay channel over PC5. The remote UE is then RRC connected over Uu.

[0159] In steps S1306 and S1307, the remote UE and the gNB establish security according to legacy procedures, and the security message is transmitted through the Relay UE.

[0160] In steps S1308 and S1309, the gNB transmits RRCReconfiguration to the remote UE via the relay UE to set up the relay SRB2 / DRB. The remote UE responds by transmitting RRCReconfigurationComplete to the gNB via the relay UE.

[0161] In step S1310, the gNB establishes an additional RLC channel between the gNB and the relay UE for traffic relay. Depending on the configuration of the gNB, the relay / remote UE establishes an additional RLC channel between the remote UE and the relay UE for traffic relay.

[0162] In the above scenario, in addition to the connection setup procedure, for L2 UE-to-Network relay:

[0163] - RRC reconfiguration and RRC disconnection procedures can reuse legacy RRC procedures with message content / configuration design left in the WI phase.

[0164] - The RRC connection re-establishment and RRC connection resumption procedures can be reused as a baseline by considering the connection establishment procedure of the L2 U2N relay above to handle relay-specific parts along with the message content / structure design. The message content / structure can be defined later.

[0165] The setup procedure of U2N relay can be performed based on the following RRC messages (see 3GPP TS 38.331).

[0166] (1)RRCSetupRequest

[0167] The RRCSetupRequest message can be used to request the establishment of an RRC connection. The RRCSetupRequest message can be sent in the following manner.

[0168] -Signalling radio bearer: SRB0

[0169] - RLC-SAP: TM

[0170] - Logical channel: CCCH

[0171] - Direction: UE to Network

[0172] The RRCSetupRequest message can be configured as shown in Table 5 below.

[0173] -- ASN1START-- TAG-RRCSETUPREQUEST-STARTRRCSetupRequest ::= SEQUENCE {rrcSetupRequest RRCSetupRequest-IEs}RRCSetupRequest-IEs ::= SEQUENCE {ue-Identity InitialUE-Identity,establishmentCause EstablishmentCause,spare BIT STRING (SIZE (1))}InitialUE-Identity ::= CHOICE {ng-5G-S-TMSI-Part1 BIT STRING (SIZE (39)),randomValue BIT STRING (SIZE (39))}EstablishmentCause ::= ENUMERATED {emergency, highPriorityAccess, mt-Access, mo-Signalling,mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess,spare6, spare5, spare4, spare3, spare2, spare1}-- TAG-RRCSETUPREQUEST-STOP-- ASN1STOP

[0174] (2)RRCSetup

[0175] The RRCSetup message can be used to establish SRB1. The RRCSetup message can be transmitted in the following manner.

[0176] -Signalling radio bearer: SRB0

[0177] - RLC-SAP: TM

[0178] - Logical channel: CCCH

[0179] - Direction: Network to UE

[0180] The RRCSetup message can be defined as shown in Table 6 below.

[0181] -- ASN1START-- TAG-RRCSETUP-STARTRRCSetup ::= SEQUENCE {rrc-TransactionIdentifier RRC-TransactionIdentifier,criticalExtensions CHOICE {rrcSetup RRCSetup-IEs,criticalExtensionsFuture SEQUENCE {}}}RRCSetup-IEs ::= SEQUENCE {radioBearerConfig RadioBearerConfig,masterCellGroup OCTET STRING (CONTAINING CellGroupConfig),lateNonCriticalExtension OCTET STRING OPTIONAL,nonCriticalExtension RRCSetup-v1700-IEs OPTIONAL}RRCSetup-v1700-IEs ::= SEQUENCE {sl-ConfigDedicatedNR-r17 SL-ConfigDedicatedNR-r16 OPTIONAL, -- Cond L2RemoteUEsl-L2RemoteUE-Config-r17 SL-L2RemoteUE-Config-r17OPTIONAL, -- Cond L2RemoteUEnonCriticalExtension SEQUENCE {} OPTIONAL}-- TAG-RRCSETUP-STOP-- ASN1STOP

[0182] (3)SL-L2RemoteUE-Config

[0183] IESL-L2RemoteUE-Config can be used to set configurations related to L2 U2N relay operation used in L2 U2N remote UE.

[0184] The SL-L2RemoteUE-Config message can be defined as shown in Table 7 below.

[0185] -- ASN1START-- TAG-SL-L2REMOTEUE-CONFIG-STARTSL-L2RemoteUE-Config-r17::= SEQUENCE {sl-SRAP-ConfigRemote-r17SL-SRAP-Config-r17OPTIONAL, --Need Msl-UEIdentityRemote-r17 RNTI-Value OPTIONAL, -- Cond FirstRRCReconfig...}-- TAG-SL-L2REMOTEUE-CONFIG-STOP-- ASN1STOP

[0186] (4)SL-SRAP-Config

[0187] IESL-SRAP-Config can be used to configure configurable SRAP parameters used by L2 U2N relay UEs and L2 U2N remote UEs (see 3GPP TS 38.351).

[0188] The SL-SRAP-Config message can be defined as shown in Table 8 below.

[0189] -- ASN1START-- TAG-SL-SRAP-CONFIG-STARTSL-SRAP-Config-r17 ::= SEQUENCE {sl-LocalIdentity-r17INTEGER(0..255)OPTIONAL, -- Need Msl-MappingToAddModList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-MappingToAddMod-r17 OPTIONAL, -- Need Nsl-MappingToReleaseList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-RemoteUE-RB-Identity-r17 OPTIONAL, -- Need N...}SL-MappingToAddMod-r17 ::= SEQUENCE {sl-RemoteUE-RB-Identity-r17 SL-RemoteUE-RB-Identity-r17, sl-EgressRLC-ChannelUu-r17 Uu-RelayRLC-ChannelID-r17OPTIONAL, -- Cond L2RelayUEsl-EgressRLC-ChannelPC5-r17 SL-RLC-ChannelID-r17OPTIONAL, -- Need N...}SL-RemoteUE-RB-Identity-r17 ::= CHOICE {srb-Identity-r17 INTEGER (0..3),drb-Identity-r17 DRB-Identity,...}-- TAG-SL-SRAP-CONFIG-STOP-- ASN1STOP

[0190] Below, a method for performing multi-hop based U2N relay communication with respect to the above-described RRC messages is described in detail.

[0191] UE type reporting for multi-hop U2N relay operation

[0192] In the existing SL relay operation (e.g., the operation defined in 3GPP Release 17), the remote UE may transmit RRCSetupRequest, RRCReestablishmentRequest and / or RRCReresumeRequest messages to the gNB through the relay UE to establish a connection with the gNB. Referring to Tables 5 to 8, such RRC request messages do not include information about the type of UE that generated the message (e.g., type information related to whether the request message is requested by the remote UE or the relay UE).

[0193] In the existing U2N operation, since the RRC connection is sequentially performed among the remote UE, the relay UE, and the gNB, the gNB can guess / estimate which UE type generated / transmitted the RRC connection request message (e.g., RRCSetupRequest, RRCReestablishmentRequest, RRCResumeRequest) based on the RRC connection order. For example, since the relay UE may first establish an RRC connection with the gNB and then the remote UE may establish an RRC connection with the gNB, the gNB can estimate that the preceding RRC connection request message is a message for the relay UE and the succeeding RRC connection request message is a message for the remote UE in relation to the U2N relay operation. For example, the gNB may establish an RRC connection with the relay UE and assign a C-RNTI value to the relay UE. Thereafter, when the relay UE again sends an RRCSetupRequest message while providing an initial ID ('InitialUE-Identity'), the gNB can infer / guess that the RRCSetupRequest message is a message sent / initiated by a remote UE connected to the relay UE. In this case, the gNB can send an RRCSetup message including configuration information suitable for the remote UE (e.g., settings for remote operation) to the remote UE through the relay UE.

[0194] However, in a multi-hop U2N relay operation composed of multiple relay UEs, it may be difficult to implicitly recognize the transmitter of the RRC request message based on the above-described method (e.g., RRC connection order). Therefore, an explicit indication of the UE type performing the relay operation for multi-hop based U2N relay communication may be required, and a method for explicitly reporting / instructing the gNB (or base station) by additionally including information related to the UE type in the RRC message will be described in detail below.

[0195] Figure 14 is a diagram for explaining a method for performing multi-hop based U2N relay communication.

[0196] Referring to FIG. 14, a remote UE can be connected to a gNB via relay UE2 and relay UE1. Here, relay UE1 can be defined as a Uu-SL relay or Uu-SL relay type, and relay UE2 can be defined as an SL-SL relay or SL-SL relay type. For example, in a multi-hop-based U2N relay, relay UEs can be classified as Uu-SL relay UEs and SL-SL relay UEs.

[0197] Ultimately, in a multi-hop based U2N relay operation, a UE connected to a Uu-SL relay UE may be either an SL-SL relay UE or a remote UE. When a gNB receives an RRC connection request message from a Uu-SL relay UE, it must know which UE type (Uu-SL relay type, SL-SL relay type, or remote type) the UE that sent the received RRC connection request message is, so that it can set up an appropriate RLC channel mapping.

[0198] Therefore, it is necessary to additionally include information specifying or indicating the UE type (Uu-SL relay UE, SL-SL relay UE, remote UE) in the RRC connection request message. For example, information (or information elements) about the UE type may be additionally defined in the RRC connection request message related to multi-hop based U2N relay communication / operation. Specifically, information about the UE type may be additionally defined in the RRCSetupRequest, RRCReestablishmentRequest, or RRCResumeRequest messages as shown in Tables 9 to 16 below.

[0199] (1)RRCSetupRequest message

[0200] The RRCSetupRequest message can be defined as shown in Tables 9 to 11.

[0201] -- ASN1START-- TAG-RRCSETUPREQUEST-STARTRRCSetupRequest ::= SEQUENCE {rrcSetupRequest RRCSetupRequest-IEs}RRCSetupRequest-IEs ::= SEQUENCE {ue-Identity InitialUE-Identity,establishmentCause EstablishmentCause,ue-TypeENUMERATED {Uu-SL_relayUE, SL-SL_relayUE, remoteUE}spare BIT STRING (SIZE (1))}InitialUE-Identity ::= CHOICE {ng-5G-S-TMSI-Part1 BIT STRING (SIZE (39)),randomValue BIT STRING (SIZE (39))}EstablishmentCause ::= ENUMERATED {emergency, highPriorityAccess, mt-Access, mo-Signalling,mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, mps-PriorityAccess, mcs-PriorityAccess,spare6, spare5, spare4, spare3, spare2, spare1}-- TAG-RRCSETUPREQUEST-STOP-- ASN1STOP

[0202] RRCSetupRequest-IEs field descriptionsestablishmentCauseProvides the establishment cause for theRRCSetupRequestin accordance with the information received from upper layers. gNB is not expected to reject anRRCSetupRequestdue to unknown cause value being used by the UE.ue-IdentityUE identity included to facilitate contention resolution by lower layers.

[0203] InitialUE-Identity field descriptionsng-5G-S-TMSI-Part1The rightmost 39 bits of 5G-S-TMSI.randomValueInteger value in the range 0 to 2 39 - 1.

[0204] (2)RRCReestablishmentRequest message

[0205] The RRCReestablishmentRequest message can be used to request the reestablishment of an RRC connection.

[0206] -Signalling radio bearer: SRB0

[0207] - RLC-SAP: TM

[0208] - Logical Channel: CCCH

[0209] - Direction: UE to Network

[0210] The RRCReestablishmentRequest message can be defined as shown in Tables 12 to 14.

[0211] -- ASN1START-- TAG-RRCREESTABLISHMENTREQUEST-STARTRRCReestablishmentRequest ::= SEQUENCE {rrcReestablishmentRequest RRCReestablishmentRequest-IEs}RRCReestablishmentRequest-IEs ::= SEQUENCE {ue-Identity ReestabUE-Identity,ue-TypeENUMERATED {Uu-SL_relayUE, SL-SL_relayUE, remoteUE}reestablishmentCause ReestablishmentCause,spare BIT STRING (SIZE (1))}ReestabUE-Identity ::= SEQUENCE {c-RNTI RNTI-Value,physCellId PhysCellId,shortMAC-I ShortMAC-I}ReestablishmentCause ::= ENUMERATED {reconfigurationFailure, handoverFailure, otherFailure, spare1}-- TAG-RRCREESTABLISHMENTREQUEST-STOP-- ASN1STOP

[0212] ReestabUE-Identity field descriptionsphysCellIdThe Physical Cell Identity of the PCell the UE was connected to prior to the failure.

[0213] RRCReestablishmentRequest-IEs field descriptionsreestablishmentCauseIndicates the failure cause that triggered the re-establishment procedure. gNB is not expected to reject aRRCReestablishmentRequestdue to unknown cause value being used by the UE.ue-IdentityUE identity included to retrieve UE context and to facilitate contention resolution by lower layers.

[0214] (3)RRCResumeRequest message

[0215] The RRCResumeRequest message is used to request the resumption of a suspended RRC connection or to perform an RNA update.

[0216] -Signalling radio bearer: SRB0

[0217] - RLC-SAP: TM

[0218] - Logical Channel: CCCH

[0219] - Direction: UE to Network

[0220] The RRCResumeRequest message can be defined as shown in Tables 15 and 16.

[0221] -- ASN1START-- TAG-RRCRESUMEREQUEST-STARTRRCResumeRequest ::= SEQUENCE {rrcResumeRequest RRCResumeRequest-IEs}RRCResumeRequest-IEs ::= SEQUENCE {resumeIdentity ShortI-RNTI-Value,ue-Type ENUMERATED {Uu-SL_relayUE, SL-SL_relayUE, remoteUE}resumeMAC-I BIT STRING (SIZE (16)),resumeCause ResumeCause,spare BIT STRING (SIZE (1))}-- TAG-RRCRESUMEREQUEST-STOP-- ASN1STOP

[0222] RRCResumeRequest-IEs field descriptionsresumeCauseProvides the resume cause for the RRC connection resume request as provided by the upper layers or RRC. The network is not expected to reject anRRCResumeRequestdue to unknown cause value being used by the UE.resumeIdentityUE identity to facilitate UE context retrieval at gNB.resumeMAC-IAuthentication token to facilitate UE authentication at gNB. The 16 least significant bits of the MAC-I calculated using the AS security configuration as specified.

[0223] The gNB may receive the RRC connection request message (or RRC connection establishment request message) described above from the Uu-SL relay UE, the SL-SL relay UE, and / or the remote UE. In this case, the gNB may transmit an RRC connection-related configuration (e.g., RRCSetup, RRCReestablishment, RRCResume) message to the Uu-SL relay UE, the SL-SL relay UE, and / or the remote UE (or the transmitting entity) for establishing an appropriate bearer / RLC channel mapping configuration according to the UE type of the transmitting entity that transmitted the RRC connection request message. For example, the gNB may check the UE type included in the RRC connection request message, and transmit an RRC connection-related configuration message (e.g., RRCSetup, RRCReestablishment, RRCResume) including information on the bearer / RLC channel mapping configuration corresponding to the checked UE type. Additionally, the above-described method can be equally applied to the RRCReconfiguration message in which the gNB re-establishes the RRC connection to the relay UE and / or remote UE.

[0224] For example, the gNB can configure the RRC connection through the configuration messages (RRCSetup, RRCReestablishment, RRCResume, RRCReconfiguration) for the RRC connection. At this time, the gNB needs to configure an appropriate RRC connection according to the UE type of each of the remote UE, the Uu-SL relay UE, and the SL-SL relay UE. For example, if the UE that transmitted the RRC connection request message is a Uu-SL relay UE, the gNB needs to establish a mapping relationship between the Uu RLC channel and the SL RLC channel through the configuration message for the RRC connection. In contrast, if the UE that transmitted the RRC connection request message is an SL-SL relay UE, the gNB needs to configure 1 st -SL RLC channel of hop and 2 nd - It is necessary to set up a mapping relationship between the SL RLC channels of the hop. Here, the mapping relationship between the Uu RLC channel and the SL RLC channel, and 1 st - SL RLC channel of Hop and 2 nd -The mapping relationship between SL RLC channels of a hop can be established based on an e2e bearer (end-to-end bearer).

[0225] The setup message for the RRC connection related to this can be defined as follows.

[0226] (1)RRCSetup message

[0227] The RRCSetup message can be used to configure SRB1. In relation to multi-hop U2N relay, the RRCSetup message can be defined as shown in Table 17 below. For example, as shown in Table 17, the RRCSetup message can additionally define the parameters of Uu-SL-L2RelayUE-Config-r17 or sl-SL-L2RelayUE-Config-r17.

[0228] -- ASN1START-- TAG-RRCSETUP-STARTRRCSetup ::= SEQUENCE {rrc-TransactionIdentifier RRC-TransactionIdentifier,criticalExtensions CHOICE {rrcSetup RRCSetup-IEs,criticalExtensionsFuture SEQUENCE {}}}RRCSetup-IEs ::= SEQUENCE {radioBearerConfig RadioBearerConfig,masterCellGroup OCTET STRING (CONTAINING CellGroupConfig),lateNonCriticalExtension OCTET STRING OPTIONAL,nonCriticalExtension RRCSetup-v1700-IEs OPTIONAL}RRCSetup-v1700-IEs ::= SEQUENCE {sl-ConfigDedicatedNR-r17 SL-ConfigDedicatedNR-r16 OPTIONAL, -- Cond L2RemoteUEsl-L2RemoteUE-Config-r17 SL-L2RemoteUE-Config-r17 OPTIONAL, -- Cond L2RemoteUEUu-SL-L2RelayUE-Config-r17 Uu-SL-L2RelayUE-Config-r17sl-SL-L2RelayUE-Config-r17 SL-SL-L2RelayUE-Config-r17nonCriticalExtension SEQUENCE {}OPTIONAL}-- TAG-RRCSETUP-STOP-- ASN1STOP

[0229] For example, if an RRC setup request message (e.g., RRCSetupRequest) in which the UE type is set to Uu-SL UE relay is received, the gNB can set a mapping relationship between the RLC channel of the Uu connection and the RLC channel of the SL connection through Uu-SL-L2RelayUE-Config-r17 of the RRCSetup message. Alternatively, if an RRC setup request message in which the UE type is set to SL-SL UE relay is received, the gNB can set a mapping relationship between the RLC channel of the Uu connection and the RLC channel of the SL connection through sl-SL-L2RelayUE-Config-r17 of the RRCSetup message. st - SL RLC channel of Hop and 2 nd -You can set the mapping relationship between SL RLC channels of a hop.

[0230] (2)RRCReestablishment message

[0231] The RRCReestablishment message can be used to reset SRB1.

[0232] -Signalling radio bearer: SRB1

[0233] - RLC-SAP: AM

[0234] - Logical channel: DCCH

[0235] - Direction: Network to UE

[0236] In relation to multi-hop U2N relay, the RRCReestablishment message can be defined as shown in Table 18 below. For example, as shown in Table 18, the RRCReestablishment message can additionally define the parameters of Uu-SL-L2RelayUE-Config-r17 or sl-SL-L2RelayUE-Config-r17.

[0237] -- ASN1START-- TAG-RRCREESTABLISHMENT-STARTRRCReestablishment ::= SEQUENCE {rrc-TransactionIdentifier RRC-TransactionIdentifier,criticalExtensions CHOICE {rrcReestablishment RRCReestablishment-IEs,criticalExtensionsFuture SEQUENCE {}}}RRCReestablishment-IEs ::= SEQUENCE {nextHopChainingCount NextHopChainingCount,lateNonCriticalExtension OCTET STRING OPTIONAL,nonCriticalExtension RRCReestablishment-v1700-IEs OPTIONAL}RRCReestablishment-v1700-IEs ::= SEQUENCE {sl-L2RemoteUE-Config-r17 SetupRelease {SL-L2RemoteUE-Config-r17} OPTIONAL, -- Cond L2RemoteUEUu-SL-L2RelayUE-Config-r17Uu-SL-L2RelayUE-Config-r17sl-SL-L2RelayUE-Config-r17SL-SL-L2RelayUE-Config-r17nonCriticalExtension SEQUENCE {} OPTIONAL}-- TAG-RRCREESTABLISHMENT-STOP-- ASN1STOP

[0238] For example, if an RRC configuration request message (e.g., an RRCReestablishmentRequest message) in which the UE type is set to Uu-SL UE relay is received, the gNB can establish a mapping relationship between the RLC channel of the Uu connection and the RLC channel of the SL connection through Uu-SL-L2RelayUE-Config-r17 of the RRCReestablishment message. Alternatively, if an RRC configuration request message in which the UE type is set to SL-SL UE relay is received, the gNB can establish a mapping relationship between the RLC channel of the Uu connection and the RLC channel of the SL connection through sl-SL-L2RelayUE-Config-r17 of the RRCReestablishment message. st - SL RLC channel of Hop and 2 nd -You can set the mapping relationship between SL RLC channels of a hop.

[0239] (2)RRCResume message

[0240] The RRCResume message can be used to resume a suspended RRC connection.

[0241] -Signalling radio bearer: SRB1

[0242] - RLC-SAP: AM

[0243] - Logical channel: DCCH

[0244] - Direction: Network to UE

[0245] In relation to multi-hop U2N relay, the RRCResume message can be defined as shown in Table 19 below. For example, as shown in Table 19, the RRCResume message can additionally define the parameters of Uu-SL-L2RelayUE-Config-r17 or sl-SL-L2RelayUE-Config-r17.

[0246] -- ASN1START-- TAG-RRCRESUME-STARTRRCResume ::= SEQUENCE {rrc-TransactionIdentifier RRC-TransactionIdentifier,criticalExtensions CHOICE {rrcResume RRCResume-IEs,criticalExtensionsFuture SEQUENCE {}}}RRCResume-IEs ::= SEQUENCE {radioBearerConfig RadioBearerConfigOPTIONAL, -- Need MmasterCellGroup OCTET STRING (CONTAINING CellGroupConfig)OPTIONAL, -- Need MmeasConfig MeasConfigOPTIONAL, -- Need MfullConfig ENUMERATED {true}OPTIONAL, -- Need NlateNonCriticalExtension OCTET STRINGOPTIONAL,nonCriticalExtension RRCResume-v1560-IEsOPTIONAL}RRCResume-v1560-IEs ::= SEQUENCE {radioBearerConfig2 OCTET STRING (CONTAINING RadioBearerConfig)OPTIONAL, -- Need Msk-Counter SK-CounterOPTIONAL, -- Need NnonCriticalExtension RRCResume-v1610-IEsOPTIONAL}RRCResume-v1610-IEs ::= SEQUENCE {idleModeMeasurementReq-r16 ENUMERATED {true}OPTIONAL, -- Need NrestoreMCG-SCells-r16 ENUMERATED {true}OPTIONAL, -- Need NrestoreSCG-r16 ENUMERATED {true}OPTIONAL,-- Need Nmrdc-SecondaryCellGroup-r16 CHOICE {nr-SCG-r16 OCTET STRING (CONTAINING RRCReconfiguration),eutra-SCG-r16 OCTET STRING} OPTIONAL, -- Cond RestoreSCGneedForGapsConfigNR-r16 SetupRelease {NeedForGapsConfigNR-r16}OPTIONAL, -- Need MnonCriticalExtension RRCResume-v1700-IEsOPTIONAL}RRCResume-v1700-IEs ::= SEQUENCE {sl-ConfigDedicatedNR-r17 SetupRelease {SL-ConfigDedicatedNR-r16}OPTIONAL, -- Cond L2RemoteUEsl-L2RemoteUE-Config-r17 SetupRelease {SL-L2RemoteUE-Config-r17}OPTIONAL, -- Cond L2RemoteUEUu-SL-L2RelayUE-Config-r17SetupRelease { Uu-SL-L2RelayUE-Config-r17}sl-SL-L2RelayUE-Config-r17SetupRelease { SL-SL-L2RelayUE-Config-r17}needForGapNCSG-ConfigNR-r17 SetupRelease {NeedForGapNCSG-ConfigNR-r17}OPTIONAL, -- Need MneedForGapNCSG-ConfigEUTRA-r17 SetupRelease {NeedForGapNCSG-ConfigEUTRA-r17}OPTIONAL, -- Need Mscg-State-r17 ENUMERATED {deactivated}OPTIONAL, -- Need NappLayerMeasConfig-r17 AppLayerMeasConfig-r17OPTIONAL,-- Need MnonCriticalExtension SEQUENCE {}OPTIONAL}-- TAG-RRCRESUME-STOP-- ASN1STOP,

[0247] For example, if an RRC setup request message (e.g., RRCResumeRequest) in which the UE type is set to Uu-SL UE relay is received, the gNB can set a mapping relationship between the RLC channel of the Uu connection and the RLC channel of the SL connection through Uu-SL-L2RelayUE-Config-r17 of the RRCResume message. Alternatively, if an RRC setup request message in which the UE type is set to SL-SL UE relay is received, the gNB can set a mapping relationship between the RLC channel of the Uu connection and the RLC channel of the SL connection through sl-SL-L2RelayUE-Config-r17 of the RRCResume message. st - SL RLC channel of Hop and 2 nd -You can set the mapping relationship between SL RLC channels of a hop.

[0248] Alternatively, the relay UE or remote UE may transmit a SUI (SidelinkUEInformationNR) message including information about the UE type to the base station after RRC connection (e.g., after performing RRC connection without distinction of UE type). The existing SUI message includes UE type information about whether it is a relay UE or a remote UE, but as described above, for multi-hop relay communication / operation, information about more detailed UE types needs to be defined. For example, for multi-hop relay communication, the SUI message may additionally include or define UE type information that is detailed as Uu-SL Relay, SL-SL Relay, or remote UE, as shown in Table 20.

[0249] SidelinkUEInformationNR-v1700-IEs ::= SEQUENCE {sl-TxResourceReqList-v1700 SL-TxResourceReqList-v1700,sl-RxDRX-ReportList-v1700 SL-RxDRX-ReportList-v1700,sl-RxInterestedGC-BC-DestList-r17 SL-RxInterestedGC-BC-DestList-r17,sl-RxInterestedFreqListDisc-r17 SL-InterestedFreqList-r16,sl-TxResourceReqListDisc-r17 SL-TxResourceReqListDisc-r17,sl-TxResourceReqListCommRelay-r17 SL-TxResourceReqListCommRelay-r17,ue-Type-r17 ENUMERATED { Uu-SL_relayUE, SL-SL_relay UE, remoteUE},sl-SourceIdentityRemoteUE-r17 SL-SourceIdentity-r17,nonCriticalExtension SidelinkUEInformationNR-v1800-IEs}

[0250] In this way, when the type information of a UE performing multi-hop-based U2N relay communication is reported to the gNB through the SUI message, the gNB can establish a mapping relationship of an RLC channel corresponding to the type of the UE through the RRC reconfiguration procedure. Meanwhile, when detailed UE type information is defined for the SUI message, information about the above-described UE type may not be defined in the RRC connection request message (RRCSetupRequest, RRCReestablishmentRequest, RRCResumeRequest message).

[0251] Meanwhile, in the current single-hop U2N, the relay UE needs a mapping relationship (based on end-to-end bearer) between the Uu RLC channel and the SL RLC channel, but for the intermediate relay UE (SL-SL relay UE) of the far hop, the mapping relationship (based on end-to-end bearer) between the ingress SL RLC channel and the egress SL RLC channel needs to be additionally defined.

[0252] For example, if the type of relay UE performing multi-hop based U2N relay communication is SL-SL relay UE, the relay UE sets 1 through an RRC configuration message. st - SL RLC channel of Hop and 2 nd - The mapping relationship between the SL RLC channels of the hop can be established. At this time, the relay UE establishes 1 through the RRC setup message. st - SL RLC channel of Hop and 2 nd - It is necessary to specify which SL RLC channel is the ingress SL RLC channel and which is the egress SL RLC channel in relation to the SL RLC channels of a hop. For this purpose, the SL-SRAP-Config configure message needs to define additional elements for the mapping relationship between the ingress SL RLC channel and the egress SL RLC channel as shown in Table 21 below. Here, the SL-SRAP-Config configure message may be a message used to configure configurable SRAP parameters used in the L2 U2N relay UE and the L2 U2N remote UE (see 3GPP TS 38.351).

[0253] -- ASN1START-- TAG-SL-SRAP-CONFIG-STARTSL-SRAP-Config-r17 ::= SEQUENCE {sl-LocalIdentity-r17 INTEGER (0..255) OPTIONAL, -- Need Msl-MappingToAddModList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-MappingToAddMod-r17 OPTIONAL, -- Need Nsl-MappingToReleaseList-r17 SEQUENCE (SIZE (1..maxLC-ID)) OF SL-RemoteUE-RB-Identity-r17 OPTIONAL, -- Need N...}SL-MappingToAddMod-r17 ::= SEQUENCE {sl-RemoteUE-RB-Identity-r17 SL-RemoteUE-RB-Identity-r17,sl-EgressRLC-ChannelUu-r17 Uu-RelayRLC-ChannelID-r17OPTIONAL, -- Cond L2RelayUEsl-ingressRLC-ChannelSL-r17 SL-RLC-ChannelID-r17,OPTIONAL, -- cond SL-SL_L2RelayUEsl-EgressRLC-ChannelPC5-r17 SL-RLC-ChannelID-r17OPTIONAL, -- Need N...}SL-RemoteUE-RB-Identity-r17 ::= CHOICE {srb-Identity-r17 INTEGER (0..3),drb-Identity-r17 DRB-Identity,...}-- TAG-SL-SRAP-CONFIG-STOP-- ASN1STOP

[0254] Here, the ingress RLC channel refers to the RLC channel of the previous hop (or, 1st-hop) based on the SL-SL relay UE, and the egress RLC channel refers to the RLC channel of the next hop (or, 2nd-hop) based on the SL-SL relay UE. In other words, the ingress RLC channel may be an RLC channel (e.g., an input RLC channel) in the direction in which the UE performing multi-hop relay communication receives packets from the relay UE, remote UE, or gNB, and the egress RLC channel may be an RLC channel (e.g., an output RLC channel) in the direction in which the UE performing multi-hop relay communication transmits packets to the relay UE, remote UE, or gNB.

[0255] Additionally, in order to receive RRC reconfiguration suitable for the UE type, the relay UE or remote UE can report the UE type to the gNB using the SUI message described above. At this time, as described with reference to Table 20, the relay UE or remote UE can clearly distinguish and report whether the UE type that transmitted the SUI message is a Uu-SL relay UE, an SL-SL relay UE, or a remote UE through the ue_Type additionally defined in the SUI message.

[0256] As described above, a UE performing multi-hop based U2N relay communication can report the exact UE type to the gNB through the above-described RRC connection request message or SUI message. Accordingly, the gNB can set up an appropriate RLC channel mapping relationship (e.g., a mapping relationship of Uu RLC channel - SL RLC channel, (input) SL RLC channel - (output) SL RLC channel) according to each UE type.

[0257] FIG. 15 is a diagram illustrating a method for a first relay UE to receive configuration information for multi-hop based U2N relay communication.

[0258] A first relay UE can forward / relay data between a remote UE and a base station via multi-hop based U2N relay communication. For example, the first relay UE can establish a direct connection (PC5 connection or SL connection) with another relay UE or the remote UE via a discovery procedure. The first relay UE can transmit an RRC connection request message related to an RRC connection of the remote UE or the first relay UE to the base station, and perform an RRC connection for the multi-hop based U2N relay based on an RRC setup message in response to the RRC connection request message.

[0259] At this time, when the first relay UE performs multi-hop based U2N relay communication / operation as described above, the mapping relationship of the RLC channel set to the first relay UE (e.g., the RLC channel mapping relationship between a Uu connection and an SL connection or the RLC channel mapping relationship between an SL connection and an SL connection) may be different depending on whether the first relay UE is a relay UE directly connected to the base station. Therefore, the first relay UE needs to explicitly provide information about its relay type to the base station in order to set an RLC channel appropriate for its relay type.

[0260] Specifically, referring to FIG. 15, a first relay UE may transmit a first message to a base station, the first message including type information about the first relay UE related to multi-hop based U2N relay communication / operation (S151). As described above, the first message may be an RRCSetupRequest message, an RRCReestablishmentRequest message, or an RRCResumeRequest message for requesting an RRC connection for multi-hop based U2N relay communication / operation. Alternatively, the first message may be an SUI message transmitted after completing an RRC connection with the base station. As defined in Table 9, Table 12, Table 15, and / or Table 20, the first message may additionally define fields / elements for a UE type related to multi-hop based U2N relay.

[0261] Here, the type information may be information on whether the first relay UE is a relay UE (or a last relay UE) directly connected to the base station in the multi-hop based U2N relay as described above, or a relay UE (or an intermediate relay UE) not directly connected to the base station. For example, if the first relay UE is a relay UE directly connected to the base station, the first relay UE may be a Uu-SL relay UE (or a first relay type). If the first relay UE is a relay UE not directly connected to the base station, the first relay UE may be a SL-SL relay UE (or a second relay type). For example, if the first relay UE performs the multi-hop based U2N relay through a first connection with a remote UE and a second connection with a second relay UE, the first relay UE may transmit the first message including type information in which the first relay type is set to the base station. Alternatively, when the first relay UE performs the multi-hop based U2N relay through a first connection with a remote UE and a second connection with a second relay UE, the first relay UE may transmit the first message including type information in which the second relay type is set to the base station.

[0262] Next, the first relay UE may receive a second message from the base station, which includes configuration information for setting up an RLC (Radio Link Control) channel for the multi-hop based U2N relay (S153). As described above, if the first message is an RRC message requesting an RRC connection, the second message may be an RRCSetup message, an RRCReestablishment message, an RRCResume message, or an RRCReconfiguration message. Alternatively, if the first message is an SUI message, the second message may be an RRCReconfiguration message.

[0263] As described above, the second message may additionally include a parameter for Uu-SL-L2RelayUE-Config-r17 or sl-SL-L2RelayUE-Config-r17 based on the type information included in the first message. Here, Uu-SL-L2RelayUE-Config-r17 may be a parameter that sets a mapping relationship between an RLC channel for a Uu connection (direct connection to a base station) for the first relay UE and an RLC channel for an SL connection (direct connection to another relay UE), and sl-SL-L2RelayUE-Config-r17 may be a parameter that sets a mapping relationship between a first RLC channel (or a first SL RLC channel) for a first SL connection for the first relay UE and a second RLC channel (or a second SL RLC channel) for a second SL connection.

[0264] For example, if the first relay UE transmits a first message including the type information for the first relay type, the first relay UE may receive the second message including configuration information for setting an RLC channel for a Uu connection, which is a direct connection to the base station, and an RLC channel for a direct connection (e.g., an SL connection or a PC5 connection) with another UE. In this case, the first relay UE may set or map the RLC channel for the Uu connection and the RLC channel for the SL connection based on the second message.

[0265] Alternatively, if the first relay UE transmits a first message including the type information for the second relay type, the first relay UE may receive the second message including configuration information for setting a first RLC channel for a first SL connection with the other relay UE and a second RLC channel for a second SL connection with another UE (e.g., another relay UE or a remote UE). In this case, the first relay UE may set or map the first RLC channel for the first SL connection and the RLC channel for the second SL connection based on the second message.

[0266] Next, the first relay UE can establish or reestablish an RRC connection with the base station based on the second message (S155). For example, the first relay UE can establish or reestablish the RRC connection by setting RLC channel(s) for the multi-hop-based U2N relay based on the configuration information.

[0267] Alternatively, the first relay UE may receive a SL-SRAP-Config configure message after completing the above-described RRC connection, and may determine what the ingress RLC channel and the egress RLC channel are among the RLC channels set by the configuration information based on the SL-SRAP-Config configure message.

[0268] Alternatively, the first relay UE may perform multi-hop based U2N relay communication / operation to relay data between the remote UE and the base station based on the RRC connection with the base station and the setup of an RLC channel.

[0269] FIG. 16 is a diagram illustrating a method for a base station to provide configuration information for a multi-hop based U2N relay.

[0270] Referring to FIG. 16, the base station may receive a first message related to a multi-hop based U2N relay from the first relay UE (S161). As described above, the first message may be an RRCSetupRequest message, an RRCReestablishmentRequest message, or an RRCResumeRequest message requesting an RRC connection for the multi-hop based U2N relay. Alternatively, the first message may be an SUI message. In addition, as described above, when the first message is a message requesting an RRC connection related to the multi-hop based U2N relay, type information regarding the first relay UE may be further included.

[0271] Next, the base station may transmit a second message to the first relay UE, the second message including configuration information for setting up RLC channel(s) related to the multi-hop based U2N relay based on the type information included in the first message (S163). As described above, the second message may be an RRCSetup message, an RRCReestablishment message, an RRCResume message, or an RRCReconfiguration message for setting up an RRC connection related to the multi-hop based U2N relay. Alternatively, when the first message is an SUI message, the second message may be an RRCReconfiguration message. As described above, the second message may additionally include parameters for Uu-SL-L2RelayUE-Config-r17 or sl-SL-L2RelayUE-Config-r17 based on the type information included in the first message (see Tables 17 to 19). Here, Uu-SL-L2RelayUE-Config-r17 is a parameter that sets a mapping relationship between an RLC channel for a Uu connection (direct connection to a base station) for the first relay UE and an RLC channel for an SL connection (direct connection to another relay UE), and sl-SL-L2RelayUE-Config-r17 is a parameter that sets a mapping relationship between an RLC channel for a Uu connection (direct connection to a base station) for the first relay UE and an RLC channel for an SL connection (direct connection to another relay UE) for the first relay UE. st 1st RLC channel and 2nd SL connection (or, 2) for hop nd It may be a parameter that sets the mapping relationship between the second RLC channels for the hop.

[0272] For example, when receiving a first message including the type information for the first relay type from the first relay UE, the base station can set a mapping relationship between an RLC channel for a Uu connection and an RLC channel for an SL connection (or, a PC5 connection) for the first relay UE through Uu-SL-L2RelayUE-Config-r17 included in the second message. Or, when receiving a first message including the type information for the second relay type from the first relay UE, the base station can set a mapping relationship between a first RLC channel for the first SL connection and a second RLC channel for the second SL connection for the first relay UE through sl-SL-L2RelayUE-Config-r17 included in the second message.

[0273] In this case, the base station can establish an RRC connection with the first relay UE (and / or remote UE) based on the second message, and transmit and receive data with the remote UE based on the multi-hop based U2N relay operation.

[0274] In this way, the proposed invention can quickly set up an appropriate RLC channel according to the relay UE type by providing relay type information on whether the UE is a Uu-SL relay UE or an SL-SL relay UE during the RRC connection setup process in multi-hop based U2N relay communication. In addition, the proposed invention can effectively ensure that the base station sets up an appropriate RLC channel mapping relationship according to the relay UE type by explicitly providing the gNB with relay type information on whether the UE is a Uu-SL relay UE or an SL-SL relay UE through an RRC connection request message or an SUI message.

[0275] Examples of communication systems to which the invention applies

[0276] Although not limited thereto, the various descriptions, functions, procedures, proposals, methods and / or operational flowcharts of the present invention disclosed in this document may be applied to various fields requiring wireless communication / connection (e.g., 5G) between devices.

[0277] Hereinafter, more specific examples will be provided with reference to the drawings. In the drawings / descriptions below, the same drawing reference numerals may represent identical or corresponding hardware blocks, software blocks, or functional blocks, unless otherwise described.

[0278] Figure 17 illustrates a communication system applied to the present invention.

[0279] Referring to FIG. 17, a communication system (1) applied to the present invention includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using a wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Things) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with a wireless communication function, an autonomous vehicle, a vehicle capable of performing vehicle-to-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices, and can be implemented in the form of HMD (Head-Mounted Device), HUD (Head-Up Display) installed in a vehicle, television, smartphone, computer, wearable device, home appliance, digital signage, vehicle, robot, etc. Mobile devices can include smartphone, smart pad, wearable device (e.g., smart watch, smart glass), computer (e.g., laptop, etc.), etc. Home appliances can include TV, refrigerator, washing machine, etc. IoT devices can include sensors, smart meters, etc. For example, base stations and networks can also be implemented as wireless devices, and a specific wireless device (200a) can act as a base station / network node to other wireless devices.

[0280] Wireless devices (100a to 100f) can be connected to a network (300) via a base station (200). Artificial Intelligence (AI) technology can be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, a 5G (e.g., NR) network, etc. The wireless devices (100a to 100f) can communicate with each other via the base station (200) / network (300), but can also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to Everything) communication). In addition, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0281] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base stations (200), and base stations (200) / base stations (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR) such as uplink / downlink communication (150a), sidelink communication (150b) (or, D2D communication), and communication between base stations (150c) (e.g., relay, IAB (Integrated Access Backhaul). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, at least some of various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present invention.

[0282] Examples of wireless devices to which the present invention is applied

[0283] Figure 18 illustrates a wireless device applicable to the present invention.

[0284] Referring to FIG. 18, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} can correspond to {the wireless device (100x), the base station (200)} and / or {the wireless device (100x), the wireless device (100x)} of FIG. 17.

[0285] A first wireless device (100) includes one or more processors (102) and one or more memories (104), and may further include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memories (104) and / or the transceivers (106), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (102) may process information in the memory (104) to generate first information / signal, and then transmit a wireless signal including the first information / signal via the transceiver (106). In addition, the processor (102) may receive a wireless signal including second information / signal via the transceiver (106), and then store information obtained from signal processing of the second information / signal in the memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may perform some or all of the processes controlled by the processor (102), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chipset designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals via one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used interchangeably with an RF (Radio Frequency) unit. In the present invention, a wireless device may also mean a communication modem / circuit / chipset.

[0286] Specifically, the first wireless device or first relay UE (100) may include a processor (102) and a memory (104) connected to a transceiver (106). The memory (104) may include at least one program capable of performing operations related to the embodiments described in FIGS. 14 to 16.

[0287] A processor (102) can control a transceiver (106) to transmit to a base station a first message including type information of a first relay UE (user equipment) related to a multi-hop based U2N (UE to Network) relay, and receive from the base station a second message including configuration information for setting an RLC (Radio Link Control) channel for the multi-hop based U2N relay. Here, the type information can include information on a first relay type or a second relay type based on whether the first relay UE is directly connected to the base station.

[0288] Alternatively, a processing device may be configured including a processor (102) and a memory (104). In this case, at least one processor; and at least one memory connected to the at least one processor and storing instructions, wherein the instructions, based on being executed by the at least one processor, cause the first relay UE to: transmit a first message to a base station, the first relay UE including type information related to a multi-hop based U2N (UE to network) relay, and receive a second message from the base station, the second message including configuration information for setting an RLC (Radio Link Control) channel for the multi-hop based U2N relay. Here, the type information may include information on a first relay type or a second relay type based on whether the first relay UE is directly connected to the base station.

[0289] The second wireless device (200) includes one or more processors (202), one or more memories (204), and may further include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memories (204) and / or the transceivers (206), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document. For example, the processor (202) may process information in the memory (204) to generate third information / signals, and then transmit a wireless signal including the third information / signals via the transceivers (206). Furthermore, the processor (202) may receive a wireless signal including fourth information / signals via the transceivers (206), and then store information obtained from signal processing of the fourth information / signals in the memory (204). The memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, the memory (204) may perform some or all of the processes controlled by the processor (202), or may store software code including commands for performing the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. Here, the processor (202) and the memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals via one or more antennas (208). The transceiver (206) may include a transmitter and / or a receiver. The transceiver (206) may be used interchangeably with an RF unit. In the present invention, a wireless device may also mean a communication modem / circuit / chip.

[0290] Specifically, the second wireless device or base station (200) may include a processor (202) and a memory (204) connected to a transceiver (206). The memory (204) may include at least one program capable of performing operations related to the embodiments described in FIGS. 14 to 16.

[0291] A processor (202) can control a transceiver (206) to receive a first message including type information of a first relay UE (user equipment) related to a multi-hop based U2N (UE to Network) relay, and transmit a second message including configuration information for setting an RLC (Radio Link Control) channel for the multi-hop based U2N relay. Here, the type information can include information on a first relay type or a second relay type determined based on whether the first relay UE is directly connected to the base station.

[0292] Hereinafter, the hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or one or more Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this document. One or more processors (102, 202) can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data or information according to the functions, procedures, proposals and / or methods disclosed herein, and provide the signals to one or more transceivers (106, 206). One or more processors (102, 202) can receive signals (e.g., baseband signals) from one or more transceivers (106, 206) and obtain PDUs, SDUs, messages, control information, data or information according to the descriptions, functions, procedures, proposals, methods and / or operational flowcharts disclosed herein.

[0293] One or more processors (102, 202) may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For 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, 202). The descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software configured to perform one or more processors (102, 202) or stored in one or more memories (104, 204) and executed by one or more processors (102, 202). The descriptions, functions, procedures, suggestions, methods and / or operation flowcharts disclosed in this document may be implemented using firmware or software in the form of codes, instructions and / or sets of instructions.

[0294] One or more memories (104, 204) may be coupled to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. The one or more memories (104, 204) may be configured as ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories (104, 204) may be located internally and / or externally to the one or more processors (102, 202). Additionally, the one or more memories (104, 204) may be coupled to the one or more processors (102, 202) via various technologies, such as wired or wireless connections.

[0295] One or more transceivers (106, 206) can transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or flowcharts of this document, to one or more other devices. One or more transceivers (106, 206) can receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or flowcharts of this document, from one or more other devices. For example, one or more transceivers (106, 206) can be connected to one or more processors (102, 202) and can transmit and receive wireless signals. For example, one or more processors (102, 202) can control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be coupled to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, or the like, as referred to in the descriptions, functions, procedures, proposals, methods, and / or operational flowcharts disclosed herein, via one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert received user data, control information, wireless signals / channels, etc. from RF band signals to baseband signals in order to process the received user data, control information, wireless signals / channels, etc. using one or more processors (102, 202).One or more transceivers (106, 206) may convert user data, control information, wireless signals / channels, etc. processed by one or more processors (102, 202) from baseband signals to RF band signals. For this purpose, one or more transceivers (106, 206) may include an (analog) oscillator and / or filter.

[0296] Examples of wireless devices to which the present invention is applied

[0297] Figure 19 illustrates another example of a wireless device applicable to the present invention. The wireless device may be implemented in various forms depending on the use case / service (see Figure 17).

[0298] Referring to FIG. 19, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 18 and may be composed of various elements, components, units / units, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and additional elements (140). The communication unit may include a communication circuit (112) and a transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 19. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 18. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and the additional elements (140) and controls the overall operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on the program / code / command / information stored in the memory unit (130). In addition, the control unit (120) may transmit information stored in the memory unit (130) to an external device (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external device (e.g., another communication device) via a wireless / wired interface in the memory unit (130).

[0299] The additional element (140) may be configured in various ways depending on the type of the wireless device. For example, the additional element (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 17, 100a), a vehicle (Fig. 17, 100b-1, 100b-2), an XR device (Fig. 17, 100c), a portable device (Fig. 17, 100d), a home appliance (Fig. 17, 100e), an IoT device (Fig. 17, 100f), a digital broadcasting terminal, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or a financial device), a security device, a climate / environmental device, an AI server / device (Fig. 17, 400), a base station (Fig. 17, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0300] In FIG. 19, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least some may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and a first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). In addition, each element, component, unit / part, and / or module within the wireless device (100, 200) may further include one or more elements. For example, the control unit (120) may be composed of one or more processor sets. For example, the control unit (120) may be composed of a set of a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, a memory control processor, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, volatile memory, non-volatile memory, and / or a combination thereof.

[0301] Examples of vehicles or autonomous vehicles to which the present invention is applied

[0302] Figure 20 illustrates a vehicle or autonomous vehicle applicable to the present invention. The vehicle or autonomous vehicle may be implemented as a mobile robot, a car, a train, a manned or unmanned aerial vehicle (AV), a ship, or the like.

[0303] Referring to FIG. 20, a vehicle or autonomous vehicle (100) may include an antenna unit (108), a communication unit (110), a control unit (120), a driving unit (140a), a power supply unit (140b), a sensor unit (140c), and an autonomous driving unit (140d). The antenna unit (108) may be configured as a part of the communication unit (110). Blocks 110 / 130 / 140a to 140d correspond to blocks 110 / 130 / 140 of FIG. 19, respectively.

[0304] The communication unit (110) can transmit and receive signals (e.g., data, control signals, etc.) with external devices such as other vehicles, base stations (e.g., base stations, road side units, etc.), and servers. The control unit (120) can control elements of the vehicle or autonomous vehicle (100) to perform various operations. The control unit (120) can include an ECU (Electronic Control Unit). The drive unit (140a) can drive the vehicle or autonomous vehicle (100) on the ground. The drive unit (140a) can include an engine, a motor, a power train, wheels, brakes, a steering device, etc. The power supply unit (140b) supplies power to the vehicle or autonomous vehicle (100) and can include a wired / wireless charging circuit, a battery, etc. The sensor unit (140c) can obtain vehicle status, surrounding environment information, user information, etc. The sensor unit (140c) may include an IMU (inertial measurement unit) sensor, a collision sensor, a wheel sensor, a speed sensor, an incline sensor, a weight detection sensor, a heading sensor, a position module, a vehicle forward / backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illuminance sensor, a pedal position sensor, etc. The autonomous driving unit (140d) may implement a technology for maintaining a driving lane, a technology for automatically controlling speed such as adaptive cruise control, a technology for automatically driving along a set path, a technology for automatically setting a path and driving when a destination is set, etc.

[0305] For example, the communication unit (110) can receive map data, traffic information data, etc. from an external server. The autonomous driving unit (140d) can generate an autonomous driving route and driving plan based on the acquired data. The control unit (120) can control the drive unit (140a) so that the vehicle or autonomous vehicle (100) moves along the autonomous driving route according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit (110) can irregularly / periodically acquire the latest traffic information data from an external server and can acquire surrounding traffic information data from surrounding vehicles. In addition, during autonomous driving, the sensor unit (140c) can acquire vehicle status and surrounding environment information. The autonomous driving unit (140d) can update the autonomous driving route and driving plan based on newly acquired data / information. The communication unit (110) can transmit information regarding the vehicle location, autonomous driving route, driving plan, etc. to the external server. External servers can predict traffic information data in advance using AI technology or other technologies based on information collected from vehicles or autonomous vehicles, and provide the predicted traffic information data to the vehicles or autonomous vehicles.

[0306] Here, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may include not only LTE, NR, and 6G, but also Narrowband Internet of Things for low-power communication. At this time, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, and may be implemented with standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification may perform communication based on LTE-M technology. At this time, for example, LTE-M technology may be an example of LPWAN technology, and may be called by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology can be implemented by at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above-described names. Additionally or alternatively, the wireless communication technology implemented in the wireless device (XXX, YYY) of the present specification can include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) considering low-power communication, and is not limited to the above-described names. For example, ZigBee technology can create PAN (personal area networks) related to small / low-power digital communication based on various standards such as IEEE 802.15.4, and can be called by various names.

[0307] The embodiments described above are combinations of components and features of the present invention in a predetermined form. Each component or feature should be considered optional unless explicitly stated otherwise. Each component or feature may be implemented without being combined with other components or features. Furthermore, it is also possible to form an embodiment of the present invention by combining some components and / or features. The order of operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment. It is self-evident that claims that do not have an explicit citation relationship in the patent claims may be combined to form an embodiment or may be incorporated as a new claim through a post-application amendment.

[0308] In this document, embodiments of the present invention have been described primarily focusing on the signal transmission and reception relationship between a terminal and a base station. This transmission and reception relationship is equally / similarly extended to signal transmission and reception between a terminal and a relay or a base station and a relay. Certain operations described as being performed by a base station in this document may, in some cases, be performed by its upper node. That is, it is obvious that various operations performed for communication with a terminal in a network composed of multiple network nodes including a base station may be performed by the base station or other network nodes other than the base station. The base station may be replaced by terms such as fixed station, Node B, eNode B (eNB), and access point. In addition, the terminal may be replaced by terms such as UE (User Equipment), MS (Mobile Station), MSS (Mobile Subscriber Station).

[0309] Embodiments of the present invention may be implemented by various means, for example, hardware, firmware, software, or a combination thereof. In the case of hardware implementation, an embodiment of the present invention may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, etc.

[0310] When implemented via firmware or software, an embodiment of the present invention may be implemented in the form of modules, procedures, functions, etc. that perform the functions or operations described above. The software code may be stored in a memory unit and executed by a processor. The memory unit may be located within or outside the processor and may exchange data with the processor via various known means.

[0311] It will be apparent to those skilled in the art that the present invention can be embodied in other specific forms without departing from the scope of the invention. Therefore, the above detailed description should not be construed as limiting in any respect, but rather as illustrative. The scope of the present invention should be determined by a reasonable interpretation of the appended claims, and all modifications within the scope of equivalents of the present invention are intended to be included within the scope of the present invention.

[0312] The embodiments of the present invention as described above can be applied to various mobile communication systems.

Claims

1. A step of transmitting a first message including type information of a first relay UE (user equipment) related to a multi-hop based U2N (UE to Network) relay to a base station; and A step of receiving a second message from the base station, the second message including configuration information for setting up an RLC (Radio Link Control) channel for the multi-hop based U2N relay, A method wherein the type information includes information about a first relay type or a second relay type based on whether the first relay UE is directly connected to the base station.

2. In paragraph 1, A method, characterized in that the type information includes information on the first relay type, based on the first relay UE performing the multi-hop based U2N relay through a Uu connection directly connected to the base station and a connection with another UE.

3. In paragraph 1, A method, characterized in that the type information includes information on the second relay type, based on the first relay UE performing the multi-hop based U2N relay without direct connection with the base station.

4. In paragraph 1, A method, characterized in that, based on the type information including information on the first relay type, the second message includes configuration information for setting an RLC channel for a Uu connection that is a direct connection with the base station and an RLC channel for a connection with another UE.

5. In paragraph 1, A method, characterized in that, based on the type information including information about the second relay type, the second message includes the configuration information for setting a first RLC channel for a first connection with a remote UE and a second RLC channel for a second connection with a second relay UE.

6. In paragraph 1, A method, characterized in that the first message is an RRCSetupRequest message, an RRCReestablishmentRequest message or an RRCResumeRequest message requesting an RRC (Radio Resource Control) connection related to the multi-hop based U2N relay.

7. In paragraph 1, A method, characterized in that the first message is a SUI (SidelinkUEInformationNR) message.

8. In paragraph 1, A method, characterized in that the RLC channel is established based on an e2e (end-to-end) bearer associated with the multi-hop based U2N relay.

9. A computer-readable recording medium having recorded thereon a program for performing the method described in Article 1.

10. In the first relay UE (user equipment), RF(Radio Frequency) transceiver; and comprising a processor connected to the RF transceiver; The processor controls the RF transceiver to transmit a first message including type information of a first relay UE (user equipment) related to a multi-hop based U2N (UE to Network) relay to a base station, and receives a second message including configuration information for setting an RLC (Radio Link Control) channel for the multi-hop based U2N relay from the base station. A first relay UE, wherein the type information includes information about a first relay type or a second relay type based on whether the first relay UE is directly connected to the base station.

11. In paragraph 10, A first relay UE, characterized in that the type information includes information on the first relay type, based on the first relay UE performing the multi-hop based U2N relay through a Uu connection directly connected to the base station and a connection with another UE.

12. In paragraph 10, A first relay UE, characterized in that the type information includes information on the second relay type, based on which the first relay UE performs the multi-hop based U2N relay without direct connection with the base station.

13. In a processing device controlling the first relay UE (User Equipment), at least one processor; and At least one memory coupled to said at least one processor and storing instructions, said instructions causing said first relay UE to: Transmitting a first message including type information of the first relay UE related to a multi-hop based U2N (UE to Network) relay to a base station, and causing the first relay UE to receive a second message including configuration information for setting an RLC (Radio Link Control) channel for the multi-hop based U2N relay from the base station, A processing device, wherein the type information includes information about a first relay type or a second relay type based on whether the first relay UE is directly connected to the base station.

14. A step of the base station receiving a first message including type information related to a multi-hop based U2N (UE to Network) relay from a first relay UE (user equipment); and The step of the base station transmitting a second message including configuration information for setting up an RLC (Radio Link Control) channel for the multi-hop based U2N relay based on the type information, A method wherein the type information includes information about a first relay type or a second relay type determined based on whether the first relay UE is directly connected to the base station.

15. At the base station, RF(Radio Frequency) transceiver; and comprising a processor connected to the RF transceiver; The processor controls the RF transceiver to receive a first message including type information of a first relay UE (user equipment) related to a multi-hop based U2N (UE to Network) relay, and transmits a second message including configuration information for setting an RLC (Radio Link Control) channel for the multi-hop based U2N relay based on the type information. A base station, wherein the type information includes information on a first relay type or a second relay type determined based on whether the first relay UE is directly connected to the base station.

Images