Method for configuring connection in consideration of pdb separation in multi-hop u2u operation and device therefor

Abstract

According to an embodiment, a method for operating a first relay user equipment (UE) related to quality of service (QOS) split in a multi-hop UE-to-UE relay involves the first relay UE: receiving QOS-related information from a source remote UE; performing a measurement on a first hop with the source remote UE and a second hop with a second relay UE; splitting the overall QoS into a QoS related to the first hop and a QoS related to the target remote UE from the second hop on the basis of the measurement; transmitting the QoS related to the first hop to the source remote UE; and transmitting, to the second relay UE, the QoS related to the target remote UE from the second hop.

Description

Connection establishment method considering PDB separation in multi-hop U2U operation and device therefor

[0001] This relates to a connection setup method and a device for the same, considering PDB (Packet Delay Budget) separation in multi-hop U2U (UE to UE relay) operation.

[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] In one embodiment, a connection can be established that takes into account PDB separation in multi-hop U2U operations. In addition, it clearly specifies how QoS splitting is performed when performing multi-hop U2U operations.

[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] One embodiment is a method for operating a first relay User Equipment (UE) related to QoS (Quality of Service) split in a multi-hop UE-to-UE relay, the method comprising: the first relay UE receiving QoS-related information from a source remote UE; the first relay UE performing measurement for a first hop with the source remote UE and a second hop with a second relay UE; the first relay UE splitting the overall QoS into a QoS related to the first hop and a QoS related to a target remote UE from the second hop based on the measurement; the first relay UE transmitting the QoS related to the first hop to the source remote UE; and the first relay UE transmitting the QoS related to the target remote UE from the second hop to the second relay UE.

[0018] One embodiment is a first relay UE involved in a Radio Link Failure (RLF) in a multi-hop User Equipment (UE)-to-UE relay, the first relay UE comprising at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, the operations comprising: receiving QoS-related information from a source remote UE; performing measurements for a first hop with the source remote UE and a second hop with a second relay UE; splitting an overall QoS into a QoS associated with the first hop and a QoS associated with a target remote UE from the second hop based on the measurements; transmitting the QoS associated with the first hop to the source remote UE; and transmitting the QoS associated with the target remote UE from the second hop to the second relay UE.

[0019] One embodiment is a non-volatile computer-readable storage medium storing at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a source remote UE, the operations comprising: receiving QoS-related information from a source remote UE; performing measurements for a first hop with the source remote UE and a second hop with a second relay UE; splitting an overall QoS into a QoS associated with the first hop and a QoS associated with a target remote UE from the second hop based on the measurements; transmitting the QoS associated with the first hop to the source remote UE; and transmitting the QoS associated with the target remote UE from the second hop to the second relay UE.

[0020] The above QoS-related information may include QoS information by RLC channel ID.

[0021] The first relay UE may receive an RRC configuration based on QoS related to the first hop from the remote UE.

[0022] From the second hop, the QoS associated with the target remote UE may be split again by the second relay UE.

[0023] Transmission of QoS related to the first hop may trigger SL RRC reconfiguration of the remote UE, and transmission of QoS related to the target remote UE from the second hop may trigger SL RRC reconfiguration of the second remote UE.

[0024] Transmission of QoS related to the first hop may trigger re-establishment of the RRC connection of the remote UE, and transmission of QoS related to the target remote UE from the second hop may trigger re-establishment of the RRC connection of the second remote UE.

[0025] The above QoS information may be an end-to-end PDB value.

[0026] The above QoS-related information may include an end-to-end bearer ID, an RLC channel ID mapped to the end-to-end bearer ID, and QoS for each RLC channel ID.

[0027] The QoS related to the target remote UE from the second hop may include an end-to-end bearer ID, an RLC channel ID mapped to the end-to-end bearer ID, and a remaining QoS for each RLC channel ID.

[0028] The first relay UE can receive a message satisfying QoS related to the first hop from the remote UE.

[0029] The above QoS may include a Packet Delay Budget (PDB).

[0030] In one embodiment, end-to-end QoS requirements can be satisfied by performing QoS split in multi-hop U2U operation.

[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 drawing for explaining a method for performing a relay connection between a terminal and a base station.

[0046] Figure 14 schematically illustrates how to switch from a direct route to an indirect route.

[0047] FIG. 15 and FIG. 16 are diagrams for explaining a procedure for U2U relay selection (UE-to-UE Relay Selection) without relay discovery.

[0048] Figure 17 schematically illustrates a flat protocol stack for L2 U2U relay.

[0049] Fig. 18 is a flowchart related to the embodiment.

[0050] FIGS. 19 to 25 are flowcharts related to various embodiments of the present invention.

[0051] Figure 26 illustrates a communication system applied to the present invention.

[0052] Figure 27 illustrates a wireless device applicable to the present invention.

[0053] Figure 28 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.

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

[0055] 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).

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

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

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

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

[0068] 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.

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

[0070] 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).

[0071] 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).

[0072] 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.

[0073] 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

[0074] 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.

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

[0076] 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.

[0077] 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.

[0078] 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).

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

[0080] 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).

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

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

[0083] 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.

[0084] 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.

[0085] 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.

[0086] 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.

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

[0088] - Satellite integrated network

[0089] - 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).

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

[0091] - 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.

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

[0093] - small cell networks

[0094] - Ultra-dense heterogeneous network

[0095] - High-capacity backhaul

[0096] - 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.

[0097] - Softwarization and virtualization

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

[0099] - 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.

[0100] - 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.

[0101] Figure 7 illustrates an electromagnetic spectrum according to an 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.

[0102] - Large-scale MIMO technology

[0103] - Hologram beamforming (HBF)

[0104] - Optical wireless technology

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

[0106] - Quantum communication

[0107] - Cell-free communication

[0108] - Integration of wireless information and power transmission

[0109] - Integration of wireless communication and sensing

[0110] - Integrated access and backhaul network

[0111] - Big data analysis

[0112] - Reconfigurable intelligent surface

[0113] - metaverse

[0114] - Blockchain

[0115] 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.

[0116] - 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.

[0117] 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.

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

[0119] 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.

[0120] 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.

[0121] 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.

[0122] 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.

[0123] 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.

[0124] 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.

[0125] 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.

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

[0127] 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).

[0128] 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.

[0129] 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.

[0130] 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.

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

[0132] 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 13 illustrates an example where the resource pool repeats with a cycle of NT subframes.

[0133] 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.

[0134] 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:

[0135] (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.

[0136] (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.

[0137] (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.

[0138] 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.

[0139] 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.

[0140] 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.

[0141] 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.

[0142] 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.

[0143] 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).

[0144] 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.

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

[0146] 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.

[0147] 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.

[0148] 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.

[0149] 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.

[0150] 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.

[0151] 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.

[0152] 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.

[0153] Figure 13 is a drawing for explaining a method for performing a relay connection between a terminal and a base station.

[0154] 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.

[0155] 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.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] 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.

[0160] 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.

[0161] For L2 UE-to-Network relay, in addition to the connection setup procedure:

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

[0163] - 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.

[0164] Figure 14 schematically illustrates how to switch from a direct route to an indirect route.

[0165] A direct remote UE can be switched to an indirect relay UE for service continuity of L2 U2N relay based on the procedure illustrated in FIG. 14.

[0166] Referring to FIG. 14, in step S1401, a remote UE may report one or more candidate relay UEs after measuring / discovering them. The remote UE may filter out appropriate relay UEs that meet higher layer criteria when reporting. The report of at least one candidate relay may include the relay UE's ID and SL RSRP information, wherein PC5 measurement-related details may be determined later.

[0167] In step S1402, the gNB decides to switch to the target relay UE and the target (re)configuration is optionally transmitted to the relay UE (S1403).

[0168] In step S1404, the RRC reconfiguration message for the remote UE may include the ID of the target relay UE, the target Uu, and the PC5 configuration.

[0169] In step S1405, if a connection is not yet established, the remote UE establishes a PC5 connection with the target relay UE.

[0170] In step S1406, the remote UE feeds back RRCReconfigurationComplete to the gNB via the target path using the target configuration provided in RRCReconfiguration.

[0171] In step S1407, the data path is switched.

[0172] FIG. 15 and FIG. 16 are diagrams for explaining a procedure for U2U relay selection (UE-to-UE Relay Selection) without relay discovery.

[0173] Referring to a given scenario (TR 23.752 section 6.8), when a source UE wants to communicate with a target UE, the source UE may first try to find the target UE by transmitting a Direct Communication Request or Solicitation message containing target UE information. If the source UE cannot reach the target UE directly, the source UE may try to discover a UE-to-UE relay to reach the target UE, and may also trigger the relay to discover the target UE. The source UE may integrate the discovery of the target UE and / or the discovery / selection of a U2U relay based on the following two alternatives:

[0174] - Alternative 1: U2U relay discovery / selection can be integrated into the unicast link setup procedure (see clause 6.3.3 of TS 23.287).

[0175] - Alternative 2: U2U relay discovery / selection can be integrated into the Model B direct discovery procedure.

[0176] A new field may be added to the Direct Communication Request or Solicitation message to indicate whether a relay is available for communication. This new field may be defined as Relay_indication. When a (source) UE broadcasts a Direct Communication Request or Solicitation message, the request message may include Relay_indication indicating whether a U2U relay is available. Meanwhile, for Release 17, the value of Relay_indication may be assumed to be limited to a single hop.

[0177] When the U2U relay receives the request message with the Relay_indication set, the U2U relay can decide whether to forward the request message (i.e., modify the message and broadcast it nearby). For example, the U2U relay can decide whether to forward the request message by considering the Application ID, authorization policy (e.g., Relay for a specific ProSe service), current traffic load of the Relay, and radio conditions between the Source UE and the Relay UE if there is a Relay Service Code.

[0178] Alternatively, multiple U2U relays may be used to reach the target UE (case 1), or the target UE may directly receive the request message from the source UE (case 2). In this case, the target UE may choose whether to respond to either the first or the second case. For example, the target UE may choose whether to respond to either the first or the second case based on signal strength, local policy (e.g., traffic load of the UE-UE relay), relay service code (if any), and / or operator policy (e.g., always preferring direct communication or only using some specific UE-UE relays).

[0179] Alternatively, the source UE may receive responses to the request message from multiple U2U relays, or may receive responses to the request message directly from the target UE. In this case, the source UE may select a communication path (direct path or indirect path) based on signal strength or operator policy (e.g., always preferring direct communication or using only certain UE-UE relays).

[0180] The above-described alternative 1 can be performed as shown in Fig. 15, and the above-described alternative 2 can be performed as shown in Fig. 16.

[0181] Figure 17(a) schematically illustrates a flat protocol stack for L2 U2U relay.

[0182] Figure 17(a) illustrates a user plane protocol stack for an L2 U2U relay, and Figure 17(b) illustrates a control plane protocol stack for an L2 U2U relay.

[0183]

[0184] Meanwhile, the QoS split operation in the current Rel-17 U2N is as follows. The gNB performs RRC reconfiguration to the remote UE / relay UE, and at this time, the Uu relay RLC channel can be configured through the Uu-RelayRLC-ChannelConfig of the relay UE via the SL-ConfigDedicatedNR IE disclosed in TS 38.331, and the SL relay RLC channel can be configured in the remote UE via SL-RLC-ChannelConfig. In the SL-RLC-ChannelConfig of the remote UE, the QoS split by the gNB (i.e., the value of the PDB that can be consumed when the remote UE transmits to the relay UE via SL among the entire PDB of data to be transmitted from the remote UE to the gNB via the relay UE) can be configured for each RLC channel ID.

[0185] In Rel-17 U2N relay, the gNB sets the RLC channel ID (and / or logical channel configuration / ID) to be used for SL communication in full configuration, the RLC channel ID to be used for the Uu link, and the split PDB value that each RLC channel can use for SL transmission.

[0186] In contrast, in Rel-18 U2U relay, it is unclear who can configure QoS split. In particular, it is ambiguous who can configure the configuration of each hop (e.g., RLC channel mapping) in a multi-hop situation. That is, how to configure the mapping relationship between the ingress RLC channel and the egress RLC channel in the SRAP layer of each relay UE and the target remote UE can be problematic. Therefore, various embodiments of the present invention are disclosed below regarding how to handle QoS split in a U2U relay, particularly in a multi-hop relay.

[0187] In the following description, the bearer ID is a value for identifying the channel between PDCP and SRAP, the RLC channel ID is a value for identifying the channel between SRAP and RLC, and the logical channel ID is a value for identifying the channel between RLC and MAC. The end-to-end bearer will be set from the source remote UE to the target remote UE, and since each relay UE does not have a PDCP / SDAP layer, splitting of the PQI level may not be possible. The value to be split is not the PQI value, but PDB splitting must be performed for each RLC channel (and / or bearer / logical channel). In the following description, the QoS value can be replaced with PDB. In the following description, the source remote UE can be called a U2U remote UE, the target remote UE can be called a peer U2U remote UE, and the relay UE can be called a U2U relay UE.

[0188]

[0189] According to an embodiment, a first relay UE related to a QoS (Quality of Service) split may receive QoS-related information from a source remote UE (S1801 of FIG. 18). The first relay UE may perform measurements for a first hop with the source remote UE and a second hop with a second relay UE (S1802). Based on the measurements, the first relay UE may split the entire QoS into a QoS related to the first hop and a QoS related to a target remote UE from the second hop (S1803). The first relay UE may transmit the QoS related to the first hop to the source remote UE (S1804). The first relay UE may transmit the QoS related to the target remote UE from the second hop to the second relay UE (S1805).

[0190] That is, in multi-hop U2U operation, the source remote UE transmits the end-to-end PDB value for each RLC channel to the relay UE1 connected to it, and the relay UE splits the PDB budget for each RLC channel and transmits it to the source remote UE. From the second hop, the QoS related to the target remote UE may be split again by the second relay UE. Thereafter, the first relay UE may receive a message that satisfies the QoS related to the first hop from the remote UE.

[0191] The first relay UE may receive an RRC configuration based on the QoS related to the first hop from the remote UE. That is, the source remote UE may perform SL RRC configuration on the relay UE1 according to the split QoS received from the relay UE1. Similarly, the relay UE1 may be matched with the operation of the source remote UE described above, and the relay UE2 may be matched with the relay UE1 described above to perform the same operation.

[0192] The above QoS-related information may include QoS information (end-to-end PDB value) by RLC channel ID. For example, the remote UE may transmit the RLC channel ID (and / or) end-to-end bearer ID) and the PDB value by RLC channel ID (and / or) end-to-end bearer ID) to the relay UE1 (using a PC5-RRC message). Alternatively, the QoS-related information may include an end-to-end bearer ID, an RLC channel ID mapped to the end-to-end bearer ID, and a QoS by the RLC channel ID. Similarly, the QoS related to the target remote UE from the second hop may include an end-to-end bearer ID, an RLC channel ID mapped to the end-to-end bearer ID, and a remaining QoS by the RLC channel ID.

[0193] Transmission of QoS related to the first hop may trigger SL RRC reconfiguration of the remote UE, and transmission of QoS related to the target remote UE from the second hop may trigger SL RRC reconfiguration of the second remote UE. That is, the source remote UE and relay UE of each hop that received the Split QoS may perform SL RRC reconfiguration of each hop.

[0194] In addition, transmission of QoS related to the first hop may trigger re-establishment of the RRC connection of the remote UE, and transmission of QoS related to the target remote UE from the second hop may trigger re-establishment of the RRC connection of the second remote UE. Since the SL RRC connection performed before the QoS Split by the relay UE may not have a configuration that reflects the QoS split, the source remote UE and the relay UE that received the QoS split value may re-establish the SL RRC connection.

[0195] As described above, end-to-end QoS requirements can be satisfied by defining QoS splits in multi-hop U2U relay operations. Furthermore, in the above embodiment, the UE that receives the RRC configuration determines the QoS splits, which has the following advantages.

[0196] Figure 19 illustrates a flowchart related to the above embodiment. Anything not described in detail in the following description of Figure 19 may be replaced by the above-described description, and the content described below is included in the above-described embodiment. In the following description, relay UE1 corresponds to the first relay UE, and relay UE2 corresponds to the second relay.

[0197] Referring to FIG. 19, in steps S1901a to S1901c, an SL connection (and / or SL RRC configuration) may be established between a source remote UE and a relay UE1, or between a relay UE1 and a relay UE2. In step S1901d, the source remote UE and a target remote UE may establish an SL connection, or the source remote UE and the target remote UE may perform SL RRC configuration for end-to-end bearer configuration.

[0198] In step S1902, the source remote UE can transmit QoS related information to the relay UE1.

[0199] In step S1910, the relay UE1 that received this can split the QoS (and / or PDB) to be used for the 1st-hop and subsequent hops based on the measurement of the SL signal strength of the 1st-hop and the 2nd-hop.

[0200] In step S1903a, relay UE1 transmits to the source remote UE the QoS value allowed for use in the 1st-hop, and in step S1903b, transmits to the relay UE2 the QoS value excluding the value allocated to the 1st-hop from the entire QoS (and / or PDB).

[0201] In step S1911, relay UE2, which has received QoS to be used for the 1st hop and subsequent hops, can perform QoS split, transmit the split QoS to be used for the 2nd hop to relay UE 1 (S1904a), and transmit the split QoS to be used for the 3rd hop to the target remote UE (S1904b).

[0202] The source remote UE that receives the split QoS value from relay UE1 can transmit the message according to the split QoS (PDB budget).

[0203] Figure 20 illustrates a case in which SL RRC Reconfiguration is performed for each hop after QoS split, unlike the embodiment described above. The main description is replaced with the description described above.

[0204]

[0205] In connection with the above description, the first relay UE may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations, wherein the operations may include: the first relay UE receiving QoS-related information from a source remote UE; the first relay UE performing measurements for a first hop with the source remote UE and a second hop with a second relay UE; the first relay UE splitting an overall QoS based on the measurements into a QoS associated with the first hop and a QoS associated with a target remote UE from the second hop; the first relay UE transmitting the QoS associated with the first hop to the source remote UE; and the first relay UE transmitting the QoS associated with the target remote UE from the second hop to the second relay UE.

[0206] Also, a non-volatile computer-readable storage medium storing at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a source remote UE, the operations may include: a first relay UE receiving QoS-related information from a source remote UE; the first relay UE performing measurements for a first hop with the source remote UE and a second hop with a second relay UE; the first relay UE splitting an overall QoS based on the measurements into a QoS associated with the first hop and a QoS associated with a target remote UE from the second hop; the first relay UE transmitting the QoS associated with the first hop to the source remote UE; and the first relay UE transmitting the QoS associated with the target remote UE from the second hop to the second relay UE.

[0207] ?

[0208] Meanwhile, the mapping relationship between the PQI value transmitted from the upper layer and the bearer can be configured when the source remote UE configures the end-to-end bearer to the target remote UE. Each relay UE can configure the mapping of the ingress RLC channel ID and the egress RLC channel ID on its own. At this time, the mapping relationship between the ingress RLC channel ID and the egress RLC channel ID can be configured as a relationship associated (and / or related) with the ID of the end-to-end bearer. For example, for the end-to-end bearer ID (A) in one relay UE, the ingress RLC channel ID (1) and the egress RLC channel ID (2) can be a mapping relationship, and this mapping relationship can be configured by the relay UE on its own.

[0209]

[0210] The above description relates to a subject receiving an SL RRC configuration (and / or a receiving UE of the SL RRC configuration) performing QoS splitting. Below, an example is disclosed in which a subject performing an SL RRC configuration (and / or a transmitting UE of the SL RRC configuration) performs QoS splitting.

[0211] Referring to FIG. 21, the source remote UE may receive measurement reporting for the next hop (the next hop (2nd-hop) based on the source remote UE) from the relay UE1 (S2102), and the source remote UE may perform QoS split (S2110). When the source remote UE performs QoS split, the source remote UE may perform QoS split together with SL RRC configuration. At this time, the values ​​that the source remote UE configures in the relay UE1 may be an RLC channel ID, a mapping relationship between an end-to-end bearer and an RLC channel ID, QoS (and / or PDB) of each end-to-end bearer, and a split QoS (and / or PDB) value for each RLC channel ID. And / or, a residual QoS (and / or PDB) value for each end-to-end bearer (and / or RLC channel ID) may be configured.

[0212] Similarly, relay UE1 can perform the same operation as the source remote UE described above, and relay UE2 can perform the same operation as relay UE1 described above.

[0213] For example, an SL connection (and / or SL RRC configuration) is established between a source remote UE and a relay UE, and between a relay UE and a relay UE (S2101a to c in FIG. 21), and the source remote UE and the target remote UE perform SL RRC configuration for end-to-end bearer configuration (S2101d in FIG. 21). The source remote UE can receive a measurement result of the 2nd hop from the relay UE1 (at this time, the measurement result of the 1st hop may be included). The source remote UE can perform QoS split using the measurement value of the 1st hop measured by the source remote UE and the measurement result value of the 2nd hop reported from the relay UE1. The source remote UE transfers the split QoS value to the relay UE1 (S2103). The value transferred at this time can use a PC5-RRC container. The values ​​included in the container can be the end-to-end bearer ID, the RLC channel ID mapped to the end-to-end bearer, the split QoS value of each RLC channel, and the remaining QoS value of each RLC channel (and / or end-to-end bearer) to be transmitted to the relay UE1.

[0214] Meanwhile, since the SL RRC Reconfiguration for each hop in S2101a~c is a value configured without performing QoS split, as illustrated in eh 22, the SL connection for each hop may need to be reconfigured after QoS split. In this case, the following values ​​may be set in the SL RRC reconfiguration (e.g., RRCReconfigurationSidelink) message that the source remote UE transmits to relay UE1 (or the relay UE transmits to another relay UE, or the relay UE transmits to the target remote UE).

[0215] - End-to-end bearer ID

[0216] - RLC channel ID mapped to end-to-end bearer ID

[0217] - QoS information split by each RLC channel ID

[0218] - Remaining QoS information split by each RLC channel ID

[0219] In cases where the initial SL connection is performed with arbitrary values ​​and then reconfiguration (and / or RRCReconfigurationSidelink) with the QoS split value is required after going through QoS split, the operation of FIG. 22 may be simpler than that of FIG. 20. This is because the split QoS value can be configured together with the SL RRC reconfiguration.

[0220] During the above process, if the source remote UE or relay UE performs SL RRC reconfiguration that reflects QoS split, a full configuration can be performed. Since the SL connections initially established for each hop may be default (and / or not QoS split) connections, they can be initialized and re-established with QoS split values. In this case, the SL RRC reconfiguration can be configured by including a full configuration indication.

[0221]

[0222] Meanwhile, a method for including QoS related information and split QoS information in an RRCReconfigurationSidelink message is disclosed below.

[0223] Figure 23 shows a flowchart of a case where QoS split and SL RRC Reconfiguration are performed together (QoS split is performed using only measurement values ​​of both hops based on the relay UE).

[0224] The source remote UE sets the RLC channel config (RLC channel ID, RLC config, logicalChannel config, QoS related information (and / or PDB)) to the relay UE1 via an RRCReconfigurationSidelink message. The RRCReconfigurationSidelink message can configure the RLC channel (and / or PDB) based on the end-to-end bearer between the source remote UE and the target remote UE. That is, the mapping relationship between the pre-configured end-to-end bearer and the 1st-hop RLC channel can be configured together (S2302a of FIG. 23). Upon receiving this, the relay UE1 can transmit the RLC channel ID and split PDB value while transmitting an RRCReconfigurationCompleteSidelink message to the source remote UE (S2302b). If the source remote UE receiving this is not satisfied with the allocated split PDB value, it can transmit an RRCReconfigurationSidelink message to the relay UE1, which may include the PDB value for each RLC channel configured by the source remote UE (S2303a', S2303b').

[0225] Relay UE1, which receives QoS related information (e.g., PDB) values ​​from a source remote UE and sets PDB values ​​for each RLC channel of the 1st hop, notifies the relay UE of the remaining PDB values, excluding the PDB value set for the 1st hop, among all available PDB values, when configuring an RLC channel. The RRCReconfigurationSidelink message can configure an RLC channel based on an end-to-end bearer between the source remote UE and the target remote UE. That is, a mapping relationship between a preset end-to-end bearer and a 2nd-hop RLC channel can be configured together (S2303a). Relay UE2 can transmit a split PDB value for each RLC channel while transmitting an RRCReconfigurationCompleteSidelink message to relay UE1 (S2303b). If the relay UE1 receiving this is not satisfied with the split PDB value, it can send an RRCReconfigurationSidelink message to the relay UE2, which can include the PDB value for each RLC channel configured by the relay UE1 (S2304a', S2304b').

[0226] Relay UE2, which has set up SL RLC of the 2nd-hop, can configure similar contents to the above-described contents to the target remote UE, and since it is the last hop, the PDB may appear to be determined based on the values ​​assigned in the previous other hops (S2304a, S2304b).

[0227] In this operation, the PDB value can be determined greedily over the first and second hops (i.e., the first hop is the most advantageous method), so the following method can be applied.

[0228] When the source remote UE transmits an RRCReconfigurationSidelink message to the relay UE1, the source remote UE may transmit the RLC channel configuration and QoS related information (required PDB per RLC channel / end-to-end bearer), the mapping relationship between the end-to-end bearer and the 1st-hop RLC channel (and / or) the measurement result (SD-RSRP, SL-RSRP) of the 1st hop together. Upon receiving this, the relay UE1 may transmit the RRCReconfigurationSidelink message to the relay UE2, the RLC channel configuration and QoS related information of the 2nd hop, the mapping relationship between the end-to-end bearer and the 2nd-hop RLC channel (and / or) the measurement result (SD-RSRP, SL-RSRP) of the 1st hop together.

[0229] Relay UE2, which receives this, can transmit the RRCReconfigurationSidelink message to the target remote UE along with the RLC channel configuration and QoS related information of the 3rd-hop, the mapping relationship between the end-to-end bearer and the 3rd-hop RLC channel (and / or) the measurement of the 1st hop (and / or) the 2nd hop (and / or) the measurement result (SD-RSRP, SL-RSRP) of the 3rd hop.

[0230] In the above description, the measurement value of each hop may be an actual measurement value. Or, it may be a level value representing it (e.g., good, normal, bad, etc.). If the values ​​measured by different relay UEs for the same hop are different (e.g., the value measured by the source remote UE and the value measured by relay UE1 for the 1st hop), the higher (and / or lower) value may be set as the representative value.

[0231] Once the final target remote UE learns the measurement value of each hop and the PDB value required for each bearer (and RLC channel) through RRCReconfigurationSidelink, the target remote UE can perform QoS split to configure the RLC-specific PDB values ​​between the target remote UE and relay UE2 (3rd-hop). The configuration can be transmitted through the RRCReconfigurationCompleteSidelink message. At this time, the transmitted RRCReconfigurationCompleteSidelink message must notify not only the RLC-specific PDB values ​​of the 3rd-hop, but also the remaining RLC-specific PDB values ​​(i.e., the remaining PDB values ​​after performing the 3rd-hop configuration from the required PDB per bearer notified by the source remote UE).

[0232] Similarly, you can set up PDBs for each RLC of the 2nd-hop and 1st-hop.

[0233] This method can perform QoS splitting more fairly because the relay / target remote UE that splits QoS can perform QoS splitting by considering the signal strength of other hops as well as the signal strength of both hops based on itself.

[0234] In multi-hop operation, when establishing an SL connection, the relay UE of the next hop can be determined by the previous relay UE.

[0235]

[0236] Meanwhile, in the above description, each relay UE may be a UE operating in mode 1. In this case, the relay UE receives configuration for SL operation from the gNB. Therefore, in order for the relay UE to properly configure the SL configuration for the next hop, RLC mapping information for the previous hop and the next hop, it must report the correct values ​​to the gNB. The mapping between the ingress RLC channel and the egress RLC channel can be configured by the relay UE itself when in mode 2, but may be configured by the gNB when operating in mode 1.

[0237] Therefore, when the relay UE operates in mode1 (and / or the relay UE is in RRC_CONNECTED state), the relay UE must report the following values ​​to the base station:

[0238] (configure) received from the previous relay UE (and / or source remote UE).

[0239] - End-to-end bearer ID

[0240] - (and / or) RLC channel ID mapped to end-to-end bearer ID

[0241] - (and / or) QoS information split by RLC channel ID

[0242] - (and / or) remaining QoS information split by each RLC channel ID

[0243] - Current hop count, total hop count

[0244] - QoS value per end-to-end bearer (value generated by source remote UE)

[0245] Measurement values, for example,

[0246] - Previous hop SL signal strength measured by the relay UE (SD / SL-RSRP),

[0247] - Current hop SL signal strength (SD / SL-RSRP) measured by the relay UE;

[0248] - Next hop SL signal strength reported from the next relay UE (SD / SL-RSRP),

[0249] (Whether it is SD-RSRP or SL-RSRP may need to be indicated. At this time, assuming that the source remote UE - relay UE1? relay UE2? relay UE3? relay UE4? target remote UE are in a connected state, and if relay UE2 is in RRC_CONNECTED state, the previous hop based on relay UE2 means relay UE1 and relay UE2, the current hop means relay UE2 and relay UE3, and the next hop means relay UE3 and relay UE4)

[0250] When the source remote UE operates in mode1, the source remote UE can report the following information to its serving base station for U2U operation. This reporting can be done via SidelinkUEINformatioion (SUI).

[0251] - The (L2 / local) ID of the target remote UE and any QoS (e.g., QoS profile, PDB) information that may be associated with it. That is, the QoS information received from the upper layer of the source remote.

[0252] - The (L2 / local) ID of the relay UE selected by the source remote UE, and QoS information that may be associated with it, e.g., split QoS information received from the relay UE.

[0253] - The source remote UE notifies the target remote UE of the association between the selected relay UE (L2 / local) ID and the U2U relay operation.

[0254] - In case of multi-hop U2U operation, if the total hop count (and / or expected hop count) is known through PC5-S (e.g., discovery message, DCR / DCA) or PC5-RRC message, then that value.

[0255] - Split QoS information when split QoS information is received from the relay UE.

[0256] - Signal strength between the source remote UE and the relay UE as measured by the source remote UE (e.g., SD-RSRP, SL-RSRP)

[0257] The serving gNB of a source remote UE performing Mode-1 operation can configure the following information to the source remote UE (i.e., the source remote UE can expect the following information to be configured by its serving gNB):

[0258] - SRAP, RLC, MAC, PHY configuration between source remote UE and relay UE

[0259] - Mapping relationship between end-to-end bearer ID (and / or index) and first-hop RLC ID (corresponding to SRAP configuration)

[0260] - Local ID of the source remote UE (and / or) relay UE

[0261] - Split QoS-related information when the serving gNB of the source remote UE performs QoS split.

[0262] - SDAP, PDCP configuration between source remote UE and target remote UE.

[0263] When a relay UE operates in mode-1, the relay UE can report the following information to its serving gNB (via SUI):

[0264] - All information configured from the source remote UE or previous (and / or next) relay UE described above, when reporting such information, the (L2 / local) ID of the source remote ((and / or) previous relay) UE that transmitted the information also needs to be reported.

[0265] - (Assuming that the relay UE has the authority to select the relay UE for the next hop,) the relay UE (L2) ID of the next-hop selected by the relay UE, and information that can inform the target remote UE that this is the one selected for it (e.g., informing the (L2) ID of the selected relay UE together with the (L2) ID of the target remote UE).

[0266] - Remaining QoS information (e.g., remaining PDB value, which may be a value assigned by bearer index (ID) or RLC channel ID) if received from another connected relay UE / source remote UE.

[0267] - The received value when split QoS information (values ​​available for the current hop) is received from the previous (and / or next) relay UE (and / or source remote UE). Alternatively, it may include original QoS profile information, split QoS profile information, etc.

[0268] - The assigned local ID value, if assigned a local ID from the source remote UE or a previous (and / or next) remote UE.

[0269] - For multi-hop U2U relay operation, total (expected / estimated) hop count and own current hop count.

[0270] - SL-RSRP (e.g., SD-RSRP, SL-RSRP) values ​​of the previous hop, (and / or) next hop measured or reported by the relay UE.

[0271] The serving gNB of a relay UE performing Mode-1 operation can configure the following information to the corresponding relay remote UE (i.e., the relay UE can expect the following information to be configured from its serving gNB):

[0272] - SRAP, RLC, MAC, PHY configuration between the relay UE and the next relay UE

[0273] - RLC channel ID mapping relationship between the previous relay UE and the next relay UE (i.e., mapping configuration between ingress RLC channel and egress RLC channel)

[0274] - Mapping relationship between the end-to-end bearer ID (and / or index) and the next transmission hop RLC ID. (This may correspond to SRAP configuration.)

[0275] - local ID of relay UE (and / or) (previous / next) relay UE

[0276] - Split QoS-related information when the serving gNB of the relay UE performs QoS split.

[0277] When a relay UE operates in mode 1 and receives configuration for SL connections from the gNB, we propose values ​​to report to ensure proper reception. Using this information, the gNB can perform RLC mapping, QoS splitting, etc. for the relay UE to configure SLs for U2U relay.

[0278]

[0279] Meanwhile, in connection with the above-described explanation or as an independent embodiment, an embodiment is disclosed below in which the order of establishing an initial SL connection varies depending on the Discovery model.

[0280] For discovery models A and B, the SL connection (and / or SL RRC Reconfiguration) of each hop must be established before the end-to-end SL connection (and / or end-to-end SL RRC Reconfiguration).

[0281] Even if a relay UE is found through the discovery procedure, the SL connection between the source remote UE and the relay UE, or between the relay UEs, must be established by sending and receiving DCR / DCA messages. During the DCR / DCA process, security must be established for each single hop, and a state in which RRC messages can be transmitted for a single hop must be established so that each hop can establish an SL connection and transmit messages through the link.

[0282] For example, in the case of Discovery model A / B, SL connection can be made in the following order as shown in Figure 25.

[0283] However, the order of the SL connection procedure may be different in methods such as integrated discovery (relay discovery and selection is integrated into the unicast link establishment procedure). In the integrated discovery method, a DCR message is transmitted to the target remote UE through multiple relay UEs, and the target remote UE selects a relay UE and transmits a DCA message to the relay UE. By exchanging security-related messages before receiving the DCR message and transmitting the DCA message, a state in which PC5-RRC messages can be exchanged is established after exchanging the DCR and DCA messages. Therefore, when selecting a relay UE using the integrated discovery method, when the source remote UE receives the DCA message, it can be determined that a state in which RRC messages can be sent from the source remote UE to the target remote UE has been established. Therefore, the SL connection may be established in the following order.

[0284] Once an end-to-end SL connection is established, the end-to-end bearer ID can be considered to have been configured between the source remote UE and the target remote UE. Therefore, the SL connection made at each hop thereafter can be considered to be an SL connection that reflects QoS split. Since the end-to-end bearer has been established, the RLC channel ID can be determined based on the end-to-end bearer, the ingress RLC channel ID and egress RLC channel ID mapping can be formed, and the QoS split required by each RLC channel can also be performed. Therefore, this method of establishing an SL connection can shorten the SL configuration time that reflects the entire QoS.

[0285] By proposing different PC5 configuration procedures depending on the discovery model, it is possible to configure the entire bearer configuration and RLC channel mapping relationship reflecting QoS split more quickly in a specific discovery model.

[0286] In the above technology, the relay UE can be extended to include gNB, IAB-node, etc.

[0287]

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

[0289] 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.

[0290] 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.

[0291] Figure 26 illustrates a communication system applied to the present invention.

[0292] Referring to FIG. 26, 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.

[0293] 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).

[0294] 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.

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

[0296] Figure 27 illustrates a wireless device applicable to the present invention.

[0297] Referring to FIG. 27, 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. 26.

[0298] 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.

[0299] Specifically, the first wireless device or terminal (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 above embodiments.

[0300] The processor (102) can perform the following operations.

[0301] The method may include receiving QoS-related information from a source remote UE; performing measurements for a first hop with the source remote UE and a second hop with a second relay UE; splitting the overall QoS into a QoS related to the first hop and a QoS related to a target remote UE from the second hop based on the measurements; transmitting the QoS related to the first hop to the source remote UE; and transmitting the QoS related to the target remote UE from the second hop to the second relay UE.

[0302] 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.

[0303] 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.

[0304] 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.

[0305] 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.

[0306] 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.

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

[0308] Figure 28 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 26).

[0309] Referring to FIG. 28, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 27 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 an additional element (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. 28. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 27. 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).

[0310] 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. 26, 100a), a vehicle (Fig. 26, 100b-1, 100b-2), an XR device (Fig. 26, 100c), a portable device (Fig. 26, 100d), a home appliance (Fig. 26, 100e), an IoT device (Fig. 26, 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. 26, 400), a base station (Fig. 26, 200), a network node, etc. Wireless devices may be mobile or stationary depending on the use / service.

[0311] In FIG. 28, 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.

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

[0313] Figure 29 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.

[0314] Referring to FIG. 29, 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. 28, respectively.

[0315] 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.

[0316] 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.

[0317] 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.

[0318] 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.

[0319] 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).

[0320] 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.

[0321] 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.

[0322] 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.

[0323]

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

Claims

1. In a method of operation of a first relay UE (User Equipment) related to QoS (Quality of Service) split in a multi-hop UE-to-UE relay, The first relay UE receives QoS-related information from the source remote UE; The first relay UE performs measurements for the first hop with the source remote UE and the second hop with the second relay UE; The first relay UE splits the overall QoS based on the measurement into a QoS related to the first hop and a QoS related to the target remote UE from the second hop; The first relay UE transmits the QoS related to the first hop to the source remote UE; and The first relay UE transmits QoS related to the target remote UE from the second hop to the second relay UE; A method comprising:

2. In paragraph 1, A method in which the above QoS-related information includes QoS information by RLC channel ID.

3. In paragraph 1, A method wherein the first relay UE receives an RRC configuration based on QoS related to the first hop from the remote UE.

4. In paragraph 1, A method wherein the QoS related to the target remote UE from the second hop is split again by the second relay UE.

5. In paragraph 1, A method wherein transmission of QoS related to the first hop triggers SL RRC reconfiguration of the remote UE, and transmission of QoS related to the target remote UE from the second hop triggers SL RRC reconfiguration of the second remote UE.

6. In paragraph 1, A method wherein transmission of QoS related to the first hop triggers re-establishment of an RRC connection of the remote UE, and transmission of QoS related to the target remote UE from the second hop triggers re-establishment of an RRC connection of the second remote UE.

7. In paragraph 1, The above QoS information is an end-to-end PDB value.

8. In paragraph 1, A method wherein the above QoS-related information includes an end-to-end bearer ID, an RLC channel ID mapped to the end-to-end bearer ID, and QoS for each RLC channel ID.

9. In paragraph 1, A method in which the QoS related to the target remote UE from the second hop includes an end-to-end bearer ID, an RLC channel ID mapped to the end-to-end bearer ID, and a remaining QoS for each RLC channel ID.

10. In paragraph 1, A method in which the first relay UE receives a message satisfying QoS related to the first hop from the remote UE.

11. In paragraph 1, A method wherein the above QoS includes a Packet Delay Budget (PDB).

12. In the first relay UE related to RLF (Radio Link Failure) in a multi-hop UE (User Equipment)-to-UE relay, at least one processor; and At least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations; The above actions are, Receive QoS related information from the source remote UE; Perform measurements for the first hop with the source remote UE and the second hop with the second relay UE; Based on the above measurement, split the overall QoS into QoS related to the first hop and QoS related to the target remote UE from the second hop; Transmitting the QoS associated with the first hop to the source remote UE; and A first relay UE, which includes transmitting QoS related to the target remote UE from the second hop to the second relay UE.

13. A non-volatile computer-readable storage medium storing at least one computer program comprising instructions that, when executed by at least one processor, cause the at least one processor to perform operations for a source remote UE, The above actions are, Receive QoS related information from the source remote UE; Perform measurements for the first hop with the source remote UE and the second hop with the second relay UE; Based on the above measurement, split the overall QoS into QoS related to the first hop and QoS related to the target remote UE from the second hop; Transmitting the QoS associated with the first hop to the source remote UE; and A storage medium comprising transmitting QoS related to a target remote UE from the second hop to the second relay UE.

Images